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.

Sign up for GitHub

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

Jump to bottom

Update scoping discussion to cover latest from ACME #163

Open
enygren opened this issue Nov 26, 2024 · 1 comment
Open

Update scoping discussion to cover latest from ACME #163

enygren opened this issue Nov 26, 2024 · 1 comment
Labels
WGLC to resolve before WGLC

Comments

@enygren
Copy link
Contributor

enygren commented Nov 26, 2024

The latest ACME draft dropped the scoping fix (ie, dropped the DNS-02 in-favor of DNS-ACCOUNT-01). See https://datatracker.ietf.org/doc/html/draft-ietf-acme-dns-account-label

We'll need to update our text to clarify that this is still a vulnerability in ACME DNS-01 and the proposed DNS-ACCOUNT-01.
@enygren enygren added the WGLC to resolve before WGLC label Nov 26, 2024
@moonshiner
Copy link
Contributor

So only partially looking at this but this CAB Forum ballot failed
https://cabforum.org/2024/11/29/ballot-sc-82-clarify-ca-assisted-dns-validation-under-3.2.2.4.7/

I think this relates. But I just spent two days explaining to some corporate security team why their Entrust EV internal certs will not validate anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
WGLC to resolve before WGLC
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@moonshiner @enygren