On 05/05/15 09:41, Werner Koch wrote:
> Note that GnuPG 2.1 generates revocation certificates by default.
Great! Good to know!
> The idea is that you should be able to tell the reason for the
> revocation.
Yes of course, this makes perfect sense. There is however the fact that
good practice guides now a days often advice to generate a preemptive
revocation certificate at the time of creation of the key. So at that
moment the reason is well... not really relevant. So it's great that 2.1
does this on keypair generation.
> You need to use this command
>
> gpg --command-fd 0 --status-fd 2 --gen-revoke 0x12345678
>
> and act upon the GET_* status lines.
Great, thanks!
This hack seems to have worked though (in python), but your suggestion
seems more robust:
import pexpect
cmd = "gpg --homedir {0} --gen-revoke {1}".format(KEYRING_DIR,
'0xDEADD00D')
px = pexpect.spawn(cmd, timeout=5)
px.expect("(y/N)")
px.sendline("y")
px.expect("Your decision?")
px.sendline('0')
px.expect("> ")
px.sendline("\n")
px.sendline("\n")
px.expect("Is this okay?")
px.sendline("y")
px.expect(pexpect.EOF)
bidx = px.before.index('-----BEGIN PGP PUBLIC KEY BLOCK-----')
eidx = px.before.index('-----END PGP PUBLIC KEY BLOCK-----')
eidx += len('-----END PGP PUBLIC KEY BLOCK-----')
print px.before[bidx:eidx]
Salud,
Luis.
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
