Remove use of RSA for cert_authority and use proper permission for root CA #2593
Conversation
This file contains hidden or 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
RSA 2048 is reprecated by NIST for 2050, so will happen for further keylengths by 2030
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Suggestion cannot be applied right now. Please check back later.
This PR removes the use of RSA algorithm for generating TLS Certificate. RSA is still used in many other places like while generating TLS Certificate for Root Domain. Might remove it from there too, but in a different PR as there the RSA algorithm is used like a spider web and might break "somethings". hence, giving it a thought before pushing.
Also, more prominent for not making the change for TLS Certificate is that cerbtot robot yet does not support ED25519 or any other stronger algorithms. Forum thread
And, along with it, previously the root_certiifcate_authority permission was (kind of) insecure, as it was letting the user, group and owner with
roaccess. Owner is fine, but group and user do not need to see root certificate.