https://bugzilla.mindrot.org/show_bug.cgi?id=2413
--- Comment #2 from Ben Creasy <[email protected]> --- I see what you mean, and it is true that various workarounds are suggested at http://superuser.com/questions/141344/dont-add-hostkey-to-known-hosts-for-ssh/141352#141352. In terms of what ssh is writing, I would image that ssh can figure out whether the final output is /dev/null (of course the last thing most people want is yet another optional switch). In my case I like being able to have a known_hosts file that has hosts that I expect to connect to more than once - it feels more organized. In my case, I'm sometimes starting up temporary DigitalOcean droplets for a little while to test something out and then destroying them. I'd rather not limit my logging or have to mess around with a config file when I do that. Is there a way to do this which doesn't require tweaking the config files but isn't a poor practice? -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
