You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
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:
Dumping a little reading list:
The text was updated successfully, but these errors were encountered: