1 Noteworthy changes in version 1.7.1 (2016-10-18)
2 ------------------------------------------------
4 * Fixed problems with the new language bindings.
6 * New helper function gpgme_addrspec_from_uid.
8 * Use option --exit-on-status-write-error with newer gpg versions.
10 * qt: Missed API from the Qt Binding inclusion has
13 * qt: abstractimportjob.h is now installed to that
14 ImportJobs can be used again.
16 * qt: Fixed spelling error in API (startReceive).
18 * Interface changes relative to the 1.7.0 release:
19 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 gpgme_addrspec_from_uid NEW.
21 qt: WksPublishJob::startRecieve RENAMED to ::startReceive.
22 qt: MultiDeleteJob NEW.
23 qt: AbstractImportJob NEW.
25 cpp: Signature::key(bool, bool) NEW.
26 cpp: UserID::addrSpecFromString(const char*) NEW.
27 cpp: UserID::addrSpec() NEW.
29 [c=C27/A16/R0 cpp=C8/A2/R0 qt=C7/A0/R0]
32 Noteworthy changes in version 1.7.0 (2016-09-21)
33 ------------------------------------------------
35 * New language bindings for Python 2 and 3.
37 * New language Bindings for C++ and the Qt-Framework API.
39 * New functions gpgme_op_createkey and gpgme_op_createsubkey to make
40 key creation easier (requires GnuPG 2.1).
42 * New functions gpgme_op_adduid and gpgme_op_revuid to make user id
43 management easier (requires GnuPG 2.1).
45 * New function gpgme_op_keysign to make key signing easier (requires
48 * New function gpgme_op_interact to replace the now deprecated
49 functions gpgme_op_edit and gpgme_op_card_edit.
51 * New function gpgme_pubkey_algo_string to convert a public key
52 algorithm into a GnuPG 2.1 style string.
54 * Support for GnuPG 2.1's TOFU trust model.
56 * Notation flags are now correctly set on verify.
58 * New global flag "require-gnupg" to set a minimal gnupg version.
60 * More supported items in gpgme_get_dirinfo.
62 * New function gpgme_data_set_flag and flag "size-hint".
64 * New function gpgme_set_ctx_flag and flags "full-status" and
67 * Improved gpgme_data_identify to distinguish more file types.
69 * New flag GPGME_ENCRYPT_SYMMETRIC for gpgme_op_encrypt to allow
70 mixed public key and symmetric encryption.
72 * New field KEYGRIP in gpgme_subkey_t. New fields FPR in gpgme_key_t.
74 * New flag GPGME_DATA_ENCODING_MIME to declare that the encrypted or
75 signed data is a valid MIME part. This is to support future GnuPG
78 * Interface changes relative to the 1.6.0 release:
79 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
80 gpgme_pubkey_algo_string NEW.
82 gpgme_set_ctx_flag NEW.
83 gpgme_data_set_flag NEW.
84 gpgme_op_createkey NEW.
85 gpgme_op_createkey_start NEW.
86 gpgme_op_createsubkey NEW.
87 gpgme_op_createsubkey_start NEW.
88 gpgme_op_adduid_start NEW.
90 gpgme_op_revuid_start NEW.
92 gpgme_op_keysign_start NEW.
94 gpgme_op_tofu_policy_start NEW.
95 gpgme_op_tofu_policy NEW.
96 gpgme_op_interact_start NEW.
97 gpgme_op_interact NEW.
98 gpgme_interact_cb_t NEW.
99 gpgme_op_edit_start DEPRECATED.
100 gpgme_op_edit DEPRECATED.
101 gpgme_op_card_edit_start DEPRECATED.
102 gpgme_op_card_edit DEPRECATED.
103 gpgme_edit_cb_t DEPRECATED.
104 gpgme_status_code_t DEPRECATED.
105 gpgme_genkey_result_t EXTENDED: New fields pubkey and seckey.
106 gpgme_signature_t EXTENDED: New field key.
107 gpgme_key_t EXTENDED: New field fpr.
108 gpgme_subkey_t EXTENDED: New field keygrip.
109 gpgme_user_id_t EXTENDED: New field tofu.
110 gpgme_tofu_policy_t NEW.
111 gpgme_tofu_info_t NEW.
112 GPGME_STATUS_KEY_CONSIDERED NEW.
113 GPGME_STATUS_TOFU_USER NEW.
114 GPGME_STATUS_TOFU_STATS NEW.
115 GPGME_STATUS_TOFU_STATS_LONG NEW.
116 GPGME_STATUS_NOTATION_FLAGS NEW.
117 GPGME_KEYLIST_MODE_WITH_TOFU NEW.
118 GPGME_DATA_TYPE_PGP_ENCRYPTED NEW.
119 GPGME_DATA_TYPE_PGP_SIGNATURE NEW.
120 GPGME_DATA_ENCODING_MIME NEW.
121 GPGME_ENCRYPT_SYMMETRIC NEW.
122 GPGME_CREATE_SIGN NEW.
123 GPGME_CREATE_ENCR NEW.
124 GPGME_CREATE_CERT NEW.
125 GPGME_CREATE_AUTH NEW.
126 GPGME_CREATE_NOPASSWD NEW.
127 GPGME_CREATE_SELFSIGNED NEW.
128 GPGME_CREATE_NOSTORE NEW.
129 GPGME_CREATE_WANTPUB NEW.
130 GPGME_CREATE_WANTSEC NEW.
131 GPGME_CREATE_FORCE NEW.
132 GPGME_KEYSIGN_LOCAL NEW.
133 GPGME_KEYSIGN_LFSEP NEW.
134 GPGME_INTERACT_CARD NEW.
136 [c=C26/A15/R0 cpp=C6/A0/R1 qt=C6/A0/R1]
139 Noteworthy changes in version 1.6.0 (2015-08-26) [C25/A14/R0]
140 ------------------------------------------------
142 * Added gpgme_set_offline to do a key listinging w/o requiring CRL.
144 * Added gpgme_set_status_cb to allow a user to see some status
147 * Added an export mode for secret keys.
149 * More precise error codes are returned if GnuPG >= 2.1.8 is used.
151 * The passphrase handler for the loopback mode has been improved and may
152 also be used with genkey.
154 * [w32] The standard GnuPG 2.1 install directory is now seached for
155 gpgconf.exe before a registry specified directory and the Gpg4win
158 * [w32] gpgme-w32spawn.exe will now only be searched in the gpgme DLL
161 * Interface changes relative to the 1.5.1 release:
162 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
163 gpgme_set_offline NEW.
164 gpgme_get_offline NEW.
165 gpgme_set_status_cb NEW.
166 gpgme_get_status_cb NEW.
167 GPGME_EXPORT_MODE_SECRET NEW
168 GPGME_EXPORT_MODE_RAW NEW.
169 GPGME_EXPORT_MODE_PKCS12 NEW.
172 Noteworthy changes in version 1.5.5 (2015-06-08) [C24/A13/R4]
173 ------------------------------------------------
175 * Fixed crash in key listings for user ids with a backslash.
177 * Fixed regression for GPGSM use with GnuPG < 2.1.
179 * Properly set signature summary for revoked OpenPGP keys.
182 Noteworthy changes in version 1.5.4 (2015-04-13) [C24/A13/R3]
183 ------------------------------------------------
185 * Fixed a possible crash in the debug code.
187 * Fixed building for Windows with newer versions of Mingw.
190 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
191 -------------------------------------------------------------
193 * The export key functions do now return an error if used with the
194 latest GnuPG version.
197 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
198 -------------------------------------------------------------
200 * gpgme-tool is now installed.
202 * Fix external listing for modern keyservers.
207 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
208 -------------------------------------------------------------
210 * Fixed possible overflow in gpgsm and uiserver engines.
213 * Added support for GnuPG 2.1's --with-secret option.
215 * Interface changes relative to the 1.5.0 release:
216 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
217 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
220 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
221 -------------------------------------------------------------
223 * On Unices the engine file names are not not anymore hardwired but
224 located via the envvar PATH. All options to set the name of the
225 engines for the configure run are removed.
227 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
228 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
229 is not found, GPGME looks for an engine named "gpg".
231 * New feature to use the gpgme I/O subsystem to run arbitrary
234 * New flag to use encryption without the default compression step.
236 * New function to access "gpg-conf --list-dirs"
238 * New configure option --enable-fixed-path for use by Android.
240 * Support ECC algorithms.
242 * Interface changes relative to the 1.4.3 release:
243 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
244 gpgme_get_dirinfo NEW.
245 gpgme_op_spawn_start NEW.
247 GPGME_PROTOCOL_SPAWN NEW.
248 GPGME_SPAWN_DETACHED NEW.
249 GPGME_SPAWN_ALLOW_SET_FG NEW.
250 GPGME_ENCRYPT_NO_COMPRESS NEW.
253 gpgme_subkey_t EXTENDED: New field curve.
254 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
255 GPGME_STATUS_MOUNTPOINT NEW.
256 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
257 GPGME_STATUS_ATTRIBUTE NEW.
258 GPGME_STATUS_BEGIN_SIGNING NEW.
259 GPGME_STATUS_KEY_NOT_CREATED NEW.
262 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
263 -------------------------------------------------------------
265 * The default engine names are now taken from the output of gpgconf.
266 If gpgconf is not found the use of gpg 1 is assumed.
268 * Under Windows the default engines names are first searched in the
269 installation directory of the gpgme DLL.
271 * New function gpgme_data_identify to detect the type of a message.
273 * Interface changes relative to the 1.4.2 release:
274 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
275 gpgme_signers_count NEW.
276 gpgme_data_type_t NEW.
277 gpgme_data_identify NEW.
280 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
281 -------------------------------------------------------------
283 * Allow symmetric encryption with gpgme_op_encrypt_sign.
285 * Fixed mismatching off_t definitions on Windows.
287 * Interface changes relative to the 1.4.1 release:
288 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
291 GPGME_PROTOCOL_OPENPGP NEW alias.
294 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
295 ------------------------------------------------------------
297 * Fixed reading of gpg.conf files with excessive use of the group
300 * Fixed building with the i686-w64-mingw32 toolchain.
302 * Disabled FD passing by default for Apple.
305 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
306 ------------------------------------------------------------
308 * New function gpgme_set_global_flag to help debugging on Android.
310 * New function gpgme_io_writen as a convenience wrapper around
313 * New functions to support the pinentry mode feature of GnuPG 2.1.
315 * New macro GPGME_VERSION_NUMBER to allow supporting different API
316 versions without the need for a configure test.
318 * Several improvements for gpgme-tool.
320 * Better logging of the common "invalid engine" error code.
322 * Support for FD passing is now enabled by default. The configure
323 option --disable-fd-passing may be used to disable this.
325 * Interface changes relative to the 1.3.1 release:
326 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
327 GPGME_VERSION_NUMBER NEW.
329 gpgme_set_global_flag NEW.
330 gpgme_set_pinentry_mode NEW.
331 gpgme_get_pinentry_mode NEW.
332 gpgme_pinentry_mode_t NEW.
333 GPGME_PINENTRY_MODE_DEFAULT NEW.
334 GPGME_PINENTRY_MODE_ASK NEW.
335 GPGME_PINENTRY_MODE_CANCEL NEW.
336 GPGME_PINENTRY_MODE_ERROR NEW.
337 GPGME_PINENTRY_MODE_LOOPBACK NEW.
340 Noteworthy changes in version 1.3.2 (2012-05-02)
341 ------------------------------------------------
343 * Remove support for libgpgme-pth. As far as we know, this was never used,
344 and GnuPG is going to use our own npth in the future.
346 * Fix signature summary information for a missing X.509 key.
348 * Fix parsing of dates >= year 2038.
351 Noteworthy changes in version 1.3.1 (2011-06-16)
352 ------------------------------------------------
354 * Ported to Windows CE.
356 * Detect GPG versions not supporting ---passwd.
358 * Interface changes relative to the 1.3.0 release:
359 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
360 GPGME_EXPORT_MODE_MINIMAL NEW
361 GPGME_STATUS_SUCCESS NEW
362 gpgme_err_code_from_syserror NEW
363 gpgme_err_set_errno NEW
364 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
365 gpgme_error_from_syserror NEW
366 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
369 Noteworthy changes in version 1.3.0 (2010-01-11)
370 ------------------------------------------------
372 * GPGME does not come with an internal libassuan version anymore.
373 The external libassuan 1.1.0 release or later is required. For
374 application programmers on systems that can resolve inter-library
375 dependencies at runtime, this is a transparent change.
377 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
379 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
381 * New API to change the passphrase of a key.
383 * Interface changes relative to the 1.2.0 release:
384 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
385 GPGME_STATUS_INV_SGNR NEW.
386 GPGME_STATUS_NO_SGNR NEW.
387 GPGME_PROTOCOL_G13 NEW.
388 gpgme_op_g13_mount NEW.
389 gpgme_g13_result_t NEW.
392 gpgme_op_passwd_start NEW.
394 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
397 Noteworthy changes in version 1.2.0 (2009-06-18)
398 ------------------------------------------------
400 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
403 * gpgme_new will fail if gpgme_check_version was not called, or a
404 selftest failed (for example, if -mms-bitfields was not used on
407 * New functions gpgme_io_read and gpgme_io_write for use with
408 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
410 * New functions gpgme_result_ref and gpgme_result_unref to detach
411 result structures from a context.
413 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
414 that allow to specify exported keys through gpgme_key_t objects
417 * New mode of operation gpgme_export_mode_t that allows exporting
420 * Interface changes relative to the 1.1.7 release:
421 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
422 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
423 GPGME_PROTOCOL_ASSUAN NEW.
424 gpgme_assuan_data_cb_t NEW.
425 gpgme_assuan_inquire_cb_t NEW.
426 gpgme_assuan_status_cb_t NEW.
427 gpgme_op_assuan_transact_start NEW.
428 gpgme_op_assuan_transact NEW.
429 gpgme_op_assuan_result NEW.
430 gpgme_op_import_keys NEW.
431 gpgme_op_import_keys_start NEW.
432 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
433 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
434 gpgme_check_version CHANGED: Is now a macro.
435 gpgme_new EXTENDED: More failure codes.
438 gpgme_result_ref NEW.
439 gpgme_result_unref NEW.
440 gpgme_export_mode_t NEW.
441 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
442 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
443 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
444 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
445 gpgme_op_export_keys_start NEW.
446 gpgme_op_export_keys NEW.
447 GPGME_DATA_ENCODING_URL NEW.
448 GPGME_DATA_ENCODING_URL0 NEW.
449 GPGME_DATA_ENCODING_URLESC NEW.
450 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
453 Noteworthy changes in version 1.1.8 (2008-12-08)
454 ------------------------------------------------
456 * SIGPIPE is now again ignored as described in the manual. Fixes
457 regresion introduced with 1.1.6.
460 Noteworthy changes in version 1.1.7 (2008-10-17)
461 ------------------------------------------------
463 * Using GPGME_KEYLIST_MODE_LOCAL combined with
464 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
465 --locate-keys feature of gpg (>= 2.0.10).
467 * The encoding of gpgme_data_t objects can affect the output encoding
468 of export, sign and encrypt operations now (the same operations
469 that are also affected by the ASCII mode switch). We believe this
470 change in the ABI is innocent enough not to break existing
471 applications (it only affects the S/MIME backend on certain
474 * The reference manual now includes the specification of "The GnuPG
477 * A new function gpgme_cancel_async can be used to asynchronously
478 cancel any pending operation at any time, from any thread.
480 * Interface changes relative to the 1.1.6 release:
481 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
482 gpgme_op_encrypt CHANGED: Output encoding can affect result.
483 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
484 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
485 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
486 gpgme_op_sign CHANGED: Output encoding can affect result.
487 gpgme_op_sign_start CHANGED: Output encoding can affect result.
488 gpgme_op_export CHANGED: Output encoding can affect result.
489 gpgme_op_export_start CHANGED: Output encoding can affect result.
490 gpgme_op_export_ext CHANGED: Output encoding can affect result.
491 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
492 gpgme_cancel_async NEW
493 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
496 Noteworthy changes in version 1.1.6 (2008-01-04)
497 ------------------------------------------------
499 * Bug fixes for for W32.
501 * A new, experimental (and thus undocumented and potentially
502 unstable) interface for accessing gpg-conf through GPGME has been
505 * Interface changes relative to the 1.1.1 release:
506 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
507 gpgme_signature_t EXTENDED: New field chain_model.
508 gpgme_op_getauditlog_start NEW.
509 gpgme_op_getauditlog NEW.
510 GPGME_AUDITLOG_HTML NEW.
511 GPGME_AUDITLOG_WITH_HELP NEW.
512 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
515 Noteworthy changes in version 1.1.5 (2007-07-09)
516 ------------------------------------------------
518 * Bug and portability fixes (mainly for W32).
521 Noteworthy changes in version 1.1.4 (2007-03-05)
522 ------------------------------------------------
524 * Detect and bail out on double plaintext messages. This is required
525 so that applications can properly detect the signed parts of a
526 message. Actual there is now a double protection as GnuPG 1.4.7
527 will detect this case too.
530 Noteworthy changes in version 1.1.3 (2007-01-29)
531 ------------------------------------------------
533 * Fixed a memory leak in gpgme_data_release_and_get_mem.
535 * Fixed a bug in Windows command line quoting.
538 Noteworthy changes in version 1.1.2 (2006-03-02)
539 ------------------------------------------------
541 * Fixed a bug in the W32 glib backend.
544 Noteworthy changes in version 1.1.1 (2006-02-23)
545 ------------------------------------------------
547 * Fixed a bug in that the fingerprints of subkeys are not available.
549 * Clarified usage of the SECRET flag in key listings. It is now
552 * Reading signature notations and policy URLs on key signatures is
553 supported. They can be found in the new field notations of the
554 gpgme_key_sig_t structure. This has to be enabled with the keylist
555 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
557 * A new gpgme_free() function solves the problem of using different
558 allocators in a single program. This function should now be used
559 instead calling free() to release the buffer returned by
560 gpgme_data_release_and_get_mem. It is recommended that you always
561 do this, but it is only necessary on certain platforms, so backwards
562 compatibility is provided. In other words: If free() worked for
563 you before, it will keep working.
565 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
566 They are analyzed by the verify handlers and made available in the
567 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
569 * Interface changes relative to the 1.1.0 release:
570 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
571 gpgme_key_sig_t EXTENDED: New field notations.
572 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
574 GPGME_STATUS_PKA_TRUST_BAD NEW
575 GPGME_STATUS_PKA_TRUST_GOOD NEW
576 gpgme_signature_t EXTENDED: New field pka_trust.
577 gpgme_signature_t EXTENDED: New field pka_address.
578 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
581 Noteworthy changes in version 1.1.0 (2005-10-01)
582 ------------------------------------------------
584 * You can now configure the backend engine file name and home
585 directory to be used, as default and per context.
587 * Information about the recipients of an encrypted text is now
588 available at decryption time.
590 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
591 and verify handlers, the information about the plaintext filename,
592 if available is made available in the new field file_name of the
593 respective result structure.
595 * The code for "automagically detecting the thread library" has been
596 removed from libgpgme. It is deprecated since version 0.4.3.
597 Since then, you had to link against libgpgme-pthread for
598 applications using pthread and libgpgme-pth for applications using
601 The code was removed because it caused compilation problems on
602 systems where the pthread.h header from GNU Pth is available in
603 addition to the system header (FreeBSD 6 and later for example).
605 * "./autogen.sh --build-w32" does now build gpgme.dll.
607 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
608 delimiter. The standard install directory is used when locating
609 gpg or gpgsm before finally falling back to the hardwired name.
611 * There is a new flag for keys and subkeys, is_qualified, which
612 indicates if a key can be used for qualified signatures according
613 to local government regulations.
615 * You can associate a filename with a data object using the new
616 function gpgme_data_set_file_name(). This filename will be stored
617 in the output when encrypting or signing the data and will be
618 returned when decrypting or verifying the output data.
620 * You can now set notation data at signature creation with the new
621 function gpgme_sig_notation_add().
623 * Interface changes relative to the 1.0.3 release:
624 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
625 gpgme_set_engine_info NEW
626 gpgme_ctx_get_engine_info NEW
627 gpgme_ctx_set_engine_info NEW
628 gpgme_recipient_t NEW
629 gpgme_decrypt_result_t EXTENDED: New field recipients.
630 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
631 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
632 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
633 GPGME_STATUS_PLAINTEXT NEW
634 gpgme_key_t EXTENDED: New field is_qualified.
635 gpgme_subkey_t EXTENDED: New field is_qualified.
636 gpgme_data_get_file_name NEW
637 gpgme_data_set_file_name NEW
638 gpgme_sig_notation_flags_t NEW
639 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
640 GPGME_SIG_NOTATAION_CRITICAL NEW
641 gpgme_sig_notation_clear NEW
642 gpgme_sig_notation_add NEW
643 gpgme_sig_notation_get NEW
644 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
647 Noteworthy changes in version 1.0.3 (2005-06-20)
648 ------------------------------------------------
650 * Previousy, GPGME would use a default "include certs" of 1. This
651 has been changed. Now GPGME will use the crypto backend engines
652 default unless you set the value with gpgme_set_include_certs()
653 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
654 as a value to explicitely request the new default behaviour.
656 Because the default changes, this is a slight change of the API
657 semantics. We consider it to be a bug fix.
659 * A bug which made GPGME hang has been fixed. If you have
660 experienced hanging before, please try out this version and let me
661 know if you still experience hanging problems.
663 * Interface changes relative to the 0.9.0 release:
664 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
665 gpgme_set_include_certs CHANGED DEFAULT
666 GPGME_INCLUDE_CERTS_DEFAULT NEW
667 GPGME_STATUS_SIG_SUBPACKET NEW
668 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
669 GPGME_STATUS_SC_OP_FAILURE NEW
670 GPGME_STATUS_SC_OP_SUCCESS NEW
671 GPGME_STATUS_CARDCTRL NEW
672 GPGME_STATUS_BACKUP_KEY_CREATED NEW
673 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
676 Noteworthy changes in version 1.0.2 (2004-12-28)
677 ------------------------------------------------
679 * Changed the license of the library to the GNU Lesser General Public
680 License (LGPL), version 2.1 or later.
683 Noteworthy changes in version 1.0.1 (2004-10-22)
684 ------------------------------------------------
689 Noteworthy changes in version 1.0.0 (2004-09-30)
690 ------------------------------------------------
692 * Version 1.0.0! We are proud to present you with a thoroughly
693 tested and stable version of the GPGME library. A big Thank You!
694 to all the people who made this possible.
696 The development will be branched into a stable 1.x.y series and the
699 * The gpgme.m4 macro supports checking the API version. Just prepend
700 it to the required version string, separated by a colon. For
701 example, this release has the version "1:1.0.0". The last release
702 to which this version is (mostly) ABI compatible is "1:0.4.2",
703 which is the default required version.
706 Noteworthy changes in version 0.9.0 (2004-06-08)
707 ------------------------------------------------
709 * The type gpgme_key_t has now a new field keylist_mode that contains
710 the keylist mode that was active at the time the key was retrieved.
712 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
713 that contains a flag indicating that the key should not have been
716 * Verifying a signature of a revoked key gives the correct result now
717 (GPG_ERR_CERT_REVOKED error code).
719 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
720 verify operations still allows you to look at the signature
723 * Clarified that patterns in keylisting operations have an upper
724 limit, and thus are not suited to list many keys at once by their
725 fingerprint. Also improve the error message if the pattern is too
726 long for the CMS protocol to handle.
728 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
729 gpgme_key_t EXTENDED: New field keylist_mode.
730 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
731 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
734 Noteworthy changes in version 0.4.7 (2004-04-29)
735 ------------------------------------------------
737 * Correctly initialize the fields expired, revoked, invalid, and
738 disabled in the gpgme_key_t structures.
740 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
741 accidently of type int instead unsigned int.
743 * Interface changes relative to the 0.4.5 release:
744 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
745 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
746 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
748 Noteworthy changes in version 0.4.6 (2004-04-06)
749 ------------------------------------------------
754 Noteworthy changes in version 0.4.5 (2004-03-07)
755 ------------------------------------------------
757 * GPGME is now compiled with LFS (large file support) by default.
758 This means that _all_ programs using GPGME must be compiled with
759 LFS support enabled by default. You can do this easily with
760 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
761 without autoconf by defining the preprocessor symbol
762 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
763 the C compiler command line, or by defining this preprocessor
764 symbol before including any system header files). For more
765 details, read the section on LFS in the manual.
767 Up to now, it was undocumented that GPGME was not using LFS.
768 But the public interfaces use off_t, and file descriptors are
769 exchanged between the application and GPGME. This was an oversight,
770 and bound to cause troubles in the future.
772 Writing GPGME as a dual mode library that seamlessly supports LFS
773 while keeping backwards compatibility is possible, but does not
774 solve the problem: Many applications already expect GPGME to have
775 LFS (they are compiled with off_t being a 64bit value). This is true
776 in particular for the popular Gtk+ and Qt programs.
778 So, although this is an ABI (but not an API) break, we will not
779 change the library version to reflect that. Because the interfaces
780 affected are probably not used yet in any GPGME 0.4 based
781 application, we don't expect any real failures from this change.
782 In fact, applications already using LFS will have some subtle bugs
785 However, if you encounter an application using GPGME 0.4.x that
786 does _not_ use LFS by default (off_t is a 32bit value), _and_
787 uses at least one of the functions gpgme_data_seek,
788 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
789 gpgme_data_new_from_cbs, then indeed this library will be ABI
790 incompatible with the program. As said above, we don't believe
791 such a program exists. If we are in error, then you have two
792 options: As a quick hack, you can configure GPGME with the
793 --disable-largefile option. This will revert the change, and GPGME
794 will not use LFS. However, GPGME will be incompatible with
795 programs that expect GPGME to use LFS. All applications are
796 required to use LFS when using GPGME, so this is only good as a
797 temporary local work-around.
799 The other option is to change the versioning of the library and
800 recompile all applications. We have reserved a special version of
801 the library for that, so you can do that without expecting a
802 version clash in the future. Furthermore, everyone who does this
803 will agree on the version to use (this is important for
804 distribution makers). Read the comment in configure.ac (before
805 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
806 blindly: As stated above, we think it is unlikely this measure is
807 needed. Still, it is there if necessary. If in doubt, contact us
808 and we will give our advise for your specific situation.
810 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
813 * New interface gpgme_cancel() that can be used to cancel
814 asynchronous operations.
816 * Interface changes relative to the 0.4.4 release:
817 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
818 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
819 gpgme_data_seek CHANGED: off_t is now a largefile type.
820 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
821 GPGME_KEYLIST_MODE_VALIDATE NEW
823 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
825 Noteworthy changes in version 0.4.4 (2004-01-12)
826 ------------------------------------------------
828 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
829 been renamed to "sig_class", to avoid clash with C++ compilers. In
830 the C API, the old name "class" has been preserved for backwards
831 compatibility, but is deprecated.
833 * Interface changes relative to the 0.4.3 release:
834 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
835 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
836 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
837 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
839 Noteworthy changes in version 0.4.3 (2003-10-06)
840 ------------------------------------------------
842 * libgpgme should not be used for threaded programs anymore. This
843 never worked reliably in all cases, because you had to
844 be careful about the linking order and libtool wouldn't do that for
845 you automatically. Instead, now you have to link against
846 libgpgme-pthread for applications using pthread and libgpgme-pth for
847 applications using GNU Pth.
849 The old code for automagically detecting the thread library is
850 still part of libgpgme, but it is DEPRECATED.
852 * There are new automake macros AM_PATH_GPGME_PTH and
853 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
854 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
855 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
856 variables of course also include the configuration for the thread
857 package itself. Alternatively, use libtool.
859 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
862 * gpgme-config doesn't support setting the prefix or exec prefix
863 anymore. I don't think it ever worked correctly, and it seems to
866 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
867 provided was not unique, instead returning the first matching key.
869 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
870 that indicates if the key can be used for authentication.
872 * gpgme_signature_t's status field is now correctly set to an error
873 with error code GPG_ERR_NO_PUBKEY if public key is not found.
875 * gpgme_new_signature_t's class field is now an unsigned int, rather
876 than an unsigned long (the old class field is preserved for
877 backwards compatibility).
879 * A new function gpgme_set_locale() is provided to allow configuring
880 the locale for the crypto backend. This is necessary for text
881 terminals so that programs like the pinentry can be started with
882 the right locale settings for the terminal the application is running
883 on, in case the terminal has different settings than the system
884 default (for example, if it is a remote terminal). You are highly
885 recommended to call the following functions directly after
890 setlocale (LC_ALL, "");
891 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
892 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
894 GPGME can not do this for you, as setlocale is not thread safe, and
895 there is no alternative.
897 * The signal action for SIGPIPE is now set to SIG_IGN by
898 gpgme_check_version, instead the first time a crypto engine is
899 started (which is not well defined).
901 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
902 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
903 to CRC24RFC2440. For now, these strings can be used as the MIC
904 parameter for PGP/MIME (if appropriately modified).
906 * Interface changes relative to the 0.4.2 release:
907 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
909 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
910 gpgme_key_t EXTENDED: New field can_authenticate.
911 gpgme_subkey_t EXTENDED: New field can_authenticate.
912 gpgme_new_signature_t CHANGED: New type for class field.
914 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
915 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
917 Noteworthy changes in version 0.4.2 (2003-07-30)
918 ------------------------------------------------
920 * Allow gpg-error to be in non-standard place when linking the test suite.
922 * Configure will fail now if gpg-error can not be found.
924 * Fixed initialized memory backed data objects for writing, which
925 caused the test program to crash (but only on Mac OS, surprisingly).
927 * Eliminate use of C99 constructs.
929 * Small improvements to the manual.
932 Noteworthy changes in version 0.4.1 (2003-06-06)
933 ------------------------------------------------
935 This is the release that 0.4.0 should have been. There are many
936 interface changes, please see below for the details. The changes are
937 sometimes the result of new functionality, but more often express a
938 paradigm shift. Others are an overdue cleanup to get GPGME in line
939 with the GNU coding standards and to make the interface more
940 self-consistent. Here is an overview on the changes:
942 All types have been renamed to conform to the GNU coding standards,
943 most of the time by keeping the whole name in lowercase and inserting
944 underscores between words.
946 All operations consistently only accept input parameters in their
947 invocation function, and return only an error code directly. Further
948 information about the result of the operation has to be retrieved
949 afterwards by calling one of the result functions. This unifies the
950 synchronous and the asynchronous interface.
952 The error values have been completely replaced by a more
953 sophisticated model that allows GPGME to transparently and accurately
954 report all errors from the other GnuPG components, irregardless of
955 process boundaries. This is achieved by using the library
956 libgpg-errors, which is shared by all GnuPG components. This library
957 is now required for GPGME.
959 The results of all operations are now provided by pointers to C
960 structs rather than by XML structs or in other ways.
962 Objects which used to be opaque (for example a key) are now pointers
963 to accessible structs, so no accessor functions are necessary.
965 Backward compatibility is provided where it was possible without too
966 much effort and did not collide with the overall sanitization effort.
967 However, this is only for ease of transition. NO DEPRECATED FUNCTION
968 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
969 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
970 Recommendations how to replace deprecated or removed functionality
971 can be found within the description of each change.
973 What follows are all changes to the interface and behaviour of GPGME
976 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
977 deprecated attributes will warn about use of obsolete functions and
978 type definitions. You can suppress these warnings by passing
979 -Wno-deprecated-declarations to the gcc command.
981 * The following types have been renamed. The old types are still
982 available as aliases, but they are deprecated now:
985 GpgmeData gpgme_data_t
986 GpgmeError gpgme_error_t
987 GpgmeDataEncoding gpgme_data_encoding_t
988 GpgmeSigStat gpgme_sig_stat_t
989 GpgmeSigMode gpgme_sig_mode_t
990 GpgmeAttr gpgme_attr_t
991 GpgmeValidity gpgme_validity_t
992 GpgmeProtocol gpgme_protocol_t
994 GpgmePassphraseCb gpgme_passphrase_cb_t
995 GpgmeProgressCb gpgme_progress_cb_t
996 GpgmeIOCb gpgme_io_cb_t
997 GpgmeRegisterIOCb gpgme_register_io_cb_t
998 GpgmeRemoveIOCb gpgme_remove_io_cb_t
999 GpgmeEventIO gpgme_event_io_t
1000 GpgmeEventIOCb gpgme_event_io_cb_t
1001 GpgmeIOCbs gpgme_io_cbs
1002 GpgmeDataReadCb gpgme_data_read_cb_t
1003 GpgmeDataWriteCb gpgme_data_write_cb_t
1004 GpgmeDataSeekCb gpgme_data_seek_cb_t
1005 GpgmeDataReleaseCb gpgme_data_release_cb_t
1006 GpgmeDataCbs gpgme_data_cbs_t
1007 GpgmeTrustItem gpgme_trust_item_t
1008 GpgmeStatusCode gpgme_status_code_t
1010 * gpgme_error_t is now identical to gpg_error_t, the error type
1011 provided by libgpg-error. More about using libgpg-error with GPGME
1012 can be found in the manual. All error symbols have been removed!
1014 * All functions and types in libgpg-error have been wrapped in GPGME.
1015 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
1016 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
1017 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
1018 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
1021 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
1023 * GnuPG 1.2.2 is required. The progress callback is now also invoked
1024 for encrypt, sign, encrypt-sign, decrypt, verify, and
1025 decrypt-verify operations. For verify operations on detached
1026 signatures, the progress callback is invoked for both the detached
1027 signature and the plaintext message, though.
1029 * gpgme_passphrase_cb_t has been changed to not provide a complete
1030 description, but the UID hint, passphrase info and a flag
1031 indicating if this is a repeated attempt individually, so the user
1032 can compose his own description from this information.
1034 The passphrase is not returned as a C string, but must be written
1035 to a file descriptor directly. This allows for secure passphrase
1038 The return type has been changed to gpgme_error_t value. This
1039 allowed to remove the gpgme_cancel function; just return
1040 the error code GPG_ERR_CANCELED in the passphrase callback directly.
1042 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
1043 The user is expected to write the response to the file descriptor,
1044 followed by a newline.
1046 * The recipients interface has been removed. Instead, you use
1047 NULL-terminated lists of keys for specifying the recipients of an
1048 encryption operation. Use the new encryption flag
1049 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
1050 the keys (but note that in general this is not a good idea).
1052 This change has been made to the prototypes of gpgme_op_encrypt,
1053 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
1054 gpgme_op_encrypt_sign_start.
1056 The export interface has been changed to use pattern strings like
1057 the keylist interface. Thus, new functions gpgme_op_export_ext and
1058 gpgme_op_export_ext_start have been added as well. Now the
1059 prototypes of gpgme_op_export_start and gpgme_op_export finally
1062 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
1063 summary anymore. Use gpgme_get_sig_status to retrieve the individual
1066 * gpgme_io_cb_t changed from a void function to a function returning
1067 a gpgme_error_t value. However, it will always return 0, so you
1068 can safely ignore the return value.
1070 * A new I/O callback event GPGME_EVENT_START has been added. The new
1071 requirement is that you must wait until this event until you are
1072 allowed to call the I/O callback handlers previously registered for
1073 this context operation. Calling I/O callback functions for this
1074 context operation before the start event happened is unsafe because
1075 it can lead to race conditions in a multi-threaded environment.
1077 * The idle function feature has been removed. It was not precisely
1078 defined in a multi-threaded environment and is obsoleted by the
1079 user I/O callback functions. If you still need a simple way to
1080 call something while waiting on one or multiple asynchronous
1081 operations to complete, don't set the HANG flag in gpgme_wait (note
1082 that this will return to your program more often than the idle
1085 * gpgme_wait can return NULL even if hang is true, if an error
1086 occurs. In that case *status contains the error code.
1088 * gpgme_get_engine_info was radically changed. Instead an XML
1089 string, an info structure of the new type gpgme_engine_info_t is
1090 returned. This makes it easier and more robust to evaluate the
1091 information in an application.
1093 * The new function gpgme_get_protocol_name can be used to convert a
1094 gpgme_protocol_t value into a string.
1096 * The status of a context operation is not checked anymore. Starting
1097 a new operation will silently cancel the previous one. Calling a
1098 function that requires you to have started an operation before without
1099 doing so is undefined.
1101 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
1102 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
1103 pointer to a structure which contains the fingerprint. This also
1104 works with gpgme_op_genkey_start. The structure also provides
1105 other information about the generated keys.
1110 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
1112 printf ("%s\n", fpr);
1116 gpgme_genkey_result_t result;
1117 err = gpgme_op_genkey (ctx, NULL, NULL);
1120 result = gpgme_op_genkey_result (ctx);
1122 printf ("%s\n", result->fpr);
1125 * The new gpgme_op_import_result function provides detailed
1126 information about the result of an import operation in
1127 gpgme_import_result_t and gpgme_import_status_t objects.
1128 Thus, the gpgme_op_import_ext variant is deprecated.
1130 * The new gpgme_op_sign_result function provides detailed information
1131 about the result of a signing operation in gpgme_sign_result_t,
1132 gpgme_invalid_key_t and gpgme_new_signature_t objects.
1134 * The new gpgme_op_encrypt_result function provides detailed
1135 information about the result of an encryption operation in
1136 a GpgmeEncryptResult object.
1138 * The new gpgme_op_decrypt_result function provides detailed
1139 information about the result of a decryption operation in
1140 a GpgmeDecryptResult object.
1142 * The new gpgme_op_verify_result function provides detailed
1143 information about the result of an verify operation in
1144 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
1145 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
1146 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
1147 and gpgme_get_notation is removed.
1149 * GpgmeTrustItem objects have now directly accessible data, so the
1150 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
1151 accessor functions are deprecated. Also, reference counting is
1152 available through gpgme_trust_item_ref and gpgme_trust_item_unref
1153 (the gpgme_trust_item_release alias for the latter is deprecated).
1155 * Keys are not cached internally anymore, so the force_update argument
1156 to gpgme_get_key has been removed.
1158 * GpgmeKey objects have now directly accessible data so the
1159 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
1160 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1161 functions are deprecated. Also, gpgme_key_release is now
1162 deprecated. The gpgme_key_get_as_xml function has been dropped.
1164 * Because all interfaces using attributes are deprecated, the
1165 GpgmeAttr data type is also deprecated.
1167 * The new gpgme_op_keylist_result function provides detailed
1168 information about the result of a key listing operation in
1169 a GpgmeKeyListResult object.
1171 * Now that each function comes with its own result retrieval
1172 interface, the generic gpgme_get_op_info interface is not useful
1173 anymore and dropped.
1175 * The type and mode of data objects is not available anymore.
1177 * Interface changes relative to the 0.4.0 release:
1178 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1179 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
1180 GpgmeData DEPRECATED: Use gpgme_data_t.
1181 GpgmeError DEPRECATED: Use gpgme_error_t.
1182 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
1183 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
1184 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
1185 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
1186 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
1187 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
1188 GpgmeKey DEPRECATED: Use gpgme_key_t.
1189 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1190 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1191 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1192 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1193 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1194 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1195 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1196 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1197 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1198 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1199 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1200 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1201 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1202 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1203 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1206 gpgme_recipients_t NEW
1208 gpgme_data_encoding_t NEW
1209 gpgme_sig_stat_t NEW
1210 gpgme_sig_mode_t NEW
1212 gpgme_validity_t NEW
1213 gpgme_protocol_t NEW
1215 gpgme_passphrase_cb_t NEW
1216 gpgme_progress_cb_t NEW
1218 gpgme_register_io_cb_t NEW
1219 gpgme_remove_io_cb_t NEW
1220 gpgme_event_io_t NEW
1221 gpgme_event_io_cb_t NEW
1223 gpgme_data_read_cb_t NEW
1224 gpgme_data_write_cb_t NEW
1225 gpgme_data_seek_cb_t NEW
1226 gpgme_data_release_cb_t NEW
1227 gpgme_data_cbs_t NEW
1228 gpgme_trust_item_t NEW
1229 gpgme_status_code_t NEW
1230 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1231 gpgme_err_code_t NEW
1232 gpgme_err_source_t NEW
1234 gpgme_err_source NEW
1237 gpgme_error_from_errno NEW
1238 gpgme_err_make_from_errno NEW
1239 gpgme_err_code_from_errno NEW
1240 gpgme_err_code_to_errno NEW
1242 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1243 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1244 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1245 gpgme_edit_cb_t CHANGED: Write directly to FD.
1246 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1247 gpgme_op_verify CHANGED: Drop R_STAT argument.
1248 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1249 gpgme_wait CHANGED: Can return NULL even if hang is true.
1250 GpgmeIdleFunc REMOVED
1251 gpgme_register_idle REMOVED
1252 GpgmeRecipients REMOVED
1253 gpgme_recipients_new REMOVED
1254 gpgme_recipients_release REMOVED
1255 gpgme_recipients_add_name REMOVED
1256 gpgme_recipients_add_name_with_validity REMOVED
1257 gpgme_recipients_count REMOVED
1258 gpgme_recipients_enum_open REMOVED
1259 gpgme_recipients_enum_read REMOVED
1260 gpgme_recipients_enum_close REMOVED
1261 gpgme_encrypt_flags_t NEW
1262 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1263 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1264 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1265 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1266 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1267 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1268 gpgme_op_export CHANGED: User IDs passed as patterns.
1269 gpgme_op_export_ext_start NEW
1270 gpgme_op_export_ext NEW
1271 gpgme_keylist_mode_t NEW
1273 gpgme_engine_info_t NEW
1274 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1275 gpgme_get_protocol_name NEW
1276 gpgme_cancel REMOVED: Return error in callback directly.
1277 gpgme_op_genkey CHANGED: FPR argument dropped.
1278 gpgme_op_genkey_result NEW
1279 gpgme_genkey_result_t NEW
1280 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1281 gpgme_op_import_result NEW
1282 gpgme_import_status_t NEW
1283 gpgme_import_result_t NEW
1284 gpgme_pubkey_algo_t NEW
1285 gpgme_hash_algo_t NEW
1286 gpgme_invalid_key_t NEW
1287 gpgme_new_signature_t NEW
1288 gpgme_sign_result_t NEW
1289 gpgme_op_sign_result NEW
1290 gpgme_pubkey_algo_name NEW
1291 gpgme_hash_algo_name NEW
1292 gpgme_encrypt_result_t NEW
1293 gpgme_op_encrypt_result NEW
1294 gpgme_decrypt_result_t NEW
1295 gpgme_op_decrypt_result NEW
1296 gpgme_verify_result_t NEW
1297 gpgme_op_verify_result NEW
1298 gpgme_get_notation REMOVED: Access verify result directly instead.
1299 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1300 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1301 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1302 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1303 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1304 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1305 gpgme_trust_item_ref NEW
1306 gpgme_trust_item_unref NEW
1307 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1308 gpgme_trust_item_get_string_attr DEPRECATED
1309 gpgme_trust_item_get_ulong_attr DEPRECATED
1310 gpgme_get_key CHANGED: Removed force_update argument.
1314 gpgme_key_t CHANGED: Now has user accessible data members.
1315 gpgme_key_get_string_attr DEPRECATED
1316 gpgme_key_get_ulong_attr DEPRECATED
1317 gpgme_key_sig_get_string_attr DEPRECATED
1318 gpgme_key_sig_get_ulong_attr DEPRECATED
1319 gpgme_key_get_as_xml REMOVED
1320 gpgme_key_list_result_t NEW
1321 gpgme_op_keylist_result NEW
1322 gpgme_get_op_info REMOVED
1323 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1325 Noteworthy changes in version 0.4.0 (2002-12-23)
1326 ------------------------------------------------
1328 * Key generation returns the fingerprint of the generated key.
1330 * New convenience function gpgme_get_key.
1332 * Supports signatures of user IDs in keys via the new
1333 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1334 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1335 interfaces. The XML info about a key also includes the signatures
1338 * New data object interface, which is more flexible and transparent.
1340 * Interface changes relative to the 0.3.9 release:
1341 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1343 GpgmeDataWriteCb NEW
1345 GpgmeDataReleaseCb NEW
1347 gpgme_data_read CHANGED: Match read() closely.
1348 gpgme_data_write CHANGED: Match write() closely.
1350 gpgme_data_new_from_fd NEW
1351 gpgme_data_new_from_stream NEW
1352 gpgme_data_new_from_cbs NEW
1353 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1354 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1355 gpgme_data_get_type REMOVED: No replacement.
1356 gpgme_op_verify CHANGED: Take different data objects for
1357 signed text and plain text.
1358 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1359 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1360 gpgme_op_genkey CHANGED: New parameter FPR.
1361 GPGME_KEYLIST_MODE_SIGS NEW
1362 gpgme_key_sig_get_string_attr NEW
1363 gpgme_key_sig_get_ulong_attr NEW
1365 GPGME_ATTR_SIG_CLASS NEW
1366 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1368 Noteworthy changes in version 0.3.16 (2003-11-19)
1369 -------------------------------------------------
1371 * Compatibility fixes for GnuPG 1.9.x
1373 Noteworthy changes in version 0.3.15 (2003-02-18)
1374 -------------------------------------------------
1376 * The progress status is sent via the progress callbacks in
1379 * Bug fix for signing operations with explicit signer settings for
1382 Noteworthy changes in version 0.3.14 (2002-12-04)
1383 -------------------------------------------------
1385 * GPGME-Plug is now in its own package "cryptplug".
1387 * Workaround for a setlocale problem. Fixed a segv related to not
1388 correctly as closed marked file descriptors.
1390 Noteworthy changes in version 0.3.13 (2002-11-20)
1391 -------------------------------------------------
1393 * Release due to changes in gpgmeplug.
1395 Noteworthy changes in version 0.3.12 (2002-10-15)
1396 -------------------------------------------------
1398 * Fixed some bux with key listings.
1400 * The development has been branched to clean up some API issues.
1401 This 0.3 series will be kept for compatibility reasons; so do don't
1402 expect new features.
1404 Noteworthy changes in version 0.3.11 (2002-09-20)
1405 -------------------------------------------------
1409 Noteworthy changes in version 0.3.10 (2002-09-02)
1410 -------------------------------------------------
1412 * Setting the signing keys for the CMS protocol does now work.
1414 * The signers setting is honoured by gpgme_op_edit.
1416 Noteworthy changes in version 0.3.9 (2002-08-21)
1417 ------------------------------------------------
1419 * A spec file for creating RPMs has been added.
1421 * An experimental interface to GnuPG's --edit-key functionality is
1422 introduced, see gpgme_op_edit.
1424 * The new gpgme_import_ext function provides a convenient access to
1425 the number of processed keys.
1427 * Interface changes relative to the 0.3.8 release:
1428 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1431 gpgme_op_edit_start NEW
1433 gpgme_op_import_ext NEW
1434 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1436 Noteworthy changes in version 0.3.8 (2002-06-25)
1437 ------------------------------------------------
1439 * It is possible to use an outside event loop for the I/O to the
1440 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1442 * Interface changes relative to the 0.3.6 release:
1443 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1445 GpgmeRegisterIOCb NEW
1449 struct GpgmeIOCbs NEW
1450 gpgme_set_io_cbs NEW
1451 gpgme_get_io_cbs NEW
1452 GPGME_ATTR_ERRTOK NEW
1453 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1455 Noteworthy changes in version 0.3.7 (2002-06-04)
1456 ------------------------------------------------
1458 * GPGME_ATTR_OTRUST is implemented now.
1460 * A first step toward thread safeness has been achieved, see the
1461 documentation for details. Supported thread libraries are pthread
1464 Noteworthy changes in version 0.3.6 (2002-05-03)
1465 ------------------------------------------------
1467 * All error output of the gpgsm backend is send to the bit bucket.
1469 * The signature verification functions are extended. Instead of
1470 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1471 expired signatures. 2 new functions may be used to retrieve more
1472 detailed information like the signature expiration time and a
1473 validity information of the key without an extra key looking.
1475 * The current passphrase callback and progress meter callback can be
1476 retrieved with the new functions gpgme_get_passphrase_cb and
1477 gpgme_get_progress_cb respectively.
1479 * Interface changes relative to the 0.3.5 release:
1480 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1481 gpgme_get_passphrase_cb NEW
1482 gpgme_get_progress_cb NEW
1483 GpgmeDataEncoding NEW
1484 gpgme_data_set_encoding NEW
1485 gpgme_data_get_encoding NEW
1486 GPGME_SIG_STAT_GOOD_EXP NEW
1487 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1488 gpgme_op_verify CHANGED: Returns more status codes.
1489 GPGME_ATTR_SIG_STATUS NEW
1490 gpgme_get_sig_string_attr NEW
1491 gpgme_get_sig_ulong_attr NEW
1492 gpgme_get_protocol NEW
1493 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1495 Noteworthy changes in version 0.3.5 (2002-04-01)
1496 ------------------------------------------------
1498 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1499 case, symmetric encryption is performed. Note that this requires a
1500 passphrase from the user.
1502 * More information is returned for X.509 certificates.
1504 * Interface changes relative to the 0.3.4 release:
1505 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1506 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1507 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1509 Noteworthy changes in version 0.3.4 (2002-03-04)
1510 ------------------------------------------------
1512 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1513 some recipients have been invalid, whereas earlier versions
1514 succeeded in this case. The plaintext is still encrypted for all valid
1515 recipients, so the application might take this error as a hint that
1516 the ciphertext is not usable for all requested recipients.
1517 Information about invalid recipients is available with gpgme_get_op_info.
1519 * gpgme_op_verify now allows to pass an uninitialized data object as
1520 its plaintext argument to check for normal and cleartext
1521 signatures. The plaintext is then returned in the data object.
1523 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1524 to set and get the number of certifications to include in S/MIME
1527 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1528 to encrypt and sign a message in a combined operation.
1530 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1532 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1534 * Interface changes relative to the 0.3.3 release:
1535 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1536 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1537 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1538 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1539 gpgme_set_include_certs NEW
1540 gpgme_get_include_certs NEW
1541 gpgme_op_encrypt_sign NEW
1542 gpgme_op_encrypt_sign_start NEW
1543 gpgme_op_keylist_ext_start NEW
1544 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1546 Noteworthy changes in version 0.3.3 (2002-02-12)
1547 ------------------------------------------------
1549 * Fix the Makefile in jnlib.
1551 * Fix the test suite (hopefully). It should clean up all its state
1552 with `make check' now.
1555 Noteworthy changes in version 0.3.2 (2002-02-10)
1556 ------------------------------------------------
1558 * Remove erroneous dependency on libgcrypt in jnlib.
1561 Noteworthy changes in version 0.3.1 (2002-02-09)
1562 ------------------------------------------------
1564 * There is a Texinfo manual documenting the API.
1566 * The gpgme_set_keylist_mode function returns an error, and changed
1567 its meaning. It is no longer usable to select between normal and
1568 fast mode (newer versions of GnuPG will always be fast), but
1569 selects between local keyring, remote keyserver, or both.
1570 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1571 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1572 current setting, a fucntion gpgme_get_keylist_mode was added to
1573 retrieve the current mode.
1575 * gpgme_wait accepts a new argument STATUS to return the error status
1576 of the operation on the context. Its definition is closer to
1577 waitpid() now than before.
1579 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1580 type from off_t to the unsigned size_t.
1582 * The R_HD argument to the GpgmePassphraseCb type changed its type
1583 from void* to void**.
1585 * New interface gpgme_op_trustlist_end() to match
1586 gpgme_op_keylist_end().
1588 * The CryptPlug modules have been renamed to gpgme-openpgp and
1589 gpgme-smime, and they are installed in pkglibdir by `make install'.
1591 * An idle function can be registered with gpgme_register_idle().
1593 * The GpgSM backend supports key generation with gpgme_op_genkey().
1595 * Interface changes relative to the 0.3.0 release:
1596 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1597 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1598 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1599 gpgme_wait CHANGED: New argument STATUS.
1600 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1601 The function has a new meaning!
1602 gpgme_get_keylist_mode NEW
1603 GPGME_KEYLIST_MODE_LOCAL NEW
1604 GPGME_KEYLIST_MODE_EXTERN NEW
1605 gpgme_op_trustlist_next NEW
1607 gpgme_register_idle NEW
1608 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1610 Noteworthy changes in version 0.3.0 (2001-12-19)
1611 ------------------------------------------------
1613 * New interface gpgme_set_protocol() to set the protocol and thus the
1614 crypto engine to be used by the context. Currently, the OpenPGP
1615 and the CMS protocols are supported. They are specified by the new
1616 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1617 A new context uses the OpenPGP engine by default.
1619 * gpgme_get_engine_info() returns information for all crypto engines
1620 compiled into the library. The XML format has changed. To
1621 reliably get the version of a crypto engine, the <version> tag
1622 after the appropriate <protocol> tag has to be looked for.
1624 * New interface gpgme_engine_check_version(), obsoleting
1625 gpgme_check_engine(). Check the version of all engines you are
1626 supporting in your software.
1628 * GpgmeKey lists the user ids in the order as they are returned by
1629 GnuPG, first the primary key with index 0, then the sub-user ids.
1631 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1632 signatures simultaneously.
1634 * The new interface gpgme_op_keylist_end() terminates a pending
1635 keylist operation. A keylist operation is also terminated when
1636 gpgme_op_keylist_next() returns GPGME_EOF.
1638 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1639 cross-compiled, or even compiled without support for GnuPG
1642 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1643 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1644 in the path, but it can also be compiled without support for GpgSM
1645 (`--without-gpgsm').
1647 * CryptPlug modules for GPGME are included and can be enabled at
1648 configure time (`--enable-gpgmeplug'). There is one module which
1649 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1650 GpgSM engine (`gpgsmplug').
1652 * Interface changes relative to the latest 0.2.x release:
1653 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1654 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1655 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1656 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1657 gpgme_get_engine_info CHANGED: New format, extended content.
1658 gpgme_engine_check_version NEW
1659 gpgme_decrypt_verify_start NEW
1660 gpgme_decrypt_verify NEW
1661 gpgme_op_keylist_next NEW
1662 gpgme_set_protocol NEW
1663 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1666 Noteworthy changes in version 0.2.3 (2001-09-17)
1667 ------------------------------------------------
1669 * New function gpgme_get_op_info which can be used to get the micalg
1670 parameter needed for MOSS.
1672 * New functions gpgme_get_armor and gpgme_get_textmode.
1674 * The usual bug fixes and some minor functionality improvements.
1676 * Added a simple encryption component for MS-Windows; however the
1677 build procedure might have some problems.
1680 Noteworthy changes in version 0.2.2 (2001-06-12)
1681 ------------------------------------------------
1683 * Implemented a key cache.
1685 * Fixed a race condition under W32 and some other bug fixes.
1688 Noteworthy changes in version 0.2.1 (2001-04-02)
1689 ------------------------------------------------
1691 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1693 * Handle GnuPG's new key capabilities output and support revocation
1696 * Made the W32 support more robust.
1699 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
1702 This file is free software; as a special exception the author gives
1703 unlimited permission to copy and/or distribute it, with or without
1704 modifications, as long as this notice is preserved.
1706 This file is distributed in the hope that it will be useful, but
1707 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1708 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.