5 ms·
It's even finer-grained than that. Each session gets a hostname -- if you open the same document twice, it's at a different hostname each time. This also implie
by kentonv 10y ago
It's even finer-grained than that. Each session gets a hostname -- if you open the same document twice, it's at a different hostname each time. This also implies that different users get different hostnames, so you can't discover the host another user sees even if you have access to the same document.
- collinmanderson 10y agoIsn't that insecure because hostnames are sent in the clear? (both in TLS handshake and DNS lookup?)
- icebraining 10y agoThe hostnames aren't authentication, just another layer of defense, mostly against JavaScript attacks (e.g. from hacked applications): https://docs.sandstorm.io/en/latest/administering/wildcard/#why-a-new-hostname-for-every-session-rather-than-for-every-document https://docs.sandstorm.io/en/latest/administering/wildcard/#...
- kentonv 10y agoRight, this is about mitigating the damage when apps have a bug -- risk management. Instead of being exploitable from anywhere on the internet, the bug becomes exploitable only by attackers who have a passive network MITM, which, while possible, is a very high barrier.