[HTTPS-E Rulesets] Google search rule

[Mike Cardwell]

On 27/10/11 10:50, Ira Hanson wrote:

> A secure Google search can now be performed from the URL
> <https://www.google.com/>, as well as from the older secure URL,
> <https://encrypted.google.com/>. (See
> <http://googleblog.blogspot.com/2011/10/making-search-more-secure.html>.)
> I don't know whether there are plans change the rules for these URLs,
> but I have attached a version of the file Google.xml that is intended
> to redirect to the newer URL. I'm new to writing rules, so I just
> replaced all of the instances in the file of the string
> [to="https://encrypted.google.com] with [to="https://www.google.com].
> Based on some preliminary tests, it appears to be working.

FWIW, https://www.google.com/ is not a new thing. It has existed for
longer than https://encrypted.google.com/. "encrypted.google.com" was
created for the reasons explained here:

http://googleenterprise.blogspot.com/2010/06/update-on-encrypted-web-search-in.html

Which basically boils down to: network admins wanting to snoop/censor
Google searches, and Google helping them.

-- 
Mike Cardwell https://grepular.com/  https://twitter.com/mickeyc
Professional  http://cardwellit.com/ http://linkedin.com/in/mikecardwell
PGP.mit.edu   0018461F/35BC AF1D 3AA2 1F84 3DC3 B0CF 70A5 F512 0018 461F

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <http://lists.eff.org/pipermail/https-everywhere-rules/attachments/20111027/bd783e85/attachment.sig>