{"id":29422,"date":"2015-03-02T20:46:35","date_gmt":"2015-03-03T01:46:35","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/how-to-keep-your-email-private-with-pgp-encryption-on-your-mac.php"},"modified":"2015-03-02T20:46:35","modified_gmt":"2015-03-03T01:46:35","slug":"how-to-keep-your-email-private-with-pgp-encryption-on-your-mac","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/how-to-keep-your-email-private-with-pgp-encryption-on-your-mac.php","title":{"rendered":"How to keep your email private with PGP encryption on your Mac"},"content":{"rendered":"<p><p>    In     our last episode of Private I, I explained the basics of    public-key (PK) cryptography, a way to scramble messages in a    way that only someone possessing a particular key can decrypt,    without that key ever having to be publicly disclosed or    shared. Its an effective system that has no known theoretical    exploits, and currently deployed implementations are considered    robust.  <\/p>\n<p>    And to recap: The clever bit    with the public-key approach is that you have two complementary    keys, one public and one private. The public key can be freely    distributed. Anything encrypted by someone else with the public    key can only be decrypted by having access to the corresponding    private key. And a private key can be used to sign a string    of text or a document to prove mathematically that only the    private keys possessor could have signed it.  <\/p>\n<p>    But there are two missing    pieces that would let Mac, iOS, and other platforms users take    advantage of PK. The first is pragmatic: Senders and recipients    need compatible software tools or plugins, preferably    integrated into apps so that little effort is required. The    second is existential: Without pre-arrangement, such as meeting    in person or a phone call, how do you know that what purports    to be someones public key is actually that persons    key?  <\/p>\n<p>    The easiest way to solve both    problems is to use an end-to-end proprietary ecosystem, but    that gets us back, more or less, to iMessage or something    similar. Silent Circle    has one of the best options that embeds public-key    cryptography, if you can convince all the people with whom you    need to communicate to opt in. It starts at $10 per month for    unlimited text, calls, video chat, and file transfers among its    users. The services messaging and calling options received    scores of 7 out of 7 in the Electronic Frontier Foundations    secure    messaging scorecard.  <\/p>\n<p>    But most of us dont live in    a walled garden, and one of the companys founders, Phil    Zimmermann, is responsible nearly 25 years ago for turning    public-key cryptography into what he called PGP, for Pretty    Good Privacy. (How    PGP works is described in Part 1.)  <\/p>\n<p>    Composing a message in Mail    to a recipient whose key is in your local GPG Keychain, the    lock icon can be clicked to encrypt the message when    sent.  <\/p>\n<p>    PGP is available for the Mac    via GPGTools, a version of    the free software GPG (GNU Privacy Guard). It lets you build a    directory of other peoples public keys, while also letting you    carry out encryption, decryption, signing, and verifying. (PGP    is a trademark, and GPG coined to get around it, but youll    often see PGP used generically to refer to this method of using    public keys.)  <\/p>\n<p>    The EFF    has very nice step-by-step instructions for installing    GPGTools to allow it to be used directly with either Apple Mail    or Mozilla Thunderbird for email; the tools are also available    via the application Services menu wherever you can manipulate    or select text. GPGTools is currently free, but plans to charge    a very modest fee for its email plug-in at some point to help    support development costs.  <\/p>\n<p>    The sent message is shown in    the Sent mailbox as being encrypted, and has to be decrypted to    view as in this window.  <\/p>\n<p>    The EFF instructions walk you    through creating your own public\/private key in GPG Keychain.    To use GPGTools with email, your key needs to have the same    email address as the return address from which you want to send    encrypted messages. Once you have a key, you can upload a key    to a keyserver by selecting your key and choosing Key > Send    Public Key to Keyserver. This makes your key searchable by your    name and email address in a PGP directory. A key has an    associated fingerprint, a cryptographic transformation of the    public key thats far shorter, which Ill get to in a    moment.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Original post:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.macworld.com\/article\/2890537\/how-to-keep-your-email-private-with-pgp-encryption-on-your-mac.html\/RK=0\/RS=4BBkixYpYY5G8fzKOiWexfHoy0c-\" title=\"How to keep your email private with PGP encryption on your Mac\">How to keep your email private with PGP encryption on your Mac<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> In our last episode of Private I, I explained the basics of public-key (PK) cryptography, a way to scramble messages in a way that only someone possessing a particular key can decrypt, without that key ever having to be publicly disclosed or shared. Its an effective system that has no known theoretical exploits, and currently deployed implementations are considered robust. And to recap: The clever bit with the public-key approach is that you have two complementary keys, one public and one private<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1600],"tags":[],"class_list":["post-29422","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29422"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=29422"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29422\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=29422"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=29422"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=29422"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}