1 Noteworthy changes in version 1.15.0 (2020-11-12)
2 -------------------------------------------------
4 * New function gpgme_op_setexpire to make changing the expiration
5 easier (requires GnuPG 2.1.22). [#4999]
7 * New function gpgme_op_revsig to revoke key signatures (requires
10 * Support exporting secret keys. [#5046]
12 * cpp: Support for set expire operations in the C++ bindings. [#5003]
14 * cpp: Support for revoking key signatures in the C++ bindings. [#5094]
16 * qt: Extended ChangeExpiryJob to support changing the expiry of
19 * qt: Extended QuickJob to support revoking of key signatures. [#5094]
21 * qt: Added QDebug stream operator for GpgME::Error.
23 * Require a somewhat newer version of libgpg-error (1.36).
25 * Interface changes relative to the 1.14.0 release:
26 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
27 gpgme_op_setexpire_start NEW.
28 gpgme_op_setexpire NEW.
29 gpgme_op_revsig_start NEW.
31 GPGME_REVSIG_LFSEP NEW.
32 cpp: Context::setExpire NEW.
33 cpp: Context::startSetExpire NEW.
34 cpp: EngineInfo::Version::operator<= NEW.
35 cpp: EngineInfo::Version::operator>= NEW.
36 cpp: EngineInfo::Version::operator!= NEW.
37 cpp: StatusConsumer NEW.
38 cpp: StatusConsumerAssuanTransaction NEW.
39 cpp: Context::cancelPendingOperationImmediately NEW.
40 cpp: Context::revokeSignature NEW.
41 cpp: Context::startRevokeSignature NEW.
42 cpp: UserID::Signature::operator< NEW.
43 qt: operator<<(QDebug debug, const GpgME::Error &err) NEW.
44 qt: QuickJob::startRevokeSignature NEW.
45 qt: QuickJob::result CHANGED: Made params 'auditLogAsHtml'
46 and 'auditLogError' optional.
48 [c=C35/A24/R0 cpp=C18/A12/R0 qt=C12/A5/R0]
50 Release-info: https://dev.gnupg.org/T5131
53 Noteworthy changes in version 1.14.0 (2020-07-16)
54 -------------------------------------------------
56 * New keylist mode to force the engine to return the keygrip. [#4820]
58 * New export mode to export as OpenSSH public key. [#4310]
60 * New context flag "extended-edit" to enable expert key edit. [#4734]
62 * Deprecate the anyway non working trustlist functions. [#4834]
64 * cpp: Add convenience API to obtain remarks. [#4734]
66 * cpp: The sign key edit-interactor now supports multiple signatures
67 from the same key. [#4734]
69 * qt: Extended signkeyjob to handle remarks and multiple signatures.
72 * qt: Added job API for gpg-card.
74 * qt: The logging category has been changed to gpg.qgpgme to be more
75 consistent with other qt logging categories.
77 * Interface changes relative to the 1.13.1 release:
78 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
79 GPGME_KEYLIST_MODE_WITH_KEYGRIP NEW.
80 GPGME_EXPORT_MODE_SSH NEW.
81 gpgme_user_id_t EXTENDED: New field 'uidhash'.
82 cpp: UserID::remark NEW.
83 cpp: UserID::remarks NEW.
84 cpp: GpgSignKeyEditInteractor::setDupeOk NEW.
85 cpp: Context::exportPublicKeys EXTENDED: New param 'flags'.
86 cpp: Context::startPublicKeyExport EXTENDED: New param 'flags'.
87 cpp: Context::ExportMode NEW.
88 qt: SignKeyJob::setDupeOk NEW.
89 qt: SignKeyJob::setRemark NEW.
91 qt: ExportJob::setExportFlags NEW.
93 [c=C34/A23/R0 cpp=C17/A11/R0 qt=C11/A4/R0]
95 Release-info: https://dev.gnupg.org/T4996
98 Noteworthy changes in version 1.13.1 (2019-06-13)
99 -------------------------------------------------
101 * cpp: gpgme_set_global_flag is now wrapped. [#4471]
103 * w32: Improved handling of unicode install paths. [#4453]
105 * w32: The gpgme_io_spawn error message is now only shown once. [#4453]
107 * Fixed a crash introduced in 1.13.0 when working with S/MIME. [#4556]
109 * w32: Fixed format string errors introduced in 1.13.0 that could
110 cause crashes. [#4440]
112 * w32: Fixed an error in the new diagnostic gpgsm support introduced
113 in 1.13.0 that caused crashes in low fd scenarios. [#4439]
115 * python: Fixed a DecryptionError Exception. [#4478]
117 * python: No longer raises BadSignatures from decrypt(verify=True).
120 * Interface changes relative to the 1.13.0 release:
121 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
122 cpp: setGlobalFlag NEW.
124 [c=C33/A22/R1 cpp=C16/A10/R0 qt=C10/A3/R4]
126 Release-info: https://dev.gnupg.org/T4551
129 Noteworthy changes in version 1.13.0 (2019-03-26)
130 -------------------------------------------------
132 * Support GPGME_AUDITLOG_DIAG for gpgsm. [#4426]
134 * New context flag "trust-model".
136 * Removed support for WindowsCE and Windows ME.
138 * Aligned the gpgrt-config code with our other libaries.
140 * Auto-check for all installed Python versions. [#3354]
142 * Fixed generating card key in the C++ bindings. [#4428]
144 * Fixed a segv due to bad parameters in genkey. [#4192]
146 * Fixed crash if the plaintext is ignored in a CMS verify.
148 * Fixed memleak on Windows. [T4238]
150 * Tweaked the Windows I/O code.
152 * Fixed random crashes on Windows due to closing an arbitrary
155 * Fixed a segv on Windows. [#4369]
157 * Fixed test suite problems related to dtags. [#4298]
159 * Fixed bunch of python bugs. [#4242,commit 9de1c96ac3cf]
161 * Several fixes to the Common Lisp bindings.
163 * Fixed minor bugs in gpgme-json. [#4331,#4341,#4342,#4343
165 * Require trace level 8 to dump all I/O data.
167 * The compiler must now support variadic macros.
169 * Interface changes relative to the 1.12.0 release:
170 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
171 gpgme_set_ctx_flag EXTENDED: New flag 'trust-model'.
172 cpp: Context::create NEW.
174 cpp: Subkey::isBad NEW.
175 cpp: UserID::isBad NEW.
176 cpp: UserID::Signature::isBad NEW.
177 cpp: GenCardKeyInteractor::setAlgo NEW.
179 [c=C33/A22/R0 cpp=C15/A9/R0 qt=C10/A3/R3]
181 Release-info: https://dev.gnupg.org/T4376
184 Noteworthy changes in version 1.12.0 (2018-10-08)
185 -------------------------------------------------
187 * Enhanced the JSON based interface tool gpgme-json to support Native
188 Messaging as well as new Javascript code to support the browser
189 site. See lang/js/README for details.
191 * Major overhaul of the Python language bindings documentation.
193 * Even for old versions of gpg a missing MDC will now lead to a
196 * Added context flag "auto-key-locate" to control the
197 behavior of GPGME_KEYLIST_MODE_LOCATE.
199 * New data function to create a data object from an estream.
201 * Add more interfaces to the C++ bindings.
203 * Improved error codes on decryption failure.
205 * Lots of minor fixes.
207 * Interface changes relative to the 1.11.1 release:
208 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
209 gpgme_data_new_from_estream NEW.
210 gpgme_decrypt_result_t EXTENDED: New field legacy_cipher_nomdc.
211 gpgme_set_ctx_flag EXTENDED: New flag 'ignore-mdc-error'.
212 GPGME_AUDITLOG_DEFAULT NEW.
213 GPGME_AUDITLOG_DIAG NEW.
214 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-locate'.
215 cpp: DecryptionResult::sessionKey NEW.
216 cpp: DecryptionResult::symkeyAlgo NEW.
217 cpp: DecryptionResult::isLegacyCipherNoMDC New.
218 cpp: Data::rewind NEW.
219 cpp: Context::setFlag NEW.
220 cpp: Context::getFlag NEW.
221 cpp: Context::createKeyEx NEW.
223 [c=C32/A21/R0 cpp=C14/A8/R0 qt=C10/A3/R2]
225 Release-info: https://dev.gnupg.org/T4109
228 Noteworthy changes in version 1.11.1 (2018-04-20)
229 -------------------------------------------------
231 * Fixed build problems in the 1.11.0 release.
233 * Added C++ interfaces which were planned for 1.11.0.
235 * Interface changes relative to the 1.10.0 release:
236 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
237 cpp: Key::origin NEW.
238 cpp: Key::lastUpdate NEW.
239 cpp: UserID::origin NEW.
240 cpp: UserID::lastUpdate NEW.
242 [c=C31/A20/R1 cpp=C13/A7/R0 qt=C10/A3/R2]
245 Noteworthy changes in version 1.11.0 (2018-04-18)
246 -------------------------------------------------
248 * New encryption API to support direct key specification including
249 hidden recipients option and taking keys from a file. This also
250 allows to enforce the use of a subkey.
252 * New encryption flag for the new API to enforce the use of plain
253 mail addresses (addr-spec).
255 * The import API can now tell whether v3 keys are skipped. These old
256 and basically broken keys are not anymore supported by GnuPG 2.1.
258 * The decrypt and verify API will now return the MIME flag as
259 specified by RFC-4880bis.
261 * The offline mode now has an effect on gpg by disabling all network
264 * A failed OpenPGP verification how returns the fingerprint of the
265 intended key if a recent gpg version was used for signature
268 * New tool gpgme-json as native messaging server for web browsers.
269 As of now public key encryption and decryption is supported.
270 Requires Libgpg-error 1.29.
272 * New context flag "request-origin" which has an effect when used
273 with GnuPG 2.2.6 or later.
275 * New context flag "no-symkey-cache" which has an effect when used
276 with GnuPG 2.2.7 or later.
278 * New convenience constant GPGME_KEYLIST_MODE_LOCATE.
280 * Improved the Python documentation.
282 * Fixed a potential regression with GnuPG 2.2.6 or later.
284 * Fixed a crash in the Python bindings on 32 bit platforms. [#3892]
286 * Various minor fixes.
288 * Interface changes relative to the 1.10.0 release:
289 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
290 gpgme_op_encrypt_ext NEW.
291 gpgme_op_encrypt_ext_start NEW.
292 gpgme_op_encrypt_sign_ext NEW.
293 gpgme_op_encrypt_sign_ext_start NEW.
294 GPGME_ENCRYPT_WANT_ADDRESS NEW.
295 GPGME_KEYLIST_MODE_LOCATE NEW.
296 gpgme_import_result_t EXTENDED: New field 'skipped_v3_keys'.
297 gpgme_decrypt_result_t EXTENDED: New field 'symkey_algo'.
298 gpgme_decrypt_result_t EXTENDED: New field 'is_mime'.
299 gpgme_verify_result_t EXTENDED: New field 'is_mime'.
300 cpp: Key::locate NEW.
301 cpp: Data::toString NEW.
302 cpp: ImportResult::numV3KeysSkipped NEW.
304 [c=C31/A20/R0 cpp=C12/A6/R0 qt=C10/A3/R1]
307 Noteworthy changes in version 1.10.0 (2017-12-12)
308 -------------------------------------------------
310 * Now returns more specific error codes for decryption to distinguish
311 between bad passphrase, user canceled, and no secret key.
313 * Now returns key origin information if available.
315 * Added context flag "auto-key-retrieve" to selectively enable the
316 corresponding gpg option.
318 * Added flag is_de_vs to decryption and verify results.
320 * py: Use SEEK_SET as default for data.seek.
322 * cpp: Various new APIs.
324 * Reduced spawn overhead on Linux again. Added new configure option
325 --disable-linux-getdents to disable this feature for very old
328 * Improved the Python bindings build system.
330 * Made the test suite less fragile.
332 * Interface changes relative to the 1.9.0 release:
333 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
334 gpgme_decrypt_result_t EXTENDED: New field 'is_de_vs'.
335 gpgme_signature_t EXTENDED: New field 'is_de_vs'.
337 gpgme_op_delete_ext NEW.
338 gpgme_op_delete_ext_start NEW.
339 GPGME_DELETE_ALLOW_SECRET NEW.
340 GPGME_DELETE_FORCE NEW.
341 gpgme_op_conf_dir NEW.
342 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-retrieve'.
343 cpp: DecryptionResult::isDeVs NEW.
344 cpp: Signature::isDeVs NEW.
345 cpp: EngineInfo::Version::operator> NEW.
346 cpp: Context::createKey NEW.
347 cpp: Context::startCreateKey NEW.
348 cpp: Context::createSubkey NEW.
349 cpp: Context::startCreateSubkey NEW.
351 py: DecryptResult EXTENDED: New boolean field 'is_de_vs'.
352 py: Signature EXTENDED: New boolean field 'is_de_vs'.
353 py: GpgError EXTENDED: Partial results in 'results'.
355 [c=C30/A19/R0 cpp=C11/A5/R0 qt=C10/A3/R0]
358 Noteworthy changes in version 1.9.0 (2017-03-28)
359 ------------------------------------------------
361 * Clarified meaning of the 'expire' parameter of gpgme_op_createkey
362 and gpgme_op_createsubkey. New flag to force a key without an
365 * New function gpgme_op_keylist_from_data_start to list keys from
366 data objects without importing them.
368 * New function gpgme_op_set_uid_flag to flag a key as primary.
370 * New function gpgme_op_decrypt_ext to run decryption with special
371 flags. This can for example be used to unwrap keys (remove only
372 the encryption layer).
374 * New encryption flags to wrap a key (adding an encryption layer to
375 an OpenPGP message) or to create anonymously encrypted messages.
377 * Support for adduid and revuid operations in the C++ bindings.
379 * Support for smartcard key generation in the C++ bindings.
381 * Several new functions for the Python binding.
383 * Many smaller bug fixes.
385 * Interface changes relative to the 1.8.0 release:
386 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
387 gpgme_op_createkey CHANGED: Meaning of 'expire' parameter.
388 gpgme_op_createsubkey CHANGED: Meaning of 'expire' parameter.
389 GPGME_CREATE_NOEXPIRE NEW.
390 gpgme_key_t EXTENDED: New field 'origin'.
391 gpgme_key_t EXTENDED: New field 'last_update'.
392 gpgme_subkey_t EXTENDED: New field 'is_de_vs'.
393 gpgme_user_id_t EXTENDED: New field 'origin'.
394 gpgme_user_id_t EXTENDED: New field 'last_update'.
395 gpgme_op_keylist_from_data_start NEW.
396 gpgme_op_set_uid_flag_start NEW.
397 gpgme_op_set_uid_flag NEW.
398 gpgme_op_decrypt_ext_start NEW.
399 gpgme_op_decrypt_ext NEW.
400 GPGME_ENCRYPT_THROW_KEYIDS NEW.
401 GPGME_ENCRYPT_WRAP NEW.
402 GPGME_DECRYPT_VERIFY NEW.
403 GPGME_DECRYPT_UNWRAP NEW.
404 gpgme_data_rewind UN-DEPRECATE.
405 cpp: Context::revUid(const Key&, const char*) NEW.
406 cpp: Context::startRevUid(const Key&, const char*) NEW.
407 cpp: Context::addUid(const Key&, const char*) NEW.
408 cpp: Context::startAddUid(const Key&, const char*) NEW.
409 cpp: Key::UserID::revoke() NEW.
410 cpp: Key::addUid() NEW.
411 cpp: Key::isDeVs NEW.
412 cpp: GpgGenCardKeyInteractor NEW.
413 cpp: Subkey::keyGrip NEW.
414 cpp: Subkey::isDeVs NEW.
415 cpp: Data::toKeys NEW.
416 cpp: Context::setDecryptFlags NEW.
417 cpp: Context::decrypt EXTENDED: Flags added.
418 cpp: Context::startDecrypt EXTENDED: Flags added.
419 cpp: Context::decryptAndVerify EXTENDED: Flags added.
420 cpp: Context::startCombinedDecryptionAndVerification EXTENDED: Flags.
421 cpp: Context::encryptFlags EXTENDED: New flags.
422 qt: CryptoConfig::stringValueList() NEW.
423 py: Context.__init__ EXTENDED: New keyword arg home_dir.
424 py: Context.home_dir NEW.
425 py: Context.keylist EXTENDED: New keyword arg mode.
426 py: Context.keylist EXTENDED: New keyword arg source.
427 py: Context.create_key NEW.
428 py: Context.create_subkey NEW.
429 py: Context.key_add_uid NEW.
430 py: Context.key_revoke_uid NEW.
431 py: Context.key_sign NEW.
432 py: Context.key_tofu_policy NEW.
433 py: core.pubkey_algo_string NEW.
434 py: core.addrspec_from_uid NEW.
436 [c=C29/A18/R0 cpp=C10/A4/R0 qt=C9/A2/R0]
439 Noteworthy changes in version 1.8.0 (2016-11-16)
440 ------------------------------------------------
442 * The module of the Python bindings has been renamed to 'gpg'.
444 * New interface to query current software versions.
446 * New feature to use gpg's --{show,override}session-key options.
448 * New interface to set the sender of a mail.
450 * qt: Added Distinguished Name parser from libkleo
452 * The --homedir option is now used with recent gpgconf versions.
454 * On 64 bit Windows systems gpgconf is now properly located.
456 * The internal locking functions have been replaced by libgpg-error
459 * Interface changes relative to the 1.7.1 release:
460 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
461 gpgme_set_sender NEW.
462 gpgme_get_sender NEW.
463 gpgme_op_query_swdb NEW.
464 gpgme_op_query_swdb_result NEW.
465 gpgme_query_swdb_result_t NEW.
466 gpgme_get_ctx_flag NEW.
467 gpgme_decrypt_result_t EXTENDED: New field session_key.
469 qt: DN::Attribute NEW.
470 qt: Job::context(Job*) NEW.
471 cpp: EngineInfo::Version::Version(const char*) NEW.
472 cpp: EngineInfo::Version::Version() NEW.
474 cpp: Context::setSender(const char*) NEW.
475 cpp: Context::getSender() NEW.
477 [c=C28/A17/R0 cpp=C9/A3/R0 qt=C8/A1/R0]
480 Noteworthy changes in version 1.7.1 (2016-10-18)
481 ------------------------------------------------
483 * Fixed problems with the new language bindings.
485 * New helper function gpgme_addrspec_from_uid.
487 * Use option --exit-on-status-write-error with newer gpg versions.
489 * qt: Missed API from the Qt Binding inclusion has
492 * qt: abstractimportjob.h is now installed to that
493 ImportJobs can be used again.
495 * qt: Fixed spelling error in API (startReceive).
497 * Interface changes relative to the 1.7.0 release:
498 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
499 gpgme_addrspec_from_uid NEW.
500 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
501 qt: MultiDeleteJob NEW.
502 qt: AbstractImportJob NEW.
504 cpp: Signature::key(bool, bool) NEW.
505 cpp: UserID::addrSpecFromString(const char*) NEW.
506 cpp: UserID::addrSpec() NEW.
508 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
511 Noteworthy changes in version 1.7.0 (2016-09-21)
512 ------------------------------------------------
514 * New language bindings for Python 2 and 3.
516 * New language Bindings for C++ and the Qt-Framework API.
518 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
519 key creation easier (requires GnuPG 2.1).
521 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
522 management easier (requires GnuPG 2.1).
524 * New function gpgme_op_keysign to make key signing easier (requires
527 * New function gpgme_op_interact to replace the now deprecated
528 functions gpgme_op_edit and gpgme_op_card_edit.
530 * New function gpgme_pubkey_algo_string to convert a public key
531 algorithm into a GnuPG 2.1 style string.
533 * Support for GnuPG 2.1's TOFU trust model.
535 * Notation flags are now correctly set on verify.
537 * New global flag "require-gnupg" to set a minimal gnupg version.
539 * More supported items in gpgme_get_dirinfo.
541 * New function gpgme_data_set_flag and flag "size-hint".
543 * New function gpgme_set_ctx_flag and flags "full-status" and
546 * Improved gpgme_data_identify to distinguish more file types.
548 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
549 mixed public key and symmetric encryption.
551 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
553 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
554 signed data is a valid MIME part. This is to support future GnuPG
557 * Interface changes relative to the 1.6.0 release:
558 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
559 gpgme_pubkey_algo_string NEW.
561 gpgme_set_ctx_flag NEW.
562 gpgme_data_set_flag NEW.
563 gpgme_op_createkey NEW.
564 gpgme_op_createkey_start NEW.
565 gpgme_op_createsubkey NEW.
566 gpgme_op_createsubkey_start NEW.
567 gpgme_op_adduid_start NEW.
569 gpgme_op_revuid_start NEW.
571 gpgme_op_keysign_start NEW.
572 gpgme_op_keysign NEW.
573 gpgme_op_tofu_policy_start NEW.
574 gpgme_op_tofu_policy NEW.
575 gpgme_op_interact_start NEW.
576 gpgme_op_interact NEW.
577 gpgme_interact_cb_t NEW.
578 gpgme_op_edit_start DEPRECATED.
579 gpgme_op_edit DEPRECATED.
580 gpgme_op_card_edit_start DEPRECATED.
581 gpgme_op_card_edit DEPRECATED.
582 gpgme_edit_cb_t DEPRECATED.
583 gpgme_status_code_t DEPRECATED.
584 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
585 gpgme_signature_t EXTENDED: New field key.
586 gpgme_key_t EXTENDED: New field fpr.
587 gpgme_subkey_t EXTENDED: New field keygrip.
588 gpgme_user_id_t EXTENDED: New field tofu.
589 gpgme_tofu_policy_t NEW.
590 gpgme_tofu_info_t NEW.
591 GPGME_STATUS_KEY_CONSIDERED NEW.
592 GPGME_STATUS_TOFU_USER NEW.
593 GPGME_STATUS_TOFU_STATS NEW.
594 GPGME_STATUS_TOFU_STATS_LONG NEW.
595 GPGME_STATUS_NOTATION_FLAGS NEW.
596 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
597 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
598 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
599 GPGME_DATA_ENCODING_MIME NEW.
600 GPGME_ENCRYPT_SYMMETRIC NEW.
601 GPGME_CREATE_SIGN NEW.
602 GPGME_CREATE_ENCR NEW.
603 GPGME_CREATE_CERT NEW.
604 GPGME_CREATE_AUTH NEW.
605 GPGME_CREATE_NOPASSWD NEW.
606 GPGME_CREATE_SELFSIGNED NEW.
607 GPGME_CREATE_NOSTORE NEW.
608 GPGME_CREATE_WANTPUB NEW.
609 GPGME_CREATE_WANTSEC NEW.
610 GPGME_CREATE_FORCE NEW.
611 GPGME_KEYSIGN_LOCAL NEW.
612 GPGME_KEYSIGN_LFSEP NEW.
613 GPGME_INTERACT_CARD NEW.
615 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
618 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
619 ------------------------------------------------
621 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
623 * Added gpgme_set_status_cb to allow a user to see some status
626 * Added an export mode for secret keys.
628 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
630 * The passphrase handler for the loopback mode has been improved and may
631 also be used with genkey.
633 * [w32] The standard GnuPG 2.1 install directory is now searched for
634 gpgconf.exe before a registry specified directory and the Gpg4win
637 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
640 * Interface changes relative to the 1.5.1 release:
641 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
642 gpgme_set_offline NEW.
643 gpgme_get_offline NEW.
644 gpgme_set_status_cb NEW.
645 gpgme_get_status_cb NEW.
646 GPGME_EXPORT_MODE_SECRET NEW
647 GPGME_EXPORT_MODE_RAW NEW.
648 GPGME_EXPORT_MODE_PKCS12 NEW.
651 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
652 ------------------------------------------------
654 * Fixed crash in key listings for user ids with a backslash.
656 * Fixed regression for GPGSM use with GnuPG < 2.1.
658 * Properly set signature summary for revoked OpenPGP keys.
661 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
662 ------------------------------------------------
664 * Fixed a possible crash in the debug code.
666 * Fixed building for Windows with newer versions of Mingw.
669 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
670 -------------------------------------------------------------
672 * The export key functions do now return an error if used with the
673 latest GnuPG version.
676 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
677 -------------------------------------------------------------
679 * gpgme-tool is now installed.
681 * Fix external listing for modern keyservers.
686 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
687 -------------------------------------------------------------
689 * Fixed possible overflow in gpgsm and uiserver engines.
692 * Added support for GnuPG 2.1's --with-secret option.
694 * Interface changes relative to the 1.5.0 release:
695 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
696 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
699 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
700 -------------------------------------------------------------
702 * On Unices the engine file names are not not anymore hardwired but
703 located via the envvar PATH. All options to set the name of the
704 engines for the configure run are removed.
706 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
707 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
708 is not found, GPGME looks for an engine named "gpg".
710 * New feature to use the gpgme I/O subsystem to run arbitrary
713 * New flag to use encryption without the default compression step.
715 * New function to access "gpg-conf --list-dirs"
717 * New configure option --enable-fixed-path for use by Android.
719 * Support ECC algorithms.
721 * Interface changes relative to the 1.4.3 release:
722 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
723 gpgme_get_dirinfo NEW.
724 gpgme_op_spawn_start NEW.
726 GPGME_PROTOCOL_SPAWN NEW.
727 GPGME_SPAWN_DETACHED NEW.
728 GPGME_SPAWN_ALLOW_SET_FG NEW.
729 GPGME_ENCRYPT_NO_COMPRESS NEW.
732 gpgme_subkey_t EXTENDED: New field curve.
733 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
734 GPGME_STATUS_MOUNTPOINT NEW.
735 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
736 GPGME_STATUS_ATTRIBUTE NEW.
737 GPGME_STATUS_BEGIN_SIGNING NEW.
738 GPGME_STATUS_KEY_NOT_CREATED NEW.
741 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
742 -------------------------------------------------------------
744 * The default engine names are now taken from the output of gpgconf.
745 If gpgconf is not found the use of gpg 1 is assumed.
747 * Under Windows the default engines names are first searched in the
748 installation directory of the gpgme DLL.
750 * New function gpgme_data_identify to detect the type of a message.
752 * Interface changes relative to the 1.4.2 release:
753 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
754 gpgme_signers_count NEW.
755 gpgme_data_type_t NEW.
756 gpgme_data_identify NEW.
759 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
760 -------------------------------------------------------------
762 * Allow symmetric encryption with gpgme_op_encrypt_sign.
764 * Fixed mismatching off_t definitions on Windows.
766 * Interface changes relative to the 1.4.1 release:
767 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
770 GPGME_PROTOCOL_OPENPGP NEW alias.
773 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
774 ------------------------------------------------------------
776 * Fixed reading of gpg.conf files with excessive use of the group
779 * Fixed building with the i686-w64-mingw32 toolchain.
781 * Disabled FD passing by default for Apple.
784 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
785 ------------------------------------------------------------
787 * New function gpgme_set_global_flag to help debugging on Android.
789 * New function gpgme_io_writen as a convenience wrapper around
792 * New functions to support the pinentry mode feature of GnuPG 2.1.
794 * New macro GPGME_VERSION_NUMBER to allow supporting different API
795 versions without the need for a configure test.
797 * Several improvements for gpgme-tool.
799 * Better logging of the common "invalid engine" error code.
801 * Support for FD passing is now enabled by default. The configure
802 option --disable-fd-passing may be used to disable this.
804 * Interface changes relative to the 1.3.1 release:
805 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
806 GPGME_VERSION_NUMBER NEW.
808 gpgme_set_global_flag NEW.
809 gpgme_set_pinentry_mode NEW.
810 gpgme_get_pinentry_mode NEW.
811 gpgme_pinentry_mode_t NEW.
812 GPGME_PINENTRY_MODE_DEFAULT NEW.
813 GPGME_PINENTRY_MODE_ASK NEW.
814 GPGME_PINENTRY_MODE_CANCEL NEW.
815 GPGME_PINENTRY_MODE_ERROR NEW.
816 GPGME_PINENTRY_MODE_LOOPBACK NEW.
819 Noteworthy changes in version 1.3.2 (2012-05-02)
820 ------------------------------------------------
822 * Remove support for libgpgme-pth. As far as we know, this was never used,
823 and GnuPG is going to use our own npth in the future.
825 * Fix signature summary information for a missing X.509 key.
827 * Fix parsing of dates >= year 2038.
830 Noteworthy changes in version 1.3.1 (2011-06-16)
831 ------------------------------------------------
833 * Ported to Windows CE.
835 * Detect GPG versions not supporting ---passwd.
837 * Interface changes relative to the 1.3.0 release:
838 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
839 GPGME_EXPORT_MODE_MINIMAL NEW
840 GPGME_STATUS_SUCCESS NEW
841 gpgme_err_code_from_syserror NEW
842 gpgme_err_set_errno NEW
843 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
844 gpgme_error_from_syserror NEW
845 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
848 Noteworthy changes in version 1.3.0 (2010-01-11)
849 ------------------------------------------------
851 * GPGME does not come with an internal libassuan version anymore.
852 The external libassuan 1.1.0 release or later is required. For
853 application programmers on systems that can resolve inter-library
854 dependencies at runtime, this is a transparent change.
856 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
858 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
860 * New API to change the passphrase of a key.
862 * Interface changes relative to the 1.2.0 release:
863 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
864 GPGME_STATUS_INV_SGNR NEW.
865 GPGME_STATUS_NO_SGNR NEW.
866 GPGME_PROTOCOL_G13 NEW.
867 gpgme_op_g13_mount NEW.
868 gpgme_g13_result_t NEW.
871 gpgme_op_passwd_start NEW.
873 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
876 Noteworthy changes in version 1.2.0 (2009-06-18)
877 ------------------------------------------------
879 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
882 * gpgme_new will fail if gpgme_check_version was not called, or a
883 selftest failed (for example, if -mms-bitfields was not used on
886 * New functions gpgme_io_read and gpgme_io_write for use with
887 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
889 * New functions gpgme_result_ref and gpgme_result_unref to detach
890 result structures from a context.
892 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
893 that allow to specify exported keys through gpgme_key_t objects
896 * New mode of operation gpgme_export_mode_t that allows exporting
899 * Interface changes relative to the 1.1.7 release:
900 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
901 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
902 GPGME_PROTOCOL_ASSUAN NEW.
903 gpgme_assuan_data_cb_t NEW.
904 gpgme_assuan_inquire_cb_t NEW.
905 gpgme_assuan_status_cb_t NEW.
906 gpgme_op_assuan_transact_start NEW.
907 gpgme_op_assuan_transact NEW.
908 gpgme_op_assuan_result NEW.
909 gpgme_op_import_keys NEW.
910 gpgme_op_import_keys_start NEW.
911 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
912 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
913 gpgme_check_version CHANGED: Is now a macro.
914 gpgme_new EXTENDED: More failure codes.
917 gpgme_result_ref NEW.
918 gpgme_result_unref NEW.
919 gpgme_export_mode_t NEW.
920 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
921 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
922 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
923 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
924 gpgme_op_export_keys_start NEW.
925 gpgme_op_export_keys NEW.
926 GPGME_DATA_ENCODING_URL NEW.
927 GPGME_DATA_ENCODING_URL0 NEW.
928 GPGME_DATA_ENCODING_URLESC NEW.
929 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
932 Noteworthy changes in version 1.1.8 (2008-12-08)
933 ------------------------------------------------
935 * SIGPIPE is now again ignored as described in the manual. Fixes
936 regression introduced with 1.1.6.
939 Noteworthy changes in version 1.1.7 (2008-10-17)
940 ------------------------------------------------
942 * Using GPGME_KEYLIST_MODE_LOCAL combined with
943 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
944 --locate-keys feature of gpg (>= 2.0.10).
946 * The encoding of gpgme_data_t objects can affect the output encoding
947 of export, sign and encrypt operations now (the same operations
948 that are also affected by the ASCII mode switch). We believe this
949 change in the ABI is innocent enough not to break existing
950 applications (it only affects the S/MIME backend on certain
953 * The reference manual now includes the specification of "The GnuPG
956 * A new function gpgme_cancel_async can be used to asynchronously
957 cancel any pending operation at any time, from any thread.
959 * Interface changes relative to the 1.1.6 release:
960 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
961 gpgme_op_encrypt CHANGED: Output encoding can affect result.
962 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
963 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
964 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
965 gpgme_op_sign CHANGED: Output encoding can affect result.
966 gpgme_op_sign_start CHANGED: Output encoding can affect result.
967 gpgme_op_export CHANGED: Output encoding can affect result.
968 gpgme_op_export_start CHANGED: Output encoding can affect result.
969 gpgme_op_export_ext CHANGED: Output encoding can affect result.
970 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
971 gpgme_cancel_async NEW
972 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
975 Noteworthy changes in version 1.1.6 (2008-01-04)
976 ------------------------------------------------
978 * Bug fixes for for W32.
980 * A new, experimental (and thus undocumented and potentially
981 unstable) interface for accessing gpg-conf through GPGME has been
984 * Interface changes relative to the 1.1.1 release:
985 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
986 gpgme_signature_t EXTENDED: New field chain_model.
987 gpgme_op_getauditlog_start NEW.
988 gpgme_op_getauditlog NEW.
989 GPGME_AUDITLOG_HTML NEW.
990 GPGME_AUDITLOG_WITH_HELP NEW.
991 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
994 Noteworthy changes in version 1.1.5 (2007-07-09)
995 ------------------------------------------------
997 * Bug and portability fixes (mainly for W32).
1000 Noteworthy changes in version 1.1.4 (2007-03-05)
1001 ------------------------------------------------
1003 * Detect and bail out on double plaintext messages. This is required
1004 so that applications can properly detect the signed parts of a
1005 message. Actual there is now a double protection as GnuPG 1.4.7
1006 will detect this case too.
1009 Noteworthy changes in version 1.1.3 (2007-01-29)
1010 ------------------------------------------------
1012 * Fixed a memory leak in gpgme_data_release_and_get_mem.
1014 * Fixed a bug in Windows command line quoting.
1017 Noteworthy changes in version 1.1.2 (2006-03-02)
1018 ------------------------------------------------
1020 * Fixed a bug in the W32 glib backend.
1023 Noteworthy changes in version 1.1.1 (2006-02-23)
1024 ------------------------------------------------
1026 * Fixed a bug in that the fingerprints of subkeys are not available.
1028 * Clarified usage of the SECRET flag in key listings. It is now
1029 reset for stub keys.
1031 * Reading signature notations and policy URLs on key signatures is
1032 supported. They can be found in the new field notations of the
1033 gpgme_key_sig_t structure. This has to be enabled with the keylist
1034 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
1036 * A new gpgme_free() function solves the problem of using different
1037 allocators in a single program. This function should now be used
1038 instead calling free() to release the buffer returned by
1039 gpgme_data_release_and_get_mem. It is recommended that you always
1040 do this, but it is only necessary on certain platforms, so backwards
1041 compatibility is provided. In other words: If free() worked for
1042 you before, it will keep working.
1044 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
1045 They are analyzed by the verify handlers and made available in the
1046 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
1048 * Interface changes relative to the 1.1.0 release:
1049 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1050 gpgme_key_sig_t EXTENDED: New field notations.
1051 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
1053 GPGME_STATUS_PKA_TRUST_BAD NEW
1054 GPGME_STATUS_PKA_TRUST_GOOD NEW
1055 gpgme_signature_t EXTENDED: New field pka_trust.
1056 gpgme_signature_t EXTENDED: New field pka_address.
1057 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1060 Noteworthy changes in version 1.1.0 (2005-10-01)
1061 ------------------------------------------------
1063 * You can now configure the backend engine file name and home
1064 directory to be used, as default and per context.
1066 * Information about the recipients of an encrypted text is now
1067 available at decryption time.
1069 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
1070 and verify handlers, the information about the plaintext filename,
1071 if available is made available in the new field file_name of the
1072 respective result structure.
1074 * The code for "automagically detecting the thread library" has been
1075 removed from libgpgme. It is deprecated since version 0.4.3.
1076 Since then, you had to link against libgpgme-pthread for
1077 applications using pthread and libgpgme-pth for applications using
1080 The code was removed because it caused compilation problems on
1081 systems where the pthread.h header from GNU Pth is available in
1082 addition to the system header (FreeBSD 6 and later for example).
1084 * "./autogen.sh --build-w32" does now build gpgme.dll.
1086 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
1087 delimiter. The standard install directory is used when locating
1088 gpg or gpgsm before finally falling back to the hardwired name.
1090 * There is a new flag for keys and subkeys, is_qualified, which
1091 indicates if a key can be used for qualified signatures according
1092 to local government regulations.
1094 * You can associate a filename with a data object using the new
1095 function gpgme_data_set_file_name(). This filename will be stored
1096 in the output when encrypting or signing the data and will be
1097 returned when decrypting or verifying the output data.
1099 * You can now set notation data at signature creation with the new
1100 function gpgme_sig_notation_add().
1102 * Interface changes relative to the 1.0.3 release:
1103 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1104 gpgme_set_engine_info NEW
1105 gpgme_ctx_get_engine_info NEW
1106 gpgme_ctx_set_engine_info NEW
1107 gpgme_recipient_t NEW
1108 gpgme_decrypt_result_t EXTENDED: New field recipients.
1109 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
1110 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
1111 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
1112 GPGME_STATUS_PLAINTEXT NEW
1113 gpgme_key_t EXTENDED: New field is_qualified.
1114 gpgme_subkey_t EXTENDED: New field is_qualified.
1115 gpgme_data_get_file_name NEW
1116 gpgme_data_set_file_name NEW
1117 gpgme_sig_notation_flags_t NEW
1118 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
1119 GPGME_SIG_NOTATAION_CRITICAL NEW
1120 gpgme_sig_notation_clear NEW
1121 gpgme_sig_notation_add NEW
1122 gpgme_sig_notation_get NEW
1123 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1126 Noteworthy changes in version 1.0.3 (2005-06-20)
1127 ------------------------------------------------
1129 * Previousy, GPGME would use a default "include certs" of 1. This
1130 has been changed. Now GPGME will use the crypto backend engines
1131 default unless you set the value with gpgme_set_include_certs()
1132 explicitly. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
1133 as a value to explicitly request the new default behaviour.
1135 Because the default changes, this is a slight change of the API
1136 semantics. We consider it to be a bug fix.
1138 * A bug which made GPGME hang has been fixed. If you have
1139 experienced hanging before, please try out this version and let me
1140 know if you still experience hanging problems.
1142 * Interface changes relative to the 0.9.0 release:
1143 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1144 gpgme_set_include_certs CHANGED DEFAULT
1145 GPGME_INCLUDE_CERTS_DEFAULT NEW
1146 GPGME_STATUS_SIG_SUBPACKET NEW
1147 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
1148 GPGME_STATUS_SC_OP_FAILURE NEW
1149 GPGME_STATUS_SC_OP_SUCCESS NEW
1150 GPGME_STATUS_CARDCTRL NEW
1151 GPGME_STATUS_BACKUP_KEY_CREATED NEW
1152 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1155 Noteworthy changes in version 1.0.2 (2004-12-28)
1156 ------------------------------------------------
1158 * Changed the license of the library to the GNU Lesser General Public
1159 License (LGPL), version 2.1 or later.
1162 Noteworthy changes in version 1.0.1 (2004-10-22)
1163 ------------------------------------------------
1168 Noteworthy changes in version 1.0.0 (2004-09-30)
1169 ------------------------------------------------
1171 * Version 1.0.0! We are proud to present you with a thoroughly
1172 tested and stable version of the GPGME library. A big Thank You!
1173 to all the people who made this possible.
1175 The development will be branched into a stable 1.x.y series and the
1178 * The gpgme.m4 macro supports checking the API version. Just prepend
1179 it to the required version string, separated by a colon. For
1180 example, this release has the version "1:1.0.0". The last release
1181 to which this version is (mostly) ABI compatible is "1:0.4.2",
1182 which is the default required version.
1185 Noteworthy changes in version 0.9.0 (2004-06-08)
1186 ------------------------------------------------
1188 * The type gpgme_key_t has now a new field keylist_mode that contains
1189 the keylist mode that was active at the time the key was retrieved.
1191 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
1192 that contains a flag indicating that the key should not have been
1193 used for encryption.
1195 * Verifying a signature of a revoked key gives the correct result now
1196 (GPG_ERR_CERT_REVOKED error code).
1198 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
1199 verify operations still allows you to look at the signature
1200 verification result.
1202 * Clarified that patterns in keylisting operations have an upper
1203 limit, and thus are not suited to list many keys at once by their
1204 fingerprint. Also improve the error message if the pattern is too
1205 long for the CMS protocol to handle.
1207 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1208 gpgme_key_t EXTENDED: New field keylist_mode.
1209 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
1210 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1213 Noteworthy changes in version 0.4.7 (2004-04-29)
1214 ------------------------------------------------
1216 * Correctly initialize the fields expired, revoked, invalid, and
1217 disabled in the gpgme_key_t structures.
1219 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
1220 accidentally of type int instead unsigned int.
1222 * Interface changes relative to the 0.4.5 release:
1223 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1224 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
1225 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1227 Noteworthy changes in version 0.4.6 (2004-04-06)
1228 ------------------------------------------------
1233 Noteworthy changes in version 0.4.5 (2004-03-07)
1234 ------------------------------------------------
1236 * GPGME is now compiled with LFS (large file support) by default.
1237 This means that _all_ programs using GPGME must be compiled with
1238 LFS support enabled by default. You can do this easily with
1239 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
1240 without autoconf by defining the preprocessor symbol
1241 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
1242 the C compiler command line, or by defining this preprocessor
1243 symbol before including any system header files). For more
1244 details, read the section on LFS in the manual.
1246 Up to now, it was undocumented that GPGME was not using LFS.
1247 But the public interfaces use off_t, and file descriptors are
1248 exchanged between the application and GPGME. This was an oversight,
1249 and bound to cause troubles in the future.
1251 Writing GPGME as a dual mode library that seamlessly supports LFS
1252 while keeping backwards compatibility is possible, but does not
1253 solve the problem: Many applications already expect GPGME to have
1254 LFS (they are compiled with off_t being a 64bit value). This is true
1255 in particular for the popular Gtk+ and Qt programs.
1257 So, although this is an ABI (but not an API) break, we will not
1258 change the library version to reflect that. Because the interfaces
1259 affected are probably not used yet in any GPGME 0.4 based
1260 application, we don't expect any real failures from this change.
1261 In fact, applications already using LFS will have some subtle bugs
1264 However, if you encounter an application using GPGME 0.4.x that
1265 does _not_ use LFS by default (off_t is a 32bit value), _and_
1266 uses at least one of the functions gpgme_data_seek,
1267 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
1268 gpgme_data_new_from_cbs, then indeed this library will be ABI
1269 incompatible with the program. As said above, we don't believe
1270 such a program exists. If we are in error, then you have two
1271 options: As a quick hack, you can configure GPGME with the
1272 --disable-largefile option. This will revert the change, and GPGME
1273 will not use LFS. However, GPGME will be incompatible with
1274 programs that expect GPGME to use LFS. All applications are
1275 required to use LFS when using GPGME, so this is only good as a
1276 temporary local work-around.
1278 The other option is to change the versioning of the library and
1279 recompile all applications. We have reserved a special version of
1280 the library for that, so you can do that without expecting a
1281 version clash in the future. Furthermore, everyone who does this
1282 will agree on the version to use (this is important for
1283 distribution makers). Read the comment in configure.ac (before
1284 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
1285 blindly: As stated above, we think it is unlikely this measure is
1286 needed. Still, it is there if necessary. If in doubt, contact us
1287 and we will give our advise for your specific situation.
1289 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
1292 * New interface gpgme_cancel() that can be used to cancel
1293 asynchronous operations.
1295 * Interface changes relative to the 0.4.4 release:
1296 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1297 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
1298 gpgme_data_seek CHANGED: off_t is now a largefile type.
1299 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
1300 GPGME_KEYLIST_MODE_VALIDATE NEW
1302 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1304 Noteworthy changes in version 0.4.4 (2004-01-12)
1305 ------------------------------------------------
1307 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
1308 been renamed to "sig_class", to avoid clash with C++ compilers. In
1309 the C API, the old name "class" has been preserved for backwards
1310 compatibility, but is deprecated.
1312 * Interface changes relative to the 0.4.3 release:
1313 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1314 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
1315 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
1316 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1318 Noteworthy changes in version 0.4.3 (2003-10-06)
1319 ------------------------------------------------
1321 * libgpgme should not be used for threaded programs anymore. This
1322 never worked reliably in all cases, because you had to
1323 be careful about the linking order and libtool wouldn't do that for
1324 you automatically. Instead, now you have to link against
1325 libgpgme-pthread for applications using pthread and libgpgme-pth for
1326 applications using GNU Pth.
1328 The old code for automagically detecting the thread library is
1329 still part of libgpgme, but it is DEPRECATED.
1331 * There are new automake macros AM_PATH_GPGME_PTH and
1332 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
1333 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
1334 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
1335 variables of course also include the configuration for the thread
1336 package itself. Alternatively, use libtool.
1338 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
1341 * gpgme-config doesn't support setting the prefix or exec prefix
1342 anymore. I don't think it ever worked correctly, and it seems to
1345 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
1346 provided was not unique, instead returning the first matching key.
1348 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
1349 that indicates if the key can be used for authentication.
1351 * gpgme_signature_t's status field is now correctly set to an error
1352 with error code GPG_ERR_NO_PUBKEY if public key is not found.
1354 * gpgme_new_signature_t's class field is now an unsigned int, rather
1355 than an unsigned long (the old class field is preserved for
1356 backwards compatibility).
1358 * A new function gpgme_set_locale() is provided to allow configuring
1359 the locale for the crypto backend. This is necessary for text
1360 terminals so that programs like the pinentry can be started with
1361 the right locale settings for the terminal the application is running
1362 on, in case the terminal has different settings than the system
1363 default (for example, if it is a remote terminal). You are highly
1364 recommended to call the following functions directly after
1365 gpgme_check_version:
1369 setlocale (LC_ALL, "");
1370 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
1371 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
1373 GPGME can not do this for you, as setlocale is not thread safe, and
1374 there is no alternative.
1376 * The signal action for SIGPIPE is now set to SIG_IGN by
1377 gpgme_check_version, instead the first time a crypto engine is
1378 started (which is not well defined).
1380 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
1381 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
1382 to CRC24RFC2440. For now, these strings can be used as the MIC
1383 parameter for PGP/MIME (if appropriately modified).
1385 * Interface changes relative to the 0.4.2 release:
1386 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1387 gpgme_strerror_t NEW
1388 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
1389 gpgme_key_t EXTENDED: New field can_authenticate.
1390 gpgme_subkey_t EXTENDED: New field can_authenticate.
1391 gpgme_new_signature_t CHANGED: New type for class field.
1392 gpgme_set_locale NEW
1393 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
1394 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1396 Noteworthy changes in version 0.4.2 (2003-07-30)
1397 ------------------------------------------------
1399 * Allow gpg-error to be in non-standard place when linking the test suite.
1401 * Configure will fail now if gpg-error can not be found.
1403 * Fixed initialized memory backed data objects for writing, which
1404 caused the test program to crash (but only on Mac OS, surprisingly).
1406 * Eliminate use of C99 constructs.
1408 * Small improvements to the manual.
1411 Noteworthy changes in version 0.4.1 (2003-06-06)
1412 ------------------------------------------------
1414 This is the release that 0.4.0 should have been. There are many
1415 interface changes, please see below for the details. The changes are
1416 sometimes the result of new functionality, but more often express a
1417 paradigm shift. Others are an overdue cleanup to get GPGME in line
1418 with the GNU coding standards and to make the interface more
1419 self-consistent. Here is an overview on the changes:
1421 All types have been renamed to conform to the GNU coding standards,
1422 most of the time by keeping the whole name in lowercase and inserting
1423 underscores between words.
1425 All operations consistently only accept input parameters in their
1426 invocation function, and return only an error code directly. Further
1427 information about the result of the operation has to be retrieved
1428 afterwards by calling one of the result functions. This unifies the
1429 synchronous and the asynchronous interface.
1431 The error values have been completely replaced by a more
1432 sophisticated model that allows GPGME to transparently and accurately
1433 report all errors from the other GnuPG components, regardless of
1434 process boundaries. This is achieved by using the library
1435 libgpg-errors, which is shared by all GnuPG components. This library
1436 is now required for GPGME.
1438 The results of all operations are now provided by pointers to C
1439 structs rather than by XML structs or in other ways.
1441 Objects which used to be opaque (for example a key) are now pointers
1442 to accessible structs, so no accessor functions are necessary.
1444 Backward compatibility is provided where it was possible without too
1445 much effort and did not collide with the overall sanitization effort.
1446 However, this is only for ease of transition. NO DEPRECATED FUNCTION
1447 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
1448 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
1449 Recommendations how to replace deprecated or removed functionality
1450 can be found within the description of each change.
1452 What follows are all changes to the interface and behaviour of GPGME
1455 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
1456 deprecated attributes will warn about use of obsolete functions and
1457 type definitions. You can suppress these warnings by passing
1458 -Wno-deprecated-declarations to the gcc command.
1460 * The following types have been renamed. The old types are still
1461 available as aliases, but they are deprecated now:
1463 GpgmeCtx gpgme_ctx_t
1464 GpgmeData gpgme_data_t
1465 GpgmeError gpgme_error_t
1466 GpgmeDataEncoding gpgme_data_encoding_t
1467 GpgmeSigStat gpgme_sig_stat_t
1468 GpgmeSigMode gpgme_sig_mode_t
1469 GpgmeAttr gpgme_attr_t
1470 GpgmeValidity gpgme_validity_t
1471 GpgmeProtocol gpgme_protocol_t
1472 GpgmeKey gpgme_key_t
1473 GpgmePassphraseCb gpgme_passphrase_cb_t
1474 GpgmeProgressCb gpgme_progress_cb_t
1475 GpgmeIOCb gpgme_io_cb_t
1476 GpgmeRegisterIOCb gpgme_register_io_cb_t
1477 GpgmeRemoveIOCb gpgme_remove_io_cb_t
1478 GpgmeEventIO gpgme_event_io_t
1479 GpgmeEventIOCb gpgme_event_io_cb_t
1480 GpgmeIOCbs gpgme_io_cbs
1481 GpgmeDataReadCb gpgme_data_read_cb_t
1482 GpgmeDataWriteCb gpgme_data_write_cb_t
1483 GpgmeDataSeekCb gpgme_data_seek_cb_t
1484 GpgmeDataReleaseCb gpgme_data_release_cb_t
1485 GpgmeDataCbs gpgme_data_cbs_t
1486 GpgmeTrustItem gpgme_trust_item_t
1487 GpgmeStatusCode gpgme_status_code_t
1489 * gpgme_error_t is now identical to gpg_error_t, the error type
1490 provided by libgpg-error. More about using libgpg-error with GPGME
1491 can be found in the manual. All error symbols have been removed!
1493 * All functions and types in libgpg-error have been wrapped in GPGME.
1494 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1495 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1496 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1497 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1500 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1502 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1503 for encrypt, sign, encrypt-sign, decrypt, verify, and
1504 decrypt-verify operations. For verify operations on detached
1505 signatures, the progress callback is invoked for both the detached
1506 signature and the plaintext message, though.
1508 * gpgme_passphrase_cb_t has been changed to not provide a complete
1509 description, but the UID hint, passphrase info and a flag
1510 indicating if this is a repeated attempt individually, so the user
1511 can compose his own description from this information.
1513 The passphrase is not returned as a C string, but must be written
1514 to a file descriptor directly. This allows for secure passphrase
1517 The return type has been changed to gpgme_error_t value. This
1518 allowed to remove the gpgme_cancel function; just return
1519 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1521 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1522 The user is expected to write the response to the file descriptor,
1523 followed by a newline.
1525 * The recipients interface has been removed. Instead, you use
1526 NULL-terminated lists of keys for specifying the recipients of an
1527 encryption operation. Use the new encryption flag
1528 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1529 the keys (but note that in general this is not a good idea).
1531 This change has been made to the prototypes of gpgme_op_encrypt,
1532 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1533 gpgme_op_encrypt_sign_start.
1535 The export interface has been changed to use pattern strings like
1536 the keylist interface. Thus, new functions gpgme_op_export_ext and
1537 gpgme_op_export_ext_start have been added as well. Now the
1538 prototypes of gpgme_op_export_start and gpgme_op_export finally
1541 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1542 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1545 * gpgme_io_cb_t changed from a void function to a function returning
1546 a gpgme_error_t value. However, it will always return 0, so you
1547 can safely ignore the return value.
1549 * A new I/O callback event GPGME_EVENT_START has been added. The new
1550 requirement is that you must wait until this event until you are
1551 allowed to call the I/O callback handlers previously registered for
1552 this context operation. Calling I/O callback functions for this
1553 context operation before the start event happened is unsafe because
1554 it can lead to race conditions in a multi-threaded environment.
1556 * The idle function feature has been removed. It was not precisely
1557 defined in a multi-threaded environment and is obsoleted by the
1558 user I/O callback functions. If you still need a simple way to
1559 call something while waiting on one or multiple asynchronous
1560 operations to complete, don't set the HANG flag in gpgme_wait (note
1561 that this will return to your program more often than the idle
1564 * gpgme_wait can return NULL even if hang is true, if an error
1565 occurs. In that case *status contains the error code.
1567 * gpgme_get_engine_info was radically changed. Instead an XML
1568 string, an info structure of the new type gpgme_engine_info_t is
1569 returned. This makes it easier and more robust to evaluate the
1570 information in an application.
1572 * The new function gpgme_get_protocol_name can be used to convert a
1573 gpgme_protocol_t value into a string.
1575 * The status of a context operation is not checked anymore. Starting
1576 a new operation will silently cancel the previous one. Calling a
1577 function that requires you to have started an operation before without
1578 doing so is undefined.
1580 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1581 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1582 pointer to a structure which contains the fingerprint. This also
1583 works with gpgme_op_genkey_start. The structure also provides
1584 other information about the generated keys.
1589 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1591 printf ("%s\n", fpr);
1595 gpgme_genkey_result_t result;
1596 err = gpgme_op_genkey (ctx, NULL, NULL);
1599 result = gpgme_op_genkey_result (ctx);
1601 printf ("%s\n", result->fpr);
1604 * The new gpgme_op_import_result function provides detailed
1605 information about the result of an import operation in
1606 gpgme_import_result_t and gpgme_import_status_t objects.
1607 Thus, the gpgme_op_import_ext variant is deprecated.
1609 * The new gpgme_op_sign_result function provides detailed information
1610 about the result of a signing operation in gpgme_sign_result_t,
1611 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1613 * The new gpgme_op_encrypt_result function provides detailed
1614 information about the result of an encryption operation in
1615 a GpgmeEncryptResult object.
1617 * The new gpgme_op_decrypt_result function provides detailed
1618 information about the result of a decryption operation in
1619 a GpgmeDecryptResult object.
1621 * The new gpgme_op_verify_result function provides detailed
1622 information about the result of an verify operation in
1623 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1624 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1625 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1626 and gpgme_get_notation is removed.
1628 * GpgmeTrustItem objects have now directly accessible data, so the
1629 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1630 accessor functions are deprecated. Also, reference counting is
1631 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1632 (the gpgme_trust_item_release alias for the latter is deprecated).
1634 * Keys are not cached internally anymore, so the force_update argument
1635 to gpgme_get_key has been removed.
1637 * GpgmeKey objects have now directly accessible data so the
1638 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1639 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1640 functions are deprecated. Also, gpgme_key_release is now
1641 deprecated. The gpgme_key_get_as_xml function has been dropped.
1643 * Because all interfaces using attributes are deprecated, the
1644 GpgmeAttr data type is also deprecated.
1646 * The new gpgme_op_keylist_result function provides detailed
1647 information about the result of a key listing operation in
1648 a GpgmeKeyListResult object.
1650 * Now that each function comes with its own result retrieval
1651 interface, the generic gpgme_get_op_info interface is not useful
1652 anymore and dropped.
1654 * The type and mode of data objects is not available anymore.
1656 * Interface changes relative to the 0.4.0 release:
1657 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1658 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1659 GpgmeData DEPRECATED: Use gpgme_data_t.
1660 GpgmeError DEPRECATED: Use gpgme_error_t.
1661 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1662 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1663 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1664 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1665 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1666 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1667 GpgmeKey DEPRECATED: Use gpgme_key_t.
1668 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1669 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1670 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1671 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1672 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1673 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1674 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1675 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1676 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1677 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1678 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1679 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1680 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1681 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1682 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1685 gpgme_recipients_t NEW
1687 gpgme_data_encoding_t NEW
1688 gpgme_sig_stat_t NEW
1689 gpgme_sig_mode_t NEW
1691 gpgme_validity_t NEW
1692 gpgme_protocol_t NEW
1694 gpgme_passphrase_cb_t NEW
1695 gpgme_progress_cb_t NEW
1697 gpgme_register_io_cb_t NEW
1698 gpgme_remove_io_cb_t NEW
1699 gpgme_event_io_t NEW
1700 gpgme_event_io_cb_t NEW
1702 gpgme_data_read_cb_t NEW
1703 gpgme_data_write_cb_t NEW
1704 gpgme_data_seek_cb_t NEW
1705 gpgme_data_release_cb_t NEW
1706 gpgme_data_cbs_t NEW
1707 gpgme_trust_item_t NEW
1708 gpgme_status_code_t NEW
1709 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1710 gpgme_err_code_t NEW
1711 gpgme_err_source_t NEW
1713 gpgme_err_source NEW
1716 gpgme_error_from_errno NEW
1717 gpgme_err_make_from_errno NEW
1718 gpgme_err_code_from_errno NEW
1719 gpgme_err_code_to_errno NEW
1721 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1722 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1723 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1724 gpgme_edit_cb_t CHANGED: Write directly to FD.
1725 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1726 gpgme_op_verify CHANGED: Drop R_STAT argument.
1727 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1728 gpgme_wait CHANGED: Can return NULL even if hang is true.
1729 GpgmeIdleFunc REMOVED
1730 gpgme_register_idle REMOVED
1731 GpgmeRecipients REMOVED
1732 gpgme_recipients_new REMOVED
1733 gpgme_recipients_release REMOVED
1734 gpgme_recipients_add_name REMOVED
1735 gpgme_recipients_add_name_with_validity REMOVED
1736 gpgme_recipients_count REMOVED
1737 gpgme_recipients_enum_open REMOVED
1738 gpgme_recipients_enum_read REMOVED
1739 gpgme_recipients_enum_close REMOVED
1740 gpgme_encrypt_flags_t NEW
1741 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1742 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1743 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1744 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1745 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1746 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1747 gpgme_op_export CHANGED: User IDs passed as patterns.
1748 gpgme_op_export_ext_start NEW
1749 gpgme_op_export_ext NEW
1750 gpgme_keylist_mode_t NEW
1752 gpgme_engine_info_t NEW
1753 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1754 gpgme_get_protocol_name NEW
1755 gpgme_cancel REMOVED: Return error in callback directly.
1756 gpgme_op_genkey CHANGED: FPR argument dropped.
1757 gpgme_op_genkey_result NEW
1758 gpgme_genkey_result_t NEW
1759 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1760 gpgme_op_import_result NEW
1761 gpgme_import_status_t NEW
1762 gpgme_import_result_t NEW
1763 gpgme_pubkey_algo_t NEW
1764 gpgme_hash_algo_t NEW
1765 gpgme_invalid_key_t NEW
1766 gpgme_new_signature_t NEW
1767 gpgme_sign_result_t NEW
1768 gpgme_op_sign_result NEW
1769 gpgme_pubkey_algo_name NEW
1770 gpgme_hash_algo_name NEW
1771 gpgme_encrypt_result_t NEW
1772 gpgme_op_encrypt_result NEW
1773 gpgme_decrypt_result_t NEW
1774 gpgme_op_decrypt_result NEW
1775 gpgme_verify_result_t NEW
1776 gpgme_op_verify_result NEW
1777 gpgme_get_notation REMOVED: Access verify result directly instead.
1778 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1779 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1780 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1781 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1782 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1783 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1784 gpgme_trust_item_ref NEW
1785 gpgme_trust_item_unref NEW
1786 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1787 gpgme_trust_item_get_string_attr DEPRECATED
1788 gpgme_trust_item_get_ulong_attr DEPRECATED
1789 gpgme_get_key CHANGED: Removed force_update argument.
1793 gpgme_key_t CHANGED: Now has user accessible data members.
1794 gpgme_key_get_string_attr DEPRECATED
1795 gpgme_key_get_ulong_attr DEPRECATED
1796 gpgme_key_sig_get_string_attr DEPRECATED
1797 gpgme_key_sig_get_ulong_attr DEPRECATED
1798 gpgme_key_get_as_xml REMOVED
1799 gpgme_key_list_result_t NEW
1800 gpgme_op_keylist_result NEW
1801 gpgme_get_op_info REMOVED
1802 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1804 Noteworthy changes in version 0.4.0 (2002-12-23)
1805 ------------------------------------------------
1807 * Key generation returns the fingerprint of the generated key.
1809 * New convenience function gpgme_get_key.
1811 * Supports signatures of user IDs in keys via the new
1812 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1813 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1814 interfaces. The XML info about a key also includes the signatures
1817 * New data object interface, which is more flexible and transparent.
1819 * Interface changes relative to the 0.3.9 release:
1820 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1822 GpgmeDataWriteCb NEW
1824 GpgmeDataReleaseCb NEW
1826 gpgme_data_read CHANGED: Match read() closely.
1827 gpgme_data_write CHANGED: Match write() closely.
1829 gpgme_data_new_from_fd NEW
1830 gpgme_data_new_from_stream NEW
1831 gpgme_data_new_from_cbs NEW
1832 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1833 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1834 gpgme_data_get_type REMOVED: No replacement.
1835 gpgme_op_verify CHANGED: Take different data objects for
1836 signed text and plain text.
1837 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1838 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1839 gpgme_op_genkey CHANGED: New parameter FPR.
1840 GPGME_KEYLIST_MODE_SIGS NEW
1841 gpgme_key_sig_get_string_attr NEW
1842 gpgme_key_sig_get_ulong_attr NEW
1844 GPGME_ATTR_SIG_CLASS NEW
1845 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1847 Noteworthy changes in version 0.3.16 (2003-11-19)
1848 -------------------------------------------------
1850 * Compatibility fixes for GnuPG 1.9.x
1852 Noteworthy changes in version 0.3.15 (2003-02-18)
1853 -------------------------------------------------
1855 * The progress status is sent via the progress callbacks in
1858 * Bug fix for signing operations with explicit signer settings for
1861 Noteworthy changes in version 0.3.14 (2002-12-04)
1862 -------------------------------------------------
1864 * GPGME-Plug is now in its own package "cryptplug".
1866 * Workaround for a setlocale problem. Fixed a segv related to not
1867 correctly as closed marked file descriptors.
1869 Noteworthy changes in version 0.3.13 (2002-11-20)
1870 -------------------------------------------------
1872 * Release due to changes in gpgmeplug.
1874 Noteworthy changes in version 0.3.12 (2002-10-15)
1875 -------------------------------------------------
1877 * Fixed some bux with key listings.
1879 * The development has been branched to clean up some API issues.
1880 This 0.3 series will be kept for compatibility reasons; so do don't
1881 expect new features.
1883 Noteworthy changes in version 0.3.11 (2002-09-20)
1884 -------------------------------------------------
1888 Noteworthy changes in version 0.3.10 (2002-09-02)
1889 -------------------------------------------------
1891 * Setting the signing keys for the CMS protocol does now work.
1893 * The signers setting is honoured by gpgme_op_edit.
1895 Noteworthy changes in version 0.3.9 (2002-08-21)
1896 ------------------------------------------------
1898 * A spec file for creating RPMs has been added.
1900 * An experimental interface to GnuPG's --edit-key functionality is
1901 introduced, see gpgme_op_edit.
1903 * The new gpgme_import_ext function provides a convenient access to
1904 the number of processed keys.
1906 * Interface changes relative to the 0.3.8 release:
1907 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1910 gpgme_op_edit_start NEW
1912 gpgme_op_import_ext NEW
1913 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1915 Noteworthy changes in version 0.3.8 (2002-06-25)
1916 ------------------------------------------------
1918 * It is possible to use an outside event loop for the I/O to the
1919 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1921 * Interface changes relative to the 0.3.6 release:
1922 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1924 GpgmeRegisterIOCb NEW
1928 struct GpgmeIOCbs NEW
1929 gpgme_set_io_cbs NEW
1930 gpgme_get_io_cbs NEW
1931 GPGME_ATTR_ERRTOK NEW
1932 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1934 Noteworthy changes in version 0.3.7 (2002-06-04)
1935 ------------------------------------------------
1937 * GPGME_ATTR_OTRUST is implemented now.
1939 * A first step toward thread safeness has been achieved, see the
1940 documentation for details. Supported thread libraries are pthread
1943 Noteworthy changes in version 0.3.6 (2002-05-03)
1944 ------------------------------------------------
1946 * All error output of the gpgsm backend is send to the bit bucket.
1948 * The signature verification functions are extended. Instead of
1949 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1950 expired signatures. 2 new functions may be used to retrieve more
1951 detailed information like the signature expiration time and a
1952 validity information of the key without an extra key looking.
1954 * The current passphrase callback and progress meter callback can be
1955 retrieved with the new functions gpgme_get_passphrase_cb and
1956 gpgme_get_progress_cb respectively.
1958 * Interface changes relative to the 0.3.5 release:
1959 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1960 gpgme_get_passphrase_cb NEW
1961 gpgme_get_progress_cb NEW
1962 GpgmeDataEncoding NEW
1963 gpgme_data_set_encoding NEW
1964 gpgme_data_get_encoding NEW
1965 GPGME_SIG_STAT_GOOD_EXP NEW
1966 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1967 gpgme_op_verify CHANGED: Returns more status codes.
1968 GPGME_ATTR_SIG_STATUS NEW
1969 gpgme_get_sig_string_attr NEW
1970 gpgme_get_sig_ulong_attr NEW
1971 gpgme_get_protocol NEW
1972 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1974 Noteworthy changes in version 0.3.5 (2002-04-01)
1975 ------------------------------------------------
1977 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1978 case, symmetric encryption is performed. Note that this requires a
1979 passphrase from the user.
1981 * More information is returned for X.509 certificates.
1983 * Interface changes relative to the 0.3.4 release:
1984 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1985 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1986 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1988 Noteworthy changes in version 0.3.4 (2002-03-04)
1989 ------------------------------------------------
1991 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1992 some recipients have been invalid, whereas earlier versions
1993 succeeded in this case. The plaintext is still encrypted for all valid
1994 recipients, so the application might take this error as a hint that
1995 the ciphertext is not usable for all requested recipients.
1996 Information about invalid recipients is available with gpgme_get_op_info.
1998 * gpgme_op_verify now allows to pass an uninitialized data object as
1999 its plaintext argument to check for normal and cleartext
2000 signatures. The plaintext is then returned in the data object.
2002 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
2003 to set and get the number of certifications to include in S/MIME
2006 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
2007 to encrypt and sign a message in a combined operation.
2009 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
2011 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
2013 * Interface changes relative to the 0.3.3 release:
2014 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2015 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
2016 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
2017 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
2018 gpgme_set_include_certs NEW
2019 gpgme_get_include_certs NEW
2020 gpgme_op_encrypt_sign NEW
2021 gpgme_op_encrypt_sign_start NEW
2022 gpgme_op_keylist_ext_start NEW
2023 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2025 Noteworthy changes in version 0.3.3 (2002-02-12)
2026 ------------------------------------------------
2028 * Fix the Makefile in jnlib.
2030 * Fix the test suite (hopefully). It should clean up all its state
2031 with `make check' now.
2034 Noteworthy changes in version 0.3.2 (2002-02-10)
2035 ------------------------------------------------
2037 * Remove erroneous dependency on libgcrypt in jnlib.
2040 Noteworthy changes in version 0.3.1 (2002-02-09)
2041 ------------------------------------------------
2043 * There is a Texinfo manual documenting the API.
2045 * The gpgme_set_keylist_mode function returns an error, and changed
2046 its meaning. It is no longer usable to select between normal and
2047 fast mode (newer versions of GnuPG will always be fast), but
2048 selects between local keyring, remote keyserver, or both.
2049 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
2050 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
2051 current setting, a function gpgme_get_keylist_mode was added to
2052 retrieve the current mode.
2054 * gpgme_wait accepts a new argument STATUS to return the error status
2055 of the operation on the context. Its definition is closer to
2056 waitpid() now than before.
2058 * The LENGTH argument to gpgme_data_new_from_filepart changed its
2059 type from off_t to the unsigned size_t.
2061 * The R_HD argument to the GpgmePassphraseCb type changed its type
2062 from void* to void**.
2064 * New interface gpgme_op_trustlist_end() to match
2065 gpgme_op_keylist_end().
2067 * The CryptPlug modules have been renamed to gpgme-openpgp and
2068 gpgme-smime, and they are installed in pkglibdir by `make install'.
2070 * An idle function can be registered with gpgme_register_idle().
2072 * The GpgSM backend supports key generation with gpgme_op_genkey().
2074 * Interface changes relative to the 0.3.0 release:
2075 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2076 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
2077 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
2078 gpgme_wait CHANGED: New argument STATUS.
2079 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
2080 The function has a new meaning!
2081 gpgme_get_keylist_mode NEW
2082 GPGME_KEYLIST_MODE_LOCAL NEW
2083 GPGME_KEYLIST_MODE_EXTERN NEW
2084 gpgme_op_trustlist_next NEW
2086 gpgme_register_idle NEW
2087 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2089 Noteworthy changes in version 0.3.0 (2001-12-19)
2090 ------------------------------------------------
2092 * New interface gpgme_set_protocol() to set the protocol and thus the
2093 crypto engine to be used by the context. Currently, the OpenPGP
2094 and the CMS protocols are supported. They are specified by the new
2095 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
2096 A new context uses the OpenPGP engine by default.
2098 * gpgme_get_engine_info() returns information for all crypto engines
2099 compiled into the library. The XML format has changed. To
2100 reliably get the version of a crypto engine, the <version> tag
2101 after the appropriate <protocol> tag has to be looked for.
2103 * New interface gpgme_engine_check_version(), obsoleting
2104 gpgme_check_engine(). Check the version of all engines you are
2105 supporting in your software.
2107 * GpgmeKey lists the user ids in the order as they are returned by
2108 GnuPG, first the primary key with index 0, then the sub-user ids.
2110 * New operation gpgme_op_decrypt_verify() to decrypt and verify
2111 signatures simultaneously.
2113 * The new interface gpgme_op_keylist_end() terminates a pending
2114 keylist operation. A keylist operation is also terminated when
2115 gpgme_op_keylist_next() returns GPGME_EOF.
2117 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
2118 cross-compiled, or even compiled without support for GnuPG
2121 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
2122 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
2123 in the path, but it can also be compiled without support for GpgSM
2124 (`--without-gpgsm').
2126 * CryptPlug modules for GPGME are included and can be enabled at
2127 configure time (`--enable-gpgmeplug'). There is one module which
2128 uses the GnuPG engine (`gpgmeplug') and one module which uses the
2129 GpgSM engine (`gpgsmplug').
2131 * Interface changes relative to the latest 0.2.x release:
2132 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2133 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
2134 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
2135 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
2136 gpgme_get_engine_info CHANGED: New format, extended content.
2137 gpgme_engine_check_version NEW
2138 gpgme_decrypt_verify_start NEW
2139 gpgme_decrypt_verify NEW
2140 gpgme_op_keylist_next NEW
2141 gpgme_set_protocol NEW
2142 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2145 Noteworthy changes in version 0.2.3 (2001-09-17)
2146 ------------------------------------------------
2148 * New function gpgme_get_op_info which can be used to get the micalg
2149 parameter needed for MOSS.
2151 * New functions gpgme_get_armor and gpgme_get_textmode.
2153 * The usual bug fixes and some minor functionality improvements.
2155 * Added a simple encryption component for MS-Windows; however the
2156 build procedure might have some problems.
2159 Noteworthy changes in version 0.2.2 (2001-06-12)
2160 ------------------------------------------------
2162 * Implemented a key cache.
2164 * Fixed a race condition under W32 and some other bug fixes.
2167 Noteworthy changes in version 0.2.1 (2001-04-02)
2168 ------------------------------------------------
2170 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
2172 * Handle GnuPG's new key capabilities output and support revocation
2175 * Made the W32 support more robust.
2178 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
2181 This file is free software; as a special exception the author gives
2182 unlimited permission to copy and/or distribute it, with or without
2183 modifications, as long as this notice is preserved.
2185 This file is distributed in the hope that it will be useful, but
2186 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
2187 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.