Using encryption and onion routing is all fine and dandy, but both can be detected and both can, at the very least, be severely hampered or even be cut off.<br/>
However, the Internet nowadays is full of services and systems that autonomously, and continuously, send data to users all over the world.<br/>
These messages or interactions are seen as formalities and have become a blind spot, even with security minded people; they are just the fixtures of the Internet.<br/>
In this lecture I want to try and effect a change of mind when looking at these fixtures and to show ways how to hack them.<br/>
Hack them, not to pwn them or to corrupt them, but rather hack them to use as communications method when all else is either watched, broken or blocked.<br/>
Not in the same way as 'just sending a few base64 encoded tweets', but really...
Subscription services send confirmation emails, two factor authentication systems send out text messages.
Search engines send out crawlers, IRC servers send out ident requests.
Webservers use session cookies to identify a session.
If done properly these 'fixtures' are secure and usually for a single intended recipient.
But what if we intentionally use the single-minded correctness of these systems? What would be the available entropy? Could we communicate? How fast, or rather, how slow?
What I want to convey is that 'blocking Twitter' or 'blocking Facebook' or rather, 'anything short of just switching the whole Internet off' is a pretty useless idea if the goal is to prevent people from communicating.
Just as you can use anything in the city to reach your destination in Parkour, you can use anything that <i>is</i> available which changes <i>something</i> on the Internet if your mindset is on 'hacking to <i>use</i>' things.
But what if they switch off the Internet?