Date: Tue, 7 Mar 2006 23:39:53 +0100 From: Roman Neuhauser <neuhauser@sigpipe.cz> To: Ruslan Savchenko <savrus@mexmat.net> Cc: freebsd-ports@freebsd.org Subject: Re: little improvement in security/pam-mysql Message-ID: <20060307223953.GB4435@isis.sigpipe.cz> In-Reply-To: <20060307.223131.635794621.savrus@mexmat.net> References: <20060307.223131.635794621.savrus@mexmat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
# savrus@mexmat.net / 2006-03-07 22:31:31 +0300:
> When I tried to set crypt=md5, I saw message
>
> Mar 3 17:00:24 ssh login: pam_mysql - non-crypt()ish MD5 hash is not supported
> in this build.
>
> Looking throw source shows that it depends on HAVE_PAM_MYSQL_MD5_DATA
> definition. One way to get it defined is to have HAVE_MD5DATA defined
> (and MD5Data() in md5.h). FreeBSD's sys/md5.h has MD5Data(), but no
> HAVE_MD5DATA. If HAVE_MD5DATA is defined in pam_mysql.c md5 passwords
> work well, so one way to fix this is to apply attached patch to
> pam_mysql.c
> --- pam_mysql.c.old Tue Mar 7 21:54:04 2006
> +++ pam_mysql.c Tue Mar 7 21:55:56 2006
> @@ -121,6 +121,7 @@
>
> #ifndef HAVE_OPENSSL
> #ifdef HAVE_MD5_H
> +#define HAVE_MD5DATA
> #include <md5.h>
> #endif
This is not the right fix. HAVE_MD5DATA is probably supposed to get
set by pam-mysql's configure script. What's the output of running
make configure in the port, and what's in ${WRKSRC}/config.log?
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060307223953.GB4435>