On Fri, Jun 29, 2001 at 05:19:48PM +1000, Howard Lowndes wrote:
> That still allows the host key to be permanently stored, and if it doesn't
> match an already stored key then you get a warning message but the
> connection continues to be established.
Yes, I knew that, but at least it doesn't wait for you to answer. It's
the best I can offer.
> Incidentally, with openssh the man page says that one of the agruments to
> StrictHostKeyChecking can be "ask". I couldn't get this to work.
Works for me:
[johnc@dropbear ~]$ ssh -V
OpenSSH_2.5.2p2, SSH protocols 1.5/2.0, OpenSSL 0x0090581f
[johnc@dropbear ~]$ ssh -o StrictHostKeyChecking=ask dropbear
The authenticity of host 'dropbear (192.168.1.16)' can't be established.
RSA1 key fingerprint is 8f:c7:dd:11:0d:49:c4:53:80:08:70:b8:4c:4c:7c:df.
Are you sure you want to continue connecting (yes/no)?
Cheers,
John
--
whois [EMAIL PROTECTED]
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
