Bug 2138540
| Summary: | howto create a specific crypto-policy for SSH | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Frank Ansari <mail> |
| Component: | crypto-policies | Assignee: | Red Hat Crypto Team <crypto-team> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 37 | CC: | asosedki, crypto-team, luk.claes, rrelyea, tm |
| Target Milestone: | --- | Flags: | fedora-admin-xmlrpc:
mirror+
|
| 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: | 2023-03-28 13:16:20 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
Frank Ansari
2022-10-29 14:18:26 UTC
> According to ssh-audit I should not set hmac-sha2-512 but only hmac-sha2-512-etm I believe that is possible with mac@SSH = HMAC-SHA2-512 ssh_etm = 0 > KexAlgorithms curve25519-sha256,curve25519-sha256 These require enabling ECDHE key_exchange, X25519 group and SHA2-256 hash. Hope that helps. > According to ssh-audit I should not set hmac-sha2-512 but only hmac-sha2-512-etm Oh, wait, you want just the etm one. I don't think that's possible with crypto-policies, so you might consider opting out of it if you want such to observe such a custom and rigid policy: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening#excluding-an-application-from-following-the-system-wide-crypto-policies_using-the-system-wide-cryptographic-policies *** This bug has been marked as a duplicate of bug 2164847 *** |