• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Staying secure without safe_mode?

J

JohnD@

Guest
I´ve always onfigured safe_mode as on with all webhosting servers. Now, I will start using SWSOFT´s Sitebuilder along with PLESK 8.2 which requires safe_mode to be set to off.

Question is, what are the alternatives to safemode to keep the server from beeing hacked. Using Scott´s ASL as well, but I do not think that it compensates fully for safe_mode?

Any suggestiongs would be welcome. Thanks.
 
PHP safe_mode is certainly not the be all and end all of security. I advise you to enable safe_mode globally (in /etc/php.ini) and disable it only for domains that run software that cannot function under safe_mode.
 
Back
Top