[Bug 2627] Documentation update: semantic of ClientAliveCountMax 0 unclear

2023-11-27 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=2627 --- Comment #8 from Christopher Maynard --- (In reply to Damien Miller from comment #7) > If you were relying on an accidental, unreliable and undocumented > behaviour for security then you always destined to have a bad time. The behavior was

[Bug 3636] New: Public key authentication fails with incorrect message if authorized_keys is not UTF-8 encoded

2023-11-27 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=3636 Bug ID: 3636 Summary: Public key authentication fails with incorrect message if authorized_keys is not UTF-8 encoded Product: Portable OpenSSH Version: 9.5p1 Hardware:

[Bug 2627] Documentation update: semantic of ClientAliveCountMax 0 unclear

2023-11-27 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=2627 --- Comment #7 from Damien Miller --- If you were relying on an accidental, unreliable and undocumented behaviour for security then you always destined to have a bad time. ClientAliveCountMax=0 *never* worked as a reliable inactivity timeout -

[Bug 2627] Documentation update: semantic of ClientAliveCountMax 0 unclear

2023-11-27 Thread bugzilla-daemon
https://bugzilla.mindrot.org/show_bug.cgi?id=2627 Christopher Maynard changed: What|Removed |Added CC||christopher.mayn...@igt.com ---