Displaying 3 results from an estimated 3 matches for "systemknownhostsfile".
2015 May 28
0
[Bug 1993] ssh tries to add keys to ~/.ssh/known_hosts though StrictHostKeyChecking yes is set
...h.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 to avoid it use:
UserKnownHostsFile none
SystemKnownHostsFile /etc/ssh/known_hosts ~/.ssh/known_hosts
to get ssh to treat the known hosts file as a system (read-only) rather
than a user (r/w) file.
--
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.
2015 Jun 01
0
[Bug 1993] ssh tries to add keys to ~/.ssh/known_hosts though StrictHostKeyChecking yes is set
...f I remember correctly, DKG has posted a patch some time ago on the
mailing list, requesting to disable CheckHostIP anyway.
I agreed with him, it seems to provide no additional security but
rather just leaks information.
> but if you want to avoid it use:
>
> UserKnownHostsFile none
> SystemKnownHostsFile /etc/ssh/known_hosts ~/.ssh/known_hosts
>
> to get ssh to treat the known hosts file as a system (read-only)
> rather than a user (r/w) file.
That's however merely a bad workaround, as this also means that the
user cannot use a personal hosts file.
I, however, just want to prevent au...
2020 Sep 16
2
ssh-ed25519 and ecdsa-sha2-nistp256 host keys
Here you go:
OpenSSH_7.9p1, OpenSSL 1.1.1d 10 Sep 2019
debug1: Reading configuration data /home/ryantm/.ssh/config
debug1: /home/ryantm/.ssh/config line 4: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 13: Applying options for *
debug2: resolving "{REDACTED}" port 22
debug2: ssh_connect_direct
debug1: Connecting to