> (The documentation is vague on this, and I'm too chicken to confirm my
> interpretation,
> but I take it "StrictHostKeyChecking no" will permit you to connect to a host
> whose
> key has changed.)
Okay, I confirmed this under controlled conditions now. You do get a
warning, with big old ugl
Maybe this could be rephrased: add an alternative "StrictHostKeyChecking
silent" and, ideally, make it the default. Like with
"StrictHostKeyChecking no", add hosts silently; but still be strict when
a key has changed, and refuse to connect.
(The documentation is vague on this, and I'm too chicken
On Thu, 27 Mar 2008 22:13:04 -, "Mathias Gug" <[EMAIL PROTECTED]>
said:
> On Thu, Mar 27, 2008 at 07:23:56PM -, era wrote:
> > + It's a usability problem that openssh-client behaves differently
> > the first time you connect to a host, particularly if you hop
> > between client machines
On Thu, Mar 27, 2008 at 07:23:56PM -, era wrote:
> - It's a usability problem that openss-client behaves differently the
> + Binary package hint: openssh-client
> +
> + It's a usability problem that openssh-client behaves differently the
> first time you connect to a host, particularly if y
** Description changed:
- It's a usability problem that openss-client behaves differently the
+ Binary package hint: openssh-client
+
+ It's a usability problem that openssh-client behaves differently the
first time you connect to a host, particularly if you hop between client
machines all th
