author | hickert <hickert@594d385d-05f5-0310-b6e9-bd551577e9d8> | |
Thu, 19 Jul 2007 05:50:58 +0000 (05:50 +0000) | ||
committer | hickert <hickert@594d385d-05f5-0310-b6e9-bd551577e9d8> | |
Thu, 19 Jul 2007 05:50:58 +0000 (05:50 +0000) | ||
commit | ea4959a6ed5e679cf8a352a26cec8c37b2212e3f | |
tree | d00b42b0fbd1872a29a5d74b428e0441096b803c | tree | snapshot |
parent | 8a851db142963c391cadb76da770a9e76f7797b3 | commit | diff |
Applied patch from Ticket 112.
Updated password method hash names to uppercase :
{crypt} to {CRYPT} and so on
TICKET DESC :
Currently some password classes use a lowercase password hashing scheme string in the userPassword attribute whilst others use an uppercase hashing string. rfc2307 and rfc2307bis do not dictate a standard but the uppercase string is a representation that is being used historically by different vendors, including OpenLDAP itself.
I propose to use uppercase everywhere (see attached patch). Since openldap/slapppaswd uses the uppercase notation itself I do not suspect any regressions on any deployed systems will occur.
I know of an application that syncs passwords from LDAP for internal usage and trips over lowercase representation (which is a bug in that program ;-) ). That bug showed me that GOsa didn't handle this consistently.
git-svn-id: https://oss.gonicus.de/repositories/gosa/branches/2.5@6915 594d385d-05f5-0310-b6e9-bd551577e9d8
Updated password method hash names to uppercase :
{crypt} to {CRYPT} and so on
TICKET DESC :
Currently some password classes use a lowercase password hashing scheme string in the userPassword attribute whilst others use an uppercase hashing string. rfc2307 and rfc2307bis do not dictate a standard but the uppercase string is a representation that is being used historically by different vendors, including OpenLDAP itself.
I propose to use uppercase everywhere (see attached patch). Since openldap/slapppaswd uses the uppercase notation itself I do not suspect any regressions on any deployed systems will occur.
I know of an application that syncs passwords from LDAP for internal usage and trips over lowercase representation (which is a bug in that program ;-) ). That bug showed me that GOsa didn't handle this consistently.
git-svn-id: https://oss.gonicus.de/repositories/gosa/branches/2.5@6915 594d385d-05f5-0310-b6e9-bd551577e9d8
include/class_password-methods-crypt.inc | diff | blob | history | |
include/class_password-methods-md5.inc | diff | blob | history | |
include/class_password-methods-ssha.inc | diff | blob | history |