Hi!
When using an old version (from 2.4.41) of slapasswd, I noticed two things:
1) Using "-h SSHA", slappasswd was asking for passwords first, then telling me: "Password generation failed for scheme SSHA: scheme not recognized"
I think "SSHA" is unique enough to recognize; and if it's not, then complain before asking for passwords.
2) When I mistyped the option as "-h '{SSHA}>'", slappasswd did not complain and produce some output.
I think if it's picky on the first case, it should also be for the second case (assuming the output "{SSHA}oTEDKWKn0fimGo6J8de0I5qRixGWJxhJ" was correct overall)
Maybe check if these problems still exist in the current version.
Regards, Ulrich Windl
--On Monday, October 31, 2022 12:23 PM +0100 Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
Hi!
When using an old version (from 2.4.41) of slapasswd, I noticed two things:
- Using "-h SSHA", slappasswd was asking for passwords first, then
telling me: "Password generation failed for scheme SSHA: scheme not recognized"
I think "SSHA" is unique enough to recognize; and if it's not, then complain before asking for passwords.
The man page is very explicit on what the valid values are. SSHA is not a valid value.
Regards, Quanah
openldap-technical@openldap.org