2 ** GpgmePassphraseCb should have void **R_HD, not void *R_HD.
3 ** trustlist has the same start/end problem as keylist had.
4 In fact, all the _start functions have this problem!
5 In addition, the resulting error of the operation can not be
6 retrieved seperately; the op_foobar operations can't be implemented
7 by the user, they are not merely convenience, but necessity, while
8 the op_foobar_start functions for these are unusable (or render the
9 context unusable, your choice).
10 ** string representation of non-secret keys and ATTR_IS_SECRET is NULL,
11 which can not be differentiated from the case that it is not
13 ** Agree on gpgme_key_unref or gpgme_key_release and drop the other?
14 ** keylisting mode can go
15 ** api to specify where to search, lokal and/or remote.
17 * Implement posix-sema.c
19 * Allow to use GTK's main loop instead of the select stuff in
22 * add locking to the key cache?
24 * Should --delete silently delete secret keys or is there a need for
25 another flag or a callback?
27 * GpgmeKey misses GPGME_ATTR_EXPIRE attribute
29 * Add ATTR to return the number of subkeys or uids.
31 * Return GPGME_Canceled when appropriate
33 * Factor out common code in _op_*_start functions.
36 ** Add note about GPGME clearing out pointer return values.
40 ** Move code common to all engines up from gpg to engine.
41 ** engine operations can return General Error on unknown protocol
42 (it's an internal error, as select_protocol checks already).
45 ** Import, export status handler.
48 ** Map ASSUAN error values.
49 ** Map GpgSM ERR messages.
50 ** Verify (and document) if Read_Error, Write_Error, Pipe_Error set errno.
54 *** Test gpgme_data_release_and_get_mem.
55 *** Test gpgme_data_rewind for invalid types.
56 *** Test gpgme_data_read's readable feature.
59 ** Make sure everything is cleaned correctly (esp. test area).
61 Bugs reported by Stephane Corthesy:
62 > - When returning a GpgmeKey GPGME_ATTR_COMMENT attribute, characters
63 > like ":" are not un-escaped, they are returned as \x3a
65 > BTW, here's another bug: it it not possible to retrieve fingerprints
68 > In GpgmeRecipients, would it be possible to provide a function which
69 > would return the validity assigned to a name contained in the
70 > GpgmeRecipients instance?
72 > - There is an inconsistent behaviour: if we pass three times an
73 > invalid (but non empty) passphrase, return code is GPGME_No_Data, but
74 > if we pass three times an empty (and invalid) passphrase, we get
75 > GPGME_No_Passphrase.
77 > passphrase callback. If I use the same GpgmeContext as the one which
78 > is currently asking for a passphrase, my app crashes: the r_hd in
80 > callback has become invalid; if I use a brand new one, the callback
81 > is called recursively, when I ask to enumerate keys.
83 > Talking about gpgme performances: did anyone make some profiling on
84 > gpgme calls and can tell me why it takes so long to enumerate the
85 > whole pubring? Listing keys with gpg is very fast, whereas with
86 > gpgme_op_keylist_XXX() it's soooooo slow.