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
openssl_csr: idempotency doesn't work correctly for keyUsage #50361
Merged
amenonsen
merged 3 commits into
ansible:devel
from
felixfontein:openssl_csr-idempotency-tests
Jan 3, 2019
Merged
openssl_csr: idempotency doesn't work correctly for keyUsage #50361
amenonsen
merged 3 commits into
ansible:devel
from
felixfontein:openssl_csr-idempotency-tests
Jan 3, 2019
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
ansibot
added
affects_2.8
This issue/PR affects Ansible v2.8
bug
This issue/PR relates to a bug.
community_review
In order to be merged, this PR must follow the community review workflow.
module
This issue/PR relates to a module.
needs_triage
Needs a first human triage before being processed.
support:community
This issue/PR relates to code supported by the Ansible community.
labels
Dec 28, 2018
thomwiggers
approved these changes
Jan 2, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ansibot
added
shipit
This PR is ready to be merged by Core
and removed
community_review
In order to be merged, this PR must follow the community review workflow.
labels
Jan 2, 2019
Great find! |
@thomwiggers @MarkusTeufelberger thanks for your reviews! |
abadger
pushed a commit
that referenced
this pull request
Jan 7, 2019
* Fix key usage idempotency bug. * Extend tests. * Add changelog. (cherry picked from commit a5bf71a)
kbreit
pushed a commit
to kbreit/ansible
that referenced
this pull request
Jan 11, 2019
…#50361) * Fix key usage idempotency bug. * Extend tests. * Add changelog.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
affects_2.8
This issue/PR affects Ansible v2.8
bug
This issue/PR relates to a bug.
crypto
Crypto community (ACME, openssl, letsencrypt)
module
This issue/PR relates to a module.
shipit
This PR is ready to be merged by Core
support:community
This issue/PR relates to code supported by the Ansible community.
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.
SUMMARY
The idempotency check for keyUsage can only distinguish between no keyUsage specified, and something specified as keyUsage. The problem is that the given values (extension and keyUsage module option) are converted to NIDs via
OpenSSL._util.lib.OBJ_txt2nid()
, which returns 0 for all valid keyUsage values. So the resulting integer sets are either empty, or consist of a single entry 0.ISSUE TYPE
COMPONENT NAME
openssl_csr