Dear colleagues, There is a need to increase RSA key requirements to make the installations more secure. Just updating the default compiled-in value isn't an option because it may significantly break legacy systems compatibility. This PR [1] introduces a new configuration option MinRSABits to be managed for security's sake. If this approach is OK for upstream, please let me know and I will improve this PR according to the feedback. [1] https://github.com/openssh/openssh-portable/pull/325 -- Dmitry Belyavskiy
On Fri, Jun 10, 2022 at 10:50 AM Dmitry Belyavskiy <dbelyavs at redhat.com> wrote:> > Dear colleagues, > > There is a need to increase RSA key requirements to make the installations > more secure. Just updating the default compiled-in value isn't an option > because it may significantly break legacy systems compatibility. This PR > [1] introduces a new configuration option MinRSABits to be managed for > security's sake.Document it, in plain language, and make it clear how to revert the change for specific targets. I went *nuts* recently because the CIS published release of RHEL 8 does not permit the older protocol specifically labeled "ssh-rsa" for public authentication, and it breaks SSH key based access to the Azure DevOps git server.> If this approach is OK for upstream, please let me know and I will improve > this PR according to the feedback. > > [1] https://github.com/openssh/openssh-portable/pull/325 > > -- > Dmitry Belyavskiy > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
On 10.06.22 16:50, Dmitry Belyavskiy wrote:> There is a need to increase RSA key requirements to make the installations > more secure. Just updating the default compiled-in value isn't an option > because it may significantly break legacy systems compatibility. This PR > [1] introduces a new configuration option MinRSABits to be managed for > security's sake. > > If this approach is OK for upstream, please let me know and I will improve > this PR according to the feedback.I realize that with the *current* selection of algorithms available in OpenSSH, fine-grained control of minimum key size almost(!) is an RSA-only topic, but nonetheless I wonder whether newly-defined config syntax thereto should be aimed at extensibility to other cryptalgorithms ... Regards, -- Jochen Bern Systemingenieur Binect GmbH -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3449 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20220613/2c02cae1/attachment.p7s>