1 Noteworthy changes in version 1.12.0 (2018-10-08)
2 -------------------------------------------------
4 * Enhanced the JSON based interface tool gpgme-json to support Native
5 Messaging as well as new Javascript code to support the browser
6 site. See lang/js/README for details.
8 * Major overhaul of the Python language bindings documentation.
10 * Even for old versions of gpg a missing MDC will now lead to a
13 * Added context flag "auto-key-locate" to control the
14 behavior of GPGME_KEYLIST_MODE_LOCATE.
16 * New data function to create a data object from an estream.
18 * Add more interfaces to the C++ bindings.
20 * Improved error codes on decryption failure.
22 * Lots of minor fixes.
24 * Interface changes relative to the 1.11.1 release:
25 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
26 gpgme_data_new_from_estream NEW.
27 gpgme_decrypt_result_t EXTENDED: New field legacy_cipher_nomdc.
28 gpgme_set_ctx_flag EXTENDED: New flag 'ignore-mdc-error'.
29 GPGME_AUDITLOG_DEFAULT NEW.
30 GPGME_AUDITLOG_DIAG NEW.
31 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-locate'.
32 cpp: DecryptionResult::sessionKey NEW.
33 cpp: DecryptionResult::symkeyAlgo NEW.
34 cpp: DecryptionResult::isLegacyCipherNoMDC New.
35 cpp: Data::rewind NEW.
36 cpp: Context::setFlag NEW.
37 cpp: Context::getFlag NEW.
38 cpp: Context::createKeyEx NEW.
40 [c=C32/A21/R0 cpp=C14/A8/R0 qt=C10/A3/R2]
42 Release-info: https://dev.gnupg.org/T4109
45 Noteworthy changes in version 1.11.1 (2018-04-20)
46 -------------------------------------------------
48 * Fixed build problems in the 1.11.0 release.
50 * Added C++ interfaces which were planned for 1.11.0.
52 * Interface changes relative to the 1.10.0 release:
53 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55 cpp: Key::lastUpdate NEW.
56 cpp: UserID::origin NEW.
57 cpp: UserID::lastUpdate NEW.
59 [c=C31/A20/R1 cpp=C13/A7/R0 qt=C10/A3/R2]
62 Noteworthy changes in version 1.11.0 (2018-04-18)
63 -------------------------------------------------
65 * New encryption API to support direct key specification including
66 hidden recipients option and taking keys from a file. This also
67 allows to enforce the use of a subkey.
69 * New encryption flag for the new API to enforce the use of plain
70 mail addresses (addr-spec).
72 * The import API can now tell whether v3 keys are skipped. These old
73 and basically broken keys are not anymore supported by GnuPG 2.1.
75 * The decrypt and verify API will now return the MIME flag as
76 specified by RFC-4880bis.
78 * The offline mode now has an effect on gpg by disabling all network
81 * A failed OpenPGP verification how returns the fingerprint of the
82 intended key if a recent gpg version was used for signature
85 * New tool gpgme-json as native messaging server for web browsers.
86 As of now public key encryption and decryption is supported.
87 Requires Libgpg-error 1.29.
89 * New context flag "request-origin" which has an effect when used
90 with GnuPG 2.2.6 or later.
92 * New context flag "no-symkey-cache" which has an effect when used
93 with GnuPG 2.2.7 or later.
95 * New convenience constant GPGME_KEYLIST_MODE_LOCATE.
97 * Improved the Python documentation.
99 * Fixed a potential regression with GnuPG 2.2.6 or later.
101 * Fixed a crash in the Python bindings on 32 bit platforms. [#3892]
103 * Various minor fixes.
105 * Interface changes relative to the 1.10.0 release:
106 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
107 gpgme_op_encrypt_ext NEW.
108 gpgme_op_encrypt_ext_start NEW.
109 gpgme_op_encrypt_sign_ext NEW.
110 gpgme_op_encrypt_sign_ext_start NEW.
111 GPGME_ENCRYPT_WANT_ADDRESS NEW.
112 GPGME_KEYLIST_MODE_LOCATE NEW.
113 gpgme_import_result_t EXTENDED: New field 'skipped_v3_keys'.
114 gpgme_decrypt_result_t EXTENDED: New field 'symkey_algo'.
115 gpgme_decrypt_result_t EXTENDED: New field 'is_mime'.
116 gpgme_verify_result_t EXTENDED: New field 'is_mime'.
117 cpp: Key::locate NEW.
118 cpp: Data::toString NEW.
119 cpp: ImportResult::numV3KeysSkipped NEW.
121 [c=C31/A20/R0 cpp=C12/A6/R0 qt=C10/A3/R1]
124 Noteworthy changes in version 1.10.0 (2017-12-12)
125 -------------------------------------------------
127 * Now returns more specific error codes for decryption to distinguish
128 between bad passphrase, user canceled, and no secret key.
130 * Now returns key origin information if available.
132 * Added context flag "auto-key-retrieve" to selectively enable the
133 corresponding gpg option.
135 * Added flag is_de_vs to decryption and verify results.
137 * py: Use SEEK_SET as default for data.seek.
139 * cpp: Various new APIs.
141 * Reduced spawn overhead on Linux again. Added new configure option
142 --disable-linux-getdents to disable this feature for very old
145 * Improved the Python bindings build system.
147 * Made the test suite less fragile.
149 * Interface changes relative to the 1.9.0 release:
150 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
151 gpgme_decrypt_result_t EXTENDED: New field 'is_de_vs'.
152 gpgme_signature_t EXTENDED: New field 'is_de_vs'.
154 gpgme_op_delete_ext NEW.
155 gpgme_op_delete_ext_start NEW.
156 GPGME_DELETE_ALLOW_SECRET NEW.
157 GPGME_DELETE_FORCE NEW.
158 gpgme_op_conf_dir NEW.
159 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-retrieve'.
160 cpp: DecryptionResult::isDeVs NEW.
161 cpp: Signature::isDeVs NEW.
162 cpp: EngineInfo::Version::operator> NEW.
163 cpp: Context::createKey NEW.
164 cpp: Context::startCreateKey NEW.
165 cpp: Context::createSubkey NEW.
166 cpp: Context::startCreateSubkey NEW.
168 py: DecryptResult EXTENDED: New boolean field 'is_de_vs'.
169 py: Signature EXTENDED: New boolean field 'is_de_vs'.
170 py: GpgError EXTENDED: Partial results in 'results'.
172 [c=C30/A19/R0 cpp=C11/A5/R0 qt=C10/A3/R0]
175 Noteworthy changes in version 1.9.0 (2017-03-28)
176 ------------------------------------------------
178 * Clarified meaning of the 'expire' parameter of gpgme_op_createkey
179 and gpgme_op_createsubkey. New flag to force a key without an
182 * New function gpgme_op_keylist_from_data_start to list keys from
183 data objects without importing them.
185 * New function gpgme_op_set_uid_flag to flag a key as primary.
187 * New function gpgme_op_decrypt_ext to run decryption with special
188 flags. This can for example be used to unwrap keys (remove only
189 the encryption layer).
191 * New encryption flags to wrap a key (adding an encryption layer to
192 an OpenPGP message) or to create anonymously encrypted messages.
194 * Support for adduid and revuid operations in the C++ bindings.
196 * Support for smartcard key generation in the C++ bindings.
198 * Several new functions for the Python binding.
200 * Many smaller bug fixes.
202 * Interface changes relative to the 1.8.0 release:
203 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
204 gpgme_op_createkey CHANGED: Meaning of 'expire' parameter.
205 gpgme_op_createsubkey CHANGED: Meaning of 'expire' parameter.
206 GPGME_CREATE_NOEXPIRE NEW.
207 gpgme_key_t EXTENDED: New field 'origin'.
208 gpgme_key_t EXTENDED: New field 'last_update'.
209 gpgme_subkey_t EXTENDED: New field 'is_de_vs'.
210 gpgme_user_id_t EXTENDED: New field 'origin'.
211 gpgme_user_id_t EXTENDED: New field 'last_update'.
212 gpgme_op_keylist_from_data_start NEW.
213 gpgme_op_set_uid_flag_start NEW.
214 gpgme_op_set_uid_flag NEW.
215 gpgme_op_decrypt_ext_start NEW.
216 gpgme_op_decrypt_ext NEW.
217 GPGME_ENCRYPT_THROW_KEYIDS NEW.
218 GPGME_ENCRYPT_WRAP NEW.
219 GPGME_DECRYPT_VERIFY NEW.
220 GPGME_DECRYPT_UNWRAP NEW.
221 gpgme_data_rewind UN-DEPRECATE.
222 cpp: Context::revUid(const Key&, const char*) NEW.
223 cpp: Context::startRevUid(const Key&, const char*) NEW.
224 cpp: Context::addUid(const Key&, const char*) NEW.
225 cpp: Context::startAddUid(const Key&, const char*) NEW.
226 cpp: Key::UserID::revoke() NEW.
227 cpp: Key::addUid() NEW.
228 cpp: Key::isDeVs NEW.
229 cpp: GpgGenCardKeyInteractor NEW.
230 cpp: Subkey::keyGrip NEW.
231 cpp: Subkey::isDeVs NEW.
232 cpp: Data::toKeys NEW.
233 cpp: Context::setDecryptFlags NEW.
234 cpp: Context::decrypt EXTENDED: Flags added.
235 cpp: Context::startDecrypt EXTENDED: Flags added.
236 cpp: Context::decryptAndVerify EXTENDED: Flags added.
237 cpp: Context::startCombinedDecryptionAndVerification EXTENDED: Flags.
238 cpp: Context::encryptFlags EXTENDED: New flags.
239 qt: CryptoConfig::stringValueList() NEW.
240 py: Context.__init__ EXTENDED: New keyword arg home_dir.
241 py: Context.home_dir NEW.
242 py: Context.keylist EXTENDED: New keyword arg mode.
243 py: Context.keylist EXTENDED: New keyword arg source.
244 py: Context.create_key NEW.
245 py: Context.create_subkey NEW.
246 py: Context.key_add_uid NEW.
247 py: Context.key_revoke_uid NEW.
248 py: Context.key_sign NEW.
249 py: Context.key_tofu_policy NEW.
250 py: core.pubkey_algo_string NEW.
251 py: core.addrspec_from_uid NEW.
253 [c=C29/A18/R0 cpp=C10/A4/R0 qt=C9/A2/R0]
256 Noteworthy changes in version 1.8.0 (2016-11-16)
257 ------------------------------------------------
259 * The module of the Python bindings has been renamed to 'gpg'.
261 * New interface to query current software versions.
263 * New feature to use gpg's --{show,override}session-key options.
265 * New interface to set the sender of a mail.
267 * qt: Added Distinguished Name parser from libkleo
269 * The --homedir option is now used with recent gpgconf versions.
271 * On 64 bit Windows systems gpgconf is now properly located.
273 * The internal locking functions have been replaced by libgpg-error
276 * Interface changes relative to the 1.7.1 release:
277 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
278 gpgme_set_sender NEW.
279 gpgme_get_sender NEW.
280 gpgme_op_query_swdb NEW.
281 gpgme_op_query_swdb_result NEW.
282 gpgme_query_swdb_result_t NEW.
283 gpgme_get_ctx_flag NEW.
284 gpgme_decrypt_result_t EXTENDED: New field session_key.
286 qt: DN::Attribute NEW.
287 qt: Job::context(Job*) NEW.
288 cpp: EngineInfo::Version::Version(const char*) NEW.
289 cpp: EngineInfo::Version::Version() NEW.
291 cpp: Context::setSender(const char*) NEW.
292 cpp: Context::getSender() NEW.
294 [c=C28/A17/R0 cpp=C9/A3/R0 qt=C8/A1/R0]
297 Noteworthy changes in version 1.7.1 (2016-10-18)
298 ------------------------------------------------
300 * Fixed problems with the new language bindings.
302 * New helper function gpgme_addrspec_from_uid.
304 * Use option --exit-on-status-write-error with newer gpg versions.
306 * qt: Missed API from the Qt Binding inclusion has
309 * qt: abstractimportjob.h is now installed to that
310 ImportJobs can be used again.
312 * qt: Fixed spelling error in API (startReceive).
314 * Interface changes relative to the 1.7.0 release:
315 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
316 gpgme_addrspec_from_uid NEW.
317 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
318 qt: MultiDeleteJob NEW.
319 qt: AbstractImportJob NEW.
321 cpp: Signature::key(bool, bool) NEW.
322 cpp: UserID::addrSpecFromString(const char*) NEW.
323 cpp: UserID::addrSpec() NEW.
325 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
328 Noteworthy changes in version 1.7.0 (2016-09-21)
329 ------------------------------------------------
331 * New language bindings for Python 2 and 3.
333 * New language Bindings for C++ and the Qt-Framework API.
335 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
336 key creation easier (requires GnuPG 2.1).
338 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
339 management easier (requires GnuPG 2.1).
341 * New function gpgme_op_keysign to make key signing easier (requires
344 * New function gpgme_op_interact to replace the now deprecated
345 functions gpgme_op_edit and gpgme_op_card_edit.
347 * New function gpgme_pubkey_algo_string to convert a public key
348 algorithm into a GnuPG 2.1 style string.
350 * Support for GnuPG 2.1's TOFU trust model.
352 * Notation flags are now correctly set on verify.
354 * New global flag "require-gnupg" to set a minimal gnupg version.
356 * More supported items in gpgme_get_dirinfo.
358 * New function gpgme_data_set_flag and flag "size-hint".
360 * New function gpgme_set_ctx_flag and flags "full-status" and
363 * Improved gpgme_data_identify to distinguish more file types.
365 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
366 mixed public key and symmetric encryption.
368 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
370 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
371 signed data is a valid MIME part. This is to support future GnuPG
374 * Interface changes relative to the 1.6.0 release:
375 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
376 gpgme_pubkey_algo_string NEW.
378 gpgme_set_ctx_flag NEW.
379 gpgme_data_set_flag NEW.
380 gpgme_op_createkey NEW.
381 gpgme_op_createkey_start NEW.
382 gpgme_op_createsubkey NEW.
383 gpgme_op_createsubkey_start NEW.
384 gpgme_op_adduid_start NEW.
386 gpgme_op_revuid_start NEW.
388 gpgme_op_keysign_start NEW.
389 gpgme_op_keysign NEW.
390 gpgme_op_tofu_policy_start NEW.
391 gpgme_op_tofu_policy NEW.
392 gpgme_op_interact_start NEW.
393 gpgme_op_interact NEW.
394 gpgme_interact_cb_t NEW.
395 gpgme_op_edit_start DEPRECATED.
396 gpgme_op_edit DEPRECATED.
397 gpgme_op_card_edit_start DEPRECATED.
398 gpgme_op_card_edit DEPRECATED.
399 gpgme_edit_cb_t DEPRECATED.
400 gpgme_status_code_t DEPRECATED.
401 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
402 gpgme_signature_t EXTENDED: New field key.
403 gpgme_key_t EXTENDED: New field fpr.
404 gpgme_subkey_t EXTENDED: New field keygrip.
405 gpgme_user_id_t EXTENDED: New field tofu.
406 gpgme_tofu_policy_t NEW.
407 gpgme_tofu_info_t NEW.
408 GPGME_STATUS_KEY_CONSIDERED NEW.
409 GPGME_STATUS_TOFU_USER NEW.
410 GPGME_STATUS_TOFU_STATS NEW.
411 GPGME_STATUS_TOFU_STATS_LONG NEW.
412 GPGME_STATUS_NOTATION_FLAGS NEW.
413 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
414 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
415 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
416 GPGME_DATA_ENCODING_MIME NEW.
417 GPGME_ENCRYPT_SYMMETRIC NEW.
418 GPGME_CREATE_SIGN NEW.
419 GPGME_CREATE_ENCR NEW.
420 GPGME_CREATE_CERT NEW.
421 GPGME_CREATE_AUTH NEW.
422 GPGME_CREATE_NOPASSWD NEW.
423 GPGME_CREATE_SELFSIGNED NEW.
424 GPGME_CREATE_NOSTORE NEW.
425 GPGME_CREATE_WANTPUB NEW.
426 GPGME_CREATE_WANTSEC NEW.
427 GPGME_CREATE_FORCE NEW.
428 GPGME_KEYSIGN_LOCAL NEW.
429 GPGME_KEYSIGN_LFSEP NEW.
430 GPGME_INTERACT_CARD NEW.
432 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
435 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
436 ------------------------------------------------
438 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
440 * Added gpgme_set_status_cb to allow a user to see some status
443 * Added an export mode for secret keys.
445 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
447 * The passphrase handler for the loopback mode has been improved and may
448 also be used with genkey.
450 * [w32] The standard GnuPG 2.1 install directory is now seached for
451 gpgconf.exe before a registry specified directory and the Gpg4win
454 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
457 * Interface changes relative to the 1.5.1 release:
458 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
459 gpgme_set_offline NEW.
460 gpgme_get_offline NEW.
461 gpgme_set_status_cb NEW.
462 gpgme_get_status_cb NEW.
463 GPGME_EXPORT_MODE_SECRET NEW
464 GPGME_EXPORT_MODE_RAW NEW.
465 GPGME_EXPORT_MODE_PKCS12 NEW.
468 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
469 ------------------------------------------------
471 * Fixed crash in key listings for user ids with a backslash.
473 * Fixed regression for GPGSM use with GnuPG < 2.1.
475 * Properly set signature summary for revoked OpenPGP keys.
478 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
479 ------------------------------------------------
481 * Fixed a possible crash in the debug code.
483 * Fixed building for Windows with newer versions of Mingw.
486 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
487 -------------------------------------------------------------
489 * The export key functions do now return an error if used with the
490 latest GnuPG version.
493 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
494 -------------------------------------------------------------
496 * gpgme-tool is now installed.
498 * Fix external listing for modern keyservers.
503 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
504 -------------------------------------------------------------
506 * Fixed possible overflow in gpgsm and uiserver engines.
509 * Added support for GnuPG 2.1's --with-secret option.
511 * Interface changes relative to the 1.5.0 release:
512 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
513 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
516 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
517 -------------------------------------------------------------
519 * On Unices the engine file names are not not anymore hardwired but
520 located via the envvar PATH. All options to set the name of the
521 engines for the configure run are removed.
523 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
524 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
525 is not found, GPGME looks for an engine named "gpg".
527 * New feature to use the gpgme I/O subsystem to run arbitrary
530 * New flag to use encryption without the default compression step.
532 * New function to access "gpg-conf --list-dirs"
534 * New configure option --enable-fixed-path for use by Android.
536 * Support ECC algorithms.
538 * Interface changes relative to the 1.4.3 release:
539 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
540 gpgme_get_dirinfo NEW.
541 gpgme_op_spawn_start NEW.
543 GPGME_PROTOCOL_SPAWN NEW.
544 GPGME_SPAWN_DETACHED NEW.
545 GPGME_SPAWN_ALLOW_SET_FG NEW.
546 GPGME_ENCRYPT_NO_COMPRESS NEW.
549 gpgme_subkey_t EXTENDED: New field curve.
550 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
551 GPGME_STATUS_MOUNTPOINT NEW.
552 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
553 GPGME_STATUS_ATTRIBUTE NEW.
554 GPGME_STATUS_BEGIN_SIGNING NEW.
555 GPGME_STATUS_KEY_NOT_CREATED NEW.
558 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
559 -------------------------------------------------------------
561 * The default engine names are now taken from the output of gpgconf.
562 If gpgconf is not found the use of gpg 1 is assumed.
564 * Under Windows the default engines names are first searched in the
565 installation directory of the gpgme DLL.
567 * New function gpgme_data_identify to detect the type of a message.
569 * Interface changes relative to the 1.4.2 release:
570 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
571 gpgme_signers_count NEW.
572 gpgme_data_type_t NEW.
573 gpgme_data_identify NEW.
576 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
577 -------------------------------------------------------------
579 * Allow symmetric encryption with gpgme_op_encrypt_sign.
581 * Fixed mismatching off_t definitions on Windows.
583 * Interface changes relative to the 1.4.1 release:
584 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
587 GPGME_PROTOCOL_OPENPGP NEW alias.
590 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
591 ------------------------------------------------------------
593 * Fixed reading of gpg.conf files with excessive use of the group
596 * Fixed building with the i686-w64-mingw32 toolchain.
598 * Disabled FD passing by default for Apple.
601 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
602 ------------------------------------------------------------
604 * New function gpgme_set_global_flag to help debugging on Android.
606 * New function gpgme_io_writen as a convenience wrapper around
609 * New functions to support the pinentry mode feature of GnuPG 2.1.
611 * New macro GPGME_VERSION_NUMBER to allow supporting different API
612 versions without the need for a configure test.
614 * Several improvements for gpgme-tool.
616 * Better logging of the common "invalid engine" error code.
618 * Support for FD passing is now enabled by default. The configure
619 option --disable-fd-passing may be used to disable this.
621 * Interface changes relative to the 1.3.1 release:
622 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
623 GPGME_VERSION_NUMBER NEW.
625 gpgme_set_global_flag NEW.
626 gpgme_set_pinentry_mode NEW.
627 gpgme_get_pinentry_mode NEW.
628 gpgme_pinentry_mode_t NEW.
629 GPGME_PINENTRY_MODE_DEFAULT NEW.
630 GPGME_PINENTRY_MODE_ASK NEW.
631 GPGME_PINENTRY_MODE_CANCEL NEW.
632 GPGME_PINENTRY_MODE_ERROR NEW.
633 GPGME_PINENTRY_MODE_LOOPBACK NEW.
636 Noteworthy changes in version 1.3.2 (2012-05-02)
637 ------------------------------------------------
639 * Remove support for libgpgme-pth. As far as we know, this was never used,
640 and GnuPG is going to use our own npth in the future.
642 * Fix signature summary information for a missing X.509 key.
644 * Fix parsing of dates >= year 2038.
647 Noteworthy changes in version 1.3.1 (2011-06-16)
648 ------------------------------------------------
650 * Ported to Windows CE.
652 * Detect GPG versions not supporting ---passwd.
654 * Interface changes relative to the 1.3.0 release:
655 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
656 GPGME_EXPORT_MODE_MINIMAL NEW
657 GPGME_STATUS_SUCCESS NEW
658 gpgme_err_code_from_syserror NEW
659 gpgme_err_set_errno NEW
660 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
661 gpgme_error_from_syserror NEW
662 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
665 Noteworthy changes in version 1.3.0 (2010-01-11)
666 ------------------------------------------------
668 * GPGME does not come with an internal libassuan version anymore.
669 The external libassuan 1.1.0 release or later is required. For
670 application programmers on systems that can resolve inter-library
671 dependencies at runtime, this is a transparent change.
673 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
675 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
677 * New API to change the passphrase of a key.
679 * Interface changes relative to the 1.2.0 release:
680 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
681 GPGME_STATUS_INV_SGNR NEW.
682 GPGME_STATUS_NO_SGNR NEW.
683 GPGME_PROTOCOL_G13 NEW.
684 gpgme_op_g13_mount NEW.
685 gpgme_g13_result_t NEW.
688 gpgme_op_passwd_start NEW.
690 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
693 Noteworthy changes in version 1.2.0 (2009-06-18)
694 ------------------------------------------------
696 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
699 * gpgme_new will fail if gpgme_check_version was not called, or a
700 selftest failed (for example, if -mms-bitfields was not used on
703 * New functions gpgme_io_read and gpgme_io_write for use with
704 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
706 * New functions gpgme_result_ref and gpgme_result_unref to detach
707 result structures from a context.
709 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
710 that allow to specify exported keys through gpgme_key_t objects
713 * New mode of operation gpgme_export_mode_t that allows exporting
716 * Interface changes relative to the 1.1.7 release:
717 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
718 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
719 GPGME_PROTOCOL_ASSUAN NEW.
720 gpgme_assuan_data_cb_t NEW.
721 gpgme_assuan_inquire_cb_t NEW.
722 gpgme_assuan_status_cb_t NEW.
723 gpgme_op_assuan_transact_start NEW.
724 gpgme_op_assuan_transact NEW.
725 gpgme_op_assuan_result NEW.
726 gpgme_op_import_keys NEW.
727 gpgme_op_import_keys_start NEW.
728 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
729 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
730 gpgme_check_version CHANGED: Is now a macro.
731 gpgme_new EXTENDED: More failure codes.
734 gpgme_result_ref NEW.
735 gpgme_result_unref NEW.
736 gpgme_export_mode_t NEW.
737 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
738 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
739 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
740 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
741 gpgme_op_export_keys_start NEW.
742 gpgme_op_export_keys NEW.
743 GPGME_DATA_ENCODING_URL NEW.
744 GPGME_DATA_ENCODING_URL0 NEW.
745 GPGME_DATA_ENCODING_URLESC NEW.
746 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
749 Noteworthy changes in version 1.1.8 (2008-12-08)
750 ------------------------------------------------
752 * SIGPIPE is now again ignored as described in the manual. Fixes
753 regresion introduced with 1.1.6.
756 Noteworthy changes in version 1.1.7 (2008-10-17)
757 ------------------------------------------------
759 * Using GPGME_KEYLIST_MODE_LOCAL combined with
760 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
761 --locate-keys feature of gpg (>= 2.0.10).
763 * The encoding of gpgme_data_t objects can affect the output encoding
764 of export, sign and encrypt operations now (the same operations
765 that are also affected by the ASCII mode switch). We believe this
766 change in the ABI is innocent enough not to break existing
767 applications (it only affects the S/MIME backend on certain
770 * The reference manual now includes the specification of "The GnuPG
773 * A new function gpgme_cancel_async can be used to asynchronously
774 cancel any pending operation at any time, from any thread.
776 * Interface changes relative to the 1.1.6 release:
777 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
778 gpgme_op_encrypt CHANGED: Output encoding can affect result.
779 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
780 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
781 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
782 gpgme_op_sign CHANGED: Output encoding can affect result.
783 gpgme_op_sign_start CHANGED: Output encoding can affect result.
784 gpgme_op_export CHANGED: Output encoding can affect result.
785 gpgme_op_export_start CHANGED: Output encoding can affect result.
786 gpgme_op_export_ext CHANGED: Output encoding can affect result.
787 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
788 gpgme_cancel_async NEW
789 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
792 Noteworthy changes in version 1.1.6 (2008-01-04)
793 ------------------------------------------------
795 * Bug fixes for for W32.
797 * A new, experimental (and thus undocumented and potentially
798 unstable) interface for accessing gpg-conf through GPGME has been
801 * Interface changes relative to the 1.1.1 release:
802 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
803 gpgme_signature_t EXTENDED: New field chain_model.
804 gpgme_op_getauditlog_start NEW.
805 gpgme_op_getauditlog NEW.
806 GPGME_AUDITLOG_HTML NEW.
807 GPGME_AUDITLOG_WITH_HELP NEW.
808 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
811 Noteworthy changes in version 1.1.5 (2007-07-09)
812 ------------------------------------------------
814 * Bug and portability fixes (mainly for W32).
817 Noteworthy changes in version 1.1.4 (2007-03-05)
818 ------------------------------------------------
820 * Detect and bail out on double plaintext messages. This is required
821 so that applications can properly detect the signed parts of a
822 message. Actual there is now a double protection as GnuPG 1.4.7
823 will detect this case too.
826 Noteworthy changes in version 1.1.3 (2007-01-29)
827 ------------------------------------------------
829 * Fixed a memory leak in gpgme_data_release_and_get_mem.
831 * Fixed a bug in Windows command line quoting.
834 Noteworthy changes in version 1.1.2 (2006-03-02)
835 ------------------------------------------------
837 * Fixed a bug in the W32 glib backend.
840 Noteworthy changes in version 1.1.1 (2006-02-23)
841 ------------------------------------------------
843 * Fixed a bug in that the fingerprints of subkeys are not available.
845 * Clarified usage of the SECRET flag in key listings. It is now
848 * Reading signature notations and policy URLs on key signatures is
849 supported. They can be found in the new field notations of the
850 gpgme_key_sig_t structure. This has to be enabled with the keylist
851 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
853 * A new gpgme_free() function solves the problem of using different
854 allocators in a single program. This function should now be used
855 instead calling free() to release the buffer returned by
856 gpgme_data_release_and_get_mem. It is recommended that you always
857 do this, but it is only necessary on certain platforms, so backwards
858 compatibility is provided. In other words: If free() worked for
859 you before, it will keep working.
861 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
862 They are analyzed by the verify handlers and made available in the
863 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
865 * Interface changes relative to the 1.1.0 release:
866 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
867 gpgme_key_sig_t EXTENDED: New field notations.
868 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
870 GPGME_STATUS_PKA_TRUST_BAD NEW
871 GPGME_STATUS_PKA_TRUST_GOOD NEW
872 gpgme_signature_t EXTENDED: New field pka_trust.
873 gpgme_signature_t EXTENDED: New field pka_address.
874 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
877 Noteworthy changes in version 1.1.0 (2005-10-01)
878 ------------------------------------------------
880 * You can now configure the backend engine file name and home
881 directory to be used, as default and per context.
883 * Information about the recipients of an encrypted text is now
884 available at decryption time.
886 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
887 and verify handlers, the information about the plaintext filename,
888 if available is made available in the new field file_name of the
889 respective result structure.
891 * The code for "automagically detecting the thread library" has been
892 removed from libgpgme. It is deprecated since version 0.4.3.
893 Since then, you had to link against libgpgme-pthread for
894 applications using pthread and libgpgme-pth for applications using
897 The code was removed because it caused compilation problems on
898 systems where the pthread.h header from GNU Pth is available in
899 addition to the system header (FreeBSD 6 and later for example).
901 * "./autogen.sh --build-w32" does now build gpgme.dll.
903 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
904 delimiter. The standard install directory is used when locating
905 gpg or gpgsm before finally falling back to the hardwired name.
907 * There is a new flag for keys and subkeys, is_qualified, which
908 indicates if a key can be used for qualified signatures according
909 to local government regulations.
911 * You can associate a filename with a data object using the new
912 function gpgme_data_set_file_name(). This filename will be stored
913 in the output when encrypting or signing the data and will be
914 returned when decrypting or verifying the output data.
916 * You can now set notation data at signature creation with the new
917 function gpgme_sig_notation_add().
919 * Interface changes relative to the 1.0.3 release:
920 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
921 gpgme_set_engine_info NEW
922 gpgme_ctx_get_engine_info NEW
923 gpgme_ctx_set_engine_info NEW
924 gpgme_recipient_t NEW
925 gpgme_decrypt_result_t EXTENDED: New field recipients.
926 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
927 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
928 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
929 GPGME_STATUS_PLAINTEXT NEW
930 gpgme_key_t EXTENDED: New field is_qualified.
931 gpgme_subkey_t EXTENDED: New field is_qualified.
932 gpgme_data_get_file_name NEW
933 gpgme_data_set_file_name NEW
934 gpgme_sig_notation_flags_t NEW
935 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
936 GPGME_SIG_NOTATAION_CRITICAL NEW
937 gpgme_sig_notation_clear NEW
938 gpgme_sig_notation_add NEW
939 gpgme_sig_notation_get NEW
940 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
943 Noteworthy changes in version 1.0.3 (2005-06-20)
944 ------------------------------------------------
946 * Previousy, GPGME would use a default "include certs" of 1. This
947 has been changed. Now GPGME will use the crypto backend engines
948 default unless you set the value with gpgme_set_include_certs()
949 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
950 as a value to explicitely request the new default behaviour.
952 Because the default changes, this is a slight change of the API
953 semantics. We consider it to be a bug fix.
955 * A bug which made GPGME hang has been fixed. If you have
956 experienced hanging before, please try out this version and let me
957 know if you still experience hanging problems.
959 * Interface changes relative to the 0.9.0 release:
960 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
961 gpgme_set_include_certs CHANGED DEFAULT
962 GPGME_INCLUDE_CERTS_DEFAULT NEW
963 GPGME_STATUS_SIG_SUBPACKET NEW
964 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
965 GPGME_STATUS_SC_OP_FAILURE NEW
966 GPGME_STATUS_SC_OP_SUCCESS NEW
967 GPGME_STATUS_CARDCTRL NEW
968 GPGME_STATUS_BACKUP_KEY_CREATED NEW
969 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
972 Noteworthy changes in version 1.0.2 (2004-12-28)
973 ------------------------------------------------
975 * Changed the license of the library to the GNU Lesser General Public
976 License (LGPL), version 2.1 or later.
979 Noteworthy changes in version 1.0.1 (2004-10-22)
980 ------------------------------------------------
985 Noteworthy changes in version 1.0.0 (2004-09-30)
986 ------------------------------------------------
988 * Version 1.0.0! We are proud to present you with a thoroughly
989 tested and stable version of the GPGME library. A big Thank You!
990 to all the people who made this possible.
992 The development will be branched into a stable 1.x.y series and the
995 * The gpgme.m4 macro supports checking the API version. Just prepend
996 it to the required version string, separated by a colon. For
997 example, this release has the version "1:1.0.0". The last release
998 to which this version is (mostly) ABI compatible is "1:0.4.2",
999 which is the default required version.
1002 Noteworthy changes in version 0.9.0 (2004-06-08)
1003 ------------------------------------------------
1005 * The type gpgme_key_t has now a new field keylist_mode that contains
1006 the keylist mode that was active at the time the key was retrieved.
1008 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
1009 that contains a flag indicating that the key should not have been
1010 used for encryption.
1012 * Verifying a signature of a revoked key gives the correct result now
1013 (GPG_ERR_CERT_REVOKED error code).
1015 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
1016 verify operations still allows you to look at the signature
1017 verification result.
1019 * Clarified that patterns in keylisting operations have an upper
1020 limit, and thus are not suited to list many keys at once by their
1021 fingerprint. Also improve the error message if the pattern is too
1022 long for the CMS protocol to handle.
1024 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1025 gpgme_key_t EXTENDED: New field keylist_mode.
1026 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
1027 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1030 Noteworthy changes in version 0.4.7 (2004-04-29)
1031 ------------------------------------------------
1033 * Correctly initialize the fields expired, revoked, invalid, and
1034 disabled in the gpgme_key_t structures.
1036 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
1037 accidently of type int instead unsigned int.
1039 * Interface changes relative to the 0.4.5 release:
1040 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1041 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
1042 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1044 Noteworthy changes in version 0.4.6 (2004-04-06)
1045 ------------------------------------------------
1050 Noteworthy changes in version 0.4.5 (2004-03-07)
1051 ------------------------------------------------
1053 * GPGME is now compiled with LFS (large file support) by default.
1054 This means that _all_ programs using GPGME must be compiled with
1055 LFS support enabled by default. You can do this easily with
1056 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
1057 without autoconf by defining the preprocessor symbol
1058 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
1059 the C compiler command line, or by defining this preprocessor
1060 symbol before including any system header files). For more
1061 details, read the section on LFS in the manual.
1063 Up to now, it was undocumented that GPGME was not using LFS.
1064 But the public interfaces use off_t, and file descriptors are
1065 exchanged between the application and GPGME. This was an oversight,
1066 and bound to cause troubles in the future.
1068 Writing GPGME as a dual mode library that seamlessly supports LFS
1069 while keeping backwards compatibility is possible, but does not
1070 solve the problem: Many applications already expect GPGME to have
1071 LFS (they are compiled with off_t being a 64bit value). This is true
1072 in particular for the popular Gtk+ and Qt programs.
1074 So, although this is an ABI (but not an API) break, we will not
1075 change the library version to reflect that. Because the interfaces
1076 affected are probably not used yet in any GPGME 0.4 based
1077 application, we don't expect any real failures from this change.
1078 In fact, applications already using LFS will have some subtle bugs
1081 However, if you encounter an application using GPGME 0.4.x that
1082 does _not_ use LFS by default (off_t is a 32bit value), _and_
1083 uses at least one of the functions gpgme_data_seek,
1084 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
1085 gpgme_data_new_from_cbs, then indeed this library will be ABI
1086 incompatible with the program. As said above, we don't believe
1087 such a program exists. If we are in error, then you have two
1088 options: As a quick hack, you can configure GPGME with the
1089 --disable-largefile option. This will revert the change, and GPGME
1090 will not use LFS. However, GPGME will be incompatible with
1091 programs that expect GPGME to use LFS. All applications are
1092 required to use LFS when using GPGME, so this is only good as a
1093 temporary local work-around.
1095 The other option is to change the versioning of the library and
1096 recompile all applications. We have reserved a special version of
1097 the library for that, so you can do that without expecting a
1098 version clash in the future. Furthermore, everyone who does this
1099 will agree on the version to use (this is important for
1100 distribution makers). Read the comment in configure.ac (before
1101 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
1102 blindly: As stated above, we think it is unlikely this measure is
1103 needed. Still, it is there if necessary. If in doubt, contact us
1104 and we will give our advise for your specific situation.
1106 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
1109 * New interface gpgme_cancel() that can be used to cancel
1110 asynchronous operations.
1112 * Interface changes relative to the 0.4.4 release:
1113 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1114 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
1115 gpgme_data_seek CHANGED: off_t is now a largefile type.
1116 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
1117 GPGME_KEYLIST_MODE_VALIDATE NEW
1119 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1121 Noteworthy changes in version 0.4.4 (2004-01-12)
1122 ------------------------------------------------
1124 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
1125 been renamed to "sig_class", to avoid clash with C++ compilers. In
1126 the C API, the old name "class" has been preserved for backwards
1127 compatibility, but is deprecated.
1129 * Interface changes relative to the 0.4.3 release:
1130 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1131 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
1132 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
1133 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1135 Noteworthy changes in version 0.4.3 (2003-10-06)
1136 ------------------------------------------------
1138 * libgpgme should not be used for threaded programs anymore. This
1139 never worked reliably in all cases, because you had to
1140 be careful about the linking order and libtool wouldn't do that for
1141 you automatically. Instead, now you have to link against
1142 libgpgme-pthread for applications using pthread and libgpgme-pth for
1143 applications using GNU Pth.
1145 The old code for automagically detecting the thread library is
1146 still part of libgpgme, but it is DEPRECATED.
1148 * There are new automake macros AM_PATH_GPGME_PTH and
1149 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
1150 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
1151 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
1152 variables of course also include the configuration for the thread
1153 package itself. Alternatively, use libtool.
1155 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
1158 * gpgme-config doesn't support setting the prefix or exec prefix
1159 anymore. I don't think it ever worked correctly, and it seems to
1162 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
1163 provided was not unique, instead returning the first matching key.
1165 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
1166 that indicates if the key can be used for authentication.
1168 * gpgme_signature_t's status field is now correctly set to an error
1169 with error code GPG_ERR_NO_PUBKEY if public key is not found.
1171 * gpgme_new_signature_t's class field is now an unsigned int, rather
1172 than an unsigned long (the old class field is preserved for
1173 backwards compatibility).
1175 * A new function gpgme_set_locale() is provided to allow configuring
1176 the locale for the crypto backend. This is necessary for text
1177 terminals so that programs like the pinentry can be started with
1178 the right locale settings for the terminal the application is running
1179 on, in case the terminal has different settings than the system
1180 default (for example, if it is a remote terminal). You are highly
1181 recommended to call the following functions directly after
1182 gpgme_check_version:
1186 setlocale (LC_ALL, "");
1187 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
1188 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
1190 GPGME can not do this for you, as setlocale is not thread safe, and
1191 there is no alternative.
1193 * The signal action for SIGPIPE is now set to SIG_IGN by
1194 gpgme_check_version, instead the first time a crypto engine is
1195 started (which is not well defined).
1197 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
1198 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
1199 to CRC24RFC2440. For now, these strings can be used as the MIC
1200 parameter for PGP/MIME (if appropriately modified).
1202 * Interface changes relative to the 0.4.2 release:
1203 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1204 gpgme_strerror_t NEW
1205 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
1206 gpgme_key_t EXTENDED: New field can_authenticate.
1207 gpgme_subkey_t EXTENDED: New field can_authenticate.
1208 gpgme_new_signature_t CHANGED: New type for class field.
1209 gpgme_set_locale NEW
1210 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
1211 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1213 Noteworthy changes in version 0.4.2 (2003-07-30)
1214 ------------------------------------------------
1216 * Allow gpg-error to be in non-standard place when linking the test suite.
1218 * Configure will fail now if gpg-error can not be found.
1220 * Fixed initialized memory backed data objects for writing, which
1221 caused the test program to crash (but only on Mac OS, surprisingly).
1223 * Eliminate use of C99 constructs.
1225 * Small improvements to the manual.
1228 Noteworthy changes in version 0.4.1 (2003-06-06)
1229 ------------------------------------------------
1231 This is the release that 0.4.0 should have been. There are many
1232 interface changes, please see below for the details. The changes are
1233 sometimes the result of new functionality, but more often express a
1234 paradigm shift. Others are an overdue cleanup to get GPGME in line
1235 with the GNU coding standards and to make the interface more
1236 self-consistent. Here is an overview on the changes:
1238 All types have been renamed to conform to the GNU coding standards,
1239 most of the time by keeping the whole name in lowercase and inserting
1240 underscores between words.
1242 All operations consistently only accept input parameters in their
1243 invocation function, and return only an error code directly. Further
1244 information about the result of the operation has to be retrieved
1245 afterwards by calling one of the result functions. This unifies the
1246 synchronous and the asynchronous interface.
1248 The error values have been completely replaced by a more
1249 sophisticated model that allows GPGME to transparently and accurately
1250 report all errors from the other GnuPG components, irregardless of
1251 process boundaries. This is achieved by using the library
1252 libgpg-errors, which is shared by all GnuPG components. This library
1253 is now required for GPGME.
1255 The results of all operations are now provided by pointers to C
1256 structs rather than by XML structs or in other ways.
1258 Objects which used to be opaque (for example a key) are now pointers
1259 to accessible structs, so no accessor functions are necessary.
1261 Backward compatibility is provided where it was possible without too
1262 much effort and did not collide with the overall sanitization effort.
1263 However, this is only for ease of transition. NO DEPRECATED FUNCTION
1264 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
1265 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
1266 Recommendations how to replace deprecated or removed functionality
1267 can be found within the description of each change.
1269 What follows are all changes to the interface and behaviour of GPGME
1272 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
1273 deprecated attributes will warn about use of obsolete functions and
1274 type definitions. You can suppress these warnings by passing
1275 -Wno-deprecated-declarations to the gcc command.
1277 * The following types have been renamed. The old types are still
1278 available as aliases, but they are deprecated now:
1280 GpgmeCtx gpgme_ctx_t
1281 GpgmeData gpgme_data_t
1282 GpgmeError gpgme_error_t
1283 GpgmeDataEncoding gpgme_data_encoding_t
1284 GpgmeSigStat gpgme_sig_stat_t
1285 GpgmeSigMode gpgme_sig_mode_t
1286 GpgmeAttr gpgme_attr_t
1287 GpgmeValidity gpgme_validity_t
1288 GpgmeProtocol gpgme_protocol_t
1289 GpgmeKey gpgme_key_t
1290 GpgmePassphraseCb gpgme_passphrase_cb_t
1291 GpgmeProgressCb gpgme_progress_cb_t
1292 GpgmeIOCb gpgme_io_cb_t
1293 GpgmeRegisterIOCb gpgme_register_io_cb_t
1294 GpgmeRemoveIOCb gpgme_remove_io_cb_t
1295 GpgmeEventIO gpgme_event_io_t
1296 GpgmeEventIOCb gpgme_event_io_cb_t
1297 GpgmeIOCbs gpgme_io_cbs
1298 GpgmeDataReadCb gpgme_data_read_cb_t
1299 GpgmeDataWriteCb gpgme_data_write_cb_t
1300 GpgmeDataSeekCb gpgme_data_seek_cb_t
1301 GpgmeDataReleaseCb gpgme_data_release_cb_t
1302 GpgmeDataCbs gpgme_data_cbs_t
1303 GpgmeTrustItem gpgme_trust_item_t
1304 GpgmeStatusCode gpgme_status_code_t
1306 * gpgme_error_t is now identical to gpg_error_t, the error type
1307 provided by libgpg-error. More about using libgpg-error with GPGME
1308 can be found in the manual. All error symbols have been removed!
1310 * All functions and types in libgpg-error have been wrapped in GPGME.
1311 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1312 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1313 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1314 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1317 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1319 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1320 for encrypt, sign, encrypt-sign, decrypt, verify, and
1321 decrypt-verify operations. For verify operations on detached
1322 signatures, the progress callback is invoked for both the detached
1323 signature and the plaintext message, though.
1325 * gpgme_passphrase_cb_t has been changed to not provide a complete
1326 description, but the UID hint, passphrase info and a flag
1327 indicating if this is a repeated attempt individually, so the user
1328 can compose his own description from this information.
1330 The passphrase is not returned as a C string, but must be written
1331 to a file descriptor directly. This allows for secure passphrase
1334 The return type has been changed to gpgme_error_t value. This
1335 allowed to remove the gpgme_cancel function; just return
1336 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1338 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1339 The user is expected to write the response to the file descriptor,
1340 followed by a newline.
1342 * The recipients interface has been removed. Instead, you use
1343 NULL-terminated lists of keys for specifying the recipients of an
1344 encryption operation. Use the new encryption flag
1345 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1346 the keys (but note that in general this is not a good idea).
1348 This change has been made to the prototypes of gpgme_op_encrypt,
1349 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1350 gpgme_op_encrypt_sign_start.
1352 The export interface has been changed to use pattern strings like
1353 the keylist interface. Thus, new functions gpgme_op_export_ext and
1354 gpgme_op_export_ext_start have been added as well. Now the
1355 prototypes of gpgme_op_export_start and gpgme_op_export finally
1358 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1359 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1362 * gpgme_io_cb_t changed from a void function to a function returning
1363 a gpgme_error_t value. However, it will always return 0, so you
1364 can safely ignore the return value.
1366 * A new I/O callback event GPGME_EVENT_START has been added. The new
1367 requirement is that you must wait until this event until you are
1368 allowed to call the I/O callback handlers previously registered for
1369 this context operation. Calling I/O callback functions for this
1370 context operation before the start event happened is unsafe because
1371 it can lead to race conditions in a multi-threaded environment.
1373 * The idle function feature has been removed. It was not precisely
1374 defined in a multi-threaded environment and is obsoleted by the
1375 user I/O callback functions. If you still need a simple way to
1376 call something while waiting on one or multiple asynchronous
1377 operations to complete, don't set the HANG flag in gpgme_wait (note
1378 that this will return to your program more often than the idle
1381 * gpgme_wait can return NULL even if hang is true, if an error
1382 occurs. In that case *status contains the error code.
1384 * gpgme_get_engine_info was radically changed. Instead an XML
1385 string, an info structure of the new type gpgme_engine_info_t is
1386 returned. This makes it easier and more robust to evaluate the
1387 information in an application.
1389 * The new function gpgme_get_protocol_name can be used to convert a
1390 gpgme_protocol_t value into a string.
1392 * The status of a context operation is not checked anymore. Starting
1393 a new operation will silently cancel the previous one. Calling a
1394 function that requires you to have started an operation before without
1395 doing so is undefined.
1397 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1398 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1399 pointer to a structure which contains the fingerprint. This also
1400 works with gpgme_op_genkey_start. The structure also provides
1401 other information about the generated keys.
1406 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1408 printf ("%s\n", fpr);
1412 gpgme_genkey_result_t result;
1413 err = gpgme_op_genkey (ctx, NULL, NULL);
1416 result = gpgme_op_genkey_result (ctx);
1418 printf ("%s\n", result->fpr);
1421 * The new gpgme_op_import_result function provides detailed
1422 information about the result of an import operation in
1423 gpgme_import_result_t and gpgme_import_status_t objects.
1424 Thus, the gpgme_op_import_ext variant is deprecated.
1426 * The new gpgme_op_sign_result function provides detailed information
1427 about the result of a signing operation in gpgme_sign_result_t,
1428 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1430 * The new gpgme_op_encrypt_result function provides detailed
1431 information about the result of an encryption operation in
1432 a GpgmeEncryptResult object.
1434 * The new gpgme_op_decrypt_result function provides detailed
1435 information about the result of a decryption operation in
1436 a GpgmeDecryptResult object.
1438 * The new gpgme_op_verify_result function provides detailed
1439 information about the result of an verify operation in
1440 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1441 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1442 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1443 and gpgme_get_notation is removed.
1445 * GpgmeTrustItem objects have now directly accessible data, so the
1446 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1447 accessor functions are deprecated. Also, reference counting is
1448 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1449 (the gpgme_trust_item_release alias for the latter is deprecated).
1451 * Keys are not cached internally anymore, so the force_update argument
1452 to gpgme_get_key has been removed.
1454 * GpgmeKey objects have now directly accessible data so the
1455 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1456 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1457 functions are deprecated. Also, gpgme_key_release is now
1458 deprecated. The gpgme_key_get_as_xml function has been dropped.
1460 * Because all interfaces using attributes are deprecated, the
1461 GpgmeAttr data type is also deprecated.
1463 * The new gpgme_op_keylist_result function provides detailed
1464 information about the result of a key listing operation in
1465 a GpgmeKeyListResult object.
1467 * Now that each function comes with its own result retrieval
1468 interface, the generic gpgme_get_op_info interface is not useful
1469 anymore and dropped.
1471 * The type and mode of data objects is not available anymore.
1473 * Interface changes relative to the 0.4.0 release:
1474 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1475 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1476 GpgmeData DEPRECATED: Use gpgme_data_t.
1477 GpgmeError DEPRECATED: Use gpgme_error_t.
1478 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1479 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1480 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1481 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1482 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1483 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1484 GpgmeKey DEPRECATED: Use gpgme_key_t.
1485 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1486 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1487 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1488 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1489 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1490 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1491 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1492 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1493 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1494 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1495 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1496 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1497 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1498 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1499 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1502 gpgme_recipients_t NEW
1504 gpgme_data_encoding_t NEW
1505 gpgme_sig_stat_t NEW
1506 gpgme_sig_mode_t NEW
1508 gpgme_validity_t NEW
1509 gpgme_protocol_t NEW
1511 gpgme_passphrase_cb_t NEW
1512 gpgme_progress_cb_t NEW
1514 gpgme_register_io_cb_t NEW
1515 gpgme_remove_io_cb_t NEW
1516 gpgme_event_io_t NEW
1517 gpgme_event_io_cb_t NEW
1519 gpgme_data_read_cb_t NEW
1520 gpgme_data_write_cb_t NEW
1521 gpgme_data_seek_cb_t NEW
1522 gpgme_data_release_cb_t NEW
1523 gpgme_data_cbs_t NEW
1524 gpgme_trust_item_t NEW
1525 gpgme_status_code_t NEW
1526 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1527 gpgme_err_code_t NEW
1528 gpgme_err_source_t NEW
1530 gpgme_err_source NEW
1533 gpgme_error_from_errno NEW
1534 gpgme_err_make_from_errno NEW
1535 gpgme_err_code_from_errno NEW
1536 gpgme_err_code_to_errno NEW
1538 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1539 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1540 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1541 gpgme_edit_cb_t CHANGED: Write directly to FD.
1542 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1543 gpgme_op_verify CHANGED: Drop R_STAT argument.
1544 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1545 gpgme_wait CHANGED: Can return NULL even if hang is true.
1546 GpgmeIdleFunc REMOVED
1547 gpgme_register_idle REMOVED
1548 GpgmeRecipients REMOVED
1549 gpgme_recipients_new REMOVED
1550 gpgme_recipients_release REMOVED
1551 gpgme_recipients_add_name REMOVED
1552 gpgme_recipients_add_name_with_validity REMOVED
1553 gpgme_recipients_count REMOVED
1554 gpgme_recipients_enum_open REMOVED
1555 gpgme_recipients_enum_read REMOVED
1556 gpgme_recipients_enum_close REMOVED
1557 gpgme_encrypt_flags_t NEW
1558 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1559 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1560 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1561 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1562 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1563 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1564 gpgme_op_export CHANGED: User IDs passed as patterns.
1565 gpgme_op_export_ext_start NEW
1566 gpgme_op_export_ext NEW
1567 gpgme_keylist_mode_t NEW
1569 gpgme_engine_info_t NEW
1570 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1571 gpgme_get_protocol_name NEW
1572 gpgme_cancel REMOVED: Return error in callback directly.
1573 gpgme_op_genkey CHANGED: FPR argument dropped.
1574 gpgme_op_genkey_result NEW
1575 gpgme_genkey_result_t NEW
1576 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1577 gpgme_op_import_result NEW
1578 gpgme_import_status_t NEW
1579 gpgme_import_result_t NEW
1580 gpgme_pubkey_algo_t NEW
1581 gpgme_hash_algo_t NEW
1582 gpgme_invalid_key_t NEW
1583 gpgme_new_signature_t NEW
1584 gpgme_sign_result_t NEW
1585 gpgme_op_sign_result NEW
1586 gpgme_pubkey_algo_name NEW
1587 gpgme_hash_algo_name NEW
1588 gpgme_encrypt_result_t NEW
1589 gpgme_op_encrypt_result NEW
1590 gpgme_decrypt_result_t NEW
1591 gpgme_op_decrypt_result NEW
1592 gpgme_verify_result_t NEW
1593 gpgme_op_verify_result NEW
1594 gpgme_get_notation REMOVED: Access verify result directly instead.
1595 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1596 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1597 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1598 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1599 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1600 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1601 gpgme_trust_item_ref NEW
1602 gpgme_trust_item_unref NEW
1603 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1604 gpgme_trust_item_get_string_attr DEPRECATED
1605 gpgme_trust_item_get_ulong_attr DEPRECATED
1606 gpgme_get_key CHANGED: Removed force_update argument.
1610 gpgme_key_t CHANGED: Now has user accessible data members.
1611 gpgme_key_get_string_attr DEPRECATED
1612 gpgme_key_get_ulong_attr DEPRECATED
1613 gpgme_key_sig_get_string_attr DEPRECATED
1614 gpgme_key_sig_get_ulong_attr DEPRECATED
1615 gpgme_key_get_as_xml REMOVED
1616 gpgme_key_list_result_t NEW
1617 gpgme_op_keylist_result NEW
1618 gpgme_get_op_info REMOVED
1619 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1621 Noteworthy changes in version 0.4.0 (2002-12-23)
1622 ------------------------------------------------
1624 * Key generation returns the fingerprint of the generated key.
1626 * New convenience function gpgme_get_key.
1628 * Supports signatures of user IDs in keys via the new
1629 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1630 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1631 interfaces. The XML info about a key also includes the signatures
1634 * New data object interface, which is more flexible and transparent.
1636 * Interface changes relative to the 0.3.9 release:
1637 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1639 GpgmeDataWriteCb NEW
1641 GpgmeDataReleaseCb NEW
1643 gpgme_data_read CHANGED: Match read() closely.
1644 gpgme_data_write CHANGED: Match write() closely.
1646 gpgme_data_new_from_fd NEW
1647 gpgme_data_new_from_stream NEW
1648 gpgme_data_new_from_cbs NEW
1649 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1650 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1651 gpgme_data_get_type REMOVED: No replacement.
1652 gpgme_op_verify CHANGED: Take different data objects for
1653 signed text and plain text.
1654 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1655 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1656 gpgme_op_genkey CHANGED: New parameter FPR.
1657 GPGME_KEYLIST_MODE_SIGS NEW
1658 gpgme_key_sig_get_string_attr NEW
1659 gpgme_key_sig_get_ulong_attr NEW
1661 GPGME_ATTR_SIG_CLASS NEW
1662 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1664 Noteworthy changes in version 0.3.16 (2003-11-19)
1665 -------------------------------------------------
1667 * Compatibility fixes for GnuPG 1.9.x
1669 Noteworthy changes in version 0.3.15 (2003-02-18)
1670 -------------------------------------------------
1672 * The progress status is sent via the progress callbacks in
1675 * Bug fix for signing operations with explicit signer settings for
1678 Noteworthy changes in version 0.3.14 (2002-12-04)
1679 -------------------------------------------------
1681 * GPGME-Plug is now in its own package "cryptplug".
1683 * Workaround for a setlocale problem. Fixed a segv related to not
1684 correctly as closed marked file descriptors.
1686 Noteworthy changes in version 0.3.13 (2002-11-20)
1687 -------------------------------------------------
1689 * Release due to changes in gpgmeplug.
1691 Noteworthy changes in version 0.3.12 (2002-10-15)
1692 -------------------------------------------------
1694 * Fixed some bux with key listings.
1696 * The development has been branched to clean up some API issues.
1697 This 0.3 series will be kept for compatibility reasons; so do don't
1698 expect new features.
1700 Noteworthy changes in version 0.3.11 (2002-09-20)
1701 -------------------------------------------------
1705 Noteworthy changes in version 0.3.10 (2002-09-02)
1706 -------------------------------------------------
1708 * Setting the signing keys for the CMS protocol does now work.
1710 * The signers setting is honoured by gpgme_op_edit.
1712 Noteworthy changes in version 0.3.9 (2002-08-21)
1713 ------------------------------------------------
1715 * A spec file for creating RPMs has been added.
1717 * An experimental interface to GnuPG's --edit-key functionality is
1718 introduced, see gpgme_op_edit.
1720 * The new gpgme_import_ext function provides a convenient access to
1721 the number of processed keys.
1723 * Interface changes relative to the 0.3.8 release:
1724 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1727 gpgme_op_edit_start NEW
1729 gpgme_op_import_ext NEW
1730 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1732 Noteworthy changes in version 0.3.8 (2002-06-25)
1733 ------------------------------------------------
1735 * It is possible to use an outside event loop for the I/O to the
1736 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1738 * Interface changes relative to the 0.3.6 release:
1739 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1741 GpgmeRegisterIOCb NEW
1745 struct GpgmeIOCbs NEW
1746 gpgme_set_io_cbs NEW
1747 gpgme_get_io_cbs NEW
1748 GPGME_ATTR_ERRTOK NEW
1749 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1751 Noteworthy changes in version 0.3.7 (2002-06-04)
1752 ------------------------------------------------
1754 * GPGME_ATTR_OTRUST is implemented now.
1756 * A first step toward thread safeness has been achieved, see the
1757 documentation for details. Supported thread libraries are pthread
1760 Noteworthy changes in version 0.3.6 (2002-05-03)
1761 ------------------------------------------------
1763 * All error output of the gpgsm backend is send to the bit bucket.
1765 * The signature verification functions are extended. Instead of
1766 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1767 expired signatures. 2 new functions may be used to retrieve more
1768 detailed information like the signature expiration time and a
1769 validity information of the key without an extra key looking.
1771 * The current passphrase callback and progress meter callback can be
1772 retrieved with the new functions gpgme_get_passphrase_cb and
1773 gpgme_get_progress_cb respectively.
1775 * Interface changes relative to the 0.3.5 release:
1776 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1777 gpgme_get_passphrase_cb NEW
1778 gpgme_get_progress_cb NEW
1779 GpgmeDataEncoding NEW
1780 gpgme_data_set_encoding NEW
1781 gpgme_data_get_encoding NEW
1782 GPGME_SIG_STAT_GOOD_EXP NEW
1783 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1784 gpgme_op_verify CHANGED: Returns more status codes.
1785 GPGME_ATTR_SIG_STATUS NEW
1786 gpgme_get_sig_string_attr NEW
1787 gpgme_get_sig_ulong_attr NEW
1788 gpgme_get_protocol NEW
1789 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1791 Noteworthy changes in version 0.3.5 (2002-04-01)
1792 ------------------------------------------------
1794 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1795 case, symmetric encryption is performed. Note that this requires a
1796 passphrase from the user.
1798 * More information is returned for X.509 certificates.
1800 * Interface changes relative to the 0.3.4 release:
1801 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1802 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1803 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1805 Noteworthy changes in version 0.3.4 (2002-03-04)
1806 ------------------------------------------------
1808 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1809 some recipients have been invalid, whereas earlier versions
1810 succeeded in this case. The plaintext is still encrypted for all valid
1811 recipients, so the application might take this error as a hint that
1812 the ciphertext is not usable for all requested recipients.
1813 Information about invalid recipients is available with gpgme_get_op_info.
1815 * gpgme_op_verify now allows to pass an uninitialized data object as
1816 its plaintext argument to check for normal and cleartext
1817 signatures. The plaintext is then returned in the data object.
1819 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1820 to set and get the number of certifications to include in S/MIME
1823 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1824 to encrypt and sign a message in a combined operation.
1826 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1828 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1830 * Interface changes relative to the 0.3.3 release:
1831 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1832 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1833 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1834 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1835 gpgme_set_include_certs NEW
1836 gpgme_get_include_certs NEW
1837 gpgme_op_encrypt_sign NEW
1838 gpgme_op_encrypt_sign_start NEW
1839 gpgme_op_keylist_ext_start NEW
1840 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1842 Noteworthy changes in version 0.3.3 (2002-02-12)
1843 ------------------------------------------------
1845 * Fix the Makefile in jnlib.
1847 * Fix the test suite (hopefully). It should clean up all its state
1848 with `make check' now.
1851 Noteworthy changes in version 0.3.2 (2002-02-10)
1852 ------------------------------------------------
1854 * Remove erroneous dependency on libgcrypt in jnlib.
1857 Noteworthy changes in version 0.3.1 (2002-02-09)
1858 ------------------------------------------------
1860 * There is a Texinfo manual documenting the API.
1862 * The gpgme_set_keylist_mode function returns an error, and changed
1863 its meaning. It is no longer usable to select between normal and
1864 fast mode (newer versions of GnuPG will always be fast), but
1865 selects between local keyring, remote keyserver, or both.
1866 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1867 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1868 current setting, a fucntion gpgme_get_keylist_mode was added to
1869 retrieve the current mode.
1871 * gpgme_wait accepts a new argument STATUS to return the error status
1872 of the operation on the context. Its definition is closer to
1873 waitpid() now than before.
1875 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1876 type from off_t to the unsigned size_t.
1878 * The R_HD argument to the GpgmePassphraseCb type changed its type
1879 from void* to void**.
1881 * New interface gpgme_op_trustlist_end() to match
1882 gpgme_op_keylist_end().
1884 * The CryptPlug modules have been renamed to gpgme-openpgp and
1885 gpgme-smime, and they are installed in pkglibdir by `make install'.
1887 * An idle function can be registered with gpgme_register_idle().
1889 * The GpgSM backend supports key generation with gpgme_op_genkey().
1891 * Interface changes relative to the 0.3.0 release:
1892 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1893 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1894 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1895 gpgme_wait CHANGED: New argument STATUS.
1896 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1897 The function has a new meaning!
1898 gpgme_get_keylist_mode NEW
1899 GPGME_KEYLIST_MODE_LOCAL NEW
1900 GPGME_KEYLIST_MODE_EXTERN NEW
1901 gpgme_op_trustlist_next NEW
1903 gpgme_register_idle NEW
1904 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1906 Noteworthy changes in version 0.3.0 (2001-12-19)
1907 ------------------------------------------------
1909 * New interface gpgme_set_protocol() to set the protocol and thus the
1910 crypto engine to be used by the context. Currently, the OpenPGP
1911 and the CMS protocols are supported. They are specified by the new
1912 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1913 A new context uses the OpenPGP engine by default.
1915 * gpgme_get_engine_info() returns information for all crypto engines
1916 compiled into the library. The XML format has changed. To
1917 reliably get the version of a crypto engine, the <version> tag
1918 after the appropriate <protocol> tag has to be looked for.
1920 * New interface gpgme_engine_check_version(), obsoleting
1921 gpgme_check_engine(). Check the version of all engines you are
1922 supporting in your software.
1924 * GpgmeKey lists the user ids in the order as they are returned by
1925 GnuPG, first the primary key with index 0, then the sub-user ids.
1927 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1928 signatures simultaneously.
1930 * The new interface gpgme_op_keylist_end() terminates a pending
1931 keylist operation. A keylist operation is also terminated when
1932 gpgme_op_keylist_next() returns GPGME_EOF.
1934 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1935 cross-compiled, or even compiled without support for GnuPG
1938 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1939 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1940 in the path, but it can also be compiled without support for GpgSM
1941 (`--without-gpgsm').
1943 * CryptPlug modules for GPGME are included and can be enabled at
1944 configure time (`--enable-gpgmeplug'). There is one module which
1945 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1946 GpgSM engine (`gpgsmplug').
1948 * Interface changes relative to the latest 0.2.x release:
1949 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1950 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1951 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1952 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1953 gpgme_get_engine_info CHANGED: New format, extended content.
1954 gpgme_engine_check_version NEW
1955 gpgme_decrypt_verify_start NEW
1956 gpgme_decrypt_verify NEW
1957 gpgme_op_keylist_next NEW
1958 gpgme_set_protocol NEW
1959 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1962 Noteworthy changes in version 0.2.3 (2001-09-17)
1963 ------------------------------------------------
1965 * New function gpgme_get_op_info which can be used to get the micalg
1966 parameter needed for MOSS.
1968 * New functions gpgme_get_armor and gpgme_get_textmode.
1970 * The usual bug fixes and some minor functionality improvements.
1972 * Added a simple encryption component for MS-Windows; however the
1973 build procedure might have some problems.
1976 Noteworthy changes in version 0.2.2 (2001-06-12)
1977 ------------------------------------------------
1979 * Implemented a key cache.
1981 * Fixed a race condition under W32 and some other bug fixes.
1984 Noteworthy changes in version 0.2.1 (2001-04-02)
1985 ------------------------------------------------
1987 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1989 * Handle GnuPG's new key capabilities output and support revocation
1992 * Made the W32 support more robust.
1995 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
1998 This file is free software; as a special exception the author gives
1999 unlimited permission to copy and/or distribute it, with or without
2000 modifications, as long as this notice is preserved.
2002 This file is distributed in the hope that it will be useful, but
2003 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
2004 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.