1 Noteworthy changes in version 1.7.0 (2016-09-21) [C26/A15/R0]
2 ------------------------------------------------
4 * New language bindings for Python 2 and 3.
6 * New language Bindings for C++ and the Qt-Framework API.
8 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
9 key creation easier (requires GnuPG 2.1).
11 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
12 management easier (requires GnuPG 2.1).
14 * New function gpgme_op_keysign to make key signing easier (requires
17 * New function gpgme_op_interact to replace the now deprecated
18 functions gpgme_op_edit and gpgme_op_card_edit.
20 * New function gpgme_pubkey_algo_string to convert a public key
21 algorithm into a GnuPG 2.1 style string.
23 * Support for GnuPG 2.1's TOFU trust model.
25 * Notation flags are now correctly set on verify.
27 * New global flag "require-gnupg" to set a minimal gnupg version.
29 * More supported items in gpgme_get_dirinfo.
31 * New function gpgme_data_set_flag and flag "size-hint".
33 * New function gpgme_set_ctx_flag and flags "full-status" and
36 * Improved gpgme_data_identify to distinguish more file types.
38 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
39 mixed public key and symmetric encryption.
41 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
43 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
44 signed data is a valid MIME part. This is to support future GnuPG
47 * Interface changes relative to the 1.6.0 release:
48 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
49 gpgme_pubkey_algo_string NEW.
51 gpgme_set_ctx_flag NEW.
52 gpgme_data_set_flag NEW.
53 gpgme_op_createkey NEW.
54 gpgme_op_createkey_start NEW.
55 gpgme_op_createsubkey NEW.
56 gpgme_op_createsubkey_start NEW.
57 gpgme_op_adduid_start NEW.
59 gpgme_op_revuid_start NEW.
61 gpgme_op_keysign_start NEW.
63 gpgme_op_tofu_policy_start NEW.
64 gpgme_op_tofu_policy NEW.
65 gpgme_op_interact_start NEW.
66 gpgme_op_interact NEW.
67 gpgme_interact_cb_t NEW.
68 gpgme_op_edit_start DEPRECATED.
69 gpgme_op_edit DEPRECATED.
70 gpgme_op_card_edit_start DEPRECATED.
71 gpgme_op_card_edit DEPRECATED.
72 gpgme_edit_cb_t DEPRECATED.
73 gpgme_status_code_t DEPRECATED.
74 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
75 gpgme_signature_t EXTENDED: New field key.
76 gpgme_key_t EXTENDED: New field fpr.
77 gpgme_subkey_t EXTENDED: New field keygrip.
78 gpgme_user_id_t EXTENDED: New field tofu.
79 gpgme_tofu_policy_t NEW.
80 gpgme_tofu_info_t NEW.
81 GPGME_STATUS_KEY_CONSIDERED NEW.
82 GPGME_STATUS_TOFU_USER NEW.
83 GPGME_STATUS_TOFU_STATS NEW.
84 GPGME_STATUS_TOFU_STATS_LONG NEW.
85 GPGME_STATUS_NOTATION_FLAGS NEW.
86 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
87 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
88 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
89 GPGME_DATA_ENCODING_MIME NEW.
90 GPGME_ENCRYPT_SYMMETRIC NEW.
91 GPGME_CREATE_SIGN NEW.
92 GPGME_CREATE_ENCR NEW.
93 GPGME_CREATE_CERT NEW.
94 GPGME_CREATE_AUTH NEW.
95 GPGME_CREATE_NOPASSWD NEW.
96 GPGME_CREATE_SELFSIGNED NEW.
97 GPGME_CREATE_NOSTORE NEW.
98 GPGME_CREATE_WANTPUB NEW.
99 GPGME_CREATE_WANTSEC NEW.
100 GPGME_CREATE_FORCE NEW.
101 GPGME_KEYSIGN_LOCAL NEW.
102 GPGME_KEYSIGN_LFSEP NEW.
103 GPGME_INTERACT_CARD NEW.
106 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
107 ------------------------------------------------
109 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
111 * Added gpgme_set_status_cb to allow a user to see some status
114 * Added an export mode for secret keys.
116 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
118 * The passphrase handler for the loopback mode has been improved and may
119 also be used with genkey.
121 * [w32] The standard GnuPG 2.1 install directory is now seached for
122 gpgconf.exe before a registry specified directory and the Gpg4win
125 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
128 * Interface changes relative to the 1.5.1 release:
129 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
130 gpgme_set_offline NEW.
131 gpgme_get_offline NEW.
132 gpgme_set_status_cb NEW.
133 gpgme_get_status_cb NEW.
134 GPGME_EXPORT_MODE_SECRET NEW
135 GPGME_EXPORT_MODE_RAW NEW.
136 GPGME_EXPORT_MODE_PKCS12 NEW.
139 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
140 ------------------------------------------------
142 * Fixed crash in key listings for user ids with a backslash.
144 * Fixed regression for GPGSM use with GnuPG < 2.1.
146 * Properly set signature summary for revoked OpenPGP keys.
149 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
150 ------------------------------------------------
152 * Fixed a possible crash in the debug code.
154 * Fixed building for Windows with newer versions of Mingw.
157 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
158 -------------------------------------------------------------
160 * The export key functions do now return an error if used with the
161 latest GnuPG version.
164 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
165 -------------------------------------------------------------
167 * gpgme-tool is now installed.
169 * Fix external listing for modern keyservers.
174 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
175 -------------------------------------------------------------
177 * Fixed possible overflow in gpgsm and uiserver engines.
180 * Added support for GnuPG 2.1's --with-secret option.
182 * Interface changes relative to the 1.5.0 release:
183 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
184 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
187 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
188 -------------------------------------------------------------
190 * On Unices the engine file names are not not anymore hardwired but
191 located via the envvar PATH. All options to set the name of the
192 engines for the configure run are removed.
194 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
195 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
196 is not found, GPGME looks for an engine named "gpg".
198 * New feature to use the gpgme I/O subsystem to run arbitrary
201 * New flag to use encryption without the default compression step.
203 * New function to access "gpg-conf --list-dirs"
205 * New configure option --enable-fixed-path for use by Android.
207 * Support ECC algorithms.
209 * Interface changes relative to the 1.4.3 release:
210 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
211 gpgme_get_dirinfo NEW.
212 gpgme_op_spawn_start NEW.
214 GPGME_PROTOCOL_SPAWN NEW.
215 GPGME_SPAWN_DETACHED NEW.
216 GPGME_SPAWN_ALLOW_SET_FG NEW.
217 GPGME_ENCRYPT_NO_COMPRESS NEW.
220 gpgme_subkey_t EXTENDED: New field curve.
221 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
222 GPGME_STATUS_MOUNTPOINT NEW.
223 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
224 GPGME_STATUS_ATTRIBUTE NEW.
225 GPGME_STATUS_BEGIN_SIGNING NEW.
226 GPGME_STATUS_KEY_NOT_CREATED NEW.
229 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
230 -------------------------------------------------------------
232 * The default engine names are now taken from the output of gpgconf.
233 If gpgconf is not found the use of gpg 1 is assumed.
235 * Under Windows the default engines names are first searched in the
236 installation directory of the gpgme DLL.
238 * New function gpgme_data_identify to detect the type of a message.
240 * Interface changes relative to the 1.4.2 release:
241 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
242 gpgme_signers_count NEW.
243 gpgme_data_type_t NEW.
244 gpgme_data_identify NEW.
247 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
248 -------------------------------------------------------------
250 * Allow symmetric encryption with gpgme_op_encrypt_sign.
252 * Fixed mismatching off_t definitions on Windows.
254 * Interface changes relative to the 1.4.1 release:
255 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
258 GPGME_PROTOCOL_OPENPGP NEW alias.
261 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
262 ------------------------------------------------------------
264 * Fixed reading of gpg.conf files with excessive use of the group
267 * Fixed building with the i686-w64-mingw32 toolchain.
269 * Disabled FD passing by default for Apple.
272 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
273 ------------------------------------------------------------
275 * New function gpgme_set_global_flag to help debugging on Android.
277 * New function gpgme_io_writen as a convenience wrapper around
280 * New functions to support the pinentry mode feature of GnuPG 2.1.
282 * New macro GPGME_VERSION_NUMBER to allow supporting different API
283 versions without the need for a configure test.
285 * Several improvements for gpgme-tool.
287 * Better logging of the common "invalid engine" error code.
289 * Support for FD passing is now enabled by default. The configure
290 option --disable-fd-passing may be used to disable this.
292 * Interface changes relative to the 1.3.1 release:
293 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
294 GPGME_VERSION_NUMBER NEW.
296 gpgme_set_global_flag NEW.
297 gpgme_set_pinentry_mode NEW.
298 gpgme_get_pinentry_mode NEW.
299 gpgme_pinentry_mode_t NEW.
300 GPGME_PINENTRY_MODE_DEFAULT NEW.
301 GPGME_PINENTRY_MODE_ASK NEW.
302 GPGME_PINENTRY_MODE_CANCEL NEW.
303 GPGME_PINENTRY_MODE_ERROR NEW.
304 GPGME_PINENTRY_MODE_LOOPBACK NEW.
307 Noteworthy changes in version 1.3.2 (2012-05-02)
308 ------------------------------------------------
310 * Remove support for libgpgme-pth. As far as we know, this was never used,
311 and GnuPG is going to use our own npth in the future.
313 * Fix signature summary information for a missing X.509 key.
315 * Fix parsing of dates >= year 2038.
318 Noteworthy changes in version 1.3.1 (2011-06-16)
319 ------------------------------------------------
321 * Ported to Windows CE.
323 * Detect GPG versions not supporting ---passwd.
325 * Interface changes relative to the 1.3.0 release:
326 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
327 GPGME_EXPORT_MODE_MINIMAL NEW
328 GPGME_STATUS_SUCCESS NEW
329 gpgme_err_code_from_syserror NEW
330 gpgme_err_set_errno NEW
331 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
332 gpgme_error_from_syserror NEW
333 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
336 Noteworthy changes in version 1.3.0 (2010-01-11)
337 ------------------------------------------------
339 * GPGME does not come with an internal libassuan version anymore.
340 The external libassuan 1.1.0 release or later is required. For
341 application programmers on systems that can resolve inter-library
342 dependencies at runtime, this is a transparent change.
344 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
346 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
348 * New API to change the passphrase of a key.
350 * Interface changes relative to the 1.2.0 release:
351 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
352 GPGME_STATUS_INV_SGNR NEW.
353 GPGME_STATUS_NO_SGNR NEW.
354 GPGME_PROTOCOL_G13 NEW.
355 gpgme_op_g13_mount NEW.
356 gpgme_g13_result_t NEW.
359 gpgme_op_passwd_start NEW.
361 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
364 Noteworthy changes in version 1.2.0 (2009-06-18)
365 ------------------------------------------------
367 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
370 * gpgme_new will fail if gpgme_check_version was not called, or a
371 selftest failed (for example, if -mms-bitfields was not used on
374 * New functions gpgme_io_read and gpgme_io_write for use with
375 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
377 * New functions gpgme_result_ref and gpgme_result_unref to detach
378 result structures from a context.
380 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
381 that allow to specify exported keys through gpgme_key_t objects
384 * New mode of operation gpgme_export_mode_t that allows exporting
387 * Interface changes relative to the 1.1.7 release:
388 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
389 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
390 GPGME_PROTOCOL_ASSUAN NEW.
391 gpgme_assuan_data_cb_t NEW.
392 gpgme_assuan_inquire_cb_t NEW.
393 gpgme_assuan_status_cb_t NEW.
394 gpgme_op_assuan_transact_start NEW.
395 gpgme_op_assuan_transact NEW.
396 gpgme_op_assuan_result NEW.
397 gpgme_op_import_keys NEW.
398 gpgme_op_import_keys_start NEW.
399 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
400 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
401 gpgme_check_version CHANGED: Is now a macro.
402 gpgme_new EXTENDED: More failure codes.
405 gpgme_result_ref NEW.
406 gpgme_result_unref NEW.
407 gpgme_export_mode_t NEW.
408 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
409 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
410 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
411 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
412 gpgme_op_export_keys_start NEW.
413 gpgme_op_export_keys NEW.
414 GPGME_DATA_ENCODING_URL NEW.
415 GPGME_DATA_ENCODING_URL0 NEW.
416 GPGME_DATA_ENCODING_URLESC NEW.
417 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
420 Noteworthy changes in version 1.1.8 (2008-12-08)
421 ------------------------------------------------
423 * SIGPIPE is now again ignored as described in the manual. Fixes
424 regresion introduced with 1.1.6.
427 Noteworthy changes in version 1.1.7 (2008-10-17)
428 ------------------------------------------------
430 * Using GPGME_KEYLIST_MODE_LOCAL combined with
431 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
432 --locate-keys feature of gpg (>= 2.0.10).
434 * The encoding of gpgme_data_t objects can affect the output encoding
435 of export, sign and encrypt operations now (the same operations
436 that are also affected by the ASCII mode switch). We believe this
437 change in the ABI is innocent enough not to break existing
438 applications (it only affects the S/MIME backend on certain
441 * The reference manual now includes the specification of "The GnuPG
444 * A new function gpgme_cancel_async can be used to asynchronously
445 cancel any pending operation at any time, from any thread.
447 * Interface changes relative to the 1.1.6 release:
448 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
449 gpgme_op_encrypt CHANGED: Output encoding can affect result.
450 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
451 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
452 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
453 gpgme_op_sign CHANGED: Output encoding can affect result.
454 gpgme_op_sign_start CHANGED: Output encoding can affect result.
455 gpgme_op_export CHANGED: Output encoding can affect result.
456 gpgme_op_export_start CHANGED: Output encoding can affect result.
457 gpgme_op_export_ext CHANGED: Output encoding can affect result.
458 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
459 gpgme_cancel_async NEW
460 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
463 Noteworthy changes in version 1.1.6 (2008-01-04)
464 ------------------------------------------------
466 * Bug fixes for for W32.
468 * A new, experimental (and thus undocumented and potentially
469 unstable) interface for accessing gpg-conf through GPGME has been
472 * Interface changes relative to the 1.1.1 release:
473 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
474 gpgme_signature_t EXTENDED: New field chain_model.
475 gpgme_op_getauditlog_start NEW.
476 gpgme_op_getauditlog NEW.
477 GPGME_AUDITLOG_HTML NEW.
478 GPGME_AUDITLOG_WITH_HELP NEW.
479 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
482 Noteworthy changes in version 1.1.5 (2007-07-09)
483 ------------------------------------------------
485 * Bug and portability fixes (mainly for W32).
488 Noteworthy changes in version 1.1.4 (2007-03-05)
489 ------------------------------------------------
491 * Detect and bail out on double plaintext messages. This is required
492 so that applications can properly detect the signed parts of a
493 message. Actual there is now a double protection as GnuPG 1.4.7
494 will detect this case too.
497 Noteworthy changes in version 1.1.3 (2007-01-29)
498 ------------------------------------------------
500 * Fixed a memory leak in gpgme_data_release_and_get_mem.
502 * Fixed a bug in Windows command line quoting.
505 Noteworthy changes in version 1.1.2 (2006-03-02)
506 ------------------------------------------------
508 * Fixed a bug in the W32 glib backend.
511 Noteworthy changes in version 1.1.1 (2006-02-23)
512 ------------------------------------------------
514 * Fixed a bug in that the fingerprints of subkeys are not available.
516 * Clarified usage of the SECRET flag in key listings. It is now
519 * Reading signature notations and policy URLs on key signatures is
520 supported. They can be found in the new field notations of the
521 gpgme_key_sig_t structure. This has to be enabled with the keylist
522 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
524 * A new gpgme_free() function solves the problem of using different
525 allocators in a single program. This function should now be used
526 instead calling free() to release the buffer returned by
527 gpgme_data_release_and_get_mem. It is recommended that you always
528 do this, but it is only necessary on certain platforms, so backwards
529 compatibility is provided. In other words: If free() worked for
530 you before, it will keep working.
532 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
533 They are analyzed by the verify handlers and made available in the
534 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
536 * Interface changes relative to the 1.1.0 release:
537 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
538 gpgme_key_sig_t EXTENDED: New field notations.
539 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
541 GPGME_STATUS_PKA_TRUST_BAD NEW
542 GPGME_STATUS_PKA_TRUST_GOOD NEW
543 gpgme_signature_t EXTENDED: New field pka_trust.
544 gpgme_signature_t EXTENDED: New field pka_address.
545 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
548 Noteworthy changes in version 1.1.0 (2005-10-01)
549 ------------------------------------------------
551 * You can now configure the backend engine file name and home
552 directory to be used, as default and per context.
554 * Information about the recipients of an encrypted text is now
555 available at decryption time.
557 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
558 and verify handlers, the information about the plaintext filename,
559 if available is made available in the new field file_name of the
560 respective result structure.
562 * The code for "automagically detecting the thread library" has been
563 removed from libgpgme. It is deprecated since version 0.4.3.
564 Since then, you had to link against libgpgme-pthread for
565 applications using pthread and libgpgme-pth for applications using
568 The code was removed because it caused compilation problems on
569 systems where the pthread.h header from GNU Pth is available in
570 addition to the system header (FreeBSD 6 and later for example).
572 * "./autogen.sh --build-w32" does now build gpgme.dll.
574 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
575 delimiter. The standard install directory is used when locating
576 gpg or gpgsm before finally falling back to the hardwired name.
578 * There is a new flag for keys and subkeys, is_qualified, which
579 indicates if a key can be used for qualified signatures according
580 to local government regulations.
582 * You can associate a filename with a data object using the new
583 function gpgme_data_set_file_name(). This filename will be stored
584 in the output when encrypting or signing the data and will be
585 returned when decrypting or verifying the output data.
587 * You can now set notation data at signature creation with the new
588 function gpgme_sig_notation_add().
590 * Interface changes relative to the 1.0.3 release:
591 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
592 gpgme_set_engine_info NEW
593 gpgme_ctx_get_engine_info NEW
594 gpgme_ctx_set_engine_info NEW
595 gpgme_recipient_t NEW
596 gpgme_decrypt_result_t EXTENDED: New field recipients.
597 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
598 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
599 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
600 GPGME_STATUS_PLAINTEXT NEW
601 gpgme_key_t EXTENDED: New field is_qualified.
602 gpgme_subkey_t EXTENDED: New field is_qualified.
603 gpgme_data_get_file_name NEW
604 gpgme_data_set_file_name NEW
605 gpgme_sig_notation_flags_t NEW
606 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
607 GPGME_SIG_NOTATAION_CRITICAL NEW
608 gpgme_sig_notation_clear NEW
609 gpgme_sig_notation_add NEW
610 gpgme_sig_notation_get NEW
611 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
614 Noteworthy changes in version 1.0.3 (2005-06-20)
615 ------------------------------------------------
617 * Previousy, GPGME would use a default "include certs" of 1. This
618 has been changed. Now GPGME will use the crypto backend engines
619 default unless you set the value with gpgme_set_include_certs()
620 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
621 as a value to explicitely request the new default behaviour.
623 Because the default changes, this is a slight change of the API
624 semantics. We consider it to be a bug fix.
626 * A bug which made GPGME hang has been fixed. If you have
627 experienced hanging before, please try out this version and let me
628 know if you still experience hanging problems.
630 * Interface changes relative to the 0.9.0 release:
631 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
632 gpgme_set_include_certs CHANGED DEFAULT
633 GPGME_INCLUDE_CERTS_DEFAULT NEW
634 GPGME_STATUS_SIG_SUBPACKET NEW
635 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
636 GPGME_STATUS_SC_OP_FAILURE NEW
637 GPGME_STATUS_SC_OP_SUCCESS NEW
638 GPGME_STATUS_CARDCTRL NEW
639 GPGME_STATUS_BACKUP_KEY_CREATED NEW
640 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
643 Noteworthy changes in version 1.0.2 (2004-12-28)
644 ------------------------------------------------
646 * Changed the license of the library to the GNU Lesser General Public
647 License (LGPL), version 2.1 or later.
650 Noteworthy changes in version 1.0.1 (2004-10-22)
651 ------------------------------------------------
656 Noteworthy changes in version 1.0.0 (2004-09-30)
657 ------------------------------------------------
659 * Version 1.0.0! We are proud to present you with a thoroughly
660 tested and stable version of the GPGME library. A big Thank You!
661 to all the people who made this possible.
663 The development will be branched into a stable 1.x.y series and the
666 * The gpgme.m4 macro supports checking the API version. Just prepend
667 it to the required version string, separated by a colon. For
668 example, this release has the version "1:1.0.0". The last release
669 to which this version is (mostly) ABI compatible is "1:0.4.2",
670 which is the default required version.
673 Noteworthy changes in version 0.9.0 (2004-06-08)
674 ------------------------------------------------
676 * The type gpgme_key_t has now a new field keylist_mode that contains
677 the keylist mode that was active at the time the key was retrieved.
679 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
680 that contains a flag indicating that the key should not have been
683 * Verifying a signature of a revoked key gives the correct result now
684 (GPG_ERR_CERT_REVOKED error code).
686 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
687 verify operations still allows you to look at the signature
690 * Clarified that patterns in keylisting operations have an upper
691 limit, and thus are not suited to list many keys at once by their
692 fingerprint. Also improve the error message if the pattern is too
693 long for the CMS protocol to handle.
695 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
696 gpgme_key_t EXTENDED: New field keylist_mode.
697 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
698 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
701 Noteworthy changes in version 0.4.7 (2004-04-29)
702 ------------------------------------------------
704 * Correctly initialize the fields expired, revoked, invalid, and
705 disabled in the gpgme_key_t structures.
707 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
708 accidently of type int instead unsigned int.
710 * Interface changes relative to the 0.4.5 release:
711 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
712 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
713 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
715 Noteworthy changes in version 0.4.6 (2004-04-06)
716 ------------------------------------------------
721 Noteworthy changes in version 0.4.5 (2004-03-07)
722 ------------------------------------------------
724 * GPGME is now compiled with LFS (large file support) by default.
725 This means that _all_ programs using GPGME must be compiled with
726 LFS support enabled by default. You can do this easily with
727 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
728 without autoconf by defining the preprocessor symbol
729 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
730 the C compiler command line, or by defining this preprocessor
731 symbol before including any system header files). For more
732 details, read the section on LFS in the manual.
734 Up to now, it was undocumented that GPGME was not using LFS.
735 But the public interfaces use off_t, and file descriptors are
736 exchanged between the application and GPGME. This was an oversight,
737 and bound to cause troubles in the future.
739 Writing GPGME as a dual mode library that seamlessly supports LFS
740 while keeping backwards compatibility is possible, but does not
741 solve the problem: Many applications already expect GPGME to have
742 LFS (they are compiled with off_t being a 64bit value). This is true
743 in particular for the popular Gtk+ and Qt programs.
745 So, although this is an ABI (but not an API) break, we will not
746 change the library version to reflect that. Because the interfaces
747 affected are probably not used yet in any GPGME 0.4 based
748 application, we don't expect any real failures from this change.
749 In fact, applications already using LFS will have some subtle bugs
752 However, if you encounter an application using GPGME 0.4.x that
753 does _not_ use LFS by default (off_t is a 32bit value), _and_
754 uses at least one of the functions gpgme_data_seek,
755 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
756 gpgme_data_new_from_cbs, then indeed this library will be ABI
757 incompatible with the program. As said above, we don't believe
758 such a program exists. If we are in error, then you have two
759 options: As a quick hack, you can configure GPGME with the
760 --disable-largefile option. This will revert the change, and GPGME
761 will not use LFS. However, GPGME will be incompatible with
762 programs that expect GPGME to use LFS. All applications are
763 required to use LFS when using GPGME, so this is only good as a
764 temporary local work-around.
766 The other option is to change the versioning of the library and
767 recompile all applications. We have reserved a special version of
768 the library for that, so you can do that without expecting a
769 version clash in the future. Furthermore, everyone who does this
770 will agree on the version to use (this is important for
771 distribution makers). Read the comment in configure.ac (before
772 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
773 blindly: As stated above, we think it is unlikely this measure is
774 needed. Still, it is there if necessary. If in doubt, contact us
775 and we will give our advise for your specific situation.
777 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
780 * New interface gpgme_cancel() that can be used to cancel
781 asynchronous operations.
783 * Interface changes relative to the 0.4.4 release:
784 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
785 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
786 gpgme_data_seek CHANGED: off_t is now a largefile type.
787 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
788 GPGME_KEYLIST_MODE_VALIDATE NEW
790 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
792 Noteworthy changes in version 0.4.4 (2004-01-12)
793 ------------------------------------------------
795 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
796 been renamed to "sig_class", to avoid clash with C++ compilers. In
797 the C API, the old name "class" has been preserved for backwards
798 compatibility, but is deprecated.
800 * Interface changes relative to the 0.4.3 release:
801 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
802 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
803 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
804 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
806 Noteworthy changes in version 0.4.3 (2003-10-06)
807 ------------------------------------------------
809 * libgpgme should not be used for threaded programs anymore. This
810 never worked reliably in all cases, because you had to
811 be careful about the linking order and libtool wouldn't do that for
812 you automatically. Instead, now you have to link against
813 libgpgme-pthread for applications using pthread and libgpgme-pth for
814 applications using GNU Pth.
816 The old code for automagically detecting the thread library is
817 still part of libgpgme, but it is DEPRECATED.
819 * There are new automake macros AM_PATH_GPGME_PTH and
820 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
821 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
822 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
823 variables of course also include the configuration for the thread
824 package itself. Alternatively, use libtool.
826 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
829 * gpgme-config doesn't support setting the prefix or exec prefix
830 anymore. I don't think it ever worked correctly, and it seems to
833 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
834 provided was not unique, instead returning the first matching key.
836 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
837 that indicates if the key can be used for authentication.
839 * gpgme_signature_t's status field is now correctly set to an error
840 with error code GPG_ERR_NO_PUBKEY if public key is not found.
842 * gpgme_new_signature_t's class field is now an unsigned int, rather
843 than an unsigned long (the old class field is preserved for
844 backwards compatibility).
846 * A new function gpgme_set_locale() is provided to allow configuring
847 the locale for the crypto backend. This is necessary for text
848 terminals so that programs like the pinentry can be started with
849 the right locale settings for the terminal the application is running
850 on, in case the terminal has different settings than the system
851 default (for example, if it is a remote terminal). You are highly
852 recommended to call the following functions directly after
857 setlocale (LC_ALL, "");
858 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
859 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
861 GPGME can not do this for you, as setlocale is not thread safe, and
862 there is no alternative.
864 * The signal action for SIGPIPE is now set to SIG_IGN by
865 gpgme_check_version, instead the first time a crypto engine is
866 started (which is not well defined).
868 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
869 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
870 to CRC24RFC2440. For now, these strings can be used as the MIC
871 parameter for PGP/MIME (if appropriately modified).
873 * Interface changes relative to the 0.4.2 release:
874 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
876 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
877 gpgme_key_t EXTENDED: New field can_authenticate.
878 gpgme_subkey_t EXTENDED: New field can_authenticate.
879 gpgme_new_signature_t CHANGED: New type for class field.
881 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
882 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
884 Noteworthy changes in version 0.4.2 (2003-07-30)
885 ------------------------------------------------
887 * Allow gpg-error to be in non-standard place when linking the test suite.
889 * Configure will fail now if gpg-error can not be found.
891 * Fixed initialized memory backed data objects for writing, which
892 caused the test program to crash (but only on Mac OS, surprisingly).
894 * Eliminate use of C99 constructs.
896 * Small improvements to the manual.
899 Noteworthy changes in version 0.4.1 (2003-06-06)
900 ------------------------------------------------
902 This is the release that 0.4.0 should have been. There are many
903 interface changes, please see below for the details. The changes are
904 sometimes the result of new functionality, but more often express a
905 paradigm shift. Others are an overdue cleanup to get GPGME in line
906 with the GNU coding standards and to make the interface more
907 self-consistent. Here is an overview on the changes:
909 All types have been renamed to conform to the GNU coding standards,
910 most of the time by keeping the whole name in lowercase and inserting
911 underscores between words.
913 All operations consistently only accept input parameters in their
914 invocation function, and return only an error code directly. Further
915 information about the result of the operation has to be retrieved
916 afterwards by calling one of the result functions. This unifies the
917 synchronous and the asynchronous interface.
919 The error values have been completely replaced by a more
920 sophisticated model that allows GPGME to transparently and accurately
921 report all errors from the other GnuPG components, irregardless of
922 process boundaries. This is achieved by using the library
923 libgpg-errors, which is shared by all GnuPG components. This library
924 is now required for GPGME.
926 The results of all operations are now provided by pointers to C
927 structs rather than by XML structs or in other ways.
929 Objects which used to be opaque (for example a key) are now pointers
930 to accessible structs, so no accessor functions are necessary.
932 Backward compatibility is provided where it was possible without too
933 much effort and did not collide with the overall sanitization effort.
934 However, this is only for ease of transition. NO DEPRECATED FUNCTION
935 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
936 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
937 Recommendations how to replace deprecated or removed functionality
938 can be found within the description of each change.
940 What follows are all changes to the interface and behaviour of GPGME
943 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
944 deprecated attributes will warn about use of obsolete functions and
945 type definitions. You can suppress these warnings by passing
946 -Wno-deprecated-declarations to the gcc command.
948 * The following types have been renamed. The old types are still
949 available as aliases, but they are deprecated now:
952 GpgmeData gpgme_data_t
953 GpgmeError gpgme_error_t
954 GpgmeDataEncoding gpgme_data_encoding_t
955 GpgmeSigStat gpgme_sig_stat_t
956 GpgmeSigMode gpgme_sig_mode_t
957 GpgmeAttr gpgme_attr_t
958 GpgmeValidity gpgme_validity_t
959 GpgmeProtocol gpgme_protocol_t
961 GpgmePassphraseCb gpgme_passphrase_cb_t
962 GpgmeProgressCb gpgme_progress_cb_t
963 GpgmeIOCb gpgme_io_cb_t
964 GpgmeRegisterIOCb gpgme_register_io_cb_t
965 GpgmeRemoveIOCb gpgme_remove_io_cb_t
966 GpgmeEventIO gpgme_event_io_t
967 GpgmeEventIOCb gpgme_event_io_cb_t
968 GpgmeIOCbs gpgme_io_cbs
969 GpgmeDataReadCb gpgme_data_read_cb_t
970 GpgmeDataWriteCb gpgme_data_write_cb_t
971 GpgmeDataSeekCb gpgme_data_seek_cb_t
972 GpgmeDataReleaseCb gpgme_data_release_cb_t
973 GpgmeDataCbs gpgme_data_cbs_t
974 GpgmeTrustItem gpgme_trust_item_t
975 GpgmeStatusCode gpgme_status_code_t
977 * gpgme_error_t is now identical to gpg_error_t, the error type
978 provided by libgpg-error. More about using libgpg-error with GPGME
979 can be found in the manual. All error symbols have been removed!
981 * All functions and types in libgpg-error have been wrapped in GPGME.
982 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
983 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
984 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
985 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
988 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
990 * GnuPG 1.2.2 is required. The progress callback is now also invoked
991 for encrypt, sign, encrypt-sign, decrypt, verify, and
992 decrypt-verify operations. For verify operations on detached
993 signatures, the progress callback is invoked for both the detached
994 signature and the plaintext message, though.
996 * gpgme_passphrase_cb_t has been changed to not provide a complete
997 description, but the UID hint, passphrase info and a flag
998 indicating if this is a repeated attempt individually, so the user
999 can compose his own description from this information.
1001 The passphrase is not returned as a C string, but must be written
1002 to a file descriptor directly. This allows for secure passphrase
1005 The return type has been changed to gpgme_error_t value. This
1006 allowed to remove the gpgme_cancel function; just return
1007 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1009 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1010 The user is expected to write the response to the file descriptor,
1011 followed by a newline.
1013 * The recipients interface has been removed. Instead, you use
1014 NULL-terminated lists of keys for specifying the recipients of an
1015 encryption operation. Use the new encryption flag
1016 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1017 the keys (but note that in general this is not a good idea).
1019 This change has been made to the prototypes of gpgme_op_encrypt,
1020 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1021 gpgme_op_encrypt_sign_start.
1023 The export interface has been changed to use pattern strings like
1024 the keylist interface. Thus, new functions gpgme_op_export_ext and
1025 gpgme_op_export_ext_start have been added as well. Now the
1026 prototypes of gpgme_op_export_start and gpgme_op_export finally
1029 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1030 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1033 * gpgme_io_cb_t changed from a void function to a function returning
1034 a gpgme_error_t value. However, it will always return 0, so you
1035 can safely ignore the return value.
1037 * A new I/O callback event GPGME_EVENT_START has been added. The new
1038 requirement is that you must wait until this event until you are
1039 allowed to call the I/O callback handlers previously registered for
1040 this context operation. Calling I/O callback functions for this
1041 context operation before the start event happened is unsafe because
1042 it can lead to race conditions in a multi-threaded environment.
1044 * The idle function feature has been removed. It was not precisely
1045 defined in a multi-threaded environment and is obsoleted by the
1046 user I/O callback functions. If you still need a simple way to
1047 call something while waiting on one or multiple asynchronous
1048 operations to complete, don't set the HANG flag in gpgme_wait (note
1049 that this will return to your program more often than the idle
1052 * gpgme_wait can return NULL even if hang is true, if an error
1053 occurs. In that case *status contains the error code.
1055 * gpgme_get_engine_info was radically changed. Instead an XML
1056 string, an info structure of the new type gpgme_engine_info_t is
1057 returned. This makes it easier and more robust to evaluate the
1058 information in an application.
1060 * The new function gpgme_get_protocol_name can be used to convert a
1061 gpgme_protocol_t value into a string.
1063 * The status of a context operation is not checked anymore. Starting
1064 a new operation will silently cancel the previous one. Calling a
1065 function that requires you to have started an operation before without
1066 doing so is undefined.
1068 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1069 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1070 pointer to a structure which contains the fingerprint. This also
1071 works with gpgme_op_genkey_start. The structure also provides
1072 other information about the generated keys.
1077 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1079 printf ("%s\n", fpr);
1083 gpgme_genkey_result_t result;
1084 err = gpgme_op_genkey (ctx, NULL, NULL);
1087 result = gpgme_op_genkey_result (ctx);
1089 printf ("%s\n", result->fpr);
1092 * The new gpgme_op_import_result function provides detailed
1093 information about the result of an import operation in
1094 gpgme_import_result_t and gpgme_import_status_t objects.
1095 Thus, the gpgme_op_import_ext variant is deprecated.
1097 * The new gpgme_op_sign_result function provides detailed information
1098 about the result of a signing operation in gpgme_sign_result_t,
1099 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1101 * The new gpgme_op_encrypt_result function provides detailed
1102 information about the result of an encryption operation in
1103 a GpgmeEncryptResult object.
1105 * The new gpgme_op_decrypt_result function provides detailed
1106 information about the result of a decryption operation in
1107 a GpgmeDecryptResult object.
1109 * The new gpgme_op_verify_result function provides detailed
1110 information about the result of an verify operation in
1111 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1112 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1113 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1114 and gpgme_get_notation is removed.
1116 * GpgmeTrustItem objects have now directly accessible data, so the
1117 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1118 accessor functions are deprecated. Also, reference counting is
1119 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1120 (the gpgme_trust_item_release alias for the latter is deprecated).
1122 * Keys are not cached internally anymore, so the force_update argument
1123 to gpgme_get_key has been removed.
1125 * GpgmeKey objects have now directly accessible data so the
1126 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1127 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1128 functions are deprecated. Also, gpgme_key_release is now
1129 deprecated. The gpgme_key_get_as_xml function has been dropped.
1131 * Because all interfaces using attributes are deprecated, the
1132 GpgmeAttr data type is also deprecated.
1134 * The new gpgme_op_keylist_result function provides detailed
1135 information about the result of a key listing operation in
1136 a GpgmeKeyListResult object.
1138 * Now that each function comes with its own result retrieval
1139 interface, the generic gpgme_get_op_info interface is not useful
1140 anymore and dropped.
1142 * The type and mode of data objects is not available anymore.
1144 * Interface changes relative to the 0.4.0 release:
1145 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1146 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1147 GpgmeData DEPRECATED: Use gpgme_data_t.
1148 GpgmeError DEPRECATED: Use gpgme_error_t.
1149 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1150 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1151 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1152 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1153 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1154 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1155 GpgmeKey DEPRECATED: Use gpgme_key_t.
1156 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1157 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1158 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1159 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1160 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1161 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1162 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1163 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1164 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1165 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1166 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1167 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1168 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1169 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1170 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1173 gpgme_recipients_t NEW
1175 gpgme_data_encoding_t NEW
1176 gpgme_sig_stat_t NEW
1177 gpgme_sig_mode_t NEW
1179 gpgme_validity_t NEW
1180 gpgme_protocol_t NEW
1182 gpgme_passphrase_cb_t NEW
1183 gpgme_progress_cb_t NEW
1185 gpgme_register_io_cb_t NEW
1186 gpgme_remove_io_cb_t NEW
1187 gpgme_event_io_t NEW
1188 gpgme_event_io_cb_t NEW
1190 gpgme_data_read_cb_t NEW
1191 gpgme_data_write_cb_t NEW
1192 gpgme_data_seek_cb_t NEW
1193 gpgme_data_release_cb_t NEW
1194 gpgme_data_cbs_t NEW
1195 gpgme_trust_item_t NEW
1196 gpgme_status_code_t NEW
1197 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1198 gpgme_err_code_t NEW
1199 gpgme_err_source_t NEW
1201 gpgme_err_source NEW
1204 gpgme_error_from_errno NEW
1205 gpgme_err_make_from_errno NEW
1206 gpgme_err_code_from_errno NEW
1207 gpgme_err_code_to_errno NEW
1209 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1210 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1211 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1212 gpgme_edit_cb_t CHANGED: Write directly to FD.
1213 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1214 gpgme_op_verify CHANGED: Drop R_STAT argument.
1215 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1216 gpgme_wait CHANGED: Can return NULL even if hang is true.
1217 GpgmeIdleFunc REMOVED
1218 gpgme_register_idle REMOVED
1219 GpgmeRecipients REMOVED
1220 gpgme_recipients_new REMOVED
1221 gpgme_recipients_release REMOVED
1222 gpgme_recipients_add_name REMOVED
1223 gpgme_recipients_add_name_with_validity REMOVED
1224 gpgme_recipients_count REMOVED
1225 gpgme_recipients_enum_open REMOVED
1226 gpgme_recipients_enum_read REMOVED
1227 gpgme_recipients_enum_close REMOVED
1228 gpgme_encrypt_flags_t NEW
1229 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1230 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1231 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1232 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1233 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1234 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1235 gpgme_op_export CHANGED: User IDs passed as patterns.
1236 gpgme_op_export_ext_start NEW
1237 gpgme_op_export_ext NEW
1238 gpgme_keylist_mode_t NEW
1240 gpgme_engine_info_t NEW
1241 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1242 gpgme_get_protocol_name NEW
1243 gpgme_cancel REMOVED: Return error in callback directly.
1244 gpgme_op_genkey CHANGED: FPR argument dropped.
1245 gpgme_op_genkey_result NEW
1246 gpgme_genkey_result_t NEW
1247 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1248 gpgme_op_import_result NEW
1249 gpgme_import_status_t NEW
1250 gpgme_import_result_t NEW
1251 gpgme_pubkey_algo_t NEW
1252 gpgme_hash_algo_t NEW
1253 gpgme_invalid_key_t NEW
1254 gpgme_new_signature_t NEW
1255 gpgme_sign_result_t NEW
1256 gpgme_op_sign_result NEW
1257 gpgme_pubkey_algo_name NEW
1258 gpgme_hash_algo_name NEW
1259 gpgme_encrypt_result_t NEW
1260 gpgme_op_encrypt_result NEW
1261 gpgme_decrypt_result_t NEW
1262 gpgme_op_decrypt_result NEW
1263 gpgme_verify_result_t NEW
1264 gpgme_op_verify_result NEW
1265 gpgme_get_notation REMOVED: Access verify result directly instead.
1266 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1267 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1268 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1269 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1270 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1271 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1272 gpgme_trust_item_ref NEW
1273 gpgme_trust_item_unref NEW
1274 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1275 gpgme_trust_item_get_string_attr DEPRECATED
1276 gpgme_trust_item_get_ulong_attr DEPRECATED
1277 gpgme_get_key CHANGED: Removed force_update argument.
1281 gpgme_key_t CHANGED: Now has user accessible data members.
1282 gpgme_key_get_string_attr DEPRECATED
1283 gpgme_key_get_ulong_attr DEPRECATED
1284 gpgme_key_sig_get_string_attr DEPRECATED
1285 gpgme_key_sig_get_ulong_attr DEPRECATED
1286 gpgme_key_get_as_xml REMOVED
1287 gpgme_key_list_result_t NEW
1288 gpgme_op_keylist_result NEW
1289 gpgme_get_op_info REMOVED
1290 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1292 Noteworthy changes in version 0.4.0 (2002-12-23)
1293 ------------------------------------------------
1295 * Key generation returns the fingerprint of the generated key.
1297 * New convenience function gpgme_get_key.
1299 * Supports signatures of user IDs in keys via the new
1300 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1301 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1302 interfaces. The XML info about a key also includes the signatures
1305 * New data object interface, which is more flexible and transparent.
1307 * Interface changes relative to the 0.3.9 release:
1308 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1310 GpgmeDataWriteCb NEW
1312 GpgmeDataReleaseCb NEW
1314 gpgme_data_read CHANGED: Match read() closely.
1315 gpgme_data_write CHANGED: Match write() closely.
1317 gpgme_data_new_from_fd NEW
1318 gpgme_data_new_from_stream NEW
1319 gpgme_data_new_from_cbs NEW
1320 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1321 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1322 gpgme_data_get_type REMOVED: No replacement.
1323 gpgme_op_verify CHANGED: Take different data objects for
1324 signed text and plain text.
1325 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1326 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1327 gpgme_op_genkey CHANGED: New parameter FPR.
1328 GPGME_KEYLIST_MODE_SIGS NEW
1329 gpgme_key_sig_get_string_attr NEW
1330 gpgme_key_sig_get_ulong_attr NEW
1332 GPGME_ATTR_SIG_CLASS NEW
1333 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1335 Noteworthy changes in version 0.3.16 (2003-11-19)
1336 -------------------------------------------------
1338 * Compatibility fixes for GnuPG 1.9.x
1340 Noteworthy changes in version 0.3.15 (2003-02-18)
1341 -------------------------------------------------
1343 * The progress status is sent via the progress callbacks in
1346 * Bug fix for signing operations with explicit signer settings for
1349 Noteworthy changes in version 0.3.14 (2002-12-04)
1350 -------------------------------------------------
1352 * GPGME-Plug is now in its own package "cryptplug".
1354 * Workaround for a setlocale problem. Fixed a segv related to not
1355 correctly as closed marked file descriptors.
1357 Noteworthy changes in version 0.3.13 (2002-11-20)
1358 -------------------------------------------------
1360 * Release due to changes in gpgmeplug.
1362 Noteworthy changes in version 0.3.12 (2002-10-15)
1363 -------------------------------------------------
1365 * Fixed some bux with key listings.
1367 * The development has been branched to clean up some API issues.
1368 This 0.3 series will be kept for compatibility reasons; so do don't
1369 expect new features.
1371 Noteworthy changes in version 0.3.11 (2002-09-20)
1372 -------------------------------------------------
1376 Noteworthy changes in version 0.3.10 (2002-09-02)
1377 -------------------------------------------------
1379 * Setting the signing keys for the CMS protocol does now work.
1381 * The signers setting is honoured by gpgme_op_edit.
1383 Noteworthy changes in version 0.3.9 (2002-08-21)
1384 ------------------------------------------------
1386 * A spec file for creating RPMs has been added.
1388 * An experimental interface to GnuPG's --edit-key functionality is
1389 introduced, see gpgme_op_edit.
1391 * The new gpgme_import_ext function provides a convenient access to
1392 the number of processed keys.
1394 * Interface changes relative to the 0.3.8 release:
1395 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1398 gpgme_op_edit_start NEW
1400 gpgme_op_import_ext NEW
1401 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1403 Noteworthy changes in version 0.3.8 (2002-06-25)
1404 ------------------------------------------------
1406 * It is possible to use an outside event loop for the I/O to the
1407 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1409 * Interface changes relative to the 0.3.6 release:
1410 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1412 GpgmeRegisterIOCb NEW
1416 struct GpgmeIOCbs NEW
1417 gpgme_set_io_cbs NEW
1418 gpgme_get_io_cbs NEW
1419 GPGME_ATTR_ERRTOK NEW
1420 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1422 Noteworthy changes in version 0.3.7 (2002-06-04)
1423 ------------------------------------------------
1425 * GPGME_ATTR_OTRUST is implemented now.
1427 * A first step toward thread safeness has been achieved, see the
1428 documentation for details. Supported thread libraries are pthread
1431 Noteworthy changes in version 0.3.6 (2002-05-03)
1432 ------------------------------------------------
1434 * All error output of the gpgsm backend is send to the bit bucket.
1436 * The signature verification functions are extended. Instead of
1437 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1438 expired signatures. 2 new functions may be used to retrieve more
1439 detailed information like the signature expiration time and a
1440 validity information of the key without an extra key looking.
1442 * The current passphrase callback and progress meter callback can be
1443 retrieved with the new functions gpgme_get_passphrase_cb and
1444 gpgme_get_progress_cb respectively.
1446 * Interface changes relative to the 0.3.5 release:
1447 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1448 gpgme_get_passphrase_cb NEW
1449 gpgme_get_progress_cb NEW
1450 GpgmeDataEncoding NEW
1451 gpgme_data_set_encoding NEW
1452 gpgme_data_get_encoding NEW
1453 GPGME_SIG_STAT_GOOD_EXP NEW
1454 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1455 gpgme_op_verify CHANGED: Returns more status codes.
1456 GPGME_ATTR_SIG_STATUS NEW
1457 gpgme_get_sig_string_attr NEW
1458 gpgme_get_sig_ulong_attr NEW
1459 gpgme_get_protocol NEW
1460 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1462 Noteworthy changes in version 0.3.5 (2002-04-01)
1463 ------------------------------------------------
1465 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1466 case, symmetric encryption is performed. Note that this requires a
1467 passphrase from the user.
1469 * More information is returned for X.509 certificates.
1471 * Interface changes relative to the 0.3.4 release:
1472 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1473 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1474 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1476 Noteworthy changes in version 0.3.4 (2002-03-04)
1477 ------------------------------------------------
1479 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1480 some recipients have been invalid, whereas earlier versions
1481 succeeded in this case. The plaintext is still encrypted for all valid
1482 recipients, so the application might take this error as a hint that
1483 the ciphertext is not usable for all requested recipients.
1484 Information about invalid recipients is available with gpgme_get_op_info.
1486 * gpgme_op_verify now allows to pass an uninitialized data object as
1487 its plaintext argument to check for normal and cleartext
1488 signatures. The plaintext is then returned in the data object.
1490 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1491 to set and get the number of certifications to include in S/MIME
1494 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1495 to encrypt and sign a message in a combined operation.
1497 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1499 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1501 * Interface changes relative to the 0.3.3 release:
1502 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1503 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1504 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1505 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1506 gpgme_set_include_certs NEW
1507 gpgme_get_include_certs NEW
1508 gpgme_op_encrypt_sign NEW
1509 gpgme_op_encrypt_sign_start NEW
1510 gpgme_op_keylist_ext_start NEW
1511 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1513 Noteworthy changes in version 0.3.3 (2002-02-12)
1514 ------------------------------------------------
1516 * Fix the Makefile in jnlib.
1518 * Fix the test suite (hopefully). It should clean up all its state
1519 with `make check' now.
1522 Noteworthy changes in version 0.3.2 (2002-02-10)
1523 ------------------------------------------------
1525 * Remove erroneous dependency on libgcrypt in jnlib.
1528 Noteworthy changes in version 0.3.1 (2002-02-09)
1529 ------------------------------------------------
1531 * There is a Texinfo manual documenting the API.
1533 * The gpgme_set_keylist_mode function returns an error, and changed
1534 its meaning. It is no longer usable to select between normal and
1535 fast mode (newer versions of GnuPG will always be fast), but
1536 selects between local keyring, remote keyserver, or both.
1537 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1538 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1539 current setting, a fucntion gpgme_get_keylist_mode was added to
1540 retrieve the current mode.
1542 * gpgme_wait accepts a new argument STATUS to return the error status
1543 of the operation on the context. Its definition is closer to
1544 waitpid() now than before.
1546 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1547 type from off_t to the unsigned size_t.
1549 * The R_HD argument to the GpgmePassphraseCb type changed its type
1550 from void* to void**.
1552 * New interface gpgme_op_trustlist_end() to match
1553 gpgme_op_keylist_end().
1555 * The CryptPlug modules have been renamed to gpgme-openpgp and
1556 gpgme-smime, and they are installed in pkglibdir by `make install'.
1558 * An idle function can be registered with gpgme_register_idle().
1560 * The GpgSM backend supports key generation with gpgme_op_genkey().
1562 * Interface changes relative to the 0.3.0 release:
1563 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1564 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1565 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1566 gpgme_wait CHANGED: New argument STATUS.
1567 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1568 The function has a new meaning!
1569 gpgme_get_keylist_mode NEW
1570 GPGME_KEYLIST_MODE_LOCAL NEW
1571 GPGME_KEYLIST_MODE_EXTERN NEW
1572 gpgme_op_trustlist_next NEW
1574 gpgme_register_idle NEW
1575 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1577 Noteworthy changes in version 0.3.0 (2001-12-19)
1578 ------------------------------------------------
1580 * New interface gpgme_set_protocol() to set the protocol and thus the
1581 crypto engine to be used by the context. Currently, the OpenPGP
1582 and the CMS protocols are supported. They are specified by the new
1583 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1584 A new context uses the OpenPGP engine by default.
1586 * gpgme_get_engine_info() returns information for all crypto engines
1587 compiled into the library. The XML format has changed. To
1588 reliably get the version of a crypto engine, the <version> tag
1589 after the appropriate <protocol> tag has to be looked for.
1591 * New interface gpgme_engine_check_version(), obsoleting
1592 gpgme_check_engine(). Check the version of all engines you are
1593 supporting in your software.
1595 * GpgmeKey lists the user ids in the order as they are returned by
1596 GnuPG, first the primary key with index 0, then the sub-user ids.
1598 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1599 signatures simultaneously.
1601 * The new interface gpgme_op_keylist_end() terminates a pending
1602 keylist operation. A keylist operation is also terminated when
1603 gpgme_op_keylist_next() returns GPGME_EOF.
1605 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1606 cross-compiled, or even compiled without support for GnuPG
1609 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1610 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1611 in the path, but it can also be compiled without support for GpgSM
1612 (`--without-gpgsm').
1614 * CryptPlug modules for GPGME are included and can be enabled at
1615 configure time (`--enable-gpgmeplug'). There is one module which
1616 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1617 GpgSM engine (`gpgsmplug').
1619 * Interface changes relative to the latest 0.2.x release:
1620 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1621 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1622 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1623 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1624 gpgme_get_engine_info CHANGED: New format, extended content.
1625 gpgme_engine_check_version NEW
1626 gpgme_decrypt_verify_start NEW
1627 gpgme_decrypt_verify NEW
1628 gpgme_op_keylist_next NEW
1629 gpgme_set_protocol NEW
1630 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1633 Noteworthy changes in version 0.2.3 (2001-09-17)
1634 ------------------------------------------------
1636 * New function gpgme_get_op_info which can be used to get the micalg
1637 parameter needed for MOSS.
1639 * New functions gpgme_get_armor and gpgme_get_textmode.
1641 * The usual bug fixes and some minor functionality improvements.
1643 * Added a simple encryption component for MS-Windows; however the
1644 build procedure might have some problems.
1647 Noteworthy changes in version 0.2.2 (2001-06-12)
1648 ------------------------------------------------
1650 * Implemented a key cache.
1652 * Fixed a race condition under W32 and some other bug fixes.
1655 Noteworthy changes in version 0.2.1 (2001-04-02)
1656 ------------------------------------------------
1658 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1660 * Handle GnuPG's new key capabilities output and support revocation
1663 * Made the W32 support more robust.
1666 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
1669 This file is free software; as a special exception the author gives
1670 unlimited permission to copy and/or distribute it, with or without
1671 modifications, as long as this notice is preserved.
1673 This file is distributed in the hope that it will be useful, but
1674 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1675 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.