You are not logged in.

#1 2013-05-02 05:45:55

testcore
Member
Registered: 2012-07-07
Posts: 8

[SOLVED-ish] SSH not respecting StrictHostKeyChecking option

Getting sick of deleting keys out of my known_hosts file, so I tried to set this up in my ~/.ssh/config:

host 192.168.*,10.*
StrictHostKeyChecking no

But it has no effect.  If a key is present in known_hosts but changed, it craps out with the "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" message.

Next I tried uncommenting "StrictHostKeyChecking no" to /etc/ssh/ssh_config - same result.

Finally, even using the CLI option "-o StrictHostKeyChecking=no" doesn't work and errors the same way.  And, If the key isn't present, it still gets auto-saved: "

>ssh -o StrictHostKeyChecking=no root@192.168.1.1
Warning: Permanently added '192.168.1.1' (RSA) to the list of known hosts.

Do any of these options work for anyone else?

I'm using the latest SSH: "OpenSSH_6.2p1, OpenSSL 1.0.1e 11 Feb 2013" and kernel: "Linux tc-slim 3.8.10-1-ARCH #1 SMP PREEMPT Sat Apr 27 12:36:59 CEST 2013 x86_64 GNU/Linux".

Last edited by testcore (2013-05-03 03:52:11)

Offline

#2 2013-05-03 03:54:46

testcore
Member
Registered: 2012-07-07
Posts: 8

Re: [SOLVED-ish] SSH not respecting StrictHostKeyChecking option

Found today that this issue is not arch-specific as I reproduced it on both a RHEL and a SLES box at work today.  Will be submitting a bug report to openssh.

Still, I'm curious to know if anyone else can (or not) verify that this occurs on their machine - please post results if you have a sec to test.  (Message me if you want a test case).

Offline

#3 2013-07-02 08:59:30

vipr
Member
Registered: 2013-07-02
Posts: 1

Re: [SOLVED-ish] SSH not respecting StrictHostKeyChecking option

I'm experiencing the same bug, have you found a solution yet?

Offline

Board footer

Powered by FluxBB