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 checking expiration of X.509 certificates #6678

Merged
merged 1 commit into from
Mar 15, 2021

Conversation

illia-v
Copy link
Contributor

@illia-v illia-v commented Mar 14, 2021

Description

not_valid_after is a naïve datetime representing a moment in UTC. It should not be compared to a naïve datetime representing the current local date and time.

Also, the value is inclusive.

https://cryptography.io/en/3.4.6/x509/reference.html#cryptography.x509.Certificate.not_valid_after

`not_valid_after` is a naïve datetime representing a moment in UTC. It should not be compared to a naïve datetime representing the current local date and time.

Also, the value is inclusive.

https://cryptography.io/en/3.4.6/x509/reference.html#cryptography.x509.Certificate.not_valid_after
@codecov
Copy link

codecov bot commented Mar 14, 2021

Codecov Report

Merging #6678 (5966c86) into master (4d77ddd) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #6678   +/-   ##
=======================================
  Coverage   70.47%   70.47%           
=======================================
  Files         138      138           
  Lines       16494    16494           
  Branches     2073     2073           
=======================================
  Hits        11624    11624           
  Misses       4668     4668           
  Partials      202      202           
Flag Coverage Δ
unittests 70.47% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
celery/security/certificate.py 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4d77ddd...5966c86. Read the comment docs.

@auvipy auvipy added this to the 5.1.0 milestone Mar 14, 2021
@auvipy auvipy added this to In progress in Celery 5.1.0 via automation Mar 14, 2021
@lgtm-com
Copy link

lgtm-com bot commented Mar 14, 2021

This pull request introduces 1 alert and fixes 1 when merging 5966c86 into 4d77ddd - view on LGTM.com

new alerts:

  • 1 for Module is imported with 'import' and 'import from'

fixed alerts:

  • 1 for Unused import

Celery 5.1.0 automation moved this from In progress to Reviewer approved Mar 15, 2021
@thedrow thedrow merged commit 1f3c981 into celery:master Mar 15, 2021
Celery 5.1.0 automation moved this from Reviewer approved to Done Mar 15, 2021
jeyrce pushed a commit to jeyrce/celery that referenced this pull request Aug 25, 2021
`not_valid_after` is a naïve datetime representing a moment in UTC. It should not be compared to a naïve datetime representing the current local date and time.

Also, the value is inclusive.

https://cryptography.io/en/3.4.6/x509/reference.html#cryptography.x509.Certificate.not_valid_after
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Celery 5.1.0
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants