BUGS AND TO DO LIST
===================

- GnuPG does not take passphrase from environment, and
  Tcl/Tk has problems with delivering it using file descriptors.
  Currently you have to enter passphrase directly in GnuPG
  shell - and therefore you must use shell with GnuPG.

- Cached key files are different between PGP and GnuPG.
  When browsed using "wrong" program, they contain garbage.
  Press "Refresh" to re-generate. I should rework this part
  anyway, because:
   a) TkPGP can (and does) read both formats
   b) Formats are so different that TkPGP can figure out
      which one it is reading
   c) Keys are stored as you see them in the listbox, with
      whitespaces, separators and such.

- Key management is a glaring omission. This, however, may be
  a laborous attempt because at this time TkPGP supports all
  popular versions of PGP (ver.2, 5 and 6) and GnuPG. Needless
  to say, they all have different key management commands.

- Related to previous paragraph: TkPGP does not specifically
  list _secret_ keys when it has to do exactly that! Right
  now TkPGP relies on assumption that you have _both_ parts
  of the key on your keyrings, and therefore you can select
  your secret key by pointing at its public component. However
  several people reported problems with that when they do not
  have their own public keys! Of course, their keyrings are
  out of order, but TkPGP should be smarter in this situation.
  Another problem with this approach is that one has to go
  through many, many public keys to find his own (secret) key.
