Quote from: Oompaloompa on July 16, 2012, 08:05 pmHad a little test of this now, I can encrypt/decrypt stuff with my own key but unlike gpg4win it seems like you can only encrypt something for one other key/recipient rather than multiple recipients & I can't select myself & another as recipient. Is that the case? The place to set this is within GPG's configuration for this account (this is one of the reasons I recommended creating a different Ubuntu user account for your SR usage).In your home directory there will be a hidden directory called ~/.gnupg/ which contains your public keyring, your secret keyring and your gpg.conf file. Make a copy of the ~/.gnupg/gpg.conf file as a backup (it's always good to have one) and then open gpg.conf in your preferred text editor (e.g. Nano, Vim, Emacs or whatever - Nano is the easiest to use).You will want to set the "default-key" to the short key ID for your key. The option to automatically encrypt everything to yourself is a couple of paragraphs down with the "encrypt-to" option, set that with the same key ID as for "default-key" option. Do not use any of the "default-recipient" options, they won't achieve the result you want for SR.GPG also has the facility to set groups of keys so that a name to a collection of keys in the gpg.conf file to encrypt to multiple recipients (or it can be done on the command line by invoking "-r" or "-R" multiple times). A group specified in this way should be able to be identified and used by any frontend (which are just passing your mouse clicks to the corresponding command line options). That said, it might be better to play around with multiple frontends and see which one(s) best fits your needs.Quote from: Oompaloompa on July 16, 2012, 08:05 pmAlso it doesn't seem to give any notification that clicking sign files actually does anything so I'm not sure if it does or not, presume I need to sign before encrypting?You can sign and encrypt simultaneously and that's what usually happens with email (e.g. with Enigmail in Thunderbird). Some systems will clearsign a message first and then encrypt that (e.g. Hushmail), but that is not the majority.There are also multiple forms of signing, mainly differentiated by whether there is a separate file containing the signature or whether that is included in the original message (that's what "--clearsign" produces). So it depends on which method the frontend is using.