Comcast is injecting 400+ lines of JavaScript into web pages

Re:Comcast is injecting 400+ lines of JavaScript into web pages by AndyMcConachie on Sunday December 10, 2017 @10:01AM (#15891659)

TFA mentions a Comcast tech referencing RFC 6108:

"[JL] This is our web notification system, documented in RFC 6108 https://tools.ietf.org/html/rfc6108, which has been in place for many years now."

However, RFC 6108 requirement for use R3.1.1 states:

   R3.1.1.   Must Only Be Used for Critical Service Notifications
             Additional Background: The system must only provide
             critical notifications, rather than trivial notifications.
             An example of a critical, non-trivial notification, which
             is also the primary motivation of this system, is to advise
             the user that their computer is infected with malware, that
             their security is at severe risk and/or has already been
             compromised, and that it is recommended that they take
             immediate, corrective action NOW.

RFC 6108:

https://tools.ietf.org/html/rfc6108

[ Parent | on HN ]

Re:Comcast is injecting 400+ lines of JavaScript into web pages by robterrell on Sunday December 10, 2017 @11:07AM (#15891982)

I'm sure the comcast "tech" knows what's in the RFC. Look in the top-right corner; he's one of its authors. He's also replying in this thread.

[ Parent | on HN ]

Re:Comcast is injecting 400+ lines of JavaScript into web pages by AndyMcConachie on Sunday December 10, 2017 @09:19PM (#15894717)

Do you consider upselling subscribers on modems a critical service notification? I don't.

[ Parent | on HN ]

Re:Comcast is injecting 400+ lines of JavaScript into web pages by kkmx on Sunday December 10, 2017 @11:02AM (#15891962)

Yea they don't really follow that RFC, they just use that RFC as an all-justification for their action.

[ Parent | on HN ]