Format of colon listings for list-sigs?
Werner Koch
wk at gnupg.org
Mon Feb 2 09:43:16 CET 2009
On Fri, 30 Jan 2009 09:19, ramon.loureiro at upf.edu said:
> but where is the info for --list-sigs ?
It is also in DETAILS.
Please consider to use gpgme as that library makes it much easier to
access the output of gpg. For example there is a documented structure
for key signatures (see below) and you can retrieve all information by
walking a linked list. Example code can be found in the regression test
suite.
Salam-Shalom,
Werner
/* A signature on a user ID. */
struct _gpgme_key_sig
{
struct _gpgme_key_sig *next;
/* True if the signature is a revocation signature. */
unsigned int revoked : 1;
/* True if the signature is expired. */
unsigned int expired : 1;
/* True if the signature is invalid. */
unsigned int invalid : 1;
/* True if the signature should be exported. */
unsigned int exportable : 1;
/* The public key algorithm used to create the signature. */
gpgme_pubkey_algo_t pubkey_algo;
/* The key ID of key used to create the signature. */
char *keyid;
/* The creation timestamp, -1 if invalid, 0 if not available. */
long int timestamp;
/* The expiration timestamp, 0 if the subkey does not expire. */
long int expires;
/* Same as in gpgme_signature_t. */
gpgme_error_t status;
/* The user ID string. */
char *uid;
/* The name part of the user ID. */
char *name;
/* The email part of the user ID. */
char *email;
/* The comment part of the user ID. */
char *comment;
/* Crypto backend specific signature class. */
unsigned int sig_class;
/* Notation data and policy URLs. */
gpgme_sig_notation_t notations;
};
typedef struct _gpgme_key_sig *gpgme_key_sig_t;
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
More information about the Gnupg-users
mailing list