Public Key Encryption

Because I solved the issue I was having with Thunderbird, I’m ready to publish my public key for all and sundry to use.

What does this mean? Well, from now on the emails you receive from me will be digitally signed and with the public key listed below you can confirm that they are from me1. Do I suspect that I’m being the target of multiple email address stealing thieves? No, but I’d rather start now than later when it becomes an issue. Insurance is something you purchase before you need it.

It also means that anyone who goes through the trouble (and it is a bit of trouble, no matter what the websites say) to set up encryption on their email will be able to exchange fully encrypted emails with me. Do I suspect that some nefarious group is snooping on my emails? No (although my company explicitly says they have that right, as does my ISP, as does the NSA, FBI, law enforcement…), but I’d rather keep my private conversations private, from anyone. As it is right now, your emails flying around the ether are open for snooping by anybody who really wants to. Sure, innocent people have nothing to fear, but we shouldn’t tacitly agree to the snooping. I am not. I want to spread the encryption meme about and make it that much more difficult to access my communications.

Join me in making it more difficult for the government, or anyone else for that matter, to monitor us. I promise that in the next few weeks, I’ll post a how-to for setting up public key encryption using Mozilla Thunderbird and GnuPG. There was a learning curve for me because most of the tutorials were written by and for people who spend a lot of time in front of a command line interface. I think there’s a market for a how-to that’s a bit more explicit.


1This requires software. You don’t just check that public key against my email. As I say in paragraph three of this post, this is a bit of trouble to set up, but relatively seamless once it is


Check over there to your right for my public key.

This entry was posted in encryption. Bookmark the permalink.

8 Responses to Public Key Encryption

  1. Chris says:

    Of course how do I know that the post above is really from the person I think it is? What if this is the Public Key of some other yahoo named Bill Ruhsam?

    As a reasonably computer saavy person, I found the Thunderbird, GnuPG, Enigmail setup to be quite painless. I just wish Outlook had a reasonably effective equivalent. The only one I could find is either 3 years old and badly implemented or costs $$$. I guess I’ll have to manually decrypt anything you send to me at work.

  2. James Cronen says:

    I was running Enigmail with the old Mozilla mail client something like five years ago, and it was a pain in the ass.

    I agree that it’s better to snatch back your privacy earlier rather than later, so I’ll help spread the meme. But first, I anxiously await your tutorial. Hopefully you had a much easier time of it than I did five years ago.

  3. Rachel says:

    Bill, I think you’ve got some odd character encoding going on. Can you post this in a plain text block or something?

  4. Bill Ruhsam says:

    Rachel: Yeah. I’ve learned another few things since this post, including that i can’t just copy/paste the PGP public key block. My blog software apparently takes the —–BEGIN PUBLIC KEY—– and changes it to — –BEGIN PUBLIC KEY— – which doesn’t work as well.

    Jim: Engimail is practically seamless in my experience now. Once you do the initial settings and setup your keys, I hardly notice it’s there. I haven’t tried multiple person key management yet, though.

    Chris: Outlook uses S/MIME and doesn’t support GnuPG. I understand that there are ways that I can work around that from the non-outlook end, but what it means for the Outlook user is that you’d have to get a Certificate either from a certificate authority (there are free ones available) or that your company might give you one. There are all sorts of issues dealing with corporate mail encryption. Way too many to deal with in a comment.

  5. Pingback: Email Security by Schierer Space

  6. Pingback: Email Security: Why? by Schierer Space

  7. Pingback: The Evil Eyebrow » Email Encryption How To (not Why)

  8. Pingback: The Evil Eyebrow » Wikileaks, First Amendment, Espionage, Information Security

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>