search for: 2e01

...; 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 StrictHostKeyChecking=no someHost > Warning: Permanently added the ECDSA host key for IP address > '2e01:2a6:b9:3823::2:1' to the list of known hosts. > (changed the IP/name for privacy reasons). Did you have an existing, valid hostkey with a different algorithm for that host? I suspect it's due to the hostkeys-00 at openssh.com method that advertises the other host key types after succes...

...wrong tree.) (In reply to Christoph Anton Mitterer from comment #4) [..] > It *still* happens, that SSH automatically adds a key, i.e.: > $ echo > ~/.ssh/known_hosts > $ ssh -o StrictHostKeyChecking=no someHost > Warning: Permanently added the ECDSA host key for IP address > '2e01:2a6:b9:3823::2:1' to the list of known hosts. > (changed the IP/name for privacy reasons). Err, that's exactly what StrictHostKeyChecking=no is supposed to do: "If this flag is set to "no", ssh will automatically add new host keys to the user known hosts files." &g...

...<calestyo at scientia.net> --- 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 StrictHostKeyChecking=no someHost Warning: Permanently added the ECDSA host key for IP address '2e01:2a6:b9:3823::2:1' to the list of known hosts. (changed the IP/name for privacy reasons). - the name truncation no longer happens, but only since the message is now a different one... so isn't that issue anyway gone? Anyway,... you asked for some information about platform, etc. I cannot g...

...on 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 > > '2e01:2a6:b9:3823::2:1' to the list of known hosts. > > (changed the IP/name for privacy reasons). First, I just tried it again with 6.7p1. > Did you have an existing, valid hostkey with a different algorithm > for that host? There was no key for that host (neither with another algo)...