[HTTPS-Everywhere] Google Searches
Peter Eckersley
pde at eff.org
Fri Mar 2 14:07:27 PST 2012
I've tried to switch country-specific search users back to their cctld google
sites with this commit:
https://gitweb.torproject.org/https-everywhere.git/commitdiff/331ab2aa740e29ef88c59ab513c2add91361031f
This is a fairly significant change, it could probably benefit from a review
or two before we test it in the wild. It seems tow work for me, but I haven't
tested all the combinations of logged in|logged out, US|geolocated elsewhere.
I also haven't tested its interactions with the things in all of the other
Google rulesets.
On Mon, Feb 27, 2012 at 08:30:18AM +0000, Nick Cross wrote:
> Hi,
>
> Thanks for the reply.
>
> The halfway point seems like a reasonable solution. The additional
> functionality on country specific sites seems to be the issue and I
> guess until Google provides encrypted.google.[co.uk] then using
> https://www.google.co.uk may be the only option
>
> Currently I have aded my own rule and disable the built in google
> search rule - this seems to work fine.
>
> Thanks
>
> Nick
>
>
> On 25/02/12 00:06, Peter Eckersley wrote:
> >I'm wavering on the encrypted.google.com / www.google.com issue.
> >
> >Another thing that is pushing me is this:
> >
> >https://trac.torproject.org/projects/tor/ticket/5152
> >
> >One halfway point might be to use the native non-US cctld sites when the user
> >types them or is redirected there, but stick with encrypted.google.com for US
> >users.
> >
> >On Tue, Feb 21, 2012 at 10:16:37PM +0000, Nick Cross wrote:
> >>
> >>Hi,
> >>
> >>I know the search uses encrypted.google.com which according to the
> >>FAQ supplies slightly better security.
> >>
> >>However, if I use http://www.google.com or https://www.google.com it
> >>reroutes me to the country specific site of http://www.google.co.uk
> >>or https://www.google.co.uk and most importantly I get the option to
> >>"show pages from the uk" which I find invaluable when searching.
> >>
> >>I understand you will not change httpseverywhere to use
> >>https://www.google.[co.uk|com] instead of encrypted.google.com but
> >>could you perhaps consider making it configurable?
> >>
> >>Currently my wife just turns off httpseverywhere just to get
> >>searches working correctly!
> >>
> >>Do custom rules overrule the built in rules?
> >>
> >>Thanks!
> >>_______________________________________________
> >>HTTPS-everywhere mailing list
> >>HTTPS-everywhere at mail1.eff.org
> >>https://mail1.eff.org/mailman/listinfo/https-everywhere
> >
>
--
Peter Eckersley pde at eff.org
Technology Projects Director Tel +1 415 436 9333 x131
Electronic Frontier Foundation Fax +1 415 436 9993
More information about the HTTPS-everywhere
mailing list