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

Use timezone aware functionality when using cryptography >= 42.0.0 #727

Merged
merged 4 commits into from
Apr 18, 2024

Conversation

felixfontein
Copy link
Contributor

SUMMARY

Fixes #726.

ISSUE TYPE
  • Bugfix Pull Request
  • Feature Pull Request
COMPONENT NAME

various

@felixfontein
Copy link
Contributor Author

I'm not sure what to do with InvalidityDate.invalidity_date, which doesn't have a _utc variant. I've asked on IRC in #pyca.

@felixfontein
Copy link
Contributor Author

I'm not sure what to do with InvalidityDate.invalidity_date, which doesn't have a _utc variant. I've asked on IRC in #pyca.

That's an oversight according to the maintainers.

Ref: pyca/cryptography#10818

@felixfontein felixfontein marked this pull request as ready for review April 15, 2024 15:00
@felixfontein felixfontein changed the title [WIP] Use timezone aware functionality when using cryptography >= 42.0.0 Use timezone aware functionality when using cryptography >= 42.0.0 Apr 15, 2024
@felixfontein felixfontein merged commit ae548de into ansible-collections:main Apr 18, 2024
142 checks passed
@felixfontein felixfontein deleted the utc branch April 18, 2024 05:49
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.

CryptographyDeprecationWarning on module x509_certificate_info
1 participant