1 Noteworthy changes in version 1.9.0 (2017-03-28)
2 ------------------------------------------------
4 * Clarified meaning of the 'expire' parameter of gpgme_op_createkey
5 and gpgme_op_createsubkey. New flag to force a key without an
8 * New function gpgme_op_keylist_from_data_start to list keys from
9 data objects without importing them.
11 * New function gpgme_op_set_uid_flag to flag a key as primary.
13 * New function gpgme_op_decrypt_ext to run decryption with special
14 flags. This can for example be used to unwrap keys (remove only
15 the encryption layer).
17 * New encryption flags to wrap a key (adding an encryption layer to
18 an OpenPGP message) or to create anonymously encrypted messages.
20 * Support for adduid and revuid operations in the C++ bindings.
22 * Support for smartcard key generation in the C++ bindings.
24 * Several new functions for the Python binding.
26 * Many smaller bug fixes.
29 * Interface changes relative to the 1.8.0 release:
30 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
31 gpgme_op_createkey CHANGED: Meaning of 'expire' parameter.
32 gpgme_op_createsubkey CHANGED: Meaning of 'expire' parameter.
33 GPGME_CREATE_NOEXPIRE NEW.
34 gpgme_key_t EXTENDED: New field 'origin'.
35 gpgme_key_t EXTENDED: New field 'last_update'.
36 gpgme_subkey_t EXTENDED: New field 'is_de_vs'.
37 gpgme_user_id_t EXTENDED: New field 'origin'.
38 gpgme_user_id_t EXTENDED: New field 'last_update'.
39 gpgme_op_keylist_from_data_start NEW.
40 gpgme_op_set_uid_flag_start NEW.
41 gpgme_op_set_uid_flag NEW.
42 gpgme_op_decrypt_ext_start NEW.
43 gpgme_op_decrypt_ext NEW.
44 GPGME_ENCRYPT_THROW_KEYIDS NEW.
45 GPGME_ENCRYPT_WRAP NEW.
46 GPGME_DECRYPT_VERIFY NEW.
47 GPGME_DECRYPT_UNWRAP NEW.
48 gpgme_data_rewind UN-DEPRECATE.
49 cpp: Context::revUid(const Key&, const char*) NEW.
50 cpp: Context::startRevUid(const Key&, const char*) NEW.
51 cpp: Context::addUid(const Key&, const char*) NEW.
52 cpp: Context::startAddUid(const Key&, const char*) NEW.
53 cpp: Key::UserID::revoke() NEW.
54 cpp: Key::addUid() NEW.
56 cpp: GpgGenCardKeyInteractor NEW.
57 cpp: Subkey::keyGrip NEW.
58 cpp: Subkey::isDeVs NEW.
59 cpp: Data::toKeys NEW.
60 cpp: Context::setDecryptFlags NEW.
61 cpp: Context::decrypt EXTENDED: Flags added.
62 cpp: Context::startDecrypt EXTENDED: Flags added.
63 cpp: Context::decryptAndVerify EXTENDED: Flags added.
64 cpp: Context::startCombinedDecryptionAndVerification EXTENDED: Flags.
65 cpp: Context::encryptFlags EXTENDED: New flags.
66 qt: CryptoConfig::stringValueList() NEW.
67 py: Context.__init__ EXTENDED: New keyword arg home_dir.
68 py: Context.home_dir NEW.
69 py: Context.keylist EXTENDED: New keyword arg mode.
70 py: Context.keylist EXTENDED: New keyword arg source.
71 py: Context.create_key NEW.
72 py: Context.create_subkey NEW.
73 py: Context.key_add_uid NEW.
74 py: Context.key_revoke_uid NEW.
75 py: Context.key_sign NEW.
76 py: Context.key_tofu_policy NEW.
77 py: core.pubkey_algo_string NEW.
78 py: core.addrspec_from_uid NEW.
80 [c=C29/A18/R0 cpp=C10/A4/R0 qt=C9/A2/R0]
83 Noteworthy changes in version 1.8.0 (2016-11-16)
84 ------------------------------------------------
86 * The module of the Python bindings has been renamed to 'gpg'.
88 * New interface to query current software versions.
90 * New feature to use gpg's --{show,override}session-key options.
92 * New interface to set the sender of a mail.
94 * qt: Added Distinguished Name parser from libkleo
96 * The --homedir option is now used with recent gpgconf versions.
98 * On 64 bit Windows systems gpgconf is now properly located.
100 * The internal locking functions have been replaced by libgpg-error
103 * Interface changes relative to the 1.7.1 release:
104 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
105 gpgme_set_sender NEW.
106 gpgme_get_sender NEW.
107 gpgme_op_query_swdb NEW.
108 gpgme_op_query_swdb_result NEW.
109 gpgme_query_swdb_result_t NEW.
110 gpgme_get_ctx_flag NEW.
111 gpgme_decrypt_result_t EXTENDED: New field session_key.
113 qt: DN::Attribute NEW.
114 qt: Job::context(Job*) NEW.
115 cpp: EngineInfo::Version::Version(const char*) NEW.
116 cpp: EngineInfo::Version::Version() NEW.
118 cpp: Context::setSender(const char*) NEW.
119 cpp: Context::getSender() NEW.
121 [c=C28/A17/R0 cpp=C9/A3/R0 qt=C8/A1/R0]
124 Noteworthy changes in version 1.7.1 (2016-10-18)
125 ------------------------------------------------
127 * Fixed problems with the new language bindings.
129 * New helper function gpgme_addrspec_from_uid.
131 * Use option --exit-on-status-write-error with newer gpg versions.
133 * qt: Missed API from the Qt Binding inclusion has
136 * qt: abstractimportjob.h is now installed to that
137 ImportJobs can be used again.
139 * qt: Fixed spelling error in API (startReceive).
141 * Interface changes relative to the 1.7.0 release:
142 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
143 gpgme_addrspec_from_uid NEW.
144 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
145 qt: MultiDeleteJob NEW.
146 qt: AbstractImportJob NEW.
148 cpp: Signature::key(bool, bool) NEW.
149 cpp: UserID::addrSpecFromString(const char*) NEW.
150 cpp: UserID::addrSpec() NEW.
152 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
155 Noteworthy changes in version 1.7.0 (2016-09-21)
156 ------------------------------------------------
158 * New language bindings for Python 2 and 3.
160 * New language Bindings for C++ and the Qt-Framework API.
162 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
163 key creation easier (requires GnuPG 2.1).
165 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
166 management easier (requires GnuPG 2.1).
168 * New function gpgme_op_keysign to make key signing easier (requires
171 * New function gpgme_op_interact to replace the now deprecated
172 functions gpgme_op_edit and gpgme_op_card_edit.
174 * New function gpgme_pubkey_algo_string to convert a public key
175 algorithm into a GnuPG 2.1 style string.
177 * Support for GnuPG 2.1's TOFU trust model.
179 * Notation flags are now correctly set on verify.
181 * New global flag "require-gnupg" to set a minimal gnupg version.
183 * More supported items in gpgme_get_dirinfo.
185 * New function gpgme_data_set_flag and flag "size-hint".
187 * New function gpgme_set_ctx_flag and flags "full-status" and
190 * Improved gpgme_data_identify to distinguish more file types.
192 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
193 mixed public key and symmetric encryption.
195 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
197 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
198 signed data is a valid MIME part. This is to support future GnuPG
201 * Interface changes relative to the 1.6.0 release:
202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
203 gpgme_pubkey_algo_string NEW.
205 gpgme_set_ctx_flag NEW.
206 gpgme_data_set_flag NEW.
207 gpgme_op_createkey NEW.
208 gpgme_op_createkey_start NEW.
209 gpgme_op_createsubkey NEW.
210 gpgme_op_createsubkey_start NEW.
211 gpgme_op_adduid_start NEW.
213 gpgme_op_revuid_start NEW.
215 gpgme_op_keysign_start NEW.
216 gpgme_op_keysign NEW.
217 gpgme_op_tofu_policy_start NEW.
218 gpgme_op_tofu_policy NEW.
219 gpgme_op_interact_start NEW.
220 gpgme_op_interact NEW.
221 gpgme_interact_cb_t NEW.
222 gpgme_op_edit_start DEPRECATED.
223 gpgme_op_edit DEPRECATED.
224 gpgme_op_card_edit_start DEPRECATED.
225 gpgme_op_card_edit DEPRECATED.
226 gpgme_edit_cb_t DEPRECATED.
227 gpgme_status_code_t DEPRECATED.
228 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
229 gpgme_signature_t EXTENDED: New field key.
230 gpgme_key_t EXTENDED: New field fpr.
231 gpgme_subkey_t EXTENDED: New field keygrip.
232 gpgme_user_id_t EXTENDED: New field tofu.
233 gpgme_tofu_policy_t NEW.
234 gpgme_tofu_info_t NEW.
235 GPGME_STATUS_KEY_CONSIDERED NEW.
236 GPGME_STATUS_TOFU_USER NEW.
237 GPGME_STATUS_TOFU_STATS NEW.
238 GPGME_STATUS_TOFU_STATS_LONG NEW.
239 GPGME_STATUS_NOTATION_FLAGS NEW.
240 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
241 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
242 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
243 GPGME_DATA_ENCODING_MIME NEW.
244 GPGME_ENCRYPT_SYMMETRIC NEW.
245 GPGME_CREATE_SIGN NEW.
246 GPGME_CREATE_ENCR NEW.
247 GPGME_CREATE_CERT NEW.
248 GPGME_CREATE_AUTH NEW.
249 GPGME_CREATE_NOPASSWD NEW.
250 GPGME_CREATE_SELFSIGNED NEW.
251 GPGME_CREATE_NOSTORE NEW.
252 GPGME_CREATE_WANTPUB NEW.
253 GPGME_CREATE_WANTSEC NEW.
254 GPGME_CREATE_FORCE NEW.
255 GPGME_KEYSIGN_LOCAL NEW.
256 GPGME_KEYSIGN_LFSEP NEW.
257 GPGME_INTERACT_CARD NEW.
259 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
262 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
263 ------------------------------------------------
265 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
267 * Added gpgme_set_status_cb to allow a user to see some status
270 * Added an export mode for secret keys.
272 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
274 * The passphrase handler for the loopback mode has been improved and may
275 also be used with genkey.
277 * [w32] The standard GnuPG 2.1 install directory is now seached for
278 gpgconf.exe before a registry specified directory and the Gpg4win
281 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
284 * Interface changes relative to the 1.5.1 release:
285 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
286 gpgme_set_offline NEW.
287 gpgme_get_offline NEW.
288 gpgme_set_status_cb NEW.
289 gpgme_get_status_cb NEW.
290 GPGME_EXPORT_MODE_SECRET NEW
291 GPGME_EXPORT_MODE_RAW NEW.
292 GPGME_EXPORT_MODE_PKCS12 NEW.
295 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
296 ------------------------------------------------
298 * Fixed crash in key listings for user ids with a backslash.
300 * Fixed regression for GPGSM use with GnuPG < 2.1.
302 * Properly set signature summary for revoked OpenPGP keys.
305 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
306 ------------------------------------------------
308 * Fixed a possible crash in the debug code.
310 * Fixed building for Windows with newer versions of Mingw.
313 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
314 -------------------------------------------------------------
316 * The export key functions do now return an error if used with the
317 latest GnuPG version.
320 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
321 -------------------------------------------------------------
323 * gpgme-tool is now installed.
325 * Fix external listing for modern keyservers.
330 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
331 -------------------------------------------------------------
333 * Fixed possible overflow in gpgsm and uiserver engines.
336 * Added support for GnuPG 2.1's --with-secret option.
338 * Interface changes relative to the 1.5.0 release:
339 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
340 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
343 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
344 -------------------------------------------------------------
346 * On Unices the engine file names are not not anymore hardwired but
347 located via the envvar PATH. All options to set the name of the
348 engines for the configure run are removed.
350 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
351 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
352 is not found, GPGME looks for an engine named "gpg".
354 * New feature to use the gpgme I/O subsystem to run arbitrary
357 * New flag to use encryption without the default compression step.
359 * New function to access "gpg-conf --list-dirs"
361 * New configure option --enable-fixed-path for use by Android.
363 * Support ECC algorithms.
365 * Interface changes relative to the 1.4.3 release:
366 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
367 gpgme_get_dirinfo NEW.
368 gpgme_op_spawn_start NEW.
370 GPGME_PROTOCOL_SPAWN NEW.
371 GPGME_SPAWN_DETACHED NEW.
372 GPGME_SPAWN_ALLOW_SET_FG NEW.
373 GPGME_ENCRYPT_NO_COMPRESS NEW.
376 gpgme_subkey_t EXTENDED: New field curve.
377 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
378 GPGME_STATUS_MOUNTPOINT NEW.
379 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
380 GPGME_STATUS_ATTRIBUTE NEW.
381 GPGME_STATUS_BEGIN_SIGNING NEW.
382 GPGME_STATUS_KEY_NOT_CREATED NEW.
385 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
386 -------------------------------------------------------------
388 * The default engine names are now taken from the output of gpgconf.
389 If gpgconf is not found the use of gpg 1 is assumed.
391 * Under Windows the default engines names are first searched in the
392 installation directory of the gpgme DLL.
394 * New function gpgme_data_identify to detect the type of a message.
396 * Interface changes relative to the 1.4.2 release:
397 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
398 gpgme_signers_count NEW.
399 gpgme_data_type_t NEW.
400 gpgme_data_identify NEW.
403 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
404 -------------------------------------------------------------
406 * Allow symmetric encryption with gpgme_op_encrypt_sign.
408 * Fixed mismatching off_t definitions on Windows.
410 * Interface changes relative to the 1.4.1 release:
411 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
414 GPGME_PROTOCOL_OPENPGP NEW alias.
417 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
418 ------------------------------------------------------------
420 * Fixed reading of gpg.conf files with excessive use of the group
423 * Fixed building with the i686-w64-mingw32 toolchain.
425 * Disabled FD passing by default for Apple.
428 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
429 ------------------------------------------------------------
431 * New function gpgme_set_global_flag to help debugging on Android.
433 * New function gpgme_io_writen as a convenience wrapper around
436 * New functions to support the pinentry mode feature of GnuPG 2.1.
438 * New macro GPGME_VERSION_NUMBER to allow supporting different API
439 versions without the need for a configure test.
441 * Several improvements for gpgme-tool.
443 * Better logging of the common "invalid engine" error code.
445 * Support for FD passing is now enabled by default. The configure
446 option --disable-fd-passing may be used to disable this.
448 * Interface changes relative to the 1.3.1 release:
449 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
450 GPGME_VERSION_NUMBER NEW.
452 gpgme_set_global_flag NEW.
453 gpgme_set_pinentry_mode NEW.
454 gpgme_get_pinentry_mode NEW.
455 gpgme_pinentry_mode_t NEW.
456 GPGME_PINENTRY_MODE_DEFAULT NEW.
457 GPGME_PINENTRY_MODE_ASK NEW.
458 GPGME_PINENTRY_MODE_CANCEL NEW.
459 GPGME_PINENTRY_MODE_ERROR NEW.
460 GPGME_PINENTRY_MODE_LOOPBACK NEW.
463 Noteworthy changes in version 1.3.2 (2012-05-02)
464 ------------------------------------------------
466 * Remove support for libgpgme-pth. As far as we know, this was never used,
467 and GnuPG is going to use our own npth in the future.
469 * Fix signature summary information for a missing X.509 key.
471 * Fix parsing of dates >= year 2038.
474 Noteworthy changes in version 1.3.1 (2011-06-16)
475 ------------------------------------------------
477 * Ported to Windows CE.
479 * Detect GPG versions not supporting ---passwd.
481 * Interface changes relative to the 1.3.0 release:
482 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
483 GPGME_EXPORT_MODE_MINIMAL NEW
484 GPGME_STATUS_SUCCESS NEW
485 gpgme_err_code_from_syserror NEW
486 gpgme_err_set_errno NEW
487 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
488 gpgme_error_from_syserror NEW
489 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
492 Noteworthy changes in version 1.3.0 (2010-01-11)
493 ------------------------------------------------
495 * GPGME does not come with an internal libassuan version anymore.
496 The external libassuan 1.1.0 release or later is required. For
497 application programmers on systems that can resolve inter-library
498 dependencies at runtime, this is a transparent change.
500 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
502 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
504 * New API to change the passphrase of a key.
506 * Interface changes relative to the 1.2.0 release:
507 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
508 GPGME_STATUS_INV_SGNR NEW.
509 GPGME_STATUS_NO_SGNR NEW.
510 GPGME_PROTOCOL_G13 NEW.
511 gpgme_op_g13_mount NEW.
512 gpgme_g13_result_t NEW.
515 gpgme_op_passwd_start NEW.
517 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
520 Noteworthy changes in version 1.2.0 (2009-06-18)
521 ------------------------------------------------
523 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
526 * gpgme_new will fail if gpgme_check_version was not called, or a
527 selftest failed (for example, if -mms-bitfields was not used on
530 * New functions gpgme_io_read and gpgme_io_write for use with
531 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
533 * New functions gpgme_result_ref and gpgme_result_unref to detach
534 result structures from a context.
536 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
537 that allow to specify exported keys through gpgme_key_t objects
540 * New mode of operation gpgme_export_mode_t that allows exporting
543 * Interface changes relative to the 1.1.7 release:
544 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
545 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
546 GPGME_PROTOCOL_ASSUAN NEW.
547 gpgme_assuan_data_cb_t NEW.
548 gpgme_assuan_inquire_cb_t NEW.
549 gpgme_assuan_status_cb_t NEW.
550 gpgme_op_assuan_transact_start NEW.
551 gpgme_op_assuan_transact NEW.
552 gpgme_op_assuan_result NEW.
553 gpgme_op_import_keys NEW.
554 gpgme_op_import_keys_start NEW.
555 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
556 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
557 gpgme_check_version CHANGED: Is now a macro.
558 gpgme_new EXTENDED: More failure codes.
561 gpgme_result_ref NEW.
562 gpgme_result_unref NEW.
563 gpgme_export_mode_t NEW.
564 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
565 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
566 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
567 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
568 gpgme_op_export_keys_start NEW.
569 gpgme_op_export_keys NEW.
570 GPGME_DATA_ENCODING_URL NEW.
571 GPGME_DATA_ENCODING_URL0 NEW.
572 GPGME_DATA_ENCODING_URLESC NEW.
573 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
576 Noteworthy changes in version 1.1.8 (2008-12-08)
577 ------------------------------------------------
579 * SIGPIPE is now again ignored as described in the manual. Fixes
580 regresion introduced with 1.1.6.
583 Noteworthy changes in version 1.1.7 (2008-10-17)
584 ------------------------------------------------
586 * Using GPGME_KEYLIST_MODE_LOCAL combined with
587 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
588 --locate-keys feature of gpg (>= 2.0.10).
590 * The encoding of gpgme_data_t objects can affect the output encoding
591 of export, sign and encrypt operations now (the same operations
592 that are also affected by the ASCII mode switch). We believe this
593 change in the ABI is innocent enough not to break existing
594 applications (it only affects the S/MIME backend on certain
597 * The reference manual now includes the specification of "The GnuPG
600 * A new function gpgme_cancel_async can be used to asynchronously
601 cancel any pending operation at any time, from any thread.
603 * Interface changes relative to the 1.1.6 release:
604 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
605 gpgme_op_encrypt CHANGED: Output encoding can affect result.
606 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
607 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
608 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
609 gpgme_op_sign CHANGED: Output encoding can affect result.
610 gpgme_op_sign_start CHANGED: Output encoding can affect result.
611 gpgme_op_export CHANGED: Output encoding can affect result.
612 gpgme_op_export_start CHANGED: Output encoding can affect result.
613 gpgme_op_export_ext CHANGED: Output encoding can affect result.
614 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
615 gpgme_cancel_async NEW
616 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
619 Noteworthy changes in version 1.1.6 (2008-01-04)
620 ------------------------------------------------
622 * Bug fixes for for W32.
624 * A new, experimental (and thus undocumented and potentially
625 unstable) interface for accessing gpg-conf through GPGME has been
628 * Interface changes relative to the 1.1.1 release:
629 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
630 gpgme_signature_t EXTENDED: New field chain_model.
631 gpgme_op_getauditlog_start NEW.
632 gpgme_op_getauditlog NEW.
633 GPGME_AUDITLOG_HTML NEW.
634 GPGME_AUDITLOG_WITH_HELP NEW.
635 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
638 Noteworthy changes in version 1.1.5 (2007-07-09)
639 ------------------------------------------------
641 * Bug and portability fixes (mainly for W32).
644 Noteworthy changes in version 1.1.4 (2007-03-05)
645 ------------------------------------------------
647 * Detect and bail out on double plaintext messages. This is required
648 so that applications can properly detect the signed parts of a
649 message. Actual there is now a double protection as GnuPG 1.4.7
650 will detect this case too.
653 Noteworthy changes in version 1.1.3 (2007-01-29)
654 ------------------------------------------------
656 * Fixed a memory leak in gpgme_data_release_and_get_mem.
658 * Fixed a bug in Windows command line quoting.
661 Noteworthy changes in version 1.1.2 (2006-03-02)
662 ------------------------------------------------
664 * Fixed a bug in the W32 glib backend.
667 Noteworthy changes in version 1.1.1 (2006-02-23)
668 ------------------------------------------------
670 * Fixed a bug in that the fingerprints of subkeys are not available.
672 * Clarified usage of the SECRET flag in key listings. It is now
675 * Reading signature notations and policy URLs on key signatures is
676 supported. They can be found in the new field notations of the
677 gpgme_key_sig_t structure. This has to be enabled with the keylist
678 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
680 * A new gpgme_free() function solves the problem of using different
681 allocators in a single program. This function should now be used
682 instead calling free() to release the buffer returned by
683 gpgme_data_release_and_get_mem. It is recommended that you always
684 do this, but it is only necessary on certain platforms, so backwards
685 compatibility is provided. In other words: If free() worked for
686 you before, it will keep working.
688 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
689 They are analyzed by the verify handlers and made available in the
690 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
692 * Interface changes relative to the 1.1.0 release:
693 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
694 gpgme_key_sig_t EXTENDED: New field notations.
695 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
697 GPGME_STATUS_PKA_TRUST_BAD NEW
698 GPGME_STATUS_PKA_TRUST_GOOD NEW
699 gpgme_signature_t EXTENDED: New field pka_trust.
700 gpgme_signature_t EXTENDED: New field pka_address.
701 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
704 Noteworthy changes in version 1.1.0 (2005-10-01)
705 ------------------------------------------------
707 * You can now configure the backend engine file name and home
708 directory to be used, as default and per context.
710 * Information about the recipients of an encrypted text is now
711 available at decryption time.
713 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
714 and verify handlers, the information about the plaintext filename,
715 if available is made available in the new field file_name of the
716 respective result structure.
718 * The code for "automagically detecting the thread library" has been
719 removed from libgpgme. It is deprecated since version 0.4.3.
720 Since then, you had to link against libgpgme-pthread for
721 applications using pthread and libgpgme-pth for applications using
724 The code was removed because it caused compilation problems on
725 systems where the pthread.h header from GNU Pth is available in
726 addition to the system header (FreeBSD 6 and later for example).
728 * "./autogen.sh --build-w32" does now build gpgme.dll.
730 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
731 delimiter. The standard install directory is used when locating
732 gpg or gpgsm before finally falling back to the hardwired name.
734 * There is a new flag for keys and subkeys, is_qualified, which
735 indicates if a key can be used for qualified signatures according
736 to local government regulations.
738 * You can associate a filename with a data object using the new
739 function gpgme_data_set_file_name(). This filename will be stored
740 in the output when encrypting or signing the data and will be
741 returned when decrypting or verifying the output data.
743 * You can now set notation data at signature creation with the new
744 function gpgme_sig_notation_add().
746 * Interface changes relative to the 1.0.3 release:
747 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
748 gpgme_set_engine_info NEW
749 gpgme_ctx_get_engine_info NEW
750 gpgme_ctx_set_engine_info NEW
751 gpgme_recipient_t NEW
752 gpgme_decrypt_result_t EXTENDED: New field recipients.
753 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
754 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
755 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
756 GPGME_STATUS_PLAINTEXT NEW
757 gpgme_key_t EXTENDED: New field is_qualified.
758 gpgme_subkey_t EXTENDED: New field is_qualified.
759 gpgme_data_get_file_name NEW
760 gpgme_data_set_file_name NEW
761 gpgme_sig_notation_flags_t NEW
762 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
763 GPGME_SIG_NOTATAION_CRITICAL NEW
764 gpgme_sig_notation_clear NEW
765 gpgme_sig_notation_add NEW
766 gpgme_sig_notation_get NEW
767 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
770 Noteworthy changes in version 1.0.3 (2005-06-20)
771 ------------------------------------------------
773 * Previousy, GPGME would use a default "include certs" of 1. This
774 has been changed. Now GPGME will use the crypto backend engines
775 default unless you set the value with gpgme_set_include_certs()
776 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
777 as a value to explicitely request the new default behaviour.
779 Because the default changes, this is a slight change of the API
780 semantics. We consider it to be a bug fix.
782 * A bug which made GPGME hang has been fixed. If you have
783 experienced hanging before, please try out this version and let me
784 know if you still experience hanging problems.
786 * Interface changes relative to the 0.9.0 release:
787 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
788 gpgme_set_include_certs CHANGED DEFAULT
789 GPGME_INCLUDE_CERTS_DEFAULT NEW
790 GPGME_STATUS_SIG_SUBPACKET NEW
791 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
792 GPGME_STATUS_SC_OP_FAILURE NEW
793 GPGME_STATUS_SC_OP_SUCCESS NEW
794 GPGME_STATUS_CARDCTRL NEW
795 GPGME_STATUS_BACKUP_KEY_CREATED NEW
796 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
799 Noteworthy changes in version 1.0.2 (2004-12-28)
800 ------------------------------------------------
802 * Changed the license of the library to the GNU Lesser General Public
803 License (LGPL), version 2.1 or later.
806 Noteworthy changes in version 1.0.1 (2004-10-22)
807 ------------------------------------------------
812 Noteworthy changes in version 1.0.0 (2004-09-30)
813 ------------------------------------------------
815 * Version 1.0.0! We are proud to present you with a thoroughly
816 tested and stable version of the GPGME library. A big Thank You!
817 to all the people who made this possible.
819 The development will be branched into a stable 1.x.y series and the
822 * The gpgme.m4 macro supports checking the API version. Just prepend
823 it to the required version string, separated by a colon. For
824 example, this release has the version "1:1.0.0". The last release
825 to which this version is (mostly) ABI compatible is "1:0.4.2",
826 which is the default required version.
829 Noteworthy changes in version 0.9.0 (2004-06-08)
830 ------------------------------------------------
832 * The type gpgme_key_t has now a new field keylist_mode that contains
833 the keylist mode that was active at the time the key was retrieved.
835 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
836 that contains a flag indicating that the key should not have been
839 * Verifying a signature of a revoked key gives the correct result now
840 (GPG_ERR_CERT_REVOKED error code).
842 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
843 verify operations still allows you to look at the signature
846 * Clarified that patterns in keylisting operations have an upper
847 limit, and thus are not suited to list many keys at once by their
848 fingerprint. Also improve the error message if the pattern is too
849 long for the CMS protocol to handle.
851 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
852 gpgme_key_t EXTENDED: New field keylist_mode.
853 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
854 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
857 Noteworthy changes in version 0.4.7 (2004-04-29)
858 ------------------------------------------------
860 * Correctly initialize the fields expired, revoked, invalid, and
861 disabled in the gpgme_key_t structures.
863 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
864 accidently of type int instead unsigned int.
866 * Interface changes relative to the 0.4.5 release:
867 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
868 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
869 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
871 Noteworthy changes in version 0.4.6 (2004-04-06)
872 ------------------------------------------------
877 Noteworthy changes in version 0.4.5 (2004-03-07)
878 ------------------------------------------------
880 * GPGME is now compiled with LFS (large file support) by default.
881 This means that _all_ programs using GPGME must be compiled with
882 LFS support enabled by default. You can do this easily with
883 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
884 without autoconf by defining the preprocessor symbol
885 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
886 the C compiler command line, or by defining this preprocessor
887 symbol before including any system header files). For more
888 details, read the section on LFS in the manual.
890 Up to now, it was undocumented that GPGME was not using LFS.
891 But the public interfaces use off_t, and file descriptors are
892 exchanged between the application and GPGME. This was an oversight,
893 and bound to cause troubles in the future.
895 Writing GPGME as a dual mode library that seamlessly supports LFS
896 while keeping backwards compatibility is possible, but does not
897 solve the problem: Many applications already expect GPGME to have
898 LFS (they are compiled with off_t being a 64bit value). This is true
899 in particular for the popular Gtk+ and Qt programs.
901 So, although this is an ABI (but not an API) break, we will not
902 change the library version to reflect that. Because the interfaces
903 affected are probably not used yet in any GPGME 0.4 based
904 application, we don't expect any real failures from this change.
905 In fact, applications already using LFS will have some subtle bugs
908 However, if you encounter an application using GPGME 0.4.x that
909 does _not_ use LFS by default (off_t is a 32bit value), _and_
910 uses at least one of the functions gpgme_data_seek,
911 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
912 gpgme_data_new_from_cbs, then indeed this library will be ABI
913 incompatible with the program. As said above, we don't believe
914 such a program exists. If we are in error, then you have two
915 options: As a quick hack, you can configure GPGME with the
916 --disable-largefile option. This will revert the change, and GPGME
917 will not use LFS. However, GPGME will be incompatible with
918 programs that expect GPGME to use LFS. All applications are
919 required to use LFS when using GPGME, so this is only good as a
920 temporary local work-around.
922 The other option is to change the versioning of the library and
923 recompile all applications. We have reserved a special version of
924 the library for that, so you can do that without expecting a
925 version clash in the future. Furthermore, everyone who does this
926 will agree on the version to use (this is important for
927 distribution makers). Read the comment in configure.ac (before
928 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
929 blindly: As stated above, we think it is unlikely this measure is
930 needed. Still, it is there if necessary. If in doubt, contact us
931 and we will give our advise for your specific situation.
933 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
936 * New interface gpgme_cancel() that can be used to cancel
937 asynchronous operations.
939 * Interface changes relative to the 0.4.4 release:
940 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
941 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
942 gpgme_data_seek CHANGED: off_t is now a largefile type.
943 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
944 GPGME_KEYLIST_MODE_VALIDATE NEW
946 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
948 Noteworthy changes in version 0.4.4 (2004-01-12)
949 ------------------------------------------------
951 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
952 been renamed to "sig_class", to avoid clash with C++ compilers. In
953 the C API, the old name "class" has been preserved for backwards
954 compatibility, but is deprecated.
956 * Interface changes relative to the 0.4.3 release:
957 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
958 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
959 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
960 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
962 Noteworthy changes in version 0.4.3 (2003-10-06)
963 ------------------------------------------------
965 * libgpgme should not be used for threaded programs anymore. This
966 never worked reliably in all cases, because you had to
967 be careful about the linking order and libtool wouldn't do that for
968 you automatically. Instead, now you have to link against
969 libgpgme-pthread for applications using pthread and libgpgme-pth for
970 applications using GNU Pth.
972 The old code for automagically detecting the thread library is
973 still part of libgpgme, but it is DEPRECATED.
975 * There are new automake macros AM_PATH_GPGME_PTH and
976 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
977 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
978 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
979 variables of course also include the configuration for the thread
980 package itself. Alternatively, use libtool.
982 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
985 * gpgme-config doesn't support setting the prefix or exec prefix
986 anymore. I don't think it ever worked correctly, and it seems to
989 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
990 provided was not unique, instead returning the first matching key.
992 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
993 that indicates if the key can be used for authentication.
995 * gpgme_signature_t's status field is now correctly set to an error
996 with error code GPG_ERR_NO_PUBKEY if public key is not found.
998 * gpgme_new_signature_t's class field is now an unsigned int, rather
999 than an unsigned long (the old class field is preserved for
1000 backwards compatibility).
1002 * A new function gpgme_set_locale() is provided to allow configuring
1003 the locale for the crypto backend. This is necessary for text
1004 terminals so that programs like the pinentry can be started with
1005 the right locale settings for the terminal the application is running
1006 on, in case the terminal has different settings than the system
1007 default (for example, if it is a remote terminal). You are highly
1008 recommended to call the following functions directly after
1009 gpgme_check_version:
1013 setlocale (LC_ALL, "");
1014 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
1015 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
1017 GPGME can not do this for you, as setlocale is not thread safe, and
1018 there is no alternative.
1020 * The signal action for SIGPIPE is now set to SIG_IGN by
1021 gpgme_check_version, instead the first time a crypto engine is
1022 started (which is not well defined).
1024 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
1025 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
1026 to CRC24RFC2440. For now, these strings can be used as the MIC
1027 parameter for PGP/MIME (if appropriately modified).
1029 * Interface changes relative to the 0.4.2 release:
1030 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1031 gpgme_strerror_t NEW
1032 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
1033 gpgme_key_t EXTENDED: New field can_authenticate.
1034 gpgme_subkey_t EXTENDED: New field can_authenticate.
1035 gpgme_new_signature_t CHANGED: New type for class field.
1036 gpgme_set_locale NEW
1037 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
1038 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1040 Noteworthy changes in version 0.4.2 (2003-07-30)
1041 ------------------------------------------------
1043 * Allow gpg-error to be in non-standard place when linking the test suite.
1045 * Configure will fail now if gpg-error can not be found.
1047 * Fixed initialized memory backed data objects for writing, which
1048 caused the test program to crash (but only on Mac OS, surprisingly).
1050 * Eliminate use of C99 constructs.
1052 * Small improvements to the manual.
1055 Noteworthy changes in version 0.4.1 (2003-06-06)
1056 ------------------------------------------------
1058 This is the release that 0.4.0 should have been. There are many
1059 interface changes, please see below for the details. The changes are
1060 sometimes the result of new functionality, but more often express a
1061 paradigm shift. Others are an overdue cleanup to get GPGME in line
1062 with the GNU coding standards and to make the interface more
1063 self-consistent. Here is an overview on the changes:
1065 All types have been renamed to conform to the GNU coding standards,
1066 most of the time by keeping the whole name in lowercase and inserting
1067 underscores between words.
1069 All operations consistently only accept input parameters in their
1070 invocation function, and return only an error code directly. Further
1071 information about the result of the operation has to be retrieved
1072 afterwards by calling one of the result functions. This unifies the
1073 synchronous and the asynchronous interface.
1075 The error values have been completely replaced by a more
1076 sophisticated model that allows GPGME to transparently and accurately
1077 report all errors from the other GnuPG components, irregardless of
1078 process boundaries. This is achieved by using the library
1079 libgpg-errors, which is shared by all GnuPG components. This library
1080 is now required for GPGME.
1082 The results of all operations are now provided by pointers to C
1083 structs rather than by XML structs or in other ways.
1085 Objects which used to be opaque (for example a key) are now pointers
1086 to accessible structs, so no accessor functions are necessary.
1088 Backward compatibility is provided where it was possible without too
1089 much effort and did not collide with the overall sanitization effort.
1090 However, this is only for ease of transition. NO DEPRECATED FUNCTION
1091 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
1092 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
1093 Recommendations how to replace deprecated or removed functionality
1094 can be found within the description of each change.
1096 What follows are all changes to the interface and behaviour of GPGME
1099 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
1100 deprecated attributes will warn about use of obsolete functions and
1101 type definitions. You can suppress these warnings by passing
1102 -Wno-deprecated-declarations to the gcc command.
1104 * The following types have been renamed. The old types are still
1105 available as aliases, but they are deprecated now:
1107 GpgmeCtx gpgme_ctx_t
1108 GpgmeData gpgme_data_t
1109 GpgmeError gpgme_error_t
1110 GpgmeDataEncoding gpgme_data_encoding_t
1111 GpgmeSigStat gpgme_sig_stat_t
1112 GpgmeSigMode gpgme_sig_mode_t
1113 GpgmeAttr gpgme_attr_t
1114 GpgmeValidity gpgme_validity_t
1115 GpgmeProtocol gpgme_protocol_t
1116 GpgmeKey gpgme_key_t
1117 GpgmePassphraseCb gpgme_passphrase_cb_t
1118 GpgmeProgressCb gpgme_progress_cb_t
1119 GpgmeIOCb gpgme_io_cb_t
1120 GpgmeRegisterIOCb gpgme_register_io_cb_t
1121 GpgmeRemoveIOCb gpgme_remove_io_cb_t
1122 GpgmeEventIO gpgme_event_io_t
1123 GpgmeEventIOCb gpgme_event_io_cb_t
1124 GpgmeIOCbs gpgme_io_cbs
1125 GpgmeDataReadCb gpgme_data_read_cb_t
1126 GpgmeDataWriteCb gpgme_data_write_cb_t
1127 GpgmeDataSeekCb gpgme_data_seek_cb_t
1128 GpgmeDataReleaseCb gpgme_data_release_cb_t
1129 GpgmeDataCbs gpgme_data_cbs_t
1130 GpgmeTrustItem gpgme_trust_item_t
1131 GpgmeStatusCode gpgme_status_code_t
1133 * gpgme_error_t is now identical to gpg_error_t, the error type
1134 provided by libgpg-error. More about using libgpg-error with GPGME
1135 can be found in the manual. All error symbols have been removed!
1137 * All functions and types in libgpg-error have been wrapped in GPGME.
1138 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1139 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1140 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1141 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1144 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1146 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1147 for encrypt, sign, encrypt-sign, decrypt, verify, and
1148 decrypt-verify operations. For verify operations on detached
1149 signatures, the progress callback is invoked for both the detached
1150 signature and the plaintext message, though.
1152 * gpgme_passphrase_cb_t has been changed to not provide a complete
1153 description, but the UID hint, passphrase info and a flag
1154 indicating if this is a repeated attempt individually, so the user
1155 can compose his own description from this information.
1157 The passphrase is not returned as a C string, but must be written
1158 to a file descriptor directly. This allows for secure passphrase
1161 The return type has been changed to gpgme_error_t value. This
1162 allowed to remove the gpgme_cancel function; just return
1163 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1165 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1166 The user is expected to write the response to the file descriptor,
1167 followed by a newline.
1169 * The recipients interface has been removed. Instead, you use
1170 NULL-terminated lists of keys for specifying the recipients of an
1171 encryption operation. Use the new encryption flag
1172 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1173 the keys (but note that in general this is not a good idea).
1175 This change has been made to the prototypes of gpgme_op_encrypt,
1176 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1177 gpgme_op_encrypt_sign_start.
1179 The export interface has been changed to use pattern strings like
1180 the keylist interface. Thus, new functions gpgme_op_export_ext and
1181 gpgme_op_export_ext_start have been added as well. Now the
1182 prototypes of gpgme_op_export_start and gpgme_op_export finally
1185 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1186 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1189 * gpgme_io_cb_t changed from a void function to a function returning
1190 a gpgme_error_t value. However, it will always return 0, so you
1191 can safely ignore the return value.
1193 * A new I/O callback event GPGME_EVENT_START has been added. The new
1194 requirement is that you must wait until this event until you are
1195 allowed to call the I/O callback handlers previously registered for
1196 this context operation. Calling I/O callback functions for this
1197 context operation before the start event happened is unsafe because
1198 it can lead to race conditions in a multi-threaded environment.
1200 * The idle function feature has been removed. It was not precisely
1201 defined in a multi-threaded environment and is obsoleted by the
1202 user I/O callback functions. If you still need a simple way to
1203 call something while waiting on one or multiple asynchronous
1204 operations to complete, don't set the HANG flag in gpgme_wait (note
1205 that this will return to your program more often than the idle
1208 * gpgme_wait can return NULL even if hang is true, if an error
1209 occurs. In that case *status contains the error code.
1211 * gpgme_get_engine_info was radically changed. Instead an XML
1212 string, an info structure of the new type gpgme_engine_info_t is
1213 returned. This makes it easier and more robust to evaluate the
1214 information in an application.
1216 * The new function gpgme_get_protocol_name can be used to convert a
1217 gpgme_protocol_t value into a string.
1219 * The status of a context operation is not checked anymore. Starting
1220 a new operation will silently cancel the previous one. Calling a
1221 function that requires you to have started an operation before without
1222 doing so is undefined.
1224 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1225 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1226 pointer to a structure which contains the fingerprint. This also
1227 works with gpgme_op_genkey_start. The structure also provides
1228 other information about the generated keys.
1233 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1235 printf ("%s\n", fpr);
1239 gpgme_genkey_result_t result;
1240 err = gpgme_op_genkey (ctx, NULL, NULL);
1243 result = gpgme_op_genkey_result (ctx);
1245 printf ("%s\n", result->fpr);
1248 * The new gpgme_op_import_result function provides detailed
1249 information about the result of an import operation in
1250 gpgme_import_result_t and gpgme_import_status_t objects.
1251 Thus, the gpgme_op_import_ext variant is deprecated.
1253 * The new gpgme_op_sign_result function provides detailed information
1254 about the result of a signing operation in gpgme_sign_result_t,
1255 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1257 * The new gpgme_op_encrypt_result function provides detailed
1258 information about the result of an encryption operation in
1259 a GpgmeEncryptResult object.
1261 * The new gpgme_op_decrypt_result function provides detailed
1262 information about the result of a decryption operation in
1263 a GpgmeDecryptResult object.
1265 * The new gpgme_op_verify_result function provides detailed
1266 information about the result of an verify operation in
1267 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1268 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1269 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1270 and gpgme_get_notation is removed.
1272 * GpgmeTrustItem objects have now directly accessible data, so the
1273 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1274 accessor functions are deprecated. Also, reference counting is
1275 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1276 (the gpgme_trust_item_release alias for the latter is deprecated).
1278 * Keys are not cached internally anymore, so the force_update argument
1279 to gpgme_get_key has been removed.
1281 * GpgmeKey objects have now directly accessible data so the
1282 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1283 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1284 functions are deprecated. Also, gpgme_key_release is now
1285 deprecated. The gpgme_key_get_as_xml function has been dropped.
1287 * Because all interfaces using attributes are deprecated, the
1288 GpgmeAttr data type is also deprecated.
1290 * The new gpgme_op_keylist_result function provides detailed
1291 information about the result of a key listing operation in
1292 a GpgmeKeyListResult object.
1294 * Now that each function comes with its own result retrieval
1295 interface, the generic gpgme_get_op_info interface is not useful
1296 anymore and dropped.
1298 * The type and mode of data objects is not available anymore.
1300 * Interface changes relative to the 0.4.0 release:
1301 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1302 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1303 GpgmeData DEPRECATED: Use gpgme_data_t.
1304 GpgmeError DEPRECATED: Use gpgme_error_t.
1305 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1306 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1307 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1308 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1309 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1310 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1311 GpgmeKey DEPRECATED: Use gpgme_key_t.
1312 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1313 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1314 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1315 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1316 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1317 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1318 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1319 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1320 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1321 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1322 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1323 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1324 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1325 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1326 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1329 gpgme_recipients_t NEW
1331 gpgme_data_encoding_t NEW
1332 gpgme_sig_stat_t NEW
1333 gpgme_sig_mode_t NEW
1335 gpgme_validity_t NEW
1336 gpgme_protocol_t NEW
1338 gpgme_passphrase_cb_t NEW
1339 gpgme_progress_cb_t NEW
1341 gpgme_register_io_cb_t NEW
1342 gpgme_remove_io_cb_t NEW
1343 gpgme_event_io_t NEW
1344 gpgme_event_io_cb_t NEW
1346 gpgme_data_read_cb_t NEW
1347 gpgme_data_write_cb_t NEW
1348 gpgme_data_seek_cb_t NEW
1349 gpgme_data_release_cb_t NEW
1350 gpgme_data_cbs_t NEW
1351 gpgme_trust_item_t NEW
1352 gpgme_status_code_t NEW
1353 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1354 gpgme_err_code_t NEW
1355 gpgme_err_source_t NEW
1357 gpgme_err_source NEW
1360 gpgme_error_from_errno NEW
1361 gpgme_err_make_from_errno NEW
1362 gpgme_err_code_from_errno NEW
1363 gpgme_err_code_to_errno NEW
1365 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1366 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1367 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1368 gpgme_edit_cb_t CHANGED: Write directly to FD.
1369 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1370 gpgme_op_verify CHANGED: Drop R_STAT argument.
1371 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1372 gpgme_wait CHANGED: Can return NULL even if hang is true.
1373 GpgmeIdleFunc REMOVED
1374 gpgme_register_idle REMOVED
1375 GpgmeRecipients REMOVED
1376 gpgme_recipients_new REMOVED
1377 gpgme_recipients_release REMOVED
1378 gpgme_recipients_add_name REMOVED
1379 gpgme_recipients_add_name_with_validity REMOVED
1380 gpgme_recipients_count REMOVED
1381 gpgme_recipients_enum_open REMOVED
1382 gpgme_recipients_enum_read REMOVED
1383 gpgme_recipients_enum_close REMOVED
1384 gpgme_encrypt_flags_t NEW
1385 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1386 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1387 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1388 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1389 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1390 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1391 gpgme_op_export CHANGED: User IDs passed as patterns.
1392 gpgme_op_export_ext_start NEW
1393 gpgme_op_export_ext NEW
1394 gpgme_keylist_mode_t NEW
1396 gpgme_engine_info_t NEW
1397 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1398 gpgme_get_protocol_name NEW
1399 gpgme_cancel REMOVED: Return error in callback directly.
1400 gpgme_op_genkey CHANGED: FPR argument dropped.
1401 gpgme_op_genkey_result NEW
1402 gpgme_genkey_result_t NEW
1403 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1404 gpgme_op_import_result NEW
1405 gpgme_import_status_t NEW
1406 gpgme_import_result_t NEW
1407 gpgme_pubkey_algo_t NEW
1408 gpgme_hash_algo_t NEW
1409 gpgme_invalid_key_t NEW
1410 gpgme_new_signature_t NEW
1411 gpgme_sign_result_t NEW
1412 gpgme_op_sign_result NEW
1413 gpgme_pubkey_algo_name NEW
1414 gpgme_hash_algo_name NEW
1415 gpgme_encrypt_result_t NEW
1416 gpgme_op_encrypt_result NEW
1417 gpgme_decrypt_result_t NEW
1418 gpgme_op_decrypt_result NEW
1419 gpgme_verify_result_t NEW
1420 gpgme_op_verify_result NEW
1421 gpgme_get_notation REMOVED: Access verify result directly instead.
1422 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1423 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1424 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1425 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1426 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1427 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1428 gpgme_trust_item_ref NEW
1429 gpgme_trust_item_unref NEW
1430 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1431 gpgme_trust_item_get_string_attr DEPRECATED
1432 gpgme_trust_item_get_ulong_attr DEPRECATED
1433 gpgme_get_key CHANGED: Removed force_update argument.
1437 gpgme_key_t CHANGED: Now has user accessible data members.
1438 gpgme_key_get_string_attr DEPRECATED
1439 gpgme_key_get_ulong_attr DEPRECATED
1440 gpgme_key_sig_get_string_attr DEPRECATED
1441 gpgme_key_sig_get_ulong_attr DEPRECATED
1442 gpgme_key_get_as_xml REMOVED
1443 gpgme_key_list_result_t NEW
1444 gpgme_op_keylist_result NEW
1445 gpgme_get_op_info REMOVED
1446 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1448 Noteworthy changes in version 0.4.0 (2002-12-23)
1449 ------------------------------------------------
1451 * Key generation returns the fingerprint of the generated key.
1453 * New convenience function gpgme_get_key.
1455 * Supports signatures of user IDs in keys via the new
1456 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1457 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1458 interfaces. The XML info about a key also includes the signatures
1461 * New data object interface, which is more flexible and transparent.
1463 * Interface changes relative to the 0.3.9 release:
1464 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1466 GpgmeDataWriteCb NEW
1468 GpgmeDataReleaseCb NEW
1470 gpgme_data_read CHANGED: Match read() closely.
1471 gpgme_data_write CHANGED: Match write() closely.
1473 gpgme_data_new_from_fd NEW
1474 gpgme_data_new_from_stream NEW
1475 gpgme_data_new_from_cbs NEW
1476 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1477 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1478 gpgme_data_get_type REMOVED: No replacement.
1479 gpgme_op_verify CHANGED: Take different data objects for
1480 signed text and plain text.
1481 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1482 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1483 gpgme_op_genkey CHANGED: New parameter FPR.
1484 GPGME_KEYLIST_MODE_SIGS NEW
1485 gpgme_key_sig_get_string_attr NEW
1486 gpgme_key_sig_get_ulong_attr NEW
1488 GPGME_ATTR_SIG_CLASS NEW
1489 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1491 Noteworthy changes in version 0.3.16 (2003-11-19)
1492 -------------------------------------------------
1494 * Compatibility fixes for GnuPG 1.9.x
1496 Noteworthy changes in version 0.3.15 (2003-02-18)
1497 -------------------------------------------------
1499 * The progress status is sent via the progress callbacks in
1502 * Bug fix for signing operations with explicit signer settings for
1505 Noteworthy changes in version 0.3.14 (2002-12-04)
1506 -------------------------------------------------
1508 * GPGME-Plug is now in its own package "cryptplug".
1510 * Workaround for a setlocale problem. Fixed a segv related to not
1511 correctly as closed marked file descriptors.
1513 Noteworthy changes in version 0.3.13 (2002-11-20)
1514 -------------------------------------------------
1516 * Release due to changes in gpgmeplug.
1518 Noteworthy changes in version 0.3.12 (2002-10-15)
1519 -------------------------------------------------
1521 * Fixed some bux with key listings.
1523 * The development has been branched to clean up some API issues.
1524 This 0.3 series will be kept for compatibility reasons; so do don't
1525 expect new features.
1527 Noteworthy changes in version 0.3.11 (2002-09-20)
1528 -------------------------------------------------
1532 Noteworthy changes in version 0.3.10 (2002-09-02)
1533 -------------------------------------------------
1535 * Setting the signing keys for the CMS protocol does now work.
1537 * The signers setting is honoured by gpgme_op_edit.
1539 Noteworthy changes in version 0.3.9 (2002-08-21)
1540 ------------------------------------------------
1542 * A spec file for creating RPMs has been added.
1544 * An experimental interface to GnuPG's --edit-key functionality is
1545 introduced, see gpgme_op_edit.
1547 * The new gpgme_import_ext function provides a convenient access to
1548 the number of processed keys.
1550 * Interface changes relative to the 0.3.8 release:
1551 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1554 gpgme_op_edit_start NEW
1556 gpgme_op_import_ext NEW
1557 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1559 Noteworthy changes in version 0.3.8 (2002-06-25)
1560 ------------------------------------------------
1562 * It is possible to use an outside event loop for the I/O to the
1563 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1565 * Interface changes relative to the 0.3.6 release:
1566 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1568 GpgmeRegisterIOCb NEW
1572 struct GpgmeIOCbs NEW
1573 gpgme_set_io_cbs NEW
1574 gpgme_get_io_cbs NEW
1575 GPGME_ATTR_ERRTOK NEW
1576 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1578 Noteworthy changes in version 0.3.7 (2002-06-04)
1579 ------------------------------------------------
1581 * GPGME_ATTR_OTRUST is implemented now.
1583 * A first step toward thread safeness has been achieved, see the
1584 documentation for details. Supported thread libraries are pthread
1587 Noteworthy changes in version 0.3.6 (2002-05-03)
1588 ------------------------------------------------
1590 * All error output of the gpgsm backend is send to the bit bucket.
1592 * The signature verification functions are extended. Instead of
1593 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1594 expired signatures. 2 new functions may be used to retrieve more
1595 detailed information like the signature expiration time and a
1596 validity information of the key without an extra key looking.
1598 * The current passphrase callback and progress meter callback can be
1599 retrieved with the new functions gpgme_get_passphrase_cb and
1600 gpgme_get_progress_cb respectively.
1602 * Interface changes relative to the 0.3.5 release:
1603 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1604 gpgme_get_passphrase_cb NEW
1605 gpgme_get_progress_cb NEW
1606 GpgmeDataEncoding NEW
1607 gpgme_data_set_encoding NEW
1608 gpgme_data_get_encoding NEW
1609 GPGME_SIG_STAT_GOOD_EXP NEW
1610 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1611 gpgme_op_verify CHANGED: Returns more status codes.
1612 GPGME_ATTR_SIG_STATUS NEW
1613 gpgme_get_sig_string_attr NEW
1614 gpgme_get_sig_ulong_attr NEW
1615 gpgme_get_protocol NEW
1616 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1618 Noteworthy changes in version 0.3.5 (2002-04-01)
1619 ------------------------------------------------
1621 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1622 case, symmetric encryption is performed. Note that this requires a
1623 passphrase from the user.
1625 * More information is returned for X.509 certificates.
1627 * Interface changes relative to the 0.3.4 release:
1628 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1629 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1630 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1632 Noteworthy changes in version 0.3.4 (2002-03-04)
1633 ------------------------------------------------
1635 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1636 some recipients have been invalid, whereas earlier versions
1637 succeeded in this case. The plaintext is still encrypted for all valid
1638 recipients, so the application might take this error as a hint that
1639 the ciphertext is not usable for all requested recipients.
1640 Information about invalid recipients is available with gpgme_get_op_info.
1642 * gpgme_op_verify now allows to pass an uninitialized data object as
1643 its plaintext argument to check for normal and cleartext
1644 signatures. The plaintext is then returned in the data object.
1646 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1647 to set and get the number of certifications to include in S/MIME
1650 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1651 to encrypt and sign a message in a combined operation.
1653 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1655 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1657 * Interface changes relative to the 0.3.3 release:
1658 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1659 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1660 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1661 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1662 gpgme_set_include_certs NEW
1663 gpgme_get_include_certs NEW
1664 gpgme_op_encrypt_sign NEW
1665 gpgme_op_encrypt_sign_start NEW
1666 gpgme_op_keylist_ext_start NEW
1667 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1669 Noteworthy changes in version 0.3.3 (2002-02-12)
1670 ------------------------------------------------
1672 * Fix the Makefile in jnlib.
1674 * Fix the test suite (hopefully). It should clean up all its state
1675 with `make check' now.
1678 Noteworthy changes in version 0.3.2 (2002-02-10)
1679 ------------------------------------------------
1681 * Remove erroneous dependency on libgcrypt in jnlib.
1684 Noteworthy changes in version 0.3.1 (2002-02-09)
1685 ------------------------------------------------
1687 * There is a Texinfo manual documenting the API.
1689 * The gpgme_set_keylist_mode function returns an error, and changed
1690 its meaning. It is no longer usable to select between normal and
1691 fast mode (newer versions of GnuPG will always be fast), but
1692 selects between local keyring, remote keyserver, or both.
1693 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1694 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1695 current setting, a fucntion gpgme_get_keylist_mode was added to
1696 retrieve the current mode.
1698 * gpgme_wait accepts a new argument STATUS to return the error status
1699 of the operation on the context. Its definition is closer to
1700 waitpid() now than before.
1702 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1703 type from off_t to the unsigned size_t.
1705 * The R_HD argument to the GpgmePassphraseCb type changed its type
1706 from void* to void**.
1708 * New interface gpgme_op_trustlist_end() to match
1709 gpgme_op_keylist_end().
1711 * The CryptPlug modules have been renamed to gpgme-openpgp and
1712 gpgme-smime, and they are installed in pkglibdir by `make install'.
1714 * An idle function can be registered with gpgme_register_idle().
1716 * The GpgSM backend supports key generation with gpgme_op_genkey().
1718 * Interface changes relative to the 0.3.0 release:
1719 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1720 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1721 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1722 gpgme_wait CHANGED: New argument STATUS.
1723 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1724 The function has a new meaning!
1725 gpgme_get_keylist_mode NEW
1726 GPGME_KEYLIST_MODE_LOCAL NEW
1727 GPGME_KEYLIST_MODE_EXTERN NEW
1728 gpgme_op_trustlist_next NEW
1730 gpgme_register_idle NEW
1731 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1733 Noteworthy changes in version 0.3.0 (2001-12-19)
1734 ------------------------------------------------
1736 * New interface gpgme_set_protocol() to set the protocol and thus the
1737 crypto engine to be used by the context. Currently, the OpenPGP
1738 and the CMS protocols are supported. They are specified by the new
1739 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1740 A new context uses the OpenPGP engine by default.
1742 * gpgme_get_engine_info() returns information for all crypto engines
1743 compiled into the library. The XML format has changed. To
1744 reliably get the version of a crypto engine, the <version> tag
1745 after the appropriate <protocol> tag has to be looked for.
1747 * New interface gpgme_engine_check_version(), obsoleting
1748 gpgme_check_engine(). Check the version of all engines you are
1749 supporting in your software.
1751 * GpgmeKey lists the user ids in the order as they are returned by
1752 GnuPG, first the primary key with index 0, then the sub-user ids.
1754 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1755 signatures simultaneously.
1757 * The new interface gpgme_op_keylist_end() terminates a pending
1758 keylist operation. A keylist operation is also terminated when
1759 gpgme_op_keylist_next() returns GPGME_EOF.
1761 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1762 cross-compiled, or even compiled without support for GnuPG
1765 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1766 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1767 in the path, but it can also be compiled without support for GpgSM
1768 (`--without-gpgsm').
1770 * CryptPlug modules for GPGME are included and can be enabled at
1771 configure time (`--enable-gpgmeplug'). There is one module which
1772 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1773 GpgSM engine (`gpgsmplug').
1775 * Interface changes relative to the latest 0.2.x release:
1776 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1777 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1778 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1779 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1780 gpgme_get_engine_info CHANGED: New format, extended content.
1781 gpgme_engine_check_version NEW
1782 gpgme_decrypt_verify_start NEW
1783 gpgme_decrypt_verify NEW
1784 gpgme_op_keylist_next NEW
1785 gpgme_set_protocol NEW
1786 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1789 Noteworthy changes in version 0.2.3 (2001-09-17)
1790 ------------------------------------------------
1792 * New function gpgme_get_op_info which can be used to get the micalg
1793 parameter needed for MOSS.
1795 * New functions gpgme_get_armor and gpgme_get_textmode.
1797 * The usual bug fixes and some minor functionality improvements.
1799 * Added a simple encryption component for MS-Windows; however the
1800 build procedure might have some problems.
1803 Noteworthy changes in version 0.2.2 (2001-06-12)
1804 ------------------------------------------------
1806 * Implemented a key cache.
1808 * Fixed a race condition under W32 and some other bug fixes.
1811 Noteworthy changes in version 0.2.1 (2001-04-02)
1812 ------------------------------------------------
1814 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1816 * Handle GnuPG's new key capabilities output and support revocation
1819 * Made the W32 support more robust.
1822 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
1825 This file is free software; as a special exception the author gives
1826 unlimited permission to copy and/or distribute it, with or without
1827 modifications, as long as this notice is preserved.
1829 This file is distributed in the hope that it will be useful, but
1830 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1831 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.