1 Noteworthy changes in version 1.11.0 (2018-04-18)
2 -------------------------------------------------
4 * New encryption API to support direct key specification including
5 hidden recipients option and taking keys from a file. This also
6 allows to enforce the use of a subkey.
8 * New encryption flag for the new API to enforce the use of plain
9 mail addresses (addr-spec).
11 * The import API can now tell whether v3 keys are skipped. These old
12 and basically broken keys are not anymore supported by GnuPG 2.1.
14 * The decrypt and verify API will now return the MIME flag as
15 specified by RFC-4880bis.
17 * The offline mode now has an effect on gpg by disabling all network
20 * A failed OpenPGP verification how returns the fingerprint of the
21 intended key if a recent gpg version was used for signature
24 * New tool gpgme-json as native messaging server for web browsers.
25 As of now public key encryption and decryption is supported.
26 Requires Libgpg-error 1.29.
28 * New context flag "request-origin" which has an effect when used
29 with GnuPG 2.2.6 or later.
31 * New context flag "no-symkey-cache" which has an effect when used
32 with GnuPG 2.2.7 or later.
34 * New convenience constant GPGME_KEYLIST_MODE_LOCATE.
36 * Improved the Python documentation.
38 * Fixed a potential regression with GnuPG 2.2.6 or later.
40 * Fixed a crash in the Python bindings on 32 bit platforms. [#3892]
42 * Various minor fixes.
44 * Interface changes relative to the 1.10.0 release:
45 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
46 gpgme_op_encrypt_ext NEW.
47 gpgme_op_encrypt_ext_start NEW.
48 gpgme_op_encrypt_sign_ext NEW.
49 gpgme_op_encrypt_sign_ext_start NEW.
50 GPGME_ENCRYPT_WANT_ADDRESS NEW.
51 GPGME_KEYLIST_MODE_LOCATE NEW.
52 gpgme_import_result_t EXTENDED: New field 'skipped_v3_keys'.
53 gpgme_decrypt_result_t EXTENDED: New field 'symkey_algo'.
54 gpgme_decrypt_result_t EXTENDED: New field 'is_mime'.
55 gpgme_verify_result_t EXTENDED: New field 'is_mime'.
57 cpp: Data::toString NEW.
58 cpp: ImportResult::numV3KeysSkipped NEW.
60 [c=C31/A20/R0 cpp=C12/A6/R0 qt=C10/A3/R1]
63 Noteworthy changes in version 1.10.0 (2017-12-12)
64 -------------------------------------------------
66 * Now returns more specific error codes for decryption to distinguish
67 between bad passphrase, user canceled, and no secret key.
69 * Now returns key origin information if available.
71 * Added context flag "auto-key-retrieve" to selectively enable the
72 corresponding gpg option.
74 * Added flag is_de_vs to decryption and verify results.
76 * py: Use SEEK_SET as default for data.seek.
78 * cpp: Various new APIs.
80 * Reduced spawn overhead on Linux again. Added new configure option
81 --disable-linux-getdents to disable this feature for very old
84 * Improved the Python bindings build system.
86 * Made the test suite less fragile.
88 * Interface changes relative to the 1.9.0 release:
89 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
90 gpgme_decrypt_result_t EXTENDED: New field 'is_de_vs'.
91 gpgme_signature_t EXTENDED: New field 'is_de_vs'.
93 gpgme_op_delete_ext NEW.
94 gpgme_op_delete_ext_start NEW.
95 GPGME_DELETE_ALLOW_SECRET NEW.
96 GPGME_DELETE_FORCE NEW.
97 gpgme_op_conf_dir NEW.
98 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-retrieve'.
99 cpp: DecryptionResult::isDeVs NEW.
100 cpp: Signature::isDeVs NEW.
101 cpp: EngineInfo::Version::operator> NEW.
102 cpp: Context::createKey NEW.
103 cpp: Context::startCreateKey NEW.
104 cpp: Context::createSubkey NEW.
105 cpp: Context::startCreateSubkey NEW.
107 py: DecryptResult EXTENDED: New boolean field 'is_de_vs'.
108 py: Signature EXTENDED: New boolean field 'is_de_vs'.
109 py: GpgError EXTENDED: Partial results in 'results'.
111 [c=C30/A19/R0 cpp=C11/A5/R0 qt=C10/A3/R0]
114 Noteworthy changes in version 1.9.0 (2017-03-28)
115 ------------------------------------------------
117 * Clarified meaning of the 'expire' parameter of gpgme_op_createkey
118 and gpgme_op_createsubkey. New flag to force a key without an
121 * New function gpgme_op_keylist_from_data_start to list keys from
122 data objects without importing them.
124 * New function gpgme_op_set_uid_flag to flag a key as primary.
126 * New function gpgme_op_decrypt_ext to run decryption with special
127 flags. This can for example be used to unwrap keys (remove only
128 the encryption layer).
130 * New encryption flags to wrap a key (adding an encryption layer to
131 an OpenPGP message) or to create anonymously encrypted messages.
133 * Support for adduid and revuid operations in the C++ bindings.
135 * Support for smartcard key generation in the C++ bindings.
137 * Several new functions for the Python binding.
139 * Many smaller bug fixes.
141 * Interface changes relative to the 1.8.0 release:
142 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
143 gpgme_op_createkey CHANGED: Meaning of 'expire' parameter.
144 gpgme_op_createsubkey CHANGED: Meaning of 'expire' parameter.
145 GPGME_CREATE_NOEXPIRE NEW.
146 gpgme_key_t EXTENDED: New field 'origin'.
147 gpgme_key_t EXTENDED: New field 'last_update'.
148 gpgme_subkey_t EXTENDED: New field 'is_de_vs'.
149 gpgme_user_id_t EXTENDED: New field 'origin'.
150 gpgme_user_id_t EXTENDED: New field 'last_update'.
151 gpgme_op_keylist_from_data_start NEW.
152 gpgme_op_set_uid_flag_start NEW.
153 gpgme_op_set_uid_flag NEW.
154 gpgme_op_decrypt_ext_start NEW.
155 gpgme_op_decrypt_ext NEW.
156 GPGME_ENCRYPT_THROW_KEYIDS NEW.
157 GPGME_ENCRYPT_WRAP NEW.
158 GPGME_DECRYPT_VERIFY NEW.
159 GPGME_DECRYPT_UNWRAP NEW.
160 gpgme_data_rewind UN-DEPRECATE.
161 cpp: Context::revUid(const Key&, const char*) NEW.
162 cpp: Context::startRevUid(const Key&, const char*) NEW.
163 cpp: Context::addUid(const Key&, const char*) NEW.
164 cpp: Context::startAddUid(const Key&, const char*) NEW.
165 cpp: Key::UserID::revoke() NEW.
166 cpp: Key::addUid() NEW.
167 cpp: Key::isDeVs NEW.
168 cpp: GpgGenCardKeyInteractor NEW.
169 cpp: Subkey::keyGrip NEW.
170 cpp: Subkey::isDeVs NEW.
171 cpp: Data::toKeys NEW.
172 cpp: Context::setDecryptFlags NEW.
173 cpp: Context::decrypt EXTENDED: Flags added.
174 cpp: Context::startDecrypt EXTENDED: Flags added.
175 cpp: Context::decryptAndVerify EXTENDED: Flags added.
176 cpp: Context::startCombinedDecryptionAndVerification EXTENDED: Flags.
177 cpp: Context::encryptFlags EXTENDED: New flags.
178 qt: CryptoConfig::stringValueList() NEW.
179 py: Context.__init__ EXTENDED: New keyword arg home_dir.
180 py: Context.home_dir NEW.
181 py: Context.keylist EXTENDED: New keyword arg mode.
182 py: Context.keylist EXTENDED: New keyword arg source.
183 py: Context.create_key NEW.
184 py: Context.create_subkey NEW.
185 py: Context.key_add_uid NEW.
186 py: Context.key_revoke_uid NEW.
187 py: Context.key_sign NEW.
188 py: Context.key_tofu_policy NEW.
189 py: core.pubkey_algo_string NEW.
190 py: core.addrspec_from_uid NEW.
192 [c=C29/A18/R0 cpp=C10/A4/R0 qt=C9/A2/R0]
195 Noteworthy changes in version 1.8.0 (2016-11-16)
196 ------------------------------------------------
198 * The module of the Python bindings has been renamed to 'gpg'.
200 * New interface to query current software versions.
202 * New feature to use gpg's --{show,override}session-key options.
204 * New interface to set the sender of a mail.
206 * qt: Added Distinguished Name parser from libkleo
208 * The --homedir option is now used with recent gpgconf versions.
210 * On 64 bit Windows systems gpgconf is now properly located.
212 * The internal locking functions have been replaced by libgpg-error
215 * Interface changes relative to the 1.7.1 release:
216 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
217 gpgme_set_sender NEW.
218 gpgme_get_sender NEW.
219 gpgme_op_query_swdb NEW.
220 gpgme_op_query_swdb_result NEW.
221 gpgme_query_swdb_result_t NEW.
222 gpgme_get_ctx_flag NEW.
223 gpgme_decrypt_result_t EXTENDED: New field session_key.
225 qt: DN::Attribute NEW.
226 qt: Job::context(Job*) NEW.
227 cpp: EngineInfo::Version::Version(const char*) NEW.
228 cpp: EngineInfo::Version::Version() NEW.
230 cpp: Context::setSender(const char*) NEW.
231 cpp: Context::getSender() NEW.
233 [c=C28/A17/R0 cpp=C9/A3/R0 qt=C8/A1/R0]
236 Noteworthy changes in version 1.7.1 (2016-10-18)
237 ------------------------------------------------
239 * Fixed problems with the new language bindings.
241 * New helper function gpgme_addrspec_from_uid.
243 * Use option --exit-on-status-write-error with newer gpg versions.
245 * qt: Missed API from the Qt Binding inclusion has
248 * qt: abstractimportjob.h is now installed to that
249 ImportJobs can be used again.
251 * qt: Fixed spelling error in API (startReceive).
253 * Interface changes relative to the 1.7.0 release:
254 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
255 gpgme_addrspec_from_uid NEW.
256 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
257 qt: MultiDeleteJob NEW.
258 qt: AbstractImportJob NEW.
260 cpp: Signature::key(bool, bool) NEW.
261 cpp: UserID::addrSpecFromString(const char*) NEW.
262 cpp: UserID::addrSpec() NEW.
264 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
267 Noteworthy changes in version 1.7.0 (2016-09-21)
268 ------------------------------------------------
270 * New language bindings for Python 2 and 3.
272 * New language Bindings for C++ and the Qt-Framework API.
274 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
275 key creation easier (requires GnuPG 2.1).
277 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
278 management easier (requires GnuPG 2.1).
280 * New function gpgme_op_keysign to make key signing easier (requires
283 * New function gpgme_op_interact to replace the now deprecated
284 functions gpgme_op_edit and gpgme_op_card_edit.
286 * New function gpgme_pubkey_algo_string to convert a public key
287 algorithm into a GnuPG 2.1 style string.
289 * Support for GnuPG 2.1's TOFU trust model.
291 * Notation flags are now correctly set on verify.
293 * New global flag "require-gnupg" to set a minimal gnupg version.
295 * More supported items in gpgme_get_dirinfo.
297 * New function gpgme_data_set_flag and flag "size-hint".
299 * New function gpgme_set_ctx_flag and flags "full-status" and
302 * Improved gpgme_data_identify to distinguish more file types.
304 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
305 mixed public key and symmetric encryption.
307 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
309 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
310 signed data is a valid MIME part. This is to support future GnuPG
313 * Interface changes relative to the 1.6.0 release:
314 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
315 gpgme_pubkey_algo_string NEW.
317 gpgme_set_ctx_flag NEW.
318 gpgme_data_set_flag NEW.
319 gpgme_op_createkey NEW.
320 gpgme_op_createkey_start NEW.
321 gpgme_op_createsubkey NEW.
322 gpgme_op_createsubkey_start NEW.
323 gpgme_op_adduid_start NEW.
325 gpgme_op_revuid_start NEW.
327 gpgme_op_keysign_start NEW.
328 gpgme_op_keysign NEW.
329 gpgme_op_tofu_policy_start NEW.
330 gpgme_op_tofu_policy NEW.
331 gpgme_op_interact_start NEW.
332 gpgme_op_interact NEW.
333 gpgme_interact_cb_t NEW.
334 gpgme_op_edit_start DEPRECATED.
335 gpgme_op_edit DEPRECATED.
336 gpgme_op_card_edit_start DEPRECATED.
337 gpgme_op_card_edit DEPRECATED.
338 gpgme_edit_cb_t DEPRECATED.
339 gpgme_status_code_t DEPRECATED.
340 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
341 gpgme_signature_t EXTENDED: New field key.
342 gpgme_key_t EXTENDED: New field fpr.
343 gpgme_subkey_t EXTENDED: New field keygrip.
344 gpgme_user_id_t EXTENDED: New field tofu.
345 gpgme_tofu_policy_t NEW.
346 gpgme_tofu_info_t NEW.
347 GPGME_STATUS_KEY_CONSIDERED NEW.
348 GPGME_STATUS_TOFU_USER NEW.
349 GPGME_STATUS_TOFU_STATS NEW.
350 GPGME_STATUS_TOFU_STATS_LONG NEW.
351 GPGME_STATUS_NOTATION_FLAGS NEW.
352 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
353 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
354 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
355 GPGME_DATA_ENCODING_MIME NEW.
356 GPGME_ENCRYPT_SYMMETRIC NEW.
357 GPGME_CREATE_SIGN NEW.
358 GPGME_CREATE_ENCR NEW.
359 GPGME_CREATE_CERT NEW.
360 GPGME_CREATE_AUTH NEW.
361 GPGME_CREATE_NOPASSWD NEW.
362 GPGME_CREATE_SELFSIGNED NEW.
363 GPGME_CREATE_NOSTORE NEW.
364 GPGME_CREATE_WANTPUB NEW.
365 GPGME_CREATE_WANTSEC NEW.
366 GPGME_CREATE_FORCE NEW.
367 GPGME_KEYSIGN_LOCAL NEW.
368 GPGME_KEYSIGN_LFSEP NEW.
369 GPGME_INTERACT_CARD NEW.
371 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
374 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
375 ------------------------------------------------
377 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
379 * Added gpgme_set_status_cb to allow a user to see some status
382 * Added an export mode for secret keys.
384 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
386 * The passphrase handler for the loopback mode has been improved and may
387 also be used with genkey.
389 * [w32] The standard GnuPG 2.1 install directory is now seached for
390 gpgconf.exe before a registry specified directory and the Gpg4win
393 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
396 * Interface changes relative to the 1.5.1 release:
397 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
398 gpgme_set_offline NEW.
399 gpgme_get_offline NEW.
400 gpgme_set_status_cb NEW.
401 gpgme_get_status_cb NEW.
402 GPGME_EXPORT_MODE_SECRET NEW
403 GPGME_EXPORT_MODE_RAW NEW.
404 GPGME_EXPORT_MODE_PKCS12 NEW.
407 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
408 ------------------------------------------------
410 * Fixed crash in key listings for user ids with a backslash.
412 * Fixed regression for GPGSM use with GnuPG < 2.1.
414 * Properly set signature summary for revoked OpenPGP keys.
417 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
418 ------------------------------------------------
420 * Fixed a possible crash in the debug code.
422 * Fixed building for Windows with newer versions of Mingw.
425 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
426 -------------------------------------------------------------
428 * The export key functions do now return an error if used with the
429 latest GnuPG version.
432 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
433 -------------------------------------------------------------
435 * gpgme-tool is now installed.
437 * Fix external listing for modern keyservers.
442 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
443 -------------------------------------------------------------
445 * Fixed possible overflow in gpgsm and uiserver engines.
448 * Added support for GnuPG 2.1's --with-secret option.
450 * Interface changes relative to the 1.5.0 release:
451 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
452 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
455 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
456 -------------------------------------------------------------
458 * On Unices the engine file names are not not anymore hardwired but
459 located via the envvar PATH. All options to set the name of the
460 engines for the configure run are removed.
462 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
463 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
464 is not found, GPGME looks for an engine named "gpg".
466 * New feature to use the gpgme I/O subsystem to run arbitrary
469 * New flag to use encryption without the default compression step.
471 * New function to access "gpg-conf --list-dirs"
473 * New configure option --enable-fixed-path for use by Android.
475 * Support ECC algorithms.
477 * Interface changes relative to the 1.4.3 release:
478 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
479 gpgme_get_dirinfo NEW.
480 gpgme_op_spawn_start NEW.
482 GPGME_PROTOCOL_SPAWN NEW.
483 GPGME_SPAWN_DETACHED NEW.
484 GPGME_SPAWN_ALLOW_SET_FG NEW.
485 GPGME_ENCRYPT_NO_COMPRESS NEW.
488 gpgme_subkey_t EXTENDED: New field curve.
489 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
490 GPGME_STATUS_MOUNTPOINT NEW.
491 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
492 GPGME_STATUS_ATTRIBUTE NEW.
493 GPGME_STATUS_BEGIN_SIGNING NEW.
494 GPGME_STATUS_KEY_NOT_CREATED NEW.
497 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
498 -------------------------------------------------------------
500 * The default engine names are now taken from the output of gpgconf.
501 If gpgconf is not found the use of gpg 1 is assumed.
503 * Under Windows the default engines names are first searched in the
504 installation directory of the gpgme DLL.
506 * New function gpgme_data_identify to detect the type of a message.
508 * Interface changes relative to the 1.4.2 release:
509 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
510 gpgme_signers_count NEW.
511 gpgme_data_type_t NEW.
512 gpgme_data_identify NEW.
515 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
516 -------------------------------------------------------------
518 * Allow symmetric encryption with gpgme_op_encrypt_sign.
520 * Fixed mismatching off_t definitions on Windows.
522 * Interface changes relative to the 1.4.1 release:
523 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
526 GPGME_PROTOCOL_OPENPGP NEW alias.
529 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
530 ------------------------------------------------------------
532 * Fixed reading of gpg.conf files with excessive use of the group
535 * Fixed building with the i686-w64-mingw32 toolchain.
537 * Disabled FD passing by default for Apple.
540 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
541 ------------------------------------------------------------
543 * New function gpgme_set_global_flag to help debugging on Android.
545 * New function gpgme_io_writen as a convenience wrapper around
548 * New functions to support the pinentry mode feature of GnuPG 2.1.
550 * New macro GPGME_VERSION_NUMBER to allow supporting different API
551 versions without the need for a configure test.
553 * Several improvements for gpgme-tool.
555 * Better logging of the common "invalid engine" error code.
557 * Support for FD passing is now enabled by default. The configure
558 option --disable-fd-passing may be used to disable this.
560 * Interface changes relative to the 1.3.1 release:
561 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
562 GPGME_VERSION_NUMBER NEW.
564 gpgme_set_global_flag NEW.
565 gpgme_set_pinentry_mode NEW.
566 gpgme_get_pinentry_mode NEW.
567 gpgme_pinentry_mode_t NEW.
568 GPGME_PINENTRY_MODE_DEFAULT NEW.
569 GPGME_PINENTRY_MODE_ASK NEW.
570 GPGME_PINENTRY_MODE_CANCEL NEW.
571 GPGME_PINENTRY_MODE_ERROR NEW.
572 GPGME_PINENTRY_MODE_LOOPBACK NEW.
575 Noteworthy changes in version 1.3.2 (2012-05-02)
576 ------------------------------------------------
578 * Remove support for libgpgme-pth. As far as we know, this was never used,
579 and GnuPG is going to use our own npth in the future.
581 * Fix signature summary information for a missing X.509 key.
583 * Fix parsing of dates >= year 2038.
586 Noteworthy changes in version 1.3.1 (2011-06-16)
587 ------------------------------------------------
589 * Ported to Windows CE.
591 * Detect GPG versions not supporting ---passwd.
593 * Interface changes relative to the 1.3.0 release:
594 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
595 GPGME_EXPORT_MODE_MINIMAL NEW
596 GPGME_STATUS_SUCCESS NEW
597 gpgme_err_code_from_syserror NEW
598 gpgme_err_set_errno NEW
599 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
600 gpgme_error_from_syserror NEW
601 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
604 Noteworthy changes in version 1.3.0 (2010-01-11)
605 ------------------------------------------------
607 * GPGME does not come with an internal libassuan version anymore.
608 The external libassuan 1.1.0 release or later is required. For
609 application programmers on systems that can resolve inter-library
610 dependencies at runtime, this is a transparent change.
612 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
614 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
616 * New API to change the passphrase of a key.
618 * Interface changes relative to the 1.2.0 release:
619 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
620 GPGME_STATUS_INV_SGNR NEW.
621 GPGME_STATUS_NO_SGNR NEW.
622 GPGME_PROTOCOL_G13 NEW.
623 gpgme_op_g13_mount NEW.
624 gpgme_g13_result_t NEW.
627 gpgme_op_passwd_start NEW.
629 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
632 Noteworthy changes in version 1.2.0 (2009-06-18)
633 ------------------------------------------------
635 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
638 * gpgme_new will fail if gpgme_check_version was not called, or a
639 selftest failed (for example, if -mms-bitfields was not used on
642 * New functions gpgme_io_read and gpgme_io_write for use with
643 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
645 * New functions gpgme_result_ref and gpgme_result_unref to detach
646 result structures from a context.
648 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
649 that allow to specify exported keys through gpgme_key_t objects
652 * New mode of operation gpgme_export_mode_t that allows exporting
655 * Interface changes relative to the 1.1.7 release:
656 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
657 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
658 GPGME_PROTOCOL_ASSUAN NEW.
659 gpgme_assuan_data_cb_t NEW.
660 gpgme_assuan_inquire_cb_t NEW.
661 gpgme_assuan_status_cb_t NEW.
662 gpgme_op_assuan_transact_start NEW.
663 gpgme_op_assuan_transact NEW.
664 gpgme_op_assuan_result NEW.
665 gpgme_op_import_keys NEW.
666 gpgme_op_import_keys_start NEW.
667 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
668 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
669 gpgme_check_version CHANGED: Is now a macro.
670 gpgme_new EXTENDED: More failure codes.
673 gpgme_result_ref NEW.
674 gpgme_result_unref NEW.
675 gpgme_export_mode_t NEW.
676 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
677 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
678 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
679 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
680 gpgme_op_export_keys_start NEW.
681 gpgme_op_export_keys NEW.
682 GPGME_DATA_ENCODING_URL NEW.
683 GPGME_DATA_ENCODING_URL0 NEW.
684 GPGME_DATA_ENCODING_URLESC NEW.
685 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
688 Noteworthy changes in version 1.1.8 (2008-12-08)
689 ------------------------------------------------
691 * SIGPIPE is now again ignored as described in the manual. Fixes
692 regresion introduced with 1.1.6.
695 Noteworthy changes in version 1.1.7 (2008-10-17)
696 ------------------------------------------------
698 * Using GPGME_KEYLIST_MODE_LOCAL combined with
699 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
700 --locate-keys feature of gpg (>= 2.0.10).
702 * The encoding of gpgme_data_t objects can affect the output encoding
703 of export, sign and encrypt operations now (the same operations
704 that are also affected by the ASCII mode switch). We believe this
705 change in the ABI is innocent enough not to break existing
706 applications (it only affects the S/MIME backend on certain
709 * The reference manual now includes the specification of "The GnuPG
712 * A new function gpgme_cancel_async can be used to asynchronously
713 cancel any pending operation at any time, from any thread.
715 * Interface changes relative to the 1.1.6 release:
716 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
717 gpgme_op_encrypt CHANGED: Output encoding can affect result.
718 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
719 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
720 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
721 gpgme_op_sign CHANGED: Output encoding can affect result.
722 gpgme_op_sign_start CHANGED: Output encoding can affect result.
723 gpgme_op_export CHANGED: Output encoding can affect result.
724 gpgme_op_export_start CHANGED: Output encoding can affect result.
725 gpgme_op_export_ext CHANGED: Output encoding can affect result.
726 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
727 gpgme_cancel_async NEW
728 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
731 Noteworthy changes in version 1.1.6 (2008-01-04)
732 ------------------------------------------------
734 * Bug fixes for for W32.
736 * A new, experimental (and thus undocumented and potentially
737 unstable) interface for accessing gpg-conf through GPGME has been
740 * Interface changes relative to the 1.1.1 release:
741 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
742 gpgme_signature_t EXTENDED: New field chain_model.
743 gpgme_op_getauditlog_start NEW.
744 gpgme_op_getauditlog NEW.
745 GPGME_AUDITLOG_HTML NEW.
746 GPGME_AUDITLOG_WITH_HELP NEW.
747 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
750 Noteworthy changes in version 1.1.5 (2007-07-09)
751 ------------------------------------------------
753 * Bug and portability fixes (mainly for W32).
756 Noteworthy changes in version 1.1.4 (2007-03-05)
757 ------------------------------------------------
759 * Detect and bail out on double plaintext messages. This is required
760 so that applications can properly detect the signed parts of a
761 message. Actual there is now a double protection as GnuPG 1.4.7
762 will detect this case too.
765 Noteworthy changes in version 1.1.3 (2007-01-29)
766 ------------------------------------------------
768 * Fixed a memory leak in gpgme_data_release_and_get_mem.
770 * Fixed a bug in Windows command line quoting.
773 Noteworthy changes in version 1.1.2 (2006-03-02)
774 ------------------------------------------------
776 * Fixed a bug in the W32 glib backend.
779 Noteworthy changes in version 1.1.1 (2006-02-23)
780 ------------------------------------------------
782 * Fixed a bug in that the fingerprints of subkeys are not available.
784 * Clarified usage of the SECRET flag in key listings. It is now
787 * Reading signature notations and policy URLs on key signatures is
788 supported. They can be found in the new field notations of the
789 gpgme_key_sig_t structure. This has to be enabled with the keylist
790 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
792 * A new gpgme_free() function solves the problem of using different
793 allocators in a single program. This function should now be used
794 instead calling free() to release the buffer returned by
795 gpgme_data_release_and_get_mem. It is recommended that you always
796 do this, but it is only necessary on certain platforms, so backwards
797 compatibility is provided. In other words: If free() worked for
798 you before, it will keep working.
800 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
801 They are analyzed by the verify handlers and made available in the
802 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
804 * Interface changes relative to the 1.1.0 release:
805 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
806 gpgme_key_sig_t EXTENDED: New field notations.
807 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
809 GPGME_STATUS_PKA_TRUST_BAD NEW
810 GPGME_STATUS_PKA_TRUST_GOOD NEW
811 gpgme_signature_t EXTENDED: New field pka_trust.
812 gpgme_signature_t EXTENDED: New field pka_address.
813 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
816 Noteworthy changes in version 1.1.0 (2005-10-01)
817 ------------------------------------------------
819 * You can now configure the backend engine file name and home
820 directory to be used, as default and per context.
822 * Information about the recipients of an encrypted text is now
823 available at decryption time.
825 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
826 and verify handlers, the information about the plaintext filename,
827 if available is made available in the new field file_name of the
828 respective result structure.
830 * The code for "automagically detecting the thread library" has been
831 removed from libgpgme. It is deprecated since version 0.4.3.
832 Since then, you had to link against libgpgme-pthread for
833 applications using pthread and libgpgme-pth for applications using
836 The code was removed because it caused compilation problems on
837 systems where the pthread.h header from GNU Pth is available in
838 addition to the system header (FreeBSD 6 and later for example).
840 * "./autogen.sh --build-w32" does now build gpgme.dll.
842 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
843 delimiter. The standard install directory is used when locating
844 gpg or gpgsm before finally falling back to the hardwired name.
846 * There is a new flag for keys and subkeys, is_qualified, which
847 indicates if a key can be used for qualified signatures according
848 to local government regulations.
850 * You can associate a filename with a data object using the new
851 function gpgme_data_set_file_name(). This filename will be stored
852 in the output when encrypting or signing the data and will be
853 returned when decrypting or verifying the output data.
855 * You can now set notation data at signature creation with the new
856 function gpgme_sig_notation_add().
858 * Interface changes relative to the 1.0.3 release:
859 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
860 gpgme_set_engine_info NEW
861 gpgme_ctx_get_engine_info NEW
862 gpgme_ctx_set_engine_info NEW
863 gpgme_recipient_t NEW
864 gpgme_decrypt_result_t EXTENDED: New field recipients.
865 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
866 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
867 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
868 GPGME_STATUS_PLAINTEXT NEW
869 gpgme_key_t EXTENDED: New field is_qualified.
870 gpgme_subkey_t EXTENDED: New field is_qualified.
871 gpgme_data_get_file_name NEW
872 gpgme_data_set_file_name NEW
873 gpgme_sig_notation_flags_t NEW
874 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
875 GPGME_SIG_NOTATAION_CRITICAL NEW
876 gpgme_sig_notation_clear NEW
877 gpgme_sig_notation_add NEW
878 gpgme_sig_notation_get NEW
879 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
882 Noteworthy changes in version 1.0.3 (2005-06-20)
883 ------------------------------------------------
885 * Previousy, GPGME would use a default "include certs" of 1. This
886 has been changed. Now GPGME will use the crypto backend engines
887 default unless you set the value with gpgme_set_include_certs()
888 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
889 as a value to explicitely request the new default behaviour.
891 Because the default changes, this is a slight change of the API
892 semantics. We consider it to be a bug fix.
894 * A bug which made GPGME hang has been fixed. If you have
895 experienced hanging before, please try out this version and let me
896 know if you still experience hanging problems.
898 * Interface changes relative to the 0.9.0 release:
899 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
900 gpgme_set_include_certs CHANGED DEFAULT
901 GPGME_INCLUDE_CERTS_DEFAULT NEW
902 GPGME_STATUS_SIG_SUBPACKET NEW
903 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
904 GPGME_STATUS_SC_OP_FAILURE NEW
905 GPGME_STATUS_SC_OP_SUCCESS NEW
906 GPGME_STATUS_CARDCTRL NEW
907 GPGME_STATUS_BACKUP_KEY_CREATED NEW
908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
911 Noteworthy changes in version 1.0.2 (2004-12-28)
912 ------------------------------------------------
914 * Changed the license of the library to the GNU Lesser General Public
915 License (LGPL), version 2.1 or later.
918 Noteworthy changes in version 1.0.1 (2004-10-22)
919 ------------------------------------------------
924 Noteworthy changes in version 1.0.0 (2004-09-30)
925 ------------------------------------------------
927 * Version 1.0.0! We are proud to present you with a thoroughly
928 tested and stable version of the GPGME library. A big Thank You!
929 to all the people who made this possible.
931 The development will be branched into a stable 1.x.y series and the
934 * The gpgme.m4 macro supports checking the API version. Just prepend
935 it to the required version string, separated by a colon. For
936 example, this release has the version "1:1.0.0". The last release
937 to which this version is (mostly) ABI compatible is "1:0.4.2",
938 which is the default required version.
941 Noteworthy changes in version 0.9.0 (2004-06-08)
942 ------------------------------------------------
944 * The type gpgme_key_t has now a new field keylist_mode that contains
945 the keylist mode that was active at the time the key was retrieved.
947 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
948 that contains a flag indicating that the key should not have been
951 * Verifying a signature of a revoked key gives the correct result now
952 (GPG_ERR_CERT_REVOKED error code).
954 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
955 verify operations still allows you to look at the signature
958 * Clarified that patterns in keylisting operations have an upper
959 limit, and thus are not suited to list many keys at once by their
960 fingerprint. Also improve the error message if the pattern is too
961 long for the CMS protocol to handle.
963 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
964 gpgme_key_t EXTENDED: New field keylist_mode.
965 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
966 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
969 Noteworthy changes in version 0.4.7 (2004-04-29)
970 ------------------------------------------------
972 * Correctly initialize the fields expired, revoked, invalid, and
973 disabled in the gpgme_key_t structures.
975 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
976 accidently of type int instead unsigned int.
978 * Interface changes relative to the 0.4.5 release:
979 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
980 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
981 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
983 Noteworthy changes in version 0.4.6 (2004-04-06)
984 ------------------------------------------------
989 Noteworthy changes in version 0.4.5 (2004-03-07)
990 ------------------------------------------------
992 * GPGME is now compiled with LFS (large file support) by default.
993 This means that _all_ programs using GPGME must be compiled with
994 LFS support enabled by default. You can do this easily with
995 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
996 without autoconf by defining the preprocessor symbol
997 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
998 the C compiler command line, or by defining this preprocessor
999 symbol before including any system header files). For more
1000 details, read the section on LFS in the manual.
1002 Up to now, it was undocumented that GPGME was not using LFS.
1003 But the public interfaces use off_t, and file descriptors are
1004 exchanged between the application and GPGME. This was an oversight,
1005 and bound to cause troubles in the future.
1007 Writing GPGME as a dual mode library that seamlessly supports LFS
1008 while keeping backwards compatibility is possible, but does not
1009 solve the problem: Many applications already expect GPGME to have
1010 LFS (they are compiled with off_t being a 64bit value). This is true
1011 in particular for the popular Gtk+ and Qt programs.
1013 So, although this is an ABI (but not an API) break, we will not
1014 change the library version to reflect that. Because the interfaces
1015 affected are probably not used yet in any GPGME 0.4 based
1016 application, we don't expect any real failures from this change.
1017 In fact, applications already using LFS will have some subtle bugs
1020 However, if you encounter an application using GPGME 0.4.x that
1021 does _not_ use LFS by default (off_t is a 32bit value), _and_
1022 uses at least one of the functions gpgme_data_seek,
1023 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
1024 gpgme_data_new_from_cbs, then indeed this library will be ABI
1025 incompatible with the program. As said above, we don't believe
1026 such a program exists. If we are in error, then you have two
1027 options: As a quick hack, you can configure GPGME with the
1028 --disable-largefile option. This will revert the change, and GPGME
1029 will not use LFS. However, GPGME will be incompatible with
1030 programs that expect GPGME to use LFS. All applications are
1031 required to use LFS when using GPGME, so this is only good as a
1032 temporary local work-around.
1034 The other option is to change the versioning of the library and
1035 recompile all applications. We have reserved a special version of
1036 the library for that, so you can do that without expecting a
1037 version clash in the future. Furthermore, everyone who does this
1038 will agree on the version to use (this is important for
1039 distribution makers). Read the comment in configure.ac (before
1040 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
1041 blindly: As stated above, we think it is unlikely this measure is
1042 needed. Still, it is there if necessary. If in doubt, contact us
1043 and we will give our advise for your specific situation.
1045 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
1048 * New interface gpgme_cancel() that can be used to cancel
1049 asynchronous operations.
1051 * Interface changes relative to the 0.4.4 release:
1052 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1053 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
1054 gpgme_data_seek CHANGED: off_t is now a largefile type.
1055 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
1056 GPGME_KEYLIST_MODE_VALIDATE NEW
1058 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1060 Noteworthy changes in version 0.4.4 (2004-01-12)
1061 ------------------------------------------------
1063 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
1064 been renamed to "sig_class", to avoid clash with C++ compilers. In
1065 the C API, the old name "class" has been preserved for backwards
1066 compatibility, but is deprecated.
1068 * Interface changes relative to the 0.4.3 release:
1069 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1070 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
1071 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
1072 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1074 Noteworthy changes in version 0.4.3 (2003-10-06)
1075 ------------------------------------------------
1077 * libgpgme should not be used for threaded programs anymore. This
1078 never worked reliably in all cases, because you had to
1079 be careful about the linking order and libtool wouldn't do that for
1080 you automatically. Instead, now you have to link against
1081 libgpgme-pthread for applications using pthread and libgpgme-pth for
1082 applications using GNU Pth.
1084 The old code for automagically detecting the thread library is
1085 still part of libgpgme, but it is DEPRECATED.
1087 * There are new automake macros AM_PATH_GPGME_PTH and
1088 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
1089 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
1090 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
1091 variables of course also include the configuration for the thread
1092 package itself. Alternatively, use libtool.
1094 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
1097 * gpgme-config doesn't support setting the prefix or exec prefix
1098 anymore. I don't think it ever worked correctly, and it seems to
1101 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
1102 provided was not unique, instead returning the first matching key.
1104 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
1105 that indicates if the key can be used for authentication.
1107 * gpgme_signature_t's status field is now correctly set to an error
1108 with error code GPG_ERR_NO_PUBKEY if public key is not found.
1110 * gpgme_new_signature_t's class field is now an unsigned int, rather
1111 than an unsigned long (the old class field is preserved for
1112 backwards compatibility).
1114 * A new function gpgme_set_locale() is provided to allow configuring
1115 the locale for the crypto backend. This is necessary for text
1116 terminals so that programs like the pinentry can be started with
1117 the right locale settings for the terminal the application is running
1118 on, in case the terminal has different settings than the system
1119 default (for example, if it is a remote terminal). You are highly
1120 recommended to call the following functions directly after
1121 gpgme_check_version:
1125 setlocale (LC_ALL, "");
1126 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
1127 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
1129 GPGME can not do this for you, as setlocale is not thread safe, and
1130 there is no alternative.
1132 * The signal action for SIGPIPE is now set to SIG_IGN by
1133 gpgme_check_version, instead the first time a crypto engine is
1134 started (which is not well defined).
1136 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
1137 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
1138 to CRC24RFC2440. For now, these strings can be used as the MIC
1139 parameter for PGP/MIME (if appropriately modified).
1141 * Interface changes relative to the 0.4.2 release:
1142 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1143 gpgme_strerror_t NEW
1144 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
1145 gpgme_key_t EXTENDED: New field can_authenticate.
1146 gpgme_subkey_t EXTENDED: New field can_authenticate.
1147 gpgme_new_signature_t CHANGED: New type for class field.
1148 gpgme_set_locale NEW
1149 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
1150 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1152 Noteworthy changes in version 0.4.2 (2003-07-30)
1153 ------------------------------------------------
1155 * Allow gpg-error to be in non-standard place when linking the test suite.
1157 * Configure will fail now if gpg-error can not be found.
1159 * Fixed initialized memory backed data objects for writing, which
1160 caused the test program to crash (but only on Mac OS, surprisingly).
1162 * Eliminate use of C99 constructs.
1164 * Small improvements to the manual.
1167 Noteworthy changes in version 0.4.1 (2003-06-06)
1168 ------------------------------------------------
1170 This is the release that 0.4.0 should have been. There are many
1171 interface changes, please see below for the details. The changes are
1172 sometimes the result of new functionality, but more often express a
1173 paradigm shift. Others are an overdue cleanup to get GPGME in line
1174 with the GNU coding standards and to make the interface more
1175 self-consistent. Here is an overview on the changes:
1177 All types have been renamed to conform to the GNU coding standards,
1178 most of the time by keeping the whole name in lowercase and inserting
1179 underscores between words.
1181 All operations consistently only accept input parameters in their
1182 invocation function, and return only an error code directly. Further
1183 information about the result of the operation has to be retrieved
1184 afterwards by calling one of the result functions. This unifies the
1185 synchronous and the asynchronous interface.
1187 The error values have been completely replaced by a more
1188 sophisticated model that allows GPGME to transparently and accurately
1189 report all errors from the other GnuPG components, irregardless of
1190 process boundaries. This is achieved by using the library
1191 libgpg-errors, which is shared by all GnuPG components. This library
1192 is now required for GPGME.
1194 The results of all operations are now provided by pointers to C
1195 structs rather than by XML structs or in other ways.
1197 Objects which used to be opaque (for example a key) are now pointers
1198 to accessible structs, so no accessor functions are necessary.
1200 Backward compatibility is provided where it was possible without too
1201 much effort and did not collide with the overall sanitization effort.
1202 However, this is only for ease of transition. NO DEPRECATED FUNCTION
1203 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
1204 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
1205 Recommendations how to replace deprecated or removed functionality
1206 can be found within the description of each change.
1208 What follows are all changes to the interface and behaviour of GPGME
1211 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
1212 deprecated attributes will warn about use of obsolete functions and
1213 type definitions. You can suppress these warnings by passing
1214 -Wno-deprecated-declarations to the gcc command.
1216 * The following types have been renamed. The old types are still
1217 available as aliases, but they are deprecated now:
1219 GpgmeCtx gpgme_ctx_t
1220 GpgmeData gpgme_data_t
1221 GpgmeError gpgme_error_t
1222 GpgmeDataEncoding gpgme_data_encoding_t
1223 GpgmeSigStat gpgme_sig_stat_t
1224 GpgmeSigMode gpgme_sig_mode_t
1225 GpgmeAttr gpgme_attr_t
1226 GpgmeValidity gpgme_validity_t
1227 GpgmeProtocol gpgme_protocol_t
1228 GpgmeKey gpgme_key_t
1229 GpgmePassphraseCb gpgme_passphrase_cb_t
1230 GpgmeProgressCb gpgme_progress_cb_t
1231 GpgmeIOCb gpgme_io_cb_t
1232 GpgmeRegisterIOCb gpgme_register_io_cb_t
1233 GpgmeRemoveIOCb gpgme_remove_io_cb_t
1234 GpgmeEventIO gpgme_event_io_t
1235 GpgmeEventIOCb gpgme_event_io_cb_t
1236 GpgmeIOCbs gpgme_io_cbs
1237 GpgmeDataReadCb gpgme_data_read_cb_t
1238 GpgmeDataWriteCb gpgme_data_write_cb_t
1239 GpgmeDataSeekCb gpgme_data_seek_cb_t
1240 GpgmeDataReleaseCb gpgme_data_release_cb_t
1241 GpgmeDataCbs gpgme_data_cbs_t
1242 GpgmeTrustItem gpgme_trust_item_t
1243 GpgmeStatusCode gpgme_status_code_t
1245 * gpgme_error_t is now identical to gpg_error_t, the error type
1246 provided by libgpg-error. More about using libgpg-error with GPGME
1247 can be found in the manual. All error symbols have been removed!
1249 * All functions and types in libgpg-error have been wrapped in GPGME.
1250 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1251 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1252 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1253 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1256 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1258 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1259 for encrypt, sign, encrypt-sign, decrypt, verify, and
1260 decrypt-verify operations. For verify operations on detached
1261 signatures, the progress callback is invoked for both the detached
1262 signature and the plaintext message, though.
1264 * gpgme_passphrase_cb_t has been changed to not provide a complete
1265 description, but the UID hint, passphrase info and a flag
1266 indicating if this is a repeated attempt individually, so the user
1267 can compose his own description from this information.
1269 The passphrase is not returned as a C string, but must be written
1270 to a file descriptor directly. This allows for secure passphrase
1273 The return type has been changed to gpgme_error_t value. This
1274 allowed to remove the gpgme_cancel function; just return
1275 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1277 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1278 The user is expected to write the response to the file descriptor,
1279 followed by a newline.
1281 * The recipients interface has been removed. Instead, you use
1282 NULL-terminated lists of keys for specifying the recipients of an
1283 encryption operation. Use the new encryption flag
1284 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1285 the keys (but note that in general this is not a good idea).
1287 This change has been made to the prototypes of gpgme_op_encrypt,
1288 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1289 gpgme_op_encrypt_sign_start.
1291 The export interface has been changed to use pattern strings like
1292 the keylist interface. Thus, new functions gpgme_op_export_ext and
1293 gpgme_op_export_ext_start have been added as well. Now the
1294 prototypes of gpgme_op_export_start and gpgme_op_export finally
1297 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1298 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1301 * gpgme_io_cb_t changed from a void function to a function returning
1302 a gpgme_error_t value. However, it will always return 0, so you
1303 can safely ignore the return value.
1305 * A new I/O callback event GPGME_EVENT_START has been added. The new
1306 requirement is that you must wait until this event until you are
1307 allowed to call the I/O callback handlers previously registered for
1308 this context operation. Calling I/O callback functions for this
1309 context operation before the start event happened is unsafe because
1310 it can lead to race conditions in a multi-threaded environment.
1312 * The idle function feature has been removed. It was not precisely
1313 defined in a multi-threaded environment and is obsoleted by the
1314 user I/O callback functions. If you still need a simple way to
1315 call something while waiting on one or multiple asynchronous
1316 operations to complete, don't set the HANG flag in gpgme_wait (note
1317 that this will return to your program more often than the idle
1320 * gpgme_wait can return NULL even if hang is true, if an error
1321 occurs. In that case *status contains the error code.
1323 * gpgme_get_engine_info was radically changed. Instead an XML
1324 string, an info structure of the new type gpgme_engine_info_t is
1325 returned. This makes it easier and more robust to evaluate the
1326 information in an application.
1328 * The new function gpgme_get_protocol_name can be used to convert a
1329 gpgme_protocol_t value into a string.
1331 * The status of a context operation is not checked anymore. Starting
1332 a new operation will silently cancel the previous one. Calling a
1333 function that requires you to have started an operation before without
1334 doing so is undefined.
1336 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1337 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1338 pointer to a structure which contains the fingerprint. This also
1339 works with gpgme_op_genkey_start. The structure also provides
1340 other information about the generated keys.
1345 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1347 printf ("%s\n", fpr);
1351 gpgme_genkey_result_t result;
1352 err = gpgme_op_genkey (ctx, NULL, NULL);
1355 result = gpgme_op_genkey_result (ctx);
1357 printf ("%s\n", result->fpr);
1360 * The new gpgme_op_import_result function provides detailed
1361 information about the result of an import operation in
1362 gpgme_import_result_t and gpgme_import_status_t objects.
1363 Thus, the gpgme_op_import_ext variant is deprecated.
1365 * The new gpgme_op_sign_result function provides detailed information
1366 about the result of a signing operation in gpgme_sign_result_t,
1367 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1369 * The new gpgme_op_encrypt_result function provides detailed
1370 information about the result of an encryption operation in
1371 a GpgmeEncryptResult object.
1373 * The new gpgme_op_decrypt_result function provides detailed
1374 information about the result of a decryption operation in
1375 a GpgmeDecryptResult object.
1377 * The new gpgme_op_verify_result function provides detailed
1378 information about the result of an verify operation in
1379 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1380 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1381 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1382 and gpgme_get_notation is removed.
1384 * GpgmeTrustItem objects have now directly accessible data, so the
1385 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1386 accessor functions are deprecated. Also, reference counting is
1387 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1388 (the gpgme_trust_item_release alias for the latter is deprecated).
1390 * Keys are not cached internally anymore, so the force_update argument
1391 to gpgme_get_key has been removed.
1393 * GpgmeKey objects have now directly accessible data so the
1394 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1395 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1396 functions are deprecated. Also, gpgme_key_release is now
1397 deprecated. The gpgme_key_get_as_xml function has been dropped.
1399 * Because all interfaces using attributes are deprecated, the
1400 GpgmeAttr data type is also deprecated.
1402 * The new gpgme_op_keylist_result function provides detailed
1403 information about the result of a key listing operation in
1404 a GpgmeKeyListResult object.
1406 * Now that each function comes with its own result retrieval
1407 interface, the generic gpgme_get_op_info interface is not useful
1408 anymore and dropped.
1410 * The type and mode of data objects is not available anymore.
1412 * Interface changes relative to the 0.4.0 release:
1413 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1414 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1415 GpgmeData DEPRECATED: Use gpgme_data_t.
1416 GpgmeError DEPRECATED: Use gpgme_error_t.
1417 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1418 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1419 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1420 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1421 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1422 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1423 GpgmeKey DEPRECATED: Use gpgme_key_t.
1424 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1425 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1426 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1427 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1428 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1429 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1430 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1431 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1432 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1433 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1434 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1435 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1436 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1437 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1438 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1441 gpgme_recipients_t NEW
1443 gpgme_data_encoding_t NEW
1444 gpgme_sig_stat_t NEW
1445 gpgme_sig_mode_t NEW
1447 gpgme_validity_t NEW
1448 gpgme_protocol_t NEW
1450 gpgme_passphrase_cb_t NEW
1451 gpgme_progress_cb_t NEW
1453 gpgme_register_io_cb_t NEW
1454 gpgme_remove_io_cb_t NEW
1455 gpgme_event_io_t NEW
1456 gpgme_event_io_cb_t NEW
1458 gpgme_data_read_cb_t NEW
1459 gpgme_data_write_cb_t NEW
1460 gpgme_data_seek_cb_t NEW
1461 gpgme_data_release_cb_t NEW
1462 gpgme_data_cbs_t NEW
1463 gpgme_trust_item_t NEW
1464 gpgme_status_code_t NEW
1465 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1466 gpgme_err_code_t NEW
1467 gpgme_err_source_t NEW
1469 gpgme_err_source NEW
1472 gpgme_error_from_errno NEW
1473 gpgme_err_make_from_errno NEW
1474 gpgme_err_code_from_errno NEW
1475 gpgme_err_code_to_errno NEW
1477 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1478 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1479 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1480 gpgme_edit_cb_t CHANGED: Write directly to FD.
1481 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1482 gpgme_op_verify CHANGED: Drop R_STAT argument.
1483 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1484 gpgme_wait CHANGED: Can return NULL even if hang is true.
1485 GpgmeIdleFunc REMOVED
1486 gpgme_register_idle REMOVED
1487 GpgmeRecipients REMOVED
1488 gpgme_recipients_new REMOVED
1489 gpgme_recipients_release REMOVED
1490 gpgme_recipients_add_name REMOVED
1491 gpgme_recipients_add_name_with_validity REMOVED
1492 gpgme_recipients_count REMOVED
1493 gpgme_recipients_enum_open REMOVED
1494 gpgme_recipients_enum_read REMOVED
1495 gpgme_recipients_enum_close REMOVED
1496 gpgme_encrypt_flags_t NEW
1497 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1498 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1499 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1500 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1501 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1502 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1503 gpgme_op_export CHANGED: User IDs passed as patterns.
1504 gpgme_op_export_ext_start NEW
1505 gpgme_op_export_ext NEW
1506 gpgme_keylist_mode_t NEW
1508 gpgme_engine_info_t NEW
1509 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1510 gpgme_get_protocol_name NEW
1511 gpgme_cancel REMOVED: Return error in callback directly.
1512 gpgme_op_genkey CHANGED: FPR argument dropped.
1513 gpgme_op_genkey_result NEW
1514 gpgme_genkey_result_t NEW
1515 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1516 gpgme_op_import_result NEW
1517 gpgme_import_status_t NEW
1518 gpgme_import_result_t NEW
1519 gpgme_pubkey_algo_t NEW
1520 gpgme_hash_algo_t NEW
1521 gpgme_invalid_key_t NEW
1522 gpgme_new_signature_t NEW
1523 gpgme_sign_result_t NEW
1524 gpgme_op_sign_result NEW
1525 gpgme_pubkey_algo_name NEW
1526 gpgme_hash_algo_name NEW
1527 gpgme_encrypt_result_t NEW
1528 gpgme_op_encrypt_result NEW
1529 gpgme_decrypt_result_t NEW
1530 gpgme_op_decrypt_result NEW
1531 gpgme_verify_result_t NEW
1532 gpgme_op_verify_result NEW
1533 gpgme_get_notation REMOVED: Access verify result directly instead.
1534 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1535 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1536 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1537 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1538 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1539 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1540 gpgme_trust_item_ref NEW
1541 gpgme_trust_item_unref NEW
1542 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1543 gpgme_trust_item_get_string_attr DEPRECATED
1544 gpgme_trust_item_get_ulong_attr DEPRECATED
1545 gpgme_get_key CHANGED: Removed force_update argument.
1549 gpgme_key_t CHANGED: Now has user accessible data members.
1550 gpgme_key_get_string_attr DEPRECATED
1551 gpgme_key_get_ulong_attr DEPRECATED
1552 gpgme_key_sig_get_string_attr DEPRECATED
1553 gpgme_key_sig_get_ulong_attr DEPRECATED
1554 gpgme_key_get_as_xml REMOVED
1555 gpgme_key_list_result_t NEW
1556 gpgme_op_keylist_result NEW
1557 gpgme_get_op_info REMOVED
1558 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1560 Noteworthy changes in version 0.4.0 (2002-12-23)
1561 ------------------------------------------------
1563 * Key generation returns the fingerprint of the generated key.
1565 * New convenience function gpgme_get_key.
1567 * Supports signatures of user IDs in keys via the new
1568 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1569 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1570 interfaces. The XML info about a key also includes the signatures
1573 * New data object interface, which is more flexible and transparent.
1575 * Interface changes relative to the 0.3.9 release:
1576 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1578 GpgmeDataWriteCb NEW
1580 GpgmeDataReleaseCb NEW
1582 gpgme_data_read CHANGED: Match read() closely.
1583 gpgme_data_write CHANGED: Match write() closely.
1585 gpgme_data_new_from_fd NEW
1586 gpgme_data_new_from_stream NEW
1587 gpgme_data_new_from_cbs NEW
1588 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1589 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1590 gpgme_data_get_type REMOVED: No replacement.
1591 gpgme_op_verify CHANGED: Take different data objects for
1592 signed text and plain text.
1593 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1594 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1595 gpgme_op_genkey CHANGED: New parameter FPR.
1596 GPGME_KEYLIST_MODE_SIGS NEW
1597 gpgme_key_sig_get_string_attr NEW
1598 gpgme_key_sig_get_ulong_attr NEW
1600 GPGME_ATTR_SIG_CLASS NEW
1601 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1603 Noteworthy changes in version 0.3.16 (2003-11-19)
1604 -------------------------------------------------
1606 * Compatibility fixes for GnuPG 1.9.x
1608 Noteworthy changes in version 0.3.15 (2003-02-18)
1609 -------------------------------------------------
1611 * The progress status is sent via the progress callbacks in
1614 * Bug fix for signing operations with explicit signer settings for
1617 Noteworthy changes in version 0.3.14 (2002-12-04)
1618 -------------------------------------------------
1620 * GPGME-Plug is now in its own package "cryptplug".
1622 * Workaround for a setlocale problem. Fixed a segv related to not
1623 correctly as closed marked file descriptors.
1625 Noteworthy changes in version 0.3.13 (2002-11-20)
1626 -------------------------------------------------
1628 * Release due to changes in gpgmeplug.
1630 Noteworthy changes in version 0.3.12 (2002-10-15)
1631 -------------------------------------------------
1633 * Fixed some bux with key listings.
1635 * The development has been branched to clean up some API issues.
1636 This 0.3 series will be kept for compatibility reasons; so do don't
1637 expect new features.
1639 Noteworthy changes in version 0.3.11 (2002-09-20)
1640 -------------------------------------------------
1644 Noteworthy changes in version 0.3.10 (2002-09-02)
1645 -------------------------------------------------
1647 * Setting the signing keys for the CMS protocol does now work.
1649 * The signers setting is honoured by gpgme_op_edit.
1651 Noteworthy changes in version 0.3.9 (2002-08-21)
1652 ------------------------------------------------
1654 * A spec file for creating RPMs has been added.
1656 * An experimental interface to GnuPG's --edit-key functionality is
1657 introduced, see gpgme_op_edit.
1659 * The new gpgme_import_ext function provides a convenient access to
1660 the number of processed keys.
1662 * Interface changes relative to the 0.3.8 release:
1663 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1666 gpgme_op_edit_start NEW
1668 gpgme_op_import_ext NEW
1669 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1671 Noteworthy changes in version 0.3.8 (2002-06-25)
1672 ------------------------------------------------
1674 * It is possible to use an outside event loop for the I/O to the
1675 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1677 * Interface changes relative to the 0.3.6 release:
1678 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1680 GpgmeRegisterIOCb NEW
1684 struct GpgmeIOCbs NEW
1685 gpgme_set_io_cbs NEW
1686 gpgme_get_io_cbs NEW
1687 GPGME_ATTR_ERRTOK NEW
1688 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1690 Noteworthy changes in version 0.3.7 (2002-06-04)
1691 ------------------------------------------------
1693 * GPGME_ATTR_OTRUST is implemented now.
1695 * A first step toward thread safeness has been achieved, see the
1696 documentation for details. Supported thread libraries are pthread
1699 Noteworthy changes in version 0.3.6 (2002-05-03)
1700 ------------------------------------------------
1702 * All error output of the gpgsm backend is send to the bit bucket.
1704 * The signature verification functions are extended. Instead of
1705 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1706 expired signatures. 2 new functions may be used to retrieve more
1707 detailed information like the signature expiration time and a
1708 validity information of the key without an extra key looking.
1710 * The current passphrase callback and progress meter callback can be
1711 retrieved with the new functions gpgme_get_passphrase_cb and
1712 gpgme_get_progress_cb respectively.
1714 * Interface changes relative to the 0.3.5 release:
1715 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1716 gpgme_get_passphrase_cb NEW
1717 gpgme_get_progress_cb NEW
1718 GpgmeDataEncoding NEW
1719 gpgme_data_set_encoding NEW
1720 gpgme_data_get_encoding NEW
1721 GPGME_SIG_STAT_GOOD_EXP NEW
1722 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1723 gpgme_op_verify CHANGED: Returns more status codes.
1724 GPGME_ATTR_SIG_STATUS NEW
1725 gpgme_get_sig_string_attr NEW
1726 gpgme_get_sig_ulong_attr NEW
1727 gpgme_get_protocol NEW
1728 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1730 Noteworthy changes in version 0.3.5 (2002-04-01)
1731 ------------------------------------------------
1733 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1734 case, symmetric encryption is performed. Note that this requires a
1735 passphrase from the user.
1737 * More information is returned for X.509 certificates.
1739 * Interface changes relative to the 0.3.4 release:
1740 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1741 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1742 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1744 Noteworthy changes in version 0.3.4 (2002-03-04)
1745 ------------------------------------------------
1747 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1748 some recipients have been invalid, whereas earlier versions
1749 succeeded in this case. The plaintext is still encrypted for all valid
1750 recipients, so the application might take this error as a hint that
1751 the ciphertext is not usable for all requested recipients.
1752 Information about invalid recipients is available with gpgme_get_op_info.
1754 * gpgme_op_verify now allows to pass an uninitialized data object as
1755 its plaintext argument to check for normal and cleartext
1756 signatures. The plaintext is then returned in the data object.
1758 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1759 to set and get the number of certifications to include in S/MIME
1762 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1763 to encrypt and sign a message in a combined operation.
1765 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1767 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1769 * Interface changes relative to the 0.3.3 release:
1770 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1771 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1772 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1773 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1774 gpgme_set_include_certs NEW
1775 gpgme_get_include_certs NEW
1776 gpgme_op_encrypt_sign NEW
1777 gpgme_op_encrypt_sign_start NEW
1778 gpgme_op_keylist_ext_start NEW
1779 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1781 Noteworthy changes in version 0.3.3 (2002-02-12)
1782 ------------------------------------------------
1784 * Fix the Makefile in jnlib.
1786 * Fix the test suite (hopefully). It should clean up all its state
1787 with `make check' now.
1790 Noteworthy changes in version 0.3.2 (2002-02-10)
1791 ------------------------------------------------
1793 * Remove erroneous dependency on libgcrypt in jnlib.
1796 Noteworthy changes in version 0.3.1 (2002-02-09)
1797 ------------------------------------------------
1799 * There is a Texinfo manual documenting the API.
1801 * The gpgme_set_keylist_mode function returns an error, and changed
1802 its meaning. It is no longer usable to select between normal and
1803 fast mode (newer versions of GnuPG will always be fast), but
1804 selects between local keyring, remote keyserver, or both.
1805 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1806 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1807 current setting, a fucntion gpgme_get_keylist_mode was added to
1808 retrieve the current mode.
1810 * gpgme_wait accepts a new argument STATUS to return the error status
1811 of the operation on the context. Its definition is closer to
1812 waitpid() now than before.
1814 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1815 type from off_t to the unsigned size_t.
1817 * The R_HD argument to the GpgmePassphraseCb type changed its type
1818 from void* to void**.
1820 * New interface gpgme_op_trustlist_end() to match
1821 gpgme_op_keylist_end().
1823 * The CryptPlug modules have been renamed to gpgme-openpgp and
1824 gpgme-smime, and they are installed in pkglibdir by `make install'.
1826 * An idle function can be registered with gpgme_register_idle().
1828 * The GpgSM backend supports key generation with gpgme_op_genkey().
1830 * Interface changes relative to the 0.3.0 release:
1831 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1832 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1833 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1834 gpgme_wait CHANGED: New argument STATUS.
1835 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1836 The function has a new meaning!
1837 gpgme_get_keylist_mode NEW
1838 GPGME_KEYLIST_MODE_LOCAL NEW
1839 GPGME_KEYLIST_MODE_EXTERN NEW
1840 gpgme_op_trustlist_next NEW
1842 gpgme_register_idle NEW
1843 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1845 Noteworthy changes in version 0.3.0 (2001-12-19)
1846 ------------------------------------------------
1848 * New interface gpgme_set_protocol() to set the protocol and thus the
1849 crypto engine to be used by the context. Currently, the OpenPGP
1850 and the CMS protocols are supported. They are specified by the new
1851 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1852 A new context uses the OpenPGP engine by default.
1854 * gpgme_get_engine_info() returns information for all crypto engines
1855 compiled into the library. The XML format has changed. To
1856 reliably get the version of a crypto engine, the <version> tag
1857 after the appropriate <protocol> tag has to be looked for.
1859 * New interface gpgme_engine_check_version(), obsoleting
1860 gpgme_check_engine(). Check the version of all engines you are
1861 supporting in your software.
1863 * GpgmeKey lists the user ids in the order as they are returned by
1864 GnuPG, first the primary key with index 0, then the sub-user ids.
1866 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1867 signatures simultaneously.
1869 * The new interface gpgme_op_keylist_end() terminates a pending
1870 keylist operation. A keylist operation is also terminated when
1871 gpgme_op_keylist_next() returns GPGME_EOF.
1873 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1874 cross-compiled, or even compiled without support for GnuPG
1877 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1878 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1879 in the path, but it can also be compiled without support for GpgSM
1880 (`--without-gpgsm').
1882 * CryptPlug modules for GPGME are included and can be enabled at
1883 configure time (`--enable-gpgmeplug'). There is one module which
1884 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1885 GpgSM engine (`gpgsmplug').
1887 * Interface changes relative to the latest 0.2.x release:
1888 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1889 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1890 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1891 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1892 gpgme_get_engine_info CHANGED: New format, extended content.
1893 gpgme_engine_check_version NEW
1894 gpgme_decrypt_verify_start NEW
1895 gpgme_decrypt_verify NEW
1896 gpgme_op_keylist_next NEW
1897 gpgme_set_protocol NEW
1898 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1901 Noteworthy changes in version 0.2.3 (2001-09-17)
1902 ------------------------------------------------
1904 * New function gpgme_get_op_info which can be used to get the micalg
1905 parameter needed for MOSS.
1907 * New functions gpgme_get_armor and gpgme_get_textmode.
1909 * The usual bug fixes and some minor functionality improvements.
1911 * Added a simple encryption component for MS-Windows; however the
1912 build procedure might have some problems.
1915 Noteworthy changes in version 0.2.2 (2001-06-12)
1916 ------------------------------------------------
1918 * Implemented a key cache.
1920 * Fixed a race condition under W32 and some other bug fixes.
1923 Noteworthy changes in version 0.2.1 (2001-04-02)
1924 ------------------------------------------------
1926 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1928 * Handle GnuPG's new key capabilities output and support revocation
1931 * Made the W32 support more robust.
1934 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
1937 This file is free software; as a special exception the author gives
1938 unlimited permission to copy and/or distribute it, with or without
1939 modifications, as long as this notice is preserved.
1941 This file is distributed in the hope that it will be useful, but
1942 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1943 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.