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 Sharding logic with using notbefore of a certificate. #647

Merged
merged 1 commit into from
Feb 6, 2020

Conversation

eccopark
Copy link
Contributor

@eccopark eccopark commented Feb 6, 2020

According to GoogleChrome/CertificateTransparency#6, a NotAfter
validity field of a X509 Certificate should be used.

The policy is as follows.
For a certificate to be accepted by the Log that has a time range
specified.
The certificate’s ‘Not After’ validity field value must:
Be at or after ‘Start’ and Be before ‘End’
fixes #647

Checklist

According to GoogleChrome/CertificateTransparency#6, a NotAfter
validity field of a X509 Certificate should be used.

The policy is as follows.
For a certificate to be accepted by the Log that has a time range
specified.
The certificate’s ‘Not After’ validity field value must:
Be at or after ‘Start’ and Be before ‘End’
@codecov
Copy link

codecov bot commented Feb 6, 2020

Codecov Report

Merging #647 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #647      +/-   ##
==========================================
- Coverage   71.78%   71.76%   -0.03%     
==========================================
  Files          90       90              
  Lines        9862     9862              
==========================================
- Hits         7079     7077       -2     
- Misses       2286     2288       +2     
  Partials      497      497
Impacted Files Coverage Δ
loglist2/logfilter.go 100% <100%> (ø) ⬆️
scanner/scanner.go 55.41% <0%> (-1.28%) ⬇️

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 203e829...fe75b78. Read the comment docs.

@Mercurrent Mercurrent merged commit 1be4951 into google:master Feb 6, 2020
@AlCutter AlCutter added the bug label Feb 7, 2020
zorawar87 pushed a commit to n-ct/certificate-transparency-go that referenced this pull request Feb 15, 2020
According to GoogleChrome/CertificateTransparency#6, a NotAfter
validity field of a X509 Certificate should be used.

The policy is as follows.
For a certificate to be accepted by the Log that has a time range
specified.
The certificate’s ‘Not After’ validity field value must:
Be at or after ‘Start’ and Be before ‘End’
zorawar87 pushed a commit to n-ct/certificate-transparency-go that referenced this pull request Feb 26, 2020
According to GoogleChrome/CertificateTransparency#6, a NotAfter
validity field of a X509 Certificate should be used.

The policy is as follows.
For a certificate to be accepted by the Log that has a time range
specified.
The certificate’s ‘Not After’ validity field value must:
Be at or after ‘Start’ and Be before ‘End’
zorawar87 pushed a commit to n-ct/certificate-transparency-go that referenced this pull request Mar 1, 2020
According to GoogleChrome/CertificateTransparency#6, a NotAfter
validity field of a X509 Certificate should be used.

The policy is as follows.
For a certificate to be accepted by the Log that has a time range
specified.
The certificate’s ‘Not After’ validity field value must:
Be at or after ‘Start’ and Be before ‘End’
@eccopark eccopark deleted the ct-proxy-branch branch April 28, 2020 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants