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

webtransport: define how to use CA-signed certificates #507

Open
marten-seemann opened this issue Jan 21, 2023 · 1 comment
Open

webtransport: define how to use CA-signed certificates #507

marten-seemann opened this issue Jan 21, 2023 · 1 comment

Comments

@marten-seemann
Copy link
Contributor

WebTransport currently only defines how to use self-signedf certificates, using serverCertificateHashes.
It should be possible to use CA-signed certificates once w3c/webtransport#411 is resolved.
@marten-seemann marten-seemann mentioned this issue Mar 29, 2023
Open
@MarcoPolo
Copy link
Contributor

I think it should be possible to include the server's domain name in the Noise extensions which would let the client check it is connected to the correct domain name, and thus assure the client the connection is secure if they dialed that domain name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
libp2p Specs
Status: Triage
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MarcoPolo @marten-seemann