1 Noteworthy changes in version 1.13.0 (2019-03-26)
2 -------------------------------------------------
4 * Support GPGME_AUDITLOG_DIAG for gpgsm. [#4426]
6 * New context flag "trust-model".
8 * Removed support for WindowsCE and Windows ME.
10 * Aligned the gpgrt-config code with our other libaries.
12 * Auto-check for all installed Python versions. [#3354]
14 * Fixed generating card key in the C++ bindings. [#4428]
16 * Fixed a segv due to bad parameters in genkey. [#4192]
18 * Fixed crash if the plaintext is ignored in a CMS verify.
20 * Fixed memleak on Windows. [T4238]
22 * Tweaked the Windows I/O code.
24 * Fixed random crashes on Windows due to closing an arbitrary
27 * Fixed a segv on Windows. [#4369]
29 * Fixed test suite problems related to dtags. [#4298]
31 * Fixed bunch of python bugs. [#4242,commit 9de1c96ac3cf]
33 * Several fixes to the Common Lisp bindings.
35 * Fixed minor bugs in gpgme-json. [#4331,#4341,#4342,#4343
37 * Require trace level 8 to dump all I/O data.
39 * The compiler must now support variadic macros.
41 * Interface changes relative to the 1.12.0 release:
42 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
43 gpgme_set_ctx_flag EXTENDED: New flag 'trust-model'.
44 cpp: Context::create NEW.
46 cpp: Subkey::isBad NEW.
47 cpp: UserID::isBad NEW.
48 cpp: UserID::Signature::isBad NEW.
49 cpp: GenCardKeyInteractor::setAlgo NEW.
51 [c=C33/A22/R0 cpp=C15/A9/R0 qt=C10/A3/R3]
53 Release-info: https://dev.gnupg.org/T4376
56 Noteworthy changes in version 1.12.0 (2018-10-08)
57 -------------------------------------------------
59 * Enhanced the JSON based interface tool gpgme-json to support Native
60 Messaging as well as new Javascript code to support the browser
61 site. See lang/js/README for details.
63 * Major overhaul of the Python language bindings documentation.
65 * Even for old versions of gpg a missing MDC will now lead to a
68 * Added context flag "auto-key-locate" to control the
69 behavior of GPGME_KEYLIST_MODE_LOCATE.
71 * New data function to create a data object from an estream.
73 * Add more interfaces to the C++ bindings.
75 * Improved error codes on decryption failure.
77 * Lots of minor fixes.
79 * Interface changes relative to the 1.11.1 release:
80 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
81 gpgme_data_new_from_estream NEW.
82 gpgme_decrypt_result_t EXTENDED: New field legacy_cipher_nomdc.
83 gpgme_set_ctx_flag EXTENDED: New flag 'ignore-mdc-error'.
84 GPGME_AUDITLOG_DEFAULT NEW.
85 GPGME_AUDITLOG_DIAG NEW.
86 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-locate'.
87 cpp: DecryptionResult::sessionKey NEW.
88 cpp: DecryptionResult::symkeyAlgo NEW.
89 cpp: DecryptionResult::isLegacyCipherNoMDC New.
90 cpp: Data::rewind NEW.
91 cpp: Context::setFlag NEW.
92 cpp: Context::getFlag NEW.
93 cpp: Context::createKeyEx NEW.
95 [c=C32/A21/R0 cpp=C14/A8/R0 qt=C10/A3/R2]
97 Release-info: https://dev.gnupg.org/T4109
100 Noteworthy changes in version 1.11.1 (2018-04-20)
101 -------------------------------------------------
103 * Fixed build problems in the 1.11.0 release.
105 * Added C++ interfaces which were planned for 1.11.0.
107 * Interface changes relative to the 1.10.0 release:
108 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
109 cpp: Key::origin NEW.
110 cpp: Key::lastUpdate NEW.
111 cpp: UserID::origin NEW.
112 cpp: UserID::lastUpdate NEW.
114 [c=C31/A20/R1 cpp=C13/A7/R0 qt=C10/A3/R2]
117 Noteworthy changes in version 1.11.0 (2018-04-18)
118 -------------------------------------------------
120 * New encryption API to support direct key specification including
121 hidden recipients option and taking keys from a file. This also
122 allows to enforce the use of a subkey.
124 * New encryption flag for the new API to enforce the use of plain
125 mail addresses (addr-spec).
127 * The import API can now tell whether v3 keys are skipped. These old
128 and basically broken keys are not anymore supported by GnuPG 2.1.
130 * The decrypt and verify API will now return the MIME flag as
131 specified by RFC-4880bis.
133 * The offline mode now has an effect on gpg by disabling all network
136 * A failed OpenPGP verification how returns the fingerprint of the
137 intended key if a recent gpg version was used for signature
140 * New tool gpgme-json as native messaging server for web browsers.
141 As of now public key encryption and decryption is supported.
142 Requires Libgpg-error 1.29.
144 * New context flag "request-origin" which has an effect when used
145 with GnuPG 2.2.6 or later.
147 * New context flag "no-symkey-cache" which has an effect when used
148 with GnuPG 2.2.7 or later.
150 * New convenience constant GPGME_KEYLIST_MODE_LOCATE.
152 * Improved the Python documentation.
154 * Fixed a potential regression with GnuPG 2.2.6 or later.
156 * Fixed a crash in the Python bindings on 32 bit platforms. [#3892]
158 * Various minor fixes.
160 * Interface changes relative to the 1.10.0 release:
161 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
162 gpgme_op_encrypt_ext NEW.
163 gpgme_op_encrypt_ext_start NEW.
164 gpgme_op_encrypt_sign_ext NEW.
165 gpgme_op_encrypt_sign_ext_start NEW.
166 GPGME_ENCRYPT_WANT_ADDRESS NEW.
167 GPGME_KEYLIST_MODE_LOCATE NEW.
168 gpgme_import_result_t EXTENDED: New field 'skipped_v3_keys'.
169 gpgme_decrypt_result_t EXTENDED: New field 'symkey_algo'.
170 gpgme_decrypt_result_t EXTENDED: New field 'is_mime'.
171 gpgme_verify_result_t EXTENDED: New field 'is_mime'.
172 cpp: Key::locate NEW.
173 cpp: Data::toString NEW.
174 cpp: ImportResult::numV3KeysSkipped NEW.
176 [c=C31/A20/R0 cpp=C12/A6/R0 qt=C10/A3/R1]
179 Noteworthy changes in version 1.10.0 (2017-12-12)
180 -------------------------------------------------
182 * Now returns more specific error codes for decryption to distinguish
183 between bad passphrase, user canceled, and no secret key.
185 * Now returns key origin information if available.
187 * Added context flag "auto-key-retrieve" to selectively enable the
188 corresponding gpg option.
190 * Added flag is_de_vs to decryption and verify results.
192 * py: Use SEEK_SET as default for data.seek.
194 * cpp: Various new APIs.
196 * Reduced spawn overhead on Linux again. Added new configure option
197 --disable-linux-getdents to disable this feature for very old
200 * Improved the Python bindings build system.
202 * Made the test suite less fragile.
204 * Interface changes relative to the 1.9.0 release:
205 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
206 gpgme_decrypt_result_t EXTENDED: New field 'is_de_vs'.
207 gpgme_signature_t EXTENDED: New field 'is_de_vs'.
209 gpgme_op_delete_ext NEW.
210 gpgme_op_delete_ext_start NEW.
211 GPGME_DELETE_ALLOW_SECRET NEW.
212 GPGME_DELETE_FORCE NEW.
213 gpgme_op_conf_dir NEW.
214 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-retrieve'.
215 cpp: DecryptionResult::isDeVs NEW.
216 cpp: Signature::isDeVs NEW.
217 cpp: EngineInfo::Version::operator> NEW.
218 cpp: Context::createKey NEW.
219 cpp: Context::startCreateKey NEW.
220 cpp: Context::createSubkey NEW.
221 cpp: Context::startCreateSubkey NEW.
223 py: DecryptResult EXTENDED: New boolean field 'is_de_vs'.
224 py: Signature EXTENDED: New boolean field 'is_de_vs'.
225 py: GpgError EXTENDED: Partial results in 'results'.
227 [c=C30/A19/R0 cpp=C11/A5/R0 qt=C10/A3/R0]
230 Noteworthy changes in version 1.9.0 (2017-03-28)
231 ------------------------------------------------
233 * Clarified meaning of the 'expire' parameter of gpgme_op_createkey
234 and gpgme_op_createsubkey. New flag to force a key without an
237 * New function gpgme_op_keylist_from_data_start to list keys from
238 data objects without importing them.
240 * New function gpgme_op_set_uid_flag to flag a key as primary.
242 * New function gpgme_op_decrypt_ext to run decryption with special
243 flags. This can for example be used to unwrap keys (remove only
244 the encryption layer).
246 * New encryption flags to wrap a key (adding an encryption layer to
247 an OpenPGP message) or to create anonymously encrypted messages.
249 * Support for adduid and revuid operations in the C++ bindings.
251 * Support for smartcard key generation in the C++ bindings.
253 * Several new functions for the Python binding.
255 * Many smaller bug fixes.
257 * Interface changes relative to the 1.8.0 release:
258 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
259 gpgme_op_createkey CHANGED: Meaning of 'expire' parameter.
260 gpgme_op_createsubkey CHANGED: Meaning of 'expire' parameter.
261 GPGME_CREATE_NOEXPIRE NEW.
262 gpgme_key_t EXTENDED: New field 'origin'.
263 gpgme_key_t EXTENDED: New field 'last_update'.
264 gpgme_subkey_t EXTENDED: New field 'is_de_vs'.
265 gpgme_user_id_t EXTENDED: New field 'origin'.
266 gpgme_user_id_t EXTENDED: New field 'last_update'.
267 gpgme_op_keylist_from_data_start NEW.
268 gpgme_op_set_uid_flag_start NEW.
269 gpgme_op_set_uid_flag NEW.
270 gpgme_op_decrypt_ext_start NEW.
271 gpgme_op_decrypt_ext NEW.
272 GPGME_ENCRYPT_THROW_KEYIDS NEW.
273 GPGME_ENCRYPT_WRAP NEW.
274 GPGME_DECRYPT_VERIFY NEW.
275 GPGME_DECRYPT_UNWRAP NEW.
276 gpgme_data_rewind UN-DEPRECATE.
277 cpp: Context::revUid(const Key&, const char*) NEW.
278 cpp: Context::startRevUid(const Key&, const char*) NEW.
279 cpp: Context::addUid(const Key&, const char*) NEW.
280 cpp: Context::startAddUid(const Key&, const char*) NEW.
281 cpp: Key::UserID::revoke() NEW.
282 cpp: Key::addUid() NEW.
283 cpp: Key::isDeVs NEW.
284 cpp: GpgGenCardKeyInteractor NEW.
285 cpp: Subkey::keyGrip NEW.
286 cpp: Subkey::isDeVs NEW.
287 cpp: Data::toKeys NEW.
288 cpp: Context::setDecryptFlags NEW.
289 cpp: Context::decrypt EXTENDED: Flags added.
290 cpp: Context::startDecrypt EXTENDED: Flags added.
291 cpp: Context::decryptAndVerify EXTENDED: Flags added.
292 cpp: Context::startCombinedDecryptionAndVerification EXTENDED: Flags.
293 cpp: Context::encryptFlags EXTENDED: New flags.
294 qt: CryptoConfig::stringValueList() NEW.
295 py: Context.__init__ EXTENDED: New keyword arg home_dir.
296 py: Context.home_dir NEW.
297 py: Context.keylist EXTENDED: New keyword arg mode.
298 py: Context.keylist EXTENDED: New keyword arg source.
299 py: Context.create_key NEW.
300 py: Context.create_subkey NEW.
301 py: Context.key_add_uid NEW.
302 py: Context.key_revoke_uid NEW.
303 py: Context.key_sign NEW.
304 py: Context.key_tofu_policy NEW.
305 py: core.pubkey_algo_string NEW.
306 py: core.addrspec_from_uid NEW.
308 [c=C29/A18/R0 cpp=C10/A4/R0 qt=C9/A2/R0]
311 Noteworthy changes in version 1.8.0 (2016-11-16)
312 ------------------------------------------------
314 * The module of the Python bindings has been renamed to 'gpg'.
316 * New interface to query current software versions.
318 * New feature to use gpg's --{show,override}session-key options.
320 * New interface to set the sender of a mail.
322 * qt: Added Distinguished Name parser from libkleo
324 * The --homedir option is now used with recent gpgconf versions.
326 * On 64 bit Windows systems gpgconf is now properly located.
328 * The internal locking functions have been replaced by libgpg-error
331 * Interface changes relative to the 1.7.1 release:
332 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
333 gpgme_set_sender NEW.
334 gpgme_get_sender NEW.
335 gpgme_op_query_swdb NEW.
336 gpgme_op_query_swdb_result NEW.
337 gpgme_query_swdb_result_t NEW.
338 gpgme_get_ctx_flag NEW.
339 gpgme_decrypt_result_t EXTENDED: New field session_key.
341 qt: DN::Attribute NEW.
342 qt: Job::context(Job*) NEW.
343 cpp: EngineInfo::Version::Version(const char*) NEW.
344 cpp: EngineInfo::Version::Version() NEW.
346 cpp: Context::setSender(const char*) NEW.
347 cpp: Context::getSender() NEW.
349 [c=C28/A17/R0 cpp=C9/A3/R0 qt=C8/A1/R0]
352 Noteworthy changes in version 1.7.1 (2016-10-18)
353 ------------------------------------------------
355 * Fixed problems with the new language bindings.
357 * New helper function gpgme_addrspec_from_uid.
359 * Use option --exit-on-status-write-error with newer gpg versions.
361 * qt: Missed API from the Qt Binding inclusion has
364 * qt: abstractimportjob.h is now installed to that
365 ImportJobs can be used again.
367 * qt: Fixed spelling error in API (startReceive).
369 * Interface changes relative to the 1.7.0 release:
370 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
371 gpgme_addrspec_from_uid NEW.
372 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
373 qt: MultiDeleteJob NEW.
374 qt: AbstractImportJob NEW.
376 cpp: Signature::key(bool, bool) NEW.
377 cpp: UserID::addrSpecFromString(const char*) NEW.
378 cpp: UserID::addrSpec() NEW.
380 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
383 Noteworthy changes in version 1.7.0 (2016-09-21)
384 ------------------------------------------------
386 * New language bindings for Python 2 and 3.
388 * New language Bindings for C++ and the Qt-Framework API.
390 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
391 key creation easier (requires GnuPG 2.1).
393 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
394 management easier (requires GnuPG 2.1).
396 * New function gpgme_op_keysign to make key signing easier (requires
399 * New function gpgme_op_interact to replace the now deprecated
400 functions gpgme_op_edit and gpgme_op_card_edit.
402 * New function gpgme_pubkey_algo_string to convert a public key
403 algorithm into a GnuPG 2.1 style string.
405 * Support for GnuPG 2.1's TOFU trust model.
407 * Notation flags are now correctly set on verify.
409 * New global flag "require-gnupg" to set a minimal gnupg version.
411 * More supported items in gpgme_get_dirinfo.
413 * New function gpgme_data_set_flag and flag "size-hint".
415 * New function gpgme_set_ctx_flag and flags "full-status" and
418 * Improved gpgme_data_identify to distinguish more file types.
420 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
421 mixed public key and symmetric encryption.
423 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
425 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
426 signed data is a valid MIME part. This is to support future GnuPG
429 * Interface changes relative to the 1.6.0 release:
430 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
431 gpgme_pubkey_algo_string NEW.
433 gpgme_set_ctx_flag NEW.
434 gpgme_data_set_flag NEW.
435 gpgme_op_createkey NEW.
436 gpgme_op_createkey_start NEW.
437 gpgme_op_createsubkey NEW.
438 gpgme_op_createsubkey_start NEW.
439 gpgme_op_adduid_start NEW.
441 gpgme_op_revuid_start NEW.
443 gpgme_op_keysign_start NEW.
444 gpgme_op_keysign NEW.
445 gpgme_op_tofu_policy_start NEW.
446 gpgme_op_tofu_policy NEW.
447 gpgme_op_interact_start NEW.
448 gpgme_op_interact NEW.
449 gpgme_interact_cb_t NEW.
450 gpgme_op_edit_start DEPRECATED.
451 gpgme_op_edit DEPRECATED.
452 gpgme_op_card_edit_start DEPRECATED.
453 gpgme_op_card_edit DEPRECATED.
454 gpgme_edit_cb_t DEPRECATED.
455 gpgme_status_code_t DEPRECATED.
456 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
457 gpgme_signature_t EXTENDED: New field key.
458 gpgme_key_t EXTENDED: New field fpr.
459 gpgme_subkey_t EXTENDED: New field keygrip.
460 gpgme_user_id_t EXTENDED: New field tofu.
461 gpgme_tofu_policy_t NEW.
462 gpgme_tofu_info_t NEW.
463 GPGME_STATUS_KEY_CONSIDERED NEW.
464 GPGME_STATUS_TOFU_USER NEW.
465 GPGME_STATUS_TOFU_STATS NEW.
466 GPGME_STATUS_TOFU_STATS_LONG NEW.
467 GPGME_STATUS_NOTATION_FLAGS NEW.
468 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
469 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
470 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
471 GPGME_DATA_ENCODING_MIME NEW.
472 GPGME_ENCRYPT_SYMMETRIC NEW.
473 GPGME_CREATE_SIGN NEW.
474 GPGME_CREATE_ENCR NEW.
475 GPGME_CREATE_CERT NEW.
476 GPGME_CREATE_AUTH NEW.
477 GPGME_CREATE_NOPASSWD NEW.
478 GPGME_CREATE_SELFSIGNED NEW.
479 GPGME_CREATE_NOSTORE NEW.
480 GPGME_CREATE_WANTPUB NEW.
481 GPGME_CREATE_WANTSEC NEW.
482 GPGME_CREATE_FORCE NEW.
483 GPGME_KEYSIGN_LOCAL NEW.
484 GPGME_KEYSIGN_LFSEP NEW.
485 GPGME_INTERACT_CARD NEW.
487 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
490 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
491 ------------------------------------------------
493 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
495 * Added gpgme_set_status_cb to allow a user to see some status
498 * Added an export mode for secret keys.
500 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
502 * The passphrase handler for the loopback mode has been improved and may
503 also be used with genkey.
505 * [w32] The standard GnuPG 2.1 install directory is now searched for
506 gpgconf.exe before a registry specified directory and the Gpg4win
509 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
512 * Interface changes relative to the 1.5.1 release:
513 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
514 gpgme_set_offline NEW.
515 gpgme_get_offline NEW.
516 gpgme_set_status_cb NEW.
517 gpgme_get_status_cb NEW.
518 GPGME_EXPORT_MODE_SECRET NEW
519 GPGME_EXPORT_MODE_RAW NEW.
520 GPGME_EXPORT_MODE_PKCS12 NEW.
523 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
524 ------------------------------------------------
526 * Fixed crash in key listings for user ids with a backslash.
528 * Fixed regression for GPGSM use with GnuPG < 2.1.
530 * Properly set signature summary for revoked OpenPGP keys.
533 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
534 ------------------------------------------------
536 * Fixed a possible crash in the debug code.
538 * Fixed building for Windows with newer versions of Mingw.
541 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
542 -------------------------------------------------------------
544 * The export key functions do now return an error if used with the
545 latest GnuPG version.
548 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
549 -------------------------------------------------------------
551 * gpgme-tool is now installed.
553 * Fix external listing for modern keyservers.
558 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
559 -------------------------------------------------------------
561 * Fixed possible overflow in gpgsm and uiserver engines.
564 * Added support for GnuPG 2.1's --with-secret option.
566 * Interface changes relative to the 1.5.0 release:
567 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
568 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
571 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
572 -------------------------------------------------------------
574 * On Unices the engine file names are not not anymore hardwired but
575 located via the envvar PATH. All options to set the name of the
576 engines for the configure run are removed.
578 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
579 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
580 is not found, GPGME looks for an engine named "gpg".
582 * New feature to use the gpgme I/O subsystem to run arbitrary
585 * New flag to use encryption without the default compression step.
587 * New function to access "gpg-conf --list-dirs"
589 * New configure option --enable-fixed-path for use by Android.
591 * Support ECC algorithms.
593 * Interface changes relative to the 1.4.3 release:
594 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
595 gpgme_get_dirinfo NEW.
596 gpgme_op_spawn_start NEW.
598 GPGME_PROTOCOL_SPAWN NEW.
599 GPGME_SPAWN_DETACHED NEW.
600 GPGME_SPAWN_ALLOW_SET_FG NEW.
601 GPGME_ENCRYPT_NO_COMPRESS NEW.
604 gpgme_subkey_t EXTENDED: New field curve.
605 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
606 GPGME_STATUS_MOUNTPOINT NEW.
607 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
608 GPGME_STATUS_ATTRIBUTE NEW.
609 GPGME_STATUS_BEGIN_SIGNING NEW.
610 GPGME_STATUS_KEY_NOT_CREATED NEW.
613 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
614 -------------------------------------------------------------
616 * The default engine names are now taken from the output of gpgconf.
617 If gpgconf is not found the use of gpg 1 is assumed.
619 * Under Windows the default engines names are first searched in the
620 installation directory of the gpgme DLL.
622 * New function gpgme_data_identify to detect the type of a message.
624 * Interface changes relative to the 1.4.2 release:
625 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
626 gpgme_signers_count NEW.
627 gpgme_data_type_t NEW.
628 gpgme_data_identify NEW.
631 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
632 -------------------------------------------------------------
634 * Allow symmetric encryption with gpgme_op_encrypt_sign.
636 * Fixed mismatching off_t definitions on Windows.
638 * Interface changes relative to the 1.4.1 release:
639 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
642 GPGME_PROTOCOL_OPENPGP NEW alias.
645 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
646 ------------------------------------------------------------
648 * Fixed reading of gpg.conf files with excessive use of the group
651 * Fixed building with the i686-w64-mingw32 toolchain.
653 * Disabled FD passing by default for Apple.
656 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
657 ------------------------------------------------------------
659 * New function gpgme_set_global_flag to help debugging on Android.
661 * New function gpgme_io_writen as a convenience wrapper around
664 * New functions to support the pinentry mode feature of GnuPG 2.1.
666 * New macro GPGME_VERSION_NUMBER to allow supporting different API
667 versions without the need for a configure test.
669 * Several improvements for gpgme-tool.
671 * Better logging of the common "invalid engine" error code.
673 * Support for FD passing is now enabled by default. The configure
674 option --disable-fd-passing may be used to disable this.
676 * Interface changes relative to the 1.3.1 release:
677 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
678 GPGME_VERSION_NUMBER NEW.
680 gpgme_set_global_flag NEW.
681 gpgme_set_pinentry_mode NEW.
682 gpgme_get_pinentry_mode NEW.
683 gpgme_pinentry_mode_t NEW.
684 GPGME_PINENTRY_MODE_DEFAULT NEW.
685 GPGME_PINENTRY_MODE_ASK NEW.
686 GPGME_PINENTRY_MODE_CANCEL NEW.
687 GPGME_PINENTRY_MODE_ERROR NEW.
688 GPGME_PINENTRY_MODE_LOOPBACK NEW.
691 Noteworthy changes in version 1.3.2 (2012-05-02)
692 ------------------------------------------------
694 * Remove support for libgpgme-pth. As far as we know, this was never used,
695 and GnuPG is going to use our own npth in the future.
697 * Fix signature summary information for a missing X.509 key.
699 * Fix parsing of dates >= year 2038.
702 Noteworthy changes in version 1.3.1 (2011-06-16)
703 ------------------------------------------------
705 * Ported to Windows CE.
707 * Detect GPG versions not supporting ---passwd.
709 * Interface changes relative to the 1.3.0 release:
710 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
711 GPGME_EXPORT_MODE_MINIMAL NEW
712 GPGME_STATUS_SUCCESS NEW
713 gpgme_err_code_from_syserror NEW
714 gpgme_err_set_errno NEW
715 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
716 gpgme_error_from_syserror NEW
717 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
720 Noteworthy changes in version 1.3.0 (2010-01-11)
721 ------------------------------------------------
723 * GPGME does not come with an internal libassuan version anymore.
724 The external libassuan 1.1.0 release or later is required. For
725 application programmers on systems that can resolve inter-library
726 dependencies at runtime, this is a transparent change.
728 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
730 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
732 * New API to change the passphrase of a key.
734 * Interface changes relative to the 1.2.0 release:
735 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
736 GPGME_STATUS_INV_SGNR NEW.
737 GPGME_STATUS_NO_SGNR NEW.
738 GPGME_PROTOCOL_G13 NEW.
739 gpgme_op_g13_mount NEW.
740 gpgme_g13_result_t NEW.
743 gpgme_op_passwd_start NEW.
745 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
748 Noteworthy changes in version 1.2.0 (2009-06-18)
749 ------------------------------------------------
751 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
754 * gpgme_new will fail if gpgme_check_version was not called, or a
755 selftest failed (for example, if -mms-bitfields was not used on
758 * New functions gpgme_io_read and gpgme_io_write for use with
759 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
761 * New functions gpgme_result_ref and gpgme_result_unref to detach
762 result structures from a context.
764 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
765 that allow to specify exported keys through gpgme_key_t objects
768 * New mode of operation gpgme_export_mode_t that allows exporting
771 * Interface changes relative to the 1.1.7 release:
772 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
773 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
774 GPGME_PROTOCOL_ASSUAN NEW.
775 gpgme_assuan_data_cb_t NEW.
776 gpgme_assuan_inquire_cb_t NEW.
777 gpgme_assuan_status_cb_t NEW.
778 gpgme_op_assuan_transact_start NEW.
779 gpgme_op_assuan_transact NEW.
780 gpgme_op_assuan_result NEW.
781 gpgme_op_import_keys NEW.
782 gpgme_op_import_keys_start NEW.
783 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
784 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
785 gpgme_check_version CHANGED: Is now a macro.
786 gpgme_new EXTENDED: More failure codes.
789 gpgme_result_ref NEW.
790 gpgme_result_unref NEW.
791 gpgme_export_mode_t NEW.
792 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
793 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
794 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
795 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
796 gpgme_op_export_keys_start NEW.
797 gpgme_op_export_keys NEW.
798 GPGME_DATA_ENCODING_URL NEW.
799 GPGME_DATA_ENCODING_URL0 NEW.
800 GPGME_DATA_ENCODING_URLESC NEW.
801 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
804 Noteworthy changes in version 1.1.8 (2008-12-08)
805 ------------------------------------------------
807 * SIGPIPE is now again ignored as described in the manual. Fixes
808 regression introduced with 1.1.6.
811 Noteworthy changes in version 1.1.7 (2008-10-17)
812 ------------------------------------------------
814 * Using GPGME_KEYLIST_MODE_LOCAL combined with
815 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
816 --locate-keys feature of gpg (>= 2.0.10).
818 * The encoding of gpgme_data_t objects can affect the output encoding
819 of export, sign and encrypt operations now (the same operations
820 that are also affected by the ASCII mode switch). We believe this
821 change in the ABI is innocent enough not to break existing
822 applications (it only affects the S/MIME backend on certain
825 * The reference manual now includes the specification of "The GnuPG
828 * A new function gpgme_cancel_async can be used to asynchronously
829 cancel any pending operation at any time, from any thread.
831 * Interface changes relative to the 1.1.6 release:
832 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
833 gpgme_op_encrypt CHANGED: Output encoding can affect result.
834 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
835 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
836 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
837 gpgme_op_sign CHANGED: Output encoding can affect result.
838 gpgme_op_sign_start CHANGED: Output encoding can affect result.
839 gpgme_op_export CHANGED: Output encoding can affect result.
840 gpgme_op_export_start CHANGED: Output encoding can affect result.
841 gpgme_op_export_ext CHANGED: Output encoding can affect result.
842 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
843 gpgme_cancel_async NEW
844 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
847 Noteworthy changes in version 1.1.6 (2008-01-04)
848 ------------------------------------------------
850 * Bug fixes for for W32.
852 * A new, experimental (and thus undocumented and potentially
853 unstable) interface for accessing gpg-conf through GPGME has been
856 * Interface changes relative to the 1.1.1 release:
857 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
858 gpgme_signature_t EXTENDED: New field chain_model.
859 gpgme_op_getauditlog_start NEW.
860 gpgme_op_getauditlog NEW.
861 GPGME_AUDITLOG_HTML NEW.
862 GPGME_AUDITLOG_WITH_HELP NEW.
863 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
866 Noteworthy changes in version 1.1.5 (2007-07-09)
867 ------------------------------------------------
869 * Bug and portability fixes (mainly for W32).
872 Noteworthy changes in version 1.1.4 (2007-03-05)
873 ------------------------------------------------
875 * Detect and bail out on double plaintext messages. This is required
876 so that applications can properly detect the signed parts of a
877 message. Actual there is now a double protection as GnuPG 1.4.7
878 will detect this case too.
881 Noteworthy changes in version 1.1.3 (2007-01-29)
882 ------------------------------------------------
884 * Fixed a memory leak in gpgme_data_release_and_get_mem.
886 * Fixed a bug in Windows command line quoting.
889 Noteworthy changes in version 1.1.2 (2006-03-02)
890 ------------------------------------------------
892 * Fixed a bug in the W32 glib backend.
895 Noteworthy changes in version 1.1.1 (2006-02-23)
896 ------------------------------------------------
898 * Fixed a bug in that the fingerprints of subkeys are not available.
900 * Clarified usage of the SECRET flag in key listings. It is now
903 * Reading signature notations and policy URLs on key signatures is
904 supported. They can be found in the new field notations of the
905 gpgme_key_sig_t structure. This has to be enabled with the keylist
906 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
908 * A new gpgme_free() function solves the problem of using different
909 allocators in a single program. This function should now be used
910 instead calling free() to release the buffer returned by
911 gpgme_data_release_and_get_mem. It is recommended that you always
912 do this, but it is only necessary on certain platforms, so backwards
913 compatibility is provided. In other words: If free() worked for
914 you before, it will keep working.
916 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
917 They are analyzed by the verify handlers and made available in the
918 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
920 * Interface changes relative to the 1.1.0 release:
921 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
922 gpgme_key_sig_t EXTENDED: New field notations.
923 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
925 GPGME_STATUS_PKA_TRUST_BAD NEW
926 GPGME_STATUS_PKA_TRUST_GOOD NEW
927 gpgme_signature_t EXTENDED: New field pka_trust.
928 gpgme_signature_t EXTENDED: New field pka_address.
929 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
932 Noteworthy changes in version 1.1.0 (2005-10-01)
933 ------------------------------------------------
935 * You can now configure the backend engine file name and home
936 directory to be used, as default and per context.
938 * Information about the recipients of an encrypted text is now
939 available at decryption time.
941 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
942 and verify handlers, the information about the plaintext filename,
943 if available is made available in the new field file_name of the
944 respective result structure.
946 * The code for "automagically detecting the thread library" has been
947 removed from libgpgme. It is deprecated since version 0.4.3.
948 Since then, you had to link against libgpgme-pthread for
949 applications using pthread and libgpgme-pth for applications using
952 The code was removed because it caused compilation problems on
953 systems where the pthread.h header from GNU Pth is available in
954 addition to the system header (FreeBSD 6 and later for example).
956 * "./autogen.sh --build-w32" does now build gpgme.dll.
958 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
959 delimiter. The standard install directory is used when locating
960 gpg or gpgsm before finally falling back to the hardwired name.
962 * There is a new flag for keys and subkeys, is_qualified, which
963 indicates if a key can be used for qualified signatures according
964 to local government regulations.
966 * You can associate a filename with a data object using the new
967 function gpgme_data_set_file_name(). This filename will be stored
968 in the output when encrypting or signing the data and will be
969 returned when decrypting or verifying the output data.
971 * You can now set notation data at signature creation with the new
972 function gpgme_sig_notation_add().
974 * Interface changes relative to the 1.0.3 release:
975 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
976 gpgme_set_engine_info NEW
977 gpgme_ctx_get_engine_info NEW
978 gpgme_ctx_set_engine_info NEW
979 gpgme_recipient_t NEW
980 gpgme_decrypt_result_t EXTENDED: New field recipients.
981 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
982 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
983 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
984 GPGME_STATUS_PLAINTEXT NEW
985 gpgme_key_t EXTENDED: New field is_qualified.
986 gpgme_subkey_t EXTENDED: New field is_qualified.
987 gpgme_data_get_file_name NEW
988 gpgme_data_set_file_name NEW
989 gpgme_sig_notation_flags_t NEW
990 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
991 GPGME_SIG_NOTATAION_CRITICAL NEW
992 gpgme_sig_notation_clear NEW
993 gpgme_sig_notation_add NEW
994 gpgme_sig_notation_get NEW
995 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
998 Noteworthy changes in version 1.0.3 (2005-06-20)
999 ------------------------------------------------
1001 * Previousy, GPGME would use a default "include certs" of 1. This
1002 has been changed. Now GPGME will use the crypto backend engines
1003 default unless you set the value with gpgme_set_include_certs()
1004 explicitly. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
1005 as a value to explicitly request the new default behaviour.
1007 Because the default changes, this is a slight change of the API
1008 semantics. We consider it to be a bug fix.
1010 * A bug which made GPGME hang has been fixed. If you have
1011 experienced hanging before, please try out this version and let me
1012 know if you still experience hanging problems.
1014 * Interface changes relative to the 0.9.0 release:
1015 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1016 gpgme_set_include_certs CHANGED DEFAULT
1017 GPGME_INCLUDE_CERTS_DEFAULT NEW
1018 GPGME_STATUS_SIG_SUBPACKET NEW
1019 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
1020 GPGME_STATUS_SC_OP_FAILURE NEW
1021 GPGME_STATUS_SC_OP_SUCCESS NEW
1022 GPGME_STATUS_CARDCTRL NEW
1023 GPGME_STATUS_BACKUP_KEY_CREATED NEW
1024 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1027 Noteworthy changes in version 1.0.2 (2004-12-28)
1028 ------------------------------------------------
1030 * Changed the license of the library to the GNU Lesser General Public
1031 License (LGPL), version 2.1 or later.
1034 Noteworthy changes in version 1.0.1 (2004-10-22)
1035 ------------------------------------------------
1040 Noteworthy changes in version 1.0.0 (2004-09-30)
1041 ------------------------------------------------
1043 * Version 1.0.0! We are proud to present you with a thoroughly
1044 tested and stable version of the GPGME library. A big Thank You!
1045 to all the people who made this possible.
1047 The development will be branched into a stable 1.x.y series and the
1050 * The gpgme.m4 macro supports checking the API version. Just prepend
1051 it to the required version string, separated by a colon. For
1052 example, this release has the version "1:1.0.0". The last release
1053 to which this version is (mostly) ABI compatible is "1:0.4.2",
1054 which is the default required version.
1057 Noteworthy changes in version 0.9.0 (2004-06-08)
1058 ------------------------------------------------
1060 * The type gpgme_key_t has now a new field keylist_mode that contains
1061 the keylist mode that was active at the time the key was retrieved.
1063 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
1064 that contains a flag indicating that the key should not have been
1065 used for encryption.
1067 * Verifying a signature of a revoked key gives the correct result now
1068 (GPG_ERR_CERT_REVOKED error code).
1070 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
1071 verify operations still allows you to look at the signature
1072 verification result.
1074 * Clarified that patterns in keylisting operations have an upper
1075 limit, and thus are not suited to list many keys at once by their
1076 fingerprint. Also improve the error message if the pattern is too
1077 long for the CMS protocol to handle.
1079 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1080 gpgme_key_t EXTENDED: New field keylist_mode.
1081 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
1082 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1085 Noteworthy changes in version 0.4.7 (2004-04-29)
1086 ------------------------------------------------
1088 * Correctly initialize the fields expired, revoked, invalid, and
1089 disabled in the gpgme_key_t structures.
1091 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
1092 accidentally of type int instead unsigned int.
1094 * Interface changes relative to the 0.4.5 release:
1095 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1096 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
1097 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1099 Noteworthy changes in version 0.4.6 (2004-04-06)
1100 ------------------------------------------------
1105 Noteworthy changes in version 0.4.5 (2004-03-07)
1106 ------------------------------------------------
1108 * GPGME is now compiled with LFS (large file support) by default.
1109 This means that _all_ programs using GPGME must be compiled with
1110 LFS support enabled by default. You can do this easily with
1111 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
1112 without autoconf by defining the preprocessor symbol
1113 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
1114 the C compiler command line, or by defining this preprocessor
1115 symbol before including any system header files). For more
1116 details, read the section on LFS in the manual.
1118 Up to now, it was undocumented that GPGME was not using LFS.
1119 But the public interfaces use off_t, and file descriptors are
1120 exchanged between the application and GPGME. This was an oversight,
1121 and bound to cause troubles in the future.
1123 Writing GPGME as a dual mode library that seamlessly supports LFS
1124 while keeping backwards compatibility is possible, but does not
1125 solve the problem: Many applications already expect GPGME to have
1126 LFS (they are compiled with off_t being a 64bit value). This is true
1127 in particular for the popular Gtk+ and Qt programs.
1129 So, although this is an ABI (but not an API) break, we will not
1130 change the library version to reflect that. Because the interfaces
1131 affected are probably not used yet in any GPGME 0.4 based
1132 application, we don't expect any real failures from this change.
1133 In fact, applications already using LFS will have some subtle bugs
1136 However, if you encounter an application using GPGME 0.4.x that
1137 does _not_ use LFS by default (off_t is a 32bit value), _and_
1138 uses at least one of the functions gpgme_data_seek,
1139 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
1140 gpgme_data_new_from_cbs, then indeed this library will be ABI
1141 incompatible with the program. As said above, we don't believe
1142 such a program exists. If we are in error, then you have two
1143 options: As a quick hack, you can configure GPGME with the
1144 --disable-largefile option. This will revert the change, and GPGME
1145 will not use LFS. However, GPGME will be incompatible with
1146 programs that expect GPGME to use LFS. All applications are
1147 required to use LFS when using GPGME, so this is only good as a
1148 temporary local work-around.
1150 The other option is to change the versioning of the library and
1151 recompile all applications. We have reserved a special version of
1152 the library for that, so you can do that without expecting a
1153 version clash in the future. Furthermore, everyone who does this
1154 will agree on the version to use (this is important for
1155 distribution makers). Read the comment in configure.ac (before
1156 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
1157 blindly: As stated above, we think it is unlikely this measure is
1158 needed. Still, it is there if necessary. If in doubt, contact us
1159 and we will give our advise for your specific situation.
1161 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
1164 * New interface gpgme_cancel() that can be used to cancel
1165 asynchronous operations.
1167 * Interface changes relative to the 0.4.4 release:
1168 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1169 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
1170 gpgme_data_seek CHANGED: off_t is now a largefile type.
1171 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
1172 GPGME_KEYLIST_MODE_VALIDATE NEW
1174 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1176 Noteworthy changes in version 0.4.4 (2004-01-12)
1177 ------------------------------------------------
1179 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
1180 been renamed to "sig_class", to avoid clash with C++ compilers. In
1181 the C API, the old name "class" has been preserved for backwards
1182 compatibility, but is deprecated.
1184 * Interface changes relative to the 0.4.3 release:
1185 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1186 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
1187 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
1188 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1190 Noteworthy changes in version 0.4.3 (2003-10-06)
1191 ------------------------------------------------
1193 * libgpgme should not be used for threaded programs anymore. This
1194 never worked reliably in all cases, because you had to
1195 be careful about the linking order and libtool wouldn't do that for
1196 you automatically. Instead, now you have to link against
1197 libgpgme-pthread for applications using pthread and libgpgme-pth for
1198 applications using GNU Pth.
1200 The old code for automagically detecting the thread library is
1201 still part of libgpgme, but it is DEPRECATED.
1203 * There are new automake macros AM_PATH_GPGME_PTH and
1204 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
1205 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
1206 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
1207 variables of course also include the configuration for the thread
1208 package itself. Alternatively, use libtool.
1210 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
1213 * gpgme-config doesn't support setting the prefix or exec prefix
1214 anymore. I don't think it ever worked correctly, and it seems to
1217 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
1218 provided was not unique, instead returning the first matching key.
1220 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
1221 that indicates if the key can be used for authentication.
1223 * gpgme_signature_t's status field is now correctly set to an error
1224 with error code GPG_ERR_NO_PUBKEY if public key is not found.
1226 * gpgme_new_signature_t's class field is now an unsigned int, rather
1227 than an unsigned long (the old class field is preserved for
1228 backwards compatibility).
1230 * A new function gpgme_set_locale() is provided to allow configuring
1231 the locale for the crypto backend. This is necessary for text
1232 terminals so that programs like the pinentry can be started with
1233 the right locale settings for the terminal the application is running
1234 on, in case the terminal has different settings than the system
1235 default (for example, if it is a remote terminal). You are highly
1236 recommended to call the following functions directly after
1237 gpgme_check_version:
1241 setlocale (LC_ALL, "");
1242 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
1243 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
1245 GPGME can not do this for you, as setlocale is not thread safe, and
1246 there is no alternative.
1248 * The signal action for SIGPIPE is now set to SIG_IGN by
1249 gpgme_check_version, instead the first time a crypto engine is
1250 started (which is not well defined).
1252 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
1253 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
1254 to CRC24RFC2440. For now, these strings can be used as the MIC
1255 parameter for PGP/MIME (if appropriately modified).
1257 * Interface changes relative to the 0.4.2 release:
1258 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1259 gpgme_strerror_t NEW
1260 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
1261 gpgme_key_t EXTENDED: New field can_authenticate.
1262 gpgme_subkey_t EXTENDED: New field can_authenticate.
1263 gpgme_new_signature_t CHANGED: New type for class field.
1264 gpgme_set_locale NEW
1265 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
1266 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1268 Noteworthy changes in version 0.4.2 (2003-07-30)
1269 ------------------------------------------------
1271 * Allow gpg-error to be in non-standard place when linking the test suite.
1273 * Configure will fail now if gpg-error can not be found.
1275 * Fixed initialized memory backed data objects for writing, which
1276 caused the test program to crash (but only on Mac OS, surprisingly).
1278 * Eliminate use of C99 constructs.
1280 * Small improvements to the manual.
1283 Noteworthy changes in version 0.4.1 (2003-06-06)
1284 ------------------------------------------------
1286 This is the release that 0.4.0 should have been. There are many
1287 interface changes, please see below for the details. The changes are
1288 sometimes the result of new functionality, but more often express a
1289 paradigm shift. Others are an overdue cleanup to get GPGME in line
1290 with the GNU coding standards and to make the interface more
1291 self-consistent. Here is an overview on the changes:
1293 All types have been renamed to conform to the GNU coding standards,
1294 most of the time by keeping the whole name in lowercase and inserting
1295 underscores between words.
1297 All operations consistently only accept input parameters in their
1298 invocation function, and return only an error code directly. Further
1299 information about the result of the operation has to be retrieved
1300 afterwards by calling one of the result functions. This unifies the
1301 synchronous and the asynchronous interface.
1303 The error values have been completely replaced by a more
1304 sophisticated model that allows GPGME to transparently and accurately
1305 report all errors from the other GnuPG components, regardless of
1306 process boundaries. This is achieved by using the library
1307 libgpg-errors, which is shared by all GnuPG components. This library
1308 is now required for GPGME.
1310 The results of all operations are now provided by pointers to C
1311 structs rather than by XML structs or in other ways.
1313 Objects which used to be opaque (for example a key) are now pointers
1314 to accessible structs, so no accessor functions are necessary.
1316 Backward compatibility is provided where it was possible without too
1317 much effort and did not collide with the overall sanitization effort.
1318 However, this is only for ease of transition. NO DEPRECATED FUNCTION
1319 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
1320 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
1321 Recommendations how to replace deprecated or removed functionality
1322 can be found within the description of each change.
1324 What follows are all changes to the interface and behaviour of GPGME
1327 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
1328 deprecated attributes will warn about use of obsolete functions and
1329 type definitions. You can suppress these warnings by passing
1330 -Wno-deprecated-declarations to the gcc command.
1332 * The following types have been renamed. The old types are still
1333 available as aliases, but they are deprecated now:
1335 GpgmeCtx gpgme_ctx_t
1336 GpgmeData gpgme_data_t
1337 GpgmeError gpgme_error_t
1338 GpgmeDataEncoding gpgme_data_encoding_t
1339 GpgmeSigStat gpgme_sig_stat_t
1340 GpgmeSigMode gpgme_sig_mode_t
1341 GpgmeAttr gpgme_attr_t
1342 GpgmeValidity gpgme_validity_t
1343 GpgmeProtocol gpgme_protocol_t
1344 GpgmeKey gpgme_key_t
1345 GpgmePassphraseCb gpgme_passphrase_cb_t
1346 GpgmeProgressCb gpgme_progress_cb_t
1347 GpgmeIOCb gpgme_io_cb_t
1348 GpgmeRegisterIOCb gpgme_register_io_cb_t
1349 GpgmeRemoveIOCb gpgme_remove_io_cb_t
1350 GpgmeEventIO gpgme_event_io_t
1351 GpgmeEventIOCb gpgme_event_io_cb_t
1352 GpgmeIOCbs gpgme_io_cbs
1353 GpgmeDataReadCb gpgme_data_read_cb_t
1354 GpgmeDataWriteCb gpgme_data_write_cb_t
1355 GpgmeDataSeekCb gpgme_data_seek_cb_t
1356 GpgmeDataReleaseCb gpgme_data_release_cb_t
1357 GpgmeDataCbs gpgme_data_cbs_t
1358 GpgmeTrustItem gpgme_trust_item_t
1359 GpgmeStatusCode gpgme_status_code_t
1361 * gpgme_error_t is now identical to gpg_error_t, the error type
1362 provided by libgpg-error. More about using libgpg-error with GPGME
1363 can be found in the manual. All error symbols have been removed!
1365 * All functions and types in libgpg-error have been wrapped in GPGME.
1366 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1367 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1368 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1369 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1372 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1374 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1375 for encrypt, sign, encrypt-sign, decrypt, verify, and
1376 decrypt-verify operations. For verify operations on detached
1377 signatures, the progress callback is invoked for both the detached
1378 signature and the plaintext message, though.
1380 * gpgme_passphrase_cb_t has been changed to not provide a complete
1381 description, but the UID hint, passphrase info and a flag
1382 indicating if this is a repeated attempt individually, so the user
1383 can compose his own description from this information.
1385 The passphrase is not returned as a C string, but must be written
1386 to a file descriptor directly. This allows for secure passphrase
1389 The return type has been changed to gpgme_error_t value. This
1390 allowed to remove the gpgme_cancel function; just return
1391 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1393 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1394 The user is expected to write the response to the file descriptor,
1395 followed by a newline.
1397 * The recipients interface has been removed. Instead, you use
1398 NULL-terminated lists of keys for specifying the recipients of an
1399 encryption operation. Use the new encryption flag
1400 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1401 the keys (but note that in general this is not a good idea).
1403 This change has been made to the prototypes of gpgme_op_encrypt,
1404 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1405 gpgme_op_encrypt_sign_start.
1407 The export interface has been changed to use pattern strings like
1408 the keylist interface. Thus, new functions gpgme_op_export_ext and
1409 gpgme_op_export_ext_start have been added as well. Now the
1410 prototypes of gpgme_op_export_start and gpgme_op_export finally
1413 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1414 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1417 * gpgme_io_cb_t changed from a void function to a function returning
1418 a gpgme_error_t value. However, it will always return 0, so you
1419 can safely ignore the return value.
1421 * A new I/O callback event GPGME_EVENT_START has been added. The new
1422 requirement is that you must wait until this event until you are
1423 allowed to call the I/O callback handlers previously registered for
1424 this context operation. Calling I/O callback functions for this
1425 context operation before the start event happened is unsafe because
1426 it can lead to race conditions in a multi-threaded environment.
1428 * The idle function feature has been removed. It was not precisely
1429 defined in a multi-threaded environment and is obsoleted by the
1430 user I/O callback functions. If you still need a simple way to
1431 call something while waiting on one or multiple asynchronous
1432 operations to complete, don't set the HANG flag in gpgme_wait (note
1433 that this will return to your program more often than the idle
1436 * gpgme_wait can return NULL even if hang is true, if an error
1437 occurs. In that case *status contains the error code.
1439 * gpgme_get_engine_info was radically changed. Instead an XML
1440 string, an info structure of the new type gpgme_engine_info_t is
1441 returned. This makes it easier and more robust to evaluate the
1442 information in an application.
1444 * The new function gpgme_get_protocol_name can be used to convert a
1445 gpgme_protocol_t value into a string.
1447 * The status of a context operation is not checked anymore. Starting
1448 a new operation will silently cancel the previous one. Calling a
1449 function that requires you to have started an operation before without
1450 doing so is undefined.
1452 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1453 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1454 pointer to a structure which contains the fingerprint. This also
1455 works with gpgme_op_genkey_start. The structure also provides
1456 other information about the generated keys.
1461 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1463 printf ("%s\n", fpr);
1467 gpgme_genkey_result_t result;
1468 err = gpgme_op_genkey (ctx, NULL, NULL);
1471 result = gpgme_op_genkey_result (ctx);
1473 printf ("%s\n", result->fpr);
1476 * The new gpgme_op_import_result function provides detailed
1477 information about the result of an import operation in
1478 gpgme_import_result_t and gpgme_import_status_t objects.
1479 Thus, the gpgme_op_import_ext variant is deprecated.
1481 * The new gpgme_op_sign_result function provides detailed information
1482 about the result of a signing operation in gpgme_sign_result_t,
1483 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1485 * The new gpgme_op_encrypt_result function provides detailed
1486 information about the result of an encryption operation in
1487 a GpgmeEncryptResult object.
1489 * The new gpgme_op_decrypt_result function provides detailed
1490 information about the result of a decryption operation in
1491 a GpgmeDecryptResult object.
1493 * The new gpgme_op_verify_result function provides detailed
1494 information about the result of an verify operation in
1495 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1496 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1497 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1498 and gpgme_get_notation is removed.
1500 * GpgmeTrustItem objects have now directly accessible data, so the
1501 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1502 accessor functions are deprecated. Also, reference counting is
1503 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1504 (the gpgme_trust_item_release alias for the latter is deprecated).
1506 * Keys are not cached internally anymore, so the force_update argument
1507 to gpgme_get_key has been removed.
1509 * GpgmeKey objects have now directly accessible data so the
1510 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1511 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1512 functions are deprecated. Also, gpgme_key_release is now
1513 deprecated. The gpgme_key_get_as_xml function has been dropped.
1515 * Because all interfaces using attributes are deprecated, the
1516 GpgmeAttr data type is also deprecated.
1518 * The new gpgme_op_keylist_result function provides detailed
1519 information about the result of a key listing operation in
1520 a GpgmeKeyListResult object.
1522 * Now that each function comes with its own result retrieval
1523 interface, the generic gpgme_get_op_info interface is not useful
1524 anymore and dropped.
1526 * The type and mode of data objects is not available anymore.
1528 * Interface changes relative to the 0.4.0 release:
1529 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1530 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1531 GpgmeData DEPRECATED: Use gpgme_data_t.
1532 GpgmeError DEPRECATED: Use gpgme_error_t.
1533 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1534 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1535 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1536 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1537 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1538 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1539 GpgmeKey DEPRECATED: Use gpgme_key_t.
1540 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1541 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1542 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1543 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1544 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1545 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1546 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1547 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1548 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1549 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1550 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1551 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1552 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1553 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1554 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1557 gpgme_recipients_t NEW
1559 gpgme_data_encoding_t NEW
1560 gpgme_sig_stat_t NEW
1561 gpgme_sig_mode_t NEW
1563 gpgme_validity_t NEW
1564 gpgme_protocol_t NEW
1566 gpgme_passphrase_cb_t NEW
1567 gpgme_progress_cb_t NEW
1569 gpgme_register_io_cb_t NEW
1570 gpgme_remove_io_cb_t NEW
1571 gpgme_event_io_t NEW
1572 gpgme_event_io_cb_t NEW
1574 gpgme_data_read_cb_t NEW
1575 gpgme_data_write_cb_t NEW
1576 gpgme_data_seek_cb_t NEW
1577 gpgme_data_release_cb_t NEW
1578 gpgme_data_cbs_t NEW
1579 gpgme_trust_item_t NEW
1580 gpgme_status_code_t NEW
1581 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1582 gpgme_err_code_t NEW
1583 gpgme_err_source_t NEW
1585 gpgme_err_source NEW
1588 gpgme_error_from_errno NEW
1589 gpgme_err_make_from_errno NEW
1590 gpgme_err_code_from_errno NEW
1591 gpgme_err_code_to_errno NEW
1593 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1594 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1595 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1596 gpgme_edit_cb_t CHANGED: Write directly to FD.
1597 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1598 gpgme_op_verify CHANGED: Drop R_STAT argument.
1599 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1600 gpgme_wait CHANGED: Can return NULL even if hang is true.
1601 GpgmeIdleFunc REMOVED
1602 gpgme_register_idle REMOVED
1603 GpgmeRecipients REMOVED
1604 gpgme_recipients_new REMOVED
1605 gpgme_recipients_release REMOVED
1606 gpgme_recipients_add_name REMOVED
1607 gpgme_recipients_add_name_with_validity REMOVED
1608 gpgme_recipients_count REMOVED
1609 gpgme_recipients_enum_open REMOVED
1610 gpgme_recipients_enum_read REMOVED
1611 gpgme_recipients_enum_close REMOVED
1612 gpgme_encrypt_flags_t NEW
1613 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1614 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1615 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1616 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1617 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1618 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1619 gpgme_op_export CHANGED: User IDs passed as patterns.
1620 gpgme_op_export_ext_start NEW
1621 gpgme_op_export_ext NEW
1622 gpgme_keylist_mode_t NEW
1624 gpgme_engine_info_t NEW
1625 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1626 gpgme_get_protocol_name NEW
1627 gpgme_cancel REMOVED: Return error in callback directly.
1628 gpgme_op_genkey CHANGED: FPR argument dropped.
1629 gpgme_op_genkey_result NEW
1630 gpgme_genkey_result_t NEW
1631 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1632 gpgme_op_import_result NEW
1633 gpgme_import_status_t NEW
1634 gpgme_import_result_t NEW
1635 gpgme_pubkey_algo_t NEW
1636 gpgme_hash_algo_t NEW
1637 gpgme_invalid_key_t NEW
1638 gpgme_new_signature_t NEW
1639 gpgme_sign_result_t NEW
1640 gpgme_op_sign_result NEW
1641 gpgme_pubkey_algo_name NEW
1642 gpgme_hash_algo_name NEW
1643 gpgme_encrypt_result_t NEW
1644 gpgme_op_encrypt_result NEW
1645 gpgme_decrypt_result_t NEW
1646 gpgme_op_decrypt_result NEW
1647 gpgme_verify_result_t NEW
1648 gpgme_op_verify_result NEW
1649 gpgme_get_notation REMOVED: Access verify result directly instead.
1650 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1651 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1652 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1653 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1654 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1655 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1656 gpgme_trust_item_ref NEW
1657 gpgme_trust_item_unref NEW
1658 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1659 gpgme_trust_item_get_string_attr DEPRECATED
1660 gpgme_trust_item_get_ulong_attr DEPRECATED
1661 gpgme_get_key CHANGED: Removed force_update argument.
1665 gpgme_key_t CHANGED: Now has user accessible data members.
1666 gpgme_key_get_string_attr DEPRECATED
1667 gpgme_key_get_ulong_attr DEPRECATED
1668 gpgme_key_sig_get_string_attr DEPRECATED
1669 gpgme_key_sig_get_ulong_attr DEPRECATED
1670 gpgme_key_get_as_xml REMOVED
1671 gpgme_key_list_result_t NEW
1672 gpgme_op_keylist_result NEW
1673 gpgme_get_op_info REMOVED
1674 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1676 Noteworthy changes in version 0.4.0 (2002-12-23)
1677 ------------------------------------------------
1679 * Key generation returns the fingerprint of the generated key.
1681 * New convenience function gpgme_get_key.
1683 * Supports signatures of user IDs in keys via the new
1684 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1685 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1686 interfaces. The XML info about a key also includes the signatures
1689 * New data object interface, which is more flexible and transparent.
1691 * Interface changes relative to the 0.3.9 release:
1692 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1694 GpgmeDataWriteCb NEW
1696 GpgmeDataReleaseCb NEW
1698 gpgme_data_read CHANGED: Match read() closely.
1699 gpgme_data_write CHANGED: Match write() closely.
1701 gpgme_data_new_from_fd NEW
1702 gpgme_data_new_from_stream NEW
1703 gpgme_data_new_from_cbs NEW
1704 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1705 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1706 gpgme_data_get_type REMOVED: No replacement.
1707 gpgme_op_verify CHANGED: Take different data objects for
1708 signed text and plain text.
1709 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1710 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1711 gpgme_op_genkey CHANGED: New parameter FPR.
1712 GPGME_KEYLIST_MODE_SIGS NEW
1713 gpgme_key_sig_get_string_attr NEW
1714 gpgme_key_sig_get_ulong_attr NEW
1716 GPGME_ATTR_SIG_CLASS NEW
1717 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1719 Noteworthy changes in version 0.3.16 (2003-11-19)
1720 -------------------------------------------------
1722 * Compatibility fixes for GnuPG 1.9.x
1724 Noteworthy changes in version 0.3.15 (2003-02-18)
1725 -------------------------------------------------
1727 * The progress status is sent via the progress callbacks in
1730 * Bug fix for signing operations with explicit signer settings for
1733 Noteworthy changes in version 0.3.14 (2002-12-04)
1734 -------------------------------------------------
1736 * GPGME-Plug is now in its own package "cryptplug".
1738 * Workaround for a setlocale problem. Fixed a segv related to not
1739 correctly as closed marked file descriptors.
1741 Noteworthy changes in version 0.3.13 (2002-11-20)
1742 -------------------------------------------------
1744 * Release due to changes in gpgmeplug.
1746 Noteworthy changes in version 0.3.12 (2002-10-15)
1747 -------------------------------------------------
1749 * Fixed some bux with key listings.
1751 * The development has been branched to clean up some API issues.
1752 This 0.3 series will be kept for compatibility reasons; so do don't
1753 expect new features.
1755 Noteworthy changes in version 0.3.11 (2002-09-20)
1756 -------------------------------------------------
1760 Noteworthy changes in version 0.3.10 (2002-09-02)
1761 -------------------------------------------------
1763 * Setting the signing keys for the CMS protocol does now work.
1765 * The signers setting is honoured by gpgme_op_edit.
1767 Noteworthy changes in version 0.3.9 (2002-08-21)
1768 ------------------------------------------------
1770 * A spec file for creating RPMs has been added.
1772 * An experimental interface to GnuPG's --edit-key functionality is
1773 introduced, see gpgme_op_edit.
1775 * The new gpgme_import_ext function provides a convenient access to
1776 the number of processed keys.
1778 * Interface changes relative to the 0.3.8 release:
1779 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1782 gpgme_op_edit_start NEW
1784 gpgme_op_import_ext NEW
1785 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1787 Noteworthy changes in version 0.3.8 (2002-06-25)
1788 ------------------------------------------------
1790 * It is possible to use an outside event loop for the I/O to the
1791 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1793 * Interface changes relative to the 0.3.6 release:
1794 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1796 GpgmeRegisterIOCb NEW
1800 struct GpgmeIOCbs NEW
1801 gpgme_set_io_cbs NEW
1802 gpgme_get_io_cbs NEW
1803 GPGME_ATTR_ERRTOK NEW
1804 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1806 Noteworthy changes in version 0.3.7 (2002-06-04)
1807 ------------------------------------------------
1809 * GPGME_ATTR_OTRUST is implemented now.
1811 * A first step toward thread safeness has been achieved, see the
1812 documentation for details. Supported thread libraries are pthread
1815 Noteworthy changes in version 0.3.6 (2002-05-03)
1816 ------------------------------------------------
1818 * All error output of the gpgsm backend is send to the bit bucket.
1820 * The signature verification functions are extended. Instead of
1821 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1822 expired signatures. 2 new functions may be used to retrieve more
1823 detailed information like the signature expiration time and a
1824 validity information of the key without an extra key looking.
1826 * The current passphrase callback and progress meter callback can be
1827 retrieved with the new functions gpgme_get_passphrase_cb and
1828 gpgme_get_progress_cb respectively.
1830 * Interface changes relative to the 0.3.5 release:
1831 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1832 gpgme_get_passphrase_cb NEW
1833 gpgme_get_progress_cb NEW
1834 GpgmeDataEncoding NEW
1835 gpgme_data_set_encoding NEW
1836 gpgme_data_get_encoding NEW
1837 GPGME_SIG_STAT_GOOD_EXP NEW
1838 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1839 gpgme_op_verify CHANGED: Returns more status codes.
1840 GPGME_ATTR_SIG_STATUS NEW
1841 gpgme_get_sig_string_attr NEW
1842 gpgme_get_sig_ulong_attr NEW
1843 gpgme_get_protocol NEW
1844 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1846 Noteworthy changes in version 0.3.5 (2002-04-01)
1847 ------------------------------------------------
1849 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1850 case, symmetric encryption is performed. Note that this requires a
1851 passphrase from the user.
1853 * More information is returned for X.509 certificates.
1855 * Interface changes relative to the 0.3.4 release:
1856 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1857 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1858 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1860 Noteworthy changes in version 0.3.4 (2002-03-04)
1861 ------------------------------------------------
1863 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1864 some recipients have been invalid, whereas earlier versions
1865 succeeded in this case. The plaintext is still encrypted for all valid
1866 recipients, so the application might take this error as a hint that
1867 the ciphertext is not usable for all requested recipients.
1868 Information about invalid recipients is available with gpgme_get_op_info.
1870 * gpgme_op_verify now allows to pass an uninitialized data object as
1871 its plaintext argument to check for normal and cleartext
1872 signatures. The plaintext is then returned in the data object.
1874 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1875 to set and get the number of certifications to include in S/MIME
1878 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1879 to encrypt and sign a message in a combined operation.
1881 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1883 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1885 * Interface changes relative to the 0.3.3 release:
1886 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1887 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1888 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1889 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1890 gpgme_set_include_certs NEW
1891 gpgme_get_include_certs NEW
1892 gpgme_op_encrypt_sign NEW
1893 gpgme_op_encrypt_sign_start NEW
1894 gpgme_op_keylist_ext_start NEW
1895 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1897 Noteworthy changes in version 0.3.3 (2002-02-12)
1898 ------------------------------------------------
1900 * Fix the Makefile in jnlib.
1902 * Fix the test suite (hopefully). It should clean up all its state
1903 with `make check' now.
1906 Noteworthy changes in version 0.3.2 (2002-02-10)
1907 ------------------------------------------------
1909 * Remove erroneous dependency on libgcrypt in jnlib.
1912 Noteworthy changes in version 0.3.1 (2002-02-09)
1913 ------------------------------------------------
1915 * There is a Texinfo manual documenting the API.
1917 * The gpgme_set_keylist_mode function returns an error, and changed
1918 its meaning. It is no longer usable to select between normal and
1919 fast mode (newer versions of GnuPG will always be fast), but
1920 selects between local keyring, remote keyserver, or both.
1921 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1922 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1923 current setting, a function gpgme_get_keylist_mode was added to
1924 retrieve the current mode.
1926 * gpgme_wait accepts a new argument STATUS to return the error status
1927 of the operation on the context. Its definition is closer to
1928 waitpid() now than before.
1930 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1931 type from off_t to the unsigned size_t.
1933 * The R_HD argument to the GpgmePassphraseCb type changed its type
1934 from void* to void**.
1936 * New interface gpgme_op_trustlist_end() to match
1937 gpgme_op_keylist_end().
1939 * The CryptPlug modules have been renamed to gpgme-openpgp and
1940 gpgme-smime, and they are installed in pkglibdir by `make install'.
1942 * An idle function can be registered with gpgme_register_idle().
1944 * The GpgSM backend supports key generation with gpgme_op_genkey().
1946 * Interface changes relative to the 0.3.0 release:
1947 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1948 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1949 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1950 gpgme_wait CHANGED: New argument STATUS.
1951 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1952 The function has a new meaning!
1953 gpgme_get_keylist_mode NEW
1954 GPGME_KEYLIST_MODE_LOCAL NEW
1955 GPGME_KEYLIST_MODE_EXTERN NEW
1956 gpgme_op_trustlist_next NEW
1958 gpgme_register_idle NEW
1959 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1961 Noteworthy changes in version 0.3.0 (2001-12-19)
1962 ------------------------------------------------
1964 * New interface gpgme_set_protocol() to set the protocol and thus the
1965 crypto engine to be used by the context. Currently, the OpenPGP
1966 and the CMS protocols are supported. They are specified by the new
1967 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1968 A new context uses the OpenPGP engine by default.
1970 * gpgme_get_engine_info() returns information for all crypto engines
1971 compiled into the library. The XML format has changed. To
1972 reliably get the version of a crypto engine, the <version> tag
1973 after the appropriate <protocol> tag has to be looked for.
1975 * New interface gpgme_engine_check_version(), obsoleting
1976 gpgme_check_engine(). Check the version of all engines you are
1977 supporting in your software.
1979 * GpgmeKey lists the user ids in the order as they are returned by
1980 GnuPG, first the primary key with index 0, then the sub-user ids.
1982 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1983 signatures simultaneously.
1985 * The new interface gpgme_op_keylist_end() terminates a pending
1986 keylist operation. A keylist operation is also terminated when
1987 gpgme_op_keylist_next() returns GPGME_EOF.
1989 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1990 cross-compiled, or even compiled without support for GnuPG
1993 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1994 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1995 in the path, but it can also be compiled without support for GpgSM
1996 (`--without-gpgsm').
1998 * CryptPlug modules for GPGME are included and can be enabled at
1999 configure time (`--enable-gpgmeplug'). There is one module which
2000 uses the GnuPG engine (`gpgmeplug') and one module which uses the
2001 GpgSM engine (`gpgsmplug').
2003 * Interface changes relative to the latest 0.2.x release:
2004 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2005 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
2006 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
2007 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
2008 gpgme_get_engine_info CHANGED: New format, extended content.
2009 gpgme_engine_check_version NEW
2010 gpgme_decrypt_verify_start NEW
2011 gpgme_decrypt_verify NEW
2012 gpgme_op_keylist_next NEW
2013 gpgme_set_protocol NEW
2014 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2017 Noteworthy changes in version 0.2.3 (2001-09-17)
2018 ------------------------------------------------
2020 * New function gpgme_get_op_info which can be used to get the micalg
2021 parameter needed for MOSS.
2023 * New functions gpgme_get_armor and gpgme_get_textmode.
2025 * The usual bug fixes and some minor functionality improvements.
2027 * Added a simple encryption component for MS-Windows; however the
2028 build procedure might have some problems.
2031 Noteworthy changes in version 0.2.2 (2001-06-12)
2032 ------------------------------------------------
2034 * Implemented a key cache.
2036 * Fixed a race condition under W32 and some other bug fixes.
2039 Noteworthy changes in version 0.2.1 (2001-04-02)
2040 ------------------------------------------------
2042 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
2044 * Handle GnuPG's new key capabilities output and support revocation
2047 * Made the W32 support more robust.
2050 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
2053 This file is free software; as a special exception the author gives
2054 unlimited permission to copy and/or distribute it, with or without
2055 modifications, as long as this notice is preserved.
2057 This file is distributed in the hope that it will be useful, but
2058 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
2059 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.