similar to: [Bug 1993] ssh tries to add keys to ~/.ssh/known_hosts though StrictHostKeyChecking yes is set

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 --- Comment #9 from Christoph Anton Mitterer <calestyo at scientia.net> --- (replies to all your comments in one) Hey. Sorry for the delay. (In reply to Darren Tucker from comment #5) > > $ ssh -o StrictHostKeyChecking=no someHost > > Warning: Permanently added the ECDSA host key for IP address > >

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Christoph Anton Mitterer <calestyo at scientia.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|6.2p1 |6.7p1 --- Comment #4 from Christoph Anton Mitterer <calestyo at scientia.net> --- Hi guys.

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 --- Comment #7 from Darren Tucker <dtucker at zip.com.au> --- (In reply to Darren Tucker from comment #6) > Created attachment 2635 [details] > Remove length limits on know host file name in log messages A slightly different version of the patch has been committed and will be in the 6.9 release. (When I first looked at this I assumed

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 alex at testcore.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alex at testcore.net Version|5.9p1 |6.2p1 --- Comment #1 from alex at testcore.net --- Also

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 --- Comment #10 from Christoph Anton Mitterer <calestyo at scientia.net> --- Created attachment 2638 --> https://bugzilla.mindrot.org/attachment.cgi?id=2638&action=edit ssh -vvv output what happens when a key is auto added for the IP address of an already trusted host -- You are receiving this mail because: You are watching

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Bug #: 1993 Summary: ssh tries to add keys to ~/.ssh/known_hosts though StrictHostKeyChecking yes is set Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All OS/Version: All Status: NEW Severity: normal

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 --- Comment #8 from Damien Miller <djm at mindrot.org> --- The hostkeys-00 at openssh.com extension has to be explicitly enabled via UpdateHostKeys=yes|ask The OP's question is the CheckHostIP option updating addresses for hostnames it already knows about. We could probably clarify the documentation for this behaviour, but if you want

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|dtucker at zip.com.au |djm at mindrot.org Status|NEW |ASSIGNED Attachment #2641|

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Roland Friedwagner <r.friedwagner at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.friedwagner at gmail.com -- You are receiving this mail because: You are watching someone on the CC

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Darren Tucker <dtucker at zip.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |djm at mindrot.org Attachment #2635| |ok?(djm at mindrot.org) Flags|

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Darren Tucker <dtucker at zip.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #2635|ok?(djm at mindrot.org) | Flags| | Attachment #2635|0 |1

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Darren Tucker <dtucker at zip.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned-bugs at mindrot.org |dtucker at zip.com.au -- You are receiving this mail because: You are watching the assignee of the bug. You

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Darren Tucker <dtucker at zip.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #2641|ok?(dtucker at zip.com.au) |ok+ Flags| | -- You are receiving this mail because: You are

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #12 from Damien Miller <djm at

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #13 from Damien Miller <djm at mindrot.org> --- Set all RESOLVED bugs to CLOSED with

https://bugzilla.mindrot.org/show_bug.cgi?id=3176 Bug ID: 3176 Summary: can't figure out how to test StrictHostKeyChecking accept-new Product: Portable OpenSSH Version: 8.3p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh

ssh -oStrictHostKeyChecking=no scrub @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just

Hello, the ssh_config man page for StrictHostKeyChecking contains a misleading sentence. The description of the option ends with "The host keys of known hosts will be verified automatically in all cases.". This sounds to me like no matter the value of StrictHostKeyChecking the host keys are verified; "verified" meaning "don't connect if they don't match".

http://bugzilla.mindrot.org/show_bug.cgi?id=1209 Summary: StrictHostKeyChecking really needs a 4th option Product: Portable OpenSSH Version: 4.3p2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy:

Long ago, when I wrote the ssh config file on my desktop box, ssh (which might have been the non-openssh one) took 3 possible values for the StrictHostKeyChecking option - yes, no & ask. Today, when I attempted to connect to a new machine, with no DNS entries (so using IP address) from my desktop box, ssh (now 2.3.0p1) SEGVed. Looks like there is some subtle interaction between having an