[Bug 2531] MaxSessions config parameter name is highly ambigious

bugzilla-daemon at bugzilla.mindrot.org bugzilla-daemon at bugzilla.mindrot.org
Mon Jan 25 23:39:14 AEDT 2016


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

--- Comment #3 from DarkTrick <DarkTrick at outlook.de> ---
ow, I didn't know, that it was added 8 years ago. Never checked the
date. So renaming of cause is not an option.

I would suggest to make it clear, that this is about multiplexing of
*one* connection and not about the number of connections.

My suggestion would be to also add the following part of the changelog:
------------------------
This is useful for disabling login/shell/subsystem access while leaving
port-forwarding working (MaxSessions 0), disabling connection
multiplexing (MaxSessions 1) or simply increasing the number of allows
multiplexed sessions.
------------------------

TBH, I don't know how to make a short sentence, that would sound nice
and express, the difference. But (at least I think) that part of the
changelog makes things more clear. In case someone thought about the
maximum number of connections, he will then understand, that this is
something different to what he's searching.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.


More information about the openssh-bugs mailing list