16 ms·
> Based on what little I know of SSL, this suggests the server was compromised too? Not necessarily. If a passive snooper knows I used Tor Browser to make an
by michaelt 4y ago
> Based on what little I know of SSL, this suggests the server was compromised too?
Not necessarily.
If a passive snooper knows I used Tor Browser to make an SSL request to en.wikipedia.org and received 987,654 bytes then immediately made a SSL request to upload.wikimedia.org and received 1,234,567 bytes that might be enough information to work out I visited https://en.wikipedia.org/wiki/National_Security_Agency https://en.wikipedia.org/wiki/National_Security_Agency.
- Scoundreller 4y agoBRB, padding all of my webpages to be exactly 650mb each.
- deleted 4y ago[deleted]
- kylehotchkiss 4y agonpm install electron react-native-web
- Jerrrry 4y agoThat size-inference side channel leak has been patched for years, random padding is added between hops to mitigate this. It is large files / DDoS going over the network that is still hard to obfuscate. Which is why TOR is intentionally slow, especially when requesting larger files. If it wasn't, you could watch the lump of data traverse across the pipe. source: n/a
- HackerNCoder 4y agosource: padding spec, https://gitweb.torproject.org/torspec.git/tree/padding-spec.txt https://gitweb.torproject.org/torspec.git/tree/padding-spec....
- Jerrrry 4y agoThank you. My brain is very damp but knew it was somewhere.
- Run_DOS_Run 4y agoThat's why Tor is communicating mostly over fixed-size cells with a fixed size of 514 bytes (or 512 if tor version < 4). There is also random padding added to cells, so that the cell content is unpredictable.