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

The usage of HTTPS for publishing CA certificates be prohibited in this standard to avoid the issues specified in Section 8 of RFC 5280 #243

Closed
currydm opened this issue Feb 1, 2021 · 2 comments
Labels

Comments

@currydm
Copy link
Contributor

currydm commented Feb 1, 2021

All Fields Are Required

Organization Name (N/A, if individual): DoD

Organization Type (see below for codes): 1 - Federal

Reference (Include section/paragraph or pdf line number): 5.5 Line 2121

Comment (Include rationale for comment): Does the specification of HTTP for publishing CA certificates preclude the usage of HTTPS? Considering RFC 5280, it probably should.

Suggested Change: Suggest the following text be added, "the usage of HTTPS for publishing CA certificates be prohibited in this standard to avoid the issues specified in Section 8 of RFC 5280, one example of which is "relying parties ... MUST be prepared for the possibility that this will result in unbounded recursion."


Organization Type: 1 = Federal, 2 = Industry, 3 = Academia, 4 = Self, 5 = Other

@currydm
Copy link
Contributor Author

currydm commented Mar 12, 2021

Propose team discussion. See also #244

@regenscheid
Copy link
Collaborator

Decline- FIPS 201 specifies that you must use HTTP, and is now silent other protocols. As the commenter noted, RFC 5280 has additional guidance on this topic.

@regenscheid regenscheid added the Declined Adjudication label Apr 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants