Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

PGP & GPG

Posted by samzenpus on Mon Jun 26, 2006 03:07 PM
from the lock-it-up dept.
Ben Rothke writes "PGP (Pretty Good Privacy), as most Slashdot readers know, is one of the most popular software encryption programs ever. It is so good and so effective that in the early 1990s the FBI launched a multi-year investigation against Phil Zimmerman, the creator of PGP, for possible violation of federal export laws, especially ITAR (International Traffic in Arms Regulation). After many years of investigation, the FBI ultimately dropped its case against Zimmerman. Even though PGP is synonymous with end-user encryption, there have only been a few books written on the subject. Jump to 2006, and PGP & GPG: Email for the Practical Paranoid is a welcome title." Read the rest of Ben's review.


On page 167 in Appendix A of the book, the author candidly writes that PGP "comes with a very good and complete manual at over 300 pages". With that, one may question why one would spend $24.95 on a book which covers much of the same information as the bundled documentation.

The reality is that there is a large class of people that will simply not read any form of documentation. Rather, they prefer something with an ISBN number. Such people are a boon to authors (of which I am one) and publishers. For that group, PGP & GPG: Email for the Practical Paranoid provides a pretty good overview of how to use PGP.

The book is written for an end-user who, while comfortable with the workings of technology, is new to the sometimes strange world of public key cryptography. The author writes in an easy-to-read style and, through repetition, inculcates the principal ideas of encryption and cryptography to the reader.

The introduction and first chapter provide a good presentation of the concepts of encryption, cryptography and public-key cryptography. The idea of public-key cryptography, on which PGP is based, is not so intuitive, and many people struggle with the basic concepts. The first chapter, appropriately titled 'Cryptography Kindergarten' is a good read for those who are public-key cryptography challenged.

On a side note, the notion that even smart end-users can be intimidated by public key cryptography was detailed in a now seminal research paper 'Why Johnny Can't Encrypt: A Usability Evaluation of PGP 5.0.'

The premise of the paper is that user errors cause or contribute to most computer security failures, yet user interfaces for security still tend to be clumsy, confusing, or near-nonexistent. The authors argue that effective security requires a different usability standard, and that it will not be achieved through the user interface design techniques appropriate to other types of consumer software. The authors conclude that PGP 5.0 is not usable enough to provide effective security for most computer users despite its attractive graphical user interface. Even though PGP is in version 9.x, it still suffers from usability flaws.

Cryptography purists may recoil when the author repeatedly uses the term 'military-grade encryption.' Military-grade encryption and military-grade cryptography are overused terms, most often by marketing departments, but there is no real definition of 'military-grade encryption' -- and even if there were, it would be classified. Most people use 'military-grade encryption' to mean really strong crypto, much like those who use the term 'Olympic-size swimming pool' to refer to a really large pool. But the term 'military-grade encryption' is so misused by so many people that it is a lost cause to try to fight it.

In the rest of the book, chapters 2 - 11, the author details the varied usages of PGP & GPG. The book also details the differences between OpenPGP, PGP and GPG.
The difference between them is that PGP is a commercial piece of software, GPG (Gnu Privacy Guard) is open source, and OpenPGP is a protocol that defines a standard format for encrypted messages, signatures, and certificates for exchanging public keys.

The author astutely writes that while PGP provides really strong security, this is only if, and this is a huge if, it is implemented correctly. Chapter 11 notes that although OpenPGP provides a reliable method of authentication and encryption, it is also not unbreakable. OpenPGP can be vulnerable to many different types of attacks and weaknesses, including poor implementation, hardware or software compromise, fake keys and more. It is important to realize that OpenPGP provides significant, but not unbreakable security.

At 180 pages and priced at $24.95, PGP & GPG: Email for the Practical Paranoid is an excellent book that shows the end-user in an easy to read and often entertaining style just about everything they need to know to effectively and properly use PGP and OpenPGP.

For those that want to save money and perhaps save a few trees, the free documentation that comes along with the product is similarly worth reading.


You can purchase PGP & GPG: Email for the Practical Paranoid from bn.com.

Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by neonprimetime (528653) on Monday June 26 2006, @03:10PM (#15608143)
    The first chapter, appropriately titled 'Cryptography Kindergarten' is a good read for those who are public-key cryptography challenged.

    So basically 99.9% of users online today.
    • This is currently modded funny, but I'm not sure why.

      So basically 99.9% of users online today.

      You're missing at least one 9, I figure. If there are a billion folks [more or less] online...
      1,000,000,000; 1 in 1000 would mean that 1,000,000 people online have more than a notion of how public-key cryptography works.

      I guess I could believe that there are 10K or more, but I certainly think there are fewer than 100K.
      • What level of understanding are we talking here? I understand how public/private key encryption works well enough to use it securely, and it's not that hard to grasp. I imagine a significant portion of Slashdotters understand it as well. With almost 1,000,000 accounts, if only one in ten of us got it, there's your 100K.

        Now if you mean understand as in "could create a secure public key algorithm," then OK, I see your point.

  • by Anonymous Coward on Monday June 26 2006, @03:11PM (#15608162)
    (Pretty Good Privacy), as most Slashdot readers know, is one of the most popular software encryption programs ever.

    This statement may indeed be true. And yet, 98 out of 100 people on the street would have no idea what PGP is. What does that say about software encryption programs.

    No one knows, no one cares and very few have been affected by their ignorance.
    • by Rob T Firefly (844560) on Monday June 26 2006, @03:27PM (#15608276) Homepage Journal
      No one knows, no one cares and very few have been affected by their ignorance.
      I'm sure many, many people have been affected.. it's just that when they get their email read or their private files exploited, they're ignorant that it could possibly have been prevented. Someone who doesn't know how to lock their front door might still be affected by a burglary.
      • by sahuaro (524043) on Monday June 26 2006, @03:52PM (#15608464) Homepage
        Mod this poster up! The inventors of public key encryption envisioned a future where encrypting email would be as common as stuffing a letter in an envelope. Phishing would be unheard of since a digital signature would prove that the mail came from who it said it did.

        The US government, of course, didn't want this future to come about and put roadblocks in place to prevent it. So, today we have phoney email scams and unencrypted personnel data that gets scattered to the winds on unsecured government and private sector computers. Encrypt your email? Why you must be doing something illegal!

        Dennisk

    • by Zarel (900479) on Monday June 26 2006, @03:30PM (#15608296)
      And yet, 98 out of 100 people on the street would have no idea what PGP is.
      That's because nerds usually don't go out on the street. :P
    • "No one knows, no one cares and very few have been affected by their ignorance."

      So what's the problem? I always thought obscurity was a key to security...
    • (Pretty Good Privacy), as most Slashdot readers know, is one of the most popular software encryption programs ever.

      This statement may indeed be true. And yet, 98 out of 100 people on the street would have no idea what PGP is. What does that say about software encryption programs.


      So then, what does this say about Slashdot readers?
  • by Rosco P. Coltrane (209368) on Monday June 26 2006, @03:12PM (#15608171)
    PGP & GPG: Email for the Practical Paranoid

    title soon to become "PGP & GPG: encryption for the practical suspicious target of the homeland security dept."
  • Pretty Poor Privacy (Score:2, Interesting)

    by Anonymous Coward
    I can't say I ever found any PGP product good for any application. It was way too complicated and just not what was needed.

    Instead, I found my holy grail of encryption in Truecrypt (http://truecrypt.org )which simply has rocked for the longest time (I'm in no way associated with it). Its free, and as far as I'm concerned as far as free encryption tools go, nothing can touch it, esp if you use one of the double pass encyption methods down the list, and don't label your volumes as truecrypt volumes or keep
    • >I don't know any compgeek that uses PGP, or anyone that uses it to encrypt their mail.

      -----BEGIN PGP MESSAGE-----

      Version: PGP for Personal Privacy 6.0

      qANQR1DBwU4DA/vEixf2Zr4QB/95c5uv6mCv4yYel3qStih a bGzW7Ekfi4STPs1T CJf/fgp3S0SHUFmCgJXL4QNdkoo37wdVD/4v5xWWj7tXPfA2KQ 8bYueHIWp8QXIx TIxxRIQhw/69WXT/RAAtRBdvFPfucphQZ8xSxOc6gPlMYnPOVC PjXqXaZcZXwk8R Cv9yICy+S8ipGiGb3miPOfvqv/FAOT/uVCHv/VGrVJhDD29xfM 7TWk25LLXlbQW5 pOjgO30DNdbdhQMdsOSmQXTQdRDJDjbwQeWWk3CFZtpLmlbjXL U0hvZ7PtAGlQKh iIboJl+HM+jsEtHurqmgXR1

    • You're right - neither you nor I know anyone that openly encrypts all their mail, however that doesn't mean PGP/GPG is useless...

      Personally, if I have some data I want secured and backed up, I use duplicity, and that backs up and encrypts the data using GPG. If I want to save a note for myself somewhere, I email it to myself, encrypted. The VAST majority of my email is GPG signed so that recipients know that the mail came from me.

      It's really useful in the geek community. Trust me, have a play - it's a great
    • Apples, oranges, pears, and bananas here people. Truecrypt is a fantastic program, but how in the world would it be easier to:

      encrypt your data in a small volume and attach it as a file to who you want to send it to...

      How would they know the passphrase to open your attachment? That's the whole point of the public/private key system.
  • by ettlz (639203) on Monday June 26 2006, @03:25PM (#15608261) Homepage Journal
    There's a Public Key field in the User Preferences page on Slashdot, but does anyone know where you go to pick up other users' keys?
    • Public Key field in the User Preferences page on Slashdot

      To be honest, this field reminds me of a common situation I run into when developing ... Management supplies the ABSOLUTE MUST-HAVE fields to be put into the the SQL backend ... and so I develop the website to with that field ... and then they never use it.

      I have never seen this used on Slashdot ... and it's not mentioned in the FAQ that I could see.
    • >does anyone know where you go to pick up other users' keys?

      There are many public keyserves to search. PGP will automatically search them for unknown keys, if so configured.

  • by DarthStrydre (685032) on Monday June 26 2006, @03:26PM (#15608271)
    "Cryptography purists may recoil when the author repeatedly uses the term 'military-grade encryption.' ... there is no real definition of 'military-grade encryption' -- and even if there were, it would be classified."

    Ahem, reference http://www.nsa.gov/ia/industry/crypto_suite_b.cfm [nsa.gov]

    While Suite A is classified, Suite B, specifically AES, is specifically mentioned as being suitable for up to TOP SECRET info.

    Military grade is not a useless term, as it is therein defined.

    HOO-AH!
    • It's not really the crypto algorithm that makes military grade crypto "military grade". It's how they implement key exchange and management.
              • Perhaps there is a secret they only need to keep secure for 30 minutes, or they have an old PC. So in this case, a 40-bit cipher would be sufficient to protect their data in that case. So would that make a 40-bit cipher military-grade encryption?

                For that particular application, absolutely. And if I find myself in a similar situation, then I can safely do the same since, if the military feels that's sufficient to protect their likely-more-important data, then I probably can, too.

                Is this really that difficu
  • S/MIME (Score:5, Interesting)

    by Lord Ender (156273) on Monday June 26 2006, @03:37PM (#15608350) Homepage
    When people say "X.509" when talking about email security, what they mean is S/MIME. It is pretty clear S/MIME is going to win the battle to be the most common form of email security on the Internet. It has built-in support on Outlook, Thunderbird, hell--even mutt.

    If people CHOOSE to trust a PKI, S/MIME works WAY better than PGP because key distribution is much easier. If they don't want to do a PKI, they can still trust individual certificates, just like PGP. They can verify certificates by reading thumbprints over the phone, if they like.

    Basically, S/MIME can do everything PGP/MIME can do except the "web of trust." And WoT is just WAY too much work for 99.9% of the population. PGP will eventually vanish.
    • I agree. S/MIME, because of the relatively full-featured certificate services bundled with Windows Server 2003, and the ability to manage certificates with Active Directory, appears to have much more institutional momentum than PGP, and that will, I think, ultimately make the difference.
    • Re:S/MIME (Score:3, Insightful)

      > It is pretty clear S/MIME is going to win the battle to be the most
      > common form of email security on the Internet.

      If this is going to happen then S/MIME has yet some way to go first. Reality is that I see S/MIME only ever "used" by corporate minions. I put quote marks around "used", because I have yet to receive anything more than a signed mail. On the other hand there are ISPs and domain registrars who work with PGP - you can give them your public key and do business like that.

      Have you noticed how
  • Outlook plugin? (Score:3, Insightful)

    by haeger (85819) on Monday June 26 2006, @03:39PM (#15608361)
    I've been looking at different plugins for gpg but haven't found anything that's quite what I want. The best one I've found is something that uses the clipboard for encryption/decryption. Works OK for someone who doesn't mind a little work.
    What I'd like to see is an Outlook plugin (or OExpress) that does the following. (Please note that I wrote O/OE because they are the major players)

    * GPG included to make it easy for the user. Just one install for the whole package.
    * Automatically create keypair during installation
    * Default option to keep passphrase cached (not safe, yes I know, I know)
    * Automatically decrypt/sigcheck all incoming emails
    * Automatically encrypt/sign all outgoing mails.
    * Attach the pubkey to all outgoing mails where the address isn't in my keyring.
    * Automatically (just ask for password confirmation or something) addition of incoming pubkeys to my keyring.
    * GPL :-)
    * The people who got the pubkey would also get a link to where to download the plugin.

    I'm sure someone can expand this list quite a bit and I'm sure I forgot half of what I wanted to put on that list, but it's a start anyway.

    Anyone care to write such a plugin? Or is there one already that I don't know of?
    I do think that if there was something to that effect that you would see a spike in encrypted emails going across the globe.
    I used to encrypt/sign everything but since I was the only one using pgp/gpg it was kind of pointless.

    .haeger

    • Well, it doesn't do absolutely everything on your list but it's a pretty good start: http://www.gpg4win.org/ [gpg4win.org].

      It does the first two, and the third - it does cache passphrases for short periods of time. I don't know off the top of my head how to change the cache duration, but there should be a config option somewhere.
      Sending encrypted or signed email is just a matter of two toggles in a toolbar on every email - you should be able to change a setting somewhere so they always default to on (right now they defa
  • Just the other day I saw the following on the website of an author selling her own book directly:

    Emailing Credit Card Numbers To email your credit card number, we suggest sending two emails. The first email should contain half of the credit card number and expiration date: 1234 5678 XXXX XXXX exp date: 07/XX The second email should contain the other half of the credit card number and expiration date. XXXX XXXX 3141 5926 exp date: XX/05

    Sigh...

    • Add to that the number of web sites using an aging perl shopping cart system whereby half the credit card number is immediately emailed to the admin and the rest is stored as plain text on the server. Also the web sites who claim that your numbers are perfectly safe as they are using 128 bit encryption and the data is not decrypted until it reaches their [colocated, probably virtual] server. I had an argument with some previous employers when they insisted on calling their colocated RAQ3 a "secure server". I pointed out that they had never even seen the facility that it was housed in, and the private data was freely accessable using telnet, because it wasn't encrypted once ssl had done with it.

      Just as a an example, I set up a shopping cart of the type I mentioned and they thought it was the mutts nutz until I showed them that I was receiving both parts of the credit card numbers by email at a private email account. Even then I don't think they thought it was a problem. I left shortly afterwards.

      I wonder whose harvesting those numbers now...

      BTW, I deleted that shopping cart, so I am not guilty of abusing the system. It was done to prove a point. [slashdot.org]

    • Any snooping done is most likely going to be automatic, and this ensures naive snooping won't work. As long as this is not in widespread use it's going to much more secure than not doing it, and it's relativly easy to do and non-obstrusive.

      All-in-all, I think it's a practical down-to-earth simple solution. Seriously, don't laugh just because it's not technical enough for you.. So while you're busy being a tech-snon, the world will be busy getting stuff done. This works; for now.

    • that's pretty secure compared to this site

      http://www.rncca.com/ [rncca.com]

      why they have a password is beyond me when they list the password on the site?
  • For those that want to save money and perhaps save a few trees, the free documentation that comes along with the product is similarly worth reading.
    I want to save money, but I hate trees. What do you suggest I do?
    • Until Microsoft starts bundling their Certificate Services in Vista Home editions as a My-Identity-broker kind of thing, X.509 is useless for most people. X.509 is in Outlook because Outlook is the frontend for Exchange.

      GPG/PGP are asymmetric cryptosystems that don't rely on PKI infrastructure, just per-user public/private keypairs. Not enterprise friendly but they can be used to bootstrap a trusted online relationship.
    • Re:X.509 is better (Score:4, Insightful)

      by nog_lorp (896553) * on Monday June 26 2006, @03:49PM (#15608431)
      I don't think anyone with who: A) has concern for their privacy and security, and B) is in their right mind, would want to use MicroSoft's Outlook email client. (Anyone recall the Outlook exploit that was executed without even opening the email?)

      Aside from the fact that noone should use outlook, I read up a tiny bit on X.509. According to Wikipedia, X.509 uses signed certificates from CAs, meaning you have to PAY, and store your certificate with a "trusted company". Not only is this horrible for paranoids who wouldn't trust Verisign, but the US Gov. could subpoena your information from these companies, rendering your encryption useless (against the government).
      • Re:X.509 is better (Score:5, Informative)

        by amliebsch (724858) on Monday June 26 2006, @03:56PM (#15608506) Journal
        First of all, you can get free personal S/MIME email certificates from Thawte, which is a trusted CA. Second of all, you don't have to use a commercial trusted CA. You can also be your own CA and issue yourself all the certificates you want. The only catch is that outside the domain of your CA, your CA will not be a trusted CA, so you either have to establish trust in advance with other users, or live with having an untrusted certificate.
      • Re:X.509 is better (Score:5, Informative)

        by Anonymous Coward on Monday June 26 2006, @04:05PM (#15608591)
        I read up a tiny bit on X.509.

        That is obvious.

        According to Wikipedia, X.509 uses signed certificates from CAs, meaning you have to PAY,

        No, you can set up your own CA (for free) with openssl. And in fact, you don't need a CA at all. You can use your own certificates that aren't signed by anyone, just like PGP/GPG. In fact, the underlying math (public-key cryptography) is exactly the same as PGP/GPG.

        and store your certificate with a "trusted company".

        Store your certificate? Bullshit. You send the CA a certificate signing request. They sign it, and send it back to you. The certificate is useless without your private key, and the private key doesn't leave your possession. Decryption can only be done with the private key. So don't lose it.

        Not only is this horrible for paranoids who wouldn't trust Verisign,

        You don't need to trust Versign for X.509 to work. The only time you need to trust Versign (or any other CA) is to identify the cert of someone you never met. How do you know that a cert really belongs to the person? Verisign (or some other CA) signed the certificate. How do you know if a PGP key really belongs to someone you never met? Someone signed it.

        But do you trust the signer? That question occurs with certificates and PGP keys.

        but the US Gov. could subpoena your information from these companies, rendering your encryption useless (against the government).

        Even if the US Gov't seizes all of verisign's info, that won't help them break your cryptography, since the private key (see above) never left your possession and Verisign never had it.

        It's one thing to be paranoid, it's another thing to be an idiot. Understand how cryptography works before you start to rant & rave.

        Frankly, if the US Gov't really, really wants to break your encryption, they'll bug your computer, or your house, or call in the NSA, or send in the Marines.

    • Re:X.509 is better (Score:5, Insightful)

      by 1nhuman (597328) on Monday June 26 2006, @04:07PM (#15608603)
      Users much prefer the simpicity of an X.509 solution.


      The simplicity of X.509? Is completly the other way around. PGP is simple :)

      You probably never implemented a corporate PKI infrastructure. I myself love PKI (it's a freeking miracle I got married, I know) and have implemented or at least contributed in implementing several PKI's over the years. Simplicity is definitely not the first thing that comes to mind. Things like OCSP and CRL's you need to check the validity of a key, basically everything around issuing keys, key-escrow etc. it is al pretty complicated. Not nescecairly the theory, but the actual implementation and integration. Plus not to mention expensive. And don't even get me started on the legal side of it, the contracts you need, the legal requirements, webtrust etc.etc.. Brrrrrrr.

      PKI is cool, has a lot of potential etc. Put it's not simple in anyway. Microsoft may make it look simple (did I just say that?), by basically "trusting" loads of CA's defaultly but how much is that trust worth exactly? Not much in my eyes. Oke, the encryption during transit... that should be ok. But is the signer of that email really who he says he is?

      Between me, my friends and my colleguae's we use GPG. Bunch of my friends are on Mac's like me others are on Linux or BSD flavored machines. Some even use Windows. I don't even know al the plug-ins everyone uses. Hell, I don't know the name of mine. It integrated with Apple Mail and I just press the buttons etc, type in my passphrase and it works. Simple. Plus the keys I trust, I explicitly trusted by hand. Basically this kind of trust is loads better then accepting any mail certificate issued by the Verisigns of the world.

      Here is the Mac link: http://macgpg.sourceforge.net/ [sourceforge.net] . Loads of GUI GPG tools.

    • X.509 is worse (Score:4, Informative)

      Me, via IM: Hey, John, here's my GPG key. <pastes GPG key into IM window>
      John: Cool. Here's mine.

      Et voila - we can now start sending private messages back and forth (neglecting man-in-the-middle issues with the key exchange that can be trivially avoided with a single phone call or in-person meeting). Notice the missing step: neither of us paid Verisign or another CA for the privilege of saying "Hey, wanna go to lunch?" in private.

      • True, but you also have absolutely no assurances that "John on IM" is really the John his PGP key says he is, unless he's got some trusties who have signed his key, and how do you know to trust them? And same goes for him. You could always set up a face-to-face meeting to examine each other's credentials, but why not just spend the five minutes to get a free personal email certificate from Thawte?
    • X.509 is a heap a crap for a number of reasons, but top of my list is that obtaining a cert for it is such a monumental bother that it renders the whole exercise pointless. You can either pay for a cert or go a-hunting for a free cert, but either way, the CAs want everything but a stool sample before they issue you with a cert that expires in anywhwere from 60 days to a year away. If you're lucky you might find a cert that lasts longer, but all that pain and suffering gets you a cert which the CAs do not va
    • Re:paranoia? (Score:5, Insightful)

      by Ohreally_factor (593551) on Monday June 26 2006, @05:45PM (#15609292) Journal
      My guesses include:

      * They've coerced the author to build in a backdoor (a la clipper).
      * They've spent enough billions on serious hardware that they can brute-force it in a reasonable time.
      * They've got some very clever mathematician to figure out a viable attack.


      I think you can safely scratch #1, while also safely assuming #2. The trick is how timely, and how much encrypted traffic there is overall. If you or your message has been flagged as a high priority decrypt, then they're likely to throw a lot of crunch at it.

      However, if you're not flagged and more people start to use encryption, you're more likely to get lost in the noise.

      Your #3, I have no idea. I don't really have enough math knowledge to have a good grasp on the difficulties such a mathematician would face.