• 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.

How do you let this happen?

R

ripdeath987

Guest
Please let me know how can you in your coding not mask the passwords when a PHP error occurs.

A client tried to add an MSSQL database user and Plesk threw the classic : The operation you were performing failed...etc

The twist about this that the error shown to the client in the Additional information there is the FULL command ran on the MSSQL server including the IP , the SA user and the PASSWORD FOR THE SA USER.

CAN SOMEONE PLEASE EXPLAIN WHY THIS IS SHOWN TO THE CLIENT SIDE????
 
Back
Top