little improvement in security/pam-mysql

[Roman Neuhauser]

# savrus at mexmat.net / 2006-03-08 10:00:57 +0300:
> Tue, 7 Mar 2006 23:39:53 +0100
> Roman Neuhauser <neuhauser at sigpipe.cz>:
> 
> > # savrus at 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?
> 
> Thank you for the answer.
> In my case it is not set, you see. I also can't see this (and even
> MD5Data) in any file except pam_mysql.c.

    I was wrong, sorry for wasting your time. I don't know where the
    HAVE_MD5DATA constant is supposed to come from.

-- 
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