diff options
author | Marcus Brinkmann <[email protected]> | 2002-02-26 23:39:58 +0000 |
---|---|---|
committer | Marcus Brinkmann <[email protected]> | 2002-02-26 23:39:58 +0000 |
commit | 31b2a458ff66a70fffe587448d60044b7127b795 (patch) | |
tree | 4b878c81bd811c278f354beb093aa4651262375b /NEWS | |
parent | 2002-02-27 Marcus Brinkmann <[email protected]> (diff) | |
download | gpgme-31b2a458ff66a70fffe587448d60044b7127b795.tar.gz gpgme-31b2a458ff66a70fffe587448d60044b7127b795.zip |
doc/
2002-02-27 Marcus Brinkmann <[email protected]>
* gpgme.texi (Encrypting a Plaintext): Document
GPGME_Invalid_Recipients.
(Error Values): Likewise.
gpgme/
2002-02-27 Marcus Brinkmann <[email protected]>
* gpgme.h: Add new error code GPGME_Invalid_Recipient.
* encrypt.c (struct encrypt_result_s): New member invalid_recipients,
rename no_recipients to no_valid_recipients.
(_gpgme_encrypt_status_handler): Include error for invalid
recipients.
* engine-gpgsm.c (gpgsm_set_recipients): Change type of first
argument to GpgsmObject. Use that to report back the status about
the recipients.
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -6,8 +6,16 @@ * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start to encrypt and sign a message in a combined operation. + * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if + some recipients have been invalid, whereas earlier versions + succeeded in this case. The plaintext is still encrypted for all valid + recipients, so the application might take this error as a hint that + the ciphertext is not usable for all requested recipients. + Information about invalid recipients is available with gpgme_get_op_info. + * Interface changes relative to the 0.3.3 release: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients gpgme_set_include_certs NEW gpgme_get_include_certs NEW gpgme_op_encrypt_sign NEW |