$Id: TODO,v 1.4 2005/12/09 23:04:47 droggo Exp $

Please submit any bug or comment to droggo@gmail.com.

0.1 version
-----------

+ Add RSA signing support.

+ Comprehensive testing of packet parsing (src/data-security/packet.c). For
  example, test bpg behavior when it receives an unexpected packet, etc.

+ Optimization/refactorization of the error handling system
  (src/data-security/error.c).

+ Rewrite bpg_ruby(3).

+ Integrate bpg_ruby wrapper with the installation (i.e. build libbpg_ruby.so
  instead of bpg_ruby.so). Is this the right way to build a library to extend
  Ruby scripts?.

+ Analyse code security. Some code was written too fast, and its security is
  not yet studied. This is crucial to have a stable version. Any expert out
  there?

+ Refactor src/data-security/packet.c to behave as a coherent and robust packet
  parser.

+ Design revision by extern developers. Do you like the design? Why/why not?
  Are three libraries too much? Or too few? Do you consider that trust should
  be a part of key management? Tell us your arguments.

+ Clean the CVS tree: remove empty directories and move src/data-security to
  src/bpg.

+ Write a decent build framework, with fancy Makefile's and configure's and so
  on.

+ Add ASCII-armor support (src/data-security/armor.c).

+ Add compression support.

Long-term issues
----------------

+ Complete packet parsing, adding the data structures and read/write functions
  for the OpenPGP Packet Types not yet implemented.

+ Write key management library, user interface and man pages.

+ Write trust library, user interface and man pages.

+ Add Python wrapper for data security library.

+ Refactor the code until it's so fancy, clean, stable and elegant that we can
  move it into the NetBSD source code :-).