| Summary: | multiple Subsystem options in sshd_config prevent sshd from starting | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Jakub Jelen <jjelen> | ||||
| Component: | sshd | Assignee: | Damien Miller <djm> | ||||
| Status: | NEW --- | ||||||
| Severity: | enhancement | CC: | boum, bugs, djm, dtucker, kerminaawad, micha, szidek | ||||
| Priority: | P5 | ||||||
| Version: | 8.4p1 | ||||||
| Hardware: | Other | ||||||
| OS: | Linux | ||||||
| Attachments: |
|
||||||
|
Description
Jakub Jelen
2020-11-30 19:16:11 AEDT
I just ran into this issue yesterday. I prefer not to modify the main config so that future updates cannot overwrite my changes, and so that the main config is always up to date. So I used the include feature to overwrite "Subsystem sftp", however, sshd would not start. If I had not found this bug report I would probably not have found the issue. I faced the same issue, hence would also like to be able to override an existing Subsystem setting in /etc/ssh/sshd_config with one in /etc/ssh/sshd_config.d/. This has also been reported downstream at the Debian bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998834 I ran into this issue has well and that was kinda frustrating because it seems this is the only setting that behave like this! Created attachment 3591 [details]
Make repeated Subsystem directives non-fatal
|