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 Edge CA and module cert CSRs to use version 0 (v1) instead of non-existent version 2 (v3). #4904

Merged
merged 2 commits into from
Apr 27, 2021

Conversation

arsing
Copy link
Member

@arsing arsing commented Apr 27, 2021

v3 is correct for certificates (X509) but not for CSRs (X509Req).

… 2 (v3).

v3 is correct for certificates (`X509`) but not for CSRs (`X509Req`).
@massand
Copy link
Contributor

massand commented Apr 27, 2021

Could you double-check edgeHub is cool with this change by running E2E tests manually? Thanks.

@arsing
Copy link
Member Author

arsing commented Apr 27, 2021

Why? Edge Hub is not affected by this change.

@arsing arsing changed the title Fix Edge CA CSR to use version 0 (v1) instead of non-existent version 2 (v3). Fix Edge CA and module cert CSRs to use version 0 (v1) instead of non-existent version 2 (v3). Apr 27, 2021
@arsing
Copy link
Member Author

arsing commented Apr 27, 2021

Okay, I see the problem. certd is copying the CSR version into the cert version. That's bogus. I'll fix that first.

@kodiakhq kodiakhq bot merged commit a88f820 into Azure:master Apr 27, 2021
@arsing arsing deleted the edge-ca-csr-version branch April 27, 2021 19:17
ggjjj pushed a commit to ggjjj/iotedge that referenced this pull request Jul 22, 2021
…-existent version 2 (v3). (Azure#4904)

v3 is correct for certificates (`X509`) but not for CSRs (`X509Req`).
damonbarry pushed a commit to damonbarry/iotedge that referenced this pull request Apr 15, 2022
…-existent version 2 (v3). (Azure#4904)

v3 is correct for certificates (`X509`) but not for CSRs (`X509Req`).
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.

3 participants