Update June 25, 2010: Since we introduced our encrypted search option last month, we’ve been listening closely to user feedback. Many users appreciate the capability to perform searches with better protection against snooping from third parties. We’ve also heard about some challenges faced by various school districts, and today, we want to inform you that we’ve moved encrypted search from https://www.google.com to https://encrypted.google.com. The site functions in the same way. For more information on this change, please read on here.
As people spend more time on the Internet, they want greater control over who has access to their online communications. Many Internet services use what are known as Secure Sockets Layer (SSL) connections to encrypt information that travels between your computer and their service. Usually recognized by a web address starting with “https” or a browser lock icon, this technology is regularly used by online banking sites and e-commerce websites. Other sites may also implement SSL in a more limited fashion, for example, to help protect your passwords when you enter your login information.
Years ago Google added SSL encryption to products ranging from Gmail to Google Docs and others, and we continue to enable encryption on more services. Like banking and e-commerce sites, Google’s encryption extends beyond login passwords to the entire service. This session-wide encryption is a significant privacy advantage over systems that only encrypt login pages and credit card information. Early this year, we took an important step forward by making SSL the default setting for all Gmail users. And today we’re gradually rolling out a new choice to search more securely at https://www.google.com.
When you search on https://www.google.com, an encrypted connection is created between your browser and Google. This secured channel helps protect your search terms and your search results pages from being intercepted by a third party on your network. The service includes a modified logo to help indicate that you’re searching using SSL and that you may encounter a somewhat different Google search experience, but as always, remember to check the start of the address bar for “https” and your browser lock indicators:
Today’s release comes with a “beta” label for a few reasons. First, it currently covers only the core Google web search product. To help avoid misunderstanding, when you search using SSL, you won’t see links to offerings like Image Search and Maps that, for the most part, don’t support SSL at this time. Also, since SSL connections require additional time to set up the encryption between your browser and the remote web server, your experience with search over SSL might be slightly slower than your regular Google search experience. What won’t change is that you will still get the same great search results.
A few notes to remember: Google will still maintain search data to improve your search quality and to provide better service. Searching over SSL doesn’t reduce the data sent to Google — it only hides that data from third parties who seek it. And clicking on any of the web results, including Google universal search results for unsupported services like Google Images, could take you out of SSL mode. Our hope is that more websites and services will add support for SSL to help create a better and more consistent experience for you.
We think users will appreciate this new option for searching. It’s a helpful addition to users’ online privacy and security, and we’ll continue to add encryption support for more search offerings. To learn more about using the feature, refer to our help article on search over SSL.
Jumat, 21 Mei 2010
Langganan:
Posting Komentar (Atom)
Blog Archive
-
▼
2010
-
▼
Mei
- This week in search 5/30/10
- Happy 1st birthday, Google Wave!
- We’ve officially acquired AdMob!
- Watch efforts to stop the oil spill live and submi...
- Congratulations to Aadith Moorthy, the 2010 Nation...
- The 2010 Doodle 4 Google winner: Makenzie Melton’s...
- Evolving from beta to stable with a faster version...
- Google’s U.S. economic impact
- PAC-MAN rules!
- Google Special Award Winners @ Intel ISEF 2010
- Keeping up-to-date on the Gulf of Mexico oil spill
- Google Apps highlights – 5/21/2010
- Search more securely with encrypted Google web search
- Working with AdMob to move mobile advertising forward
- Celebrating PAC-MAN’s 30th birthday
- Announcing Google TV: TV meets web. Web meets TV.
- Android Froyo, with some sprinkles
- Google I/O 2010 Day 1: A more powerful web in more...
- Celebrating Bike to Work Day(s)
- Simplify common tasks with the new Google Apps Script
- Remember to tune in to live-streamed Google I/O ke...
- Doodle 4 Google, meet the 40 Regional Finalists (w...
- This week in search 5/14/10
- WiFi data collection: An update
- Announcing the Google Model Your Town Competition ...
- Nexus One changes in availability
- Google Voice invites for students
- Five more languages on translate.google.com
- Hello Google Apps, hello real collaboration
- A word is worth 884 pictures
- Understanding the web to find short answers and “s...
- Giving a voice to more languages on Google Translate
- Google @ Intel ISEF 2010
- This week in search 5/7/10
- Google Apps highlights – 5/7/2010
- Schools are (almost) out for summer...and in for Apps
- Honoring those who give voice to the silenced
- The Google design, turned up a notch
- Live, from Google I/O!
- Happy half-birthday Dashboard! Six months in and 1...
- A spring metamorphosis — Google’s new look
- Mapping the Gulf oil spill in Google Earth
- Google Ventures: Year one
- Not merely tilting at windmills — investing in the...
- Introducing Google’s 2010 Anita Borg Scholars & Fi...
- This week in search 5/1/10
-
▼
Mei
0 komentar:
Posting Komentar