On Wed, 2013-10-16 at 15:44 -0400, Antoine Beaupré wrote: > On 2013-10-16 15:28:46, Philip Jägenstedt wrote: > > I looks to me --with-colons will show both revocation of the public keys > > and uids, e.g. here's my old revoked key: > > > > pub:r:1024:17:C8D53F30F42163A4:2006-08-25:::-:Philip Jägenstedt > > <phi...@foolip.org>::sca: > > uid:r::::2008-06-30::FB9A4CAE39D8CE6BADFFF3E7D87D69568335E1FD::Philip > > Jägenstedt <phil...@opera.com>: > > sub:r:1024:16:2D587BA5340611CA:2006-08-25::::::e: > > That looks like the --list-keys output, not --list-secret-keys.
Indeed it is. > > It's true that --list-secret-keys --with-colons doesn't show which uids > > are revoked, but I don't think that's relevant when trying to determine > > (programatically) whether or not the key/uid is revoked/expired. > > So yes, it's possible to extract that information, but that would > involve re-running --list-keys for every secret key imported, really > annoying. I don't understand, why is --list-secret-keys involved at all when inspecting the key you're signing? Signing your own keys using monkeysign sounds a bit weird, is that supported? Philip
signature.asc
Description: This is a digitally signed message part
