Commentary

Google: We're Encrypting Everyone's Gmail Automatically

Whether or not the timing of this announcement has anything to do with Google's recent actions in the Chinese market is unknown. The company today said that it is switching Gmail access to https for all users by default.

Whether or not the timing of this announcement has anything to do with Google's recent actions in the Chinese market is unknown. The company today said that it is switching Gmail access to https for all users by default.Gmail's log in page is always encrypted. Your username and password are safe as they travel across the Internet. The same hasn't been true for your Gmail once logged in. Back in 2008, the company gave everyone the option to use https (instead of http) for their entire Gmail experience. It has to be manually turned on in the settings menus. According to Google, https is now set by default.

The company wrote in a blog post, "Using https helps protect data from being snooped by third parties, such as in public wifi hotspots. We initially left the choice of using it up to you because there's a downside: https can make your mail slower since encrypted data doesn't travel across the web as quickly as unencrypted data. Over the last few months, we've been researching the security/latency tradeoff and decided that turning https on for everyone was the right thing to do."


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Google is in the process of rolling this out to all users. In good 'ole Google fashion, the company is still giving its customers choice. If you want to turn https off, you can do so by making the change in the settings menus.

For businesses using Google Apps, users of domains not already encrypted (by admins) can still use http Gmail. If site admins have set up https, however, the option to turn https off won't be available.

Google cautions that offline Gmail users will likely encounter problems once the switch to https is complete. Google has a few suggestions for those users here.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links