I tried the configure line you suggested, but with no luck. I moved to
OpenSSH 2.9p1 and had the same problem.
Is there a possibility that --with-md5-passwords isn't working? I would
really hate to have to hack the md5crypt function in the source just to
get it to work.
Doug
On Thu, 24 May 2001, Julius C. Duque wrote:
> On Wed, 23 May 2001, Doug Hass wrote:
>
> > I'm using Slackware 7, OpenSSH 2.5.2p2, and OpenSSL 0.9.6a
> >
> > My configure line:
> >
> > ./configure --prefix= --sysconfdir=/etc --without-tcp-wrappers
> > --without-pam --with-ssl-dir=/usr/bin --without-rsh --without-xauth
> > --with-md5-passwords --with-shadow --with-pid-dir=/var/run
>
> (1) You didn't specify a path to the --prefix option.
> (2) You didn't specify the path of your ssl in the --with-ssl-dir option
>
> These may or may not solve your problem, but try it out anyway.
> As a guide, try my own configure options below. I have used this on
> 2 Linux boxes, one is Slackware 7, the other is Red Hat 6.
>
> --------------------
>
> ./configure --host=i686-pc-linux-gnu --x-includes=/usr/X11R6/include
> --x-libraries=/usr/X11R6/lib --with-ssl-dir=/usr/local/ssl
> --with-random=/dev/urandom --with-catman=man --with-tcp-wrappers
> --with-md5-passwords --with-lastlog=/var/log/lastlog --with-ipv4-default
>
> --------------------
>
> I would also discourage you from disabling tcp wrapper. tcp wrapper
> checks whether a host trying to establish connection to your box is
> allowed or not. ssh only encrypts communication (thus protecting the
> contents of your traffic); ssh does not shut out the bad guys trying
> to get hold of your server.
>
> Also, there is already openssh 2.9p1.
>
>
>
> > You'll note that I'm USING --with-md5-passwords. In the Makefile, I've
> > added -lcrypt, but I can only login with NON md5 passwords.
>
> You don't need to add -lcrypt manually. The configure script will do
> this for you.
>
> --
> Under capitalism, man exploits man.
> Under communism, it's just the opposite.
> -- J.K. Galbraith
>
