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

Statements about the certificate_authorities extensions are inaccurate and inconsistent with previous arguments #14

Open
dadrian opened this issue Jul 20, 2024 · 0 comments

Comments

@dadrian
Copy link

dadrian commented Jul 20, 2024

In "Fingerprinting and Client Privacy", there are two statements comparing the risk of certificate_authorities to Trust Expressions, both of which are inaccurate or political speculation:

  1. Scalability:

    not viable for establishing a domestic root program because it does not scale

    A domestic root program can be a single or small number of CAs, so scaling is not a requirement.

  2. Mandates

    certificate_authorities has only been implemented for client certificates…no government can force a change to how TLS libraries handle certificate_authorities

    If the government cannot mandate changes to clients, then root programs will continue to have sovereignty over their root stores and all of this discussion is irrelevant.

These statements are also inconsistent with earlier arguments about mandates. If a government cannot mandate changes to clients, why does trust anchor negotiation somehow make it more likely that a government can mandate a change to clients? If server adoption via a negotiation mechanism is a key concern to the feasibility of mandating trust store contents, how come existing (albeit inefficient) negotiation mechanisms cannot be leveraged to enact the same mandate?

Overall, this section is full of technical inaccuracies and baseless political speculation. Continuing to have this flavor of discussion discourages productive participation by a broad set of IETF contributors.

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

No branches or pull requests

1 participant