Closed Bug 738376 Opened 8 years ago Closed 8 years ago

Use https://encrypted.google.com/ instead of https://www.google.com/ for security and privacy reasons

Categories

(Firefox :: Search, defect, major)

14 Branch
defect
Not set
major

Tracking

()

VERIFIED WONTFIX

People

(Reporter: Virtual, Unassigned)

References

Details

(Keywords: nightly-community, privacy, Whiteboard: [testday-20120615])

Attachments

(1 file)

The correct option for implementing encrypted search at this scale is to use https://www.google.com, which is properly supported across Google's global search domains.
I see that both sites produce the same results in searching sth,
so it will be wise to use site with better privacy & security and didn't leak information about anything.

What https://encrypted.google.com/ didn't support, which https://www.google.com/ support ?
(In reply to Virtual_ManPL from comment #2)
> I see that both sites produce the same results in searching sth,
> so it will be wise to use site with better privacy & security and didn't
> leak information about anything.

Did you test with a clean Firefox profile from multiple IP-addresses in different non-English speaking countries and made sure that the results still were the same as with https://www.google.com?
I can only say that I see no differences in search results from my side using Firefox on different ISPs and PCs located in Poland.

If someone have different results please post it, don't forget to have same options set in settings, because it use different cookie as I see.
Attached image Google rec
Even Google stated that https://encrypted.google.com/ is "more secure and private" than https://www.google.com/

"Encrypted search

Encrypt the search traffic between your computer and Google, helping to protect your search terms and your search results pages from being intercepted by a third party. Try a more secure and private search experience."



So what are we doing with this guys ?
I think you're misinterpreting that statement - it isn't contrasting https://encrypted.google.com to https://www.google.com, it's comparing https://encrypted.google.com to the normal non-SSL Google search.

Google has told us - in this bug, even (comment 1) - that encrypted.google.com currently isn't set up to properly handle our millions of users, so we can't just make the switch.
gavin: is this a wontfix?
Whiteboard: [testday-20120615]
for the moment, yes
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.