|
- gnupg - Now that `sshcontrol` has been deprecated, how to use gpg key . . .
The GnuPG Manual states that: This [sshcontrol] file is deprecated in favor of the quot;Use-for-ssh quot; attribute in the key files What is now the correct way to configure gpg gpg-agent to
- gnupg - gpg: decryption failed: No secret key - Information Security . . .
The steps depend on your specific environment, but checking (or creating) the pinentry-program option in ~ gnupg gpg-agent conf is a good place to start In my case (on OS X with Homebrew-installed gpg and pinentry-mac ) I had to create that file with the following contents:
- gnupg - Restored GPG keys are invisible - Information Security Stack . . .
GnuPG stores all public keys and metadata (regardless of whether or not the private part is known) in a key database This can either be an SQLite database or a GPG-specific file (called pubring kbx or pubring gpg ; the former uses the new keybox format, the latter is a legacy file)
- gnupg - Convert PGP key to X. 509? - Information Security Stack Exchange
The GnuPG software, originally developed for PGP, in recent years also supports SMIME which uses X 509 PKIX, and OpenSSH given an RSA private PGP key (which PGP and GnuPG call secret for historical reasons) you can convert it to an SMIME key and export that as PKCS8 X509 and or PKCS12 (which is a wrapper for both PKCS8 and X509)
- gnupg - GPG encryption failed - Unusable public key - Information . . .
The version of gnupg that comes with Amazon Linux is too old to support ECC cryptography If you look at the output of gpg --list-key 40BXFE61 , you can check for any pub or sub entries that have cv25519 or nistp256 in them, e g :
- gnupg - gpg decrypt without keyring - Information Security Stack Exchange
GnuPG also provides its features through libraries, especially GPGME and libgcrypt However, both seem to be useless for your purpose However, both seem to be useless for your purpose GPGME still uses keyrings, and libgcrypt is purely a cryptographic library which cannot parse GPG-created files
- gnupg - Restore GPG key after exported to a smartcard - Information . . .
GnuPG before version 2 1 cannot merge private keys, so you'd need to completely remove the key and import it again (don't forget to --edit-key the key and check whether it still has ultimate trust assigned through the trust command)
- gnupg - GPG: Why the gpg --expert --full-gen-key command does not . . .
Options 5, 6 and 12 are only available if you create a subkey with gnupg --edit-key and then addkey The options are: (5) Elgamal (encrypt only) (6) RSA (encrypt only) (12) ECC (encrypt only) So subkeys can be pure encryption keys without the signing capability
|
|
|