bugzilla-daemon at mindrot.org
2002-Mar-30 19:02 UTC
[Bug 108] Enable continuation with '\' (backslash) in /etc/ssh/sshd_config (feature request)
http://bugzilla.mindrot.org/show_bug.cgi?id=108 ------- Additional Comments From stevesk at pobox.com 2002-03-31 05:02 ------- i don't know if this should be wontfix or future. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Apr-17 02:18 UTC
[Bug 108] Enable continuation with '\' (backslash) in /etc/ssh/sshd_config (feature request)
http://bugzilla.mindrot.org/show_bug.cgi?id=108 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From djm at mindrot.org 2002-04-17 12:18 ------- WONTFIX - you can avoid long lines by using multiple AllowUsers directives as each gets added to the list. E.g. your example could be written: AllowUsers user1 at host1.somewhere.com user1 at host2.somewhere.com AllowUsers user2 at host1.somewhere.com user2 at host3.somewhere.com ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Apr-17 03:38 UTC
[Bug 108] Enable continuation with '\' (backslash) in /etc/ssh/sshd_config (feature request)
http://bugzilla.mindrot.org/show_bug.cgi?id=108 ------- Additional Comments From dan at doxpara.com 2002-04-17 13:38 ------- Hmmm, I've created a few ProxyCommand pipes that wouldn't fit into 80 characters, and it wouldn't really make sense to have multiple ProxyCommand options. (are they piped together? &&'d? should I need to create a file and sh -c it?) \ as a line extension mechanism has a decent amount of precedent -- I think it's been around since bourne shell -- and might make some configuration files easier to read. The main cost I see is that, as far as I know, there's not a mode to make grep aware of the backslash. That would mean $ grep AllowUsers /etc/sshd/sshd_config would return only the first line of users allowed. So: Is it better to have something more usable and more standard for users to enter configurations into, or is it better to be compatible with per-line parsing systems? I'm not really sure. We've already sacrificed line independence -- a group of options can be encapsulated by a pattern match; the above grep would match all patterns equally. Damien -- what's your reasoning for disliking \ notation, out of curiosity? --Dan ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Apr-17 03:47 UTC
[Bug 108] Enable continuation with '\' (backslash) in /etc/ssh/sshd_config (feature request)
http://bugzilla.mindrot.org/show_bug.cgi?id=108 ------- Additional Comments From djm at mindrot.org 2002-04-17 13:47 ------- It adds complexity where it is not required. OpenSSH has a simple line-at-a-time config parser, it doesn't need to be more complicated. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
Reasonably Related Threads
- [Bug 108] New: Enable continuation with '\' (backslash) in /etc/ssh/sshd_config (feature request)
- why does rsync translate user@host into '$RSYNC_RSH -l user host'?
- Question regarding patch for ProxyCommand setting
- [Bug 3751] New: ssh fails to parse ProxyCommand option with a string that ends in a backslash
- Help with ssh -A, screen, ssh -a, detach, logout