sshd problem

[Igor Gueths]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all. Turns out I fixed the problem I was having and all is well now. I
forgot to enable md5-password support in configure script. Thanks all for
your suggestions. I may switch to running under tcprapper such as inetd,
however I've heard it takes longer to negotiate connections when doing
this.

On Tue, 12 Aug 2003, Adam Myrow wrote:

> On Tue, 12 Aug 2003, igueths at comcast.net wrote:
>
> > Hi there. I can't login from the current machine I am at, but a friend said
> > he can get into the box no problem using his account. I'm not running sshd
> > under inetd so that wouldn't be a problem as was the case with telnetd. I
> > should probably check into the public keys/authorized_keys.
>
> I am under the impression that you compiled your own sshd.  Is that true?
> If so, I think you have to enable tcp wrapper support for it to work
> correctly.  Then, even though it doesn't run from inetd, you would need a
> line in /etc/hosts.allow like:
> sshd: all
> to make it work.  I never compiled my own sshd.  I've always used the one
> that came with the distribution and had to use hosts.allow to enable it as
> I have all services denied by default.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Made with pgp4pine 1.75-6

iD8DBQE/Oc/MGT7f58lCbH0RAvoiAJ9l0OFQkZv34MUwKZb3DdP1X5BrFACfWuGr
1qhdhv5Thdbb+mKhemGMkPI=
=glTb
-----END PGP SIGNATURE-----