Are you running debian or a variant? This is supposed to be a debian specific problem. Also it doesnt occur if you simply run your sshd on a different port. but try to setup a tcp wrapper or something to forward a local port to another ssh server. Then this occurs.
On 9/17/07, Shyam Mani <[EMAIL PROTECTED]> wrote: > > On 9/17/07, Samir Kuthiala <[EMAIL PROTECTED]> wrote: > > > just that it has trouble swallowing 127.0.0.1. From what I understand > after > > some googling, this is one of the security policies in ssh to not allow > > connections to a known host (in this case itself) at a different port. > So > > its something on my host machine which blocks calls of this type. > > Umm, can't seem to reproduce. > > [EMAIL PROTECTED] ~ $ ssh -p 2222 127.0.0.1 > The authenticity of host '127.0.0.1 (127.0.0.1)' can't be established. > RSA key fingerprint is eb:a2:be:59:30:70:e0:d3:5e:1d:6d:1a:8e:71:83:a1. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added '127.0.0.1' (RSA) to the list of known hosts. > Password: > Last login: Mon Sep 10 23:12:22 2007 > > [EMAIL PROTECTED] ~ $ > > > -- > Shyam Mani | http://xinetd.accosted.net/ > Gentoo Dev | http://dev.gentoo.org/~fox2mike > Email | [EMAIL PROTECTED] > GPG Key | 0xFDD0E345 >
_______________________________________________ Slugnet mailing list [email protected] http://www.lugs.org.sg/mailman/listinfo/slugnet
