1 Noteworthy changes in version 1.11.1 (2018-04-20)
2 -------------------------------------------------
4 * Fixed build problems in the 1.11.0 release.
6 * Added C++ interfaces which were planned for 1.11.0.
8 * Interface changes relative to the 1.10.0 release:
9 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11 cpp: Key::lastUpdate NEW.
12 cpp: UserID::origin NEW.
13 cpp: UserID::lastUpdate NEW.
15 [c=C31/A20/R1 cpp=C13/A7/R0 qt=C10/A3/R2]
18 Noteworthy changes in version 1.11.0 (2018-04-18)
19 -------------------------------------------------
21 * New encryption API to support direct key specification including
22 hidden recipients option and taking keys from a file. This also
23 allows to enforce the use of a subkey.
25 * New encryption flag for the new API to enforce the use of plain
26 mail addresses (addr-spec).
28 * The import API can now tell whether v3 keys are skipped. These old
29 and basically broken keys are not anymore supported by GnuPG 2.1.
31 * The decrypt and verify API will now return the MIME flag as
32 specified by RFC-4880bis.
34 * The offline mode now has an effect on gpg by disabling all network
37 * A failed OpenPGP verification how returns the fingerprint of the
38 intended key if a recent gpg version was used for signature
41 * New tool gpgme-json as native messaging server for web browsers.
42 As of now public key encryption and decryption is supported.
43 Requires Libgpg-error 1.29.
45 * New context flag "request-origin" which has an effect when used
46 with GnuPG 2.2.6 or later.
48 * New context flag "no-symkey-cache" which has an effect when used
49 with GnuPG 2.2.7 or later.
51 * New convenience constant GPGME_KEYLIST_MODE_LOCATE.
53 * Improved the Python documentation.
55 * Fixed a potential regression with GnuPG 2.2.6 or later.
57 * Fixed a crash in the Python bindings on 32 bit platforms. [#3892]
59 * Various minor fixes.
61 * Interface changes relative to the 1.10.0 release:
62 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
63 gpgme_op_encrypt_ext NEW.
64 gpgme_op_encrypt_ext_start NEW.
65 gpgme_op_encrypt_sign_ext NEW.
66 gpgme_op_encrypt_sign_ext_start NEW.
67 GPGME_ENCRYPT_WANT_ADDRESS NEW.
68 GPGME_KEYLIST_MODE_LOCATE NEW.
69 gpgme_import_result_t EXTENDED: New field 'skipped_v3_keys'.
70 gpgme_decrypt_result_t EXTENDED: New field 'symkey_algo'.
71 gpgme_decrypt_result_t EXTENDED: New field 'is_mime'.
72 gpgme_verify_result_t EXTENDED: New field 'is_mime'.
74 cpp: Data::toString NEW.
75 cpp: ImportResult::numV3KeysSkipped NEW.
77 [c=C31/A20/R0 cpp=C12/A6/R0 qt=C10/A3/R1]
80 Noteworthy changes in version 1.10.0 (2017-12-12)
81 -------------------------------------------------
83 * Now returns more specific error codes for decryption to distinguish
84 between bad passphrase, user canceled, and no secret key.
86 * Now returns key origin information if available.
88 * Added context flag "auto-key-retrieve" to selectively enable the
89 corresponding gpg option.
91 * Added flag is_de_vs to decryption and verify results.
93 * py: Use SEEK_SET as default for data.seek.
95 * cpp: Various new APIs.
97 * Reduced spawn overhead on Linux again. Added new configure option
98 --disable-linux-getdents to disable this feature for very old
101 * Improved the Python bindings build system.
103 * Made the test suite less fragile.
105 * Interface changes relative to the 1.9.0 release:
106 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
107 gpgme_decrypt_result_t EXTENDED: New field 'is_de_vs'.
108 gpgme_signature_t EXTENDED: New field 'is_de_vs'.
110 gpgme_op_delete_ext NEW.
111 gpgme_op_delete_ext_start NEW.
112 GPGME_DELETE_ALLOW_SECRET NEW.
113 GPGME_DELETE_FORCE NEW.
114 gpgme_op_conf_dir NEW.
115 gpgme_set_ctx_flag EXTENDED: New flag 'auto-key-retrieve'.
116 cpp: DecryptionResult::isDeVs NEW.
117 cpp: Signature::isDeVs NEW.
118 cpp: EngineInfo::Version::operator> NEW.
119 cpp: Context::createKey NEW.
120 cpp: Context::startCreateKey NEW.
121 cpp: Context::createSubkey NEW.
122 cpp: Context::startCreateSubkey NEW.
124 py: DecryptResult EXTENDED: New boolean field 'is_de_vs'.
125 py: Signature EXTENDED: New boolean field 'is_de_vs'.
126 py: GpgError EXTENDED: Partial results in 'results'.
128 [c=C30/A19/R0 cpp=C11/A5/R0 qt=C10/A3/R0]
131 Noteworthy changes in version 1.9.0 (2017-03-28)
132 ------------------------------------------------
134 * Clarified meaning of the 'expire' parameter of gpgme_op_createkey
135 and gpgme_op_createsubkey. New flag to force a key without an
138 * New function gpgme_op_keylist_from_data_start to list keys from
139 data objects without importing them.
141 * New function gpgme_op_set_uid_flag to flag a key as primary.
143 * New function gpgme_op_decrypt_ext to run decryption with special
144 flags. This can for example be used to unwrap keys (remove only
145 the encryption layer).
147 * New encryption flags to wrap a key (adding an encryption layer to
148 an OpenPGP message) or to create anonymously encrypted messages.
150 * Support for adduid and revuid operations in the C++ bindings.
152 * Support for smartcard key generation in the C++ bindings.
154 * Several new functions for the Python binding.
156 * Many smaller bug fixes.
158 * Interface changes relative to the 1.8.0 release:
159 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
160 gpgme_op_createkey CHANGED: Meaning of 'expire' parameter.
161 gpgme_op_createsubkey CHANGED: Meaning of 'expire' parameter.
162 GPGME_CREATE_NOEXPIRE NEW.
163 gpgme_key_t EXTENDED: New field 'origin'.
164 gpgme_key_t EXTENDED: New field 'last_update'.
165 gpgme_subkey_t EXTENDED: New field 'is_de_vs'.
166 gpgme_user_id_t EXTENDED: New field 'origin'.
167 gpgme_user_id_t EXTENDED: New field 'last_update'.
168 gpgme_op_keylist_from_data_start NEW.
169 gpgme_op_set_uid_flag_start NEW.
170 gpgme_op_set_uid_flag NEW.
171 gpgme_op_decrypt_ext_start NEW.
172 gpgme_op_decrypt_ext NEW.
173 GPGME_ENCRYPT_THROW_KEYIDS NEW.
174 GPGME_ENCRYPT_WRAP NEW.
175 GPGME_DECRYPT_VERIFY NEW.
176 GPGME_DECRYPT_UNWRAP NEW.
177 gpgme_data_rewind UN-DEPRECATE.
178 cpp: Context::revUid(const Key&, const char*) NEW.
179 cpp: Context::startRevUid(const Key&, const char*) NEW.
180 cpp: Context::addUid(const Key&, const char*) NEW.
181 cpp: Context::startAddUid(const Key&, const char*) NEW.
182 cpp: Key::UserID::revoke() NEW.
183 cpp: Key::addUid() NEW.
184 cpp: Key::isDeVs NEW.
185 cpp: GpgGenCardKeyInteractor NEW.
186 cpp: Subkey::keyGrip NEW.
187 cpp: Subkey::isDeVs NEW.
188 cpp: Data::toKeys NEW.
189 cpp: Context::setDecryptFlags NEW.
190 cpp: Context::decrypt EXTENDED: Flags added.
191 cpp: Context::startDecrypt EXTENDED: Flags added.
192 cpp: Context::decryptAndVerify EXTENDED: Flags added.
193 cpp: Context::startCombinedDecryptionAndVerification EXTENDED: Flags.
194 cpp: Context::encryptFlags EXTENDED: New flags.
195 qt: CryptoConfig::stringValueList() NEW.
196 py: Context.__init__ EXTENDED: New keyword arg home_dir.
197 py: Context.home_dir NEW.
198 py: Context.keylist EXTENDED: New keyword arg mode.
199 py: Context.keylist EXTENDED: New keyword arg source.
200 py: Context.create_key NEW.
201 py: Context.create_subkey NEW.
202 py: Context.key_add_uid NEW.
203 py: Context.key_revoke_uid NEW.
204 py: Context.key_sign NEW.
205 py: Context.key_tofu_policy NEW.
206 py: core.pubkey_algo_string NEW.
207 py: core.addrspec_from_uid NEW.
209 [c=C29/A18/R0 cpp=C10/A4/R0 qt=C9/A2/R0]
212 Noteworthy changes in version 1.8.0 (2016-11-16)
213 ------------------------------------------------
215 * The module of the Python bindings has been renamed to 'gpg'.
217 * New interface to query current software versions.
219 * New feature to use gpg's --{show,override}session-key options.
221 * New interface to set the sender of a mail.
223 * qt: Added Distinguished Name parser from libkleo
225 * The --homedir option is now used with recent gpgconf versions.
227 * On 64 bit Windows systems gpgconf is now properly located.
229 * The internal locking functions have been replaced by libgpg-error
232 * Interface changes relative to the 1.7.1 release:
233 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
234 gpgme_set_sender NEW.
235 gpgme_get_sender NEW.
236 gpgme_op_query_swdb NEW.
237 gpgme_op_query_swdb_result NEW.
238 gpgme_query_swdb_result_t NEW.
239 gpgme_get_ctx_flag NEW.
240 gpgme_decrypt_result_t EXTENDED: New field session_key.
242 qt: DN::Attribute NEW.
243 qt: Job::context(Job*) NEW.
244 cpp: EngineInfo::Version::Version(const char*) NEW.
245 cpp: EngineInfo::Version::Version() NEW.
247 cpp: Context::setSender(const char*) NEW.
248 cpp: Context::getSender() NEW.
250 [c=C28/A17/R0 cpp=C9/A3/R0 qt=C8/A1/R0]
253 Noteworthy changes in version 1.7.1 (2016-10-18)
254 ------------------------------------------------
256 * Fixed problems with the new language bindings.
258 * New helper function gpgme_addrspec_from_uid.
260 * Use option --exit-on-status-write-error with newer gpg versions.
262 * qt: Missed API from the Qt Binding inclusion has
265 * qt: abstractimportjob.h is now installed to that
266 ImportJobs can be used again.
268 * qt: Fixed spelling error in API (startReceive).
270 * Interface changes relative to the 1.7.0 release:
271 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
272 gpgme_addrspec_from_uid NEW.
273 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
274 qt: MultiDeleteJob NEW.
275 qt: AbstractImportJob NEW.
277 cpp: Signature::key(bool, bool) NEW.
278 cpp: UserID::addrSpecFromString(const char*) NEW.
279 cpp: UserID::addrSpec() NEW.
281 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
284 Noteworthy changes in version 1.7.0 (2016-09-21)
285 ------------------------------------------------
287 * New language bindings for Python 2 and 3.
289 * New language Bindings for C++ and the Qt-Framework API.
291 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
292 key creation easier (requires GnuPG 2.1).
294 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
295 management easier (requires GnuPG 2.1).
297 * New function gpgme_op_keysign to make key signing easier (requires
300 * New function gpgme_op_interact to replace the now deprecated
301 functions gpgme_op_edit and gpgme_op_card_edit.
303 * New function gpgme_pubkey_algo_string to convert a public key
304 algorithm into a GnuPG 2.1 style string.
306 * Support for GnuPG 2.1's TOFU trust model.
308 * Notation flags are now correctly set on verify.
310 * New global flag "require-gnupg" to set a minimal gnupg version.
312 * More supported items in gpgme_get_dirinfo.
314 * New function gpgme_data_set_flag and flag "size-hint".
316 * New function gpgme_set_ctx_flag and flags "full-status" and
319 * Improved gpgme_data_identify to distinguish more file types.
321 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
322 mixed public key and symmetric encryption.
324 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
326 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
327 signed data is a valid MIME part. This is to support future GnuPG
330 * Interface changes relative to the 1.6.0 release:
331 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
332 gpgme_pubkey_algo_string NEW.
334 gpgme_set_ctx_flag NEW.
335 gpgme_data_set_flag NEW.
336 gpgme_op_createkey NEW.
337 gpgme_op_createkey_start NEW.
338 gpgme_op_createsubkey NEW.
339 gpgme_op_createsubkey_start NEW.
340 gpgme_op_adduid_start NEW.
342 gpgme_op_revuid_start NEW.
344 gpgme_op_keysign_start NEW.
345 gpgme_op_keysign NEW.
346 gpgme_op_tofu_policy_start NEW.
347 gpgme_op_tofu_policy NEW.
348 gpgme_op_interact_start NEW.
349 gpgme_op_interact NEW.
350 gpgme_interact_cb_t NEW.
351 gpgme_op_edit_start DEPRECATED.
352 gpgme_op_edit DEPRECATED.
353 gpgme_op_card_edit_start DEPRECATED.
354 gpgme_op_card_edit DEPRECATED.
355 gpgme_edit_cb_t DEPRECATED.
356 gpgme_status_code_t DEPRECATED.
357 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
358 gpgme_signature_t EXTENDED: New field key.
359 gpgme_key_t EXTENDED: New field fpr.
360 gpgme_subkey_t EXTENDED: New field keygrip.
361 gpgme_user_id_t EXTENDED: New field tofu.
362 gpgme_tofu_policy_t NEW.
363 gpgme_tofu_info_t NEW.
364 GPGME_STATUS_KEY_CONSIDERED NEW.
365 GPGME_STATUS_TOFU_USER NEW.
366 GPGME_STATUS_TOFU_STATS NEW.
367 GPGME_STATUS_TOFU_STATS_LONG NEW.
368 GPGME_STATUS_NOTATION_FLAGS NEW.
369 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
370 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
371 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
372 GPGME_DATA_ENCODING_MIME NEW.
373 GPGME_ENCRYPT_SYMMETRIC NEW.
374 GPGME_CREATE_SIGN NEW.
375 GPGME_CREATE_ENCR NEW.
376 GPGME_CREATE_CERT NEW.
377 GPGME_CREATE_AUTH NEW.
378 GPGME_CREATE_NOPASSWD NEW.
379 GPGME_CREATE_SELFSIGNED NEW.
380 GPGME_CREATE_NOSTORE NEW.
381 GPGME_CREATE_WANTPUB NEW.
382 GPGME_CREATE_WANTSEC NEW.
383 GPGME_CREATE_FORCE NEW.
384 GPGME_KEYSIGN_LOCAL NEW.
385 GPGME_KEYSIGN_LFSEP NEW.
386 GPGME_INTERACT_CARD NEW.
388 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
391 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
392 ------------------------------------------------
394 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
396 * Added gpgme_set_status_cb to allow a user to see some status
399 * Added an export mode for secret keys.
401 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
403 * The passphrase handler for the loopback mode has been improved and may
404 also be used with genkey.
406 * [w32] The standard GnuPG 2.1 install directory is now seached for
407 gpgconf.exe before a registry specified directory and the Gpg4win
410 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
413 * Interface changes relative to the 1.5.1 release:
414 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
415 gpgme_set_offline NEW.
416 gpgme_get_offline NEW.
417 gpgme_set_status_cb NEW.
418 gpgme_get_status_cb NEW.
419 GPGME_EXPORT_MODE_SECRET NEW
420 GPGME_EXPORT_MODE_RAW NEW.
421 GPGME_EXPORT_MODE_PKCS12 NEW.
424 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
425 ------------------------------------------------
427 * Fixed crash in key listings for user ids with a backslash.
429 * Fixed regression for GPGSM use with GnuPG < 2.1.
431 * Properly set signature summary for revoked OpenPGP keys.
434 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
435 ------------------------------------------------
437 * Fixed a possible crash in the debug code.
439 * Fixed building for Windows with newer versions of Mingw.
442 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
443 -------------------------------------------------------------
445 * The export key functions do now return an error if used with the
446 latest GnuPG version.
449 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
450 -------------------------------------------------------------
452 * gpgme-tool is now installed.
454 * Fix external listing for modern keyservers.
459 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
460 -------------------------------------------------------------
462 * Fixed possible overflow in gpgsm and uiserver engines.
465 * Added support for GnuPG 2.1's --with-secret option.
467 * Interface changes relative to the 1.5.0 release:
468 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
469 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
472 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
473 -------------------------------------------------------------
475 * On Unices the engine file names are not not anymore hardwired but
476 located via the envvar PATH. All options to set the name of the
477 engines for the configure run are removed.
479 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
480 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
481 is not found, GPGME looks for an engine named "gpg".
483 * New feature to use the gpgme I/O subsystem to run arbitrary
486 * New flag to use encryption without the default compression step.
488 * New function to access "gpg-conf --list-dirs"
490 * New configure option --enable-fixed-path for use by Android.
492 * Support ECC algorithms.
494 * Interface changes relative to the 1.4.3 release:
495 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
496 gpgme_get_dirinfo NEW.
497 gpgme_op_spawn_start NEW.
499 GPGME_PROTOCOL_SPAWN NEW.
500 GPGME_SPAWN_DETACHED NEW.
501 GPGME_SPAWN_ALLOW_SET_FG NEW.
502 GPGME_ENCRYPT_NO_COMPRESS NEW.
505 gpgme_subkey_t EXTENDED: New field curve.
506 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
507 GPGME_STATUS_MOUNTPOINT NEW.
508 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
509 GPGME_STATUS_ATTRIBUTE NEW.
510 GPGME_STATUS_BEGIN_SIGNING NEW.
511 GPGME_STATUS_KEY_NOT_CREATED NEW.
514 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
515 -------------------------------------------------------------
517 * The default engine names are now taken from the output of gpgconf.
518 If gpgconf is not found the use of gpg 1 is assumed.
520 * Under Windows the default engines names are first searched in the
521 installation directory of the gpgme DLL.
523 * New function gpgme_data_identify to detect the type of a message.
525 * Interface changes relative to the 1.4.2 release:
526 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
527 gpgme_signers_count NEW.
528 gpgme_data_type_t NEW.
529 gpgme_data_identify NEW.
532 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
533 -------------------------------------------------------------
535 * Allow symmetric encryption with gpgme_op_encrypt_sign.
537 * Fixed mismatching off_t definitions on Windows.
539 * Interface changes relative to the 1.4.1 release:
540 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
543 GPGME_PROTOCOL_OPENPGP NEW alias.
546 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
547 ------------------------------------------------------------
549 * Fixed reading of gpg.conf files with excessive use of the group
552 * Fixed building with the i686-w64-mingw32 toolchain.
554 * Disabled FD passing by default for Apple.
557 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
558 ------------------------------------------------------------
560 * New function gpgme_set_global_flag to help debugging on Android.
562 * New function gpgme_io_writen as a convenience wrapper around
565 * New functions to support the pinentry mode feature of GnuPG 2.1.
567 * New macro GPGME_VERSION_NUMBER to allow supporting different API
568 versions without the need for a configure test.
570 * Several improvements for gpgme-tool.
572 * Better logging of the common "invalid engine" error code.
574 * Support for FD passing is now enabled by default. The configure
575 option --disable-fd-passing may be used to disable this.
577 * Interface changes relative to the 1.3.1 release:
578 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
579 GPGME_VERSION_NUMBER NEW.
581 gpgme_set_global_flag NEW.
582 gpgme_set_pinentry_mode NEW.
583 gpgme_get_pinentry_mode NEW.
584 gpgme_pinentry_mode_t NEW.
585 GPGME_PINENTRY_MODE_DEFAULT NEW.
586 GPGME_PINENTRY_MODE_ASK NEW.
587 GPGME_PINENTRY_MODE_CANCEL NEW.
588 GPGME_PINENTRY_MODE_ERROR NEW.
589 GPGME_PINENTRY_MODE_LOOPBACK NEW.
592 Noteworthy changes in version 1.3.2 (2012-05-02)
593 ------------------------------------------------
595 * Remove support for libgpgme-pth. As far as we know, this was never used,
596 and GnuPG is going to use our own npth in the future.
598 * Fix signature summary information for a missing X.509 key.
600 * Fix parsing of dates >= year 2038.
603 Noteworthy changes in version 1.3.1 (2011-06-16)
604 ------------------------------------------------
606 * Ported to Windows CE.
608 * Detect GPG versions not supporting ---passwd.
610 * Interface changes relative to the 1.3.0 release:
611 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
612 GPGME_EXPORT_MODE_MINIMAL NEW
613 GPGME_STATUS_SUCCESS NEW
614 gpgme_err_code_from_syserror NEW
615 gpgme_err_set_errno NEW
616 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
617 gpgme_error_from_syserror NEW
618 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
621 Noteworthy changes in version 1.3.0 (2010-01-11)
622 ------------------------------------------------
624 * GPGME does not come with an internal libassuan version anymore.
625 The external libassuan 1.1.0 release or later is required. For
626 application programmers on systems that can resolve inter-library
627 dependencies at runtime, this is a transparent change.
629 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
631 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
633 * New API to change the passphrase of a key.
635 * Interface changes relative to the 1.2.0 release:
636 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
637 GPGME_STATUS_INV_SGNR NEW.
638 GPGME_STATUS_NO_SGNR NEW.
639 GPGME_PROTOCOL_G13 NEW.
640 gpgme_op_g13_mount NEW.
641 gpgme_g13_result_t NEW.
644 gpgme_op_passwd_start NEW.
646 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
649 Noteworthy changes in version 1.2.0 (2009-06-18)
650 ------------------------------------------------
652 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
655 * gpgme_new will fail if gpgme_check_version was not called, or a
656 selftest failed (for example, if -mms-bitfields was not used on
659 * New functions gpgme_io_read and gpgme_io_write for use with
660 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
662 * New functions gpgme_result_ref and gpgme_result_unref to detach
663 result structures from a context.
665 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
666 that allow to specify exported keys through gpgme_key_t objects
669 * New mode of operation gpgme_export_mode_t that allows exporting
672 * Interface changes relative to the 1.1.7 release:
673 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
674 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
675 GPGME_PROTOCOL_ASSUAN NEW.
676 gpgme_assuan_data_cb_t NEW.
677 gpgme_assuan_inquire_cb_t NEW.
678 gpgme_assuan_status_cb_t NEW.
679 gpgme_op_assuan_transact_start NEW.
680 gpgme_op_assuan_transact NEW.
681 gpgme_op_assuan_result NEW.
682 gpgme_op_import_keys NEW.
683 gpgme_op_import_keys_start NEW.
684 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
685 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
686 gpgme_check_version CHANGED: Is now a macro.
687 gpgme_new EXTENDED: More failure codes.
690 gpgme_result_ref NEW.
691 gpgme_result_unref NEW.
692 gpgme_export_mode_t NEW.
693 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
694 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
695 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
696 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
697 gpgme_op_export_keys_start NEW.
698 gpgme_op_export_keys NEW.
699 GPGME_DATA_ENCODING_URL NEW.
700 GPGME_DATA_ENCODING_URL0 NEW.
701 GPGME_DATA_ENCODING_URLESC NEW.
702 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
705 Noteworthy changes in version 1.1.8 (2008-12-08)
706 ------------------------------------------------
708 * SIGPIPE is now again ignored as described in the manual. Fixes
709 regresion introduced with 1.1.6.
712 Noteworthy changes in version 1.1.7 (2008-10-17)
713 ------------------------------------------------
715 * Using GPGME_KEYLIST_MODE_LOCAL combined with
716 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
717 --locate-keys feature of gpg (>= 2.0.10).
719 * The encoding of gpgme_data_t objects can affect the output encoding
720 of export, sign and encrypt operations now (the same operations
721 that are also affected by the ASCII mode switch). We believe this
722 change in the ABI is innocent enough not to break existing
723 applications (it only affects the S/MIME backend on certain
726 * The reference manual now includes the specification of "The GnuPG
729 * A new function gpgme_cancel_async can be used to asynchronously
730 cancel any pending operation at any time, from any thread.
732 * Interface changes relative to the 1.1.6 release:
733 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
734 gpgme_op_encrypt CHANGED: Output encoding can affect result.
735 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
736 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
737 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
738 gpgme_op_sign CHANGED: Output encoding can affect result.
739 gpgme_op_sign_start CHANGED: Output encoding can affect result.
740 gpgme_op_export CHANGED: Output encoding can affect result.
741 gpgme_op_export_start CHANGED: Output encoding can affect result.
742 gpgme_op_export_ext CHANGED: Output encoding can affect result.
743 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
744 gpgme_cancel_async NEW
745 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
748 Noteworthy changes in version 1.1.6 (2008-01-04)
749 ------------------------------------------------
751 * Bug fixes for for W32.
753 * A new, experimental (and thus undocumented and potentially
754 unstable) interface for accessing gpg-conf through GPGME has been
757 * Interface changes relative to the 1.1.1 release:
758 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
759 gpgme_signature_t EXTENDED: New field chain_model.
760 gpgme_op_getauditlog_start NEW.
761 gpgme_op_getauditlog NEW.
762 GPGME_AUDITLOG_HTML NEW.
763 GPGME_AUDITLOG_WITH_HELP NEW.
764 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
767 Noteworthy changes in version 1.1.5 (2007-07-09)
768 ------------------------------------------------
770 * Bug and portability fixes (mainly for W32).
773 Noteworthy changes in version 1.1.4 (2007-03-05)
774 ------------------------------------------------
776 * Detect and bail out on double plaintext messages. This is required
777 so that applications can properly detect the signed parts of a
778 message. Actual there is now a double protection as GnuPG 1.4.7
779 will detect this case too.
782 Noteworthy changes in version 1.1.3 (2007-01-29)
783 ------------------------------------------------
785 * Fixed a memory leak in gpgme_data_release_and_get_mem.
787 * Fixed a bug in Windows command line quoting.
790 Noteworthy changes in version 1.1.2 (2006-03-02)
791 ------------------------------------------------
793 * Fixed a bug in the W32 glib backend.
796 Noteworthy changes in version 1.1.1 (2006-02-23)
797 ------------------------------------------------
799 * Fixed a bug in that the fingerprints of subkeys are not available.
801 * Clarified usage of the SECRET flag in key listings. It is now
804 * Reading signature notations and policy URLs on key signatures is
805 supported. They can be found in the new field notations of the
806 gpgme_key_sig_t structure. This has to be enabled with the keylist
807 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
809 * A new gpgme_free() function solves the problem of using different
810 allocators in a single program. This function should now be used
811 instead calling free() to release the buffer returned by
812 gpgme_data_release_and_get_mem. It is recommended that you always
813 do this, but it is only necessary on certain platforms, so backwards
814 compatibility is provided. In other words: If free() worked for
815 you before, it will keep working.
817 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
818 They are analyzed by the verify handlers and made available in the
819 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
821 * Interface changes relative to the 1.1.0 release:
822 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
823 gpgme_key_sig_t EXTENDED: New field notations.
824 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
826 GPGME_STATUS_PKA_TRUST_BAD NEW
827 GPGME_STATUS_PKA_TRUST_GOOD NEW
828 gpgme_signature_t EXTENDED: New field pka_trust.
829 gpgme_signature_t EXTENDED: New field pka_address.
830 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
833 Noteworthy changes in version 1.1.0 (2005-10-01)
834 ------------------------------------------------
836 * You can now configure the backend engine file name and home
837 directory to be used, as default and per context.
839 * Information about the recipients of an encrypted text is now
840 available at decryption time.
842 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
843 and verify handlers, the information about the plaintext filename,
844 if available is made available in the new field file_name of the
845 respective result structure.
847 * The code for "automagically detecting the thread library" has been
848 removed from libgpgme. It is deprecated since version 0.4.3.
849 Since then, you had to link against libgpgme-pthread for
850 applications using pthread and libgpgme-pth for applications using
853 The code was removed because it caused compilation problems on
854 systems where the pthread.h header from GNU Pth is available in
855 addition to the system header (FreeBSD 6 and later for example).
857 * "./autogen.sh --build-w32" does now build gpgme.dll.
859 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
860 delimiter. The standard install directory is used when locating
861 gpg or gpgsm before finally falling back to the hardwired name.
863 * There is a new flag for keys and subkeys, is_qualified, which
864 indicates if a key can be used for qualified signatures according
865 to local government regulations.
867 * You can associate a filename with a data object using the new
868 function gpgme_data_set_file_name(). This filename will be stored
869 in the output when encrypting or signing the data and will be
870 returned when decrypting or verifying the output data.
872 * You can now set notation data at signature creation with the new
873 function gpgme_sig_notation_add().
875 * Interface changes relative to the 1.0.3 release:
876 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
877 gpgme_set_engine_info NEW
878 gpgme_ctx_get_engine_info NEW
879 gpgme_ctx_set_engine_info NEW
880 gpgme_recipient_t NEW
881 gpgme_decrypt_result_t EXTENDED: New field recipients.
882 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
883 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
884 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
885 GPGME_STATUS_PLAINTEXT NEW
886 gpgme_key_t EXTENDED: New field is_qualified.
887 gpgme_subkey_t EXTENDED: New field is_qualified.
888 gpgme_data_get_file_name NEW
889 gpgme_data_set_file_name NEW
890 gpgme_sig_notation_flags_t NEW
891 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
892 GPGME_SIG_NOTATAION_CRITICAL NEW
893 gpgme_sig_notation_clear NEW
894 gpgme_sig_notation_add NEW
895 gpgme_sig_notation_get NEW
896 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
899 Noteworthy changes in version 1.0.3 (2005-06-20)
900 ------------------------------------------------
902 * Previousy, GPGME would use a default "include certs" of 1. This
903 has been changed. Now GPGME will use the crypto backend engines
904 default unless you set the value with gpgme_set_include_certs()
905 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
906 as a value to explicitely request the new default behaviour.
908 Because the default changes, this is a slight change of the API
909 semantics. We consider it to be a bug fix.
911 * A bug which made GPGME hang has been fixed. If you have
912 experienced hanging before, please try out this version and let me
913 know if you still experience hanging problems.
915 * Interface changes relative to the 0.9.0 release:
916 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
917 gpgme_set_include_certs CHANGED DEFAULT
918 GPGME_INCLUDE_CERTS_DEFAULT NEW
919 GPGME_STATUS_SIG_SUBPACKET NEW
920 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
921 GPGME_STATUS_SC_OP_FAILURE NEW
922 GPGME_STATUS_SC_OP_SUCCESS NEW
923 GPGME_STATUS_CARDCTRL NEW
924 GPGME_STATUS_BACKUP_KEY_CREATED NEW
925 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
928 Noteworthy changes in version 1.0.2 (2004-12-28)
929 ------------------------------------------------
931 * Changed the license of the library to the GNU Lesser General Public
932 License (LGPL), version 2.1 or later.
935 Noteworthy changes in version 1.0.1 (2004-10-22)
936 ------------------------------------------------
941 Noteworthy changes in version 1.0.0 (2004-09-30)
942 ------------------------------------------------
944 * Version 1.0.0! We are proud to present you with a thoroughly
945 tested and stable version of the GPGME library. A big Thank You!
946 to all the people who made this possible.
948 The development will be branched into a stable 1.x.y series and the
951 * The gpgme.m4 macro supports checking the API version. Just prepend
952 it to the required version string, separated by a colon. For
953 example, this release has the version "1:1.0.0". The last release
954 to which this version is (mostly) ABI compatible is "1:0.4.2",
955 which is the default required version.
958 Noteworthy changes in version 0.9.0 (2004-06-08)
959 ------------------------------------------------
961 * The type gpgme_key_t has now a new field keylist_mode that contains
962 the keylist mode that was active at the time the key was retrieved.
964 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
965 that contains a flag indicating that the key should not have been
968 * Verifying a signature of a revoked key gives the correct result now
969 (GPG_ERR_CERT_REVOKED error code).
971 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
972 verify operations still allows you to look at the signature
975 * Clarified that patterns in keylisting operations have an upper
976 limit, and thus are not suited to list many keys at once by their
977 fingerprint. Also improve the error message if the pattern is too
978 long for the CMS protocol to handle.
980 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
981 gpgme_key_t EXTENDED: New field keylist_mode.
982 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
983 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
986 Noteworthy changes in version 0.4.7 (2004-04-29)
987 ------------------------------------------------
989 * Correctly initialize the fields expired, revoked, invalid, and
990 disabled in the gpgme_key_t structures.
992 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
993 accidently of type int instead unsigned int.
995 * Interface changes relative to the 0.4.5 release:
996 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
997 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
998 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1000 Noteworthy changes in version 0.4.6 (2004-04-06)
1001 ------------------------------------------------
1006 Noteworthy changes in version 0.4.5 (2004-03-07)
1007 ------------------------------------------------
1009 * GPGME is now compiled with LFS (large file support) by default.
1010 This means that _all_ programs using GPGME must be compiled with
1011 LFS support enabled by default. You can do this easily with
1012 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
1013 without autoconf by defining the preprocessor symbol
1014 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
1015 the C compiler command line, or by defining this preprocessor
1016 symbol before including any system header files). For more
1017 details, read the section on LFS in the manual.
1019 Up to now, it was undocumented that GPGME was not using LFS.
1020 But the public interfaces use off_t, and file descriptors are
1021 exchanged between the application and GPGME. This was an oversight,
1022 and bound to cause troubles in the future.
1024 Writing GPGME as a dual mode library that seamlessly supports LFS
1025 while keeping backwards compatibility is possible, but does not
1026 solve the problem: Many applications already expect GPGME to have
1027 LFS (they are compiled with off_t being a 64bit value). This is true
1028 in particular for the popular Gtk+ and Qt programs.
1030 So, although this is an ABI (but not an API) break, we will not
1031 change the library version to reflect that. Because the interfaces
1032 affected are probably not used yet in any GPGME 0.4 based
1033 application, we don't expect any real failures from this change.
1034 In fact, applications already using LFS will have some subtle bugs
1037 However, if you encounter an application using GPGME 0.4.x that
1038 does _not_ use LFS by default (off_t is a 32bit value), _and_
1039 uses at least one of the functions gpgme_data_seek,
1040 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
1041 gpgme_data_new_from_cbs, then indeed this library will be ABI
1042 incompatible with the program. As said above, we don't believe
1043 such a program exists. If we are in error, then you have two
1044 options: As a quick hack, you can configure GPGME with the
1045 --disable-largefile option. This will revert the change, and GPGME
1046 will not use LFS. However, GPGME will be incompatible with
1047 programs that expect GPGME to use LFS. All applications are
1048 required to use LFS when using GPGME, so this is only good as a
1049 temporary local work-around.
1051 The other option is to change the versioning of the library and
1052 recompile all applications. We have reserved a special version of
1053 the library for that, so you can do that without expecting a
1054 version clash in the future. Furthermore, everyone who does this
1055 will agree on the version to use (this is important for
1056 distribution makers). Read the comment in configure.ac (before
1057 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
1058 blindly: As stated above, we think it is unlikely this measure is
1059 needed. Still, it is there if necessary. If in doubt, contact us
1060 and we will give our advise for your specific situation.
1062 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
1065 * New interface gpgme_cancel() that can be used to cancel
1066 asynchronous operations.
1068 * Interface changes relative to the 0.4.4 release:
1069 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1070 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
1071 gpgme_data_seek CHANGED: off_t is now a largefile type.
1072 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
1073 GPGME_KEYLIST_MODE_VALIDATE NEW
1075 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1077 Noteworthy changes in version 0.4.4 (2004-01-12)
1078 ------------------------------------------------
1080 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
1081 been renamed to "sig_class", to avoid clash with C++ compilers. In
1082 the C API, the old name "class" has been preserved for backwards
1083 compatibility, but is deprecated.
1085 * Interface changes relative to the 0.4.3 release:
1086 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1087 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
1088 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
1089 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1091 Noteworthy changes in version 0.4.3 (2003-10-06)
1092 ------------------------------------------------
1094 * libgpgme should not be used for threaded programs anymore. This
1095 never worked reliably in all cases, because you had to
1096 be careful about the linking order and libtool wouldn't do that for
1097 you automatically. Instead, now you have to link against
1098 libgpgme-pthread for applications using pthread and libgpgme-pth for
1099 applications using GNU Pth.
1101 The old code for automagically detecting the thread library is
1102 still part of libgpgme, but it is DEPRECATED.
1104 * There are new automake macros AM_PATH_GPGME_PTH and
1105 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
1106 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
1107 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
1108 variables of course also include the configuration for the thread
1109 package itself. Alternatively, use libtool.
1111 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
1114 * gpgme-config doesn't support setting the prefix or exec prefix
1115 anymore. I don't think it ever worked correctly, and it seems to
1118 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
1119 provided was not unique, instead returning the first matching key.
1121 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
1122 that indicates if the key can be used for authentication.
1124 * gpgme_signature_t's status field is now correctly set to an error
1125 with error code GPG_ERR_NO_PUBKEY if public key is not found.
1127 * gpgme_new_signature_t's class field is now an unsigned int, rather
1128 than an unsigned long (the old class field is preserved for
1129 backwards compatibility).
1131 * A new function gpgme_set_locale() is provided to allow configuring
1132 the locale for the crypto backend. This is necessary for text
1133 terminals so that programs like the pinentry can be started with
1134 the right locale settings for the terminal the application is running
1135 on, in case the terminal has different settings than the system
1136 default (for example, if it is a remote terminal). You are highly
1137 recommended to call the following functions directly after
1138 gpgme_check_version:
1142 setlocale (LC_ALL, "");
1143 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
1144 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
1146 GPGME can not do this for you, as setlocale is not thread safe, and
1147 there is no alternative.
1149 * The signal action for SIGPIPE is now set to SIG_IGN by
1150 gpgme_check_version, instead the first time a crypto engine is
1151 started (which is not well defined).
1153 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
1154 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
1155 to CRC24RFC2440. For now, these strings can be used as the MIC
1156 parameter for PGP/MIME (if appropriately modified).
1158 * Interface changes relative to the 0.4.2 release:
1159 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1160 gpgme_strerror_t NEW
1161 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
1162 gpgme_key_t EXTENDED: New field can_authenticate.
1163 gpgme_subkey_t EXTENDED: New field can_authenticate.
1164 gpgme_new_signature_t CHANGED: New type for class field.
1165 gpgme_set_locale NEW
1166 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
1167 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1169 Noteworthy changes in version 0.4.2 (2003-07-30)
1170 ------------------------------------------------
1172 * Allow gpg-error to be in non-standard place when linking the test suite.
1174 * Configure will fail now if gpg-error can not be found.
1176 * Fixed initialized memory backed data objects for writing, which
1177 caused the test program to crash (but only on Mac OS, surprisingly).
1179 * Eliminate use of C99 constructs.
1181 * Small improvements to the manual.
1184 Noteworthy changes in version 0.4.1 (2003-06-06)
1185 ------------------------------------------------
1187 This is the release that 0.4.0 should have been. There are many
1188 interface changes, please see below for the details. The changes are
1189 sometimes the result of new functionality, but more often express a
1190 paradigm shift. Others are an overdue cleanup to get GPGME in line
1191 with the GNU coding standards and to make the interface more
1192 self-consistent. Here is an overview on the changes:
1194 All types have been renamed to conform to the GNU coding standards,
1195 most of the time by keeping the whole name in lowercase and inserting
1196 underscores between words.
1198 All operations consistently only accept input parameters in their
1199 invocation function, and return only an error code directly. Further
1200 information about the result of the operation has to be retrieved
1201 afterwards by calling one of the result functions. This unifies the
1202 synchronous and the asynchronous interface.
1204 The error values have been completely replaced by a more
1205 sophisticated model that allows GPGME to transparently and accurately
1206 report all errors from the other GnuPG components, irregardless of
1207 process boundaries. This is achieved by using the library
1208 libgpg-errors, which is shared by all GnuPG components. This library
1209 is now required for GPGME.
1211 The results of all operations are now provided by pointers to C
1212 structs rather than by XML structs or in other ways.
1214 Objects which used to be opaque (for example a key) are now pointers
1215 to accessible structs, so no accessor functions are necessary.
1217 Backward compatibility is provided where it was possible without too
1218 much effort and did not collide with the overall sanitization effort.
1219 However, this is only for ease of transition. NO DEPRECATED FUNCTION
1220 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
1221 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
1222 Recommendations how to replace deprecated or removed functionality
1223 can be found within the description of each change.
1225 What follows are all changes to the interface and behaviour of GPGME
1228 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
1229 deprecated attributes will warn about use of obsolete functions and
1230 type definitions. You can suppress these warnings by passing
1231 -Wno-deprecated-declarations to the gcc command.
1233 * The following types have been renamed. The old types are still
1234 available as aliases, but they are deprecated now:
1236 GpgmeCtx gpgme_ctx_t
1237 GpgmeData gpgme_data_t
1238 GpgmeError gpgme_error_t
1239 GpgmeDataEncoding gpgme_data_encoding_t
1240 GpgmeSigStat gpgme_sig_stat_t
1241 GpgmeSigMode gpgme_sig_mode_t
1242 GpgmeAttr gpgme_attr_t
1243 GpgmeValidity gpgme_validity_t
1244 GpgmeProtocol gpgme_protocol_t
1245 GpgmeKey gpgme_key_t
1246 GpgmePassphraseCb gpgme_passphrase_cb_t
1247 GpgmeProgressCb gpgme_progress_cb_t
1248 GpgmeIOCb gpgme_io_cb_t
1249 GpgmeRegisterIOCb gpgme_register_io_cb_t
1250 GpgmeRemoveIOCb gpgme_remove_io_cb_t
1251 GpgmeEventIO gpgme_event_io_t
1252 GpgmeEventIOCb gpgme_event_io_cb_t
1253 GpgmeIOCbs gpgme_io_cbs
1254 GpgmeDataReadCb gpgme_data_read_cb_t
1255 GpgmeDataWriteCb gpgme_data_write_cb_t
1256 GpgmeDataSeekCb gpgme_data_seek_cb_t
1257 GpgmeDataReleaseCb gpgme_data_release_cb_t
1258 GpgmeDataCbs gpgme_data_cbs_t
1259 GpgmeTrustItem gpgme_trust_item_t
1260 GpgmeStatusCode gpgme_status_code_t
1262 * gpgme_error_t is now identical to gpg_error_t, the error type
1263 provided by libgpg-error. More about using libgpg-error with GPGME
1264 can be found in the manual. All error symbols have been removed!
1266 * All functions and types in libgpg-error have been wrapped in GPGME.
1267 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1268 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1269 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1270 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1273 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1275 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1276 for encrypt, sign, encrypt-sign, decrypt, verify, and
1277 decrypt-verify operations. For verify operations on detached
1278 signatures, the progress callback is invoked for both the detached
1279 signature and the plaintext message, though.
1281 * gpgme_passphrase_cb_t has been changed to not provide a complete
1282 description, but the UID hint, passphrase info and a flag
1283 indicating if this is a repeated attempt individually, so the user
1284 can compose his own description from this information.
1286 The passphrase is not returned as a C string, but must be written
1287 to a file descriptor directly. This allows for secure passphrase
1290 The return type has been changed to gpgme_error_t value. This
1291 allowed to remove the gpgme_cancel function; just return
1292 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1294 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1295 The user is expected to write the response to the file descriptor,
1296 followed by a newline.
1298 * The recipients interface has been removed. Instead, you use
1299 NULL-terminated lists of keys for specifying the recipients of an
1300 encryption operation. Use the new encryption flag
1301 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1302 the keys (but note that in general this is not a good idea).
1304 This change has been made to the prototypes of gpgme_op_encrypt,
1305 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1306 gpgme_op_encrypt_sign_start.
1308 The export interface has been changed to use pattern strings like
1309 the keylist interface. Thus, new functions gpgme_op_export_ext and
1310 gpgme_op_export_ext_start have been added as well. Now the
1311 prototypes of gpgme_op_export_start and gpgme_op_export finally
1314 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1315 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1318 * gpgme_io_cb_t changed from a void function to a function returning
1319 a gpgme_error_t value. However, it will always return 0, so you
1320 can safely ignore the return value.
1322 * A new I/O callback event GPGME_EVENT_START has been added. The new
1323 requirement is that you must wait until this event until you are
1324 allowed to call the I/O callback handlers previously registered for
1325 this context operation. Calling I/O callback functions for this
1326 context operation before the start event happened is unsafe because
1327 it can lead to race conditions in a multi-threaded environment.
1329 * The idle function feature has been removed. It was not precisely
1330 defined in a multi-threaded environment and is obsoleted by the
1331 user I/O callback functions. If you still need a simple way to
1332 call something while waiting on one or multiple asynchronous
1333 operations to complete, don't set the HANG flag in gpgme_wait (note
1334 that this will return to your program more often than the idle
1337 * gpgme_wait can return NULL even if hang is true, if an error
1338 occurs. In that case *status contains the error code.
1340 * gpgme_get_engine_info was radically changed. Instead an XML
1341 string, an info structure of the new type gpgme_engine_info_t is
1342 returned. This makes it easier and more robust to evaluate the
1343 information in an application.
1345 * The new function gpgme_get_protocol_name can be used to convert a
1346 gpgme_protocol_t value into a string.
1348 * The status of a context operation is not checked anymore. Starting
1349 a new operation will silently cancel the previous one. Calling a
1350 function that requires you to have started an operation before without
1351 doing so is undefined.
1353 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1354 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1355 pointer to a structure which contains the fingerprint. This also
1356 works with gpgme_op_genkey_start. The structure also provides
1357 other information about the generated keys.
1362 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1364 printf ("%s\n", fpr);
1368 gpgme_genkey_result_t result;
1369 err = gpgme_op_genkey (ctx, NULL, NULL);
1372 result = gpgme_op_genkey_result (ctx);
1374 printf ("%s\n", result->fpr);
1377 * The new gpgme_op_import_result function provides detailed
1378 information about the result of an import operation in
1379 gpgme_import_result_t and gpgme_import_status_t objects.
1380 Thus, the gpgme_op_import_ext variant is deprecated.
1382 * The new gpgme_op_sign_result function provides detailed information
1383 about the result of a signing operation in gpgme_sign_result_t,
1384 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1386 * The new gpgme_op_encrypt_result function provides detailed
1387 information about the result of an encryption operation in
1388 a GpgmeEncryptResult object.
1390 * The new gpgme_op_decrypt_result function provides detailed
1391 information about the result of a decryption operation in
1392 a GpgmeDecryptResult object.
1394 * The new gpgme_op_verify_result function provides detailed
1395 information about the result of an verify operation in
1396 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1397 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1398 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1399 and gpgme_get_notation is removed.
1401 * GpgmeTrustItem objects have now directly accessible data, so the
1402 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1403 accessor functions are deprecated. Also, reference counting is
1404 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1405 (the gpgme_trust_item_release alias for the latter is deprecated).
1407 * Keys are not cached internally anymore, so the force_update argument
1408 to gpgme_get_key has been removed.
1410 * GpgmeKey objects have now directly accessible data so the
1411 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1412 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1413 functions are deprecated. Also, gpgme_key_release is now
1414 deprecated. The gpgme_key_get_as_xml function has been dropped.
1416 * Because all interfaces using attributes are deprecated, the
1417 GpgmeAttr data type is also deprecated.
1419 * The new gpgme_op_keylist_result function provides detailed
1420 information about the result of a key listing operation in
1421 a GpgmeKeyListResult object.
1423 * Now that each function comes with its own result retrieval
1424 interface, the generic gpgme_get_op_info interface is not useful
1425 anymore and dropped.
1427 * The type and mode of data objects is not available anymore.
1429 * Interface changes relative to the 0.4.0 release:
1430 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1431 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1432 GpgmeData DEPRECATED: Use gpgme_data_t.
1433 GpgmeError DEPRECATED: Use gpgme_error_t.
1434 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1435 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1436 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1437 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1438 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1439 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1440 GpgmeKey DEPRECATED: Use gpgme_key_t.
1441 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1442 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1443 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1444 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1445 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1446 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1447 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1448 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1449 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1450 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1451 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1452 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1453 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1454 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1455 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1458 gpgme_recipients_t NEW
1460 gpgme_data_encoding_t NEW
1461 gpgme_sig_stat_t NEW
1462 gpgme_sig_mode_t NEW
1464 gpgme_validity_t NEW
1465 gpgme_protocol_t NEW
1467 gpgme_passphrase_cb_t NEW
1468 gpgme_progress_cb_t NEW
1470 gpgme_register_io_cb_t NEW
1471 gpgme_remove_io_cb_t NEW
1472 gpgme_event_io_t NEW
1473 gpgme_event_io_cb_t NEW
1475 gpgme_data_read_cb_t NEW
1476 gpgme_data_write_cb_t NEW
1477 gpgme_data_seek_cb_t NEW
1478 gpgme_data_release_cb_t NEW
1479 gpgme_data_cbs_t NEW
1480 gpgme_trust_item_t NEW
1481 gpgme_status_code_t NEW
1482 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1483 gpgme_err_code_t NEW
1484 gpgme_err_source_t NEW
1486 gpgme_err_source NEW
1489 gpgme_error_from_errno NEW
1490 gpgme_err_make_from_errno NEW
1491 gpgme_err_code_from_errno NEW
1492 gpgme_err_code_to_errno NEW
1494 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1495 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1496 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1497 gpgme_edit_cb_t CHANGED: Write directly to FD.
1498 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1499 gpgme_op_verify CHANGED: Drop R_STAT argument.
1500 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1501 gpgme_wait CHANGED: Can return NULL even if hang is true.
1502 GpgmeIdleFunc REMOVED
1503 gpgme_register_idle REMOVED
1504 GpgmeRecipients REMOVED
1505 gpgme_recipients_new REMOVED
1506 gpgme_recipients_release REMOVED
1507 gpgme_recipients_add_name REMOVED
1508 gpgme_recipients_add_name_with_validity REMOVED
1509 gpgme_recipients_count REMOVED
1510 gpgme_recipients_enum_open REMOVED
1511 gpgme_recipients_enum_read REMOVED
1512 gpgme_recipients_enum_close REMOVED
1513 gpgme_encrypt_flags_t NEW
1514 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1515 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1516 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1517 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1518 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1519 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1520 gpgme_op_export CHANGED: User IDs passed as patterns.
1521 gpgme_op_export_ext_start NEW
1522 gpgme_op_export_ext NEW
1523 gpgme_keylist_mode_t NEW
1525 gpgme_engine_info_t NEW
1526 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1527 gpgme_get_protocol_name NEW
1528 gpgme_cancel REMOVED: Return error in callback directly.
1529 gpgme_op_genkey CHANGED: FPR argument dropped.
1530 gpgme_op_genkey_result NEW
1531 gpgme_genkey_result_t NEW
1532 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1533 gpgme_op_import_result NEW
1534 gpgme_import_status_t NEW
1535 gpgme_import_result_t NEW
1536 gpgme_pubkey_algo_t NEW
1537 gpgme_hash_algo_t NEW
1538 gpgme_invalid_key_t NEW
1539 gpgme_new_signature_t NEW
1540 gpgme_sign_result_t NEW
1541 gpgme_op_sign_result NEW
1542 gpgme_pubkey_algo_name NEW
1543 gpgme_hash_algo_name NEW
1544 gpgme_encrypt_result_t NEW
1545 gpgme_op_encrypt_result NEW
1546 gpgme_decrypt_result_t NEW
1547 gpgme_op_decrypt_result NEW
1548 gpgme_verify_result_t NEW
1549 gpgme_op_verify_result NEW
1550 gpgme_get_notation REMOVED: Access verify result directly instead.
1551 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1552 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1553 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1554 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1555 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1556 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1557 gpgme_trust_item_ref NEW
1558 gpgme_trust_item_unref NEW
1559 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1560 gpgme_trust_item_get_string_attr DEPRECATED
1561 gpgme_trust_item_get_ulong_attr DEPRECATED
1562 gpgme_get_key CHANGED: Removed force_update argument.
1566 gpgme_key_t CHANGED: Now has user accessible data members.
1567 gpgme_key_get_string_attr DEPRECATED
1568 gpgme_key_get_ulong_attr DEPRECATED
1569 gpgme_key_sig_get_string_attr DEPRECATED
1570 gpgme_key_sig_get_ulong_attr DEPRECATED
1571 gpgme_key_get_as_xml REMOVED
1572 gpgme_key_list_result_t NEW
1573 gpgme_op_keylist_result NEW
1574 gpgme_get_op_info REMOVED
1575 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1577 Noteworthy changes in version 0.4.0 (2002-12-23)
1578 ------------------------------------------------
1580 * Key generation returns the fingerprint of the generated key.
1582 * New convenience function gpgme_get_key.
1584 * Supports signatures of user IDs in keys via the new
1585 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1586 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1587 interfaces. The XML info about a key also includes the signatures
1590 * New data object interface, which is more flexible and transparent.
1592 * Interface changes relative to the 0.3.9 release:
1593 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1595 GpgmeDataWriteCb NEW
1597 GpgmeDataReleaseCb NEW
1599 gpgme_data_read CHANGED: Match read() closely.
1600 gpgme_data_write CHANGED: Match write() closely.
1602 gpgme_data_new_from_fd NEW
1603 gpgme_data_new_from_stream NEW
1604 gpgme_data_new_from_cbs NEW
1605 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1606 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1607 gpgme_data_get_type REMOVED: No replacement.
1608 gpgme_op_verify CHANGED: Take different data objects for
1609 signed text and plain text.
1610 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1611 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1612 gpgme_op_genkey CHANGED: New parameter FPR.
1613 GPGME_KEYLIST_MODE_SIGS NEW
1614 gpgme_key_sig_get_string_attr NEW
1615 gpgme_key_sig_get_ulong_attr NEW
1617 GPGME_ATTR_SIG_CLASS NEW
1618 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1620 Noteworthy changes in version 0.3.16 (2003-11-19)
1621 -------------------------------------------------
1623 * Compatibility fixes for GnuPG 1.9.x
1625 Noteworthy changes in version 0.3.15 (2003-02-18)
1626 -------------------------------------------------
1628 * The progress status is sent via the progress callbacks in
1631 * Bug fix for signing operations with explicit signer settings for
1634 Noteworthy changes in version 0.3.14 (2002-12-04)
1635 -------------------------------------------------
1637 * GPGME-Plug is now in its own package "cryptplug".
1639 * Workaround for a setlocale problem. Fixed a segv related to not
1640 correctly as closed marked file descriptors.
1642 Noteworthy changes in version 0.3.13 (2002-11-20)
1643 -------------------------------------------------
1645 * Release due to changes in gpgmeplug.
1647 Noteworthy changes in version 0.3.12 (2002-10-15)
1648 -------------------------------------------------
1650 * Fixed some bux with key listings.
1652 * The development has been branched to clean up some API issues.
1653 This 0.3 series will be kept for compatibility reasons; so do don't
1654 expect new features.
1656 Noteworthy changes in version 0.3.11 (2002-09-20)
1657 -------------------------------------------------
1661 Noteworthy changes in version 0.3.10 (2002-09-02)
1662 -------------------------------------------------
1664 * Setting the signing keys for the CMS protocol does now work.
1666 * The signers setting is honoured by gpgme_op_edit.
1668 Noteworthy changes in version 0.3.9 (2002-08-21)
1669 ------------------------------------------------
1671 * A spec file for creating RPMs has been added.
1673 * An experimental interface to GnuPG's --edit-key functionality is
1674 introduced, see gpgme_op_edit.
1676 * The new gpgme_import_ext function provides a convenient access to
1677 the number of processed keys.
1679 * Interface changes relative to the 0.3.8 release:
1680 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1683 gpgme_op_edit_start NEW
1685 gpgme_op_import_ext NEW
1686 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1688 Noteworthy changes in version 0.3.8 (2002-06-25)
1689 ------------------------------------------------
1691 * It is possible to use an outside event loop for the I/O to the
1692 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1694 * Interface changes relative to the 0.3.6 release:
1695 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1697 GpgmeRegisterIOCb NEW
1701 struct GpgmeIOCbs NEW
1702 gpgme_set_io_cbs NEW
1703 gpgme_get_io_cbs NEW
1704 GPGME_ATTR_ERRTOK NEW
1705 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1707 Noteworthy changes in version 0.3.7 (2002-06-04)
1708 ------------------------------------------------
1710 * GPGME_ATTR_OTRUST is implemented now.
1712 * A first step toward thread safeness has been achieved, see the
1713 documentation for details. Supported thread libraries are pthread
1716 Noteworthy changes in version 0.3.6 (2002-05-03)
1717 ------------------------------------------------
1719 * All error output of the gpgsm backend is send to the bit bucket.
1721 * The signature verification functions are extended. Instead of
1722 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1723 expired signatures. 2 new functions may be used to retrieve more
1724 detailed information like the signature expiration time and a
1725 validity information of the key without an extra key looking.
1727 * The current passphrase callback and progress meter callback can be
1728 retrieved with the new functions gpgme_get_passphrase_cb and
1729 gpgme_get_progress_cb respectively.
1731 * Interface changes relative to the 0.3.5 release:
1732 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1733 gpgme_get_passphrase_cb NEW
1734 gpgme_get_progress_cb NEW
1735 GpgmeDataEncoding NEW
1736 gpgme_data_set_encoding NEW
1737 gpgme_data_get_encoding NEW
1738 GPGME_SIG_STAT_GOOD_EXP NEW
1739 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1740 gpgme_op_verify CHANGED: Returns more status codes.
1741 GPGME_ATTR_SIG_STATUS NEW
1742 gpgme_get_sig_string_attr NEW
1743 gpgme_get_sig_ulong_attr NEW
1744 gpgme_get_protocol NEW
1745 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1747 Noteworthy changes in version 0.3.5 (2002-04-01)
1748 ------------------------------------------------
1750 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1751 case, symmetric encryption is performed. Note that this requires a
1752 passphrase from the user.
1754 * More information is returned for X.509 certificates.
1756 * Interface changes relative to the 0.3.4 release:
1757 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1758 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1759 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1761 Noteworthy changes in version 0.3.4 (2002-03-04)
1762 ------------------------------------------------
1764 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1765 some recipients have been invalid, whereas earlier versions
1766 succeeded in this case. The plaintext is still encrypted for all valid
1767 recipients, so the application might take this error as a hint that
1768 the ciphertext is not usable for all requested recipients.
1769 Information about invalid recipients is available with gpgme_get_op_info.
1771 * gpgme_op_verify now allows to pass an uninitialized data object as
1772 its plaintext argument to check for normal and cleartext
1773 signatures. The plaintext is then returned in the data object.
1775 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1776 to set and get the number of certifications to include in S/MIME
1779 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1780 to encrypt and sign a message in a combined operation.
1782 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1784 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1786 * Interface changes relative to the 0.3.3 release:
1787 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1788 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1789 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1790 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1791 gpgme_set_include_certs NEW
1792 gpgme_get_include_certs NEW
1793 gpgme_op_encrypt_sign NEW
1794 gpgme_op_encrypt_sign_start NEW
1795 gpgme_op_keylist_ext_start NEW
1796 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1798 Noteworthy changes in version 0.3.3 (2002-02-12)
1799 ------------------------------------------------
1801 * Fix the Makefile in jnlib.
1803 * Fix the test suite (hopefully). It should clean up all its state
1804 with `make check' now.
1807 Noteworthy changes in version 0.3.2 (2002-02-10)
1808 ------------------------------------------------
1810 * Remove erroneous dependency on libgcrypt in jnlib.
1813 Noteworthy changes in version 0.3.1 (2002-02-09)
1814 ------------------------------------------------
1816 * There is a Texinfo manual documenting the API.
1818 * The gpgme_set_keylist_mode function returns an error, and changed
1819 its meaning. It is no longer usable to select between normal and
1820 fast mode (newer versions of GnuPG will always be fast), but
1821 selects between local keyring, remote keyserver, or both.
1822 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1823 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1824 current setting, a fucntion gpgme_get_keylist_mode was added to
1825 retrieve the current mode.
1827 * gpgme_wait accepts a new argument STATUS to return the error status
1828 of the operation on the context. Its definition is closer to
1829 waitpid() now than before.
1831 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1832 type from off_t to the unsigned size_t.
1834 * The R_HD argument to the GpgmePassphraseCb type changed its type
1835 from void* to void**.
1837 * New interface gpgme_op_trustlist_end() to match
1838 gpgme_op_keylist_end().
1840 * The CryptPlug modules have been renamed to gpgme-openpgp and
1841 gpgme-smime, and they are installed in pkglibdir by `make install'.
1843 * An idle function can be registered with gpgme_register_idle().
1845 * The GpgSM backend supports key generation with gpgme_op_genkey().
1847 * Interface changes relative to the 0.3.0 release:
1848 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1849 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1850 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1851 gpgme_wait CHANGED: New argument STATUS.
1852 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1853 The function has a new meaning!
1854 gpgme_get_keylist_mode NEW
1855 GPGME_KEYLIST_MODE_LOCAL NEW
1856 GPGME_KEYLIST_MODE_EXTERN NEW
1857 gpgme_op_trustlist_next NEW
1859 gpgme_register_idle NEW
1860 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1862 Noteworthy changes in version 0.3.0 (2001-12-19)
1863 ------------------------------------------------
1865 * New interface gpgme_set_protocol() to set the protocol and thus the
1866 crypto engine to be used by the context. Currently, the OpenPGP
1867 and the CMS protocols are supported. They are specified by the new
1868 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1869 A new context uses the OpenPGP engine by default.
1871 * gpgme_get_engine_info() returns information for all crypto engines
1872 compiled into the library. The XML format has changed. To
1873 reliably get the version of a crypto engine, the <version> tag
1874 after the appropriate <protocol> tag has to be looked for.
1876 * New interface gpgme_engine_check_version(), obsoleting
1877 gpgme_check_engine(). Check the version of all engines you are
1878 supporting in your software.
1880 * GpgmeKey lists the user ids in the order as they are returned by
1881 GnuPG, first the primary key with index 0, then the sub-user ids.
1883 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1884 signatures simultaneously.
1886 * The new interface gpgme_op_keylist_end() terminates a pending
1887 keylist operation. A keylist operation is also terminated when
1888 gpgme_op_keylist_next() returns GPGME_EOF.
1890 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1891 cross-compiled, or even compiled without support for GnuPG
1894 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1895 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1896 in the path, but it can also be compiled without support for GpgSM
1897 (`--without-gpgsm').
1899 * CryptPlug modules for GPGME are included and can be enabled at
1900 configure time (`--enable-gpgmeplug'). There is one module which
1901 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1902 GpgSM engine (`gpgsmplug').
1904 * Interface changes relative to the latest 0.2.x release:
1905 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1906 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1907 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1908 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1909 gpgme_get_engine_info CHANGED: New format, extended content.
1910 gpgme_engine_check_version NEW
1911 gpgme_decrypt_verify_start NEW
1912 gpgme_decrypt_verify NEW
1913 gpgme_op_keylist_next NEW
1914 gpgme_set_protocol NEW
1915 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1918 Noteworthy changes in version 0.2.3 (2001-09-17)
1919 ------------------------------------------------
1921 * New function gpgme_get_op_info which can be used to get the micalg
1922 parameter needed for MOSS.
1924 * New functions gpgme_get_armor and gpgme_get_textmode.
1926 * The usual bug fixes and some minor functionality improvements.
1928 * Added a simple encryption component for MS-Windows; however the
1929 build procedure might have some problems.
1932 Noteworthy changes in version 0.2.2 (2001-06-12)
1933 ------------------------------------------------
1935 * Implemented a key cache.
1937 * Fixed a race condition under W32 and some other bug fixes.
1940 Noteworthy changes in version 0.2.1 (2001-04-02)
1941 ------------------------------------------------
1943 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1945 * Handle GnuPG's new key capabilities output and support revocation
1948 * Made the W32 support more robust.
1951 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
1954 This file is free software; as a special exception the author gives
1955 unlimited permission to copy and/or distribute it, with or without
1956 modifications, as long as this notice is preserved.
1958 This file is distributed in the hope that it will be useful, but
1959 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1960 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.