1 Noteworthy changes in version 1.8.0 (2016-11-16)
2 ------------------------------------------------
4 * The module of the Python bindings has been renamed to 'gpg'.
6 * New interface to query current software versions.
8 * New feature to use gpg's --{show,override}session-key options.
10 * New interface to set the sender of a mail.
12 * qt: Added Distinguished Name parser from libkleo
14 * The --homedir option is now used with recent gpgconf versions.
16 * On 64 bit Windows systems gpgconf is now properly located.
18 * The internal locking functions have been replaced by libgpg-error
21 * Interface changes relative to the 1.7.1 release:
22 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
25 gpgme_op_query_swdb NEW.
26 gpgme_op_query_swdb_result NEW.
27 gpgme_query_swdb_result_t NEW.
28 gpgme_get_ctx_flag NEW.
29 gpgme_decrypt_result_t EXTENDED: New field session_key.
31 qt: DN::Attribute NEW.
32 qt: Job::context(Job*) NEW.
33 cpp: EngineInfo::Version::Version(const char*) NEW.
34 cpp: EngineInfo::Version::Version() NEW.
36 cpp: Context::setSender(const char*) NEW.
37 cpp: Context::getSender() NEW.
39 [c=C28/A17/R0 cpp=C9/A3/R0 qt=C8/A1/R0]
42 Noteworthy changes in version 1.7.1 (2016-10-18)
43 ------------------------------------------------
45 * Fixed problems with the new language bindings.
47 * New helper function gpgme_addrspec_from_uid.
49 * Use option --exit-on-status-write-error with newer gpg versions.
51 * qt: Missed API from the Qt Binding inclusion has
54 * qt: abstractimportjob.h is now installed to that
55 ImportJobs can be used again.
57 * qt: Fixed spelling error in API (startReceive).
59 * Interface changes relative to the 1.7.0 release:
60 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
61 gpgme_addrspec_from_uid NEW.
62 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
63 qt: MultiDeleteJob NEW.
64 qt: AbstractImportJob NEW.
66 cpp: Signature::key(bool, bool) NEW.
67 cpp: UserID::addrSpecFromString(const char*) NEW.
68 cpp: UserID::addrSpec() NEW.
70 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
73 Noteworthy changes in version 1.7.0 (2016-09-21)
74 ------------------------------------------------
76 * New language bindings for Python 2 and 3.
78 * New language Bindings for C++ and the Qt-Framework API.
80 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
81 key creation easier (requires GnuPG 2.1).
83 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
84 management easier (requires GnuPG 2.1).
86 * New function gpgme_op_keysign to make key signing easier (requires
89 * New function gpgme_op_interact to replace the now deprecated
90 functions gpgme_op_edit and gpgme_op_card_edit.
92 * New function gpgme_pubkey_algo_string to convert a public key
93 algorithm into a GnuPG 2.1 style string.
95 * Support for GnuPG 2.1's TOFU trust model.
97 * Notation flags are now correctly set on verify.
99 * New global flag "require-gnupg" to set a minimal gnupg version.
101 * More supported items in gpgme_get_dirinfo.
103 * New function gpgme_data_set_flag and flag "size-hint".
105 * New function gpgme_set_ctx_flag and flags "full-status" and
108 * Improved gpgme_data_identify to distinguish more file types.
110 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
111 mixed public key and symmetric encryption.
113 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
115 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
116 signed data is a valid MIME part. This is to support future GnuPG
119 * Interface changes relative to the 1.6.0 release:
120 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
121 gpgme_pubkey_algo_string NEW.
123 gpgme_set_ctx_flag NEW.
124 gpgme_data_set_flag NEW.
125 gpgme_op_createkey NEW.
126 gpgme_op_createkey_start NEW.
127 gpgme_op_createsubkey NEW.
128 gpgme_op_createsubkey_start NEW.
129 gpgme_op_adduid_start NEW.
131 gpgme_op_revuid_start NEW.
133 gpgme_op_keysign_start NEW.
134 gpgme_op_keysign NEW.
135 gpgme_op_tofu_policy_start NEW.
136 gpgme_op_tofu_policy NEW.
137 gpgme_op_interact_start NEW.
138 gpgme_op_interact NEW.
139 gpgme_interact_cb_t NEW.
140 gpgme_op_edit_start DEPRECATED.
141 gpgme_op_edit DEPRECATED.
142 gpgme_op_card_edit_start DEPRECATED.
143 gpgme_op_card_edit DEPRECATED.
144 gpgme_edit_cb_t DEPRECATED.
145 gpgme_status_code_t DEPRECATED.
146 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
147 gpgme_signature_t EXTENDED: New field key.
148 gpgme_key_t EXTENDED: New field fpr.
149 gpgme_subkey_t EXTENDED: New field keygrip.
150 gpgme_user_id_t EXTENDED: New field tofu.
151 gpgme_tofu_policy_t NEW.
152 gpgme_tofu_info_t NEW.
153 GPGME_STATUS_KEY_CONSIDERED NEW.
154 GPGME_STATUS_TOFU_USER NEW.
155 GPGME_STATUS_TOFU_STATS NEW.
156 GPGME_STATUS_TOFU_STATS_LONG NEW.
157 GPGME_STATUS_NOTATION_FLAGS NEW.
158 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
159 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
160 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
161 GPGME_DATA_ENCODING_MIME NEW.
162 GPGME_ENCRYPT_SYMMETRIC NEW.
163 GPGME_CREATE_SIGN NEW.
164 GPGME_CREATE_ENCR NEW.
165 GPGME_CREATE_CERT NEW.
166 GPGME_CREATE_AUTH NEW.
167 GPGME_CREATE_NOPASSWD NEW.
168 GPGME_CREATE_SELFSIGNED NEW.
169 GPGME_CREATE_NOSTORE NEW.
170 GPGME_CREATE_WANTPUB NEW.
171 GPGME_CREATE_WANTSEC NEW.
172 GPGME_CREATE_FORCE NEW.
173 GPGME_KEYSIGN_LOCAL NEW.
174 GPGME_KEYSIGN_LFSEP NEW.
175 GPGME_INTERACT_CARD NEW.
177 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
180 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
181 ------------------------------------------------
183 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
185 * Added gpgme_set_status_cb to allow a user to see some status
188 * Added an export mode for secret keys.
190 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
192 * The passphrase handler for the loopback mode has been improved and may
193 also be used with genkey.
195 * [w32] The standard GnuPG 2.1 install directory is now seached for
196 gpgconf.exe before a registry specified directory and the Gpg4win
199 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
202 * Interface changes relative to the 1.5.1 release:
203 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
204 gpgme_set_offline NEW.
205 gpgme_get_offline NEW.
206 gpgme_set_status_cb NEW.
207 gpgme_get_status_cb NEW.
208 GPGME_EXPORT_MODE_SECRET NEW
209 GPGME_EXPORT_MODE_RAW NEW.
210 GPGME_EXPORT_MODE_PKCS12 NEW.
213 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
214 ------------------------------------------------
216 * Fixed crash in key listings for user ids with a backslash.
218 * Fixed regression for GPGSM use with GnuPG < 2.1.
220 * Properly set signature summary for revoked OpenPGP keys.
223 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
224 ------------------------------------------------
226 * Fixed a possible crash in the debug code.
228 * Fixed building for Windows with newer versions of Mingw.
231 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
232 -------------------------------------------------------------
234 * The export key functions do now return an error if used with the
235 latest GnuPG version.
238 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
239 -------------------------------------------------------------
241 * gpgme-tool is now installed.
243 * Fix external listing for modern keyservers.
248 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
249 -------------------------------------------------------------
251 * Fixed possible overflow in gpgsm and uiserver engines.
254 * Added support for GnuPG 2.1's --with-secret option.
256 * Interface changes relative to the 1.5.0 release:
257 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
258 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
261 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
262 -------------------------------------------------------------
264 * On Unices the engine file names are not not anymore hardwired but
265 located via the envvar PATH. All options to set the name of the
266 engines for the configure run are removed.
268 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
269 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
270 is not found, GPGME looks for an engine named "gpg".
272 * New feature to use the gpgme I/O subsystem to run arbitrary
275 * New flag to use encryption without the default compression step.
277 * New function to access "gpg-conf --list-dirs"
279 * New configure option --enable-fixed-path for use by Android.
281 * Support ECC algorithms.
283 * Interface changes relative to the 1.4.3 release:
284 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
285 gpgme_get_dirinfo NEW.
286 gpgme_op_spawn_start NEW.
288 GPGME_PROTOCOL_SPAWN NEW.
289 GPGME_SPAWN_DETACHED NEW.
290 GPGME_SPAWN_ALLOW_SET_FG NEW.
291 GPGME_ENCRYPT_NO_COMPRESS NEW.
294 gpgme_subkey_t EXTENDED: New field curve.
295 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
296 GPGME_STATUS_MOUNTPOINT NEW.
297 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
298 GPGME_STATUS_ATTRIBUTE NEW.
299 GPGME_STATUS_BEGIN_SIGNING NEW.
300 GPGME_STATUS_KEY_NOT_CREATED NEW.
303 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
304 -------------------------------------------------------------
306 * The default engine names are now taken from the output of gpgconf.
307 If gpgconf is not found the use of gpg 1 is assumed.
309 * Under Windows the default engines names are first searched in the
310 installation directory of the gpgme DLL.
312 * New function gpgme_data_identify to detect the type of a message.
314 * Interface changes relative to the 1.4.2 release:
315 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
316 gpgme_signers_count NEW.
317 gpgme_data_type_t NEW.
318 gpgme_data_identify NEW.
321 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
322 -------------------------------------------------------------
324 * Allow symmetric encryption with gpgme_op_encrypt_sign.
326 * Fixed mismatching off_t definitions on Windows.
328 * Interface changes relative to the 1.4.1 release:
329 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
332 GPGME_PROTOCOL_OPENPGP NEW alias.
335 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
336 ------------------------------------------------------------
338 * Fixed reading of gpg.conf files with excessive use of the group
341 * Fixed building with the i686-w64-mingw32 toolchain.
343 * Disabled FD passing by default for Apple.
346 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
347 ------------------------------------------------------------
349 * New function gpgme_set_global_flag to help debugging on Android.
351 * New function gpgme_io_writen as a convenience wrapper around
354 * New functions to support the pinentry mode feature of GnuPG 2.1.
356 * New macro GPGME_VERSION_NUMBER to allow supporting different API
357 versions without the need for a configure test.
359 * Several improvements for gpgme-tool.
361 * Better logging of the common "invalid engine" error code.
363 * Support for FD passing is now enabled by default. The configure
364 option --disable-fd-passing may be used to disable this.
366 * Interface changes relative to the 1.3.1 release:
367 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
368 GPGME_VERSION_NUMBER NEW.
370 gpgme_set_global_flag NEW.
371 gpgme_set_pinentry_mode NEW.
372 gpgme_get_pinentry_mode NEW.
373 gpgme_pinentry_mode_t NEW.
374 GPGME_PINENTRY_MODE_DEFAULT NEW.
375 GPGME_PINENTRY_MODE_ASK NEW.
376 GPGME_PINENTRY_MODE_CANCEL NEW.
377 GPGME_PINENTRY_MODE_ERROR NEW.
378 GPGME_PINENTRY_MODE_LOOPBACK NEW.
381 Noteworthy changes in version 1.3.2 (2012-05-02)
382 ------------------------------------------------
384 * Remove support for libgpgme-pth. As far as we know, this was never used,
385 and GnuPG is going to use our own npth in the future.
387 * Fix signature summary information for a missing X.509 key.
389 * Fix parsing of dates >= year 2038.
392 Noteworthy changes in version 1.3.1 (2011-06-16)
393 ------------------------------------------------
395 * Ported to Windows CE.
397 * Detect GPG versions not supporting ---passwd.
399 * Interface changes relative to the 1.3.0 release:
400 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
401 GPGME_EXPORT_MODE_MINIMAL NEW
402 GPGME_STATUS_SUCCESS NEW
403 gpgme_err_code_from_syserror NEW
404 gpgme_err_set_errno NEW
405 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
406 gpgme_error_from_syserror NEW
407 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
410 Noteworthy changes in version 1.3.0 (2010-01-11)
411 ------------------------------------------------
413 * GPGME does not come with an internal libassuan version anymore.
414 The external libassuan 1.1.0 release or later is required. For
415 application programmers on systems that can resolve inter-library
416 dependencies at runtime, this is a transparent change.
418 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
420 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
422 * New API to change the passphrase of a key.
424 * Interface changes relative to the 1.2.0 release:
425 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
426 GPGME_STATUS_INV_SGNR NEW.
427 GPGME_STATUS_NO_SGNR NEW.
428 GPGME_PROTOCOL_G13 NEW.
429 gpgme_op_g13_mount NEW.
430 gpgme_g13_result_t NEW.
433 gpgme_op_passwd_start NEW.
435 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
438 Noteworthy changes in version 1.2.0 (2009-06-18)
439 ------------------------------------------------
441 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
444 * gpgme_new will fail if gpgme_check_version was not called, or a
445 selftest failed (for example, if -mms-bitfields was not used on
448 * New functions gpgme_io_read and gpgme_io_write for use with
449 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
451 * New functions gpgme_result_ref and gpgme_result_unref to detach
452 result structures from a context.
454 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
455 that allow to specify exported keys through gpgme_key_t objects
458 * New mode of operation gpgme_export_mode_t that allows exporting
461 * Interface changes relative to the 1.1.7 release:
462 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
463 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
464 GPGME_PROTOCOL_ASSUAN NEW.
465 gpgme_assuan_data_cb_t NEW.
466 gpgme_assuan_inquire_cb_t NEW.
467 gpgme_assuan_status_cb_t NEW.
468 gpgme_op_assuan_transact_start NEW.
469 gpgme_op_assuan_transact NEW.
470 gpgme_op_assuan_result NEW.
471 gpgme_op_import_keys NEW.
472 gpgme_op_import_keys_start NEW.
473 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
474 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
475 gpgme_check_version CHANGED: Is now a macro.
476 gpgme_new EXTENDED: More failure codes.
479 gpgme_result_ref NEW.
480 gpgme_result_unref NEW.
481 gpgme_export_mode_t NEW.
482 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
483 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
484 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
485 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
486 gpgme_op_export_keys_start NEW.
487 gpgme_op_export_keys NEW.
488 GPGME_DATA_ENCODING_URL NEW.
489 GPGME_DATA_ENCODING_URL0 NEW.
490 GPGME_DATA_ENCODING_URLESC NEW.
491 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
494 Noteworthy changes in version 1.1.8 (2008-12-08)
495 ------------------------------------------------
497 * SIGPIPE is now again ignored as described in the manual. Fixes
498 regresion introduced with 1.1.6.
501 Noteworthy changes in version 1.1.7 (2008-10-17)
502 ------------------------------------------------
504 * Using GPGME_KEYLIST_MODE_LOCAL combined with
505 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
506 --locate-keys feature of gpg (>= 2.0.10).
508 * The encoding of gpgme_data_t objects can affect the output encoding
509 of export, sign and encrypt operations now (the same operations
510 that are also affected by the ASCII mode switch). We believe this
511 change in the ABI is innocent enough not to break existing
512 applications (it only affects the S/MIME backend on certain
515 * The reference manual now includes the specification of "The GnuPG
518 * A new function gpgme_cancel_async can be used to asynchronously
519 cancel any pending operation at any time, from any thread.
521 * Interface changes relative to the 1.1.6 release:
522 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
523 gpgme_op_encrypt CHANGED: Output encoding can affect result.
524 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
525 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
526 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
527 gpgme_op_sign CHANGED: Output encoding can affect result.
528 gpgme_op_sign_start CHANGED: Output encoding can affect result.
529 gpgme_op_export CHANGED: Output encoding can affect result.
530 gpgme_op_export_start CHANGED: Output encoding can affect result.
531 gpgme_op_export_ext CHANGED: Output encoding can affect result.
532 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
533 gpgme_cancel_async NEW
534 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
537 Noteworthy changes in version 1.1.6 (2008-01-04)
538 ------------------------------------------------
540 * Bug fixes for for W32.
542 * A new, experimental (and thus undocumented and potentially
543 unstable) interface for accessing gpg-conf through GPGME has been
546 * Interface changes relative to the 1.1.1 release:
547 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
548 gpgme_signature_t EXTENDED: New field chain_model.
549 gpgme_op_getauditlog_start NEW.
550 gpgme_op_getauditlog NEW.
551 GPGME_AUDITLOG_HTML NEW.
552 GPGME_AUDITLOG_WITH_HELP NEW.
553 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
556 Noteworthy changes in version 1.1.5 (2007-07-09)
557 ------------------------------------------------
559 * Bug and portability fixes (mainly for W32).
562 Noteworthy changes in version 1.1.4 (2007-03-05)
563 ------------------------------------------------
565 * Detect and bail out on double plaintext messages. This is required
566 so that applications can properly detect the signed parts of a
567 message. Actual there is now a double protection as GnuPG 1.4.7
568 will detect this case too.
571 Noteworthy changes in version 1.1.3 (2007-01-29)
572 ------------------------------------------------
574 * Fixed a memory leak in gpgme_data_release_and_get_mem.
576 * Fixed a bug in Windows command line quoting.
579 Noteworthy changes in version 1.1.2 (2006-03-02)
580 ------------------------------------------------
582 * Fixed a bug in the W32 glib backend.
585 Noteworthy changes in version 1.1.1 (2006-02-23)
586 ------------------------------------------------
588 * Fixed a bug in that the fingerprints of subkeys are not available.
590 * Clarified usage of the SECRET flag in key listings. It is now
593 * Reading signature notations and policy URLs on key signatures is
594 supported. They can be found in the new field notations of the
595 gpgme_key_sig_t structure. This has to be enabled with the keylist
596 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
598 * A new gpgme_free() function solves the problem of using different
599 allocators in a single program. This function should now be used
600 instead calling free() to release the buffer returned by
601 gpgme_data_release_and_get_mem. It is recommended that you always
602 do this, but it is only necessary on certain platforms, so backwards
603 compatibility is provided. In other words: If free() worked for
604 you before, it will keep working.
606 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
607 They are analyzed by the verify handlers and made available in the
608 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
610 * Interface changes relative to the 1.1.0 release:
611 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
612 gpgme_key_sig_t EXTENDED: New field notations.
613 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
615 GPGME_STATUS_PKA_TRUST_BAD NEW
616 GPGME_STATUS_PKA_TRUST_GOOD NEW
617 gpgme_signature_t EXTENDED: New field pka_trust.
618 gpgme_signature_t EXTENDED: New field pka_address.
619 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
622 Noteworthy changes in version 1.1.0 (2005-10-01)
623 ------------------------------------------------
625 * You can now configure the backend engine file name and home
626 directory to be used, as default and per context.
628 * Information about the recipients of an encrypted text is now
629 available at decryption time.
631 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
632 and verify handlers, the information about the plaintext filename,
633 if available is made available in the new field file_name of the
634 respective result structure.
636 * The code for "automagically detecting the thread library" has been
637 removed from libgpgme. It is deprecated since version 0.4.3.
638 Since then, you had to link against libgpgme-pthread for
639 applications using pthread and libgpgme-pth for applications using
642 The code was removed because it caused compilation problems on
643 systems where the pthread.h header from GNU Pth is available in
644 addition to the system header (FreeBSD 6 and later for example).
646 * "./autogen.sh --build-w32" does now build gpgme.dll.
648 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
649 delimiter. The standard install directory is used when locating
650 gpg or gpgsm before finally falling back to the hardwired name.
652 * There is a new flag for keys and subkeys, is_qualified, which
653 indicates if a key can be used for qualified signatures according
654 to local government regulations.
656 * You can associate a filename with a data object using the new
657 function gpgme_data_set_file_name(). This filename will be stored
658 in the output when encrypting or signing the data and will be
659 returned when decrypting or verifying the output data.
661 * You can now set notation data at signature creation with the new
662 function gpgme_sig_notation_add().
664 * Interface changes relative to the 1.0.3 release:
665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
666 gpgme_set_engine_info NEW
667 gpgme_ctx_get_engine_info NEW
668 gpgme_ctx_set_engine_info NEW
669 gpgme_recipient_t NEW
670 gpgme_decrypt_result_t EXTENDED: New field recipients.
671 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
672 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
673 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
674 GPGME_STATUS_PLAINTEXT NEW
675 gpgme_key_t EXTENDED: New field is_qualified.
676 gpgme_subkey_t EXTENDED: New field is_qualified.
677 gpgme_data_get_file_name NEW
678 gpgme_data_set_file_name NEW
679 gpgme_sig_notation_flags_t NEW
680 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
681 GPGME_SIG_NOTATAION_CRITICAL NEW
682 gpgme_sig_notation_clear NEW
683 gpgme_sig_notation_add NEW
684 gpgme_sig_notation_get NEW
685 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
688 Noteworthy changes in version 1.0.3 (2005-06-20)
689 ------------------------------------------------
691 * Previousy, GPGME would use a default "include certs" of 1. This
692 has been changed. Now GPGME will use the crypto backend engines
693 default unless you set the value with gpgme_set_include_certs()
694 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
695 as a value to explicitely request the new default behaviour.
697 Because the default changes, this is a slight change of the API
698 semantics. We consider it to be a bug fix.
700 * A bug which made GPGME hang has been fixed. If you have
701 experienced hanging before, please try out this version and let me
702 know if you still experience hanging problems.
704 * Interface changes relative to the 0.9.0 release:
705 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
706 gpgme_set_include_certs CHANGED DEFAULT
707 GPGME_INCLUDE_CERTS_DEFAULT NEW
708 GPGME_STATUS_SIG_SUBPACKET NEW
709 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
710 GPGME_STATUS_SC_OP_FAILURE NEW
711 GPGME_STATUS_SC_OP_SUCCESS NEW
712 GPGME_STATUS_CARDCTRL NEW
713 GPGME_STATUS_BACKUP_KEY_CREATED NEW
714 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
717 Noteworthy changes in version 1.0.2 (2004-12-28)
718 ------------------------------------------------
720 * Changed the license of the library to the GNU Lesser General Public
721 License (LGPL), version 2.1 or later.
724 Noteworthy changes in version 1.0.1 (2004-10-22)
725 ------------------------------------------------
730 Noteworthy changes in version 1.0.0 (2004-09-30)
731 ------------------------------------------------
733 * Version 1.0.0! We are proud to present you with a thoroughly
734 tested and stable version of the GPGME library. A big Thank You!
735 to all the people who made this possible.
737 The development will be branched into a stable 1.x.y series and the
740 * The gpgme.m4 macro supports checking the API version. Just prepend
741 it to the required version string, separated by a colon. For
742 example, this release has the version "1:1.0.0". The last release
743 to which this version is (mostly) ABI compatible is "1:0.4.2",
744 which is the default required version.
747 Noteworthy changes in version 0.9.0 (2004-06-08)
748 ------------------------------------------------
750 * The type gpgme_key_t has now a new field keylist_mode that contains
751 the keylist mode that was active at the time the key was retrieved.
753 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
754 that contains a flag indicating that the key should not have been
757 * Verifying a signature of a revoked key gives the correct result now
758 (GPG_ERR_CERT_REVOKED error code).
760 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
761 verify operations still allows you to look at the signature
764 * Clarified that patterns in keylisting operations have an upper
765 limit, and thus are not suited to list many keys at once by their
766 fingerprint. Also improve the error message if the pattern is too
767 long for the CMS protocol to handle.
769 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
770 gpgme_key_t EXTENDED: New field keylist_mode.
771 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
772 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
775 Noteworthy changes in version 0.4.7 (2004-04-29)
776 ------------------------------------------------
778 * Correctly initialize the fields expired, revoked, invalid, and
779 disabled in the gpgme_key_t structures.
781 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
782 accidently of type int instead unsigned int.
784 * Interface changes relative to the 0.4.5 release:
785 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
786 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
787 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
789 Noteworthy changes in version 0.4.6 (2004-04-06)
790 ------------------------------------------------
795 Noteworthy changes in version 0.4.5 (2004-03-07)
796 ------------------------------------------------
798 * GPGME is now compiled with LFS (large file support) by default.
799 This means that _all_ programs using GPGME must be compiled with
800 LFS support enabled by default. You can do this easily with
801 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
802 without autoconf by defining the preprocessor symbol
803 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
804 the C compiler command line, or by defining this preprocessor
805 symbol before including any system header files). For more
806 details, read the section on LFS in the manual.
808 Up to now, it was undocumented that GPGME was not using LFS.
809 But the public interfaces use off_t, and file descriptors are
810 exchanged between the application and GPGME. This was an oversight,
811 and bound to cause troubles in the future.
813 Writing GPGME as a dual mode library that seamlessly supports LFS
814 while keeping backwards compatibility is possible, but does not
815 solve the problem: Many applications already expect GPGME to have
816 LFS (they are compiled with off_t being a 64bit value). This is true
817 in particular for the popular Gtk+ and Qt programs.
819 So, although this is an ABI (but not an API) break, we will not
820 change the library version to reflect that. Because the interfaces
821 affected are probably not used yet in any GPGME 0.4 based
822 application, we don't expect any real failures from this change.
823 In fact, applications already using LFS will have some subtle bugs
826 However, if you encounter an application using GPGME 0.4.x that
827 does _not_ use LFS by default (off_t is a 32bit value), _and_
828 uses at least one of the functions gpgme_data_seek,
829 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
830 gpgme_data_new_from_cbs, then indeed this library will be ABI
831 incompatible with the program. As said above, we don't believe
832 such a program exists. If we are in error, then you have two
833 options: As a quick hack, you can configure GPGME with the
834 --disable-largefile option. This will revert the change, and GPGME
835 will not use LFS. However, GPGME will be incompatible with
836 programs that expect GPGME to use LFS. All applications are
837 required to use LFS when using GPGME, so this is only good as a
838 temporary local work-around.
840 The other option is to change the versioning of the library and
841 recompile all applications. We have reserved a special version of
842 the library for that, so you can do that without expecting a
843 version clash in the future. Furthermore, everyone who does this
844 will agree on the version to use (this is important for
845 distribution makers). Read the comment in configure.ac (before
846 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
847 blindly: As stated above, we think it is unlikely this measure is
848 needed. Still, it is there if necessary. If in doubt, contact us
849 and we will give our advise for your specific situation.
851 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
854 * New interface gpgme_cancel() that can be used to cancel
855 asynchronous operations.
857 * Interface changes relative to the 0.4.4 release:
858 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
859 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
860 gpgme_data_seek CHANGED: off_t is now a largefile type.
861 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
862 GPGME_KEYLIST_MODE_VALIDATE NEW
864 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
866 Noteworthy changes in version 0.4.4 (2004-01-12)
867 ------------------------------------------------
869 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
870 been renamed to "sig_class", to avoid clash with C++ compilers. In
871 the C API, the old name "class" has been preserved for backwards
872 compatibility, but is deprecated.
874 * Interface changes relative to the 0.4.3 release:
875 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
876 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
877 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
878 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
880 Noteworthy changes in version 0.4.3 (2003-10-06)
881 ------------------------------------------------
883 * libgpgme should not be used for threaded programs anymore. This
884 never worked reliably in all cases, because you had to
885 be careful about the linking order and libtool wouldn't do that for
886 you automatically. Instead, now you have to link against
887 libgpgme-pthread for applications using pthread and libgpgme-pth for
888 applications using GNU Pth.
890 The old code for automagically detecting the thread library is
891 still part of libgpgme, but it is DEPRECATED.
893 * There are new automake macros AM_PATH_GPGME_PTH and
894 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
895 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
896 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
897 variables of course also include the configuration for the thread
898 package itself. Alternatively, use libtool.
900 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
903 * gpgme-config doesn't support setting the prefix or exec prefix
904 anymore. I don't think it ever worked correctly, and it seems to
907 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
908 provided was not unique, instead returning the first matching key.
910 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
911 that indicates if the key can be used for authentication.
913 * gpgme_signature_t's status field is now correctly set to an error
914 with error code GPG_ERR_NO_PUBKEY if public key is not found.
916 * gpgme_new_signature_t's class field is now an unsigned int, rather
917 than an unsigned long (the old class field is preserved for
918 backwards compatibility).
920 * A new function gpgme_set_locale() is provided to allow configuring
921 the locale for the crypto backend. This is necessary for text
922 terminals so that programs like the pinentry can be started with
923 the right locale settings for the terminal the application is running
924 on, in case the terminal has different settings than the system
925 default (for example, if it is a remote terminal). You are highly
926 recommended to call the following functions directly after
931 setlocale (LC_ALL, "");
932 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
933 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
935 GPGME can not do this for you, as setlocale is not thread safe, and
936 there is no alternative.
938 * The signal action for SIGPIPE is now set to SIG_IGN by
939 gpgme_check_version, instead the first time a crypto engine is
940 started (which is not well defined).
942 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
943 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
944 to CRC24RFC2440. For now, these strings can be used as the MIC
945 parameter for PGP/MIME (if appropriately modified).
947 * Interface changes relative to the 0.4.2 release:
948 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
950 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
951 gpgme_key_t EXTENDED: New field can_authenticate.
952 gpgme_subkey_t EXTENDED: New field can_authenticate.
953 gpgme_new_signature_t CHANGED: New type for class field.
955 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
956 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
958 Noteworthy changes in version 0.4.2 (2003-07-30)
959 ------------------------------------------------
961 * Allow gpg-error to be in non-standard place when linking the test suite.
963 * Configure will fail now if gpg-error can not be found.
965 * Fixed initialized memory backed data objects for writing, which
966 caused the test program to crash (but only on Mac OS, surprisingly).
968 * Eliminate use of C99 constructs.
970 * Small improvements to the manual.
973 Noteworthy changes in version 0.4.1 (2003-06-06)
974 ------------------------------------------------
976 This is the release that 0.4.0 should have been. There are many
977 interface changes, please see below for the details. The changes are
978 sometimes the result of new functionality, but more often express a
979 paradigm shift. Others are an overdue cleanup to get GPGME in line
980 with the GNU coding standards and to make the interface more
981 self-consistent. Here is an overview on the changes:
983 All types have been renamed to conform to the GNU coding standards,
984 most of the time by keeping the whole name in lowercase and inserting
985 underscores between words.
987 All operations consistently only accept input parameters in their
988 invocation function, and return only an error code directly. Further
989 information about the result of the operation has to be retrieved
990 afterwards by calling one of the result functions. This unifies the
991 synchronous and the asynchronous interface.
993 The error values have been completely replaced by a more
994 sophisticated model that allows GPGME to transparently and accurately
995 report all errors from the other GnuPG components, irregardless of
996 process boundaries. This is achieved by using the library
997 libgpg-errors, which is shared by all GnuPG components. This library
998 is now required for GPGME.
1000 The results of all operations are now provided by pointers to C
1001 structs rather than by XML structs or in other ways.
1003 Objects which used to be opaque (for example a key) are now pointers
1004 to accessible structs, so no accessor functions are necessary.
1006 Backward compatibility is provided where it was possible without too
1007 much effort and did not collide with the overall sanitization effort.
1008 However, this is only for ease of transition. NO DEPRECATED FUNCTION
1009 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
1010 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
1011 Recommendations how to replace deprecated or removed functionality
1012 can be found within the description of each change.
1014 What follows are all changes to the interface and behaviour of GPGME
1017 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
1018 deprecated attributes will warn about use of obsolete functions and
1019 type definitions. You can suppress these warnings by passing
1020 -Wno-deprecated-declarations to the gcc command.
1022 * The following types have been renamed. The old types are still
1023 available as aliases, but they are deprecated now:
1025 GpgmeCtx gpgme_ctx_t
1026 GpgmeData gpgme_data_t
1027 GpgmeError gpgme_error_t
1028 GpgmeDataEncoding gpgme_data_encoding_t
1029 GpgmeSigStat gpgme_sig_stat_t
1030 GpgmeSigMode gpgme_sig_mode_t
1031 GpgmeAttr gpgme_attr_t
1032 GpgmeValidity gpgme_validity_t
1033 GpgmeProtocol gpgme_protocol_t
1034 GpgmeKey gpgme_key_t
1035 GpgmePassphraseCb gpgme_passphrase_cb_t
1036 GpgmeProgressCb gpgme_progress_cb_t
1037 GpgmeIOCb gpgme_io_cb_t
1038 GpgmeRegisterIOCb gpgme_register_io_cb_t
1039 GpgmeRemoveIOCb gpgme_remove_io_cb_t
1040 GpgmeEventIO gpgme_event_io_t
1041 GpgmeEventIOCb gpgme_event_io_cb_t
1042 GpgmeIOCbs gpgme_io_cbs
1043 GpgmeDataReadCb gpgme_data_read_cb_t
1044 GpgmeDataWriteCb gpgme_data_write_cb_t
1045 GpgmeDataSeekCb gpgme_data_seek_cb_t
1046 GpgmeDataReleaseCb gpgme_data_release_cb_t
1047 GpgmeDataCbs gpgme_data_cbs_t
1048 GpgmeTrustItem gpgme_trust_item_t
1049 GpgmeStatusCode gpgme_status_code_t
1051 * gpgme_error_t is now identical to gpg_error_t, the error type
1052 provided by libgpg-error. More about using libgpg-error with GPGME
1053 can be found in the manual. All error symbols have been removed!
1055 * All functions and types in libgpg-error have been wrapped in GPGME.
1056 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1057 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1058 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1059 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1062 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1064 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1065 for encrypt, sign, encrypt-sign, decrypt, verify, and
1066 decrypt-verify operations. For verify operations on detached
1067 signatures, the progress callback is invoked for both the detached
1068 signature and the plaintext message, though.
1070 * gpgme_passphrase_cb_t has been changed to not provide a complete
1071 description, but the UID hint, passphrase info and a flag
1072 indicating if this is a repeated attempt individually, so the user
1073 can compose his own description from this information.
1075 The passphrase is not returned as a C string, but must be written
1076 to a file descriptor directly. This allows for secure passphrase
1079 The return type has been changed to gpgme_error_t value. This
1080 allowed to remove the gpgme_cancel function; just return
1081 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1083 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1084 The user is expected to write the response to the file descriptor,
1085 followed by a newline.
1087 * The recipients interface has been removed. Instead, you use
1088 NULL-terminated lists of keys for specifying the recipients of an
1089 encryption operation. Use the new encryption flag
1090 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1091 the keys (but note that in general this is not a good idea).
1093 This change has been made to the prototypes of gpgme_op_encrypt,
1094 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1095 gpgme_op_encrypt_sign_start.
1097 The export interface has been changed to use pattern strings like
1098 the keylist interface. Thus, new functions gpgme_op_export_ext and
1099 gpgme_op_export_ext_start have been added as well. Now the
1100 prototypes of gpgme_op_export_start and gpgme_op_export finally
1103 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1104 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1107 * gpgme_io_cb_t changed from a void function to a function returning
1108 a gpgme_error_t value. However, it will always return 0, so you
1109 can safely ignore the return value.
1111 * A new I/O callback event GPGME_EVENT_START has been added. The new
1112 requirement is that you must wait until this event until you are
1113 allowed to call the I/O callback handlers previously registered for
1114 this context operation. Calling I/O callback functions for this
1115 context operation before the start event happened is unsafe because
1116 it can lead to race conditions in a multi-threaded environment.
1118 * The idle function feature has been removed. It was not precisely
1119 defined in a multi-threaded environment and is obsoleted by the
1120 user I/O callback functions. If you still need a simple way to
1121 call something while waiting on one or multiple asynchronous
1122 operations to complete, don't set the HANG flag in gpgme_wait (note
1123 that this will return to your program more often than the idle
1126 * gpgme_wait can return NULL even if hang is true, if an error
1127 occurs. In that case *status contains the error code.
1129 * gpgme_get_engine_info was radically changed. Instead an XML
1130 string, an info structure of the new type gpgme_engine_info_t is
1131 returned. This makes it easier and more robust to evaluate the
1132 information in an application.
1134 * The new function gpgme_get_protocol_name can be used to convert a
1135 gpgme_protocol_t value into a string.
1137 * The status of a context operation is not checked anymore. Starting
1138 a new operation will silently cancel the previous one. Calling a
1139 function that requires you to have started an operation before without
1140 doing so is undefined.
1142 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1143 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1144 pointer to a structure which contains the fingerprint. This also
1145 works with gpgme_op_genkey_start. The structure also provides
1146 other information about the generated keys.
1151 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1153 printf ("%s\n", fpr);
1157 gpgme_genkey_result_t result;
1158 err = gpgme_op_genkey (ctx, NULL, NULL);
1161 result = gpgme_op_genkey_result (ctx);
1163 printf ("%s\n", result->fpr);
1166 * The new gpgme_op_import_result function provides detailed
1167 information about the result of an import operation in
1168 gpgme_import_result_t and gpgme_import_status_t objects.
1169 Thus, the gpgme_op_import_ext variant is deprecated.
1171 * The new gpgme_op_sign_result function provides detailed information
1172 about the result of a signing operation in gpgme_sign_result_t,
1173 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1175 * The new gpgme_op_encrypt_result function provides detailed
1176 information about the result of an encryption operation in
1177 a GpgmeEncryptResult object.
1179 * The new gpgme_op_decrypt_result function provides detailed
1180 information about the result of a decryption operation in
1181 a GpgmeDecryptResult object.
1183 * The new gpgme_op_verify_result function provides detailed
1184 information about the result of an verify operation in
1185 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1186 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1187 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1188 and gpgme_get_notation is removed.
1190 * GpgmeTrustItem objects have now directly accessible data, so the
1191 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1192 accessor functions are deprecated. Also, reference counting is
1193 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1194 (the gpgme_trust_item_release alias for the latter is deprecated).
1196 * Keys are not cached internally anymore, so the force_update argument
1197 to gpgme_get_key has been removed.
1199 * GpgmeKey objects have now directly accessible data so the
1200 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1201 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1202 functions are deprecated. Also, gpgme_key_release is now
1203 deprecated. The gpgme_key_get_as_xml function has been dropped.
1205 * Because all interfaces using attributes are deprecated, the
1206 GpgmeAttr data type is also deprecated.
1208 * The new gpgme_op_keylist_result function provides detailed
1209 information about the result of a key listing operation in
1210 a GpgmeKeyListResult object.
1212 * Now that each function comes with its own result retrieval
1213 interface, the generic gpgme_get_op_info interface is not useful
1214 anymore and dropped.
1216 * The type and mode of data objects is not available anymore.
1218 * Interface changes relative to the 0.4.0 release:
1219 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1220 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1221 GpgmeData DEPRECATED: Use gpgme_data_t.
1222 GpgmeError DEPRECATED: Use gpgme_error_t.
1223 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1224 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1225 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1226 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1227 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1228 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1229 GpgmeKey DEPRECATED: Use gpgme_key_t.
1230 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1231 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1232 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1233 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1234 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1235 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1236 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1237 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1238 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1239 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1240 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1241 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1242 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1243 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1244 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1247 gpgme_recipients_t NEW
1249 gpgme_data_encoding_t NEW
1250 gpgme_sig_stat_t NEW
1251 gpgme_sig_mode_t NEW
1253 gpgme_validity_t NEW
1254 gpgme_protocol_t NEW
1256 gpgme_passphrase_cb_t NEW
1257 gpgme_progress_cb_t NEW
1259 gpgme_register_io_cb_t NEW
1260 gpgme_remove_io_cb_t NEW
1261 gpgme_event_io_t NEW
1262 gpgme_event_io_cb_t NEW
1264 gpgme_data_read_cb_t NEW
1265 gpgme_data_write_cb_t NEW
1266 gpgme_data_seek_cb_t NEW
1267 gpgme_data_release_cb_t NEW
1268 gpgme_data_cbs_t NEW
1269 gpgme_trust_item_t NEW
1270 gpgme_status_code_t NEW
1271 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1272 gpgme_err_code_t NEW
1273 gpgme_err_source_t NEW
1275 gpgme_err_source NEW
1278 gpgme_error_from_errno NEW
1279 gpgme_err_make_from_errno NEW
1280 gpgme_err_code_from_errno NEW
1281 gpgme_err_code_to_errno NEW
1283 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1284 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1285 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1286 gpgme_edit_cb_t CHANGED: Write directly to FD.
1287 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1288 gpgme_op_verify CHANGED: Drop R_STAT argument.
1289 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1290 gpgme_wait CHANGED: Can return NULL even if hang is true.
1291 GpgmeIdleFunc REMOVED
1292 gpgme_register_idle REMOVED
1293 GpgmeRecipients REMOVED
1294 gpgme_recipients_new REMOVED
1295 gpgme_recipients_release REMOVED
1296 gpgme_recipients_add_name REMOVED
1297 gpgme_recipients_add_name_with_validity REMOVED
1298 gpgme_recipients_count REMOVED
1299 gpgme_recipients_enum_open REMOVED
1300 gpgme_recipients_enum_read REMOVED
1301 gpgme_recipients_enum_close REMOVED
1302 gpgme_encrypt_flags_t NEW
1303 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1304 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1305 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1306 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1307 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1308 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1309 gpgme_op_export CHANGED: User IDs passed as patterns.
1310 gpgme_op_export_ext_start NEW
1311 gpgme_op_export_ext NEW
1312 gpgme_keylist_mode_t NEW
1314 gpgme_engine_info_t NEW
1315 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1316 gpgme_get_protocol_name NEW
1317 gpgme_cancel REMOVED: Return error in callback directly.
1318 gpgme_op_genkey CHANGED: FPR argument dropped.
1319 gpgme_op_genkey_result NEW
1320 gpgme_genkey_result_t NEW
1321 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1322 gpgme_op_import_result NEW
1323 gpgme_import_status_t NEW
1324 gpgme_import_result_t NEW
1325 gpgme_pubkey_algo_t NEW
1326 gpgme_hash_algo_t NEW
1327 gpgme_invalid_key_t NEW
1328 gpgme_new_signature_t NEW
1329 gpgme_sign_result_t NEW
1330 gpgme_op_sign_result NEW
1331 gpgme_pubkey_algo_name NEW
1332 gpgme_hash_algo_name NEW
1333 gpgme_encrypt_result_t NEW
1334 gpgme_op_encrypt_result NEW
1335 gpgme_decrypt_result_t NEW
1336 gpgme_op_decrypt_result NEW
1337 gpgme_verify_result_t NEW
1338 gpgme_op_verify_result NEW
1339 gpgme_get_notation REMOVED: Access verify result directly instead.
1340 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1341 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1342 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1343 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1344 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1345 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1346 gpgme_trust_item_ref NEW
1347 gpgme_trust_item_unref NEW
1348 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1349 gpgme_trust_item_get_string_attr DEPRECATED
1350 gpgme_trust_item_get_ulong_attr DEPRECATED
1351 gpgme_get_key CHANGED: Removed force_update argument.
1355 gpgme_key_t CHANGED: Now has user accessible data members.
1356 gpgme_key_get_string_attr DEPRECATED
1357 gpgme_key_get_ulong_attr DEPRECATED
1358 gpgme_key_sig_get_string_attr DEPRECATED
1359 gpgme_key_sig_get_ulong_attr DEPRECATED
1360 gpgme_key_get_as_xml REMOVED
1361 gpgme_key_list_result_t NEW
1362 gpgme_op_keylist_result NEW
1363 gpgme_get_op_info REMOVED
1364 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1366 Noteworthy changes in version 0.4.0 (2002-12-23)
1367 ------------------------------------------------
1369 * Key generation returns the fingerprint of the generated key.
1371 * New convenience function gpgme_get_key.
1373 * Supports signatures of user IDs in keys via the new
1374 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1375 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1376 interfaces. The XML info about a key also includes the signatures
1379 * New data object interface, which is more flexible and transparent.
1381 * Interface changes relative to the 0.3.9 release:
1382 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1384 GpgmeDataWriteCb NEW
1386 GpgmeDataReleaseCb NEW
1388 gpgme_data_read CHANGED: Match read() closely.
1389 gpgme_data_write CHANGED: Match write() closely.
1391 gpgme_data_new_from_fd NEW
1392 gpgme_data_new_from_stream NEW
1393 gpgme_data_new_from_cbs NEW
1394 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1395 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1396 gpgme_data_get_type REMOVED: No replacement.
1397 gpgme_op_verify CHANGED: Take different data objects for
1398 signed text and plain text.
1399 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1400 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1401 gpgme_op_genkey CHANGED: New parameter FPR.
1402 GPGME_KEYLIST_MODE_SIGS NEW
1403 gpgme_key_sig_get_string_attr NEW
1404 gpgme_key_sig_get_ulong_attr NEW
1406 GPGME_ATTR_SIG_CLASS NEW
1407 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1409 Noteworthy changes in version 0.3.16 (2003-11-19)
1410 -------------------------------------------------
1412 * Compatibility fixes for GnuPG 1.9.x
1414 Noteworthy changes in version 0.3.15 (2003-02-18)
1415 -------------------------------------------------
1417 * The progress status is sent via the progress callbacks in
1420 * Bug fix for signing operations with explicit signer settings for
1423 Noteworthy changes in version 0.3.14 (2002-12-04)
1424 -------------------------------------------------
1426 * GPGME-Plug is now in its own package "cryptplug".
1428 * Workaround for a setlocale problem. Fixed a segv related to not
1429 correctly as closed marked file descriptors.
1431 Noteworthy changes in version 0.3.13 (2002-11-20)
1432 -------------------------------------------------
1434 * Release due to changes in gpgmeplug.
1436 Noteworthy changes in version 0.3.12 (2002-10-15)
1437 -------------------------------------------------
1439 * Fixed some bux with key listings.
1441 * The development has been branched to clean up some API issues.
1442 This 0.3 series will be kept for compatibility reasons; so do don't
1443 expect new features.
1445 Noteworthy changes in version 0.3.11 (2002-09-20)
1446 -------------------------------------------------
1450 Noteworthy changes in version 0.3.10 (2002-09-02)
1451 -------------------------------------------------
1453 * Setting the signing keys for the CMS protocol does now work.
1455 * The signers setting is honoured by gpgme_op_edit.
1457 Noteworthy changes in version 0.3.9 (2002-08-21)
1458 ------------------------------------------------
1460 * A spec file for creating RPMs has been added.
1462 * An experimental interface to GnuPG's --edit-key functionality is
1463 introduced, see gpgme_op_edit.
1465 * The new gpgme_import_ext function provides a convenient access to
1466 the number of processed keys.
1468 * Interface changes relative to the 0.3.8 release:
1469 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1472 gpgme_op_edit_start NEW
1474 gpgme_op_import_ext NEW
1475 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1477 Noteworthy changes in version 0.3.8 (2002-06-25)
1478 ------------------------------------------------
1480 * It is possible to use an outside event loop for the I/O to the
1481 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1483 * Interface changes relative to the 0.3.6 release:
1484 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1486 GpgmeRegisterIOCb NEW
1490 struct GpgmeIOCbs NEW
1491 gpgme_set_io_cbs NEW
1492 gpgme_get_io_cbs NEW
1493 GPGME_ATTR_ERRTOK NEW
1494 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1496 Noteworthy changes in version 0.3.7 (2002-06-04)
1497 ------------------------------------------------
1499 * GPGME_ATTR_OTRUST is implemented now.
1501 * A first step toward thread safeness has been achieved, see the
1502 documentation for details. Supported thread libraries are pthread
1505 Noteworthy changes in version 0.3.6 (2002-05-03)
1506 ------------------------------------------------
1508 * All error output of the gpgsm backend is send to the bit bucket.
1510 * The signature verification functions are extended. Instead of
1511 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1512 expired signatures. 2 new functions may be used to retrieve more
1513 detailed information like the signature expiration time and a
1514 validity information of the key without an extra key looking.
1516 * The current passphrase callback and progress meter callback can be
1517 retrieved with the new functions gpgme_get_passphrase_cb and
1518 gpgme_get_progress_cb respectively.
1520 * Interface changes relative to the 0.3.5 release:
1521 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1522 gpgme_get_passphrase_cb NEW
1523 gpgme_get_progress_cb NEW
1524 GpgmeDataEncoding NEW
1525 gpgme_data_set_encoding NEW
1526 gpgme_data_get_encoding NEW
1527 GPGME_SIG_STAT_GOOD_EXP NEW
1528 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1529 gpgme_op_verify CHANGED: Returns more status codes.
1530 GPGME_ATTR_SIG_STATUS NEW
1531 gpgme_get_sig_string_attr NEW
1532 gpgme_get_sig_ulong_attr NEW
1533 gpgme_get_protocol NEW
1534 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1536 Noteworthy changes in version 0.3.5 (2002-04-01)
1537 ------------------------------------------------
1539 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1540 case, symmetric encryption is performed. Note that this requires a
1541 passphrase from the user.
1543 * More information is returned for X.509 certificates.
1545 * Interface changes relative to the 0.3.4 release:
1546 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1547 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1548 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1550 Noteworthy changes in version 0.3.4 (2002-03-04)
1551 ------------------------------------------------
1553 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1554 some recipients have been invalid, whereas earlier versions
1555 succeeded in this case. The plaintext is still encrypted for all valid
1556 recipients, so the application might take this error as a hint that
1557 the ciphertext is not usable for all requested recipients.
1558 Information about invalid recipients is available with gpgme_get_op_info.
1560 * gpgme_op_verify now allows to pass an uninitialized data object as
1561 its plaintext argument to check for normal and cleartext
1562 signatures. The plaintext is then returned in the data object.
1564 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1565 to set and get the number of certifications to include in S/MIME
1568 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1569 to encrypt and sign a message in a combined operation.
1571 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1573 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1575 * Interface changes relative to the 0.3.3 release:
1576 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1577 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1578 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1579 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1580 gpgme_set_include_certs NEW
1581 gpgme_get_include_certs NEW
1582 gpgme_op_encrypt_sign NEW
1583 gpgme_op_encrypt_sign_start NEW
1584 gpgme_op_keylist_ext_start NEW
1585 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1587 Noteworthy changes in version 0.3.3 (2002-02-12)
1588 ------------------------------------------------
1590 * Fix the Makefile in jnlib.
1592 * Fix the test suite (hopefully). It should clean up all its state
1593 with `make check' now.
1596 Noteworthy changes in version 0.3.2 (2002-02-10)
1597 ------------------------------------------------
1599 * Remove erroneous dependency on libgcrypt in jnlib.
1602 Noteworthy changes in version 0.3.1 (2002-02-09)
1603 ------------------------------------------------
1605 * There is a Texinfo manual documenting the API.
1607 * The gpgme_set_keylist_mode function returns an error, and changed
1608 its meaning. It is no longer usable to select between normal and
1609 fast mode (newer versions of GnuPG will always be fast), but
1610 selects between local keyring, remote keyserver, or both.
1611 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1612 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1613 current setting, a fucntion gpgme_get_keylist_mode was added to
1614 retrieve the current mode.
1616 * gpgme_wait accepts a new argument STATUS to return the error status
1617 of the operation on the context. Its definition is closer to
1618 waitpid() now than before.
1620 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1621 type from off_t to the unsigned size_t.
1623 * The R_HD argument to the GpgmePassphraseCb type changed its type
1624 from void* to void**.
1626 * New interface gpgme_op_trustlist_end() to match
1627 gpgme_op_keylist_end().
1629 * The CryptPlug modules have been renamed to gpgme-openpgp and
1630 gpgme-smime, and they are installed in pkglibdir by `make install'.
1632 * An idle function can be registered with gpgme_register_idle().
1634 * The GpgSM backend supports key generation with gpgme_op_genkey().
1636 * Interface changes relative to the 0.3.0 release:
1637 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1638 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1639 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1640 gpgme_wait CHANGED: New argument STATUS.
1641 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1642 The function has a new meaning!
1643 gpgme_get_keylist_mode NEW
1644 GPGME_KEYLIST_MODE_LOCAL NEW
1645 GPGME_KEYLIST_MODE_EXTERN NEW
1646 gpgme_op_trustlist_next NEW
1648 gpgme_register_idle NEW
1649 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1651 Noteworthy changes in version 0.3.0 (2001-12-19)
1652 ------------------------------------------------
1654 * New interface gpgme_set_protocol() to set the protocol and thus the
1655 crypto engine to be used by the context. Currently, the OpenPGP
1656 and the CMS protocols are supported. They are specified by the new
1657 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1658 A new context uses the OpenPGP engine by default.
1660 * gpgme_get_engine_info() returns information for all crypto engines
1661 compiled into the library. The XML format has changed. To
1662 reliably get the version of a crypto engine, the <version> tag
1663 after the appropriate <protocol> tag has to be looked for.
1665 * New interface gpgme_engine_check_version(), obsoleting
1666 gpgme_check_engine(). Check the version of all engines you are
1667 supporting in your software.
1669 * GpgmeKey lists the user ids in the order as they are returned by
1670 GnuPG, first the primary key with index 0, then the sub-user ids.
1672 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1673 signatures simultaneously.
1675 * The new interface gpgme_op_keylist_end() terminates a pending
1676 keylist operation. A keylist operation is also terminated when
1677 gpgme_op_keylist_next() returns GPGME_EOF.
1679 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1680 cross-compiled, or even compiled without support for GnuPG
1683 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1684 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1685 in the path, but it can also be compiled without support for GpgSM
1686 (`--without-gpgsm').
1688 * CryptPlug modules for GPGME are included and can be enabled at
1689 configure time (`--enable-gpgmeplug'). There is one module which
1690 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1691 GpgSM engine (`gpgsmplug').
1693 * Interface changes relative to the latest 0.2.x release:
1694 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1695 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1696 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1697 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1698 gpgme_get_engine_info CHANGED: New format, extended content.
1699 gpgme_engine_check_version NEW
1700 gpgme_decrypt_verify_start NEW
1701 gpgme_decrypt_verify NEW
1702 gpgme_op_keylist_next NEW
1703 gpgme_set_protocol NEW
1704 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1707 Noteworthy changes in version 0.2.3 (2001-09-17)
1708 ------------------------------------------------
1710 * New function gpgme_get_op_info which can be used to get the micalg
1711 parameter needed for MOSS.
1713 * New functions gpgme_get_armor and gpgme_get_textmode.
1715 * The usual bug fixes and some minor functionality improvements.
1717 * Added a simple encryption component for MS-Windows; however the
1718 build procedure might have some problems.
1721 Noteworthy changes in version 0.2.2 (2001-06-12)
1722 ------------------------------------------------
1724 * Implemented a key cache.
1726 * Fixed a race condition under W32 and some other bug fixes.
1729 Noteworthy changes in version 0.2.1 (2001-04-02)
1730 ------------------------------------------------
1732 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1734 * Handle GnuPG's new key capabilities output and support revocation
1737 * Made the W32 support more robust.
1740 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
1743 This file is free software; as a special exception the author gives
1744 unlimited permission to copy and/or distribute it, with or without
1745 modifications, as long as this notice is preserved.
1747 This file is distributed in the hope that it will be useful, but
1748 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1749 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.