{"id":13006,"date":"2022-03-22T12:39:42","date_gmt":"2022-03-22T11:39:42","guid":{"rendered":"https:\/\/inlab.fib.upc.edu\/uncategorized-ca\/flowcrypt-chrome-extension-message-encryption\/2022\/"},"modified":"2023-05-24T09:17:17","modified_gmt":"2023-05-24T08:17:17","slug":"flowcrypt-chrome-extension-message-encryption","status":"publish","type":"post","link":"https:\/\/inlab.fib.upc.edu\/en\/news\/flowcrypt-chrome-extension-message-encryption","title":{"rendered":"FlowCrypt the Chrome extension for message encryption"},"content":{"rendered":"

It is common to find ourselves in situations where we have to send documents with sensitive information by email, or share passwords via WhatsApp or Slack. The moment this sensitive information is sent, we give up the certainty that the information remains private. We may think that by using the HTTPS communication protocol we ensure that no one can capture the traffic and see the information, but the problem lies in the fact that it will be private as long as the company offering the service we use (Gmail, Slack , etc.) respects privacy or, putting us in a worse situation, all the data we store, including our private documents or passwords, is leaked.<\/span><\/p>\n

To avoid possible problems, it is important to get into the habit of encrypting all this information so that only we and those we allow can read it.<\/span><\/p>\n

FlowCrypt is a Google Chrome extension that allows us to send encrypted and signed e-mails. It makes use of PGP (“Prety Good Privacy”), a protocol that allows sending encrypted documents using asymmetric cryptography. We can add the tool directly to our browser from the official website.<\/span><\/p>\n

Before going into detail on how to use this tool, we will explain how asymmetric cryptography works.<\/span><\/p>\n

What is asymmetric cryptography?<\/strong><\/h2>\n

In asymmetric cryptography, each user has a public<\/span> key and a private<\/span> key. The public<\/span> key can be shared with anyone who wants to send encrypted data to you, but the private<\/span> key should only be known to the user himself. If user A<\/strong> wants to send an encrypted email to user B<\/strong>, he will take user B<\/strong>‘s public<\/span> key and use it to encrypt the message. This encrypted message can only be decrypted by B<\/strong>‘s private<\/span> key, thus achieving privacy, since only B<\/strong> knows his private<\/span> key and is the only user capable of decrypting the message.<\/p>\n

An easy way to visualize this is to see the public<\/span> key as if it were a padlock and the private<\/span> key as if it were a key. Everyone will be able to take the padlock<\/span> offered by B<\/strong> and use it to close the messages, but only B<\/strong> has the key to open this padlock<\/span> and, therefore, the only one who will be able to read the messages.<\/p>\n

\"\"<\/p>\n

Example of the use of asymmetric cryptography (1)<\/em><\/p>\n

We don’t need to worry about encryption algorithms, as the FlowCrypt tool already handles it for us. A detailed guide on how to install, configure and make use of this tool will be explained below.<\/p>\n

Installation Guide<\/strong><\/h2>\n

1. Add extension<\/strong><\/h3>\n

\u200bIt is important to be using the Chrome browser. The first step is to go to the official website and download and add the extension directly to the browser by clicking the green button shown in the image.<\/p>\n

\"\"<\/p>\n

FlowCrypt official website, Source: Own elaboration. <\/em><\/p>\n

It will redirect us to the Chrome Web Store page, and there we must click on “Add to Chrome”. An alert will pop up asking for confirmation if we want to add the extension to our browser, which we must accept. A few seconds later we will have the extension. Next to the profile image of the Google session we will see the icons of the extensions we have installed in the browser where FlowCrypt should appear.<\/p>\n

\"\"<\/p>\n

Browser extensions in which the FlowCrypt extension can be seen. Source: Own elaboration<\/em><\/p>\n

2. Configuration<\/strong><\/h3>\n

If we click on the icon or name of the extension, we will be redirected to a configuration page of the extension. The first step is to log in to the Google account we want to use FlowCrypt with and accept the permissions and conditions.<\/p>\n

The next step is to generate our keys. As this is the first time we do this, we do not have any private key and we must generate a new one, we will choose the first option: New Encryption Key<\/strong>. In case we already have one, we would choose the other option.<\/p>\n

\u200b\"\"<\/strong><\/h3>\n

Selection menu after Log-in. Source: Own elaboration<\/em><\/p>\n

Next you will have us create a pass phrase. It acts like a password, but it is intended to be as secure as possible, so a simple password like “passord123” will not be valid. I recommend using a password manager, such as Bitwarden or Keepass, to create and store passwords securely without having to remember them all. Do not activate the “Remember Pass Phrase” option and never save the password in an Excel, notepad, post-it…<\/p>\n

The other two options are left enabled. The configuration should be as shown in the following image. It is worth mentioning that the last option allows us to choose what type of password we want to use. Of the four offered, RSA 2048 is the one we recommend the least, as it is the shortest and the easiest to find compared to the other keys offered.<\/p>\n

\"\"<\/p>\n

Encryption-key generation and configuration. Source: Own elaboration<\/em><\/p>\n

We must not confuse this pass phrase with our private key. The pass phrase is simply a password to verify in the extension that it is us and not someone who wants to impersonate us using our private key.<\/p>\n

To check that everything has been done correctly, if we go to our Gmail we can see that on the “Compose” option there is a new option “Secure Compose” with the FlowCrypt logo. We will also have received two emails, one with information and the other with a backup of our private key.<\/p>\n

\"\"<\/p>\n

New option to send mail in Gmail. Source: Own elaboration<\/em><\/p>\n

3. Sharing the public key<\/strong><\/h3>\n

When creating an account, a public and private key has already been generated, we do not have to worry about using them to encrypt anything, all this is already done by the application. But if someone wants to send us an encrypted message, they will need our public key. To find it, go back to the FlowCrypt extension settings. You will see a drop-down menu and click on the gear that indicates configuration. A window like the one shown in the image will appear. Go to Additional Settings<\/p>\n

\"\"<\/em><\/p>\n

Configuration menu. Source: Own elaboration<\/em><\/p>\n

A window similar to the previous one will appear, but with new options. We will go to the first one, where it says Public Key. There we will be able to see our public and private key, but we are only interested in sharing the public one. We can see that there are several options. We can download it in a file and send the file, copy and paste it to the clipboard, or share the link they propose us. Don’t worry about sending this key by any unsecured communication channel, you are only sharing the public key, which as the name indicates, it’s okay, everyone can see it.<\/p>\n

\"\"<\/p>\n

Menu for copying and saving public and private keys. Source: Own elaboration<\/em><\/p>\n

4. Import public key<\/strong><\/h3>\n

In case we want to send an encrypted message to another user, we will need his public key first. We will assume that this user has already sent us his public key in a previous email. To import their key, we will go back to the Additional Settings. Once there, we will go to Contacts and then to import public key. We will see a space where we can attach the public key that we have received. Click on Show Content and if the key is correct, we will see the Gmail corresponding to that key. Once we confirm, we will be able to send encrypted emails to that email address.<\/p>\n

\"\"<\/p>\n

Menu that allows importing public keys from other users. Source: own elaboration.<\/em><\/p>\n

Once we have reached this point, we already have all the necessary configuration to use the tool correctly. We will have to import all the public keys of everyone with whom we want to exchange encrypted information.<\/p>\n

Encrypt and sign messages<\/strong><\/h2>\n

Sending encrypted messages is just as easy as sending normal messages. Go to Gmail and instead of clicking on “Compose”, click on “Secure Compose”. You will see an interface for composing an email very similar to the normal one, but with a green color. To perform the test, we will send an email to two users, one of whom we do not have his public key. The Gmails for which we do not have the public key will be grayed out, while the others will be green. We cannot send this email, since we cannot encrypt the message for one of the recipients. FlowCrypt offers the functionality to add a password, so the message will be encrypted with this password and the user (whose public key is not available) will also need it to read the message.<\/p>\n

\"\"<\/p>\n

Example of encrypted mail in which we do not have a recipient’s public key. Source: Own elaboration.<\/em><\/p>\n

If instead of encrypting the email, we only want to sign it, we must click on the drop-down menu where it says “Encrypt, Sign and Send” and select only “Sign” (deselecting the Encrypt). We can see that we can send signed messages to users whose public key we do not have.<\/p>\n

Signing an e-mail will not encrypt its contents, but it will allow the recipients to confirm that we are the owners of that signature and, therefore, also of that e-mail.<\/p>\n

Finally, e-mails that we receive and are encrypted will be automatically decrypted as long as we are logged in to the extension (by entering our pass-phrase), otherwise, three dots will appear indicating that we cannot read their contents.<\/p>\n

Bibliography<\/strong><\/h2>\n
    \n
  • (1) https:\/\/en.wikipedia.org\/wiki\/User:Davidgothberg#\/media\/File:Public_key_signing.svg<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

    It is common to find ourselves in situations where we have to send documents with sensitive information by email, or share passwords via WhatsApp or Slack. The moment this sensitive information is sent, we give up the certainty that the information remains private. We may think that by using the HTTPS communication protocol we ensure […]<\/p>\n","protected":false},"author":1211,"featured_media":12971,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[571],"tags":[],"experteses":[20],"class_list":["post-13006","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","experteses-cybersecurity-en"],"acf":[],"_links":{"self":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts\/13006","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/users\/1211"}],"replies":[{"embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/comments?post=13006"}],"version-history":[{"count":1,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts\/13006\/revisions"}],"predecessor-version":[{"id":20815,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/posts\/13006\/revisions\/20815"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/media\/12971"}],"wp:attachment":[{"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/media?parent=13006"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/categories?post=13006"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/tags?post=13006"},{"taxonomy":"experteses","embeddable":true,"href":"https:\/\/inlab.fib.upc.edu\/en\/wp-json\/wp\/v2\/experteses?post=13006"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}