1 Noteworthy changes in version 1.13.1 (2019-06-13)
2 -------------------------------------------------
4 * cpp: gpgme_set_global_flag is now wrapped. [#4471]
6 * w32: Improved handling of unicode install paths. [#4453]
8 * w32: The gpgme_io_spawn error message is now only shown once. [#4453]
10 * Fixed a crash introduced in 1.13.0 when working with S/MIME. [#4556]
12 * w32: Fixed format string errors introduced in 1.13.0 that could
13 cause crashes. [#4440]
15 * w32: Fixed an error in the new diagnostic gpgsm support introduced
16 in 1.13.0 that caused crashes in low fd scenarios. [#4439]
18 * python: Fixed a DecryptionError Exception. [#4478]
20 * python: No longer raises BadSignatures from decrypt(verify=True).
23 * Interface changes relative to the 1.13.0 release:
24 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
25 cpp: setGlobalFlag NEW.
27 [c=C33/A22/R1 cpp=C16/A10/R0 qt=C10/A3/R4]
29 Release-info: https://dev.gnupg.org/T4551
32 Noteworthy changes in version 1.13.0 (2019-03-26)
33 -------------------------------------------------
35 * Support GPGME_AUDITLOG_DIAG for gpgsm. [#4426]
37 * New context flag "trust-model".
39 * Removed support for WindowsCE and Windows ME.
41 * Aligned the gpgrt-config code with our other libaries.
43 * Auto-check for all installed Python versions. [#3354]
45 * Fixed generating card key in the C++ bindings. [#4428]
47 * Fixed a segv due to bad parameters in genkey. [#4192]
49 * Fixed crash if the plaintext is ignored in a CMS verify.
51 * Fixed memleak on Windows. [T4238]
53 * Tweaked the Windows I/O code.
55 * Fixed random crashes on Windows due to closing an arbitrary
58 * Fixed a segv on Windows. [#4369]
60 * Fixed test suite problems related to dtags. [#4298]
62 * Fixed bunch of python bugs. [#4242,commit 9de1c96ac3cf]
64 * Several fixes to the Common Lisp bindings.
66 * Fixed minor bugs in gpgme-json. [#4331,#4341,#4342,#4343
68 * Require trace level 8 to dump all I/O data.
70 * The compiler must now support variadic macros.
72 * Interface changes relative to the 1.12.0 release:
73 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
74 gpgme_set_ctx_flag EXTENDED: New flag 'trust-model'.
75 cpp: Context::create NEW.
77 cpp: Subkey::isBad NEW.
78 cpp: UserID::isBad NEW.
79 cpp: UserID::Signature::isBad NEW.
80 cpp: GenCardKeyInteractor::setAlgo NEW.
82 [c=C33/A22/R0 cpp=C15/A9/R0 qt=C10/A3/R3]
84 Release-info: https://dev.gnupg.org/T4376
87 Noteworthy changes in version 1.12.0 (2018-10-08)
88 -------------------------------------------------
90 * Enhanced the JSON based interface tool gpgme-json to support Native
91 Messaging as well as new Javascript code to support the browser
92 site. See lang/js/README for details.
94 * Major overhaul of the Python language bindings documentation.
96 * Even for old versions of gpg a missing MDC will now lead to a
99 * Added context flag "auto-key-locate" to control the
100 behavior of GPGME_KEYLIST_MODE_LOCATE.
102 * New data function to create a data object from an estream.
104 * Add more interfaces to the C++ bindings.
106 * Improved error codes on decryption failure.
108 * Lots of minor fixes.
110 * Interface changes relative to the 1.11.1 release:
111 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
112 gpgme_data_new_from_estream NEW.
113 gpgme_decrypt_result_t EXTENDED: New field legacy_cipher_nomdc.
114 gpgme_set_ctx_flag EXTENDED: New flag 'ignore-mdc-error'.
115 GPGME_AUDITLOG_DEFAULT NEW.
116 GPGME_AUDITLOG_DIAG NEW.
117 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-locate'.
118 cpp: DecryptionResult::sessionKey NEW.
119 cpp: DecryptionResult::symkeyAlgo NEW.
120 cpp: DecryptionResult::isLegacyCipherNoMDC New.
121 cpp: Data::rewind NEW.
122 cpp: Context::setFlag NEW.
123 cpp: Context::getFlag NEW.
124 cpp: Context::createKeyEx NEW.
126 [c=C32/A21/R0 cpp=C14/A8/R0 qt=C10/A3/R2]
128 Release-info: https://dev.gnupg.org/T4109
131 Noteworthy changes in version 1.11.1 (2018-04-20)
132 -------------------------------------------------
134 * Fixed build problems in the 1.11.0 release.
136 * Added C++ interfaces which were planned for 1.11.0.
138 * Interface changes relative to the 1.10.0 release:
139 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
140 cpp: Key::origin NEW.
141 cpp: Key::lastUpdate NEW.
142 cpp: UserID::origin NEW.
143 cpp: UserID::lastUpdate NEW.
145 [c=C31/A20/R1 cpp=C13/A7/R0 qt=C10/A3/R2]
148 Noteworthy changes in version 1.11.0 (2018-04-18)
149 -------------------------------------------------
151 * New encryption API to support direct key specification including
152 hidden recipients option and taking keys from a file. This also
153 allows to enforce the use of a subkey.
155 * New encryption flag for the new API to enforce the use of plain
156 mail addresses (addr-spec).
158 * The import API can now tell whether v3 keys are skipped. These old
159 and basically broken keys are not anymore supported by GnuPG 2.1.
161 * The decrypt and verify API will now return the MIME flag as
162 specified by RFC-4880bis.
164 * The offline mode now has an effect on gpg by disabling all network
167 * A failed OpenPGP verification how returns the fingerprint of the
168 intended key if a recent gpg version was used for signature
171 * New tool gpgme-json as native messaging server for web browsers.
172 As of now public key encryption and decryption is supported.
173 Requires Libgpg-error 1.29.
175 * New context flag "request-origin" which has an effect when used
176 with GnuPG 2.2.6 or later.
178 * New context flag "no-symkey-cache" which has an effect when used
179 with GnuPG 2.2.7 or later.
181 * New convenience constant GPGME_KEYLIST_MODE_LOCATE.
183 * Improved the Python documentation.
185 * Fixed a potential regression with GnuPG 2.2.6 or later.
187 * Fixed a crash in the Python bindings on 32 bit platforms. [#3892]
189 * Various minor fixes.
191 * Interface changes relative to the 1.10.0 release:
192 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
193 gpgme_op_encrypt_ext NEW.
194 gpgme_op_encrypt_ext_start NEW.
195 gpgme_op_encrypt_sign_ext NEW.
196 gpgme_op_encrypt_sign_ext_start NEW.
197 GPGME_ENCRYPT_WANT_ADDRESS NEW.
198 GPGME_KEYLIST_MODE_LOCATE NEW.
199 gpgme_import_result_t EXTENDED: New field 'skipped_v3_keys'.
200 gpgme_decrypt_result_t EXTENDED: New field 'symkey_algo'.
201 gpgme_decrypt_result_t EXTENDED: New field 'is_mime'.
202 gpgme_verify_result_t EXTENDED: New field 'is_mime'.
203 cpp: Key::locate NEW.
204 cpp: Data::toString NEW.
205 cpp: ImportResult::numV3KeysSkipped NEW.
207 [c=C31/A20/R0 cpp=C12/A6/R0 qt=C10/A3/R1]
210 Noteworthy changes in version 1.10.0 (2017-12-12)
211 -------------------------------------------------
213 * Now returns more specific error codes for decryption to distinguish
214 between bad passphrase, user canceled, and no secret key.
216 * Now returns key origin information if available.
218 * Added context flag "auto-key-retrieve" to selectively enable the
219 corresponding gpg option.
221 * Added flag is_de_vs to decryption and verify results.
223 * py: Use SEEK_SET as default for data.seek.
225 * cpp: Various new APIs.
227 * Reduced spawn overhead on Linux again. Added new configure option
228 --disable-linux-getdents to disable this feature for very old
231 * Improved the Python bindings build system.
233 * Made the test suite less fragile.
235 * Interface changes relative to the 1.9.0 release:
236 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
237 gpgme_decrypt_result_t EXTENDED: New field 'is_de_vs'.
238 gpgme_signature_t EXTENDED: New field 'is_de_vs'.
240 gpgme_op_delete_ext NEW.
241 gpgme_op_delete_ext_start NEW.
242 GPGME_DELETE_ALLOW_SECRET NEW.
243 GPGME_DELETE_FORCE NEW.
244 gpgme_op_conf_dir NEW.
245 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-retrieve'.
246 cpp: DecryptionResult::isDeVs NEW.
247 cpp: Signature::isDeVs NEW.
248 cpp: EngineInfo::Version::operator> NEW.
249 cpp: Context::createKey NEW.
250 cpp: Context::startCreateKey NEW.
251 cpp: Context::createSubkey NEW.
252 cpp: Context::startCreateSubkey NEW.
254 py: DecryptResult EXTENDED: New boolean field 'is_de_vs'.
255 py: Signature EXTENDED: New boolean field 'is_de_vs'.
256 py: GpgError EXTENDED: Partial results in 'results'.
258 [c=C30/A19/R0 cpp=C11/A5/R0 qt=C10/A3/R0]
261 Noteworthy changes in version 1.9.0 (2017-03-28)
262 ------------------------------------------------
264 * Clarified meaning of the 'expire' parameter of gpgme_op_createkey
265 and gpgme_op_createsubkey. New flag to force a key without an
268 * New function gpgme_op_keylist_from_data_start to list keys from
269 data objects without importing them.
271 * New function gpgme_op_set_uid_flag to flag a key as primary.
273 * New function gpgme_op_decrypt_ext to run decryption with special
274 flags. This can for example be used to unwrap keys (remove only
275 the encryption layer).
277 * New encryption flags to wrap a key (adding an encryption layer to
278 an OpenPGP message) or to create anonymously encrypted messages.
280 * Support for adduid and revuid operations in the C++ bindings.
282 * Support for smartcard key generation in the C++ bindings.
284 * Several new functions for the Python binding.
286 * Many smaller bug fixes.
288 * Interface changes relative to the 1.8.0 release:
289 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
290 gpgme_op_createkey CHANGED: Meaning of 'expire' parameter.
291 gpgme_op_createsubkey CHANGED: Meaning of 'expire' parameter.
292 GPGME_CREATE_NOEXPIRE NEW.
293 gpgme_key_t EXTENDED: New field 'origin'.
294 gpgme_key_t EXTENDED: New field 'last_update'.
295 gpgme_subkey_t EXTENDED: New field 'is_de_vs'.
296 gpgme_user_id_t EXTENDED: New field 'origin'.
297 gpgme_user_id_t EXTENDED: New field 'last_update'.
298 gpgme_op_keylist_from_data_start NEW.
299 gpgme_op_set_uid_flag_start NEW.
300 gpgme_op_set_uid_flag NEW.
301 gpgme_op_decrypt_ext_start NEW.
302 gpgme_op_decrypt_ext NEW.
303 GPGME_ENCRYPT_THROW_KEYIDS NEW.
304 GPGME_ENCRYPT_WRAP NEW.
305 GPGME_DECRYPT_VERIFY NEW.
306 GPGME_DECRYPT_UNWRAP NEW.
307 gpgme_data_rewind UN-DEPRECATE.
308 cpp: Context::revUid(const Key&, const char*) NEW.
309 cpp: Context::startRevUid(const Key&, const char*) NEW.
310 cpp: Context::addUid(const Key&, const char*) NEW.
311 cpp: Context::startAddUid(const Key&, const char*) NEW.
312 cpp: Key::UserID::revoke() NEW.
313 cpp: Key::addUid() NEW.
314 cpp: Key::isDeVs NEW.
315 cpp: GpgGenCardKeyInteractor NEW.
316 cpp: Subkey::keyGrip NEW.
317 cpp: Subkey::isDeVs NEW.
318 cpp: Data::toKeys NEW.
319 cpp: Context::setDecryptFlags NEW.
320 cpp: Context::decrypt EXTENDED: Flags added.
321 cpp: Context::startDecrypt EXTENDED: Flags added.
322 cpp: Context::decryptAndVerify EXTENDED: Flags added.
323 cpp: Context::startCombinedDecryptionAndVerification EXTENDED: Flags.
324 cpp: Context::encryptFlags EXTENDED: New flags.
325 qt: CryptoConfig::stringValueList() NEW.
326 py: Context.__init__ EXTENDED: New keyword arg home_dir.
327 py: Context.home_dir NEW.
328 py: Context.keylist EXTENDED: New keyword arg mode.
329 py: Context.keylist EXTENDED: New keyword arg source.
330 py: Context.create_key NEW.
331 py: Context.create_subkey NEW.
332 py: Context.key_add_uid NEW.
333 py: Context.key_revoke_uid NEW.
334 py: Context.key_sign NEW.
335 py: Context.key_tofu_policy NEW.
336 py: core.pubkey_algo_string NEW.
337 py: core.addrspec_from_uid NEW.
339 [c=C29/A18/R0 cpp=C10/A4/R0 qt=C9/A2/R0]
342 Noteworthy changes in version 1.8.0 (2016-11-16)
343 ------------------------------------------------
345 * The module of the Python bindings has been renamed to 'gpg'.
347 * New interface to query current software versions.
349 * New feature to use gpg's --{show,override}session-key options.
351 * New interface to set the sender of a mail.
353 * qt: Added Distinguished Name parser from libkleo
355 * The --homedir option is now used with recent gpgconf versions.
357 * On 64 bit Windows systems gpgconf is now properly located.
359 * The internal locking functions have been replaced by libgpg-error
362 * Interface changes relative to the 1.7.1 release:
363 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
364 gpgme_set_sender NEW.
365 gpgme_get_sender NEW.
366 gpgme_op_query_swdb NEW.
367 gpgme_op_query_swdb_result NEW.
368 gpgme_query_swdb_result_t NEW.
369 gpgme_get_ctx_flag NEW.
370 gpgme_decrypt_result_t EXTENDED: New field session_key.
372 qt: DN::Attribute NEW.
373 qt: Job::context(Job*) NEW.
374 cpp: EngineInfo::Version::Version(const char*) NEW.
375 cpp: EngineInfo::Version::Version() NEW.
377 cpp: Context::setSender(const char*) NEW.
378 cpp: Context::getSender() NEW.
380 [c=C28/A17/R0 cpp=C9/A3/R0 qt=C8/A1/R0]
383 Noteworthy changes in version 1.7.1 (2016-10-18)
384 ------------------------------------------------
386 * Fixed problems with the new language bindings.
388 * New helper function gpgme_addrspec_from_uid.
390 * Use option --exit-on-status-write-error with newer gpg versions.
392 * qt: Missed API from the Qt Binding inclusion has
395 * qt: abstractimportjob.h is now installed to that
396 ImportJobs can be used again.
398 * qt: Fixed spelling error in API (startReceive).
400 * Interface changes relative to the 1.7.0 release:
401 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
402 gpgme_addrspec_from_uid NEW.
403 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
404 qt: MultiDeleteJob NEW.
405 qt: AbstractImportJob NEW.
407 cpp: Signature::key(bool, bool) NEW.
408 cpp: UserID::addrSpecFromString(const char*) NEW.
409 cpp: UserID::addrSpec() NEW.
411 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
414 Noteworthy changes in version 1.7.0 (2016-09-21)
415 ------------------------------------------------
417 * New language bindings for Python 2 and 3.
419 * New language Bindings for C++ and the Qt-Framework API.
421 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
422 key creation easier (requires GnuPG 2.1).
424 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
425 management easier (requires GnuPG 2.1).
427 * New function gpgme_op_keysign to make key signing easier (requires
430 * New function gpgme_op_interact to replace the now deprecated
431 functions gpgme_op_edit and gpgme_op_card_edit.
433 * New function gpgme_pubkey_algo_string to convert a public key
434 algorithm into a GnuPG 2.1 style string.
436 * Support for GnuPG 2.1's TOFU trust model.
438 * Notation flags are now correctly set on verify.
440 * New global flag "require-gnupg" to set a minimal gnupg version.
442 * More supported items in gpgme_get_dirinfo.
444 * New function gpgme_data_set_flag and flag "size-hint".
446 * New function gpgme_set_ctx_flag and flags "full-status" and
449 * Improved gpgme_data_identify to distinguish more file types.
451 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
452 mixed public key and symmetric encryption.
454 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
456 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
457 signed data is a valid MIME part. This is to support future GnuPG
460 * Interface changes relative to the 1.6.0 release:
461 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
462 gpgme_pubkey_algo_string NEW.
464 gpgme_set_ctx_flag NEW.
465 gpgme_data_set_flag NEW.
466 gpgme_op_createkey NEW.
467 gpgme_op_createkey_start NEW.
468 gpgme_op_createsubkey NEW.
469 gpgme_op_createsubkey_start NEW.
470 gpgme_op_adduid_start NEW.
472 gpgme_op_revuid_start NEW.
474 gpgme_op_keysign_start NEW.
475 gpgme_op_keysign NEW.
476 gpgme_op_tofu_policy_start NEW.
477 gpgme_op_tofu_policy NEW.
478 gpgme_op_interact_start NEW.
479 gpgme_op_interact NEW.
480 gpgme_interact_cb_t NEW.
481 gpgme_op_edit_start DEPRECATED.
482 gpgme_op_edit DEPRECATED.
483 gpgme_op_card_edit_start DEPRECATED.
484 gpgme_op_card_edit DEPRECATED.
485 gpgme_edit_cb_t DEPRECATED.
486 gpgme_status_code_t DEPRECATED.
487 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
488 gpgme_signature_t EXTENDED: New field key.
489 gpgme_key_t EXTENDED: New field fpr.
490 gpgme_subkey_t EXTENDED: New field keygrip.
491 gpgme_user_id_t EXTENDED: New field tofu.
492 gpgme_tofu_policy_t NEW.
493 gpgme_tofu_info_t NEW.
494 GPGME_STATUS_KEY_CONSIDERED NEW.
495 GPGME_STATUS_TOFU_USER NEW.
496 GPGME_STATUS_TOFU_STATS NEW.
497 GPGME_STATUS_TOFU_STATS_LONG NEW.
498 GPGME_STATUS_NOTATION_FLAGS NEW.
499 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
500 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
501 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
502 GPGME_DATA_ENCODING_MIME NEW.
503 GPGME_ENCRYPT_SYMMETRIC NEW.
504 GPGME_CREATE_SIGN NEW.
505 GPGME_CREATE_ENCR NEW.
506 GPGME_CREATE_CERT NEW.
507 GPGME_CREATE_AUTH NEW.
508 GPGME_CREATE_NOPASSWD NEW.
509 GPGME_CREATE_SELFSIGNED NEW.
510 GPGME_CREATE_NOSTORE NEW.
511 GPGME_CREATE_WANTPUB NEW.
512 GPGME_CREATE_WANTSEC NEW.
513 GPGME_CREATE_FORCE NEW.
514 GPGME_KEYSIGN_LOCAL NEW.
515 GPGME_KEYSIGN_LFSEP NEW.
516 GPGME_INTERACT_CARD NEW.
518 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
521 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
522 ------------------------------------------------
524 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
526 * Added gpgme_set_status_cb to allow a user to see some status
529 * Added an export mode for secret keys.
531 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
533 * The passphrase handler for the loopback mode has been improved and may
534 also be used with genkey.
536 * [w32] The standard GnuPG 2.1 install directory is now searched for
537 gpgconf.exe before a registry specified directory and the Gpg4win
540 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
543 * Interface changes relative to the 1.5.1 release:
544 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
545 gpgme_set_offline NEW.
546 gpgme_get_offline NEW.
547 gpgme_set_status_cb NEW.
548 gpgme_get_status_cb NEW.
549 GPGME_EXPORT_MODE_SECRET NEW
550 GPGME_EXPORT_MODE_RAW NEW.
551 GPGME_EXPORT_MODE_PKCS12 NEW.
554 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
555 ------------------------------------------------
557 * Fixed crash in key listings for user ids with a backslash.
559 * Fixed regression for GPGSM use with GnuPG < 2.1.
561 * Properly set signature summary for revoked OpenPGP keys.
564 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
565 ------------------------------------------------
567 * Fixed a possible crash in the debug code.
569 * Fixed building for Windows with newer versions of Mingw.
572 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
573 -------------------------------------------------------------
575 * The export key functions do now return an error if used with the
576 latest GnuPG version.
579 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
580 -------------------------------------------------------------
582 * gpgme-tool is now installed.
584 * Fix external listing for modern keyservers.
589 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
590 -------------------------------------------------------------
592 * Fixed possible overflow in gpgsm and uiserver engines.
595 * Added support for GnuPG 2.1's --with-secret option.
597 * Interface changes relative to the 1.5.0 release:
598 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
599 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
602 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
603 -------------------------------------------------------------
605 * On Unices the engine file names are not not anymore hardwired but
606 located via the envvar PATH. All options to set the name of the
607 engines for the configure run are removed.
609 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
610 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
611 is not found, GPGME looks for an engine named "gpg".
613 * New feature to use the gpgme I/O subsystem to run arbitrary
616 * New flag to use encryption without the default compression step.
618 * New function to access "gpg-conf --list-dirs"
620 * New configure option --enable-fixed-path for use by Android.
622 * Support ECC algorithms.
624 * Interface changes relative to the 1.4.3 release:
625 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
626 gpgme_get_dirinfo NEW.
627 gpgme_op_spawn_start NEW.
629 GPGME_PROTOCOL_SPAWN NEW.
630 GPGME_SPAWN_DETACHED NEW.
631 GPGME_SPAWN_ALLOW_SET_FG NEW.
632 GPGME_ENCRYPT_NO_COMPRESS NEW.
635 gpgme_subkey_t EXTENDED: New field curve.
636 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
637 GPGME_STATUS_MOUNTPOINT NEW.
638 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
639 GPGME_STATUS_ATTRIBUTE NEW.
640 GPGME_STATUS_BEGIN_SIGNING NEW.
641 GPGME_STATUS_KEY_NOT_CREATED NEW.
644 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
645 -------------------------------------------------------------
647 * The default engine names are now taken from the output of gpgconf.
648 If gpgconf is not found the use of gpg 1 is assumed.
650 * Under Windows the default engines names are first searched in the
651 installation directory of the gpgme DLL.
653 * New function gpgme_data_identify to detect the type of a message.
655 * Interface changes relative to the 1.4.2 release:
656 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
657 gpgme_signers_count NEW.
658 gpgme_data_type_t NEW.
659 gpgme_data_identify NEW.
662 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
663 -------------------------------------------------------------
665 * Allow symmetric encryption with gpgme_op_encrypt_sign.
667 * Fixed mismatching off_t definitions on Windows.
669 * Interface changes relative to the 1.4.1 release:
670 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
673 GPGME_PROTOCOL_OPENPGP NEW alias.
676 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
677 ------------------------------------------------------------
679 * Fixed reading of gpg.conf files with excessive use of the group
682 * Fixed building with the i686-w64-mingw32 toolchain.
684 * Disabled FD passing by default for Apple.
687 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
688 ------------------------------------------------------------
690 * New function gpgme_set_global_flag to help debugging on Android.
692 * New function gpgme_io_writen as a convenience wrapper around
695 * New functions to support the pinentry mode feature of GnuPG 2.1.
697 * New macro GPGME_VERSION_NUMBER to allow supporting different API
698 versions without the need for a configure test.
700 * Several improvements for gpgme-tool.
702 * Better logging of the common "invalid engine" error code.
704 * Support for FD passing is now enabled by default. The configure
705 option --disable-fd-passing may be used to disable this.
707 * Interface changes relative to the 1.3.1 release:
708 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
709 GPGME_VERSION_NUMBER NEW.
711 gpgme_set_global_flag NEW.
712 gpgme_set_pinentry_mode NEW.
713 gpgme_get_pinentry_mode NEW.
714 gpgme_pinentry_mode_t NEW.
715 GPGME_PINENTRY_MODE_DEFAULT NEW.
716 GPGME_PINENTRY_MODE_ASK NEW.
717 GPGME_PINENTRY_MODE_CANCEL NEW.
718 GPGME_PINENTRY_MODE_ERROR NEW.
719 GPGME_PINENTRY_MODE_LOOPBACK NEW.
722 Noteworthy changes in version 1.3.2 (2012-05-02)
723 ------------------------------------------------
725 * Remove support for libgpgme-pth. As far as we know, this was never used,
726 and GnuPG is going to use our own npth in the future.
728 * Fix signature summary information for a missing X.509 key.
730 * Fix parsing of dates >= year 2038.
733 Noteworthy changes in version 1.3.1 (2011-06-16)
734 ------------------------------------------------
736 * Ported to Windows CE.
738 * Detect GPG versions not supporting ---passwd.
740 * Interface changes relative to the 1.3.0 release:
741 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
742 GPGME_EXPORT_MODE_MINIMAL NEW
743 GPGME_STATUS_SUCCESS NEW
744 gpgme_err_code_from_syserror NEW
745 gpgme_err_set_errno NEW
746 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
747 gpgme_error_from_syserror NEW
748 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
751 Noteworthy changes in version 1.3.0 (2010-01-11)
752 ------------------------------------------------
754 * GPGME does not come with an internal libassuan version anymore.
755 The external libassuan 1.1.0 release or later is required. For
756 application programmers on systems that can resolve inter-library
757 dependencies at runtime, this is a transparent change.
759 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
761 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
763 * New API to change the passphrase of a key.
765 * Interface changes relative to the 1.2.0 release:
766 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
767 GPGME_STATUS_INV_SGNR NEW.
768 GPGME_STATUS_NO_SGNR NEW.
769 GPGME_PROTOCOL_G13 NEW.
770 gpgme_op_g13_mount NEW.
771 gpgme_g13_result_t NEW.
774 gpgme_op_passwd_start NEW.
776 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
779 Noteworthy changes in version 1.2.0 (2009-06-18)
780 ------------------------------------------------
782 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
785 * gpgme_new will fail if gpgme_check_version was not called, or a
786 selftest failed (for example, if -mms-bitfields was not used on
789 * New functions gpgme_io_read and gpgme_io_write for use with
790 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
792 * New functions gpgme_result_ref and gpgme_result_unref to detach
793 result structures from a context.
795 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
796 that allow to specify exported keys through gpgme_key_t objects
799 * New mode of operation gpgme_export_mode_t that allows exporting
802 * Interface changes relative to the 1.1.7 release:
803 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
804 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
805 GPGME_PROTOCOL_ASSUAN NEW.
806 gpgme_assuan_data_cb_t NEW.
807 gpgme_assuan_inquire_cb_t NEW.
808 gpgme_assuan_status_cb_t NEW.
809 gpgme_op_assuan_transact_start NEW.
810 gpgme_op_assuan_transact NEW.
811 gpgme_op_assuan_result NEW.
812 gpgme_op_import_keys NEW.
813 gpgme_op_import_keys_start NEW.
814 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
815 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
816 gpgme_check_version CHANGED: Is now a macro.
817 gpgme_new EXTENDED: More failure codes.
820 gpgme_result_ref NEW.
821 gpgme_result_unref NEW.
822 gpgme_export_mode_t NEW.
823 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
824 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
825 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
826 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
827 gpgme_op_export_keys_start NEW.
828 gpgme_op_export_keys NEW.
829 GPGME_DATA_ENCODING_URL NEW.
830 GPGME_DATA_ENCODING_URL0 NEW.
831 GPGME_DATA_ENCODING_URLESC NEW.
832 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
835 Noteworthy changes in version 1.1.8 (2008-12-08)
836 ------------------------------------------------
838 * SIGPIPE is now again ignored as described in the manual. Fixes
839 regression introduced with 1.1.6.
842 Noteworthy changes in version 1.1.7 (2008-10-17)
843 ------------------------------------------------
845 * Using GPGME_KEYLIST_MODE_LOCAL combined with
846 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
847 --locate-keys feature of gpg (>= 2.0.10).
849 * The encoding of gpgme_data_t objects can affect the output encoding
850 of export, sign and encrypt operations now (the same operations
851 that are also affected by the ASCII mode switch). We believe this
852 change in the ABI is innocent enough not to break existing
853 applications (it only affects the S/MIME backend on certain
856 * The reference manual now includes the specification of "The GnuPG
859 * A new function gpgme_cancel_async can be used to asynchronously
860 cancel any pending operation at any time, from any thread.
862 * Interface changes relative to the 1.1.6 release:
863 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
864 gpgme_op_encrypt CHANGED: Output encoding can affect result.
865 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
866 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
867 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
868 gpgme_op_sign CHANGED: Output encoding can affect result.
869 gpgme_op_sign_start CHANGED: Output encoding can affect result.
870 gpgme_op_export CHANGED: Output encoding can affect result.
871 gpgme_op_export_start CHANGED: Output encoding can affect result.
872 gpgme_op_export_ext CHANGED: Output encoding can affect result.
873 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
874 gpgme_cancel_async NEW
875 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
878 Noteworthy changes in version 1.1.6 (2008-01-04)
879 ------------------------------------------------
881 * Bug fixes for for W32.
883 * A new, experimental (and thus undocumented and potentially
884 unstable) interface for accessing gpg-conf through GPGME has been
887 * Interface changes relative to the 1.1.1 release:
888 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
889 gpgme_signature_t EXTENDED: New field chain_model.
890 gpgme_op_getauditlog_start NEW.
891 gpgme_op_getauditlog NEW.
892 GPGME_AUDITLOG_HTML NEW.
893 GPGME_AUDITLOG_WITH_HELP NEW.
894 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
897 Noteworthy changes in version 1.1.5 (2007-07-09)
898 ------------------------------------------------
900 * Bug and portability fixes (mainly for W32).
903 Noteworthy changes in version 1.1.4 (2007-03-05)
904 ------------------------------------------------
906 * Detect and bail out on double plaintext messages. This is required
907 so that applications can properly detect the signed parts of a
908 message. Actual there is now a double protection as GnuPG 1.4.7
909 will detect this case too.
912 Noteworthy changes in version 1.1.3 (2007-01-29)
913 ------------------------------------------------
915 * Fixed a memory leak in gpgme_data_release_and_get_mem.
917 * Fixed a bug in Windows command line quoting.
920 Noteworthy changes in version 1.1.2 (2006-03-02)
921 ------------------------------------------------
923 * Fixed a bug in the W32 glib backend.
926 Noteworthy changes in version 1.1.1 (2006-02-23)
927 ------------------------------------------------
929 * Fixed a bug in that the fingerprints of subkeys are not available.
931 * Clarified usage of the SECRET flag in key listings. It is now
934 * Reading signature notations and policy URLs on key signatures is
935 supported. They can be found in the new field notations of the
936 gpgme_key_sig_t structure. This has to be enabled with the keylist
937 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
939 * A new gpgme_free() function solves the problem of using different
940 allocators in a single program. This function should now be used
941 instead calling free() to release the buffer returned by
942 gpgme_data_release_and_get_mem. It is recommended that you always
943 do this, but it is only necessary on certain platforms, so backwards
944 compatibility is provided. In other words: If free() worked for
945 you before, it will keep working.
947 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
948 They are analyzed by the verify handlers and made available in the
949 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
951 * Interface changes relative to the 1.1.0 release:
952 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
953 gpgme_key_sig_t EXTENDED: New field notations.
954 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
956 GPGME_STATUS_PKA_TRUST_BAD NEW
957 GPGME_STATUS_PKA_TRUST_GOOD NEW
958 gpgme_signature_t EXTENDED: New field pka_trust.
959 gpgme_signature_t EXTENDED: New field pka_address.
960 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
963 Noteworthy changes in version 1.1.0 (2005-10-01)
964 ------------------------------------------------
966 * You can now configure the backend engine file name and home
967 directory to be used, as default and per context.
969 * Information about the recipients of an encrypted text is now
970 available at decryption time.
972 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
973 and verify handlers, the information about the plaintext filename,
974 if available is made available in the new field file_name of the
975 respective result structure.
977 * The code for "automagically detecting the thread library" has been
978 removed from libgpgme. It is deprecated since version 0.4.3.
979 Since then, you had to link against libgpgme-pthread for
980 applications using pthread and libgpgme-pth for applications using
983 The code was removed because it caused compilation problems on
984 systems where the pthread.h header from GNU Pth is available in
985 addition to the system header (FreeBSD 6 and later for example).
987 * "./autogen.sh --build-w32" does now build gpgme.dll.
989 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
990 delimiter. The standard install directory is used when locating
991 gpg or gpgsm before finally falling back to the hardwired name.
993 * There is a new flag for keys and subkeys, is_qualified, which
994 indicates if a key can be used for qualified signatures according
995 to local government regulations.
997 * You can associate a filename with a data object using the new
998 function gpgme_data_set_file_name(). This filename will be stored
999 in the output when encrypting or signing the data and will be
1000 returned when decrypting or verifying the output data.
1002 * You can now set notation data at signature creation with the new
1003 function gpgme_sig_notation_add().
1005 * Interface changes relative to the 1.0.3 release:
1006 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1007 gpgme_set_engine_info NEW
1008 gpgme_ctx_get_engine_info NEW
1009 gpgme_ctx_set_engine_info NEW
1010 gpgme_recipient_t NEW
1011 gpgme_decrypt_result_t EXTENDED: New field recipients.
1012 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
1013 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
1014 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
1015 GPGME_STATUS_PLAINTEXT NEW
1016 gpgme_key_t EXTENDED: New field is_qualified.
1017 gpgme_subkey_t EXTENDED: New field is_qualified.
1018 gpgme_data_get_file_name NEW
1019 gpgme_data_set_file_name NEW
1020 gpgme_sig_notation_flags_t NEW
1021 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
1022 GPGME_SIG_NOTATAION_CRITICAL NEW
1023 gpgme_sig_notation_clear NEW
1024 gpgme_sig_notation_add NEW
1025 gpgme_sig_notation_get NEW
1026 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1029 Noteworthy changes in version 1.0.3 (2005-06-20)
1030 ------------------------------------------------
1032 * Previousy, GPGME would use a default "include certs" of 1. This
1033 has been changed. Now GPGME will use the crypto backend engines
1034 default unless you set the value with gpgme_set_include_certs()
1035 explicitly. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
1036 as a value to explicitly request the new default behaviour.
1038 Because the default changes, this is a slight change of the API
1039 semantics. We consider it to be a bug fix.
1041 * A bug which made GPGME hang has been fixed. If you have
1042 experienced hanging before, please try out this version and let me
1043 know if you still experience hanging problems.
1045 * Interface changes relative to the 0.9.0 release:
1046 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1047 gpgme_set_include_certs CHANGED DEFAULT
1048 GPGME_INCLUDE_CERTS_DEFAULT NEW
1049 GPGME_STATUS_SIG_SUBPACKET NEW
1050 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
1051 GPGME_STATUS_SC_OP_FAILURE NEW
1052 GPGME_STATUS_SC_OP_SUCCESS NEW
1053 GPGME_STATUS_CARDCTRL NEW
1054 GPGME_STATUS_BACKUP_KEY_CREATED NEW
1055 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1058 Noteworthy changes in version 1.0.2 (2004-12-28)
1059 ------------------------------------------------
1061 * Changed the license of the library to the GNU Lesser General Public
1062 License (LGPL), version 2.1 or later.
1065 Noteworthy changes in version 1.0.1 (2004-10-22)
1066 ------------------------------------------------
1071 Noteworthy changes in version 1.0.0 (2004-09-30)
1072 ------------------------------------------------
1074 * Version 1.0.0! We are proud to present you with a thoroughly
1075 tested and stable version of the GPGME library. A big Thank You!
1076 to all the people who made this possible.
1078 The development will be branched into a stable 1.x.y series and the
1081 * The gpgme.m4 macro supports checking the API version. Just prepend
1082 it to the required version string, separated by a colon. For
1083 example, this release has the version "1:1.0.0". The last release
1084 to which this version is (mostly) ABI compatible is "1:0.4.2",
1085 which is the default required version.
1088 Noteworthy changes in version 0.9.0 (2004-06-08)
1089 ------------------------------------------------
1091 * The type gpgme_key_t has now a new field keylist_mode that contains
1092 the keylist mode that was active at the time the key was retrieved.
1094 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
1095 that contains a flag indicating that the key should not have been
1096 used for encryption.
1098 * Verifying a signature of a revoked key gives the correct result now
1099 (GPG_ERR_CERT_REVOKED error code).
1101 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
1102 verify operations still allows you to look at the signature
1103 verification result.
1105 * Clarified that patterns in keylisting operations have an upper
1106 limit, and thus are not suited to list many keys at once by their
1107 fingerprint. Also improve the error message if the pattern is too
1108 long for the CMS protocol to handle.
1110 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1111 gpgme_key_t EXTENDED: New field keylist_mode.
1112 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
1113 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1116 Noteworthy changes in version 0.4.7 (2004-04-29)
1117 ------------------------------------------------
1119 * Correctly initialize the fields expired, revoked, invalid, and
1120 disabled in the gpgme_key_t structures.
1122 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
1123 accidentally of type int instead unsigned int.
1125 * Interface changes relative to the 0.4.5 release:
1126 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1127 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
1128 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1130 Noteworthy changes in version 0.4.6 (2004-04-06)
1131 ------------------------------------------------
1136 Noteworthy changes in version 0.4.5 (2004-03-07)
1137 ------------------------------------------------
1139 * GPGME is now compiled with LFS (large file support) by default.
1140 This means that _all_ programs using GPGME must be compiled with
1141 LFS support enabled by default. You can do this easily with
1142 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
1143 without autoconf by defining the preprocessor symbol
1144 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
1145 the C compiler command line, or by defining this preprocessor
1146 symbol before including any system header files). For more
1147 details, read the section on LFS in the manual.
1149 Up to now, it was undocumented that GPGME was not using LFS.
1150 But the public interfaces use off_t, and file descriptors are
1151 exchanged between the application and GPGME. This was an oversight,
1152 and bound to cause troubles in the future.
1154 Writing GPGME as a dual mode library that seamlessly supports LFS
1155 while keeping backwards compatibility is possible, but does not
1156 solve the problem: Many applications already expect GPGME to have
1157 LFS (they are compiled with off_t being a 64bit value). This is true
1158 in particular for the popular Gtk+ and Qt programs.
1160 So, although this is an ABI (but not an API) break, we will not
1161 change the library version to reflect that. Because the interfaces
1162 affected are probably not used yet in any GPGME 0.4 based
1163 application, we don't expect any real failures from this change.
1164 In fact, applications already using LFS will have some subtle bugs
1167 However, if you encounter an application using GPGME 0.4.x that
1168 does _not_ use LFS by default (off_t is a 32bit value), _and_
1169 uses at least one of the functions gpgme_data_seek,
1170 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
1171 gpgme_data_new_from_cbs, then indeed this library will be ABI
1172 incompatible with the program. As said above, we don't believe
1173 such a program exists. If we are in error, then you have two
1174 options: As a quick hack, you can configure GPGME with the
1175 --disable-largefile option. This will revert the change, and GPGME
1176 will not use LFS. However, GPGME will be incompatible with
1177 programs that expect GPGME to use LFS. All applications are
1178 required to use LFS when using GPGME, so this is only good as a
1179 temporary local work-around.
1181 The other option is to change the versioning of the library and
1182 recompile all applications. We have reserved a special version of
1183 the library for that, so you can do that without expecting a
1184 version clash in the future. Furthermore, everyone who does this
1185 will agree on the version to use (this is important for
1186 distribution makers). Read the comment in configure.ac (before
1187 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
1188 blindly: As stated above, we think it is unlikely this measure is
1189 needed. Still, it is there if necessary. If in doubt, contact us
1190 and we will give our advise for your specific situation.
1192 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
1195 * New interface gpgme_cancel() that can be used to cancel
1196 asynchronous operations.
1198 * Interface changes relative to the 0.4.4 release:
1199 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1200 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
1201 gpgme_data_seek CHANGED: off_t is now a largefile type.
1202 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
1203 GPGME_KEYLIST_MODE_VALIDATE NEW
1205 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1207 Noteworthy changes in version 0.4.4 (2004-01-12)
1208 ------------------------------------------------
1210 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
1211 been renamed to "sig_class", to avoid clash with C++ compilers. In
1212 the C API, the old name "class" has been preserved for backwards
1213 compatibility, but is deprecated.
1215 * Interface changes relative to the 0.4.3 release:
1216 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1217 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
1218 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
1219 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1221 Noteworthy changes in version 0.4.3 (2003-10-06)
1222 ------------------------------------------------
1224 * libgpgme should not be used for threaded programs anymore. This
1225 never worked reliably in all cases, because you had to
1226 be careful about the linking order and libtool wouldn't do that for
1227 you automatically. Instead, now you have to link against
1228 libgpgme-pthread for applications using pthread and libgpgme-pth for
1229 applications using GNU Pth.
1231 The old code for automagically detecting the thread library is
1232 still part of libgpgme, but it is DEPRECATED.
1234 * There are new automake macros AM_PATH_GPGME_PTH and
1235 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
1236 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
1237 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
1238 variables of course also include the configuration for the thread
1239 package itself. Alternatively, use libtool.
1241 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
1244 * gpgme-config doesn't support setting the prefix or exec prefix
1245 anymore. I don't think it ever worked correctly, and it seems to
1248 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
1249 provided was not unique, instead returning the first matching key.
1251 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
1252 that indicates if the key can be used for authentication.
1254 * gpgme_signature_t's status field is now correctly set to an error
1255 with error code GPG_ERR_NO_PUBKEY if public key is not found.
1257 * gpgme_new_signature_t's class field is now an unsigned int, rather
1258 than an unsigned long (the old class field is preserved for
1259 backwards compatibility).
1261 * A new function gpgme_set_locale() is provided to allow configuring
1262 the locale for the crypto backend. This is necessary for text
1263 terminals so that programs like the pinentry can be started with
1264 the right locale settings for the terminal the application is running
1265 on, in case the terminal has different settings than the system
1266 default (for example, if it is a remote terminal). You are highly
1267 recommended to call the following functions directly after
1268 gpgme_check_version:
1272 setlocale (LC_ALL, "");
1273 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
1274 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
1276 GPGME can not do this for you, as setlocale is not thread safe, and
1277 there is no alternative.
1279 * The signal action for SIGPIPE is now set to SIG_IGN by
1280 gpgme_check_version, instead the first time a crypto engine is
1281 started (which is not well defined).
1283 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
1284 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
1285 to CRC24RFC2440. For now, these strings can be used as the MIC
1286 parameter for PGP/MIME (if appropriately modified).
1288 * Interface changes relative to the 0.4.2 release:
1289 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1290 gpgme_strerror_t NEW
1291 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
1292 gpgme_key_t EXTENDED: New field can_authenticate.
1293 gpgme_subkey_t EXTENDED: New field can_authenticate.
1294 gpgme_new_signature_t CHANGED: New type for class field.
1295 gpgme_set_locale NEW
1296 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
1297 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1299 Noteworthy changes in version 0.4.2 (2003-07-30)
1300 ------------------------------------------------
1302 * Allow gpg-error to be in non-standard place when linking the test suite.
1304 * Configure will fail now if gpg-error can not be found.
1306 * Fixed initialized memory backed data objects for writing, which
1307 caused the test program to crash (but only on Mac OS, surprisingly).
1309 * Eliminate use of C99 constructs.
1311 * Small improvements to the manual.
1314 Noteworthy changes in version 0.4.1 (2003-06-06)
1315 ------------------------------------------------
1317 This is the release that 0.4.0 should have been. There are many
1318 interface changes, please see below for the details. The changes are
1319 sometimes the result of new functionality, but more often express a
1320 paradigm shift. Others are an overdue cleanup to get GPGME in line
1321 with the GNU coding standards and to make the interface more
1322 self-consistent. Here is an overview on the changes:
1324 All types have been renamed to conform to the GNU coding standards,
1325 most of the time by keeping the whole name in lowercase and inserting
1326 underscores between words.
1328 All operations consistently only accept input parameters in their
1329 invocation function, and return only an error code directly. Further
1330 information about the result of the operation has to be retrieved
1331 afterwards by calling one of the result functions. This unifies the
1332 synchronous and the asynchronous interface.
1334 The error values have been completely replaced by a more
1335 sophisticated model that allows GPGME to transparently and accurately
1336 report all errors from the other GnuPG components, regardless of
1337 process boundaries. This is achieved by using the library
1338 libgpg-errors, which is shared by all GnuPG components. This library
1339 is now required for GPGME.
1341 The results of all operations are now provided by pointers to C
1342 structs rather than by XML structs or in other ways.
1344 Objects which used to be opaque (for example a key) are now pointers
1345 to accessible structs, so no accessor functions are necessary.
1347 Backward compatibility is provided where it was possible without too
1348 much effort and did not collide with the overall sanitization effort.
1349 However, this is only for ease of transition. NO DEPRECATED FUNCTION
1350 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
1351 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
1352 Recommendations how to replace deprecated or removed functionality
1353 can be found within the description of each change.
1355 What follows are all changes to the interface and behaviour of GPGME
1358 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
1359 deprecated attributes will warn about use of obsolete functions and
1360 type definitions. You can suppress these warnings by passing
1361 -Wno-deprecated-declarations to the gcc command.
1363 * The following types have been renamed. The old types are still
1364 available as aliases, but they are deprecated now:
1366 GpgmeCtx gpgme_ctx_t
1367 GpgmeData gpgme_data_t
1368 GpgmeError gpgme_error_t
1369 GpgmeDataEncoding gpgme_data_encoding_t
1370 GpgmeSigStat gpgme_sig_stat_t
1371 GpgmeSigMode gpgme_sig_mode_t
1372 GpgmeAttr gpgme_attr_t
1373 GpgmeValidity gpgme_validity_t
1374 GpgmeProtocol gpgme_protocol_t
1375 GpgmeKey gpgme_key_t
1376 GpgmePassphraseCb gpgme_passphrase_cb_t
1377 GpgmeProgressCb gpgme_progress_cb_t
1378 GpgmeIOCb gpgme_io_cb_t
1379 GpgmeRegisterIOCb gpgme_register_io_cb_t
1380 GpgmeRemoveIOCb gpgme_remove_io_cb_t
1381 GpgmeEventIO gpgme_event_io_t
1382 GpgmeEventIOCb gpgme_event_io_cb_t
1383 GpgmeIOCbs gpgme_io_cbs
1384 GpgmeDataReadCb gpgme_data_read_cb_t
1385 GpgmeDataWriteCb gpgme_data_write_cb_t
1386 GpgmeDataSeekCb gpgme_data_seek_cb_t
1387 GpgmeDataReleaseCb gpgme_data_release_cb_t
1388 GpgmeDataCbs gpgme_data_cbs_t
1389 GpgmeTrustItem gpgme_trust_item_t
1390 GpgmeStatusCode gpgme_status_code_t
1392 * gpgme_error_t is now identical to gpg_error_t, the error type
1393 provided by libgpg-error. More about using libgpg-error with GPGME
1394 can be found in the manual. All error symbols have been removed!
1396 * All functions and types in libgpg-error have been wrapped in GPGME.
1397 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1398 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1399 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1400 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1403 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1405 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1406 for encrypt, sign, encrypt-sign, decrypt, verify, and
1407 decrypt-verify operations. For verify operations on detached
1408 signatures, the progress callback is invoked for both the detached
1409 signature and the plaintext message, though.
1411 * gpgme_passphrase_cb_t has been changed to not provide a complete
1412 description, but the UID hint, passphrase info and a flag
1413 indicating if this is a repeated attempt individually, so the user
1414 can compose his own description from this information.
1416 The passphrase is not returned as a C string, but must be written
1417 to a file descriptor directly. This allows for secure passphrase
1420 The return type has been changed to gpgme_error_t value. This
1421 allowed to remove the gpgme_cancel function; just return
1422 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1424 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1425 The user is expected to write the response to the file descriptor,
1426 followed by a newline.
1428 * The recipients interface has been removed. Instead, you use
1429 NULL-terminated lists of keys for specifying the recipients of an
1430 encryption operation. Use the new encryption flag
1431 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1432 the keys (but note that in general this is not a good idea).
1434 This change has been made to the prototypes of gpgme_op_encrypt,
1435 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1436 gpgme_op_encrypt_sign_start.
1438 The export interface has been changed to use pattern strings like
1439 the keylist interface. Thus, new functions gpgme_op_export_ext and
1440 gpgme_op_export_ext_start have been added as well. Now the
1441 prototypes of gpgme_op_export_start and gpgme_op_export finally
1444 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1445 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1448 * gpgme_io_cb_t changed from a void function to a function returning
1449 a gpgme_error_t value. However, it will always return 0, so you
1450 can safely ignore the return value.
1452 * A new I/O callback event GPGME_EVENT_START has been added. The new
1453 requirement is that you must wait until this event until you are
1454 allowed to call the I/O callback handlers previously registered for
1455 this context operation. Calling I/O callback functions for this
1456 context operation before the start event happened is unsafe because
1457 it can lead to race conditions in a multi-threaded environment.
1459 * The idle function feature has been removed. It was not precisely
1460 defined in a multi-threaded environment and is obsoleted by the
1461 user I/O callback functions. If you still need a simple way to
1462 call something while waiting on one or multiple asynchronous
1463 operations to complete, don't set the HANG flag in gpgme_wait (note
1464 that this will return to your program more often than the idle
1467 * gpgme_wait can return NULL even if hang is true, if an error
1468 occurs. In that case *status contains the error code.
1470 * gpgme_get_engine_info was radically changed. Instead an XML
1471 string, an info structure of the new type gpgme_engine_info_t is
1472 returned. This makes it easier and more robust to evaluate the
1473 information in an application.
1475 * The new function gpgme_get_protocol_name can be used to convert a
1476 gpgme_protocol_t value into a string.
1478 * The status of a context operation is not checked anymore. Starting
1479 a new operation will silently cancel the previous one. Calling a
1480 function that requires you to have started an operation before without
1481 doing so is undefined.
1483 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1484 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1485 pointer to a structure which contains the fingerprint. This also
1486 works with gpgme_op_genkey_start. The structure also provides
1487 other information about the generated keys.
1492 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1494 printf ("%s\n", fpr);
1498 gpgme_genkey_result_t result;
1499 err = gpgme_op_genkey (ctx, NULL, NULL);
1502 result = gpgme_op_genkey_result (ctx);
1504 printf ("%s\n", result->fpr);
1507 * The new gpgme_op_import_result function provides detailed
1508 information about the result of an import operation in
1509 gpgme_import_result_t and gpgme_import_status_t objects.
1510 Thus, the gpgme_op_import_ext variant is deprecated.
1512 * The new gpgme_op_sign_result function provides detailed information
1513 about the result of a signing operation in gpgme_sign_result_t,
1514 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1516 * The new gpgme_op_encrypt_result function provides detailed
1517 information about the result of an encryption operation in
1518 a GpgmeEncryptResult object.
1520 * The new gpgme_op_decrypt_result function provides detailed
1521 information about the result of a decryption operation in
1522 a GpgmeDecryptResult object.
1524 * The new gpgme_op_verify_result function provides detailed
1525 information about the result of an verify operation in
1526 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1527 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1528 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1529 and gpgme_get_notation is removed.
1531 * GpgmeTrustItem objects have now directly accessible data, so the
1532 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1533 accessor functions are deprecated. Also, reference counting is
1534 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1535 (the gpgme_trust_item_release alias for the latter is deprecated).
1537 * Keys are not cached internally anymore, so the force_update argument
1538 to gpgme_get_key has been removed.
1540 * GpgmeKey objects have now directly accessible data so the
1541 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1542 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1543 functions are deprecated. Also, gpgme_key_release is now
1544 deprecated. The gpgme_key_get_as_xml function has been dropped.
1546 * Because all interfaces using attributes are deprecated, the
1547 GpgmeAttr data type is also deprecated.
1549 * The new gpgme_op_keylist_result function provides detailed
1550 information about the result of a key listing operation in
1551 a GpgmeKeyListResult object.
1553 * Now that each function comes with its own result retrieval
1554 interface, the generic gpgme_get_op_info interface is not useful
1555 anymore and dropped.
1557 * The type and mode of data objects is not available anymore.
1559 * Interface changes relative to the 0.4.0 release:
1560 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1561 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1562 GpgmeData DEPRECATED: Use gpgme_data_t.
1563 GpgmeError DEPRECATED: Use gpgme_error_t.
1564 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1565 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1566 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1567 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1568 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1569 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1570 GpgmeKey DEPRECATED: Use gpgme_key_t.
1571 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1572 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1573 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1574 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1575 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1576 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1577 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1578 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1579 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1580 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1581 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1582 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1583 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1584 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1585 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1588 gpgme_recipients_t NEW
1590 gpgme_data_encoding_t NEW
1591 gpgme_sig_stat_t NEW
1592 gpgme_sig_mode_t NEW
1594 gpgme_validity_t NEW
1595 gpgme_protocol_t NEW
1597 gpgme_passphrase_cb_t NEW
1598 gpgme_progress_cb_t NEW
1600 gpgme_register_io_cb_t NEW
1601 gpgme_remove_io_cb_t NEW
1602 gpgme_event_io_t NEW
1603 gpgme_event_io_cb_t NEW
1605 gpgme_data_read_cb_t NEW
1606 gpgme_data_write_cb_t NEW
1607 gpgme_data_seek_cb_t NEW
1608 gpgme_data_release_cb_t NEW
1609 gpgme_data_cbs_t NEW
1610 gpgme_trust_item_t NEW
1611 gpgme_status_code_t NEW
1612 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1613 gpgme_err_code_t NEW
1614 gpgme_err_source_t NEW
1616 gpgme_err_source NEW
1619 gpgme_error_from_errno NEW
1620 gpgme_err_make_from_errno NEW
1621 gpgme_err_code_from_errno NEW
1622 gpgme_err_code_to_errno NEW
1624 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1625 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1626 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1627 gpgme_edit_cb_t CHANGED: Write directly to FD.
1628 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1629 gpgme_op_verify CHANGED: Drop R_STAT argument.
1630 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1631 gpgme_wait CHANGED: Can return NULL even if hang is true.
1632 GpgmeIdleFunc REMOVED
1633 gpgme_register_idle REMOVED
1634 GpgmeRecipients REMOVED
1635 gpgme_recipients_new REMOVED
1636 gpgme_recipients_release REMOVED
1637 gpgme_recipients_add_name REMOVED
1638 gpgme_recipients_add_name_with_validity REMOVED
1639 gpgme_recipients_count REMOVED
1640 gpgme_recipients_enum_open REMOVED
1641 gpgme_recipients_enum_read REMOVED
1642 gpgme_recipients_enum_close REMOVED
1643 gpgme_encrypt_flags_t NEW
1644 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1645 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1646 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1647 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1648 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1649 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1650 gpgme_op_export CHANGED: User IDs passed as patterns.
1651 gpgme_op_export_ext_start NEW
1652 gpgme_op_export_ext NEW
1653 gpgme_keylist_mode_t NEW
1655 gpgme_engine_info_t NEW
1656 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1657 gpgme_get_protocol_name NEW
1658 gpgme_cancel REMOVED: Return error in callback directly.
1659 gpgme_op_genkey CHANGED: FPR argument dropped.
1660 gpgme_op_genkey_result NEW
1661 gpgme_genkey_result_t NEW
1662 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1663 gpgme_op_import_result NEW
1664 gpgme_import_status_t NEW
1665 gpgme_import_result_t NEW
1666 gpgme_pubkey_algo_t NEW
1667 gpgme_hash_algo_t NEW
1668 gpgme_invalid_key_t NEW
1669 gpgme_new_signature_t NEW
1670 gpgme_sign_result_t NEW
1671 gpgme_op_sign_result NEW
1672 gpgme_pubkey_algo_name NEW
1673 gpgme_hash_algo_name NEW
1674 gpgme_encrypt_result_t NEW
1675 gpgme_op_encrypt_result NEW
1676 gpgme_decrypt_result_t NEW
1677 gpgme_op_decrypt_result NEW
1678 gpgme_verify_result_t NEW
1679 gpgme_op_verify_result NEW
1680 gpgme_get_notation REMOVED: Access verify result directly instead.
1681 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1682 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1683 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1684 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1685 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1686 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1687 gpgme_trust_item_ref NEW
1688 gpgme_trust_item_unref NEW
1689 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1690 gpgme_trust_item_get_string_attr DEPRECATED
1691 gpgme_trust_item_get_ulong_attr DEPRECATED
1692 gpgme_get_key CHANGED: Removed force_update argument.
1696 gpgme_key_t CHANGED: Now has user accessible data members.
1697 gpgme_key_get_string_attr DEPRECATED
1698 gpgme_key_get_ulong_attr DEPRECATED
1699 gpgme_key_sig_get_string_attr DEPRECATED
1700 gpgme_key_sig_get_ulong_attr DEPRECATED
1701 gpgme_key_get_as_xml REMOVED
1702 gpgme_key_list_result_t NEW
1703 gpgme_op_keylist_result NEW
1704 gpgme_get_op_info REMOVED
1705 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1707 Noteworthy changes in version 0.4.0 (2002-12-23)
1708 ------------------------------------------------
1710 * Key generation returns the fingerprint of the generated key.
1712 * New convenience function gpgme_get_key.
1714 * Supports signatures of user IDs in keys via the new
1715 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1716 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1717 interfaces. The XML info about a key also includes the signatures
1720 * New data object interface, which is more flexible and transparent.
1722 * Interface changes relative to the 0.3.9 release:
1723 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1725 GpgmeDataWriteCb NEW
1727 GpgmeDataReleaseCb NEW
1729 gpgme_data_read CHANGED: Match read() closely.
1730 gpgme_data_write CHANGED: Match write() closely.
1732 gpgme_data_new_from_fd NEW
1733 gpgme_data_new_from_stream NEW
1734 gpgme_data_new_from_cbs NEW
1735 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1736 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1737 gpgme_data_get_type REMOVED: No replacement.
1738 gpgme_op_verify CHANGED: Take different data objects for
1739 signed text and plain text.
1740 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1741 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1742 gpgme_op_genkey CHANGED: New parameter FPR.
1743 GPGME_KEYLIST_MODE_SIGS NEW
1744 gpgme_key_sig_get_string_attr NEW
1745 gpgme_key_sig_get_ulong_attr NEW
1747 GPGME_ATTR_SIG_CLASS NEW
1748 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1750 Noteworthy changes in version 0.3.16 (2003-11-19)
1751 -------------------------------------------------
1753 * Compatibility fixes for GnuPG 1.9.x
1755 Noteworthy changes in version 0.3.15 (2003-02-18)
1756 -------------------------------------------------
1758 * The progress status is sent via the progress callbacks in
1761 * Bug fix for signing operations with explicit signer settings for
1764 Noteworthy changes in version 0.3.14 (2002-12-04)
1765 -------------------------------------------------
1767 * GPGME-Plug is now in its own package "cryptplug".
1769 * Workaround for a setlocale problem. Fixed a segv related to not
1770 correctly as closed marked file descriptors.
1772 Noteworthy changes in version 0.3.13 (2002-11-20)
1773 -------------------------------------------------
1775 * Release due to changes in gpgmeplug.
1777 Noteworthy changes in version 0.3.12 (2002-10-15)
1778 -------------------------------------------------
1780 * Fixed some bux with key listings.
1782 * The development has been branched to clean up some API issues.
1783 This 0.3 series will be kept for compatibility reasons; so do don't
1784 expect new features.
1786 Noteworthy changes in version 0.3.11 (2002-09-20)
1787 -------------------------------------------------
1791 Noteworthy changes in version 0.3.10 (2002-09-02)
1792 -------------------------------------------------
1794 * Setting the signing keys for the CMS protocol does now work.
1796 * The signers setting is honoured by gpgme_op_edit.
1798 Noteworthy changes in version 0.3.9 (2002-08-21)
1799 ------------------------------------------------
1801 * A spec file for creating RPMs has been added.
1803 * An experimental interface to GnuPG's --edit-key functionality is
1804 introduced, see gpgme_op_edit.
1806 * The new gpgme_import_ext function provides a convenient access to
1807 the number of processed keys.
1809 * Interface changes relative to the 0.3.8 release:
1810 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1813 gpgme_op_edit_start NEW
1815 gpgme_op_import_ext NEW
1816 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1818 Noteworthy changes in version 0.3.8 (2002-06-25)
1819 ------------------------------------------------
1821 * It is possible to use an outside event loop for the I/O to the
1822 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1824 * Interface changes relative to the 0.3.6 release:
1825 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1827 GpgmeRegisterIOCb NEW
1831 struct GpgmeIOCbs NEW
1832 gpgme_set_io_cbs NEW
1833 gpgme_get_io_cbs NEW
1834 GPGME_ATTR_ERRTOK NEW
1835 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1837 Noteworthy changes in version 0.3.7 (2002-06-04)
1838 ------------------------------------------------
1840 * GPGME_ATTR_OTRUST is implemented now.
1842 * A first step toward thread safeness has been achieved, see the
1843 documentation for details. Supported thread libraries are pthread
1846 Noteworthy changes in version 0.3.6 (2002-05-03)
1847 ------------------------------------------------
1849 * All error output of the gpgsm backend is send to the bit bucket.
1851 * The signature verification functions are extended. Instead of
1852 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1853 expired signatures. 2 new functions may be used to retrieve more
1854 detailed information like the signature expiration time and a
1855 validity information of the key without an extra key looking.
1857 * The current passphrase callback and progress meter callback can be
1858 retrieved with the new functions gpgme_get_passphrase_cb and
1859 gpgme_get_progress_cb respectively.
1861 * Interface changes relative to the 0.3.5 release:
1862 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1863 gpgme_get_passphrase_cb NEW
1864 gpgme_get_progress_cb NEW
1865 GpgmeDataEncoding NEW
1866 gpgme_data_set_encoding NEW
1867 gpgme_data_get_encoding NEW
1868 GPGME_SIG_STAT_GOOD_EXP NEW
1869 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1870 gpgme_op_verify CHANGED: Returns more status codes.
1871 GPGME_ATTR_SIG_STATUS NEW
1872 gpgme_get_sig_string_attr NEW
1873 gpgme_get_sig_ulong_attr NEW
1874 gpgme_get_protocol NEW
1875 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1877 Noteworthy changes in version 0.3.5 (2002-04-01)
1878 ------------------------------------------------
1880 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1881 case, symmetric encryption is performed. Note that this requires a
1882 passphrase from the user.
1884 * More information is returned for X.509 certificates.
1886 * Interface changes relative to the 0.3.4 release:
1887 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1888 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1889 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1891 Noteworthy changes in version 0.3.4 (2002-03-04)
1892 ------------------------------------------------
1894 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1895 some recipients have been invalid, whereas earlier versions
1896 succeeded in this case. The plaintext is still encrypted for all valid
1897 recipients, so the application might take this error as a hint that
1898 the ciphertext is not usable for all requested recipients.
1899 Information about invalid recipients is available with gpgme_get_op_info.
1901 * gpgme_op_verify now allows to pass an uninitialized data object as
1902 its plaintext argument to check for normal and cleartext
1903 signatures. The plaintext is then returned in the data object.
1905 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1906 to set and get the number of certifications to include in S/MIME
1909 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1910 to encrypt and sign a message in a combined operation.
1912 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1914 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1916 * Interface changes relative to the 0.3.3 release:
1917 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1918 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1919 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1920 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1921 gpgme_set_include_certs NEW
1922 gpgme_get_include_certs NEW
1923 gpgme_op_encrypt_sign NEW
1924 gpgme_op_encrypt_sign_start NEW
1925 gpgme_op_keylist_ext_start NEW
1926 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1928 Noteworthy changes in version 0.3.3 (2002-02-12)
1929 ------------------------------------------------
1931 * Fix the Makefile in jnlib.
1933 * Fix the test suite (hopefully). It should clean up all its state
1934 with `make check' now.
1937 Noteworthy changes in version 0.3.2 (2002-02-10)
1938 ------------------------------------------------
1940 * Remove erroneous dependency on libgcrypt in jnlib.
1943 Noteworthy changes in version 0.3.1 (2002-02-09)
1944 ------------------------------------------------
1946 * There is a Texinfo manual documenting the API.
1948 * The gpgme_set_keylist_mode function returns an error, and changed
1949 its meaning. It is no longer usable to select between normal and
1950 fast mode (newer versions of GnuPG will always be fast), but
1951 selects between local keyring, remote keyserver, or both.
1952 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1953 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1954 current setting, a function gpgme_get_keylist_mode was added to
1955 retrieve the current mode.
1957 * gpgme_wait accepts a new argument STATUS to return the error status
1958 of the operation on the context. Its definition is closer to
1959 waitpid() now than before.
1961 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1962 type from off_t to the unsigned size_t.
1964 * The R_HD argument to the GpgmePassphraseCb type changed its type
1965 from void* to void**.
1967 * New interface gpgme_op_trustlist_end() to match
1968 gpgme_op_keylist_end().
1970 * The CryptPlug modules have been renamed to gpgme-openpgp and
1971 gpgme-smime, and they are installed in pkglibdir by `make install'.
1973 * An idle function can be registered with gpgme_register_idle().
1975 * The GpgSM backend supports key generation with gpgme_op_genkey().
1977 * Interface changes relative to the 0.3.0 release:
1978 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1979 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1980 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1981 gpgme_wait CHANGED: New argument STATUS.
1982 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1983 The function has a new meaning!
1984 gpgme_get_keylist_mode NEW
1985 GPGME_KEYLIST_MODE_LOCAL NEW
1986 GPGME_KEYLIST_MODE_EXTERN NEW
1987 gpgme_op_trustlist_next NEW
1989 gpgme_register_idle NEW
1990 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1992 Noteworthy changes in version 0.3.0 (2001-12-19)
1993 ------------------------------------------------
1995 * New interface gpgme_set_protocol() to set the protocol and thus the
1996 crypto engine to be used by the context. Currently, the OpenPGP
1997 and the CMS protocols are supported. They are specified by the new
1998 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1999 A new context uses the OpenPGP engine by default.
2001 * gpgme_get_engine_info() returns information for all crypto engines
2002 compiled into the library. The XML format has changed. To
2003 reliably get the version of a crypto engine, the <version> tag
2004 after the appropriate <protocol> tag has to be looked for.
2006 * New interface gpgme_engine_check_version(), obsoleting
2007 gpgme_check_engine(). Check the version of all engines you are
2008 supporting in your software.
2010 * GpgmeKey lists the user ids in the order as they are returned by
2011 GnuPG, first the primary key with index 0, then the sub-user ids.
2013 * New operation gpgme_op_decrypt_verify() to decrypt and verify
2014 signatures simultaneously.
2016 * The new interface gpgme_op_keylist_end() terminates a pending
2017 keylist operation. A keylist operation is also terminated when
2018 gpgme_op_keylist_next() returns GPGME_EOF.
2020 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
2021 cross-compiled, or even compiled without support for GnuPG
2024 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
2025 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
2026 in the path, but it can also be compiled without support for GpgSM
2027 (`--without-gpgsm').
2029 * CryptPlug modules for GPGME are included and can be enabled at
2030 configure time (`--enable-gpgmeplug'). There is one module which
2031 uses the GnuPG engine (`gpgmeplug') and one module which uses the
2032 GpgSM engine (`gpgsmplug').
2034 * Interface changes relative to the latest 0.2.x release:
2035 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2036 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
2037 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
2038 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
2039 gpgme_get_engine_info CHANGED: New format, extended content.
2040 gpgme_engine_check_version NEW
2041 gpgme_decrypt_verify_start NEW
2042 gpgme_decrypt_verify NEW
2043 gpgme_op_keylist_next NEW
2044 gpgme_set_protocol NEW
2045 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2048 Noteworthy changes in version 0.2.3 (2001-09-17)
2049 ------------------------------------------------
2051 * New function gpgme_get_op_info which can be used to get the micalg
2052 parameter needed for MOSS.
2054 * New functions gpgme_get_armor and gpgme_get_textmode.
2056 * The usual bug fixes and some minor functionality improvements.
2058 * Added a simple encryption component for MS-Windows; however the
2059 build procedure might have some problems.
2062 Noteworthy changes in version 0.2.2 (2001-06-12)
2063 ------------------------------------------------
2065 * Implemented a key cache.
2067 * Fixed a race condition under W32 and some other bug fixes.
2070 Noteworthy changes in version 0.2.1 (2001-04-02)
2071 ------------------------------------------------
2073 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
2075 * Handle GnuPG's new key capabilities output and support revocation
2078 * Made the W32 support more robust.
2081 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
2084 This file is free software; as a special exception the author gives
2085 unlimited permission to copy and/or distribute it, with or without
2086 modifications, as long as this notice is preserved.
2088 This file is distributed in the hope that it will be useful, but
2089 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
2090 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.