β¦ described a technique and provided software for configuring your MTA to encrypt all incoming email with a public PGP key. The reason I did this was to secure my mail on the server and also in my various IMAP client β¦
β¦ PGP, but most of the emails I receive aren't even PGP signed, let alone encrypted. So I've started encrypting them myself as soon as they arrive. The MTA I am using is Exim, although the encryption methodology I am β¦
β¦ out there is a problem before sending the credentials over the unencrypted connection and stops you. With Lavabit, your email client will happily send your credentials over an unencrypted connection. Not only β¦
β¦ so, I've been using a simple Perl script that I wrote called gpgit to encrypt email stored on my mail server, both incoming and outgoing. It just takes a raw email on stdin and writes the modified email to stdout. It β¦
Typical blog posts about Dropbox security concentrate on data or network encryption. I want to talk about protecting your system from Dropbox the application, as well as Dropbox the company. In this blog post I tell you β¦
β¦ signing and certifying keys, and also a single subkey responsible for encryption. Here is an example keypair I just created using "gpg --keygen", and then viewed by running: "gpg --edit-key C80ED3A9": pub β¦
β¦ insecure password to protect it. They could leak the key, eg by using unencrypted backups or copying it to an easily lost USB stick. If you give them a smart card with a pre-generated key, then they wont be able to β¦
β¦ either locked or turned off, and my keyring is protected by full disk encryption. So unless you manage to steal it whilst I'm using it and logged in, it's no use to you. However, my smartcard is never "off". If you β¦
β¦ from the DNS server you connected to is the one that it sent, and also encrypts it over that single hop. I've seen people recommend this as a technology to increase your privacy. Especially given the recent news that β¦
β¦ store your private PGP key on your mobile phone. In other words, do not encrypt/decrypt work emails on your smartphone. Rationale: Mobile phones are inherently insecure because the baseband processor on your phone β¦
β¦ a number of you use some code which I wrote (gpgit) for automatically encrypting your incoming email with your public PGP key. I just did a dist-upgrade on my mail server, (a Debian Testing box) and it broke hard. β¦
TextSecure is an Android application for sending and receiving encrypted SMS. Even if the people you're communicating with don't use it, it's still useful because it intercepts your incoming SMS and stores them β¦
β¦ If you wanted to automatically fetch my key, and encrypt something using it, you'd run: gpg --auto-key-locate pka -ear mike.cardwell@example.com GnuPG will happily download public keys from the β¦
β¦ PGP functionality to the browser. It automatically detects PGP signed/encrypted content in a page and provides the ability to decrypt/verify it. It also provides simple functionality to encrypt and sign data inside β¦
β¦ will automatically fetch the public key of mike@example.com and start encrypting with it: gpg --auto-key-locate pka -ea -r mike@example.com If you put "auto-key-locate pka" in your gpg.conf you don't even need to β¦
The Keybase extension injects its chat box into the page, so Reddit, Twitter and the others can read what you type and send messages as you. Use the app.
My small Perl script warns when a PGP master key or subkey is close to expiry. It prints nothing otherwise, so a daily cron job emails me only when needed.
After Comodo and DigiNotar, I propose certificates signed by several independent CAs, so forgery gets harder and no CA is too big to remove from browsers.
Why this site used a free CAcert certificate in 2010 despite browser warnings, why I resent paying CAs, and my hope for certificate fingerprints in DNSSEC.
If a certificate hash could be published in a DNSSEC signed zone, domain owners could prove a self-generated cert is theirs without paying a commercial CA.