Skip to content
This repository has been archived by the owner. It is now read-only.

Do dns-addressed links guarantee content authenticity? #225

Closed
dotchev opened this issue Feb 12, 2017 · 7 comments
Closed

Do dns-addressed links guarantee content authenticity? #225

dotchev opened this issue Feb 12, 2017 · 7 comments

Comments

@dotchev
Copy link

dotchev commented Feb 12, 2017

Considering that a dns link of the form /ipns/exmple.com contains 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?

@Kubuxu
Copy link

Kubuxu commented Feb 12, 2017

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.

@kcolford
Copy link

kcolford commented Mar 30, 2017

@Kubuxu On that note, do you use DNSSEC validation on your gateways (to prevent such spoofing where an administrator has set it up correctly)?

@Kubuxu
Copy link

Kubuxu commented Mar 31, 2017

Not sure, cc @lgierth

If we are not, we might want to do that.

@lidel
Copy link

lidel commented Mar 31, 2017

@ghost
Copy link

ghost commented Mar 31, 2017

Yeah we might want to have IPNS check DNSSEC signatures. Low priority for now, but I'll happily support pull requests.

@Kubuxu
Copy link

Kubuxu commented Mar 31, 2017

I think it is more of a infrastructure thing, having local resolver working with DNSSEC.

@madavieb
Copy link

madavieb commented May 23, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants