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 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 #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 --- Comment #5 from Darren Tucker <dtucker at zip.com.au> --- (In reply to Christoph Anton Mitterer from comment #4) > Hi guys. > > With version: 6.7p1 > > > Regarding my initial report: > > It *still* happens, that SSH automatically adds a key, i.e.: > $ echo > ~/.ssh/known_hosts > $ ssh -o

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 --- 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 --- 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 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

Brian Candler wrote: > Chris Green wrote: > > ... redundant ones are because I have a mixed population of > > Raspberry Pis and such on my LAN and they get rebuilt fairly > > frequently and thus, each time, get a new entry in known_hosts. > ...many useful tips... > To disable host key checking altogether for certain domains and/or networks, > you can put this in

On 14/02/2024 11:42, Chris Green wrote: > Is there any way to remove old entries from the known_hosts file? With > the hashed 'names' one can't easily see which entries are which. I > have around 150 lines in my known hosts but in reality I only ssh to a > dozen or so systems. All the redundant ones are because I have a > mixed population of Raspberry Pis and such on

Hello & thanks for reading. I'm having a problem configuring known_hosts from scripts so an accept key yes/no prompt doesn't appear. I'm using this command to detect if the server is known and add it to known_hosts: if ! ssh-keygen -F ${IP_ADDR} -f ~/.ssh/known_hosts > /dev/null 2>&1; t hen ssh-keyscan -p ${PORT} ${IP_ADDR} >> ~/.ssh/known_hosts; fi This works

If I want to specify for LAN addresses that I don't want to deal with host keys, how do I do that? Understanding the risks, knowing almost everyone will say not to do this - it's a horrible idea, but deciding I want to do it anyway. Tired of having to remove entries from known_hosts with the multiple VM's I have that often change fingerprints, and am willing to live with the risks.

Hi! Is it somehow possible to disable the known_hosts checking for some hosts? The StrictHostKeyChecking affects only the asking about new computers, but doesn't affect the changed ones. I need it for the test computers, which are reinstalled twice/hour and I really don't like editing .ssh/known_hosts each time :-( Thanks Michal