Skip to content
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

Fix crash in x509_certificate #241

Merged
merged 2 commits into from
Jun 2, 2021

Conversation

felixfontein
Copy link
Contributor

SUMMARY

Fixes #240.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

x509_certificate

@felixfontein felixfontein mentioned this pull request Jun 2, 2021
11 tasks
Copy link
Collaborator

@Ajpantuso Ajpantuso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM as far as fixing the issue is concerned.
I checked the other backends and I didn't see any other references to self.path, but if it makes sense to have that attribute available it could just be initialized from the CertificateBackend base class instead of removing the references here.

@felixfontein
Copy link
Contributor Author

I thought about that as well, but it will be kind of undefined for the x509_certificate_pipe module. That's why I decided to simply remove it; the other error messages also don't mention the certificate's filename.

@felixfontein felixfontein merged commit bfb8e5d into ansible-collections:main Jun 2, 2021
@felixfontein felixfontein deleted the fix-bug branch June 2, 2021 14:45
@felixfontein
Copy link
Contributor Author

@Ajpantuso @twouters thanks for reviewing and testing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Exception when certificate does not belong to the specified private key
2 participants