[Bug 2400] StrictHostKeyChecking=no behaviour on HOST_CHANGED is excessively insecure

[bugzilla-daemon at bugzilla.mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=2400

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #2682|0                           |1
        is obsolete|                            |
             Status|NEW                         |ASSIGNED
           Assignee|unassigned-bugs at mindrot.org |djm at mindrot.org

--- Comment #6 from Damien Miller <djm at mindrot.org> ---
Created attachment 2794
  --> https://bugzilla.mindrot.org/attachment.cgi?id=2794&action=edit
add StrictHpstkeyChecking=accept-new|off

This adds a couple more granular options to StrictHostkeyChecking:
"accept-new" (better name wanted) and "off".

StrictHostkeyChecking=off is the current behaviour of "no".

StrictHostkeyChecking=accept-new will accept new hostkeys without
prompting but will disconnect for changed hostkeys.

If this goes in then we can make StrictHostkeyChecking=no a synonym for
accept-new at some future time (and with forewarning).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.