https://www.defcon.org/html/defcon-23/dc-23-speakers.html#Gr...
https://news.ycombinator.com/item?id=6521517
These discussions are definitely post-mortem analysis but there is also discussion on another OpSec presentation:
Protecting livestock, so they can be fleeced by their proper owner, on the otherhand, doesn't imbue the same sort of charisma upon the good shepherd.
Example: https://thetinhat.com/tutorials/darknets/tor-vpn-using-both....
I see your point, don't worry, it would just be a lot more rough than you're implying, particularly to upload many heavy PDFs. (I kind of want to lab it now that we've discussed it.)
Turns out Cloudflare deems 5 seconds latency too much. I thought most default timeouts were something like 30 seconds, and when writing applications myself I usually limit them to 8 or 10 seconds (to be able to get back to the user quick enough with an "unable to connect" error, but to also give it a moment). I expected that 5 seconds latency would be slow, but not unbearable. Instead it breaks stuff completely.
From my testing, 3.5 seconds latency works fine. Slow, but it consistently works.
Adding 5 seconds latency just breaks TLS connections to Cloudflare, though DNS, TCP and HTTP work. I was able to retrieve a webpage (via netcat) from my site, the redirect to HTTPS from http://news.ycombinator.com worked, and pinging showed a consistent 5030ms +/- 10ms latency.
Adding 3.5 to 5 seconds latency (random variance) makes, as expected, some connections fail. On my second try, I was able to load the Hacker News homepage, consisting of: 1) the homepage; 2) robots.txt (wget retrieves this); 3) css file; 4) javascript file; 5) favicon; 6-10) 4 images. In total 10 resources, taking a minute and 20 seconds. After establishing a TLS connection, it could reuse that connection for multiple requests. I think this is equivalent to hitting reload a few times in a browser.
So VPN-TOR-VPN might work still, though it is indeed more on the edge than I expected. Thanks for making me venture here, I learned something!
Relatively, sure. But I've found it very usable in recent times actually. Used it almost full-time (besides a normal Firefox instance for the company's intranet) to get around some silly firewall that wouldn't let me download "hack tools" (I was an intern in the cyber security department, security tools were part of my job). There were times where I didn't notice at all that I was using Tor, and most of the time it was comparable to mediocre wifi.
And as for monitoring, I guess it might be possible, but if someone thinks to use bridge nodes that's also defeated.
https://grugq.github.io/blog/2013/12/21/in-search-of-opsec-m...
I discovered he moved to Github pages after years only to realize he has not published much since I first heard of him.
Maybe they would have found other evidence. But it wouldn't have been just him connecting to Tor.
The University simply looked their their logs to see who was connecting to known Tor nodes, narrowed it down by time and found the kid.
Source: http://www.theregister.co.uk/2013/12/18/harvard_bomb_hoax_ch...