Google launches SSL encrypted searches

The prefix is great from a usability perspective because it makes it much easier to determine that you are using the encrypted site at a glance.
 
Ohhhkay... Been using https for a while now.
 
Encrypted connections between 2 nodes, nothing new here. Its probably very complex at that level but did they really need to create a completely separate domain from the ones we are are already used. Something like https://www.gooogle.co.za and why is the no https://encrypted.google.co.za
they initially had it that way, but that meant that companies / schools couldn't block ssl search without also blocking gmail /google apps logins, etc... (putting some google apps deals with schools at risk which also want to block students from searching for some terms)

(The exact details are in a blog post somewhere on the google blog)
 
How is it secure if the URL still has the search string?
HTTPS URLs are not visible across the network.

For acccessing https://www.google.com/?q=test, the following happens:
1. Connect to www.google.com port 443. (CONNECT request if (http) proxy is involved, direct TCP otherwise)
2. Negotiate SSL and establish encrypted conenction (not sure about details here)
3. Send request (GET https://www.google.com/?q=test) to server and wait for response over connection

For normal HTTP, the GET is send directly to the proxy or over the unencrypted conenction to the server.
 
hmmm - ok - thanks... studied this crap almost 10 years ago... obviously lost on me already :p
 
Top
Sign up to the MyBroadband newsletter
X