• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Worrying protected directories behaviour

ghazlewood

Basic Pleskian
I have a Plesk 11.0.9 server (fully up-to-date) running Centos x86_64.

A client called today to say that they were having problems logging in to a protected directory with the usual username and password and additionally they had discovered that they could access a protected directory with the username only, leaving the password blank.

This is very worrying and of course immediately made me think something was up with the server. Checking the database directly I was expecting to see the pd_users table connected to the accounts table by id but the pd_users table has 0 for every account_id. Unless I am mistaken on the structure of the database something seems to be wrong here. Looking at the accounts table again I was expecting to see all passwords encrypted with the new $AES format but some are still using the crypt format and some are blank!

The client in question has been able to login correctly with their details in the past and although this client has been through several versions of Plesk (7, 8, 9 and 10) I am now worried that there is something inherently wrong with authentication on this server.

Anyone have any ideas or suggestions before I use the Mass Password Reset script to update all protected directories?
 
Back
Top