Rewrite x509 modules using cryptography (v2 with breaking changes)#63099
Merged
Ch3LL merged 33 commits intosaltstack:masterfrom Dec 22, 2022
Merged
Rewrite x509 modules using cryptography (v2 with breaking changes)#63099Ch3LL merged 33 commits intosaltstack:masterfrom
cryptography (v2 with breaking changes)#63099Ch3LL merged 33 commits intosaltstack:masterfrom
Conversation
The necessary fix for linting salt/states/x509_v2.py is found in v2.13.6. 2.14 seems to be incompatible with saltpylint.
since they make signing policies less reliable.
Collaborator
|
I like this. however it needs a bunch of changelogs. to reflect the changes this is bringing in. also might need to start working through decommissioning the old x509 in favor of this. not just the flag change but calling out that people should start moving over in the logs with a decommission version. |
Contributor
Author
|
From what you wrote, I deduce that I should treat this as the x509 module and mark the issues as fixed as well as write feature requests for the big features. Will update this PR soonish with changelog and deprecation. |
This was referenced Dec 7, 2022
Ch3LL
previously approved these changes
Dec 16, 2022
whytewolf
previously approved these changes
Dec 16, 2022
s0undt3ch
suggested changes
Dec 20, 2022
s0undt3ch
approved these changes
Dec 21, 2022
whytewolf
approved these changes
Dec 21, 2022
Contributor
|
This will indeed get into 3006.0 :) Thanks for your quick follow up on this PR to get it over the line |
3 tasks
6 tasks
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
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.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
x509modules usingcryptographyinstead ofM2Cryptosubjectdoes not override signing policiesOpen questions for the reviewer
Do I mark issues related tov1as fixed and include those in the changelog? How do I submit feature requests for what is essentially a new module?Would it make more sense to not XOR v1 and v2, but simply deprecate v1? That would help justify the list of breaking changes (see the execution module docstring).cryptography[and increase the required version]? As far as I can tell, it is always part of Salt's indirect requirements (throughpyopenssl).What issues does this PR fix or reference?
Not sure if a breakingv2counts as a fix, so not marking some of those as fixed for the time.References:
Fixes: #59169
Fixes: #52167
Fixes: #58165
Fixes: #59315
Fixes: #63103
Fixes: #57535 (tested manually, works)
Fixes: #63248
Fixes: #63249
#63066 (would contribute to eventual fix)
#63085 (would contribute to eventual fix)
Previous Behavior
New Behavior
prereqMerge requirements satisfied?
Commits signed with GPG?
Yes