-
Notifications
You must be signed in to change notification settings - Fork 281
Enforce DANE policy #50
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
Comments
DANE requires DNSSEC right? |
Yep. |
Perhaps we should include a small DNSSEC-enabled resolver in maddy. This will also make things slightly more secure in general. |
I wonder how this could integrate with the Go standard library. Is there a way to override the resolver? |
It doesn't seem to be possible, sadly. |
I would count this as a low-priority issue, after some research I found out that DANE is much less widely deployed then MTA-STS (to the point where it took a lot of effort to find ONE domain with a TLSA record). |
It would be nice to support DANE in addition to MTA-STS to increase interoperability.
Again, there are two sides in DANE support:
Check if we have DANE record and reject unencrypted MTA connections.https://tools.ietf.org/html/rfc7672
The text was updated successfully, but these errors were encountered: