[anti-abuse-wg] Google Privacy Abuse
- Previous message (by thread): [anti-abuse-wg] Google Privacy Abuse
- Next message (by thread): [anti-abuse-wg] Google Privacy Abuse
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Esa Laitinen
esa at laitinen.org
Thu Mar 14 09:53:47 CET 2019
On Thu, Mar 14, 2019 at 6:05 AM ac <ac at main.me> wrote: > HTTPS protocol, by design, is secure and private. > > The average consumer expects this to be true. > > Google had to actually go and change, in an "under cover" way, the > entire way and method that HTTPS works. This "change" is being sold as > a "good thing" to poor people and/or people with low bandwidth and that > Google is doing a "good thing" by making this change. > Dear Andre The URLs you're accessing are also available for - your ISP - your VPN provider (unless you've rolled your own) and some information is also potentially stored by - your DNS provider And Opera browser has been doing similar things when you've enabled the bandwidth savings. or am I missing something? OK. I'm ignoring here that this particular thingi is using MITM methods to do the optimization, which is for me a bit more worrying than google having access to the URLs I browse. They have them mostly anyway. But, it is a choice a user makes, it is not forced upon them. Yours, esa -- Skype: reunaesa Yahoo: reunaesa Mobile: +4178 838 57 77 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20190314/f15bcef3/attachment.html>
- Previous message (by thread): [anti-abuse-wg] Google Privacy Abuse
- Next message (by thread): [anti-abuse-wg] Google Privacy Abuse
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]