diff options
| -rw-r--r-- | NEWS | 29 | ||||
| -rw-r--r-- | README | 10 | ||||
| -rw-r--r-- | configure.ac | 18 | ||||
| -rw-r--r-- | doc/gpgme.texi | 4 | ||||
| -rw-r--r-- | src/versioninfo.rc.in | 2 |
5 files changed, 45 insertions, 18 deletions
@@ -1,9 +1,30 @@ -Noteworthy changes in version 1.8.1 (unreleased) +Noteworthy changes in version 1.9.0 (2017-03-28) ------------------------------------------------ - * cpp: Support for adduid and revuid operations. + * Clarified meaning of the 'expire' parameter of gpgme_op_createkey + and gpgme_op_createsubkey. New flag to force a key without an + expiration date. + + * New function gpgme_op_keylist_from_data_start to list keys from + data objects without importing them. + + * New function gpgme_op_set_uid_flag to flag a key as primary. + + * New function gpgme_op_decrypt_ext to run decryption with special + flags. This can for example be used to unwrap keys (remove only + the encryption layer). + + * New encryption flags to wrap a key (adding an encryption layer to + an OpenPGP message) or to create anonymously encrypted messages. + + * Support for adduid and revuid operations in the C++ bindings. + + * Support for smartcard key generation in the C++ bindings. + + * Several new functions for the Python binding. + + * Many smaller bug fixes. - * cpp: Support for smartcard key generation. * Interface changes relative to the 1.8.0 release: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -56,6 +77,8 @@ Noteworthy changes in version 1.8.1 (unreleased) py: core.pubkey_algo_string NEW. py: core.addrspec_from_uid NEW. + [c=C29/A18/R0 cpp=C10/A4/R0 qt=C9/A2/R0] + Noteworthy changes in version 1.8.0 (2016-11-16) ------------------------------------------------ @@ -1,7 +1,7 @@ GPGME - GnuPG Made Easy --------------------------- - Copyright 2001-2016 g10 Code GmbH +Copyright 2001-2017 g10 Code GmbH This file is free software; as a special exception the author gives unlimited permission to copy and/or distribute it, with or without @@ -70,7 +70,7 @@ a) If you have a trusted Version of GnuPG installed, you can simply check indeed a a signature of gpgme-x.y.z.tar.gz. The key used to create this signature is either of: - 2048R/4F25E3B6 2011-01-12 [expires: 2019-12-31] + rsa2048/4F25E3B6 2011-01-12 [expires: 2019-12-31] Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6 Werner Koch (dist sig) @@ -86,10 +86,14 @@ a) If you have a trusted Version of GnuPG installed, you can simply check Key fingerprint = D238 EA65 D64C 67ED 4C30 73F2 8A86 1B1C 7EFD 60D9 Werner Koch (Release Signing Key) + rsa3072/4B092E28 2017-03-17 [expires: 2027-03-15] + Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28 + Andre Heinecke (Release Signing Key) + You may retrieve these files from the keyservers using this command gpg --recv-keys 249B39D24F25E3B6 04376F3EE0856959 \ - 2071B08A33BD3F06 8A861B1C7EFD60D9 + 2071B08A33BD3F06 8A861B1C7EFD60D9 BCEF7E294B092E28 The keys are also available at https://gnupg.org/signature_key.html and in released GnuPG tarballs in the file g10/distsigkey.gpg . diff --git a/configure.ac b/configure.ac index 2701d413..0dac6cef 100644 --- a/configure.ac +++ b/configure.ac @@ -28,8 +28,8 @@ min_automake_version="1.14" # commit and push so that the git magic is able to work. See below # for the LT versions. m4_define(mym4_version_major, [1]) -m4_define(mym4_version_minor, [8]) -m4_define(mym4_version_micro, [1]) +m4_define(mym4_version_minor, [9]) +m4_define(mym4_version_micro, [0]) # Below is m4 magic to extract and compute the revision number, the # decimalized short revision number, a beta version string, and a flag @@ -55,19 +55,19 @@ AC_INIT([gpgme],[mym4_full_version],[http://bugs.gnupg.org]) # (Interfaces added: AGE++) # (Interfaces removed/changed: AGE=0) # -LIBGPGME_LT_CURRENT=28 -LIBGPGME_LT_AGE=17 +LIBGPGME_LT_CURRENT=29 +LIBGPGME_LT_AGE=18 LIBGPGME_LT_REVISION=0 # If there is an ABI break in gpgmepp or qgpgme also bump the # version in IMPORTED_LOCATION in the GpgmeppConfig-w32.cmake.in.in -LIBGPGMEPP_LT_CURRENT=9 -LIBGPGMEPP_LT_AGE=3 +LIBGPGMEPP_LT_CURRENT=10 +LIBGPGMEPP_LT_AGE=4 LIBGPGMEPP_LT_REVISION=0 -LIBQGPGME_LT_CURRENT=8 -LIBQGPGME_LT_AGE=1 +LIBQGPGME_LT_CURRENT=9 +LIBQGPGME_LT_AGE=2 LIBQGPGME_LT_REVISION=0 # If the API is changed in an incompatible way: increment the next counter. @@ -789,7 +789,7 @@ AH_BOTTOM([ #define GPG_ERR_ENABLE_ERRNO_MACROS 1 #define CRIGHTBLURB "Copyright (C) 2000 Werner Koch\n" \ - "Copyright (C) 2001--2016 g10 Code GmbH\n" + "Copyright (C) 2001--2017 g10 Code GmbH\n" ]) diff --git a/doc/gpgme.texi b/doc/gpgme.texi index 62004aed..40423cff 100644 --- a/doc/gpgme.texi +++ b/doc/gpgme.texi @@ -14,7 +14,7 @@ @syncodeindex pg fn @copying -Copyright @copyright{} 2002--2008, 2010, 2012--2016 g10 Code GmbH. +Copyright @copyright{} 2002--2008, 2010, 2012--2017 g10 Code GmbH. @quotation Permission is granted to copy, distribute and/or modify this document @@ -3426,7 +3426,7 @@ The function @code{gpgme_op_keylist_from_data_start} initiates a key listing operation inside the context @var{ctx}. In contrast to the other key listing operation the keys are read from the supplied @var{data} and not from the local key database. The keys are also not -imported into the local ley database. The function sets everything up +imported into the local key database. The function sets everything up so that subsequent invocations of @code{gpgme_op_keylist_next} return the keys from @var{data}. diff --git a/src/versioninfo.rc.in b/src/versioninfo.rc.in index 3ce38f02..2b1cc811 100644 --- a/src/versioninfo.rc.in +++ b/src/versioninfo.rc.in @@ -39,7 +39,7 @@ BEGIN VALUE "FileDescription", "GPGME - GnuPG Made Easy\0" VALUE "FileVersion", "@LIBGPGME_LT_CURRENT@.@LIBGPGME_LT_AGE@.@LIBGPGME_LT_REVISION@.@BUILD_REVISION@\0" VALUE "InternalName", "gpgme\0" - VALUE "LegalCopyright", "Copyright � 2001-2016 g10 Code GmbH\0" + VALUE "LegalCopyright", "Copyright � 2001-2017 g10 Code GmbH\0" VALUE "LegalTrademarks", "\0" VALUE "OriginalFilename", "gpgme.dll\0" VALUE "PrivateBuild", "\0" |