I wouldn't fuck with anything related to flying tbh, since that shit is pretty closely monitored for anything sus.
this post was submitted on 25 Sep 2023
71 points (96.1% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54609 readers
763 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
OP, please listen to this.
What are they gonna do? Kick you out of the plane?
Put you on the no-fly list
I already got there when I opened a Linux terminal and somebody yelled "HE HAS A BOMB"
Do you really want to fuck around and find out...
Depends how much work you want to do? You could tunnel a VPN over DNS queries, and that usually works in many networks, cuz they still let you look up DNS entries even if they're not routing your traffic
I had success with iodine, it's slow but it worked.
I remember seeing some chatter about tunneling over XMPP. Most plane wifi allows chat protocols, and it should be possible to encapsulate your traffic as ascii text in XMPP packets. You "just" need to set up the endpoints to do the bridging.
Of I were to do it, I'd run a a script that sets up a tun/tap interface that everything else on my laptop will communicate through. This script also connects to my xmpp server at home. Any data coming in on the tun/tap is encoded to ascii strings and sent as chat messages to my xmpp server. The same script can also do the reverse. At home a similar script does, mirroring that on my laptop. Make sure prerouting is set up accordingly in both ends.
From what I've seen on planes, it's mostly down to captive portals using mac addresses to track clients. In theory it should also be able to sneak through by spoofing hardware addresses of someone who's paid for the service.
I only understood about half of that, but it seems like this would result in very high ping and very low bandwidth.
You will get that on airplanes anyways
Hop on a plane between a major city and Las Vegas a couple days before DEFCON and I'm sure someone will know
I'd want to look into where the limitation is.
- If it's with DNS, you can just set your local resolver to
1.1.1.1(Cloudflare) - If it's on the port, then you can try tunnelling traffic over port 443 to somewhere that simply relays your traffic onward, like a personal server running SSH on port 443.
- If it's on the IP, blocking access to any IPs not in a whitelist of known WhatsApp IPs, you may be SOL.
Didn't Facebook block this by limiting the number of messages you can send in a given time period? I remembering reading something about that, but can't remember the context.
First, you find out how they whitelist whatsapp. Is it IP address? SNI? Restricted DNS?
Of course your seat neighbor is going to see you using hacking tools, call the FA and you'll be arrested when you land.
They use MAC address filtering I believe.
Mac filtering aint doing shit in this case.
Either it's open or not with MAC filtering.
This is more likely protocol, port and IP/DNS based blocking.
You can run an arp-scan to check and see if there are any devices on the network that could be whitelisted and spoof their MAC