Live data from Hacker News

Comcast is injecting 400+ lines of JavaScript into web pages

forums.xfinity.com

281–290 of 498 posts

Re: Comcast is injecting 400+ lines of JavaScript into web pages

#281

J. Livingood (a Comcast VP) responded to the OP: > [JL] We are not trying to sell you a new one. If you own your modem we're informing you that it is either end of life (EOL) or that you are about to get a speed upgrade that the modem will be unable to deliver. Incidentally, Livingood is a co-author of IETF RFC 6108, which he has conveniently linked. From the RFC's general requirements numero uno: > R3.1.1. Must Only…

I think it's amazing Comcast documented their MITM attack as an RFC. Are those still literally Requests for Comments? Are the comments collected anywhere?

RFC 6108 is from 2011, last revised 2015, and marked as informational, which I think means there's no review & comment... But I'm not sure about that.

Re: Comcast is injecting 400+ lines of JavaScript into web pages

#284

The thing that's so irritating about large telco's is not just that they're evil, but the casual stupidity of their actions, including their evil actions. I mean, look at the code. Look at the function of this code. Look at the business purpose of this code. Look at the security aspects of using this code. Look at the legal ramifications (why the hell is that LGPL thing up top there ?). Look at their internal communi…

> How can an organisation that executes this badly become this big ? Lots of ads, undercut your competition by something like $1 and "new customer deals" and then shaft your customers after a while The average customer just go to the store with the flashier lights (or the one which is more convenient)

> "undercut your competition"

When there even is any competition. Where I live, it's literally Comcast or else tether my mobile phone. Satellite is technically an option, but realistically between the cost and my tree coverage there's no way to make it work.

Re: Comcast is injecting 400+ lines of JavaScript into web pages

#285

Earlier quoted context omitted.

Use HTTPSEverywhere on your browsers, and then enjoy the "You're close to your monthly limit!" pop-up on the Steam Store!

What?

I think the intent was to comment that extensions don't protect programs with embedded web views, like the steam store. I'd hope the steam store is using https though...

Re: Comcast is injecting 400+ lines of JavaScript into web pages

#286
post #282

Does Comcast inject this code in https urls or just http urls? Since https transfer is encrypted I suspect the code injection can't be done. Can someone please tell if my reasoning is correct?

Yeah that's correct, they can't do it in https unless they did something with root certs, which would be 1000x more messed up (And that's saying a lot because this is already pretty despicable). At any rate if they were doing that browsers would revoke the CA.

Re: Comcast is injecting 400+ lines of JavaScript into web pages

#287

Comcast forced me to upgrade a perfectly acceptable modem so I would have to option to have higher speed service (which I do not want)! Here's what they did: 1. asked me to upgrade the modem (emails and letters) 2. Inserted a filter on my line so I lost my connection 3. I bought a new modem (not realizing they stuck a filter there) 4. They removed the filter I guess this approach does not scale as well as the 400 lin…

What spec of DOCSIS was your old modem? If it was 1.0, 1.1, or 2.0, sorry you lose all support, the older specs had hard bonded channels that HD TV on them after the swap that they informed people of for 2 years before it happened. And they put TV on them since they were degrading channels due to overuse across the entire network (as in across the country). The later specs allowed for floating channels based on chann…

The SB6121 is a DOCSIS 3.0 4x4 modem rated for 174mbps, SB6141 is a 8x4 rated for 343mbps, and SB6181 is a 16x4 rated for 686mbps. Outside of their capabilities, the hardware on them are nearly identical. There is nothing "EOL" about the SB6121 except for the idea that it's unable to support 200mbps. It's a perfectly good entry-level modem capable of offering speeds that are over 7 times the minimum definition of "high speed internet".

Re: Comcast is injecting 400+ lines of JavaScript into web pages

#288

Earlier quoted context omitted.

> Although I disagree with Comcast's method and categorization, it would be interesting to learn what modem the OP was using. We start telling customers that a modem needs to be upgraded when one of two things happen: either they are about to or just had a speed upgrade that their modem cannot support or the modem has gone end-of-life (EOL) from the vendor. In the former case, if the device is leased, you are send a…

All that may be true. There is no ethical excuse to ever inject code into a webpage. Your own argument about it being critical is false or sophistry. If there were wildfires coming to burn someone's house down..that might qualify as critical. Not this, and deep down you know it. You should be embarrassed to attach your name to such an obviously poor decision.

Indeed. Whoever thinks this is fine would probably also be okay with the telephone company injecting jingles into your phone conversations every 30 seconds.

Re: Comcast is injecting 400+ lines of JavaScript into web pages

#289

Could Comcast hijack DNS and redirect https requests to a page explaining the issue with a button that lets the user go back to the site they wanted to visit? Or do modern browsers mitigate that?

They could but because of HSTS (https://blog.stackpath.com/glossary/hsts/) which would largely mitigate it. They have a preload list in browsers too. But if a site wasn't using HSTS then yeah they could do that. I don't think that's better per-se.

Re: Comcast is injecting 400+ lines of JavaScript into web pages

#290

Earlier quoted context omitted.

What?

I think the intent was to comment that extensions don't protect programs with embedded web views, like the steam store. I'd hope the steam store is using https though...

Only on checkout pages. For the rest of the storefront they actually redirect you from HTTPS to HTTP.
Post reply on HN