3 ms·
Thanks. How do you deal with the multiple copies problem? (Or is it all transparently handled by Mail.app?) Do you just not save copies of messages encrypted
by rwl 13y ago
Thanks. How do you deal with the multiple copies problem? (Or is it all transparently handled by Mail.app?) Do you just not save copies of messages encrypted with someone else's key? keep your version in a special folder? etc.
- LoganCale 13y agoGPGTools via Mail.app encrypts a single message with both keys rather than saving two copies with each encrypted to one key. When doing this via the command line interface you just need to specify each recipient when encrypting. http://stackoverflow.com/questions/597188/encryption-with-multiple-different-keys http://stackoverflow.com/questions/597188/encryption-with-mu...
- malandrew 13y agoWhat's the go to solution for doing the same on a Linux or OpenBSD box? I've been thinking of making the switch to some sort of *nix from OS X and I'd like to start on day 1 with 100% security practices. Moving to a new machine seems like the perfect way to start implementing everything in my life securely from the ground up.
- LoganCale 13y agoI've never used Enigmail with Thunderbird, but it's the commonly recommended GUI implementation for Linux. Enigmail has a setting in the preferences to "Add my own key to the recipients list", which will let you decrypt your own sent messages.
- rwl 13y agoThe advice I got on the debian-users list for this particular issue was: use the "encrypt-to" option in your ~/.gnupg/gpg.conf, e.g. for me: # encrypt to me as well encrypt-to CF6FA646 This adds your own key as one of the recipients whenever GPG encrypts a message.