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)

* GPG does return 'SC_OP_FAILURE' when a bad PIn was entered.
  (IMHO: gpg should issue something like 'BAD_PIN [args]')

* The passphrase callback is not very useful to enter a
  PIN because the serial number of the card is not provided.
  Just "OPENPGP 1" as the passphrase hint.
  (IMHO: this is a GPG problem)

* 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	* 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	* GPG does return 'SC_OP_FAILURE' when a bad PIn was entered.
12	(IMHO: gpg should issue something like 'BAD_PIN [args]')
13
14	* The passphrase callback is not very useful to enter a
15	PIN because the serial number of the card is not provided.
16	Just "OPENPGP 1" as the passphrase hint.
17	(IMHO: this is a GPG problem)
18
19	* When a revocation certificate is imported, there is no way
20	to call the user why the key has been revoked
21	(superseded, insecure, ....) and the optional text.
22
23	* The current way to send large file through pipes is OK as
24	long as the file is not too large. The limite is <100 MB.
25	Otherwise the process would take too much time and propably
26	the window/process freezes up.
27
28	* Either use gpgconf or improve the gpg config file parser.
29
30	* Check for memory leaks, espcially in cleanup cases.
31
32	* Find out why the gpgme_op_decrypt_result_t (recipients)
33	does not contain all recipients sometimes.