1 Hey Emacs, this is -*- outline -*- mode!
4 ** gpgme-config must include info about libgpg-error.
7 ** Compatibility interfaces that can be removed in future versions:
8 *** gpgme_data_new_from_filepart
9 *** gpgme_data_new_from_file
10 *** gpgme_data_new_with_read_cb
12 *** gpgme_op_import_ext
14 *** gpgme_get_sig_ulong_attr
15 *** gpgme_get_sig_string_attr
17 *** gpgme_get_sig_status
18 *** gpgme_trust_item_release
19 *** gpgme_trust_item_get_string_attr
20 *** gpgme_trust_item_get_ulong_attr
22 *** All Gpgme* typedefs.
25 ** Build thread modules for static linking (which just suck in the
26 desired symbols the hard way). !!
27 ** Ordering the libs is important, but libtool gets it wrong. Argh.
30 ** notification system
31 We need a simple notification system, probably a simple callback
32 with a string and some optional arguments. This is for example
33 required to notify an application of a changed smartcard, The
34 application can then do whatever is required. There are other
35 usages too. This notfication system should be independent of any
37 ** --learn-code support
38 This might be integrated with import. we still need to work out how
39 to learn a card when gpg and gpgsm have support for smartcards.
40 ** set_locale for thread safe and env independent locale selection.
41 ** How to terminate a pending operation? Something like gpgme_op_reset,
42 but where are you allowed to call it (think callback handlers).
43 Then gpgme_op_*list_end can go.
44 ** Might need a stat() for data objects and use it for length param to gpg.
45 ** Allow to export secret keys.
46 ** Implement support for photo ids.
47 ** New features requested by our dear users, but rejected or left for
49 *** Selecting the key ring, setting the version or comment in output.
50 Rejected because the naive implementation is engine specific, the
51 configuration is part of the engine's configuration or readily
52 worked around in a different way
53 *** Selecting the symmetric cipher.
54 *** Exchanging keys with key servers.
57 ** Document validity and trust issues.
60 ** Do not create/destroy engines, but create engine and then reset it.
61 Internally the reset operation still spawns a new engine process,
62 but this can be replaced with a reset later. Also, be very sure to
63 release everything properly at a reset and at an error. Think hard
64 about where to guarantee what (ie, what happens if start fails, are
65 the fds unregistered immediately - i think so?)
66 ** Optimize the case where a data object has an underlying fd we can pass
67 directly to the engine.
68 ** Move code common to all engines up from gpg to engine.
69 ** engine operations can return General Error on unknown protocol
70 (it's an internal error, as select_protocol checks already).
71 ** When server mode is implemented properly, more care has to be taken to
72 release all resources on error (for example to free assuan_cmd).
75 ** If no passphrase cb is installed, status handler is not run even if
76 password is required by crypto engine. !!
77 ** Export status handler need much more work. !!!
78 ** Import should return a useful error when one happened.
79 *** Import does not take notice of NODATA status report.
80 *** When GPGSM does issue IMPORT_OK status reports, make sure to check for them
81 in tests/gpgs m/t-import.c.
82 ** Genkey should return something more useful than General_Error.
83 ** Factor out common code in _op_*_start functions.
84 ** Optimize the file descriptor list, so the number of open fds is
86 ** Encryption: It should be verified that the behaviour for partially untrusted
87 recipients is correct.
88 ** When GPG issues INV_something for invalid signers, catch them.
91 ** Map ASSUAN/GpgSM ERR error values in a better way than is done now. !!
92 ** Some error values should identify the source more correctly (mostly error
93 values derived from status messages).
96 ** Write a fake gpg-agent so that we can supply known passphrases to
97 gpgsm and setup the configuration files to use the agent. Without
98 this we are testing a currently running gpg-agent which is not a
101 *** Test gpgme_data_release_and_get_mem.
102 *** Test gpgme_data_seek for invalid types.
105 ** Handle malloc and vasprintf errors. But decide first if they should be
106 ignored (and logged with 255?!), or really be assertions. !
109 ** Make sure everything is cleaned correctly (esp. test area).