![]() (You can just message them on a dating application, though then they'll make a show of refusing to hire you and reporting you to the FBI as a possible cyberterrorist. and they were tanking my GPA.Īnyways, I'm re-hash-ing very old gripes, but it felt like something fundemental shifted when https went widespread, while universities seem to focus on weird CTF bullshit. they weren't some cute woman from Iowa in town for a book signing meeting me for espresso, they were literally a professor teaching, in one case, a "statistics for psychology students" course I selected EXPLICITLY because their students also haven't had Calculus. (In retrospect, it was a situation where I was rules lawyering because I was pissed because I kept bumping into a string of people who'd tell me "It's not my job to teach you" only. I ended up in the actual professor's office, with a listout of the various codes for manufacturers and pointing out there's no "OSX" specific one. The TA marked it wrong and said "no, it's from an OSX system". I got hung up on the fact an extra credit question go marked wrong because I said based on the SSID, the packets were from a BSD operating system. I have no idea if that's still the case, because those moron librarians added a card reader, and I don't know how to parkour onto the roof of that building. Thanks for this! I haven't really played around with packet captures since back before HTTPS was widespread but I've heard a lot of people gripe about it over the years.īig shoutout to one of the poor bastards who had me as their student back when Pitt segmented the school of information science away from the rest of the network. On Android specifically, the WireGuard app allows you to only proxy specific apps (not possible with a global proxy config)ĭoes that make more sense now? We also have a bit more documentation at. You avoid the "apps ignore proxy settings" problem. You can intercept/modify UDP, in particular DNS. Put differently, instead of using an explicit proxy configuration or something like iptables to route packets to mitmproxy, you use a VPN (WireGuard). mitmproxy then transparently intercepts all requests that are coming through that WireGuard tunnel (the device still needs to trust the mitmproxy CA). Now you don't set a proxy on your device, but you configure your device to use WireGuard with a config that sends all traffic to mitmproxy. To overcome these shortcomings, we now have WireGuard mode: Mitmproxy spawns a WireGuard server on startup (instead of an HTTP proxy listener). ![]() Additionally, apps may choose to ignore the proxy settings and it's hard to tell if they do. You could configure an HTTP proxy in your system settings, but this does not capture any UDP-based protocols. Suppose you have an Android device for which you want to see all traffic. ![]()
0 Comments
Leave a Reply. |