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 #5973 on windows by disregarding errors when querying legacy cert path #6013

Merged
merged 1 commit into from
Jan 9, 2019

Conversation

ncabatoff
Copy link
Collaborator

@ncabatoff ncabatoff commented Jan 8, 2019

@jefferai suggested either disregarding the error here or skipping the legacy query when on windows; I chose to do the former as it seemed a smaller change.

@ncabatoff ncabatoff requested a review from vishalnayak January 8, 2019 23:53
return nil, errutil.InternalError{Err: fmt.Sprintf("error fetching certificate %s: %s", serial, err)}
}
// Retrieve the old-style path. We disregard errors here because they always manifest on windows, and thus the initial
// check for a revoked cert fails would return an error when the cert isn't revoked, preventing the happy path from working.
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you wrap your comments at a 80 width?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done.

@briankassouf briankassouf added this to the 1.0.2 milestone Jan 9, 2019
@ncabatoff ncabatoff force-pushed the issue5973-ignore-cert-legacypath-errors branch from 3fec1ef to 0681df1 Compare January 9, 2019 00:53
@briankassouf briankassouf merged commit 04fa50c into master Jan 9, 2019
@briankassouf briankassouf deleted the issue5973-ignore-cert-legacypath-errors branch January 9, 2019 02:08
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.

2 participants