Skip difficult password check for database user restores

Version 1.36


When the difficult password enforcement option is enabled, during database restores, if the user didn't exist, DA creates a temp random password which may or may not pass the difficult password check, and the user is attempted to be created normally. The crypted password is then set to overwrite the other password in a seperate step. If the temp password didn't pass the check, the db user doesn't get created, and the reset of the crypted password fails. The net effect is that for some users, they'll be missing after the restore. The fix consist of a new flag to skip the difficult password check for restores, since that password is only very temporary and is never used.

Interested to try DirectAdmin? Get a 30-day Free Trial!