winpt/trunk/TODO-GPGME-PORT.txt

* Grep for 'XXX' and implement the missing code or
  replace the dummy code with real code.

* GPGME does not support 'timestamp' field yet.

* If the card is not inserted and for example gpgme_op_sign
  is called there is no real error.
  (IMHO: gpgme should care for 'CARDCTRL 5' and then return
   GPG_ERR_CARD_REMOVED)

* When a revocation certificate is imported, there is no way
  to call the user why the key has been revoked
  (superseded, insecure, ....) and the optional text.

* The current way to send large file through pipes is OK as
  long as the file is not too large. The limite is <100 MB.
  Otherwise the process would take too much time and propably
  the window/process freezes up.

* Either use gpgconf or improve the gpg config file parser.

* Check for memory leaks, espcially in cleanup cases.

* Find out why the gpgme_op_decrypt_result_t (recipients)
  does not contain all recipients sometimes.
1	twoaday	26	* Grep for 'XXX' and implement the missing code or
2			replace the dummy code with real code.
3
4			* GPGME does not support 'timestamp' field yet.
5
6			* If the card is not inserted and for example gpgme_op_sign
7			is called there is no real error.
8			(IMHO: gpgme should care for 'CARDCTRL 5' and then return
9			GPG_ERR_CARD_REMOVED)
10
11			* When a revocation certificate is imported, there is no way
12			to call the user why the key has been revoked
13			(superseded, insecure, ....) and the optional text.
14
15			* The current way to send large file through pipes is OK as
16			long as the file is not too large. The limite is <100 MB.
17			Otherwise the process would take too much time and propably
18			the window/process freezes up.
19
20			* Either use gpgconf or improve the gpg config file parser.
21
22			* Check for memory leaks, espcially in cleanup cases.
23
24			* Find out why the gpgme_op_decrypt_result_t (recipients)
25			does not contain all recipients sometimes.