This repository has been archived by the owner. It is now read-only.
Do dns-addressed links guarantee content authenticity? #225
Comments
|
If DNS takeover/spoofing is part of your threat model, yes. We use DNS to resolve them to hash links, so if DNS service is compromised they hash link can be replaced. |
|
@Kubuxu On that note, do you use DNSSEC validation on your gateways (to prevent such spoofing where an administrator has set it up correctly)? |
|
Not sure, cc @lgierth If we are not, we might want to do that. |
|
This may be helpful: |
|
Yeah we might want to have IPNS check DNSSEC signatures. Low priority for now, but I'll happily support pull requests. |
|
I think it is more of a infrastructure thing, having local resolver working with DNSSEC. |
|
This issue has been moved to https://discuss.ipfs.io/t/do-dns-addressed-links-guarantee-content-authenticity/462. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
dotchev commentedFeb 12, 2017
•
edited
Considering that a dns link of the form
/ipns/exmple.comcontains no public key hash, how can we be sure of the authenticity of the content it points to?Isn't it a security degradation compared to normal ipns links?
The text was updated successfully, but these errors were encountered: