1 Noteworthy changes in version 1.16.0 (2021-06-24)
2 -------------------------------------------------
4 * New context flag "cert-expire". [#5505]
6 * New data flags "io-buffer-size" and "sensitive". [#5478]
8 * Increase I/O buffer size from 512 to 4k under Windows.
10 * cpp,qt: Add support for trust signatures. [#5421]
12 * qt: Add support for flags in LDAP server options. [#5217]
14 * qt: Fix too high memory consumption due to QProcess. [#5475]
16 * qt: Do not set empty base DN as query of keyserver URL. [#5465]
18 * qt: Extend SignKeyJob to create signatures with expiration date.
21 * python: New optional parameter filter_signatures for decrypt.
24 * Interface changes relative to the 1.15.1 release:
25 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
26 gpgme_set_ctx_flag EXTENDED: New flag 'cert-expire'.
27 cpp: SignKeyJob::setTrustSignature NEW.
28 cpp: TrustSignatureTrust NEW.
29 cpp: GpgSignKeyEditInteractor::setTrustSignatureTrust NEW.
30 cpp: GpgSignKeyEditInteractor::setTrustSignatureDepth NEW.
31 cpp: GpgSignKeyEditInteractor::setTrustSignatureScope NEW.
32 cpp: UserID::Signature::isTrustSignature NEW.
33 cpp: UserID::Signature::trustValue NEW.
34 cpp: UserID::Signature::trustDepth NEW.
35 cpp: UserID::Signature::trustScope NEW.
36 gpgme_key_sig_t EXTENDED: New field 'trust_depth'.
37 gpgme_key_sig_t EXTENDED: New field 'trust_value'.
38 gpgme_key_sig_t EXTENDED: New field 'trust_scope'.
39 GPGME_KEYSIGN_FORCE NEW.
40 qt: CryptoConfig::entry CHANGED: Added overload; deprecated old
42 [c=C36/A25/R0 cpp=C19/A13/R0 qt=C13/A6/R0]
44 Release-info: https://dev.gnupg.org/T5499
47 Noteworthy changes in version 1.15.1 (2021-01-08)
48 -------------------------------------------------
50 * Fix another bug in the secret key export. [#5046]
52 * Make listing of signatures work if only secret keys are listed. [#3580]
54 * Fix build problem on FreeBSD. [a6220adf30]
56 * qt: Avoid empty "rem@gnupg.org" signature notations. [#5142]
58 * python: Fix key_export functions. [#5149]
61 [c=C35/A24/R1 cpp=C18/A12/R1 qt=C12/A5/R1]
63 Release-info: https://dev.gnupg.org/T5225
66 Noteworthy changes in version 1.15.0 (2020-11-12)
67 -------------------------------------------------
69 * New function gpgme_op_setexpire to make changing the expiration
70 easier (requires GnuPG 2.1.22). [#4999]
72 * New function gpgme_op_revsig to revoke key signatures (requires
73 GnuPG 2.2.24). [#5094]
75 * Support exporting secret keys. [#5046]
77 * cpp: Support for set expire operations in the C++ bindings. [#5003]
79 * cpp: Support for revoking key signatures in the C++ bindings. [#5094]
81 * qt: Extended ChangeExpiryJob to support changing the expiry of
84 * qt: Extended QuickJob to support revoking of key signatures. [#5094]
86 * qt: Added QDebug stream operator for GpgME::Error.
88 * Require a somewhat newer version of libgpg-error (1.36).
90 * Interface changes relative to the 1.14.0 release:
91 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
92 gpgme_op_setexpire_start NEW.
93 gpgme_op_setexpire NEW.
94 gpgme_op_revsig_start NEW.
96 GPGME_REVSIG_LFSEP NEW.
97 cpp: Context::setExpire NEW.
98 cpp: Context::startSetExpire NEW.
99 cpp: EngineInfo::Version::operator<= NEW.
100 cpp: EngineInfo::Version::operator>= NEW.
101 cpp: EngineInfo::Version::operator!= NEW.
102 cpp: StatusConsumer NEW.
103 cpp: StatusConsumerAssuanTransaction NEW.
104 cpp: Context::cancelPendingOperationImmediately NEW.
105 cpp: Context::revokeSignature NEW.
106 cpp: Context::startRevokeSignature NEW.
107 cpp: UserID::Signature::operator< NEW.
108 qt: operator<<(QDebug debug, const GpgME::Error &err) NEW.
109 qt: QuickJob::startRevokeSignature NEW.
110 qt: QuickJob::result CHANGED: Made params 'auditLogAsHtml'
111 and 'auditLogError' optional.
113 [c=C35/A24/R0 cpp=C18/A12/R0 qt=C12/A5/R0]
115 Release-info: https://dev.gnupg.org/T5131
118 Noteworthy changes in version 1.14.0 (2020-07-16)
119 -------------------------------------------------
121 * New keylist mode to force the engine to return the keygrip. [#4820]
123 * New export mode to export as OpenSSH public key. [#4310]
125 * New context flag "extended-edit" to enable expert key edit. [#4734]
127 * Deprecate the anyway non working trustlist functions. [#4834]
129 * cpp: Add convenience API to obtain remarks. [#4734]
131 * cpp: The sign key edit-interactor now supports multiple signatures
132 from the same key. [#4734]
134 * qt: Extended signkeyjob to handle remarks and multiple signatures.
137 * qt: Added job API for gpg-card.
139 * qt: The logging category has been changed to gpg.qgpgme to be more
140 consistent with other qt logging categories.
142 * Interface changes relative to the 1.13.1 release:
143 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
144 GPGME_KEYLIST_MODE_WITH_KEYGRIP NEW.
145 GPGME_EXPORT_MODE_SSH NEW.
146 gpgme_user_id_t EXTENDED: New field 'uidhash'.
147 cpp: UserID::remark NEW.
148 cpp: UserID::remarks NEW.
149 cpp: GpgSignKeyEditInteractor::setDupeOk NEW.
150 cpp: Context::exportPublicKeys EXTENDED: New param 'flags'.
151 cpp: Context::startPublicKeyExport EXTENDED: New param 'flags'.
152 cpp: Context::ExportMode NEW.
153 qt: SignKeyJob::setDupeOk NEW.
154 qt: SignKeyJob::setRemark NEW.
156 qt: ExportJob::setExportFlags NEW.
158 [c=C34/A23/R0 cpp=C17/A11/R0 qt=C11/A4/R0]
160 Release-info: https://dev.gnupg.org/T4996
163 Noteworthy changes in version 1.13.1 (2019-06-13)
164 -------------------------------------------------
166 * cpp: gpgme_set_global_flag is now wrapped. [#4471]
168 * w32: Improved handling of unicode install paths. [#4453]
170 * w32: The gpgme_io_spawn error message is now only shown once. [#4453]
172 * Fixed a crash introduced in 1.13.0 when working with S/MIME. [#4556]
174 * w32: Fixed format string errors introduced in 1.13.0 that could
175 cause crashes. [#4440]
177 * w32: Fixed an error in the new diagnostic gpgsm support introduced
178 in 1.13.0 that caused crashes in low fd scenarios. [#4439]
180 * python: Fixed a DecryptionError Exception. [#4478]
182 * python: No longer raises BadSignatures from decrypt(verify=True).
185 * Interface changes relative to the 1.13.0 release:
186 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
187 cpp: setGlobalFlag NEW.
189 [c=C33/A22/R1 cpp=C16/A10/R0 qt=C10/A3/R4]
191 Release-info: https://dev.gnupg.org/T4551
194 Noteworthy changes in version 1.13.0 (2019-03-26)
195 -------------------------------------------------
197 * Support GPGME_AUDITLOG_DIAG for gpgsm. [#4426]
199 * New context flag "trust-model".
201 * Removed support for WindowsCE and Windows ME.
203 * Aligned the gpgrt-config code with our other libaries.
205 * Auto-check for all installed Python versions. [#3354]
207 * Fixed generating card key in the C++ bindings. [#4428]
209 * Fixed a segv due to bad parameters in genkey. [#4192]
211 * Fixed crash if the plaintext is ignored in a CMS verify.
213 * Fixed memleak on Windows. [T4238]
215 * Tweaked the Windows I/O code.
217 * Fixed random crashes on Windows due to closing an arbitrary
220 * Fixed a segv on Windows. [#4369]
222 * Fixed test suite problems related to dtags. [#4298]
224 * Fixed bunch of python bugs. [#4242,commit 9de1c96ac3cf]
226 * Several fixes to the Common Lisp bindings.
228 * Fixed minor bugs in gpgme-json. [#4331,#4341,#4342,#4343
230 * Require trace level 8 to dump all I/O data.
232 * The compiler must now support variadic macros.
234 * Interface changes relative to the 1.12.0 release:
235 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
236 gpgme_set_ctx_flag EXTENDED: New flag 'trust-model'.
237 cpp: Context::create NEW.
239 cpp: Subkey::isBad NEW.
240 cpp: UserID::isBad NEW.
241 cpp: UserID::Signature::isBad NEW.
242 cpp: GenCardKeyInteractor::setAlgo NEW.
244 [c=C33/A22/R0 cpp=C15/A9/R0 qt=C10/A3/R3]
246 Release-info: https://dev.gnupg.org/T4376
249 Noteworthy changes in version 1.12.0 (2018-10-08)
250 -------------------------------------------------
252 * Enhanced the JSON based interface tool gpgme-json to support Native
253 Messaging as well as new Javascript code to support the browser
254 site. See lang/js/README for details.
256 * Major overhaul of the Python language bindings documentation.
258 * Even for old versions of gpg a missing MDC will now lead to a
261 * Added context flag "auto-key-locate" to control the
262 behavior of GPGME_KEYLIST_MODE_LOCATE.
264 * New data function to create a data object from an estream.
266 * Add more interfaces to the C++ bindings.
268 * Improved error codes on decryption failure.
270 * Lots of minor fixes.
272 * Interface changes relative to the 1.11.1 release:
273 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
274 gpgme_data_new_from_estream NEW.
275 gpgme_decrypt_result_t EXTENDED: New field legacy_cipher_nomdc.
276 gpgme_set_ctx_flag EXTENDED: New flag 'ignore-mdc-error'.
277 GPGME_AUDITLOG_DEFAULT NEW.
278 GPGME_AUDITLOG_DIAG NEW.
279 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-locate'.
280 cpp: DecryptionResult::sessionKey NEW.
281 cpp: DecryptionResult::symkeyAlgo NEW.
282 cpp: DecryptionResult::isLegacyCipherNoMDC New.
283 cpp: Data::rewind NEW.
284 cpp: Context::setFlag NEW.
285 cpp: Context::getFlag NEW.
286 cpp: Context::createKeyEx NEW.
288 [c=C32/A21/R0 cpp=C14/A8/R0 qt=C10/A3/R2]
290 Release-info: https://dev.gnupg.org/T4109
293 Noteworthy changes in version 1.11.1 (2018-04-20)
294 -------------------------------------------------
296 * Fixed build problems in the 1.11.0 release.
298 * Added C++ interfaces which were planned for 1.11.0.
300 * Interface changes relative to the 1.10.0 release:
301 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
302 cpp: Key::origin NEW.
303 cpp: Key::lastUpdate NEW.
304 cpp: UserID::origin NEW.
305 cpp: UserID::lastUpdate NEW.
307 [c=C31/A20/R1 cpp=C13/A7/R0 qt=C10/A3/R2]
310 Noteworthy changes in version 1.11.0 (2018-04-18)
311 -------------------------------------------------
313 * New encryption API to support direct key specification including
314 hidden recipients option and taking keys from a file. This also
315 allows to enforce the use of a subkey.
317 * New encryption flag for the new API to enforce the use of plain
318 mail addresses (addr-spec).
320 * The import API can now tell whether v3 keys are skipped. These old
321 and basically broken keys are not anymore supported by GnuPG 2.1.
323 * The decrypt and verify API will now return the MIME flag as
324 specified by RFC-4880bis.
326 * The offline mode now has an effect on gpg by disabling all network
329 * A failed OpenPGP verification how returns the fingerprint of the
330 intended key if a recent gpg version was used for signature
333 * New tool gpgme-json as native messaging server for web browsers.
334 As of now public key encryption and decryption is supported.
335 Requires Libgpg-error 1.29.
337 * New context flag "request-origin" which has an effect when used
338 with GnuPG 2.2.6 or later.
340 * New context flag "no-symkey-cache" which has an effect when used
341 with GnuPG 2.2.7 or later.
343 * New convenience constant GPGME_KEYLIST_MODE_LOCATE.
345 * Improved the Python documentation.
347 * Fixed a potential regression with GnuPG 2.2.6 or later.
349 * Fixed a crash in the Python bindings on 32 bit platforms. [#3892]
351 * Various minor fixes.
353 * Interface changes relative to the 1.10.0 release:
354 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
355 gpgme_op_encrypt_ext NEW.
356 gpgme_op_encrypt_ext_start NEW.
357 gpgme_op_encrypt_sign_ext NEW.
358 gpgme_op_encrypt_sign_ext_start NEW.
359 GPGME_ENCRYPT_WANT_ADDRESS NEW.
360 GPGME_KEYLIST_MODE_LOCATE NEW.
361 gpgme_import_result_t EXTENDED: New field 'skipped_v3_keys'.
362 gpgme_decrypt_result_t EXTENDED: New field 'symkey_algo'.
363 gpgme_decrypt_result_t EXTENDED: New field 'is_mime'.
364 gpgme_verify_result_t EXTENDED: New field 'is_mime'.
365 cpp: Key::locate NEW.
366 cpp: Data::toString NEW.
367 cpp: ImportResult::numV3KeysSkipped NEW.
369 [c=C31/A20/R0 cpp=C12/A6/R0 qt=C10/A3/R1]
372 Noteworthy changes in version 1.10.0 (2017-12-12)
373 -------------------------------------------------
375 * Now returns more specific error codes for decryption to distinguish
376 between bad passphrase, user canceled, and no secret key.
378 * Now returns key origin information if available.
380 * Added context flag "auto-key-retrieve" to selectively enable the
381 corresponding gpg option.
383 * Added flag is_de_vs to decryption and verify results.
385 * py: Use SEEK_SET as default for data.seek.
387 * cpp: Various new APIs.
389 * Reduced spawn overhead on Linux again. Added new configure option
390 --disable-linux-getdents to disable this feature for very old
393 * Improved the Python bindings build system.
395 * Made the test suite less fragile.
397 * Interface changes relative to the 1.9.0 release:
398 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
399 gpgme_decrypt_result_t EXTENDED: New field 'is_de_vs'.
400 gpgme_signature_t EXTENDED: New field 'is_de_vs'.
402 gpgme_op_delete_ext NEW.
403 gpgme_op_delete_ext_start NEW.
404 GPGME_DELETE_ALLOW_SECRET NEW.
405 GPGME_DELETE_FORCE NEW.
406 gpgme_op_conf_dir NEW.
407 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-retrieve'.
408 cpp: DecryptionResult::isDeVs NEW.
409 cpp: Signature::isDeVs NEW.
410 cpp: EngineInfo::Version::operator> NEW.
411 cpp: Context::createKey NEW.
412 cpp: Context::startCreateKey NEW.
413 cpp: Context::createSubkey NEW.
414 cpp: Context::startCreateSubkey NEW.
416 py: DecryptResult EXTENDED: New boolean field 'is_de_vs'.
417 py: Signature EXTENDED: New boolean field 'is_de_vs'.
418 py: GpgError EXTENDED: Partial results in 'results'.
420 [c=C30/A19/R0 cpp=C11/A5/R0 qt=C10/A3/R0]
423 Noteworthy changes in version 1.9.0 (2017-03-28)
424 ------------------------------------------------
426 * Clarified meaning of the 'expire' parameter of gpgme_op_createkey
427 and gpgme_op_createsubkey. New flag to force a key without an
430 * New function gpgme_op_keylist_from_data_start to list keys from
431 data objects without importing them.
433 * New function gpgme_op_set_uid_flag to flag a key as primary.
435 * New function gpgme_op_decrypt_ext to run decryption with special
436 flags. This can for example be used to unwrap keys (remove only
437 the encryption layer).
439 * New encryption flags to wrap a key (adding an encryption layer to
440 an OpenPGP message) or to create anonymously encrypted messages.
442 * Support for adduid and revuid operations in the C++ bindings.
444 * Support for smartcard key generation in the C++ bindings.
446 * Several new functions for the Python binding.
448 * Many smaller bug fixes.
450 * Interface changes relative to the 1.8.0 release:
451 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
452 gpgme_op_createkey CHANGED: Meaning of 'expire' parameter.
453 gpgme_op_createsubkey CHANGED: Meaning of 'expire' parameter.
454 GPGME_CREATE_NOEXPIRE NEW.
455 gpgme_key_t EXTENDED: New field 'origin'.
456 gpgme_key_t EXTENDED: New field 'last_update'.
457 gpgme_subkey_t EXTENDED: New field 'is_de_vs'.
458 gpgme_user_id_t EXTENDED: New field 'origin'.
459 gpgme_user_id_t EXTENDED: New field 'last_update'.
460 gpgme_op_keylist_from_data_start NEW.
461 gpgme_op_set_uid_flag_start NEW.
462 gpgme_op_set_uid_flag NEW.
463 gpgme_op_decrypt_ext_start NEW.
464 gpgme_op_decrypt_ext NEW.
465 GPGME_ENCRYPT_THROW_KEYIDS NEW.
466 GPGME_ENCRYPT_WRAP NEW.
467 GPGME_DECRYPT_VERIFY NEW.
468 GPGME_DECRYPT_UNWRAP NEW.
469 gpgme_data_rewind UN-DEPRECATE.
470 cpp: Context::revUid(const Key&, const char*) NEW.
471 cpp: Context::startRevUid(const Key&, const char*) NEW.
472 cpp: Context::addUid(const Key&, const char*) NEW.
473 cpp: Context::startAddUid(const Key&, const char*) NEW.
474 cpp: Key::UserID::revoke() NEW.
475 cpp: Key::addUid() NEW.
476 cpp: Key::isDeVs NEW.
477 cpp: GpgGenCardKeyInteractor NEW.
478 cpp: Subkey::keyGrip NEW.
479 cpp: Subkey::isDeVs NEW.
480 cpp: Data::toKeys NEW.
481 cpp: Context::setDecryptFlags NEW.
482 cpp: Context::decrypt EXTENDED: Flags added.
483 cpp: Context::startDecrypt EXTENDED: Flags added.
484 cpp: Context::decryptAndVerify EXTENDED: Flags added.
485 cpp: Context::startCombinedDecryptionAndVerification EXTENDED: Flags.
486 cpp: Context::encryptFlags EXTENDED: New flags.
487 qt: CryptoConfig::stringValueList() NEW.
488 py: Context.__init__ EXTENDED: New keyword arg home_dir.
489 py: Context.home_dir NEW.
490 py: Context.keylist EXTENDED: New keyword arg mode.
491 py: Context.keylist EXTENDED: New keyword arg source.
492 py: Context.create_key NEW.
493 py: Context.create_subkey NEW.
494 py: Context.key_add_uid NEW.
495 py: Context.key_revoke_uid NEW.
496 py: Context.key_sign NEW.
497 py: Context.key_tofu_policy NEW.
498 py: core.pubkey_algo_string NEW.
499 py: core.addrspec_from_uid NEW.
501 [c=C29/A18/R0 cpp=C10/A4/R0 qt=C9/A2/R0]
504 Noteworthy changes in version 1.8.0 (2016-11-16)
505 ------------------------------------------------
507 * The module of the Python bindings has been renamed to 'gpg'.
509 * New interface to query current software versions.
511 * New feature to use gpg's --{show,override}session-key options.
513 * New interface to set the sender of a mail.
515 * qt: Added Distinguished Name parser from libkleo
517 * The --homedir option is now used with recent gpgconf versions.
519 * On 64 bit Windows systems gpgconf is now properly located.
521 * The internal locking functions have been replaced by libgpg-error
524 * Interface changes relative to the 1.7.1 release:
525 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
526 gpgme_set_sender NEW.
527 gpgme_get_sender NEW.
528 gpgme_op_query_swdb NEW.
529 gpgme_op_query_swdb_result NEW.
530 gpgme_query_swdb_result_t NEW.
531 gpgme_get_ctx_flag NEW.
532 gpgme_decrypt_result_t EXTENDED: New field session_key.
534 qt: DN::Attribute NEW.
535 qt: Job::context(Job*) NEW.
536 cpp: EngineInfo::Version::Version(const char*) NEW.
537 cpp: EngineInfo::Version::Version() NEW.
539 cpp: Context::setSender(const char*) NEW.
540 cpp: Context::getSender() NEW.
542 [c=C28/A17/R0 cpp=C9/A3/R0 qt=C8/A1/R0]
545 Noteworthy changes in version 1.7.1 (2016-10-18)
546 ------------------------------------------------
548 * Fixed problems with the new language bindings.
550 * New helper function gpgme_addrspec_from_uid.
552 * Use option --exit-on-status-write-error with newer gpg versions.
554 * qt: Missed API from the Qt Binding inclusion has
557 * qt: abstractimportjob.h is now installed to that
558 ImportJobs can be used again.
560 * qt: Fixed spelling error in API (startReceive).
562 * Interface changes relative to the 1.7.0 release:
563 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
564 gpgme_addrspec_from_uid NEW.
565 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
566 qt: MultiDeleteJob NEW.
567 qt: AbstractImportJob NEW.
569 cpp: Signature::key(bool, bool) NEW.
570 cpp: UserID::addrSpecFromString(const char*) NEW.
571 cpp: UserID::addrSpec() NEW.
573 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
576 Noteworthy changes in version 1.7.0 (2016-09-21)
577 ------------------------------------------------
579 * New language bindings for Python 2 and 3.
581 * New language Bindings for C++ and the Qt-Framework API.
583 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
584 key creation easier (requires GnuPG 2.1).
586 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
587 management easier (requires GnuPG 2.1).
589 * New function gpgme_op_keysign to make key signing easier (requires
592 * New function gpgme_op_interact to replace the now deprecated
593 functions gpgme_op_edit and gpgme_op_card_edit.
595 * New function gpgme_pubkey_algo_string to convert a public key
596 algorithm into a GnuPG 2.1 style string.
598 * Support for GnuPG 2.1's TOFU trust model.
600 * Notation flags are now correctly set on verify.
602 * New global flag "require-gnupg" to set a minimal gnupg version.
604 * More supported items in gpgme_get_dirinfo.
606 * New function gpgme_data_set_flag and flag "size-hint".
608 * New function gpgme_set_ctx_flag and flags "full-status" and
611 * Improved gpgme_data_identify to distinguish more file types.
613 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
614 mixed public key and symmetric encryption.
616 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
618 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
619 signed data is a valid MIME part. This is to support future GnuPG
622 * Interface changes relative to the 1.6.0 release:
623 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
624 gpgme_pubkey_algo_string NEW.
626 gpgme_set_ctx_flag NEW.
627 gpgme_data_set_flag NEW.
628 gpgme_op_createkey NEW.
629 gpgme_op_createkey_start NEW.
630 gpgme_op_createsubkey NEW.
631 gpgme_op_createsubkey_start NEW.
632 gpgme_op_adduid_start NEW.
634 gpgme_op_revuid_start NEW.
636 gpgme_op_keysign_start NEW.
637 gpgme_op_keysign NEW.
638 gpgme_op_tofu_policy_start NEW.
639 gpgme_op_tofu_policy NEW.
640 gpgme_op_interact_start NEW.
641 gpgme_op_interact NEW.
642 gpgme_interact_cb_t NEW.
643 gpgme_op_edit_start DEPRECATED.
644 gpgme_op_edit DEPRECATED.
645 gpgme_op_card_edit_start DEPRECATED.
646 gpgme_op_card_edit DEPRECATED.
647 gpgme_edit_cb_t DEPRECATED.
648 gpgme_status_code_t DEPRECATED.
649 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
650 gpgme_signature_t EXTENDED: New field key.
651 gpgme_key_t EXTENDED: New field fpr.
652 gpgme_subkey_t EXTENDED: New field keygrip.
653 gpgme_user_id_t EXTENDED: New field tofu.
654 gpgme_tofu_policy_t NEW.
655 gpgme_tofu_info_t NEW.
656 GPGME_STATUS_KEY_CONSIDERED NEW.
657 GPGME_STATUS_TOFU_USER NEW.
658 GPGME_STATUS_TOFU_STATS NEW.
659 GPGME_STATUS_TOFU_STATS_LONG NEW.
660 GPGME_STATUS_NOTATION_FLAGS NEW.
661 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
662 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
663 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
664 GPGME_DATA_ENCODING_MIME NEW.
665 GPGME_ENCRYPT_SYMMETRIC NEW.
666 GPGME_CREATE_SIGN NEW.
667 GPGME_CREATE_ENCR NEW.
668 GPGME_CREATE_CERT NEW.
669 GPGME_CREATE_AUTH NEW.
670 GPGME_CREATE_NOPASSWD NEW.
671 GPGME_CREATE_SELFSIGNED NEW.
672 GPGME_CREATE_NOSTORE NEW.
673 GPGME_CREATE_WANTPUB NEW.
674 GPGME_CREATE_WANTSEC NEW.
675 GPGME_CREATE_FORCE NEW.
676 GPGME_KEYSIGN_LOCAL NEW.
677 GPGME_KEYSIGN_LFSEP NEW.
678 GPGME_INTERACT_CARD NEW.
680 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
683 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
684 ------------------------------------------------
686 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
688 * Added gpgme_set_status_cb to allow a user to see some status
691 * Added an export mode for secret keys.
693 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
695 * The passphrase handler for the loopback mode has been improved and may
696 also be used with genkey.
698 * [w32] The standard GnuPG 2.1 install directory is now searched for
699 gpgconf.exe before a registry specified directory and the Gpg4win
702 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
705 * Interface changes relative to the 1.5.1 release:
706 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
707 gpgme_set_offline NEW.
708 gpgme_get_offline NEW.
709 gpgme_set_status_cb NEW.
710 gpgme_get_status_cb NEW.
711 GPGME_EXPORT_MODE_SECRET NEW
712 GPGME_EXPORT_MODE_RAW NEW.
713 GPGME_EXPORT_MODE_PKCS12 NEW.
716 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
717 ------------------------------------------------
719 * Fixed crash in key listings for user ids with a backslash.
721 * Fixed regression for GPGSM use with GnuPG < 2.1.
723 * Properly set signature summary for revoked OpenPGP keys.
726 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
727 ------------------------------------------------
729 * Fixed a possible crash in the debug code.
731 * Fixed building for Windows with newer versions of Mingw.
734 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
735 -------------------------------------------------------------
737 * The export key functions do now return an error if used with the
738 latest GnuPG version.
741 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
742 -------------------------------------------------------------
744 * gpgme-tool is now installed.
746 * Fix external listing for modern keyservers.
751 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
752 -------------------------------------------------------------
754 * Fixed possible overflow in gpgsm and uiserver engines.
757 * Added support for GnuPG 2.1's --with-secret option.
759 * Interface changes relative to the 1.5.0 release:
760 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
761 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
764 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
765 -------------------------------------------------------------
767 * On Unices the engine file names are not not anymore hardwired but
768 located via the envvar PATH. All options to set the name of the
769 engines for the configure run are removed.
771 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
772 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
773 is not found, GPGME looks for an engine named "gpg".
775 * New feature to use the gpgme I/O subsystem to run arbitrary
778 * New flag to use encryption without the default compression step.
780 * New function to access "gpg-conf --list-dirs"
782 * New configure option --enable-fixed-path for use by Android.
784 * Support ECC algorithms.
786 * Interface changes relative to the 1.4.3 release:
787 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
788 gpgme_get_dirinfo NEW.
789 gpgme_op_spawn_start NEW.
791 GPGME_PROTOCOL_SPAWN NEW.
792 GPGME_SPAWN_DETACHED NEW.
793 GPGME_SPAWN_ALLOW_SET_FG NEW.
794 GPGME_ENCRYPT_NO_COMPRESS NEW.
797 gpgme_subkey_t EXTENDED: New field curve.
798 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
799 GPGME_STATUS_MOUNTPOINT NEW.
800 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
801 GPGME_STATUS_ATTRIBUTE NEW.
802 GPGME_STATUS_BEGIN_SIGNING NEW.
803 GPGME_STATUS_KEY_NOT_CREATED NEW.
806 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
807 -------------------------------------------------------------
809 * The default engine names are now taken from the output of gpgconf.
810 If gpgconf is not found the use of gpg 1 is assumed.
812 * Under Windows the default engines names are first searched in the
813 installation directory of the gpgme DLL.
815 * New function gpgme_data_identify to detect the type of a message.
817 * Interface changes relative to the 1.4.2 release:
818 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
819 gpgme_signers_count NEW.
820 gpgme_data_type_t NEW.
821 gpgme_data_identify NEW.
824 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
825 -------------------------------------------------------------
827 * Allow symmetric encryption with gpgme_op_encrypt_sign.
829 * Fixed mismatching off_t definitions on Windows.
831 * Interface changes relative to the 1.4.1 release:
832 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
835 GPGME_PROTOCOL_OPENPGP NEW alias.
838 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
839 ------------------------------------------------------------
841 * Fixed reading of gpg.conf files with excessive use of the group
844 * Fixed building with the i686-w64-mingw32 toolchain.
846 * Disabled FD passing by default for Apple.
849 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
850 ------------------------------------------------------------
852 * New function gpgme_set_global_flag to help debugging on Android.
854 * New function gpgme_io_writen as a convenience wrapper around
857 * New functions to support the pinentry mode feature of GnuPG 2.1.
859 * New macro GPGME_VERSION_NUMBER to allow supporting different API
860 versions without the need for a configure test.
862 * Several improvements for gpgme-tool.
864 * Better logging of the common "invalid engine" error code.
866 * Support for FD passing is now enabled by default. The configure
867 option --disable-fd-passing may be used to disable this.
869 * Interface changes relative to the 1.3.1 release:
870 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
871 GPGME_VERSION_NUMBER NEW.
873 gpgme_set_global_flag NEW.
874 gpgme_set_pinentry_mode NEW.
875 gpgme_get_pinentry_mode NEW.
876 gpgme_pinentry_mode_t NEW.
877 GPGME_PINENTRY_MODE_DEFAULT NEW.
878 GPGME_PINENTRY_MODE_ASK NEW.
879 GPGME_PINENTRY_MODE_CANCEL NEW.
880 GPGME_PINENTRY_MODE_ERROR NEW.
881 GPGME_PINENTRY_MODE_LOOPBACK NEW.
884 Noteworthy changes in version 1.3.2 (2012-05-02)
885 ------------------------------------------------
887 * Remove support for libgpgme-pth. As far as we know, this was never used,
888 and GnuPG is going to use our own npth in the future.
890 * Fix signature summary information for a missing X.509 key.
892 * Fix parsing of dates >= year 2038.
895 Noteworthy changes in version 1.3.1 (2011-06-16)
896 ------------------------------------------------
898 * Ported to Windows CE.
900 * Detect GPG versions not supporting ---passwd.
902 * Interface changes relative to the 1.3.0 release:
903 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
904 GPGME_EXPORT_MODE_MINIMAL NEW
905 GPGME_STATUS_SUCCESS NEW
906 gpgme_err_code_from_syserror NEW
907 gpgme_err_set_errno NEW
908 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
909 gpgme_error_from_syserror NEW
910 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
913 Noteworthy changes in version 1.3.0 (2010-01-11)
914 ------------------------------------------------
916 * GPGME does not come with an internal libassuan version anymore.
917 The external libassuan 1.1.0 release or later is required. For
918 application programmers on systems that can resolve inter-library
919 dependencies at runtime, this is a transparent change.
921 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
923 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
925 * New API to change the passphrase of a key.
927 * Interface changes relative to the 1.2.0 release:
928 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
929 GPGME_STATUS_INV_SGNR NEW.
930 GPGME_STATUS_NO_SGNR NEW.
931 GPGME_PROTOCOL_G13 NEW.
932 gpgme_op_g13_mount NEW.
933 gpgme_g13_result_t NEW.
936 gpgme_op_passwd_start NEW.
938 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
941 Noteworthy changes in version 1.2.0 (2009-06-18)
942 ------------------------------------------------
944 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
947 * gpgme_new will fail if gpgme_check_version was not called, or a
948 selftest failed (for example, if -mms-bitfields was not used on
951 * New functions gpgme_io_read and gpgme_io_write for use with
952 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
954 * New functions gpgme_result_ref and gpgme_result_unref to detach
955 result structures from a context.
957 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
958 that allow to specify exported keys through gpgme_key_t objects
961 * New mode of operation gpgme_export_mode_t that allows exporting
964 * Interface changes relative to the 1.1.7 release:
965 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
966 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
967 GPGME_PROTOCOL_ASSUAN NEW.
968 gpgme_assuan_data_cb_t NEW.
969 gpgme_assuan_inquire_cb_t NEW.
970 gpgme_assuan_status_cb_t NEW.
971 gpgme_op_assuan_transact_start NEW.
972 gpgme_op_assuan_transact NEW.
973 gpgme_op_assuan_result NEW.
974 gpgme_op_import_keys NEW.
975 gpgme_op_import_keys_start NEW.
976 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
977 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
978 gpgme_check_version CHANGED: Is now a macro.
979 gpgme_new EXTENDED: More failure codes.
982 gpgme_result_ref NEW.
983 gpgme_result_unref NEW.
984 gpgme_export_mode_t NEW.
985 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
986 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
987 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
988 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
989 gpgme_op_export_keys_start NEW.
990 gpgme_op_export_keys NEW.
991 GPGME_DATA_ENCODING_URL NEW.
992 GPGME_DATA_ENCODING_URL0 NEW.
993 GPGME_DATA_ENCODING_URLESC NEW.
994 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
997 Noteworthy changes in version 1.1.8 (2008-12-08)
998 ------------------------------------------------
1000 * SIGPIPE is now again ignored as described in the manual. Fixes
1001 regression introduced with 1.1.6.
1004 Noteworthy changes in version 1.1.7 (2008-10-17)
1005 ------------------------------------------------
1007 * Using GPGME_KEYLIST_MODE_LOCAL combined with
1008 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
1009 --locate-keys feature of gpg (>= 2.0.10).
1011 * The encoding of gpgme_data_t objects can affect the output encoding
1012 of export, sign and encrypt operations now (the same operations
1013 that are also affected by the ASCII mode switch). We believe this
1014 change in the ABI is innocent enough not to break existing
1015 applications (it only affects the S/MIME backend on certain
1018 * The reference manual now includes the specification of "The GnuPG
1019 UI Server protocol".
1021 * A new function gpgme_cancel_async can be used to asynchronously
1022 cancel any pending operation at any time, from any thread.
1024 * Interface changes relative to the 1.1.6 release:
1025 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1026 gpgme_op_encrypt CHANGED: Output encoding can affect result.
1027 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
1028 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
1029 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
1030 gpgme_op_sign CHANGED: Output encoding can affect result.
1031 gpgme_op_sign_start CHANGED: Output encoding can affect result.
1032 gpgme_op_export CHANGED: Output encoding can affect result.
1033 gpgme_op_export_start CHANGED: Output encoding can affect result.
1034 gpgme_op_export_ext CHANGED: Output encoding can affect result.
1035 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
1036 gpgme_cancel_async NEW
1037 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1040 Noteworthy changes in version 1.1.6 (2008-01-04)
1041 ------------------------------------------------
1043 * Bug fixes for for W32.
1045 * A new, experimental (and thus undocumented and potentially
1046 unstable) interface for accessing gpg-conf through GPGME has been
1049 * Interface changes relative to the 1.1.1 release:
1050 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1051 gpgme_signature_t EXTENDED: New field chain_model.
1052 gpgme_op_getauditlog_start NEW.
1053 gpgme_op_getauditlog NEW.
1054 GPGME_AUDITLOG_HTML NEW.
1055 GPGME_AUDITLOG_WITH_HELP NEW.
1056 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1059 Noteworthy changes in version 1.1.5 (2007-07-09)
1060 ------------------------------------------------
1062 * Bug and portability fixes (mainly for W32).
1065 Noteworthy changes in version 1.1.4 (2007-03-05)
1066 ------------------------------------------------
1068 * Detect and bail out on double plaintext messages. This is required
1069 so that applications can properly detect the signed parts of a
1070 message. Actual there is now a double protection as GnuPG 1.4.7
1071 will detect this case too.
1074 Noteworthy changes in version 1.1.3 (2007-01-29)
1075 ------------------------------------------------
1077 * Fixed a memory leak in gpgme_data_release_and_get_mem.
1079 * Fixed a bug in Windows command line quoting.
1082 Noteworthy changes in version 1.1.2 (2006-03-02)
1083 ------------------------------------------------
1085 * Fixed a bug in the W32 glib backend.
1088 Noteworthy changes in version 1.1.1 (2006-02-23)
1089 ------------------------------------------------
1091 * Fixed a bug in that the fingerprints of subkeys are not available.
1093 * Clarified usage of the SECRET flag in key listings. It is now
1094 reset for stub keys.
1096 * Reading signature notations and policy URLs on key signatures is
1097 supported. They can be found in the new field notations of the
1098 gpgme_key_sig_t structure. This has to be enabled with the keylist
1099 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
1101 * A new gpgme_free() function solves the problem of using different
1102 allocators in a single program. This function should now be used
1103 instead calling free() to release the buffer returned by
1104 gpgme_data_release_and_get_mem. It is recommended that you always
1105 do this, but it is only necessary on certain platforms, so backwards
1106 compatibility is provided. In other words: If free() worked for
1107 you before, it will keep working.
1109 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
1110 They are analyzed by the verify handlers and made available in the
1111 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
1113 * Interface changes relative to the 1.1.0 release:
1114 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1115 gpgme_key_sig_t EXTENDED: New field notations.
1116 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
1118 GPGME_STATUS_PKA_TRUST_BAD NEW
1119 GPGME_STATUS_PKA_TRUST_GOOD NEW
1120 gpgme_signature_t EXTENDED: New field pka_trust.
1121 gpgme_signature_t EXTENDED: New field pka_address.
1122 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1125 Noteworthy changes in version 1.1.0 (2005-10-01)
1126 ------------------------------------------------
1128 * You can now configure the backend engine file name and home
1129 directory to be used, as default and per context.
1131 * Information about the recipients of an encrypted text is now
1132 available at decryption time.
1134 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
1135 and verify handlers, the information about the plaintext filename,
1136 if available is made available in the new field file_name of the
1137 respective result structure.
1139 * The code for "automagically detecting the thread library" has been
1140 removed from libgpgme. It is deprecated since version 0.4.3.
1141 Since then, you had to link against libgpgme-pthread for
1142 applications using pthread and libgpgme-pth for applications using
1145 The code was removed because it caused compilation problems on
1146 systems where the pthread.h header from GNU Pth is available in
1147 addition to the system header (FreeBSD 6 and later for example).
1149 * "./autogen.sh --build-w32" does now build gpgme.dll.
1151 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
1152 delimiter. The standard install directory is used when locating
1153 gpg or gpgsm before finally falling back to the hardwired name.
1155 * There is a new flag for keys and subkeys, is_qualified, which
1156 indicates if a key can be used for qualified signatures according
1157 to local government regulations.
1159 * You can associate a filename with a data object using the new
1160 function gpgme_data_set_file_name(). This filename will be stored
1161 in the output when encrypting or signing the data and will be
1162 returned when decrypting or verifying the output data.
1164 * You can now set notation data at signature creation with the new
1165 function gpgme_sig_notation_add().
1167 * Interface changes relative to the 1.0.3 release:
1168 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1169 gpgme_set_engine_info NEW
1170 gpgme_ctx_get_engine_info NEW
1171 gpgme_ctx_set_engine_info NEW
1172 gpgme_recipient_t NEW
1173 gpgme_decrypt_result_t EXTENDED: New field recipients.
1174 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
1175 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
1176 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
1177 GPGME_STATUS_PLAINTEXT NEW
1178 gpgme_key_t EXTENDED: New field is_qualified.
1179 gpgme_subkey_t EXTENDED: New field is_qualified.
1180 gpgme_data_get_file_name NEW
1181 gpgme_data_set_file_name NEW
1182 gpgme_sig_notation_flags_t NEW
1183 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
1184 GPGME_SIG_NOTATAION_CRITICAL NEW
1185 gpgme_sig_notation_clear NEW
1186 gpgme_sig_notation_add NEW
1187 gpgme_sig_notation_get NEW
1188 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1191 Noteworthy changes in version 1.0.3 (2005-06-20)
1192 ------------------------------------------------
1194 * Previousy, GPGME would use a default "include certs" of 1. This
1195 has been changed. Now GPGME will use the crypto backend engines
1196 default unless you set the value with gpgme_set_include_certs()
1197 explicitly. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
1198 as a value to explicitly request the new default behaviour.
1200 Because the default changes, this is a slight change of the API
1201 semantics. We consider it to be a bug fix.
1203 * A bug which made GPGME hang has been fixed. If you have
1204 experienced hanging before, please try out this version and let me
1205 know if you still experience hanging problems.
1207 * Interface changes relative to the 0.9.0 release:
1208 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1209 gpgme_set_include_certs CHANGED DEFAULT
1210 GPGME_INCLUDE_CERTS_DEFAULT NEW
1211 GPGME_STATUS_SIG_SUBPACKET NEW
1212 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
1213 GPGME_STATUS_SC_OP_FAILURE NEW
1214 GPGME_STATUS_SC_OP_SUCCESS NEW
1215 GPGME_STATUS_CARDCTRL NEW
1216 GPGME_STATUS_BACKUP_KEY_CREATED NEW
1217 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1220 Noteworthy changes in version 1.0.2 (2004-12-28)
1221 ------------------------------------------------
1223 * Changed the license of the library to the GNU Lesser General Public
1224 License (LGPL), version 2.1 or later.
1227 Noteworthy changes in version 1.0.1 (2004-10-22)
1228 ------------------------------------------------
1233 Noteworthy changes in version 1.0.0 (2004-09-30)
1234 ------------------------------------------------
1236 * Version 1.0.0! We are proud to present you with a thoroughly
1237 tested and stable version of the GPGME library. A big Thank You!
1238 to all the people who made this possible.
1240 The development will be branched into a stable 1.x.y series and the
1243 * The gpgme.m4 macro supports checking the API version. Just prepend
1244 it to the required version string, separated by a colon. For
1245 example, this release has the version "1:1.0.0". The last release
1246 to which this version is (mostly) ABI compatible is "1:0.4.2",
1247 which is the default required version.
1250 Noteworthy changes in version 0.9.0 (2004-06-08)
1251 ------------------------------------------------
1253 * The type gpgme_key_t has now a new field keylist_mode that contains
1254 the keylist mode that was active at the time the key was retrieved.
1256 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
1257 that contains a flag indicating that the key should not have been
1258 used for encryption.
1260 * Verifying a signature of a revoked key gives the correct result now
1261 (GPG_ERR_CERT_REVOKED error code).
1263 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
1264 verify operations still allows you to look at the signature
1265 verification result.
1267 * Clarified that patterns in keylisting operations have an upper
1268 limit, and thus are not suited to list many keys at once by their
1269 fingerprint. Also improve the error message if the pattern is too
1270 long for the CMS protocol to handle.
1272 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1273 gpgme_key_t EXTENDED: New field keylist_mode.
1274 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
1275 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1278 Noteworthy changes in version 0.4.7 (2004-04-29)
1279 ------------------------------------------------
1281 * Correctly initialize the fields expired, revoked, invalid, and
1282 disabled in the gpgme_key_t structures.
1284 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
1285 accidentally of type int instead unsigned int.
1287 * Interface changes relative to the 0.4.5 release:
1288 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1289 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
1290 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1292 Noteworthy changes in version 0.4.6 (2004-04-06)
1293 ------------------------------------------------
1298 Noteworthy changes in version 0.4.5 (2004-03-07)
1299 ------------------------------------------------
1301 * GPGME is now compiled with LFS (large file support) by default.
1302 This means that _all_ programs using GPGME must be compiled with
1303 LFS support enabled by default. You can do this easily with
1304 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
1305 without autoconf by defining the preprocessor symbol
1306 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
1307 the C compiler command line, or by defining this preprocessor
1308 symbol before including any system header files). For more
1309 details, read the section on LFS in the manual.
1311 Up to now, it was undocumented that GPGME was not using LFS.
1312 But the public interfaces use off_t, and file descriptors are
1313 exchanged between the application and GPGME. This was an oversight,
1314 and bound to cause troubles in the future.
1316 Writing GPGME as a dual mode library that seamlessly supports LFS
1317 while keeping backwards compatibility is possible, but does not
1318 solve the problem: Many applications already expect GPGME to have
1319 LFS (they are compiled with off_t being a 64bit value). This is true
1320 in particular for the popular Gtk+ and Qt programs.
1322 So, although this is an ABI (but not an API) break, we will not
1323 change the library version to reflect that. Because the interfaces
1324 affected are probably not used yet in any GPGME 0.4 based
1325 application, we don't expect any real failures from this change.
1326 In fact, applications already using LFS will have some subtle bugs
1329 However, if you encounter an application using GPGME 0.4.x that
1330 does _not_ use LFS by default (off_t is a 32bit value), _and_
1331 uses at least one of the functions gpgme_data_seek,
1332 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
1333 gpgme_data_new_from_cbs, then indeed this library will be ABI
1334 incompatible with the program. As said above, we don't believe
1335 such a program exists. If we are in error, then you have two
1336 options: As a quick hack, you can configure GPGME with the
1337 --disable-largefile option. This will revert the change, and GPGME
1338 will not use LFS. However, GPGME will be incompatible with
1339 programs that expect GPGME to use LFS. All applications are
1340 required to use LFS when using GPGME, so this is only good as a
1341 temporary local work-around.
1343 The other option is to change the versioning of the library and
1344 recompile all applications. We have reserved a special version of
1345 the library for that, so you can do that without expecting a
1346 version clash in the future. Furthermore, everyone who does this
1347 will agree on the version to use (this is important for
1348 distribution makers). Read the comment in configure.ac (before
1349 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
1350 blindly: As stated above, we think it is unlikely this measure is
1351 needed. Still, it is there if necessary. If in doubt, contact us
1352 and we will give our advise for your specific situation.
1354 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
1357 * New interface gpgme_cancel() that can be used to cancel
1358 asynchronous operations.
1360 * Interface changes relative to the 0.4.4 release:
1361 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1362 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
1363 gpgme_data_seek CHANGED: off_t is now a largefile type.
1364 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
1365 GPGME_KEYLIST_MODE_VALIDATE NEW
1367 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1369 Noteworthy changes in version 0.4.4 (2004-01-12)
1370 ------------------------------------------------
1372 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
1373 been renamed to "sig_class", to avoid clash with C++ compilers. In
1374 the C API, the old name "class" has been preserved for backwards
1375 compatibility, but is deprecated.
1377 * Interface changes relative to the 0.4.3 release:
1378 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1379 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
1380 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
1381 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1383 Noteworthy changes in version 0.4.3 (2003-10-06)
1384 ------------------------------------------------
1386 * libgpgme should not be used for threaded programs anymore. This
1387 never worked reliably in all cases, because you had to
1388 be careful about the linking order and libtool wouldn't do that for
1389 you automatically. Instead, now you have to link against
1390 libgpgme-pthread for applications using pthread and libgpgme-pth for
1391 applications using GNU Pth.
1393 The old code for automagically detecting the thread library is
1394 still part of libgpgme, but it is DEPRECATED.
1396 * There are new automake macros AM_PATH_GPGME_PTH and
1397 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
1398 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
1399 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
1400 variables of course also include the configuration for the thread
1401 package itself. Alternatively, use libtool.
1403 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
1406 * gpgme-config doesn't support setting the prefix or exec prefix
1407 anymore. I don't think it ever worked correctly, and it seems to
1410 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
1411 provided was not unique, instead returning the first matching key.
1413 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
1414 that indicates if the key can be used for authentication.
1416 * gpgme_signature_t's status field is now correctly set to an error
1417 with error code GPG_ERR_NO_PUBKEY if public key is not found.
1419 * gpgme_new_signature_t's class field is now an unsigned int, rather
1420 than an unsigned long (the old class field is preserved for
1421 backwards compatibility).
1423 * A new function gpgme_set_locale() is provided to allow configuring
1424 the locale for the crypto backend. This is necessary for text
1425 terminals so that programs like the pinentry can be started with
1426 the right locale settings for the terminal the application is running
1427 on, in case the terminal has different settings than the system
1428 default (for example, if it is a remote terminal). You are highly
1429 recommended to call the following functions directly after
1430 gpgme_check_version:
1434 setlocale (LC_ALL, "");
1435 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
1436 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
1438 GPGME can not do this for you, as setlocale is not thread safe, and
1439 there is no alternative.
1441 * The signal action for SIGPIPE is now set to SIG_IGN by
1442 gpgme_check_version, instead the first time a crypto engine is
1443 started (which is not well defined).
1445 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
1446 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
1447 to CRC24RFC2440. For now, these strings can be used as the MIC
1448 parameter for PGP/MIME (if appropriately modified).
1450 * Interface changes relative to the 0.4.2 release:
1451 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1452 gpgme_strerror_t NEW
1453 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
1454 gpgme_key_t EXTENDED: New field can_authenticate.
1455 gpgme_subkey_t EXTENDED: New field can_authenticate.
1456 gpgme_new_signature_t CHANGED: New type for class field.
1457 gpgme_set_locale NEW
1458 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
1459 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1461 Noteworthy changes in version 0.4.2 (2003-07-30)
1462 ------------------------------------------------
1464 * Allow gpg-error to be in non-standard place when linking the test suite.
1466 * Configure will fail now if gpg-error can not be found.
1468 * Fixed initialized memory backed data objects for writing, which
1469 caused the test program to crash (but only on Mac OS, surprisingly).
1471 * Eliminate use of C99 constructs.
1473 * Small improvements to the manual.
1476 Noteworthy changes in version 0.4.1 (2003-06-06)
1477 ------------------------------------------------
1479 This is the release that 0.4.0 should have been. There are many
1480 interface changes, please see below for the details. The changes are
1481 sometimes the result of new functionality, but more often express a
1482 paradigm shift. Others are an overdue cleanup to get GPGME in line
1483 with the GNU coding standards and to make the interface more
1484 self-consistent. Here is an overview on the changes:
1486 All types have been renamed to conform to the GNU coding standards,
1487 most of the time by keeping the whole name in lowercase and inserting
1488 underscores between words.
1490 All operations consistently only accept input parameters in their
1491 invocation function, and return only an error code directly. Further
1492 information about the result of the operation has to be retrieved
1493 afterwards by calling one of the result functions. This unifies the
1494 synchronous and the asynchronous interface.
1496 The error values have been completely replaced by a more
1497 sophisticated model that allows GPGME to transparently and accurately
1498 report all errors from the other GnuPG components, regardless of
1499 process boundaries. This is achieved by using the library
1500 libgpg-errors, which is shared by all GnuPG components. This library
1501 is now required for GPGME.
1503 The results of all operations are now provided by pointers to C
1504 structs rather than by XML structs or in other ways.
1506 Objects which used to be opaque (for example a key) are now pointers
1507 to accessible structs, so no accessor functions are necessary.
1509 Backward compatibility is provided where it was possible without too
1510 much effort and did not collide with the overall sanitization effort.
1511 However, this is only for ease of transition. NO DEPRECATED FUNCTION
1512 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
1513 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
1514 Recommendations how to replace deprecated or removed functionality
1515 can be found within the description of each change.
1517 What follows are all changes to the interface and behaviour of GPGME
1520 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
1521 deprecated attributes will warn about use of obsolete functions and
1522 type definitions. You can suppress these warnings by passing
1523 -Wno-deprecated-declarations to the gcc command.
1525 * The following types have been renamed. The old types are still
1526 available as aliases, but they are deprecated now:
1528 GpgmeCtx gpgme_ctx_t
1529 GpgmeData gpgme_data_t
1530 GpgmeError gpgme_error_t
1531 GpgmeDataEncoding gpgme_data_encoding_t
1532 GpgmeSigStat gpgme_sig_stat_t
1533 GpgmeSigMode gpgme_sig_mode_t
1534 GpgmeAttr gpgme_attr_t
1535 GpgmeValidity gpgme_validity_t
1536 GpgmeProtocol gpgme_protocol_t
1537 GpgmeKey gpgme_key_t
1538 GpgmePassphraseCb gpgme_passphrase_cb_t
1539 GpgmeProgressCb gpgme_progress_cb_t
1540 GpgmeIOCb gpgme_io_cb_t
1541 GpgmeRegisterIOCb gpgme_register_io_cb_t
1542 GpgmeRemoveIOCb gpgme_remove_io_cb_t
1543 GpgmeEventIO gpgme_event_io_t
1544 GpgmeEventIOCb gpgme_event_io_cb_t
1545 GpgmeIOCbs gpgme_io_cbs
1546 GpgmeDataReadCb gpgme_data_read_cb_t
1547 GpgmeDataWriteCb gpgme_data_write_cb_t
1548 GpgmeDataSeekCb gpgme_data_seek_cb_t
1549 GpgmeDataReleaseCb gpgme_data_release_cb_t
1550 GpgmeDataCbs gpgme_data_cbs_t
1551 GpgmeTrustItem gpgme_trust_item_t
1552 GpgmeStatusCode gpgme_status_code_t
1554 * gpgme_error_t is now identical to gpg_error_t, the error type
1555 provided by libgpg-error. More about using libgpg-error with GPGME
1556 can be found in the manual. All error symbols have been removed!
1558 * All functions and types in libgpg-error have been wrapped in GPGME.
1559 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1560 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1561 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1562 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1565 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1567 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1568 for encrypt, sign, encrypt-sign, decrypt, verify, and
1569 decrypt-verify operations. For verify operations on detached
1570 signatures, the progress callback is invoked for both the detached
1571 signature and the plaintext message, though.
1573 * gpgme_passphrase_cb_t has been changed to not provide a complete
1574 description, but the UID hint, passphrase info and a flag
1575 indicating if this is a repeated attempt individually, so the user
1576 can compose his own description from this information.
1578 The passphrase is not returned as a C string, but must be written
1579 to a file descriptor directly. This allows for secure passphrase
1582 The return type has been changed to gpgme_error_t value. This
1583 allowed to remove the gpgme_cancel function; just return
1584 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1586 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1587 The user is expected to write the response to the file descriptor,
1588 followed by a newline.
1590 * The recipients interface has been removed. Instead, you use
1591 NULL-terminated lists of keys for specifying the recipients of an
1592 encryption operation. Use the new encryption flag
1593 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1594 the keys (but note that in general this is not a good idea).
1596 This change has been made to the prototypes of gpgme_op_encrypt,
1597 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1598 gpgme_op_encrypt_sign_start.
1600 The export interface has been changed to use pattern strings like
1601 the keylist interface. Thus, new functions gpgme_op_export_ext and
1602 gpgme_op_export_ext_start have been added as well. Now the
1603 prototypes of gpgme_op_export_start and gpgme_op_export finally
1606 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1607 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1610 * gpgme_io_cb_t changed from a void function to a function returning
1611 a gpgme_error_t value. However, it will always return 0, so you
1612 can safely ignore the return value.
1614 * A new I/O callback event GPGME_EVENT_START has been added. The new
1615 requirement is that you must wait until this event until you are
1616 allowed to call the I/O callback handlers previously registered for
1617 this context operation. Calling I/O callback functions for this
1618 context operation before the start event happened is unsafe because
1619 it can lead to race conditions in a multi-threaded environment.
1621 * The idle function feature has been removed. It was not precisely
1622 defined in a multi-threaded environment and is obsoleted by the
1623 user I/O callback functions. If you still need a simple way to
1624 call something while waiting on one or multiple asynchronous
1625 operations to complete, don't set the HANG flag in gpgme_wait (note
1626 that this will return to your program more often than the idle
1629 * gpgme_wait can return NULL even if hang is true, if an error
1630 occurs. In that case *status contains the error code.
1632 * gpgme_get_engine_info was radically changed. Instead an XML
1633 string, an info structure of the new type gpgme_engine_info_t is
1634 returned. This makes it easier and more robust to evaluate the
1635 information in an application.
1637 * The new function gpgme_get_protocol_name can be used to convert a
1638 gpgme_protocol_t value into a string.
1640 * The status of a context operation is not checked anymore. Starting
1641 a new operation will silently cancel the previous one. Calling a
1642 function that requires you to have started an operation before without
1643 doing so is undefined.
1645 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1646 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1647 pointer to a structure which contains the fingerprint. This also
1648 works with gpgme_op_genkey_start. The structure also provides
1649 other information about the generated keys.
1654 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1656 printf ("%s\n", fpr);
1660 gpgme_genkey_result_t result;
1661 err = gpgme_op_genkey (ctx, NULL, NULL);
1664 result = gpgme_op_genkey_result (ctx);
1666 printf ("%s\n", result->fpr);
1669 * The new gpgme_op_import_result function provides detailed
1670 information about the result of an import operation in
1671 gpgme_import_result_t and gpgme_import_status_t objects.
1672 Thus, the gpgme_op_import_ext variant is deprecated.
1674 * The new gpgme_op_sign_result function provides detailed information
1675 about the result of a signing operation in gpgme_sign_result_t,
1676 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1678 * The new gpgme_op_encrypt_result function provides detailed
1679 information about the result of an encryption operation in
1680 a GpgmeEncryptResult object.
1682 * The new gpgme_op_decrypt_result function provides detailed
1683 information about the result of a decryption operation in
1684 a GpgmeDecryptResult object.
1686 * The new gpgme_op_verify_result function provides detailed
1687 information about the result of an verify operation in
1688 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1689 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1690 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1691 and gpgme_get_notation is removed.
1693 * GpgmeTrustItem objects have now directly accessible data, so the
1694 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1695 accessor functions are deprecated. Also, reference counting is
1696 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1697 (the gpgme_trust_item_release alias for the latter is deprecated).
1699 * Keys are not cached internally anymore, so the force_update argument
1700 to gpgme_get_key has been removed.
1702 * GpgmeKey objects have now directly accessible data so the
1703 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1704 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1705 functions are deprecated. Also, gpgme_key_release is now
1706 deprecated. The gpgme_key_get_as_xml function has been dropped.
1708 * Because all interfaces using attributes are deprecated, the
1709 GpgmeAttr data type is also deprecated.
1711 * The new gpgme_op_keylist_result function provides detailed
1712 information about the result of a key listing operation in
1713 a GpgmeKeyListResult object.
1715 * Now that each function comes with its own result retrieval
1716 interface, the generic gpgme_get_op_info interface is not useful
1717 anymore and dropped.
1719 * The type and mode of data objects is not available anymore.
1721 * Interface changes relative to the 0.4.0 release:
1722 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1723 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1724 GpgmeData DEPRECATED: Use gpgme_data_t.
1725 GpgmeError DEPRECATED: Use gpgme_error_t.
1726 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1727 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1728 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1729 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1730 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1731 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1732 GpgmeKey DEPRECATED: Use gpgme_key_t.
1733 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1734 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1735 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1736 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1737 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1738 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1739 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1740 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1741 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1742 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1743 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1744 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1745 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1746 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1747 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1750 gpgme_recipients_t NEW
1752 gpgme_data_encoding_t NEW
1753 gpgme_sig_stat_t NEW
1754 gpgme_sig_mode_t NEW
1756 gpgme_validity_t NEW
1757 gpgme_protocol_t NEW
1759 gpgme_passphrase_cb_t NEW
1760 gpgme_progress_cb_t NEW
1762 gpgme_register_io_cb_t NEW
1763 gpgme_remove_io_cb_t NEW
1764 gpgme_event_io_t NEW
1765 gpgme_event_io_cb_t NEW
1767 gpgme_data_read_cb_t NEW
1768 gpgme_data_write_cb_t NEW
1769 gpgme_data_seek_cb_t NEW
1770 gpgme_data_release_cb_t NEW
1771 gpgme_data_cbs_t NEW
1772 gpgme_trust_item_t NEW
1773 gpgme_status_code_t NEW
1774 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1775 gpgme_err_code_t NEW
1776 gpgme_err_source_t NEW
1778 gpgme_err_source NEW
1781 gpgme_error_from_errno NEW
1782 gpgme_err_make_from_errno NEW
1783 gpgme_err_code_from_errno NEW
1784 gpgme_err_code_to_errno NEW
1786 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1787 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1788 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1789 gpgme_edit_cb_t CHANGED: Write directly to FD.
1790 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1791 gpgme_op_verify CHANGED: Drop R_STAT argument.
1792 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1793 gpgme_wait CHANGED: Can return NULL even if hang is true.
1794 GpgmeIdleFunc REMOVED
1795 gpgme_register_idle REMOVED
1796 GpgmeRecipients REMOVED
1797 gpgme_recipients_new REMOVED
1798 gpgme_recipients_release REMOVED
1799 gpgme_recipients_add_name REMOVED
1800 gpgme_recipients_add_name_with_validity REMOVED
1801 gpgme_recipients_count REMOVED
1802 gpgme_recipients_enum_open REMOVED
1803 gpgme_recipients_enum_read REMOVED
1804 gpgme_recipients_enum_close REMOVED
1805 gpgme_encrypt_flags_t NEW
1806 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1807 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1808 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1809 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1810 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1811 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1812 gpgme_op_export CHANGED: User IDs passed as patterns.
1813 gpgme_op_export_ext_start NEW
1814 gpgme_op_export_ext NEW
1815 gpgme_keylist_mode_t NEW
1817 gpgme_engine_info_t NEW
1818 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1819 gpgme_get_protocol_name NEW
1820 gpgme_cancel REMOVED: Return error in callback directly.
1821 gpgme_op_genkey CHANGED: FPR argument dropped.
1822 gpgme_op_genkey_result NEW
1823 gpgme_genkey_result_t NEW
1824 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1825 gpgme_op_import_result NEW
1826 gpgme_import_status_t NEW
1827 gpgme_import_result_t NEW
1828 gpgme_pubkey_algo_t NEW
1829 gpgme_hash_algo_t NEW
1830 gpgme_invalid_key_t NEW
1831 gpgme_new_signature_t NEW
1832 gpgme_sign_result_t NEW
1833 gpgme_op_sign_result NEW
1834 gpgme_pubkey_algo_name NEW
1835 gpgme_hash_algo_name NEW
1836 gpgme_encrypt_result_t NEW
1837 gpgme_op_encrypt_result NEW
1838 gpgme_decrypt_result_t NEW
1839 gpgme_op_decrypt_result NEW
1840 gpgme_verify_result_t NEW
1841 gpgme_op_verify_result NEW
1842 gpgme_get_notation REMOVED: Access verify result directly instead.
1843 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1844 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1845 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1846 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1847 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1848 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1849 gpgme_trust_item_ref NEW
1850 gpgme_trust_item_unref NEW
1851 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1852 gpgme_trust_item_get_string_attr DEPRECATED
1853 gpgme_trust_item_get_ulong_attr DEPRECATED
1854 gpgme_get_key CHANGED: Removed force_update argument.
1858 gpgme_key_t CHANGED: Now has user accessible data members.
1859 gpgme_key_get_string_attr DEPRECATED
1860 gpgme_key_get_ulong_attr DEPRECATED
1861 gpgme_key_sig_get_string_attr DEPRECATED
1862 gpgme_key_sig_get_ulong_attr DEPRECATED
1863 gpgme_key_get_as_xml REMOVED
1864 gpgme_key_list_result_t NEW
1865 gpgme_op_keylist_result NEW
1866 gpgme_get_op_info REMOVED
1867 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1869 Noteworthy changes in version 0.4.0 (2002-12-23)
1870 ------------------------------------------------
1872 * Key generation returns the fingerprint of the generated key.
1874 * New convenience function gpgme_get_key.
1876 * Supports signatures of user IDs in keys via the new
1877 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1878 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1879 interfaces. The XML info about a key also includes the signatures
1882 * New data object interface, which is more flexible and transparent.
1884 * Interface changes relative to the 0.3.9 release:
1885 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1887 GpgmeDataWriteCb NEW
1889 GpgmeDataReleaseCb NEW
1891 gpgme_data_read CHANGED: Match read() closely.
1892 gpgme_data_write CHANGED: Match write() closely.
1894 gpgme_data_new_from_fd NEW
1895 gpgme_data_new_from_stream NEW
1896 gpgme_data_new_from_cbs NEW
1897 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1898 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1899 gpgme_data_get_type REMOVED: No replacement.
1900 gpgme_op_verify CHANGED: Take different data objects for
1901 signed text and plain text.
1902 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1903 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1904 gpgme_op_genkey CHANGED: New parameter FPR.
1905 GPGME_KEYLIST_MODE_SIGS NEW
1906 gpgme_key_sig_get_string_attr NEW
1907 gpgme_key_sig_get_ulong_attr NEW
1909 GPGME_ATTR_SIG_CLASS NEW
1910 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1912 Noteworthy changes in version 0.3.16 (2003-11-19)
1913 -------------------------------------------------
1915 * Compatibility fixes for GnuPG 1.9.x
1917 Noteworthy changes in version 0.3.15 (2003-02-18)
1918 -------------------------------------------------
1920 * The progress status is sent via the progress callbacks in
1923 * Bug fix for signing operations with explicit signer settings for
1926 Noteworthy changes in version 0.3.14 (2002-12-04)
1927 -------------------------------------------------
1929 * GPGME-Plug is now in its own package "cryptplug".
1931 * Workaround for a setlocale problem. Fixed a segv related to not
1932 correctly as closed marked file descriptors.
1934 Noteworthy changes in version 0.3.13 (2002-11-20)
1935 -------------------------------------------------
1937 * Release due to changes in gpgmeplug.
1939 Noteworthy changes in version 0.3.12 (2002-10-15)
1940 -------------------------------------------------
1942 * Fixed some bux with key listings.
1944 * The development has been branched to clean up some API issues.
1945 This 0.3 series will be kept for compatibility reasons; so do don't
1946 expect new features.
1948 Noteworthy changes in version 0.3.11 (2002-09-20)
1949 -------------------------------------------------
1953 Noteworthy changes in version 0.3.10 (2002-09-02)
1954 -------------------------------------------------
1956 * Setting the signing keys for the CMS protocol does now work.
1958 * The signers setting is honoured by gpgme_op_edit.
1960 Noteworthy changes in version 0.3.9 (2002-08-21)
1961 ------------------------------------------------
1963 * A spec file for creating RPMs has been added.
1965 * An experimental interface to GnuPG's --edit-key functionality is
1966 introduced, see gpgme_op_edit.
1968 * The new gpgme_import_ext function provides a convenient access to
1969 the number of processed keys.
1971 * Interface changes relative to the 0.3.8 release:
1972 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1975 gpgme_op_edit_start NEW
1977 gpgme_op_import_ext NEW
1978 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1980 Noteworthy changes in version 0.3.8 (2002-06-25)
1981 ------------------------------------------------
1983 * It is possible to use an outside event loop for the I/O to the
1984 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1986 * Interface changes relative to the 0.3.6 release:
1987 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1989 GpgmeRegisterIOCb NEW
1993 struct GpgmeIOCbs NEW
1994 gpgme_set_io_cbs NEW
1995 gpgme_get_io_cbs NEW
1996 GPGME_ATTR_ERRTOK NEW
1997 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1999 Noteworthy changes in version 0.3.7 (2002-06-04)
2000 ------------------------------------------------
2002 * GPGME_ATTR_OTRUST is implemented now.
2004 * A first step toward thread safeness has been achieved, see the
2005 documentation for details. Supported thread libraries are pthread
2008 Noteworthy changes in version 0.3.6 (2002-05-03)
2009 ------------------------------------------------
2011 * All error output of the gpgsm backend is send to the bit bucket.
2013 * The signature verification functions are extended. Instead of
2014 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
2015 expired signatures. 2 new functions may be used to retrieve more
2016 detailed information like the signature expiration time and a
2017 validity information of the key without an extra key looking.
2019 * The current passphrase callback and progress meter callback can be
2020 retrieved with the new functions gpgme_get_passphrase_cb and
2021 gpgme_get_progress_cb respectively.
2023 * Interface changes relative to the 0.3.5 release:
2024 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2025 gpgme_get_passphrase_cb NEW
2026 gpgme_get_progress_cb NEW
2027 GpgmeDataEncoding NEW
2028 gpgme_data_set_encoding NEW
2029 gpgme_data_get_encoding NEW
2030 GPGME_SIG_STAT_GOOD_EXP NEW
2031 GPGME_SIG_STAT_GOOD_EXPKEY NEW
2032 gpgme_op_verify CHANGED: Returns more status codes.
2033 GPGME_ATTR_SIG_STATUS NEW
2034 gpgme_get_sig_string_attr NEW
2035 gpgme_get_sig_ulong_attr NEW
2036 gpgme_get_protocol NEW
2037 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2039 Noteworthy changes in version 0.3.5 (2002-04-01)
2040 ------------------------------------------------
2042 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
2043 case, symmetric encryption is performed. Note that this requires a
2044 passphrase from the user.
2046 * More information is returned for X.509 certificates.
2048 * Interface changes relative to the 0.3.4 release:
2049 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2050 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
2051 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2053 Noteworthy changes in version 0.3.4 (2002-03-04)
2054 ------------------------------------------------
2056 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
2057 some recipients have been invalid, whereas earlier versions
2058 succeeded in this case. The plaintext is still encrypted for all valid
2059 recipients, so the application might take this error as a hint that
2060 the ciphertext is not usable for all requested recipients.
2061 Information about invalid recipients is available with gpgme_get_op_info.
2063 * gpgme_op_verify now allows to pass an uninitialized data object as
2064 its plaintext argument to check for normal and cleartext
2065 signatures. The plaintext is then returned in the data object.
2067 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
2068 to set and get the number of certifications to include in S/MIME
2071 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
2072 to encrypt and sign a message in a combined operation.
2074 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
2076 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
2078 * Interface changes relative to the 0.3.3 release:
2079 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2080 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
2081 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
2082 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
2083 gpgme_set_include_certs NEW
2084 gpgme_get_include_certs NEW
2085 gpgme_op_encrypt_sign NEW
2086 gpgme_op_encrypt_sign_start NEW
2087 gpgme_op_keylist_ext_start NEW
2088 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2090 Noteworthy changes in version 0.3.3 (2002-02-12)
2091 ------------------------------------------------
2093 * Fix the Makefile in jnlib.
2095 * Fix the test suite (hopefully). It should clean up all its state
2096 with `make check' now.
2099 Noteworthy changes in version 0.3.2 (2002-02-10)
2100 ------------------------------------------------
2102 * Remove erroneous dependency on libgcrypt in jnlib.
2105 Noteworthy changes in version 0.3.1 (2002-02-09)
2106 ------------------------------------------------
2108 * There is a Texinfo manual documenting the API.
2110 * The gpgme_set_keylist_mode function returns an error, and changed
2111 its meaning. It is no longer usable to select between normal and
2112 fast mode (newer versions of GnuPG will always be fast), but
2113 selects between local keyring, remote keyserver, or both.
2114 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
2115 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
2116 current setting, a function gpgme_get_keylist_mode was added to
2117 retrieve the current mode.
2119 * gpgme_wait accepts a new argument STATUS to return the error status
2120 of the operation on the context. Its definition is closer to
2121 waitpid() now than before.
2123 * The LENGTH argument to gpgme_data_new_from_filepart changed its
2124 type from off_t to the unsigned size_t.
2126 * The R_HD argument to the GpgmePassphraseCb type changed its type
2127 from void* to void**.
2129 * New interface gpgme_op_trustlist_end() to match
2130 gpgme_op_keylist_end().
2132 * The CryptPlug modules have been renamed to gpgme-openpgp and
2133 gpgme-smime, and they are installed in pkglibdir by `make install'.
2135 * An idle function can be registered with gpgme_register_idle().
2137 * The GpgSM backend supports key generation with gpgme_op_genkey().
2139 * Interface changes relative to the 0.3.0 release:
2140 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2141 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
2142 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
2143 gpgme_wait CHANGED: New argument STATUS.
2144 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
2145 The function has a new meaning!
2146 gpgme_get_keylist_mode NEW
2147 GPGME_KEYLIST_MODE_LOCAL NEW
2148 GPGME_KEYLIST_MODE_EXTERN NEW
2149 gpgme_op_trustlist_next NEW
2151 gpgme_register_idle NEW
2152 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2154 Noteworthy changes in version 0.3.0 (2001-12-19)
2155 ------------------------------------------------
2157 * New interface gpgme_set_protocol() to set the protocol and thus the
2158 crypto engine to be used by the context. Currently, the OpenPGP
2159 and the CMS protocols are supported. They are specified by the new
2160 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
2161 A new context uses the OpenPGP engine by default.
2163 * gpgme_get_engine_info() returns information for all crypto engines
2164 compiled into the library. The XML format has changed. To
2165 reliably get the version of a crypto engine, the <version> tag
2166 after the appropriate <protocol> tag has to be looked for.
2168 * New interface gpgme_engine_check_version(), obsoleting
2169 gpgme_check_engine(). Check the version of all engines you are
2170 supporting in your software.
2172 * GpgmeKey lists the user ids in the order as they are returned by
2173 GnuPG, first the primary key with index 0, then the sub-user ids.
2175 * New operation gpgme_op_decrypt_verify() to decrypt and verify
2176 signatures simultaneously.
2178 * The new interface gpgme_op_keylist_end() terminates a pending
2179 keylist operation. A keylist operation is also terminated when
2180 gpgme_op_keylist_next() returns GPGME_EOF.
2182 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
2183 cross-compiled, or even compiled without support for GnuPG
2186 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
2187 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
2188 in the path, but it can also be compiled without support for GpgSM
2189 (`--without-gpgsm').
2191 * CryptPlug modules for GPGME are included and can be enabled at
2192 configure time (`--enable-gpgmeplug'). There is one module which
2193 uses the GnuPG engine (`gpgmeplug') and one module which uses the
2194 GpgSM engine (`gpgsmplug').
2196 * Interface changes relative to the latest 0.2.x release:
2197 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2198 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
2199 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
2200 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
2201 gpgme_get_engine_info CHANGED: New format, extended content.
2202 gpgme_engine_check_version NEW
2203 gpgme_decrypt_verify_start NEW
2204 gpgme_decrypt_verify NEW
2205 gpgme_op_keylist_next NEW
2206 gpgme_set_protocol NEW
2207 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2210 Noteworthy changes in version 0.2.3 (2001-09-17)
2211 ------------------------------------------------
2213 * New function gpgme_get_op_info which can be used to get the micalg
2214 parameter needed for MOSS.
2216 * New functions gpgme_get_armor and gpgme_get_textmode.
2218 * The usual bug fixes and some minor functionality improvements.
2220 * Added a simple encryption component for MS-Windows; however the
2221 build procedure might have some problems.
2224 Noteworthy changes in version 0.2.2 (2001-06-12)
2225 ------------------------------------------------
2227 * Implemented a key cache.
2229 * Fixed a race condition under W32 and some other bug fixes.
2232 Noteworthy changes in version 0.2.1 (2001-04-02)
2233 ------------------------------------------------
2235 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
2237 * Handle GnuPG's new key capabilities output and support revocation
2240 * Made the W32 support more robust.
2243 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
2246 This file is free software; as a special exception the author gives
2247 unlimited permission to copy and/or distribute it, with or without
2248 modifications, as long as this notice is preserved.
2250 This file is distributed in the hope that it will be useful, but
2251 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
2252 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.