News for hackers. Stuff that matters.
Re:Malicious attack on Wikipedia – what we know and what we’... by kfrzcode on Saturday September 07, 2019 @12:17PM (#20904709)
Nothing stopping you from capturing packets at the router or using tcpdump on your phone. Not convenient but theoretically possible.
Re:Malicious attack on Wikipedia – what we know and what we’... by mises on Saturday September 07, 2019 @12:39PM (#20904855)
Gee, lemme just call up my grandma and teach her how to set up kismet and snort.

Seriously though, this is like holding some one liable if his car is stolen and used as a get-away car in a crime. It's also not really possible to get a shell on most of these devices with serious effort, so apart from turning one off, I'm not sure how any one is supposed to mitigate this. They're too locked down to do any kind of disinfection, in most cases. I guess now I have to teach granny to use a uart cable, too.

Re:Malicious attack on Wikipedia – what we know and what we’... by kfrzcode on Saturday September 14, 2019 @05:44PM (#20974012)
I didn't say it was easy or a solution to the problem. I was adding an additional point of context to a discussion in order to clarify the parent comment, which was insinuating impossibility of said action.

It's not easy, but it's not impossible. I could envision a software based solution that approaches simplicity in installation.

What I'm not arguing, is that someone should be held liable for their devices being used in a botnet.

I believe the manufacturers and retailers have the liability. But I am definitely not a lawyer.

Re:Malicious attack on Wikipedia – what we know and what we’... by dna_polymerase on Saturday September 07, 2019 @12:28PM (#20904777)
> Nothing stopping you from capturing packets at the router or using tcpdump on your phone. Not convenient but theoretically possible.

You don't interact with people out of your bubble much, do you? It's time to start write better code, not blaming users for the programmer's incapability.