From 02a1dbee30e990b25dae67fe3406dbac1463f509 Mon Sep 17 00:00:00 2001 From: Marcus Brinkmann Date: Thu, 28 Apr 2005 16:11:34 +0000 Subject: doc/ 2005-04-28 Marcus Brinkmann * gpgme.texi (Included Certificates): Document GPGME_INCLUDE_CERTS_DEFAULT. gpgme/ 2005-04-28 Marcus Brinkmann * gpgme.h (GPGME_INCLUDE_CERTS_DEFAULT): New macro. * engine-gpgsm.c (gpgsm_sign): Send the include-certs option after the reset, just for cleanliness, and do not sent it at all if the default is requested. * gpgme.c (gpgme_set_include_certs): Allow to use GPGME_INCLUDE_CERTS_DEFAULT. --- NEWS | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'NEWS') diff --git a/NEWS b/NEWS index 221ec476..431b1e19 100644 --- a/NEWS +++ b/NEWS @@ -4,10 +4,21 @@ Noteworthy changes in version 1.1.0 (unreleased) * You can now configure the backend engine file name and home directory to be used, as default and per context. + * Previousy, GPGME would use a default "include certs" of 1. This + has been changed. Now GPGME will use the crypto backend engines + default unless you set the value with gpgme_set_include_certs() + explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used + as a value to explicitely request the new default behaviour. + + Because the default changes, this is a slight change of the API + semantics. We consider it to be a bug fix. + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gpgme_set_engine_info NEW gpgme_ctx_get_engine_info NEW gpgme_ctx_set_engine_info NEW +gpgme_set_include_certs CHANGED DEFAULT +GPGME_INCLUDE_CERTS_DEFAULT NEW ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- cgit v1.2.3