1 Noteworthy changes in version 1.14.0 (2020-07-16)
2 -------------------------------------------------
4 * New keylist mode to force the engine to return the keygrip. [#4820]
6 * New export mode to export as OpenSSH public key. [#4310]
8 * New context flag "extended-edit" to enable expert key edit. [#4734]
10 * Deprecate the anyway non working trustlist functions. [#4834]
12 * cpp: Add convenience API to obtain remarks. [#4734]
14 * cpp: The sign key edit-interactor now supports multiple signatures
15 from the same key. [#4734]
17 * qt: Extended signkeyjob to handle remarks and multiple signatures.
20 * qt: Added job API for gpg-card.
22 * qt: The logging category has been changed to gpg.qgpgme to be more
23 consistent with other qt logging categories.
25 * Interface changes relative to the 1.13.1 release:
26 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
27 GPGME_KEYLIST_MODE_WITH_KEYGRIP NEW.
28 GPGME_EXPORT_MODE_SSH NEW.
29 gpgme_user_id_t EXTENDED: New field 'uidhash'.
30 cpp: UserID::remark NEW.
31 cpp: UserID::remarks NEW.
32 cpp: GpgSignKeyEditInteractor::setDupeOk NEW.
33 cpp: Context::exportPublicKeys EXTENDED: New param 'flags'.
34 cpp: Context::startPublicKeyExport EXTENDED: New param 'flags'.
35 cpp: Context::ExportMode NEW.
36 qt: SignKeyJob::setDupeOk NEW.
37 qt: SignKeyJob::setRemark NEW.
39 qt: ExportJob::setExportFlags NEW.
41 [c=C34/A23/R0 cpp=C17/A11/R0 qt=C11/A4/R0]
43 Release-info: https://dev.gnupg.org/T4996
46 Noteworthy changes in version 1.13.1 (2019-06-13)
47 -------------------------------------------------
49 * cpp: gpgme_set_global_flag is now wrapped. [#4471]
51 * w32: Improved handling of unicode install paths. [#4453]
53 * w32: The gpgme_io_spawn error message is now only shown once. [#4453]
55 * Fixed a crash introduced in 1.13.0 when working with S/MIME. [#4556]
57 * w32: Fixed format string errors introduced in 1.13.0 that could
58 cause crashes. [#4440]
60 * w32: Fixed an error in the new diagnostic gpgsm support introduced
61 in 1.13.0 that caused crashes in low fd scenarios. [#4439]
63 * python: Fixed a DecryptionError Exception. [#4478]
65 * python: No longer raises BadSignatures from decrypt(verify=True).
68 * Interface changes relative to the 1.13.0 release:
69 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
70 cpp: setGlobalFlag NEW.
72 [c=C33/A22/R1 cpp=C16/A10/R0 qt=C10/A3/R4]
74 Release-info: https://dev.gnupg.org/T4551
77 Noteworthy changes in version 1.13.0 (2019-03-26)
78 -------------------------------------------------
80 * Support GPGME_AUDITLOG_DIAG for gpgsm. [#4426]
82 * New context flag "trust-model".
84 * Removed support for WindowsCE and Windows ME.
86 * Aligned the gpgrt-config code with our other libaries.
88 * Auto-check for all installed Python versions. [#3354]
90 * Fixed generating card key in the C++ bindings. [#4428]
92 * Fixed a segv due to bad parameters in genkey. [#4192]
94 * Fixed crash if the plaintext is ignored in a CMS verify.
96 * Fixed memleak on Windows. [T4238]
98 * Tweaked the Windows I/O code.
100 * Fixed random crashes on Windows due to closing an arbitrary
103 * Fixed a segv on Windows. [#4369]
105 * Fixed test suite problems related to dtags. [#4298]
107 * Fixed bunch of python bugs. [#4242,commit 9de1c96ac3cf]
109 * Several fixes to the Common Lisp bindings.
111 * Fixed minor bugs in gpgme-json. [#4331,#4341,#4342,#4343
113 * Require trace level 8 to dump all I/O data.
115 * The compiler must now support variadic macros.
117 * Interface changes relative to the 1.12.0 release:
118 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
119 gpgme_set_ctx_flag EXTENDED: New flag 'trust-model'.
120 cpp: Context::create NEW.
122 cpp: Subkey::isBad NEW.
123 cpp: UserID::isBad NEW.
124 cpp: UserID::Signature::isBad NEW.
125 cpp: GenCardKeyInteractor::setAlgo NEW.
127 [c=C33/A22/R0 cpp=C15/A9/R0 qt=C10/A3/R3]
129 Release-info: https://dev.gnupg.org/T4376
132 Noteworthy changes in version 1.12.0 (2018-10-08)
133 -------------------------------------------------
135 * Enhanced the JSON based interface tool gpgme-json to support Native
136 Messaging as well as new Javascript code to support the browser
137 site. See lang/js/README for details.
139 * Major overhaul of the Python language bindings documentation.
141 * Even for old versions of gpg a missing MDC will now lead to a
144 * Added context flag "auto-key-locate" to control the
145 behavior of GPGME_KEYLIST_MODE_LOCATE.
147 * New data function to create a data object from an estream.
149 * Add more interfaces to the C++ bindings.
151 * Improved error codes on decryption failure.
153 * Lots of minor fixes.
155 * Interface changes relative to the 1.11.1 release:
156 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
157 gpgme_data_new_from_estream NEW.
158 gpgme_decrypt_result_t EXTENDED: New field legacy_cipher_nomdc.
159 gpgme_set_ctx_flag EXTENDED: New flag 'ignore-mdc-error'.
160 GPGME_AUDITLOG_DEFAULT NEW.
161 GPGME_AUDITLOG_DIAG NEW.
162 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-locate'.
163 cpp: DecryptionResult::sessionKey NEW.
164 cpp: DecryptionResult::symkeyAlgo NEW.
165 cpp: DecryptionResult::isLegacyCipherNoMDC New.
166 cpp: Data::rewind NEW.
167 cpp: Context::setFlag NEW.
168 cpp: Context::getFlag NEW.
169 cpp: Context::createKeyEx NEW.
171 [c=C32/A21/R0 cpp=C14/A8/R0 qt=C10/A3/R2]
173 Release-info: https://dev.gnupg.org/T4109
176 Noteworthy changes in version 1.11.1 (2018-04-20)
177 -------------------------------------------------
179 * Fixed build problems in the 1.11.0 release.
181 * Added C++ interfaces which were planned for 1.11.0.
183 * Interface changes relative to the 1.10.0 release:
184 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
185 cpp: Key::origin NEW.
186 cpp: Key::lastUpdate NEW.
187 cpp: UserID::origin NEW.
188 cpp: UserID::lastUpdate NEW.
190 [c=C31/A20/R1 cpp=C13/A7/R0 qt=C10/A3/R2]
193 Noteworthy changes in version 1.11.0 (2018-04-18)
194 -------------------------------------------------
196 * New encryption API to support direct key specification including
197 hidden recipients option and taking keys from a file. This also
198 allows to enforce the use of a subkey.
200 * New encryption flag for the new API to enforce the use of plain
201 mail addresses (addr-spec).
203 * The import API can now tell whether v3 keys are skipped. These old
204 and basically broken keys are not anymore supported by GnuPG 2.1.
206 * The decrypt and verify API will now return the MIME flag as
207 specified by RFC-4880bis.
209 * The offline mode now has an effect on gpg by disabling all network
212 * A failed OpenPGP verification how returns the fingerprint of the
213 intended key if a recent gpg version was used for signature
216 * New tool gpgme-json as native messaging server for web browsers.
217 As of now public key encryption and decryption is supported.
218 Requires Libgpg-error 1.29.
220 * New context flag "request-origin" which has an effect when used
221 with GnuPG 2.2.6 or later.
223 * New context flag "no-symkey-cache" which has an effect when used
224 with GnuPG 2.2.7 or later.
226 * New convenience constant GPGME_KEYLIST_MODE_LOCATE.
228 * Improved the Python documentation.
230 * Fixed a potential regression with GnuPG 2.2.6 or later.
232 * Fixed a crash in the Python bindings on 32 bit platforms. [#3892]
234 * Various minor fixes.
236 * Interface changes relative to the 1.10.0 release:
237 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
238 gpgme_op_encrypt_ext NEW.
239 gpgme_op_encrypt_ext_start NEW.
240 gpgme_op_encrypt_sign_ext NEW.
241 gpgme_op_encrypt_sign_ext_start NEW.
242 GPGME_ENCRYPT_WANT_ADDRESS NEW.
243 GPGME_KEYLIST_MODE_LOCATE NEW.
244 gpgme_import_result_t EXTENDED: New field 'skipped_v3_keys'.
245 gpgme_decrypt_result_t EXTENDED: New field 'symkey_algo'.
246 gpgme_decrypt_result_t EXTENDED: New field 'is_mime'.
247 gpgme_verify_result_t EXTENDED: New field 'is_mime'.
248 cpp: Key::locate NEW.
249 cpp: Data::toString NEW.
250 cpp: ImportResult::numV3KeysSkipped NEW.
252 [c=C31/A20/R0 cpp=C12/A6/R0 qt=C10/A3/R1]
255 Noteworthy changes in version 1.10.0 (2017-12-12)
256 -------------------------------------------------
258 * Now returns more specific error codes for decryption to distinguish
259 between bad passphrase, user canceled, and no secret key.
261 * Now returns key origin information if available.
263 * Added context flag "auto-key-retrieve" to selectively enable the
264 corresponding gpg option.
266 * Added flag is_de_vs to decryption and verify results.
268 * py: Use SEEK_SET as default for data.seek.
270 * cpp: Various new APIs.
272 * Reduced spawn overhead on Linux again. Added new configure option
273 --disable-linux-getdents to disable this feature for very old
276 * Improved the Python bindings build system.
278 * Made the test suite less fragile.
280 * Interface changes relative to the 1.9.0 release:
281 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
282 gpgme_decrypt_result_t EXTENDED: New field 'is_de_vs'.
283 gpgme_signature_t EXTENDED: New field 'is_de_vs'.
285 gpgme_op_delete_ext NEW.
286 gpgme_op_delete_ext_start NEW.
287 GPGME_DELETE_ALLOW_SECRET NEW.
288 GPGME_DELETE_FORCE NEW.
289 gpgme_op_conf_dir NEW.
290 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-retrieve'.
291 cpp: DecryptionResult::isDeVs NEW.
292 cpp: Signature::isDeVs NEW.
293 cpp: EngineInfo::Version::operator> NEW.
294 cpp: Context::createKey NEW.
295 cpp: Context::startCreateKey NEW.
296 cpp: Context::createSubkey NEW.
297 cpp: Context::startCreateSubkey NEW.
299 py: DecryptResult EXTENDED: New boolean field 'is_de_vs'.
300 py: Signature EXTENDED: New boolean field 'is_de_vs'.
301 py: GpgError EXTENDED: Partial results in 'results'.
303 [c=C30/A19/R0 cpp=C11/A5/R0 qt=C10/A3/R0]
306 Noteworthy changes in version 1.9.0 (2017-03-28)
307 ------------------------------------------------
309 * Clarified meaning of the 'expire' parameter of gpgme_op_createkey
310 and gpgme_op_createsubkey. New flag to force a key without an
313 * New function gpgme_op_keylist_from_data_start to list keys from
314 data objects without importing them.
316 * New function gpgme_op_set_uid_flag to flag a key as primary.
318 * New function gpgme_op_decrypt_ext to run decryption with special
319 flags. This can for example be used to unwrap keys (remove only
320 the encryption layer).
322 * New encryption flags to wrap a key (adding an encryption layer to
323 an OpenPGP message) or to create anonymously encrypted messages.
325 * Support for adduid and revuid operations in the C++ bindings.
327 * Support for smartcard key generation in the C++ bindings.
329 * Several new functions for the Python binding.
331 * Many smaller bug fixes.
333 * Interface changes relative to the 1.8.0 release:
334 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
335 gpgme_op_createkey CHANGED: Meaning of 'expire' parameter.
336 gpgme_op_createsubkey CHANGED: Meaning of 'expire' parameter.
337 GPGME_CREATE_NOEXPIRE NEW.
338 gpgme_key_t EXTENDED: New field 'origin'.
339 gpgme_key_t EXTENDED: New field 'last_update'.
340 gpgme_subkey_t EXTENDED: New field 'is_de_vs'.
341 gpgme_user_id_t EXTENDED: New field 'origin'.
342 gpgme_user_id_t EXTENDED: New field 'last_update'.
343 gpgme_op_keylist_from_data_start NEW.
344 gpgme_op_set_uid_flag_start NEW.
345 gpgme_op_set_uid_flag NEW.
346 gpgme_op_decrypt_ext_start NEW.
347 gpgme_op_decrypt_ext NEW.
348 GPGME_ENCRYPT_THROW_KEYIDS NEW.
349 GPGME_ENCRYPT_WRAP NEW.
350 GPGME_DECRYPT_VERIFY NEW.
351 GPGME_DECRYPT_UNWRAP NEW.
352 gpgme_data_rewind UN-DEPRECATE.
353 cpp: Context::revUid(const Key&, const char*) NEW.
354 cpp: Context::startRevUid(const Key&, const char*) NEW.
355 cpp: Context::addUid(const Key&, const char*) NEW.
356 cpp: Context::startAddUid(const Key&, const char*) NEW.
357 cpp: Key::UserID::revoke() NEW.
358 cpp: Key::addUid() NEW.
359 cpp: Key::isDeVs NEW.
360 cpp: GpgGenCardKeyInteractor NEW.
361 cpp: Subkey::keyGrip NEW.
362 cpp: Subkey::isDeVs NEW.
363 cpp: Data::toKeys NEW.
364 cpp: Context::setDecryptFlags NEW.
365 cpp: Context::decrypt EXTENDED: Flags added.
366 cpp: Context::startDecrypt EXTENDED: Flags added.
367 cpp: Context::decryptAndVerify EXTENDED: Flags added.
368 cpp: Context::startCombinedDecryptionAndVerification EXTENDED: Flags.
369 cpp: Context::encryptFlags EXTENDED: New flags.
370 qt: CryptoConfig::stringValueList() NEW.
371 py: Context.__init__ EXTENDED: New keyword arg home_dir.
372 py: Context.home_dir NEW.
373 py: Context.keylist EXTENDED: New keyword arg mode.
374 py: Context.keylist EXTENDED: New keyword arg source.
375 py: Context.create_key NEW.
376 py: Context.create_subkey NEW.
377 py: Context.key_add_uid NEW.
378 py: Context.key_revoke_uid NEW.
379 py: Context.key_sign NEW.
380 py: Context.key_tofu_policy NEW.
381 py: core.pubkey_algo_string NEW.
382 py: core.addrspec_from_uid NEW.
384 [c=C29/A18/R0 cpp=C10/A4/R0 qt=C9/A2/R0]
387 Noteworthy changes in version 1.8.0 (2016-11-16)
388 ------------------------------------------------
390 * The module of the Python bindings has been renamed to 'gpg'.
392 * New interface to query current software versions.
394 * New feature to use gpg's --{show,override}session-key options.
396 * New interface to set the sender of a mail.
398 * qt: Added Distinguished Name parser from libkleo
400 * The --homedir option is now used with recent gpgconf versions.
402 * On 64 bit Windows systems gpgconf is now properly located.
404 * The internal locking functions have been replaced by libgpg-error
407 * Interface changes relative to the 1.7.1 release:
408 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
409 gpgme_set_sender NEW.
410 gpgme_get_sender NEW.
411 gpgme_op_query_swdb NEW.
412 gpgme_op_query_swdb_result NEW.
413 gpgme_query_swdb_result_t NEW.
414 gpgme_get_ctx_flag NEW.
415 gpgme_decrypt_result_t EXTENDED: New field session_key.
417 qt: DN::Attribute NEW.
418 qt: Job::context(Job*) NEW.
419 cpp: EngineInfo::Version::Version(const char*) NEW.
420 cpp: EngineInfo::Version::Version() NEW.
422 cpp: Context::setSender(const char*) NEW.
423 cpp: Context::getSender() NEW.
425 [c=C28/A17/R0 cpp=C9/A3/R0 qt=C8/A1/R0]
428 Noteworthy changes in version 1.7.1 (2016-10-18)
429 ------------------------------------------------
431 * Fixed problems with the new language bindings.
433 * New helper function gpgme_addrspec_from_uid.
435 * Use option --exit-on-status-write-error with newer gpg versions.
437 * qt: Missed API from the Qt Binding inclusion has
440 * qt: abstractimportjob.h is now installed to that
441 ImportJobs can be used again.
443 * qt: Fixed spelling error in API (startReceive).
445 * Interface changes relative to the 1.7.0 release:
446 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
447 gpgme_addrspec_from_uid NEW.
448 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
449 qt: MultiDeleteJob NEW.
450 qt: AbstractImportJob NEW.
452 cpp: Signature::key(bool, bool) NEW.
453 cpp: UserID::addrSpecFromString(const char*) NEW.
454 cpp: UserID::addrSpec() NEW.
456 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
459 Noteworthy changes in version 1.7.0 (2016-09-21)
460 ------------------------------------------------
462 * New language bindings for Python 2 and 3.
464 * New language Bindings for C++ and the Qt-Framework API.
466 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
467 key creation easier (requires GnuPG 2.1).
469 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
470 management easier (requires GnuPG 2.1).
472 * New function gpgme_op_keysign to make key signing easier (requires
475 * New function gpgme_op_interact to replace the now deprecated
476 functions gpgme_op_edit and gpgme_op_card_edit.
478 * New function gpgme_pubkey_algo_string to convert a public key
479 algorithm into a GnuPG 2.1 style string.
481 * Support for GnuPG 2.1's TOFU trust model.
483 * Notation flags are now correctly set on verify.
485 * New global flag "require-gnupg" to set a minimal gnupg version.
487 * More supported items in gpgme_get_dirinfo.
489 * New function gpgme_data_set_flag and flag "size-hint".
491 * New function gpgme_set_ctx_flag and flags "full-status" and
494 * Improved gpgme_data_identify to distinguish more file types.
496 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
497 mixed public key and symmetric encryption.
499 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
501 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
502 signed data is a valid MIME part. This is to support future GnuPG
505 * Interface changes relative to the 1.6.0 release:
506 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
507 gpgme_pubkey_algo_string NEW.
509 gpgme_set_ctx_flag NEW.
510 gpgme_data_set_flag NEW.
511 gpgme_op_createkey NEW.
512 gpgme_op_createkey_start NEW.
513 gpgme_op_createsubkey NEW.
514 gpgme_op_createsubkey_start NEW.
515 gpgme_op_adduid_start NEW.
517 gpgme_op_revuid_start NEW.
519 gpgme_op_keysign_start NEW.
520 gpgme_op_keysign NEW.
521 gpgme_op_tofu_policy_start NEW.
522 gpgme_op_tofu_policy NEW.
523 gpgme_op_interact_start NEW.
524 gpgme_op_interact NEW.
525 gpgme_interact_cb_t NEW.
526 gpgme_op_edit_start DEPRECATED.
527 gpgme_op_edit DEPRECATED.
528 gpgme_op_card_edit_start DEPRECATED.
529 gpgme_op_card_edit DEPRECATED.
530 gpgme_edit_cb_t DEPRECATED.
531 gpgme_status_code_t DEPRECATED.
532 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
533 gpgme_signature_t EXTENDED: New field key.
534 gpgme_key_t EXTENDED: New field fpr.
535 gpgme_subkey_t EXTENDED: New field keygrip.
536 gpgme_user_id_t EXTENDED: New field tofu.
537 gpgme_tofu_policy_t NEW.
538 gpgme_tofu_info_t NEW.
539 GPGME_STATUS_KEY_CONSIDERED NEW.
540 GPGME_STATUS_TOFU_USER NEW.
541 GPGME_STATUS_TOFU_STATS NEW.
542 GPGME_STATUS_TOFU_STATS_LONG NEW.
543 GPGME_STATUS_NOTATION_FLAGS NEW.
544 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
545 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
546 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
547 GPGME_DATA_ENCODING_MIME NEW.
548 GPGME_ENCRYPT_SYMMETRIC NEW.
549 GPGME_CREATE_SIGN NEW.
550 GPGME_CREATE_ENCR NEW.
551 GPGME_CREATE_CERT NEW.
552 GPGME_CREATE_AUTH NEW.
553 GPGME_CREATE_NOPASSWD NEW.
554 GPGME_CREATE_SELFSIGNED NEW.
555 GPGME_CREATE_NOSTORE NEW.
556 GPGME_CREATE_WANTPUB NEW.
557 GPGME_CREATE_WANTSEC NEW.
558 GPGME_CREATE_FORCE NEW.
559 GPGME_KEYSIGN_LOCAL NEW.
560 GPGME_KEYSIGN_LFSEP NEW.
561 GPGME_INTERACT_CARD NEW.
563 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
566 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
567 ------------------------------------------------
569 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
571 * Added gpgme_set_status_cb to allow a user to see some status
574 * Added an export mode for secret keys.
576 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
578 * The passphrase handler for the loopback mode has been improved and may
579 also be used with genkey.
581 * [w32] The standard GnuPG 2.1 install directory is now searched for
582 gpgconf.exe before a registry specified directory and the Gpg4win
585 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
588 * Interface changes relative to the 1.5.1 release:
589 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
590 gpgme_set_offline NEW.
591 gpgme_get_offline NEW.
592 gpgme_set_status_cb NEW.
593 gpgme_get_status_cb NEW.
594 GPGME_EXPORT_MODE_SECRET NEW
595 GPGME_EXPORT_MODE_RAW NEW.
596 GPGME_EXPORT_MODE_PKCS12 NEW.
599 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
600 ------------------------------------------------
602 * Fixed crash in key listings for user ids with a backslash.
604 * Fixed regression for GPGSM use with GnuPG < 2.1.
606 * Properly set signature summary for revoked OpenPGP keys.
609 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
610 ------------------------------------------------
612 * Fixed a possible crash in the debug code.
614 * Fixed building for Windows with newer versions of Mingw.
617 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
618 -------------------------------------------------------------
620 * The export key functions do now return an error if used with the
621 latest GnuPG version.
624 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
625 -------------------------------------------------------------
627 * gpgme-tool is now installed.
629 * Fix external listing for modern keyservers.
634 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
635 -------------------------------------------------------------
637 * Fixed possible overflow in gpgsm and uiserver engines.
640 * Added support for GnuPG 2.1's --with-secret option.
642 * Interface changes relative to the 1.5.0 release:
643 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
644 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
647 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
648 -------------------------------------------------------------
650 * On Unices the engine file names are not not anymore hardwired but
651 located via the envvar PATH. All options to set the name of the
652 engines for the configure run are removed.
654 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
655 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
656 is not found, GPGME looks for an engine named "gpg".
658 * New feature to use the gpgme I/O subsystem to run arbitrary
661 * New flag to use encryption without the default compression step.
663 * New function to access "gpg-conf --list-dirs"
665 * New configure option --enable-fixed-path for use by Android.
667 * Support ECC algorithms.
669 * Interface changes relative to the 1.4.3 release:
670 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
671 gpgme_get_dirinfo NEW.
672 gpgme_op_spawn_start NEW.
674 GPGME_PROTOCOL_SPAWN NEW.
675 GPGME_SPAWN_DETACHED NEW.
676 GPGME_SPAWN_ALLOW_SET_FG NEW.
677 GPGME_ENCRYPT_NO_COMPRESS NEW.
680 gpgme_subkey_t EXTENDED: New field curve.
681 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
682 GPGME_STATUS_MOUNTPOINT NEW.
683 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
684 GPGME_STATUS_ATTRIBUTE NEW.
685 GPGME_STATUS_BEGIN_SIGNING NEW.
686 GPGME_STATUS_KEY_NOT_CREATED NEW.
689 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
690 -------------------------------------------------------------
692 * The default engine names are now taken from the output of gpgconf.
693 If gpgconf is not found the use of gpg 1 is assumed.
695 * Under Windows the default engines names are first searched in the
696 installation directory of the gpgme DLL.
698 * New function gpgme_data_identify to detect the type of a message.
700 * Interface changes relative to the 1.4.2 release:
701 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
702 gpgme_signers_count NEW.
703 gpgme_data_type_t NEW.
704 gpgme_data_identify NEW.
707 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
708 -------------------------------------------------------------
710 * Allow symmetric encryption with gpgme_op_encrypt_sign.
712 * Fixed mismatching off_t definitions on Windows.
714 * Interface changes relative to the 1.4.1 release:
715 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
718 GPGME_PROTOCOL_OPENPGP NEW alias.
721 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
722 ------------------------------------------------------------
724 * Fixed reading of gpg.conf files with excessive use of the group
727 * Fixed building with the i686-w64-mingw32 toolchain.
729 * Disabled FD passing by default for Apple.
732 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
733 ------------------------------------------------------------
735 * New function gpgme_set_global_flag to help debugging on Android.
737 * New function gpgme_io_writen as a convenience wrapper around
740 * New functions to support the pinentry mode feature of GnuPG 2.1.
742 * New macro GPGME_VERSION_NUMBER to allow supporting different API
743 versions without the need for a configure test.
745 * Several improvements for gpgme-tool.
747 * Better logging of the common "invalid engine" error code.
749 * Support for FD passing is now enabled by default. The configure
750 option --disable-fd-passing may be used to disable this.
752 * Interface changes relative to the 1.3.1 release:
753 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
754 GPGME_VERSION_NUMBER NEW.
756 gpgme_set_global_flag NEW.
757 gpgme_set_pinentry_mode NEW.
758 gpgme_get_pinentry_mode NEW.
759 gpgme_pinentry_mode_t NEW.
760 GPGME_PINENTRY_MODE_DEFAULT NEW.
761 GPGME_PINENTRY_MODE_ASK NEW.
762 GPGME_PINENTRY_MODE_CANCEL NEW.
763 GPGME_PINENTRY_MODE_ERROR NEW.
764 GPGME_PINENTRY_MODE_LOOPBACK NEW.
767 Noteworthy changes in version 1.3.2 (2012-05-02)
768 ------------------------------------------------
770 * Remove support for libgpgme-pth. As far as we know, this was never used,
771 and GnuPG is going to use our own npth in the future.
773 * Fix signature summary information for a missing X.509 key.
775 * Fix parsing of dates >= year 2038.
778 Noteworthy changes in version 1.3.1 (2011-06-16)
779 ------------------------------------------------
781 * Ported to Windows CE.
783 * Detect GPG versions not supporting ---passwd.
785 * Interface changes relative to the 1.3.0 release:
786 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
787 GPGME_EXPORT_MODE_MINIMAL NEW
788 GPGME_STATUS_SUCCESS NEW
789 gpgme_err_code_from_syserror NEW
790 gpgme_err_set_errno NEW
791 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
792 gpgme_error_from_syserror NEW
793 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
796 Noteworthy changes in version 1.3.0 (2010-01-11)
797 ------------------------------------------------
799 * GPGME does not come with an internal libassuan version anymore.
800 The external libassuan 1.1.0 release or later is required. For
801 application programmers on systems that can resolve inter-library
802 dependencies at runtime, this is a transparent change.
804 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
806 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
808 * New API to change the passphrase of a key.
810 * Interface changes relative to the 1.2.0 release:
811 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
812 GPGME_STATUS_INV_SGNR NEW.
813 GPGME_STATUS_NO_SGNR NEW.
814 GPGME_PROTOCOL_G13 NEW.
815 gpgme_op_g13_mount NEW.
816 gpgme_g13_result_t NEW.
819 gpgme_op_passwd_start NEW.
821 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
824 Noteworthy changes in version 1.2.0 (2009-06-18)
825 ------------------------------------------------
827 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
830 * gpgme_new will fail if gpgme_check_version was not called, or a
831 selftest failed (for example, if -mms-bitfields was not used on
834 * New functions gpgme_io_read and gpgme_io_write for use with
835 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
837 * New functions gpgme_result_ref and gpgme_result_unref to detach
838 result structures from a context.
840 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
841 that allow to specify exported keys through gpgme_key_t objects
844 * New mode of operation gpgme_export_mode_t that allows exporting
847 * Interface changes relative to the 1.1.7 release:
848 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
849 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
850 GPGME_PROTOCOL_ASSUAN NEW.
851 gpgme_assuan_data_cb_t NEW.
852 gpgme_assuan_inquire_cb_t NEW.
853 gpgme_assuan_status_cb_t NEW.
854 gpgme_op_assuan_transact_start NEW.
855 gpgme_op_assuan_transact NEW.
856 gpgme_op_assuan_result NEW.
857 gpgme_op_import_keys NEW.
858 gpgme_op_import_keys_start NEW.
859 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
860 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
861 gpgme_check_version CHANGED: Is now a macro.
862 gpgme_new EXTENDED: More failure codes.
865 gpgme_result_ref NEW.
866 gpgme_result_unref NEW.
867 gpgme_export_mode_t NEW.
868 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
869 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
870 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
871 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
872 gpgme_op_export_keys_start NEW.
873 gpgme_op_export_keys NEW.
874 GPGME_DATA_ENCODING_URL NEW.
875 GPGME_DATA_ENCODING_URL0 NEW.
876 GPGME_DATA_ENCODING_URLESC NEW.
877 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
880 Noteworthy changes in version 1.1.8 (2008-12-08)
881 ------------------------------------------------
883 * SIGPIPE is now again ignored as described in the manual. Fixes
884 regression introduced with 1.1.6.
887 Noteworthy changes in version 1.1.7 (2008-10-17)
888 ------------------------------------------------
890 * Using GPGME_KEYLIST_MODE_LOCAL combined with
891 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
892 --locate-keys feature of gpg (>= 2.0.10).
894 * The encoding of gpgme_data_t objects can affect the output encoding
895 of export, sign and encrypt operations now (the same operations
896 that are also affected by the ASCII mode switch). We believe this
897 change in the ABI is innocent enough not to break existing
898 applications (it only affects the S/MIME backend on certain
901 * The reference manual now includes the specification of "The GnuPG
904 * A new function gpgme_cancel_async can be used to asynchronously
905 cancel any pending operation at any time, from any thread.
907 * Interface changes relative to the 1.1.6 release:
908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
909 gpgme_op_encrypt CHANGED: Output encoding can affect result.
910 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
911 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
912 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
913 gpgme_op_sign CHANGED: Output encoding can affect result.
914 gpgme_op_sign_start CHANGED: Output encoding can affect result.
915 gpgme_op_export CHANGED: Output encoding can affect result.
916 gpgme_op_export_start CHANGED: Output encoding can affect result.
917 gpgme_op_export_ext CHANGED: Output encoding can affect result.
918 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
919 gpgme_cancel_async NEW
920 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
923 Noteworthy changes in version 1.1.6 (2008-01-04)
924 ------------------------------------------------
926 * Bug fixes for for W32.
928 * A new, experimental (and thus undocumented and potentially
929 unstable) interface for accessing gpg-conf through GPGME has been
932 * Interface changes relative to the 1.1.1 release:
933 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
934 gpgme_signature_t EXTENDED: New field chain_model.
935 gpgme_op_getauditlog_start NEW.
936 gpgme_op_getauditlog NEW.
937 GPGME_AUDITLOG_HTML NEW.
938 GPGME_AUDITLOG_WITH_HELP NEW.
939 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
942 Noteworthy changes in version 1.1.5 (2007-07-09)
943 ------------------------------------------------
945 * Bug and portability fixes (mainly for W32).
948 Noteworthy changes in version 1.1.4 (2007-03-05)
949 ------------------------------------------------
951 * Detect and bail out on double plaintext messages. This is required
952 so that applications can properly detect the signed parts of a
953 message. Actual there is now a double protection as GnuPG 1.4.7
954 will detect this case too.
957 Noteworthy changes in version 1.1.3 (2007-01-29)
958 ------------------------------------------------
960 * Fixed a memory leak in gpgme_data_release_and_get_mem.
962 * Fixed a bug in Windows command line quoting.
965 Noteworthy changes in version 1.1.2 (2006-03-02)
966 ------------------------------------------------
968 * Fixed a bug in the W32 glib backend.
971 Noteworthy changes in version 1.1.1 (2006-02-23)
972 ------------------------------------------------
974 * Fixed a bug in that the fingerprints of subkeys are not available.
976 * Clarified usage of the SECRET flag in key listings. It is now
979 * Reading signature notations and policy URLs on key signatures is
980 supported. They can be found in the new field notations of the
981 gpgme_key_sig_t structure. This has to be enabled with the keylist
982 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
984 * A new gpgme_free() function solves the problem of using different
985 allocators in a single program. This function should now be used
986 instead calling free() to release the buffer returned by
987 gpgme_data_release_and_get_mem. It is recommended that you always
988 do this, but it is only necessary on certain platforms, so backwards
989 compatibility is provided. In other words: If free() worked for
990 you before, it will keep working.
992 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
993 They are analyzed by the verify handlers and made available in the
994 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
996 * Interface changes relative to the 1.1.0 release:
997 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
998 gpgme_key_sig_t EXTENDED: New field notations.
999 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
1001 GPGME_STATUS_PKA_TRUST_BAD NEW
1002 GPGME_STATUS_PKA_TRUST_GOOD NEW
1003 gpgme_signature_t EXTENDED: New field pka_trust.
1004 gpgme_signature_t EXTENDED: New field pka_address.
1005 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1008 Noteworthy changes in version 1.1.0 (2005-10-01)
1009 ------------------------------------------------
1011 * You can now configure the backend engine file name and home
1012 directory to be used, as default and per context.
1014 * Information about the recipients of an encrypted text is now
1015 available at decryption time.
1017 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
1018 and verify handlers, the information about the plaintext filename,
1019 if available is made available in the new field file_name of the
1020 respective result structure.
1022 * The code for "automagically detecting the thread library" has been
1023 removed from libgpgme. It is deprecated since version 0.4.3.
1024 Since then, you had to link against libgpgme-pthread for
1025 applications using pthread and libgpgme-pth for applications using
1028 The code was removed because it caused compilation problems on
1029 systems where the pthread.h header from GNU Pth is available in
1030 addition to the system header (FreeBSD 6 and later for example).
1032 * "./autogen.sh --build-w32" does now build gpgme.dll.
1034 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
1035 delimiter. The standard install directory is used when locating
1036 gpg or gpgsm before finally falling back to the hardwired name.
1038 * There is a new flag for keys and subkeys, is_qualified, which
1039 indicates if a key can be used for qualified signatures according
1040 to local government regulations.
1042 * You can associate a filename with a data object using the new
1043 function gpgme_data_set_file_name(). This filename will be stored
1044 in the output when encrypting or signing the data and will be
1045 returned when decrypting or verifying the output data.
1047 * You can now set notation data at signature creation with the new
1048 function gpgme_sig_notation_add().
1050 * Interface changes relative to the 1.0.3 release:
1051 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1052 gpgme_set_engine_info NEW
1053 gpgme_ctx_get_engine_info NEW
1054 gpgme_ctx_set_engine_info NEW
1055 gpgme_recipient_t NEW
1056 gpgme_decrypt_result_t EXTENDED: New field recipients.
1057 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
1058 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
1059 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
1060 GPGME_STATUS_PLAINTEXT NEW
1061 gpgme_key_t EXTENDED: New field is_qualified.
1062 gpgme_subkey_t EXTENDED: New field is_qualified.
1063 gpgme_data_get_file_name NEW
1064 gpgme_data_set_file_name NEW
1065 gpgme_sig_notation_flags_t NEW
1066 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
1067 GPGME_SIG_NOTATAION_CRITICAL NEW
1068 gpgme_sig_notation_clear NEW
1069 gpgme_sig_notation_add NEW
1070 gpgme_sig_notation_get NEW
1071 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1074 Noteworthy changes in version 1.0.3 (2005-06-20)
1075 ------------------------------------------------
1077 * Previousy, GPGME would use a default "include certs" of 1. This
1078 has been changed. Now GPGME will use the crypto backend engines
1079 default unless you set the value with gpgme_set_include_certs()
1080 explicitly. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
1081 as a value to explicitly request the new default behaviour.
1083 Because the default changes, this is a slight change of the API
1084 semantics. We consider it to be a bug fix.
1086 * A bug which made GPGME hang has been fixed. If you have
1087 experienced hanging before, please try out this version and let me
1088 know if you still experience hanging problems.
1090 * Interface changes relative to the 0.9.0 release:
1091 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1092 gpgme_set_include_certs CHANGED DEFAULT
1093 GPGME_INCLUDE_CERTS_DEFAULT NEW
1094 GPGME_STATUS_SIG_SUBPACKET NEW
1095 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
1096 GPGME_STATUS_SC_OP_FAILURE NEW
1097 GPGME_STATUS_SC_OP_SUCCESS NEW
1098 GPGME_STATUS_CARDCTRL NEW
1099 GPGME_STATUS_BACKUP_KEY_CREATED NEW
1100 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1103 Noteworthy changes in version 1.0.2 (2004-12-28)
1104 ------------------------------------------------
1106 * Changed the license of the library to the GNU Lesser General Public
1107 License (LGPL), version 2.1 or later.
1110 Noteworthy changes in version 1.0.1 (2004-10-22)
1111 ------------------------------------------------
1116 Noteworthy changes in version 1.0.0 (2004-09-30)
1117 ------------------------------------------------
1119 * Version 1.0.0! We are proud to present you with a thoroughly
1120 tested and stable version of the GPGME library. A big Thank You!
1121 to all the people who made this possible.
1123 The development will be branched into a stable 1.x.y series and the
1126 * The gpgme.m4 macro supports checking the API version. Just prepend
1127 it to the required version string, separated by a colon. For
1128 example, this release has the version "1:1.0.0". The last release
1129 to which this version is (mostly) ABI compatible is "1:0.4.2",
1130 which is the default required version.
1133 Noteworthy changes in version 0.9.0 (2004-06-08)
1134 ------------------------------------------------
1136 * The type gpgme_key_t has now a new field keylist_mode that contains
1137 the keylist mode that was active at the time the key was retrieved.
1139 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
1140 that contains a flag indicating that the key should not have been
1141 used for encryption.
1143 * Verifying a signature of a revoked key gives the correct result now
1144 (GPG_ERR_CERT_REVOKED error code).
1146 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
1147 verify operations still allows you to look at the signature
1148 verification result.
1150 * Clarified that patterns in keylisting operations have an upper
1151 limit, and thus are not suited to list many keys at once by their
1152 fingerprint. Also improve the error message if the pattern is too
1153 long for the CMS protocol to handle.
1155 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1156 gpgme_key_t EXTENDED: New field keylist_mode.
1157 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
1158 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1161 Noteworthy changes in version 0.4.7 (2004-04-29)
1162 ------------------------------------------------
1164 * Correctly initialize the fields expired, revoked, invalid, and
1165 disabled in the gpgme_key_t structures.
1167 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
1168 accidentally of type int instead unsigned int.
1170 * Interface changes relative to the 0.4.5 release:
1171 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1172 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
1173 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1175 Noteworthy changes in version 0.4.6 (2004-04-06)
1176 ------------------------------------------------
1181 Noteworthy changes in version 0.4.5 (2004-03-07)
1182 ------------------------------------------------
1184 * GPGME is now compiled with LFS (large file support) by default.
1185 This means that _all_ programs using GPGME must be compiled with
1186 LFS support enabled by default. You can do this easily with
1187 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
1188 without autoconf by defining the preprocessor symbol
1189 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
1190 the C compiler command line, or by defining this preprocessor
1191 symbol before including any system header files). For more
1192 details, read the section on LFS in the manual.
1194 Up to now, it was undocumented that GPGME was not using LFS.
1195 But the public interfaces use off_t, and file descriptors are
1196 exchanged between the application and GPGME. This was an oversight,
1197 and bound to cause troubles in the future.
1199 Writing GPGME as a dual mode library that seamlessly supports LFS
1200 while keeping backwards compatibility is possible, but does not
1201 solve the problem: Many applications already expect GPGME to have
1202 LFS (they are compiled with off_t being a 64bit value). This is true
1203 in particular for the popular Gtk+ and Qt programs.
1205 So, although this is an ABI (but not an API) break, we will not
1206 change the library version to reflect that. Because the interfaces
1207 affected are probably not used yet in any GPGME 0.4 based
1208 application, we don't expect any real failures from this change.
1209 In fact, applications already using LFS will have some subtle bugs
1212 However, if you encounter an application using GPGME 0.4.x that
1213 does _not_ use LFS by default (off_t is a 32bit value), _and_
1214 uses at least one of the functions gpgme_data_seek,
1215 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
1216 gpgme_data_new_from_cbs, then indeed this library will be ABI
1217 incompatible with the program. As said above, we don't believe
1218 such a program exists. If we are in error, then you have two
1219 options: As a quick hack, you can configure GPGME with the
1220 --disable-largefile option. This will revert the change, and GPGME
1221 will not use LFS. However, GPGME will be incompatible with
1222 programs that expect GPGME to use LFS. All applications are
1223 required to use LFS when using GPGME, so this is only good as a
1224 temporary local work-around.
1226 The other option is to change the versioning of the library and
1227 recompile all applications. We have reserved a special version of
1228 the library for that, so you can do that without expecting a
1229 version clash in the future. Furthermore, everyone who does this
1230 will agree on the version to use (this is important for
1231 distribution makers). Read the comment in configure.ac (before
1232 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
1233 blindly: As stated above, we think it is unlikely this measure is
1234 needed. Still, it is there if necessary. If in doubt, contact us
1235 and we will give our advise for your specific situation.
1237 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
1240 * New interface gpgme_cancel() that can be used to cancel
1241 asynchronous operations.
1243 * Interface changes relative to the 0.4.4 release:
1244 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1245 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
1246 gpgme_data_seek CHANGED: off_t is now a largefile type.
1247 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
1248 GPGME_KEYLIST_MODE_VALIDATE NEW
1250 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1252 Noteworthy changes in version 0.4.4 (2004-01-12)
1253 ------------------------------------------------
1255 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
1256 been renamed to "sig_class", to avoid clash with C++ compilers. In
1257 the C API, the old name "class" has been preserved for backwards
1258 compatibility, but is deprecated.
1260 * Interface changes relative to the 0.4.3 release:
1261 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1262 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
1263 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
1264 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1266 Noteworthy changes in version 0.4.3 (2003-10-06)
1267 ------------------------------------------------
1269 * libgpgme should not be used for threaded programs anymore. This
1270 never worked reliably in all cases, because you had to
1271 be careful about the linking order and libtool wouldn't do that for
1272 you automatically. Instead, now you have to link against
1273 libgpgme-pthread for applications using pthread and libgpgme-pth for
1274 applications using GNU Pth.
1276 The old code for automagically detecting the thread library is
1277 still part of libgpgme, but it is DEPRECATED.
1279 * There are new automake macros AM_PATH_GPGME_PTH and
1280 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
1281 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
1282 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
1283 variables of course also include the configuration for the thread
1284 package itself. Alternatively, use libtool.
1286 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
1289 * gpgme-config doesn't support setting the prefix or exec prefix
1290 anymore. I don't think it ever worked correctly, and it seems to
1293 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
1294 provided was not unique, instead returning the first matching key.
1296 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
1297 that indicates if the key can be used for authentication.
1299 * gpgme_signature_t's status field is now correctly set to an error
1300 with error code GPG_ERR_NO_PUBKEY if public key is not found.
1302 * gpgme_new_signature_t's class field is now an unsigned int, rather
1303 than an unsigned long (the old class field is preserved for
1304 backwards compatibility).
1306 * A new function gpgme_set_locale() is provided to allow configuring
1307 the locale for the crypto backend. This is necessary for text
1308 terminals so that programs like the pinentry can be started with
1309 the right locale settings for the terminal the application is running
1310 on, in case the terminal has different settings than the system
1311 default (for example, if it is a remote terminal). You are highly
1312 recommended to call the following functions directly after
1313 gpgme_check_version:
1317 setlocale (LC_ALL, "");
1318 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
1319 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
1321 GPGME can not do this for you, as setlocale is not thread safe, and
1322 there is no alternative.
1324 * The signal action for SIGPIPE is now set to SIG_IGN by
1325 gpgme_check_version, instead the first time a crypto engine is
1326 started (which is not well defined).
1328 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
1329 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
1330 to CRC24RFC2440. For now, these strings can be used as the MIC
1331 parameter for PGP/MIME (if appropriately modified).
1333 * Interface changes relative to the 0.4.2 release:
1334 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1335 gpgme_strerror_t NEW
1336 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
1337 gpgme_key_t EXTENDED: New field can_authenticate.
1338 gpgme_subkey_t EXTENDED: New field can_authenticate.
1339 gpgme_new_signature_t CHANGED: New type for class field.
1340 gpgme_set_locale NEW
1341 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
1342 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1344 Noteworthy changes in version 0.4.2 (2003-07-30)
1345 ------------------------------------------------
1347 * Allow gpg-error to be in non-standard place when linking the test suite.
1349 * Configure will fail now if gpg-error can not be found.
1351 * Fixed initialized memory backed data objects for writing, which
1352 caused the test program to crash (but only on Mac OS, surprisingly).
1354 * Eliminate use of C99 constructs.
1356 * Small improvements to the manual.
1359 Noteworthy changes in version 0.4.1 (2003-06-06)
1360 ------------------------------------------------
1362 This is the release that 0.4.0 should have been. There are many
1363 interface changes, please see below for the details. The changes are
1364 sometimes the result of new functionality, but more often express a
1365 paradigm shift. Others are an overdue cleanup to get GPGME in line
1366 with the GNU coding standards and to make the interface more
1367 self-consistent. Here is an overview on the changes:
1369 All types have been renamed to conform to the GNU coding standards,
1370 most of the time by keeping the whole name in lowercase and inserting
1371 underscores between words.
1373 All operations consistently only accept input parameters in their
1374 invocation function, and return only an error code directly. Further
1375 information about the result of the operation has to be retrieved
1376 afterwards by calling one of the result functions. This unifies the
1377 synchronous and the asynchronous interface.
1379 The error values have been completely replaced by a more
1380 sophisticated model that allows GPGME to transparently and accurately
1381 report all errors from the other GnuPG components, regardless of
1382 process boundaries. This is achieved by using the library
1383 libgpg-errors, which is shared by all GnuPG components. This library
1384 is now required for GPGME.
1386 The results of all operations are now provided by pointers to C
1387 structs rather than by XML structs or in other ways.
1389 Objects which used to be opaque (for example a key) are now pointers
1390 to accessible structs, so no accessor functions are necessary.
1392 Backward compatibility is provided where it was possible without too
1393 much effort and did not collide with the overall sanitization effort.
1394 However, this is only for ease of transition. NO DEPRECATED FUNCTION
1395 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
1396 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
1397 Recommendations how to replace deprecated or removed functionality
1398 can be found within the description of each change.
1400 What follows are all changes to the interface and behaviour of GPGME
1403 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
1404 deprecated attributes will warn about use of obsolete functions and
1405 type definitions. You can suppress these warnings by passing
1406 -Wno-deprecated-declarations to the gcc command.
1408 * The following types have been renamed. The old types are still
1409 available as aliases, but they are deprecated now:
1411 GpgmeCtx gpgme_ctx_t
1412 GpgmeData gpgme_data_t
1413 GpgmeError gpgme_error_t
1414 GpgmeDataEncoding gpgme_data_encoding_t
1415 GpgmeSigStat gpgme_sig_stat_t
1416 GpgmeSigMode gpgme_sig_mode_t
1417 GpgmeAttr gpgme_attr_t
1418 GpgmeValidity gpgme_validity_t
1419 GpgmeProtocol gpgme_protocol_t
1420 GpgmeKey gpgme_key_t
1421 GpgmePassphraseCb gpgme_passphrase_cb_t
1422 GpgmeProgressCb gpgme_progress_cb_t
1423 GpgmeIOCb gpgme_io_cb_t
1424 GpgmeRegisterIOCb gpgme_register_io_cb_t
1425 GpgmeRemoveIOCb gpgme_remove_io_cb_t
1426 GpgmeEventIO gpgme_event_io_t
1427 GpgmeEventIOCb gpgme_event_io_cb_t
1428 GpgmeIOCbs gpgme_io_cbs
1429 GpgmeDataReadCb gpgme_data_read_cb_t
1430 GpgmeDataWriteCb gpgme_data_write_cb_t
1431 GpgmeDataSeekCb gpgme_data_seek_cb_t
1432 GpgmeDataReleaseCb gpgme_data_release_cb_t
1433 GpgmeDataCbs gpgme_data_cbs_t
1434 GpgmeTrustItem gpgme_trust_item_t
1435 GpgmeStatusCode gpgme_status_code_t
1437 * gpgme_error_t is now identical to gpg_error_t, the error type
1438 provided by libgpg-error. More about using libgpg-error with GPGME
1439 can be found in the manual. All error symbols have been removed!
1441 * All functions and types in libgpg-error have been wrapped in GPGME.
1442 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1443 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1444 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1445 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1448 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1450 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1451 for encrypt, sign, encrypt-sign, decrypt, verify, and
1452 decrypt-verify operations. For verify operations on detached
1453 signatures, the progress callback is invoked for both the detached
1454 signature and the plaintext message, though.
1456 * gpgme_passphrase_cb_t has been changed to not provide a complete
1457 description, but the UID hint, passphrase info and a flag
1458 indicating if this is a repeated attempt individually, so the user
1459 can compose his own description from this information.
1461 The passphrase is not returned as a C string, but must be written
1462 to a file descriptor directly. This allows for secure passphrase
1465 The return type has been changed to gpgme_error_t value. This
1466 allowed to remove the gpgme_cancel function; just return
1467 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1469 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1470 The user is expected to write the response to the file descriptor,
1471 followed by a newline.
1473 * The recipients interface has been removed. Instead, you use
1474 NULL-terminated lists of keys for specifying the recipients of an
1475 encryption operation. Use the new encryption flag
1476 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1477 the keys (but note that in general this is not a good idea).
1479 This change has been made to the prototypes of gpgme_op_encrypt,
1480 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1481 gpgme_op_encrypt_sign_start.
1483 The export interface has been changed to use pattern strings like
1484 the keylist interface. Thus, new functions gpgme_op_export_ext and
1485 gpgme_op_export_ext_start have been added as well. Now the
1486 prototypes of gpgme_op_export_start and gpgme_op_export finally
1489 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1490 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1493 * gpgme_io_cb_t changed from a void function to a function returning
1494 a gpgme_error_t value. However, it will always return 0, so you
1495 can safely ignore the return value.
1497 * A new I/O callback event GPGME_EVENT_START has been added. The new
1498 requirement is that you must wait until this event until you are
1499 allowed to call the I/O callback handlers previously registered for
1500 this context operation. Calling I/O callback functions for this
1501 context operation before the start event happened is unsafe because
1502 it can lead to race conditions in a multi-threaded environment.
1504 * The idle function feature has been removed. It was not precisely
1505 defined in a multi-threaded environment and is obsoleted by the
1506 user I/O callback functions. If you still need a simple way to
1507 call something while waiting on one or multiple asynchronous
1508 operations to complete, don't set the HANG flag in gpgme_wait (note
1509 that this will return to your program more often than the idle
1512 * gpgme_wait can return NULL even if hang is true, if an error
1513 occurs. In that case *status contains the error code.
1515 * gpgme_get_engine_info was radically changed. Instead an XML
1516 string, an info structure of the new type gpgme_engine_info_t is
1517 returned. This makes it easier and more robust to evaluate the
1518 information in an application.
1520 * The new function gpgme_get_protocol_name can be used to convert a
1521 gpgme_protocol_t value into a string.
1523 * The status of a context operation is not checked anymore. Starting
1524 a new operation will silently cancel the previous one. Calling a
1525 function that requires you to have started an operation before without
1526 doing so is undefined.
1528 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1529 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1530 pointer to a structure which contains the fingerprint. This also
1531 works with gpgme_op_genkey_start. The structure also provides
1532 other information about the generated keys.
1537 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1539 printf ("%s\n", fpr);
1543 gpgme_genkey_result_t result;
1544 err = gpgme_op_genkey (ctx, NULL, NULL);
1547 result = gpgme_op_genkey_result (ctx);
1549 printf ("%s\n", result->fpr);
1552 * The new gpgme_op_import_result function provides detailed
1553 information about the result of an import operation in
1554 gpgme_import_result_t and gpgme_import_status_t objects.
1555 Thus, the gpgme_op_import_ext variant is deprecated.
1557 * The new gpgme_op_sign_result function provides detailed information
1558 about the result of a signing operation in gpgme_sign_result_t,
1559 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1561 * The new gpgme_op_encrypt_result function provides detailed
1562 information about the result of an encryption operation in
1563 a GpgmeEncryptResult object.
1565 * The new gpgme_op_decrypt_result function provides detailed
1566 information about the result of a decryption operation in
1567 a GpgmeDecryptResult object.
1569 * The new gpgme_op_verify_result function provides detailed
1570 information about the result of an verify operation in
1571 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1572 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1573 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1574 and gpgme_get_notation is removed.
1576 * GpgmeTrustItem objects have now directly accessible data, so the
1577 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1578 accessor functions are deprecated. Also, reference counting is
1579 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1580 (the gpgme_trust_item_release alias for the latter is deprecated).
1582 * Keys are not cached internally anymore, so the force_update argument
1583 to gpgme_get_key has been removed.
1585 * GpgmeKey objects have now directly accessible data so the
1586 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1587 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1588 functions are deprecated. Also, gpgme_key_release is now
1589 deprecated. The gpgme_key_get_as_xml function has been dropped.
1591 * Because all interfaces using attributes are deprecated, the
1592 GpgmeAttr data type is also deprecated.
1594 * The new gpgme_op_keylist_result function provides detailed
1595 information about the result of a key listing operation in
1596 a GpgmeKeyListResult object.
1598 * Now that each function comes with its own result retrieval
1599 interface, the generic gpgme_get_op_info interface is not useful
1600 anymore and dropped.
1602 * The type and mode of data objects is not available anymore.
1604 * Interface changes relative to the 0.4.0 release:
1605 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1606 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1607 GpgmeData DEPRECATED: Use gpgme_data_t.
1608 GpgmeError DEPRECATED: Use gpgme_error_t.
1609 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1610 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1611 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1612 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1613 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1614 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1615 GpgmeKey DEPRECATED: Use gpgme_key_t.
1616 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1617 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1618 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1619 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1620 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1621 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1622 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1623 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1624 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1625 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1626 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1627 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1628 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1629 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1630 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1633 gpgme_recipients_t NEW
1635 gpgme_data_encoding_t NEW
1636 gpgme_sig_stat_t NEW
1637 gpgme_sig_mode_t NEW
1639 gpgme_validity_t NEW
1640 gpgme_protocol_t NEW
1642 gpgme_passphrase_cb_t NEW
1643 gpgme_progress_cb_t NEW
1645 gpgme_register_io_cb_t NEW
1646 gpgme_remove_io_cb_t NEW
1647 gpgme_event_io_t NEW
1648 gpgme_event_io_cb_t NEW
1650 gpgme_data_read_cb_t NEW
1651 gpgme_data_write_cb_t NEW
1652 gpgme_data_seek_cb_t NEW
1653 gpgme_data_release_cb_t NEW
1654 gpgme_data_cbs_t NEW
1655 gpgme_trust_item_t NEW
1656 gpgme_status_code_t NEW
1657 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1658 gpgme_err_code_t NEW
1659 gpgme_err_source_t NEW
1661 gpgme_err_source NEW
1664 gpgme_error_from_errno NEW
1665 gpgme_err_make_from_errno NEW
1666 gpgme_err_code_from_errno NEW
1667 gpgme_err_code_to_errno NEW
1669 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1670 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1671 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1672 gpgme_edit_cb_t CHANGED: Write directly to FD.
1673 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1674 gpgme_op_verify CHANGED: Drop R_STAT argument.
1675 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1676 gpgme_wait CHANGED: Can return NULL even if hang is true.
1677 GpgmeIdleFunc REMOVED
1678 gpgme_register_idle REMOVED
1679 GpgmeRecipients REMOVED
1680 gpgme_recipients_new REMOVED
1681 gpgme_recipients_release REMOVED
1682 gpgme_recipients_add_name REMOVED
1683 gpgme_recipients_add_name_with_validity REMOVED
1684 gpgme_recipients_count REMOVED
1685 gpgme_recipients_enum_open REMOVED
1686 gpgme_recipients_enum_read REMOVED
1687 gpgme_recipients_enum_close REMOVED
1688 gpgme_encrypt_flags_t NEW
1689 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1690 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1691 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1692 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1693 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1694 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1695 gpgme_op_export CHANGED: User IDs passed as patterns.
1696 gpgme_op_export_ext_start NEW
1697 gpgme_op_export_ext NEW
1698 gpgme_keylist_mode_t NEW
1700 gpgme_engine_info_t NEW
1701 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1702 gpgme_get_protocol_name NEW
1703 gpgme_cancel REMOVED: Return error in callback directly.
1704 gpgme_op_genkey CHANGED: FPR argument dropped.
1705 gpgme_op_genkey_result NEW
1706 gpgme_genkey_result_t NEW
1707 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1708 gpgme_op_import_result NEW
1709 gpgme_import_status_t NEW
1710 gpgme_import_result_t NEW
1711 gpgme_pubkey_algo_t NEW
1712 gpgme_hash_algo_t NEW
1713 gpgme_invalid_key_t NEW
1714 gpgme_new_signature_t NEW
1715 gpgme_sign_result_t NEW
1716 gpgme_op_sign_result NEW
1717 gpgme_pubkey_algo_name NEW
1718 gpgme_hash_algo_name NEW
1719 gpgme_encrypt_result_t NEW
1720 gpgme_op_encrypt_result NEW
1721 gpgme_decrypt_result_t NEW
1722 gpgme_op_decrypt_result NEW
1723 gpgme_verify_result_t NEW
1724 gpgme_op_verify_result NEW
1725 gpgme_get_notation REMOVED: Access verify result directly instead.
1726 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1727 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1728 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1729 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1730 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1731 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1732 gpgme_trust_item_ref NEW
1733 gpgme_trust_item_unref NEW
1734 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1735 gpgme_trust_item_get_string_attr DEPRECATED
1736 gpgme_trust_item_get_ulong_attr DEPRECATED
1737 gpgme_get_key CHANGED: Removed force_update argument.
1741 gpgme_key_t CHANGED: Now has user accessible data members.
1742 gpgme_key_get_string_attr DEPRECATED
1743 gpgme_key_get_ulong_attr DEPRECATED
1744 gpgme_key_sig_get_string_attr DEPRECATED
1745 gpgme_key_sig_get_ulong_attr DEPRECATED
1746 gpgme_key_get_as_xml REMOVED
1747 gpgme_key_list_result_t NEW
1748 gpgme_op_keylist_result NEW
1749 gpgme_get_op_info REMOVED
1750 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1752 Noteworthy changes in version 0.4.0 (2002-12-23)
1753 ------------------------------------------------
1755 * Key generation returns the fingerprint of the generated key.
1757 * New convenience function gpgme_get_key.
1759 * Supports signatures of user IDs in keys via the new
1760 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1761 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1762 interfaces. The XML info about a key also includes the signatures
1765 * New data object interface, which is more flexible and transparent.
1767 * Interface changes relative to the 0.3.9 release:
1768 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1770 GpgmeDataWriteCb NEW
1772 GpgmeDataReleaseCb NEW
1774 gpgme_data_read CHANGED: Match read() closely.
1775 gpgme_data_write CHANGED: Match write() closely.
1777 gpgme_data_new_from_fd NEW
1778 gpgme_data_new_from_stream NEW
1779 gpgme_data_new_from_cbs NEW
1780 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1781 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1782 gpgme_data_get_type REMOVED: No replacement.
1783 gpgme_op_verify CHANGED: Take different data objects for
1784 signed text and plain text.
1785 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1786 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1787 gpgme_op_genkey CHANGED: New parameter FPR.
1788 GPGME_KEYLIST_MODE_SIGS NEW
1789 gpgme_key_sig_get_string_attr NEW
1790 gpgme_key_sig_get_ulong_attr NEW
1792 GPGME_ATTR_SIG_CLASS NEW
1793 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1795 Noteworthy changes in version 0.3.16 (2003-11-19)
1796 -------------------------------------------------
1798 * Compatibility fixes for GnuPG 1.9.x
1800 Noteworthy changes in version 0.3.15 (2003-02-18)
1801 -------------------------------------------------
1803 * The progress status is sent via the progress callbacks in
1806 * Bug fix for signing operations with explicit signer settings for
1809 Noteworthy changes in version 0.3.14 (2002-12-04)
1810 -------------------------------------------------
1812 * GPGME-Plug is now in its own package "cryptplug".
1814 * Workaround for a setlocale problem. Fixed a segv related to not
1815 correctly as closed marked file descriptors.
1817 Noteworthy changes in version 0.3.13 (2002-11-20)
1818 -------------------------------------------------
1820 * Release due to changes in gpgmeplug.
1822 Noteworthy changes in version 0.3.12 (2002-10-15)
1823 -------------------------------------------------
1825 * Fixed some bux with key listings.
1827 * The development has been branched to clean up some API issues.
1828 This 0.3 series will be kept for compatibility reasons; so do don't
1829 expect new features.
1831 Noteworthy changes in version 0.3.11 (2002-09-20)
1832 -------------------------------------------------
1836 Noteworthy changes in version 0.3.10 (2002-09-02)
1837 -------------------------------------------------
1839 * Setting the signing keys for the CMS protocol does now work.
1841 * The signers setting is honoured by gpgme_op_edit.
1843 Noteworthy changes in version 0.3.9 (2002-08-21)
1844 ------------------------------------------------
1846 * A spec file for creating RPMs has been added.
1848 * An experimental interface to GnuPG's --edit-key functionality is
1849 introduced, see gpgme_op_edit.
1851 * The new gpgme_import_ext function provides a convenient access to
1852 the number of processed keys.
1854 * Interface changes relative to the 0.3.8 release:
1855 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1858 gpgme_op_edit_start NEW
1860 gpgme_op_import_ext NEW
1861 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1863 Noteworthy changes in version 0.3.8 (2002-06-25)
1864 ------------------------------------------------
1866 * It is possible to use an outside event loop for the I/O to the
1867 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1869 * Interface changes relative to the 0.3.6 release:
1870 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1872 GpgmeRegisterIOCb NEW
1876 struct GpgmeIOCbs NEW
1877 gpgme_set_io_cbs NEW
1878 gpgme_get_io_cbs NEW
1879 GPGME_ATTR_ERRTOK NEW
1880 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1882 Noteworthy changes in version 0.3.7 (2002-06-04)
1883 ------------------------------------------------
1885 * GPGME_ATTR_OTRUST is implemented now.
1887 * A first step toward thread safeness has been achieved, see the
1888 documentation for details. Supported thread libraries are pthread
1891 Noteworthy changes in version 0.3.6 (2002-05-03)
1892 ------------------------------------------------
1894 * All error output of the gpgsm backend is send to the bit bucket.
1896 * The signature verification functions are extended. Instead of
1897 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1898 expired signatures. 2 new functions may be used to retrieve more
1899 detailed information like the signature expiration time and a
1900 validity information of the key without an extra key looking.
1902 * The current passphrase callback and progress meter callback can be
1903 retrieved with the new functions gpgme_get_passphrase_cb and
1904 gpgme_get_progress_cb respectively.
1906 * Interface changes relative to the 0.3.5 release:
1907 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1908 gpgme_get_passphrase_cb NEW
1909 gpgme_get_progress_cb NEW
1910 GpgmeDataEncoding NEW
1911 gpgme_data_set_encoding NEW
1912 gpgme_data_get_encoding NEW
1913 GPGME_SIG_STAT_GOOD_EXP NEW
1914 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1915 gpgme_op_verify CHANGED: Returns more status codes.
1916 GPGME_ATTR_SIG_STATUS NEW
1917 gpgme_get_sig_string_attr NEW
1918 gpgme_get_sig_ulong_attr NEW
1919 gpgme_get_protocol NEW
1920 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1922 Noteworthy changes in version 0.3.5 (2002-04-01)
1923 ------------------------------------------------
1925 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1926 case, symmetric encryption is performed. Note that this requires a
1927 passphrase from the user.
1929 * More information is returned for X.509 certificates.
1931 * Interface changes relative to the 0.3.4 release:
1932 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1933 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1934 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1936 Noteworthy changes in version 0.3.4 (2002-03-04)
1937 ------------------------------------------------
1939 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1940 some recipients have been invalid, whereas earlier versions
1941 succeeded in this case. The plaintext is still encrypted for all valid
1942 recipients, so the application might take this error as a hint that
1943 the ciphertext is not usable for all requested recipients.
1944 Information about invalid recipients is available with gpgme_get_op_info.
1946 * gpgme_op_verify now allows to pass an uninitialized data object as
1947 its plaintext argument to check for normal and cleartext
1948 signatures. The plaintext is then returned in the data object.
1950 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1951 to set and get the number of certifications to include in S/MIME
1954 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1955 to encrypt and sign a message in a combined operation.
1957 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1959 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1961 * Interface changes relative to the 0.3.3 release:
1962 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1963 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1964 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1965 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1966 gpgme_set_include_certs NEW
1967 gpgme_get_include_certs NEW
1968 gpgme_op_encrypt_sign NEW
1969 gpgme_op_encrypt_sign_start NEW
1970 gpgme_op_keylist_ext_start NEW
1971 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1973 Noteworthy changes in version 0.3.3 (2002-02-12)
1974 ------------------------------------------------
1976 * Fix the Makefile in jnlib.
1978 * Fix the test suite (hopefully). It should clean up all its state
1979 with `make check' now.
1982 Noteworthy changes in version 0.3.2 (2002-02-10)
1983 ------------------------------------------------
1985 * Remove erroneous dependency on libgcrypt in jnlib.
1988 Noteworthy changes in version 0.3.1 (2002-02-09)
1989 ------------------------------------------------
1991 * There is a Texinfo manual documenting the API.
1993 * The gpgme_set_keylist_mode function returns an error, and changed
1994 its meaning. It is no longer usable to select between normal and
1995 fast mode (newer versions of GnuPG will always be fast), but
1996 selects between local keyring, remote keyserver, or both.
1997 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1998 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1999 current setting, a function gpgme_get_keylist_mode was added to
2000 retrieve the current mode.
2002 * gpgme_wait accepts a new argument STATUS to return the error status
2003 of the operation on the context. Its definition is closer to
2004 waitpid() now than before.
2006 * The LENGTH argument to gpgme_data_new_from_filepart changed its
2007 type from off_t to the unsigned size_t.
2009 * The R_HD argument to the GpgmePassphraseCb type changed its type
2010 from void* to void**.
2012 * New interface gpgme_op_trustlist_end() to match
2013 gpgme_op_keylist_end().
2015 * The CryptPlug modules have been renamed to gpgme-openpgp and
2016 gpgme-smime, and they are installed in pkglibdir by `make install'.
2018 * An idle function can be registered with gpgme_register_idle().
2020 * The GpgSM backend supports key generation with gpgme_op_genkey().
2022 * Interface changes relative to the 0.3.0 release:
2023 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2024 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
2025 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
2026 gpgme_wait CHANGED: New argument STATUS.
2027 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
2028 The function has a new meaning!
2029 gpgme_get_keylist_mode NEW
2030 GPGME_KEYLIST_MODE_LOCAL NEW
2031 GPGME_KEYLIST_MODE_EXTERN NEW
2032 gpgme_op_trustlist_next NEW
2034 gpgme_register_idle NEW
2035 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2037 Noteworthy changes in version 0.3.0 (2001-12-19)
2038 ------------------------------------------------
2040 * New interface gpgme_set_protocol() to set the protocol and thus the
2041 crypto engine to be used by the context. Currently, the OpenPGP
2042 and the CMS protocols are supported. They are specified by the new
2043 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
2044 A new context uses the OpenPGP engine by default.
2046 * gpgme_get_engine_info() returns information for all crypto engines
2047 compiled into the library. The XML format has changed. To
2048 reliably get the version of a crypto engine, the <version> tag
2049 after the appropriate <protocol> tag has to be looked for.
2051 * New interface gpgme_engine_check_version(), obsoleting
2052 gpgme_check_engine(). Check the version of all engines you are
2053 supporting in your software.
2055 * GpgmeKey lists the user ids in the order as they are returned by
2056 GnuPG, first the primary key with index 0, then the sub-user ids.
2058 * New operation gpgme_op_decrypt_verify() to decrypt and verify
2059 signatures simultaneously.
2061 * The new interface gpgme_op_keylist_end() terminates a pending
2062 keylist operation. A keylist operation is also terminated when
2063 gpgme_op_keylist_next() returns GPGME_EOF.
2065 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
2066 cross-compiled, or even compiled without support for GnuPG
2069 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
2070 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
2071 in the path, but it can also be compiled without support for GpgSM
2072 (`--without-gpgsm').
2074 * CryptPlug modules for GPGME are included and can be enabled at
2075 configure time (`--enable-gpgmeplug'). There is one module which
2076 uses the GnuPG engine (`gpgmeplug') and one module which uses the
2077 GpgSM engine (`gpgsmplug').
2079 * Interface changes relative to the latest 0.2.x release:
2080 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2081 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
2082 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
2083 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
2084 gpgme_get_engine_info CHANGED: New format, extended content.
2085 gpgme_engine_check_version NEW
2086 gpgme_decrypt_verify_start NEW
2087 gpgme_decrypt_verify NEW
2088 gpgme_op_keylist_next NEW
2089 gpgme_set_protocol NEW
2090 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2093 Noteworthy changes in version 0.2.3 (2001-09-17)
2094 ------------------------------------------------
2096 * New function gpgme_get_op_info which can be used to get the micalg
2097 parameter needed for MOSS.
2099 * New functions gpgme_get_armor and gpgme_get_textmode.
2101 * The usual bug fixes and some minor functionality improvements.
2103 * Added a simple encryption component for MS-Windows; however the
2104 build procedure might have some problems.
2107 Noteworthy changes in version 0.2.2 (2001-06-12)
2108 ------------------------------------------------
2110 * Implemented a key cache.
2112 * Fixed a race condition under W32 and some other bug fixes.
2115 Noteworthy changes in version 0.2.1 (2001-04-02)
2116 ------------------------------------------------
2118 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
2120 * Handle GnuPG's new key capabilities output and support revocation
2123 * Made the W32 support more robust.
2126 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
2129 This file is free software; as a special exception the author gives
2130 unlimited permission to copy and/or distribute it, with or without
2131 modifications, as long as this notice is preserved.
2133 This file is distributed in the hope that it will be useful, but
2134 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
2135 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
projects / platform / upstream / gpgme.git / blob