Bug 2145026
| Summary: | 'Include /etc/ssh/sshd_config.d/*.conf' in /etc/ssh/sshd_config subjected to accidential removals | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Robert Scheck <redhat-bugzilla> |
| Component: | openssh | Assignee: | Dmitry Belyavskiy <dbelyavs> |
| Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9.1 | CC: | asosedki, jjelen, ravpatil, robert.scheck |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-29 14:06:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Robert Scheck
2022-11-22 23:48:31 UTC
Cross-filed case #03368892 at the Red Hat customer portal. It doesn't look like a OpenSSH bug to me. Yes, accidental change of the config may cause problems, but I don't see how to prevent it. Yes, it isn't an OpenSSH upstream bug, it's IMHO an issue caused by packaging on Red Hat side as a downstream. Instead of leveraging the 'Include' directive, a more nice but especially robust upstream solution could have been created by implementing something like a hardcoded include directly in the OpenSSH ELF binaries (as already mentioned in the last paragraph of my initial description). Opting out of crypto-policies is a supported scenario, described in, say https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening Going for a hardcoded include would go against that, or at the very least, make the procedure more complicated than it should be. IMO, in general, making software hard to misconfigure is a rather futule goal. And when performed downstream-only, it becomes an extra source of confusion and frustration. A distribution is supposed to configure OpenSSH by leveraging the existing configuration facilities, not hardcoding secret downstream ones with unclear interplay with the upstream ones. |