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

Toreless - draft-5 section 4.2: does section 4.2 need to explain redirection? #79

Open
mcr opened this issue Dec 18, 2023 · 0 comments · May be fixed by #146
Open

Toreless - draft-5 section 4.2: does section 4.2 need to explain redirection? #79

mcr opened this issue Dec 18, 2023 · 0 comments · May be fixed by #146

Comments

@mcr
Copy link
Member

mcr commented Dec 18, 2023

511	   assumed services are accessed at that domain too.  As trust is
512	   already established via the Voucher, the pledge does a full TLS
513	   handshake against the local RA indicated by the voucher response.

515	   The returned voucher contains an attribute, "est-domain", defined in
516	   Section 5 below.  The pledge is directed to continue enrollment using
517	   the EST registrar found at that URI.  The pledge uses the pinned-
518	   domain-cert from the voucher to authenticate the EST registrar.

I am not sure these two paragraphs are needed given how the explanation after
the picture should cover it all in chronological order. But if you want to
keep this text, please reorder from benjaming button order to chronological.
@upros upros changed the title does section 4.2 need to explain redirection? Toreless - draft-5 section 4.2: does section 4.2 need to explain redirection? Jan 21, 2024
upros added a commit that referenced this issue May 4, 2024
@upros upros linked a pull request May 4, 2024 that will close this issue
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 a pull request may close this issue.

1 participant