{"id":2331,"date":"2013-07-23T10:00:46","date_gmt":"2013-07-23T14:00:46","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=2331"},"modified":"2020-02-26T10:41:28","modified_gmt":"2020-02-26T15:41:28","slug":"send-gmails-that-not-even-google-can-read","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/send-gmails-that-not-even-google-can-read\/2331\/","title":{"rendered":"Send Gmails That Not Even Google Can Read"},"content":{"rendered":"

Google provides some pretty strong security controls like two-factor authentication in order to prevent hackers from hijacking your account and other controls that allow you to recover your account in the event that it\u2019s compromised. Unfortunately, Google monitors messages on its freely available email service in order to serve specifically tailored ads, and if the National Security Agency comes knocking on Google\u2019s Mountain View, California doors with warrant issued by the Federal Intelligence Surveillance court, then Google has no choice but to hand data from your various Google accounts.<\/p>\n

\"gmail_title_EN\"<\/a><\/p>\n

A San Francisco-based email management company called Streak somewhat recently developed SecureGmail<\/a>, an excellent, open-source Chrome-extension the gives users the power to encrypt their messages locally, so that Google never has access to the unencrypted contents of a given message. That\u2019s right, the only thing that ends up on Google\u2019s servers is the completely and incomprehensibly encrypted text. And if Google can\u2019t read your emails, then it\u2019s a safe bet that no one else can either.<\/p>\n

I once broached the subject of whether or not Gmail was safe for work<\/a>. SecureGmail is definitely safe for work.<\/p>\n

It works like this: you go to the Chrome Web Store and install the SecureGmail extension for free. When you want to send a secure message, you\u2019ll notice a small box next to the compose button with a nearly invisible padlock on it. If you click it, a red, compose message box saying \u201cNew Message \u2013 Secured\u201d will pop-up.<\/p>\n

\"Screen<\/a><\/p>\n

After you pick a recipient and compose your email, you will be prompted to create a password. When your recipient receives the email he or she will be prompted to enter the password. If a user has not yet installed SecureGmail, he or she will be prompted to do this as well. After your recipient enters the password, he or she can read the message. Just like that: free privacy.<\/a><\/p>\n

SecureGmail is only as strong as the password you create and the password you create is only as strong as the method you choose to deliver it.<\/div>\n

\u00a0<\/p>\n

The obvious question becomes, how do you securely relay that password? The best choice is in person, but that may not be possible. SecureGmail will also let you create a hint for the password. This could be a secure way to relay the message without ever even telling the recipient what the password is, but you\u2019d need to be pretty clever to play it this way.<\/p>\n

Remember, SecureGmail is only as strong as the password you create and the password you create is only as strong as the method you choose to deliver it. It\u2019s not a terrible idea to write down a completely random, alpha-numeric password mixing in capital and lower case letters and symbols and just mail it to your recipient. You could tell your recipient the password in a phone conversation or over the internet too, but this is less secure. DO NOT send the password via Gmail or any other Google service. That would completely undercut the purpose of SecureGmail. This bears repeating though, the very best way to transmit the password is by whispering it in the recipient\u2019s ear. Get creative about sending it; think cloak and dagger.<\/p>\n

Your password is also no good if someone has already installed a keylogger or compromised your machine in some other way. So make sure you keep everything up-to-date and run a solid anti-virus product<\/a>.<\/p>\n

Encryption is really the backbone of Internet security<\/a>. This extension is particularly great \u2013 among the best in fact<\/a> \u2013 because it brings strong encryption to Gmail in such a simple, intuitive way that almost anyone can figure it out and improve the security of sensitive messages. And better yet, it\u2019s security that you get to control!<\/p>\n

\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"

Google provides some pretty strong security controls like two-factor authentication in order to prevent hackers from hijacking your account and other controls that allow you to recover your account in<\/p>\n","protected":false},"author":42,"featured_media":2334,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5],"tags":[261,175,22,363],"class_list":{"0":"post-2331","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"tag-encryption","9":"tag-gmail","10":"tag-google","11":"tag-personal-data"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/send-gmails-that-not-even-google-can-read\/2331\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/send-gmails-that-not-even-google-can-read\/2232\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/send-gmails-that-not-even-google-can-read\/2280\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/send-gmails-that-not-even-google-can-read\/1254\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/send-gmails-that-not-even-google-can-read\/2331\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/send-gmails-that-not-even-google-can-read\/2331\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/encryption\/","name":"encryption"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/2331","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/42"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=2331"}],"version-history":[{"count":3,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/2331\/revisions"}],"predecessor-version":[{"id":32841,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/2331\/revisions\/32841"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/2334"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=2331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=2331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=2331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}