Damn that's smart. I think I remember watching a defcon talk a few years ago where someone made a script that ran on the router to replace imaged in real-time to fuck with wifi leaches - I wonder if something similar could be done so it replaces stuff with things that will trigger them hard.
Man-in-the-middle shenanigans are much harder with TLS (SSL) conversations, which unsurprisingly has been what Google has been push hard at, for years. You'd have to serve content that's from a cert-signed source. All the other browser makers have followed suit so that you can't even go to an unsecured site without huge warnings.
There's still valuable information to be gained. DNS over HTTPS is fairly rare still, you'd be able to get a lot of information from just hostnames and outgoing IPs. While you couldn't get path or form data, you're still tracking time spent on sites and usage habits.
Damn that's smart. I think I remember watching a defcon talk a few years ago where someone made a script that ran on the router to replace imaged in real-time to fuck with wifi leaches - I wonder if something similar could be done so it replaces stuff with things that will trigger them hard.
Man-in-the-middle shenanigans are much harder with TLS (SSL) conversations, which unsurprisingly has been what Google has been push hard at, for years. You'd have to serve content that's from a cert-signed source. All the other browser makers have followed suit so that you can't even go to an unsecured site without huge warnings.
There's still valuable information to be gained. DNS over HTTPS is fairly rare still, you'd be able to get a lot of information from just hostnames and outgoing IPs. While you couldn't get path or form data, you're still tracking time spent on sites and usage habits.