From 3c9959368e0099af4ef8c27953d7fc3c3d4cea29 Mon Sep 17 00:00:00 2001 From: Marcus Brinkmann Date: Sun, 3 Mar 2002 17:37:34 +0000 Subject: doc/ 2002-03-03 Marcus Brinkmann * gpgme.texi (Information About Keys): Document GPGME_ATTR_EXPIRE. gpgme/ 2002-03-03 Marcus Brinkmann * passphrase.c (_gpgme_passphrase_status_handler): Also set the error No_Passphrase if only a bad passphrase was provided. --- TODO | 6 ------ 1 file changed, 6 deletions(-) (limited to 'TODO') diff --git a/TODO b/TODO index 8970c399..0e1752c8 100644 --- a/TODO +++ b/TODO @@ -10,8 +10,6 @@ Hey Emacs, this is -*- outline -*- mode! * add locking to the key cache? -* GpgmeKey misses GPGME_ATTR_EXPIRE attribute - * Documentation ** Add note about GPGME clearing out pointer return values. ** validity/trust @@ -38,10 +36,6 @@ Hey Emacs, this is -*- outline -*- mode! * Error Values ** Map ASSUAN/GpgSM ERR error values in a better way than is done now. ** Verify (and document) if Read_Error, Write_Error, Pipe_Error set errno. -** "There is an inconsistent behaviour: if we pass three times an - invalid (but non empty) passphrase, return code is GPGME_No_Data, - but if we pass three times an empty (and invalid) passphrase, we - get GPGME_No_Passphrase." Bug reported by Stephane Corthesy. * Tests ** Write a fake gpg-agent so that we can supply known passphrases to -- cgit v1.2.3