4 ms·
> morning at the airport as your wife waits for you to find the tickets. Hah oh the flashbacks. I've literally done this. Except — ironically — I was keeping t
by deathanatos 3y ago
> morning at the airport as your wife waits for you to find the tickets.
Hah oh the flashbacks. I've literally done this. Except — ironically — I was keeping the tickets in the airline's app.
The airlines app, idiotically, needed the network to fetch the tickets. The airport's network was misconfigured, as many are: it had one of those idiotic "proxy all traffic to the captive portal"¹ things, so the airline app was confused about why its AJAXs weren't returning the right stuff. But in the moment (i.e., TSA) I wasn't grokking that the error from the app was a lie because the network was malicious.
Perhaps Emacs could have saved me…?
(What I do now is open the ticket beforehand and then screenshot it so that it's local. And we also bring paper fallbacks. Paper cannot have it's packets captured.)
¹There's a proper way to do captive portals. This ain't it.
- ptramo 3y agoWhat's the proper way to do captive portals?
- ElectricalUnion 3y agoHow did "proxy all traffic to the captive portal" MITM the app? Does the app ignore HTTPS errors? Does the app send your PII in plaintext? Does the app not know what are the expected protocols and status code from it's own backend servers?
- yencabulator 3y agoI once had a ticket on my phone. My phone overheated and crashed just before I reached the ticket checking station at the gate. It refused to start for several minutes, because it was still too hot. Ever since then, I've been printing out plane tickets...