Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • I ISPConfig 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 590
    • Issues 590
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 49
    • Merge requests 49
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #4191
Closed
Open
Issue created Sep 15, 2016 by Viliam Jobko@viliam.jobko

Updating database user password on MySQL 5.7 leads to "double hash"

How to reproduce issue

Using ISPConfig 3.1 and MySQL 5.7 try to update database user password. The password get "double hashed" (eg. setting password "SuperStrongPWD" get saved as "*3393F833E1C626709E4230489AF71599FF3B6496" instead of "*CC37CB1BF2C651C2AA0CC64461E3C73E816D8F39").

Creating new database user is not affected by this issue.

Cause

ISPConfig is using SET PASSWORD to change database user password. Starting from MySQL 5.7.6 syntax for SET PASSWORD were changed from:

SET PASSWORD FOR user = "password_hash";

to:

SET PASSWORD FOR user = "password";

But ISPConfig is still sending "password_hash" instead of "password" causing password to get hashed again.

Temperory workaround

Delete, create user with desired password and attach him to desired databases.

Assignee
Assign to
Time tracking