HTTPS Deployment Growing by Leaps and Bounds

Re:HTTPS Deployment Growing by Leaps and Bounds by tyingq on Friday December 23, 2016 @12:29PM (#13245927)

>HTTPS keeps your ISP, your wifi hotspot, a dodgy router, or anything else from injecting ads and tracking information into your pages

I suspect this is the main reason Google is so gung-ho about "https everywhere". Because of the popularity of GA, adsense, Double Click, and Google local caches at every ISP...they already have near global tracking. Closing the ISP MITM hole ensures that nobody else does.

Of course, "https everywhere" is good for other reasons, so not complaining...

[ Parent | on HN ]

Re:HTTPS Deployment Growing by Leaps and Bounds by iRobbery on Friday December 23, 2016 @01:00PM (#13246161)

i agree, though i'm worried about the security it actually offers and what protocols and ciphers are still considered secure.

Next PCI DSS will require most services to be using (and not honoring lower then) TLSv1.2; i'm not sure about what to do when (not matter of if, but when) that is considering no longer secure, TLSv1.3 isnt ready yet from what i understand.

Now that i write this i wonder, are there btw server/client solutions that utilize PGP? E.g. send requests via encryption with public pgp key server and response back to client with public key of client?

[ Parent | on HN ]