Added option RSAMinimumModulusSize <int> to lower the (now) hard limit #188
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SSH_RSA_MINIMUM_MODULUS_SIZE when necessary. Although it is usually possible and extremely advisable to generate new longer server keys, there are older devices where this is not possible. It is, however, practical still use SSH with them even if it is not as secure as it should be. It is still safer to use SSH with 800 bit keys that telnet without any encryption.
mirabilos
reviewed
Jul 17, 2020
| @@ -1486,6 +1486,12 @@ an OpenSSH Key Revocation List (KRL) as generated by | |||
| .Xr ssh-keygen 1 . | |||
| For more information on KRLs, see the KEY REVOCATION LISTS section in | |||
| .Xr ssh-keygen 1 . | |||
| .It Cm RSAMinimumModulusSize | |||
| Specifies the minimum accepted RSA modulus size in different | |||
| contexts. This is only be used with older SSH servers when it is | |||
There was a problem hiding this comment.
Line break after a full stop, so the spacing (american or proper) is applied automatically. See: https://man.openbsd.org/roff.7#Sentence_Spacing
mirabilos
reviewed
Jul 17, 2020
| contexts. This is only be used with older SSH servers when it is | ||
| impossible to have or generate longer keys for them. This should not | ||
| be used in any other purposes except perhaps testing. There is still | ||
| hard limit, 512. To use shorter RSA keys than that, OpenSSH must be recompiled. |
|
Thank you, I agree.
How we could get the patch merged to the repository? As I have stated, there is
a need for this. And I tried to implement it in such a way that it would be
used only when needed.
/alo
mirabilos wrote:
…
***@***.**** commented on this pull request.
--------------------------------------------------------------------------------
In ssh_config.5
<#188 (comment)>:
> @@ -1486,6 +1486,12 @@ an OpenSSH Key Revocation List (KRL) as generated by
.Xr ssh-keygen 1 .
For more information on KRLs, see the KEY REVOCATION LISTS section in
.Xr ssh-keygen 1 .
+.It Cm RSAMinimumModulusSize
+Specifies the minimum accepted RSA modulus size in different
+contexts. This is only be used with older SSH servers when it is
+impossible to have or generate longer keys for them. This should not
+be used in any other purposes except perhaps testing. There is still
+hard limit, 512. To use shorter RSA keys than that, OpenSSH must be recompiled.
|s/hard/a &/|
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#188 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA73A6VX6S7T3SVIHWKYMFDR4BSB5ANCNFSM4NOJVYOA>.
|
|
sinihappo dixit:
How we could get the patch merged to the repository? As I have stated, there is
a need for this. And I tried to implement it in such a way that it would be
used only when needed.
Sorry, not an OpenSSH developer :/
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Added option RSAMinimumModulusSize to lower the (now) hard limit
SSH_RSA_MINIMUM_MODULUS_SIZE when necessary. Although it is usually
possible and extremely advisable to generate new longer server keys,
there are older devices where this is not possible. It is, however,
practical still use SSH with them even if it is not as secure as it
should be. It is still safer to use SSH with 800 bit keys that telnet
without any encryption.
Background:
I have struggled with older network gear, where either it is not possible because of the lack of new FW or lack of permit to upgrade. If you think that having this option needs more safeguards, please give ideas on what kind of extra checks or options or anything.