1
0
mirror of git://git.gnupg.org/gnupg.git synced 2024-12-22 10:19:57 +01:00
gnupg/TODO

114 lines
3.4 KiB
Plaintext
Raw Normal View History

-*- outline -*-
1998-10-18 15:21:22 +00:00
* src/base64
** Make parsing more robust
2006-10-24 14:45:34 +00:00
Currently we don't cope with overlong lines in the best way.
2006-03-21 12:48:51 +00:00
** Check that we really release the ksba reader/writer objects.
2000-10-11 17:26:49 +00:00
* sm/call-agent.c
** Some code should go into import.c
** When we allow concurrent service request in gpgsm, we
2006-10-24 14:45:34 +00:00
might want to have an agent context for each service request
(i.e. Assuan context).
* sm/certchain.c
2006-03-21 09:56:47 +00:00
** Try to keep certificate references somewhere
This will help with some of our caching code. We also need to test
2006-06-20 17:21:37 +00:00
that caching; in particular "regtp_ca_chainlen".
* sm/decrypt.c
** replace leading zero in integer hack by a cleaner solution
* sm/gpgsm.c
** mark all unimplemented commands and options.
** Implement --default-key
** support the anyPolicy semantic
* sm/keydb.c
** Check file permissions
** Check that all error code mapping is done.
** Remove the inter-module dependencies between gpgsm and keybox
2003-06-03 19:55:50 +00:00
** Add an source_of_key field
2002-06-29 14:15:02 +00:00
* agent/
** If we detect that a private key has been deleted
Bump the key event counter.
* agent/command.c
** Make sure that secure memory is used where appropriate
2002-06-29 14:15:02 +00:00
* agent/pkdecrypt.c, agent/pksign.c
** Support DSA
* Move pkcs-1 encoding into libgcrypt.
* Use a MAC to protect sensitive files.
The problem here is that we need yet another key and it is unlikely
that users are willing to remember that key too. It is possible to
do this with a smartcard, though.
* sm/export.c
** Return an error code or a status info per user ID.
* common/tlv.c
2006-10-24 14:45:34 +00:00
The parse_sexp function should not go into this file. Check whether
we can change all S-expression handling code to make use of this
function.
* scd
** Application context vs. reader slot
We have 2 concurrent method of tracking whether a reader is in use:
2008-11-11 08:22:06 +00:00
Using the session_list in command.c and the lock_table in app.c. It
would be better to do this just at one place. First we need to see
how we can support cards with multiple applications.
** Resolve fixme in do_sign of app-dinsig.
2006-03-01 11:05:47 +00:00
2008-03-26 09:20:40 +00:00
** Add a regression test to check the extkeyusage.
2007-06-15 14:27:31 +00:00
* Windows port (W32)
** Regex support is disabled
We need to adjust the test to find the regex we have anyway in
2008-02-22 15:47:18 +00:00
gpg4win. Is that regex compatible to the OpenPGP requirement?
2007-06-15 14:27:31 +00:00
* sm/
** check that we issue NO_SECKEY xxx if a -u key was not found
2006-09-22 18:15:18 +00:00
We don't. The messages returned are also wrong (recipient vs. signer).
** gpgsm_format_name2
Replace by an estream based implementation.
* jnlib/
** Try to remove all jnlib_xmalloc.
2006-08-17 18:01:25 +00:00
* g10/
** issue a NO_SECKEY xxxx if a -u key was not found.
2006-10-18 17:19:08 +00:00
2006-08-17 18:01:25 +00:00
* Extend selinux support to other modules
2008-11-11 08:22:06 +00:00
See also http://etbe.coker.com.au/2008/06/06/se-linux-support-gpg/
2006-08-17 18:01:25 +00:00
2007-05-08 13:59:41 +00:00
* UTF-8 specific TODOs
None.
* Pinpad Reader
We do not yet support P15 applications. The trivial thing using
ASCII characters will be easy to implement but the other cases need
some more work.
* Bugs
2008-11-11 08:22:06 +00:00
* Howtos
** Migrate OpenPGP keys to another system
2007-11-19 16:32:05 +00:00
* Gpg-Agent Locale
Although we pass LC_MESSAGE from gpgsm et al. to Pinentry, this has
only an effect on the stock GTK strings (e.g. "OK") and not on any
strings gpg-agent generates and passes to Pinentry. This defeats
our design goal to allow changing the locale without changing
gpg-agent's default locale (e.g. by the command updatestartuptty).
* RFC 4387: Operational Protocols: Certificate Store Access via HTTP
Do we support this?
2007-11-19 16:32:05 +00:00