Bug 2066882
Summary: | OpenSSH can still use 1k RSA keys despite DEFAULT crypto-policy settings claims 2k is minimum | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Jakub Jelen <jjelen> |
Component: | openssh | Assignee: | Dmitry Belyavskiy <dbelyavs> |
Status: | CLOSED ERRATA | QA Contact: | Ondrej Moriš <omoris> |
Severity: | medium | Docs Contact: | Jan Fiala <jafiala> |
Priority: | medium | ||
Version: | 9.0 | CC: | asosedki, dbelyavs, hkario, jafiala, jjelen, mhavrila, omoris, szidek, tscherf |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | Flags: | pm-rhel:
mirror+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
.New option in OpenSSH supports setting the minimum RSA key length
Accidentally using short RSA keys makes the system more vulnerable to attacks. With this update, you can set minimum RSA key lengths for OpenSSH servers and clients. To define the minimum RSA key length, use the new `RequiredRSASize` option in the `/etc/ssh/sshd_config` file for OpenSSH servers, and in the `/etc/ssh/ssh_config` file for OpenSSH clients.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-15 11:21:44 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: | |||
Bug Depends On: | |||
Bug Blocks: | 2102774 |
Description
Jakub Jelen
2022-03-22 16:49:10 UTC
Ideal solution would be to have a configuration option, but upstream will probably not like it. Maybe use as downstream patch? The problem is not the ssh-keygen generating the keys, but the ssh/sshd using and accepting these keys. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (openssh bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8375 |