You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some problems with using legacy authentication with Firebird 4:
* Using the default existing legacy sysdba/masterke works
* Creating a new user with the Legacy_UserManager (create user ... password '...' using plugin Legacy_UserManager) or with gsec (Legacy_UserManager is the first in the list), and trying to login leads to an authentication failure
* Using gsec to alter the password of the legacy sysdba and then trying to login leads to an authentication failure (even if I changed to masterke or masterkey)
The above seems to suggest that the Legacy_UserManager is broken when hashing passwords
NOTE: Vlad already committed a fix
The text was updated successfully, but these errors were encountered:
Submitted by: @mrotteveel
I have some problems with using legacy authentication with Firebird 4:
* Using the default existing legacy sysdba/masterke works
* Creating a new user with the Legacy_UserManager (create user ... password '...' using plugin Legacy_UserManager) or with gsec (Legacy_UserManager is the first in the list), and trying to login leads to an authentication failure
* Using gsec to alter the password of the legacy sysdba and then trying to login leads to an authentication failure (even if I changed to masterke or masterkey)
The above seems to suggest that the Legacy_UserManager is broken when hashing passwords
NOTE: Vlad already committed a fix
The text was updated successfully, but these errors were encountered: