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.

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

Domain fronting #18

Open
ghost opened this issue May 14, 2017 · 2 comments
Open

Domain fronting #18

ghost opened this issue May 14, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented May 14, 2017

Domain fronting is a technique that incentivizes actors to not block an individual website/service. It's used by Signal, Lantern, Tor, Psiphon, and others.

I can see this being useful to:

  • protect bootstrapping -- we can make the go-ws-transport capable of domain fronting, and then deploy websockets bootstrappers with major cloud providers
  • protect individual IPNS/dnslink pages -- with TLS/SNI inspection, it's possible to allow 99% of traffic to the ipfs.io gateway, but block e.g. example.com CNAME'd to the ipfs.io gateway.

Dumping a little reading list:

@mnp
Copy link

mnp commented Apr 22, 2018

@Mikaela
Copy link

Mikaela commented Feb 15, 2019

The Register thinks that ESNI is the solution Don't panic about domain fronting, an SNI fix is getting hacked out, but I don't see issues about it or TLS 1.3 or DNS over HTTPS here. Do you have any plans for them or are they something that would need to be implemented by users of libp2p?

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

No branches or pull requests

2 participants