New answers tagged gpg
The "problem" is, that gpg writes directly to the TTY instead of STDOUT or STDERR. That means it cannot be redirected. You can either use the --batch option as daniel suggested, but as a more general approach you can use the script tool, which fakes a TTY. Any output is then sent to STDOUT, so you can redirect it to /dev/null: script -c 'echo ...
Add the --batch option. If you would like to achieve the same result through redirection you would have to close STDIN through: gpg … <&-
You can copy ~/.gnupg/trustdb.gpg from one machine to another. You can also export the ownertrust values (which are the ones that matter) and import them on the new machine: gpg --export-ownertrust > otrust.txt rm ~/.gnupg/trustdb.gpg gpg --import-ownertrust < otrust.txt See the gpg manpage for details (although the version on the website doesn't ...
GPG itself acts on one file at a time. Acting on directories is not its job. Packing directories into single objects is the job of an archiver. Thus it is perfectly natural to create an archive (e.g. with tar) and call gnupg on it if you want to encrypt it. Alternatively, you can encrypt each file individually. If you're only worried about file contents, ...
Is this an elegant and secure way of encrypting directories? Elegant -- no. Secure -- as secure as gpg. Am I using GPG's full cryptographic power? Yes. Are there better alternatives? tar the directory first instead of zip. gpg compresses data anyway.
Because some functions are not working directly with gpgme interface. For example, the following functions aren't working in my environment: ^K extract-keys <Esc>k mail-key when all the basic key functions are working with gpgme.
What I've managed to find out. Correct me if I'm wrong. There are public and private keys, they go in pairs. There are primary keys and each primary key can have one or more subkeys. By default, when you generate a key, you get four keys ((1) RSA and RSA (default)). One keypair for signing and certification (primary keys) and one keypair for encryption ...
Since you're installing in non-standard locations, you'll need to tell each configure script where to find things. ./configure --help should give an indication of the appropriate option; for libgcrypt you'd run ./configure --prefix=/local/gpg2 --with-libgpg-error-prefix=/local/gpg2 Except that because of a bug in libgcrypt's configure script, only ...
Top 50 recent answers are included