News for hackers. Stuff that matters.

A comment on Comcast is injecting 400+ lines of JavaScript into web pages. Parent comment

Re:Comcast is injecting 400+ lines of JavaScript into web pages by sulam on Sunday December 10, 2017 @10:06AM (#15891689)
If his modem is actively interfering with your network I could see that this is critical. If he has been hacked and is actively DDOSing sites, that’s critical. We can debate the correct response in those cases (getting on the phone and calling seems to work really well when you want people to pay you, as does turning off service).

Unless I’m misunderstanding, this was not causing such a problem. Casting it as a customer good is rhetorically amusing, and probably holds water with people who are predisposed to agree with you, but I can make any number of morally bankrupt decisions using exactly the same logic. You have simpler ways to deliver this message, that do not cause nearly as much harm to your customer and do not require you to intercept and modify their traffic.

[ Parent | on HN ]
Re:Comcast is injecting 400+ lines of JavaScript into web pages by lucio on Sunday December 10, 2017 @02:14PM (#15892958)
It's true that if there's a vulnerability discovered, and you have 50000 modems with the vulnerability, you cannot wait for the modems "to be hacked" to act. It is reasonable to try to replace EOL modems ASAP.
[ Parent | on HN ]
Re:Comcast is injecting 400+ lines of JavaScript into web pages by sulam on Sunday December 10, 2017 @03:49PM (#15893422)
In this scenario do you honestly believe the best course of action is to insert a popup on web pages? If you are truly concerned you will act to preserve your network for all customers by blocking traffic from the problematic modem and then call the person. This is legally less risky than doing traffic inspection. (Losing common carrier status would be a very big deal.)
[ Parent | on HN ]