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

Spoofed DNS records aren't an issue #46

Open

ekr opened this issue Nov 21, 2021 · 0 comments

Contributor

ekr commented Nov 21, 2021

Additionally, implementors should be aware of issues presented by a Spoofed DNS records where the record returned by a malicious DNS Server is inauthentic and allows the record to be pointed at a malicious server which contains a different DID Document. To prevent this type of issue, usage of DNSSEC which is defined in RFC4033, RFC4034, and RFC4035.

The point of having the server authenticate via HTTPS is to not have to rely on DNSSEC here.

gribneau mentioned this issue

Reorganize, streamline, and extend did:web. #42 #43

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment