1 Hey Emacs, this is -*- outline -*- mode!
4 ** string representation of non-secret keys and ATTR_IS_SECRET is NULL,
5 which can not be differentiated from the case that it is not
8 * Allow to use GTK's main loop instead of the select stuff in
11 * add locking to the key cache?
13 * GpgmeKey misses GPGME_ATTR_EXPIRE attribute
16 ** Add note about GPGME clearing out pointer return values.
21 ** Move code common to all engines up from gpg to engine.
22 ** engine operations can return General Error on unknown protocol
23 (it's an internal error, as select_protocol checks already).
26 ** Export status handler need much more work.
27 ** Import should return a useful error when one happened.
28 ** Genkey should return something more useful than General_Error.
29 ** Factor out common code in _op_*_start functions.
30 ** Add ATTR to return the number of subkeys or uids.
31 ** "When returning a GpgmeKey GPGME_ATTR_COMMENT attribute, characters
32 like ":" are not un-escaped, they are returned as \x3a" Bug
33 reported by Stephane Corthesy.
37 ** Map ASSUAN/GpgSM ERR error values in a better way than is done now.
38 ** Verify (and document) if Read_Error, Write_Error, Pipe_Error set errno.
39 ** "There is an inconsistent behaviour: if we pass three times an
40 invalid (but non empty) passphrase, return code is GPGME_No_Data,
41 but if we pass three times an empty (and invalid) passphrase, we
42 get GPGME_No_Passphrase." Bug reported by Stephane Corthesy.
46 *** Test gpgme_data_release_and_get_mem.
47 *** Test gpgme_data_rewind for invalid types.
48 *** Test gpgme_data_read's readable feature.
51 ** Make sure everything is cleaned correctly (esp. test area).
52 ** There is a spurious 4/10 tests failed in some conditions.
53 Rebuilding from scratch works around that.
55 * Architecture support
56 ** Implement posix-sema.c
58 Bugs reported by Stephane Corthesy:
59 > BTW, here's another bug: it it not possible to retrieve fingerprints
62 > In GpgmeRecipients, would it be possible to provide a function which
63 > would return the validity assigned to a name contained in the
64 > GpgmeRecipients instance?
66 > passphrase callback. If I use the same GpgmeContext as the one which
67 > is currently asking for a passphrase, my app crashes: the r_hd in
69 > callback has become invalid; if I use a brand new one, the callback
70 > is called recursively, when I ask to enumerate keys.