3 ms·

So the whole RFC Comcast submitted containing details of how they MITM HTTP traffic... https://tools.ietf.org/html/rfc6108 https://tools.ietf.org/html/rfc6108

So the whole RFC Comcast submitted containing details of how they MITM HTTP traffic... https://tools.ietf.org/html/rfc6108 https://tools.ietf.org/html/rfc6108 Nobody is affected by this?

jlarocco 9y ago
Isn't that putting the cart before the horse? If the connection were HTTPS they could simply block it or redirect it wherever they want to give the same message. An ISP will always be able to MITM the connection.
- Franciscouzo 9y ago
  You can't redirect HTTPS traffic unless you have a root certificate or have the private key of the site, and blocking HTTPS traffic would make at least 68% of web traffic not work, so not a real option.
  - dingo_bat 9y ago
    Can't an ISP's DNS server tell you that https://www.google.com https://www.google.com is at 10.10.10.10? And that is an internal server hosting whatever ISP wants.
    - Franciscouzo 9y ago
      They can, but you will get a certificate error, because the ISP doesn't has a valid certificate for the domain.
      - rhencke 9y ago
        Exactly. It will show up in any modern browser with a big red "This site is not safe!" type of message if that was to happen. This is one of the reasons Google (and others) so proactively protect the certificate infrastructure so meticulously, and run efforts like https://www.certificate-transparency.org/ https://www.certificate-transparency.org/
    - IncRnd 9y ago
      Yes, and that is an argument for https with certificates...