paxdiscount.blogg.se

I specified the subkey by fingerprint but gpg interpreted the command as if I had specified my primary key instead. I tried using batch mode as well: $ gpg -batch -yes -delete-secret-keys 9CAE802DA78E4624BD8F88FE20AA2F4F7A28CD01 (as controlled by gpg-agent) is only used for the given OpenPGP public key. This extra pre-caution is done because gpg can’t be sure that the secret key The option -yes can be used to advice gpg-agent not to request a confirmation.

In batch mode the key must be specified by fingerprint. $ gpg -delete-secret-keys 9CAE802DA78E4624BD8F88FE20AA2F4F7A28CD01Įven though I specified the subkey by fingerprint, gpg asks me to confirm the deletion of the primary key. Gpg: key 0xA52099E0E7EB77A5 marked as ultimately trusted

I was able to reproduce my mistake with the following commands: $ gpg -batch -passphrase '' -quick-generate-key 'test key' rsa4096 cert 0 I tried to use gpg -delete-secret-keys to delete some revoked subkeys but ended up accidentally deleting my primary key instead.