-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewrite x509 modules using cryptography
(v2 with breaking changes)
#63099
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.
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. |
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 will indeed get into 3006.0 :) Thanks for your quick follow up on this PR to get it over the line |
What does this PR do?
x509
modules usingcryptography
instead ofM2Crypto
subject
does not override signing policiesOpen questions for the reviewer
Do I mark issues related tov1
as 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 breakingv2
counts 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
prereq
Merge requirements satisfied?
Commits signed with GPG?
Yes