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

Question There are accounts with passwords encrypted using a deprecated algorithm

yes I have already looked at. if I understand correctly then this script sets new passwords? then the new password would have to be exchanged for hundreds of customers in their scripts.
 
Alternative solution could be (theoretically):
Modify the login script of Plesk in a way, that it also checks against the algorythm used in confixx and automatically update the hash on a login.
I did such a thing for converting oscommerce users into modified shop with a phppass modification.
Drawback is ... it remains the old encryption until the user logs in ... in some cases that could happen never

But carefull! I have absolutely no idea if this is possible somehow without microupdates or mayor updates removing your modification.
In my case it worked, but it was not plesk.
 
Back
Top