MD5 hashing produces inconsistent output for /etc/pam_pgsql.conf option:
Bug #578556 reported by
Randall Svancara
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam-pgsql (Debian) |
Fix Released
|
Unknown
|
|||
pam-pgsql (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
There is already a bug report on this at sourceforge. I am using Ubuntu Lucid Lynx.
http://
The package, libpam_pgsql, generates an inconsistent md5 hash with what md5 in postgresql generates. for example,
After hacking pam_pgsql so that I could see the hash, the md5 hash i noticed the hashes were being generated differently.
Clear text works fine, but pw_type = md5 does not.
I applied a fix by specifying this option to the configure script:
$ ./configure CFLAGS=-D__alpha
This alters the setting of the uint32 type in md5.h
Kudos to Philip Kershaw.
Changed in pam-pgsql (Debian): | |
status: | Unknown → Fix Released |
To post a comment you must log in.
I think this bug is a duplicate of Debian bug #584683 [1] that has been fixed in Debian's pam-pgsql version 0.7.1-2.
[1] http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 584683