1 Noteworthy changes in version 1.5.3 (2014-12-11) [C24/A13/R2]
2 -------------------------------------------------------------
4 * The export key functions do now return an error if used with the
8 Noteworthy changes in version 1.5.2 (2014-11-21) [C24/A13/R1]
9 -------------------------------------------------------------
11 * gpgme-tool is now installed.
13 * Fix external listing for modern keyservers.
18 Noteworthy changes in version 1.5.1 (2014-07-30) [C24/A13/R0]
19 -------------------------------------------------------------
21 * Fixed possible overflow in gpgsm and uiserver engines.
24 * Added support for GnuPG 2.1's --with-secret option.
26 * Interface changes relative to the 1.5.0 release:
27 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
28 GPGME_KEYLIST_MODE_WITH_SECRET NEW.
31 Noteworthy changes in version 1.5.0 (2014-05-21) [C23/A12/R0]
32 -------------------------------------------------------------
34 * On Unices the engine file names are not not anymore hardwired but
35 located via the envvar PATH. All options to set the name of the
36 engines for the configure run are removed.
38 * If GPGME finds the gpgconf binary it defaults to using gpg2 or
39 whatever gpgconf tells as name for the OpenPGP engine. If gpgconf
40 is not found, GPGME looks for an engine named "gpg".
42 * New feature to use the gpgme I/O subsystem to run arbitrary
45 * New flag to use encryption without the default compression step.
47 * New function to access "gpg-conf --list-dirs"
49 * New configure option --enable-fixed-path for use by Android.
51 * Support ECC algorithms.
53 * Interface changes relative to the 1.4.3 release:
54 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
55 gpgme_get_dirinfo NEW.
56 gpgme_op_spawn_start NEW.
58 GPGME_PROTOCOL_SPAWN NEW.
59 GPGME_SPAWN_DETACHED NEW.
60 GPGME_SPAWN_ALLOW_SET_FG NEW.
61 GPGME_ENCRYPT_NO_COMPRESS NEW.
64 gpgme_subkey_t EXTENDED: New field curve.
65 GPGME_STATUS_PLAINTEXT_LENGTH NEW.
66 GPGME_STATUS_MOUNTPOINT NEW.
67 GPGME_STATUS_PINENTRY_LAUNCHED NEW.
68 GPGME_STATUS_ATTRIBUTE NEW.
69 GPGME_STATUS_BEGIN_SIGNING NEW.
70 GPGME_STATUS_KEY_NOT_CREATED NEW.
73 Noteworthy changes in version 1.4.3 (2013-08-12) [C22/A11/R0]
74 -------------------------------------------------------------
76 * The default engine names are now taken from the output of gpgconf.
77 If gpgconf is not found the use of gpg 1 is assumed.
79 * Under Windows the default engines names are first searched in the
80 installation directory of the gpgme DLL.
82 * New function gpgme_data_identify to detect the type of a message.
84 * Interface changes relative to the 1.4.2 release:
85 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
86 gpgme_signers_count NEW.
87 gpgme_data_type_t NEW.
88 gpgme_data_identify NEW.
91 Noteworthy changes in version 1.4.2 (2013-05-28) [C21/A10/R0]
92 -------------------------------------------------------------
94 * Allow symmetric encryption with gpgme_op_encrypt_sign.
96 * Fixed mismatching off_t definitions on Windows.
98 * Interface changes relative to the 1.4.1 release:
99 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
102 GPGME_PROTOCOL_OPENPGP NEW alias.
105 Noteworthy changes in version 1.4.1 (2013-05-01) [C20/A9/R1]
106 ------------------------------------------------------------
108 * Fixed reading of gpg.conf files with excessive use of the group
111 * Fixed building with the i686-w64-mingw32 toolchain.
113 * Disabled FD passing by default for Apple.
116 Noteworthy changes in version 1.4.0 (2013-02-26) [C20/A9/R0]
117 ------------------------------------------------------------
119 * New function gpgme_set_global_flag to help debugging on Android.
121 * New function gpgme_io_writen as a convenience wrapper around
124 * New functions to support the pinentry mode feature of GnuPG 2.1.
126 * New macro GPGME_VERSION_NUMBER to allow supporting different API
127 versions without the need for a configure test.
129 * Several improvements for gpgme-tool.
131 * Better logging of the common "invalid engine" error code.
133 * Support for FD passing is now enabled by default. The configure
134 option --disable-fd-passing may be used to disable this.
136 * Interface changes relative to the 1.3.1 release:
137 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
138 GPGME_VERSION_NUMBER NEW.
140 gpgme_set_global_flag NEW.
141 gpgme_set_pinentry_mode NEW.
142 gpgme_get_pinentry_mode NEW.
143 gpgme_pinentry_mode_t NEW.
144 GPGME_PINENTRY_MODE_DEFAULT NEW.
145 GPGME_PINENTRY_MODE_ASK NEW.
146 GPGME_PINENTRY_MODE_CANCEL NEW.
147 GPGME_PINENTRY_MODE_ERROR NEW.
148 GPGME_PINENTRY_MODE_LOOPBACK NEW.
151 Noteworthy changes in version 1.3.2 (2012-05-02)
152 ------------------------------------------------
154 * Remove support for libgpgme-pth. As far as we know, this was never used,
155 and GnuPG is going to use our own npth in the future.
157 * Fix signature summary information for a missing X.509 key.
159 * Fix parsing of dates >= year 2038.
162 Noteworthy changes in version 1.3.1 (2011-06-16)
163 ------------------------------------------------
165 * Ported to Windows CE.
167 * Detect GPG versions not supporting ---passwd.
169 * Interface changes relative to the 1.3.0 release:
170 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
171 GPGME_EXPORT_MODE_MINIMAL NEW
172 GPGME_STATUS_SUCCESS NEW
173 gpgme_err_code_from_syserror NEW
174 gpgme_err_set_errno NEW
175 gpgme_error_from_errno CHANGED: Return gpgme_error_t (compatible type).
176 gpgme_error_from_syserror NEW
177 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
180 Noteworthy changes in version 1.3.0 (2010-01-11)
181 ------------------------------------------------
183 * GPGME does not come with an internal libassuan version anymore.
184 The external libassuan 1.1.0 release or later is required. For
185 application programmers on systems that can resolve inter-library
186 dependencies at runtime, this is a transparent change.
188 * New engine GPGME_PROTOCOL_G13 to support the new g13 tool.
190 * New engine GPGME_PROTOCOL_UISERVER to support UI Servers.
192 * New API to change the passphrase of a key.
194 * Interface changes relative to the 1.2.0 release:
195 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
196 GPGME_STATUS_INV_SGNR NEW.
197 GPGME_STATUS_NO_SGNR NEW.
198 GPGME_PROTOCOL_G13 NEW.
199 gpgme_op_g13_mount NEW.
200 gpgme_g13_result_t NEW.
203 gpgme_op_passwd_start NEW.
205 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
208 Noteworthy changes in version 1.2.0 (2009-06-18)
209 ------------------------------------------------
211 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
214 * gpgme_new will fail if gpgme_check_version was not called, or a
215 selftest failed (for example, if -mms-bitfields was not used on
218 * New functions gpgme_io_read and gpgme_io_write for use with
219 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
221 * New functions gpgme_result_ref and gpgme_result_unref to detach
222 result structures from a context.
224 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
225 that allow to specify exported keys through gpgme_key_t objects
228 * New mode of operation gpgme_export_mode_t that allows exporting
231 * Interface changes relative to the 1.1.7 release:
232 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
233 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
234 GPGME_PROTOCOL_ASSUAN NEW.
235 gpgme_assuan_data_cb_t NEW.
236 gpgme_assuan_inquire_cb_t NEW.
237 gpgme_assuan_status_cb_t NEW.
238 gpgme_op_assuan_transact_start NEW.
239 gpgme_op_assuan_transact NEW.
240 gpgme_op_assuan_result NEW.
241 gpgme_op_import_keys NEW.
242 gpgme_op_import_keys_start NEW.
243 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
244 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
245 gpgme_check_version CHANGED: Is now a macro.
246 gpgme_new EXTENDED: More failure codes.
249 gpgme_result_ref NEW.
250 gpgme_result_unref NEW.
251 gpgme_export_mode_t NEW.
252 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
253 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
254 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
255 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
256 gpgme_op_export_keys_start NEW.
257 gpgme_op_export_keys NEW.
258 GPGME_DATA_ENCODING_URL NEW.
259 GPGME_DATA_ENCODING_URL0 NEW.
260 GPGME_DATA_ENCODING_URLESC NEW.
261 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
264 Noteworthy changes in version 1.1.8 (2008-12-08)
265 ------------------------------------------------
267 * SIGPIPE is now again ignored as described in the manual. Fixes
268 regresion introduced with 1.1.6.
271 Noteworthy changes in version 1.1.7 (2008-10-17)
272 ------------------------------------------------
274 * Using GPGME_KEYLIST_MODE_LOCAL combined with
275 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
276 --locate-keys feature of gpg (>= 2.0.10).
278 * The encoding of gpgme_data_t objects can affect the output encoding
279 of export, sign and encrypt operations now (the same operations
280 that are also affected by the ASCII mode switch). We believe this
281 change in the ABI is innocent enough not to break existing
282 applications (it only affects the S/MIME backend on certain
285 * The reference manual now includes the specification of "The GnuPG
288 * A new function gpgme_cancel_async can be used to asynchronously
289 cancel any pending operation at any time, from any thread.
291 * Interface changes relative to the 1.1.6 release:
292 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
293 gpgme_op_encrypt CHANGED: Output encoding can affect result.
294 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
295 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
296 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
297 gpgme_op_sign CHANGED: Output encoding can affect result.
298 gpgme_op_sign_start CHANGED: Output encoding can affect result.
299 gpgme_op_export CHANGED: Output encoding can affect result.
300 gpgme_op_export_start CHANGED: Output encoding can affect result.
301 gpgme_op_export_ext CHANGED: Output encoding can affect result.
302 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
303 gpgme_cancel_async NEW
304 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
307 Noteworthy changes in version 1.1.6 (2008-01-04)
308 ------------------------------------------------
310 * Bug fixes for for W32.
312 * A new, experimental (and thus undocumented and potentially
313 unstable) interface for accessing gpg-conf through GPGME has been
316 * Interface changes relative to the 1.1.1 release:
317 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
318 gpgme_signature_t EXTENDED: New field chain_model.
319 gpgme_op_getauditlog_start NEW.
320 gpgme_op_getauditlog NEW.
321 GPGME_AUDITLOG_HTML NEW.
322 GPGME_AUDITLOG_WITH_HELP NEW.
323 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
326 Noteworthy changes in version 1.1.5 (2007-07-09)
327 ------------------------------------------------
329 * Bug and portability fixes (mainly for W32).
332 Noteworthy changes in version 1.1.4 (2007-03-05)
333 ------------------------------------------------
335 * Detect and bail out on double plaintext messages. This is required
336 so that applications can properly detect the signed parts of a
337 message. Actual there is now a double protection as GnuPG 1.4.7
338 will detect this case too.
341 Noteworthy changes in version 1.1.3 (2007-01-29)
342 ------------------------------------------------
344 * Fixed a memory leak in gpgme_data_release_and_get_mem.
346 * Fixed a bug in Windows command line quoting.
349 Noteworthy changes in version 1.1.2 (2006-03-02)
350 ------------------------------------------------
352 * Fixed a bug in the W32 glib backend.
355 Noteworthy changes in version 1.1.1 (2006-02-23)
356 ------------------------------------------------
358 * Fixed a bug in that the fingerprints of subkeys are not available.
360 * Clarified usage of the SECRET flag in key listings. It is now
363 * Reading signature notations and policy URLs on key signatures is
364 supported. They can be found in the new field notations of the
365 gpgme_key_sig_t structure. This has to be enabled with the keylist
366 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
368 * A new gpgme_free() function solves the problem of using different
369 allocators in a single program. This function should now be used
370 instead calling free() to release the buffer returned by
371 gpgme_data_release_and_get_mem. It is recommended that you always
372 do this, but it is only necessary on certain platforms, so backwards
373 compatibility is provided. In other words: If free() worked for
374 you before, it will keep working.
376 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
377 They are analyzed by the verify handlers and made available in the
378 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
380 * Interface changes relative to the 1.1.0 release:
381 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
382 gpgme_key_sig_t EXTENDED: New field notations.
383 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
385 GPGME_STATUS_PKA_TRUST_BAD NEW
386 GPGME_STATUS_PKA_TRUST_GOOD NEW
387 gpgme_signature_t EXTENDED: New field pka_trust.
388 gpgme_signature_t EXTENDED: New field pka_address.
389 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
392 Noteworthy changes in version 1.1.0 (2005-10-01)
393 ------------------------------------------------
395 * You can now configure the backend engine file name and home
396 directory to be used, as default and per context.
398 * Information about the recipients of an encrypted text is now
399 available at decryption time.
401 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
402 and verify handlers, the information about the plaintext filename,
403 if available is made available in the new field file_name of the
404 respective result structure.
406 * The code for "automagically detecting the thread library" has been
407 removed from libgpgme. It is deprecated since version 0.4.3.
408 Since then, you had to link against libgpgme-pthread for
409 applications using pthread and libgpgme-pth for applications using
412 The code was removed because it caused compilation problems on
413 systems where the pthread.h header from GNU Pth is available in
414 addition to the system header (FreeBSD 6 and later for example).
416 * "./autogen.sh --build-w32" does now build gpgme.dll.
418 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
419 delimiter. The standard install directory is used when locating
420 gpg or gpgsm before finally falling back to the hardwired name.
422 * There is a new flag for keys and subkeys, is_qualified, which
423 indicates if a key can be used for qualified signatures according
424 to local government regulations.
426 * You can associate a filename with a data object using the new
427 function gpgme_data_set_file_name(). This filename will be stored
428 in the output when encrypting or signing the data and will be
429 returned when decrypting or verifying the output data.
431 * You can now set notation data at signature creation with the new
432 function gpgme_sig_notation_add().
434 * Interface changes relative to the 1.0.3 release:
435 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
436 gpgme_set_engine_info NEW
437 gpgme_ctx_get_engine_info NEW
438 gpgme_ctx_set_engine_info NEW
439 gpgme_recipient_t NEW
440 gpgme_decrypt_result_t EXTENDED: New field recipients.
441 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
442 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
443 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
444 GPGME_STATUS_PLAINTEXT NEW
445 gpgme_key_t EXTENDED: New field is_qualified.
446 gpgme_subkey_t EXTENDED: New field is_qualified.
447 gpgme_data_get_file_name NEW
448 gpgme_data_set_file_name NEW
449 gpgme_sig_notation_flags_t NEW
450 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
451 GPGME_SIG_NOTATAION_CRITICAL NEW
452 gpgme_sig_notation_clear NEW
453 gpgme_sig_notation_add NEW
454 gpgme_sig_notation_get NEW
455 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
458 Noteworthy changes in version 1.0.3 (2005-06-20)
459 ------------------------------------------------
461 * Previousy, GPGME would use a default "include certs" of 1. This
462 has been changed. Now GPGME will use the crypto backend engines
463 default unless you set the value with gpgme_set_include_certs()
464 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
465 as a value to explicitely request the new default behaviour.
467 Because the default changes, this is a slight change of the API
468 semantics. We consider it to be a bug fix.
470 * A bug which made GPGME hang has been fixed. If you have
471 experienced hanging before, please try out this version and let me
472 know if you still experience hanging problems.
474 * Interface changes relative to the 0.9.0 release:
475 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
476 gpgme_set_include_certs CHANGED DEFAULT
477 GPGME_INCLUDE_CERTS_DEFAULT NEW
478 GPGME_STATUS_SIG_SUBPACKET NEW
479 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
480 GPGME_STATUS_SC_OP_FAILURE NEW
481 GPGME_STATUS_SC_OP_SUCCESS NEW
482 GPGME_STATUS_CARDCTRL NEW
483 GPGME_STATUS_BACKUP_KEY_CREATED NEW
484 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
487 Noteworthy changes in version 1.0.2 (2004-12-28)
488 ------------------------------------------------
490 * Changed the license of the library to the GNU Lesser General Public
491 License (LGPL), version 2.1 or later.
494 Noteworthy changes in version 1.0.1 (2004-10-22)
495 ------------------------------------------------
500 Noteworthy changes in version 1.0.0 (2004-09-30)
501 ------------------------------------------------
503 * Version 1.0.0! We are proud to present you with a thoroughly
504 tested and stable version of the GPGME library. A big Thank You!
505 to all the people who made this possible.
507 The development will be branched into a stable 1.x.y series and the
510 * The gpgme.m4 macro supports checking the API version. Just prepend
511 it to the required version string, separated by a colon. For
512 example, this release has the version "1:1.0.0". The last release
513 to which this version is (mostly) ABI compatible is "1:0.4.2",
514 which is the default required version.
517 Noteworthy changes in version 0.9.0 (2004-06-08)
518 ------------------------------------------------
520 * The type gpgme_key_t has now a new field keylist_mode that contains
521 the keylist mode that was active at the time the key was retrieved.
523 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
524 that contains a flag indicating that the key should not have been
527 * Verifying a signature of a revoked key gives the correct result now
528 (GPG_ERR_CERT_REVOKED error code).
530 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
531 verify operations still allows you to look at the signature
534 * Clarified that patterns in keylisting operations have an upper
535 limit, and thus are not suited to list many keys at once by their
536 fingerprint. Also improve the error message if the pattern is too
537 long for the CMS protocol to handle.
539 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
540 gpgme_key_t EXTENDED: New field keylist_mode.
541 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
542 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
545 Noteworthy changes in version 0.4.7 (2004-04-29)
546 ------------------------------------------------
548 * Correctly initialize the fields expired, revoked, invalid, and
549 disabled in the gpgme_key_t structures.
551 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
552 accidently of type int instead unsigned int.
554 * Interface changes relative to the 0.4.5 release:
555 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
556 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
557 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
559 Noteworthy changes in version 0.4.6 (2004-04-06)
560 ------------------------------------------------
565 Noteworthy changes in version 0.4.5 (2004-03-07)
566 ------------------------------------------------
568 * GPGME is now compiled with LFS (large file support) by default.
569 This means that _all_ programs using GPGME must be compiled with
570 LFS support enabled by default. You can do this easily with
571 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
572 without autoconf by defining the preprocessor symbol
573 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
574 the C compiler command line, or by defining this preprocessor
575 symbol before including any system header files). For more
576 details, read the section on LFS in the manual.
578 Up to now, it was undocumented that GPGME was not using LFS.
579 But the public interfaces use off_t, and file descriptors are
580 exchanged between the application and GPGME. This was an oversight,
581 and bound to cause troubles in the future.
583 Writing GPGME as a dual mode library that seamlessly supports LFS
584 while keeping backwards compatibility is possible, but does not
585 solve the problem: Many applications already expect GPGME to have
586 LFS (they are compiled with off_t being a 64bit value). This is true
587 in particular for the popular Gtk+ and Qt programs.
589 So, although this is an ABI (but not an API) break, we will not
590 change the library version to reflect that. Because the interfaces
591 affected are probably not used yet in any GPGME 0.4 based
592 application, we don't expect any real failures from this change.
593 In fact, applications already using LFS will have some subtle bugs
596 However, if you encounter an application using GPGME 0.4.x that
597 does _not_ use LFS by default (off_t is a 32bit value), _and_
598 uses at least one of the functions gpgme_data_seek,
599 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
600 gpgme_data_new_from_cbs, then indeed this library will be ABI
601 incompatible with the program. As said above, we don't believe
602 such a program exists. If we are in error, then you have two
603 options: As a quick hack, you can configure GPGME with the
604 --disable-largefile option. This will revert the change, and GPGME
605 will not use LFS. However, GPGME will be incompatible with
606 programs that expect GPGME to use LFS. All applications are
607 required to use LFS when using GPGME, so this is only good as a
608 temporary local work-around.
610 The other option is to change the versioning of the library and
611 recompile all applications. We have reserved a special version of
612 the library for that, so you can do that without expecting a
613 version clash in the future. Furthermore, everyone who does this
614 will agree on the version to use (this is important for
615 distribution makers). Read the comment in configure.ac (before
616 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
617 blindly: As stated above, we think it is unlikely this measure is
618 needed. Still, it is there if necessary. If in doubt, contact us
619 and we will give our advise for your specific situation.
621 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
624 * New interface gpgme_cancel() that can be used to cancel
625 asynchronous operations.
627 * Interface changes relative to the 0.4.4 release:
628 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
629 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
630 gpgme_data_seek CHANGED: off_t is now a largefile type.
631 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
632 GPGME_KEYLIST_MODE_VALIDATE NEW
634 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
636 Noteworthy changes in version 0.4.4 (2004-01-12)
637 ------------------------------------------------
639 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
640 been renamed to "sig_class", to avoid clash with C++ compilers. In
641 the C API, the old name "class" has been preserved for backwards
642 compatibility, but is deprecated.
644 * Interface changes relative to the 0.4.3 release:
645 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
646 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
647 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
648 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
650 Noteworthy changes in version 0.4.3 (2003-10-06)
651 ------------------------------------------------
653 * libgpgme should not be used for threaded programs anymore. This
654 never worked reliably in all cases, because you had to
655 be careful about the linking order and libtool wouldn't do that for
656 you automatically. Instead, now you have to link against
657 libgpgme-pthread for applications using pthread and libgpgme-pth for
658 applications using GNU Pth.
660 The old code for automagically detecting the thread library is
661 still part of libgpgme, but it is DEPRECATED.
663 * There are new automake macros AM_PATH_GPGME_PTH and
664 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
665 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
666 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
667 variables of course also include the configuration for the thread
668 package itself. Alternatively, use libtool.
670 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
673 * gpgme-config doesn't support setting the prefix or exec prefix
674 anymore. I don't think it ever worked correctly, and it seems to
677 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
678 provided was not unique, instead returning the first matching key.
680 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
681 that indicates if the key can be used for authentication.
683 * gpgme_signature_t's status field is now correctly set to an error
684 with error code GPG_ERR_NO_PUBKEY if public key is not found.
686 * gpgme_new_signature_t's class field is now an unsigned int, rather
687 than an unsigned long (the old class field is preserved for
688 backwards compatibility).
690 * A new function gpgme_set_locale() is provided to allow configuring
691 the locale for the crypto backend. This is necessary for text
692 terminals so that programs like the pinentry can be started with
693 the right locale settings for the terminal the application is running
694 on, in case the terminal has different settings than the system
695 default (for example, if it is a remote terminal). You are highly
696 recommended to call the following functions directly after
701 setlocale (LC_ALL, "");
702 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
703 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
705 GPGME can not do this for you, as setlocale is not thread safe, and
706 there is no alternative.
708 * The signal action for SIGPIPE is now set to SIG_IGN by
709 gpgme_check_version, instead the first time a crypto engine is
710 started (which is not well defined).
712 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
713 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
714 to CRC24RFC2440. For now, these strings can be used as the MIC
715 parameter for PGP/MIME (if appropriately modified).
717 * Interface changes relative to the 0.4.2 release:
718 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
720 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
721 gpgme_key_t EXTENDED: New field can_authenticate.
722 gpgme_subkey_t EXTENDED: New field can_authenticate.
723 gpgme_new_signature_t CHANGED: New type for class field.
725 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
726 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
728 Noteworthy changes in version 0.4.2 (2003-07-30)
729 ------------------------------------------------
731 * Allow gpg-error to be in non-standard place when linking the test suite.
733 * Configure will fail now if gpg-error can not be found.
735 * Fixed initialized memory backed data objects for writing, which
736 caused the test program to crash (but only on Mac OS, surprisingly).
738 * Eliminate use of C99 constructs.
740 * Small improvements to the manual.
743 Noteworthy changes in version 0.4.1 (2003-06-06)
744 ------------------------------------------------
746 This is the release that 0.4.0 should have been. There are many
747 interface changes, please see below for the details. The changes are
748 sometimes the result of new functionality, but more often express a
749 paradigm shift. Others are an overdue cleanup to get GPGME in line
750 with the GNU coding standards and to make the interface more
751 self-consistent. Here is an overview on the changes:
753 All types have been renamed to conform to the GNU coding standards,
754 most of the time by keeping the whole name in lowercase and inserting
755 underscores between words.
757 All operations consistently only accept input parameters in their
758 invocation function, and return only an error code directly. Further
759 information about the result of the operation has to be retrieved
760 afterwards by calling one of the result functions. This unifies the
761 synchronous and the asynchronous interface.
763 The error values have been completely replaced by a more
764 sophisticated model that allows GPGME to transparently and accurately
765 report all errors from the other GnuPG components, irregardless of
766 process boundaries. This is achieved by using the library
767 libgpg-errors, which is shared by all GnuPG components. This library
768 is now required for GPGME.
770 The results of all operations are now provided by pointers to C
771 structs rather than by XML structs or in other ways.
773 Objects which used to be opaque (for example a key) are now pointers
774 to accessible structs, so no accessor functions are necessary.
776 Backward compatibility is provided where it was possible without too
777 much effort and did not collide with the overall sanitization effort.
778 However, this is only for ease of transition. NO DEPRECATED FUNCTION
779 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
780 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
781 Recommendations how to replace deprecated or removed functionality
782 can be found within the description of each change.
784 What follows are all changes to the interface and behaviour of GPGME
787 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
788 deprecated attributes will warn about use of obsolete functions and
789 type definitions. You can suppress these warnings by passing
790 -Wno-deprecated-declarations to the gcc command.
792 * The following types have been renamed. The old types are still
793 available as aliases, but they are deprecated now:
796 GpgmeData gpgme_data_t
797 GpgmeError gpgme_error_t
798 GpgmeDataEncoding gpgme_data_encoding_t
799 GpgmeSigStat gpgme_sig_stat_t
800 GpgmeSigMode gpgme_sig_mode_t
801 GpgmeAttr gpgme_attr_t
802 GpgmeValidity gpgme_validity_t
803 GpgmeProtocol gpgme_protocol_t
805 GpgmePassphraseCb gpgme_passphrase_cb_t
806 GpgmeProgressCb gpgme_progress_cb_t
807 GpgmeIOCb gpgme_io_cb_t
808 GpgmeRegisterIOCb gpgme_register_io_cb_t
809 GpgmeRemoveIOCb gpgme_remove_io_cb_t
810 GpgmeEventIO gpgme_event_io_t
811 GpgmeEventIOCb gpgme_event_io_cb_t
812 GpgmeIOCbs gpgme_io_cbs
813 GpgmeDataReadCb gpgme_data_read_cb_t
814 GpgmeDataWriteCb gpgme_data_write_cb_t
815 GpgmeDataSeekCb gpgme_data_seek_cb_t
816 GpgmeDataReleaseCb gpgme_data_release_cb_t
817 GpgmeDataCbs gpgme_data_cbs_t
818 GpgmeTrustItem gpgme_trust_item_t
819 GpgmeStatusCode gpgme_status_code_t
821 * gpgme_error_t is now identical to gpg_error_t, the error type
822 provided by libgpg-error. More about using libgpg-error with GPGME
823 can be found in the manual. All error symbols have been removed!
825 * All functions and types in libgpg-error have been wrapped in GPGME.
826 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
827 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
828 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
829 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
832 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
834 * GnuPG 1.2.2 is required. The progress callback is now also invoked
835 for encrypt, sign, encrypt-sign, decrypt, verify, and
836 decrypt-verify operations. For verify operations on detached
837 signatures, the progress callback is invoked for both the detached
838 signature and the plaintext message, though.
840 * gpgme_passphrase_cb_t has been changed to not provide a complete
841 description, but the UID hint, passphrase info and a flag
842 indicating if this is a repeated attempt individually, so the user
843 can compose his own description from this information.
845 The passphrase is not returned as a C string, but must be written
846 to a file descriptor directly. This allows for secure passphrase
849 The return type has been changed to gpgme_error_t value. This
850 allowed to remove the gpgme_cancel function; just return
851 the error code GPG_ERR_CANCELED in the passphrase callback directly.
853 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
854 The user is expected to write the response to the file descriptor,
855 followed by a newline.
857 * The recipients interface has been removed. Instead, you use
858 NULL-terminated lists of keys for specifying the recipients of an
859 encryption operation. Use the new encryption flag
860 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
861 the keys (but note that in general this is not a good idea).
863 This change has been made to the prototypes of gpgme_op_encrypt,
864 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
865 gpgme_op_encrypt_sign_start.
867 The export interface has been changed to use pattern strings like
868 the keylist interface. Thus, new functions gpgme_op_export_ext and
869 gpgme_op_export_ext_start have been added as well. Now the
870 prototypes of gpgme_op_export_start and gpgme_op_export finally
873 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
874 summary anymore. Use gpgme_get_sig_status to retrieve the individual
877 * gpgme_io_cb_t changed from a void function to a function returning
878 a gpgme_error_t value. However, it will always return 0, so you
879 can safely ignore the return value.
881 * A new I/O callback event GPGME_EVENT_START has been added. The new
882 requirement is that you must wait until this event until you are
883 allowed to call the I/O callback handlers previously registered for
884 this context operation. Calling I/O callback functions for this
885 context operation before the start event happened is unsafe because
886 it can lead to race conditions in a multi-threaded environment.
888 * The idle function feature has been removed. It was not precisely
889 defined in a multi-threaded environment and is obsoleted by the
890 user I/O callback functions. If you still need a simple way to
891 call something while waiting on one or multiple asynchronous
892 operations to complete, don't set the HANG flag in gpgme_wait (note
893 that this will return to your program more often than the idle
896 * gpgme_wait can return NULL even if hang is true, if an error
897 occurs. In that case *status contains the error code.
899 * gpgme_get_engine_info was radically changed. Instead an XML
900 string, an info structure of the new type gpgme_engine_info_t is
901 returned. This makes it easier and more robust to evaluate the
902 information in an application.
904 * The new function gpgme_get_protocol_name can be used to convert a
905 gpgme_protocol_t value into a string.
907 * The status of a context operation is not checked anymore. Starting
908 a new operation will silently cancel the previous one. Calling a
909 function that requires you to have started an operation before without
910 doing so is undefined.
912 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
913 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
914 pointer to a structure which contains the fingerprint. This also
915 works with gpgme_op_genkey_start. The structure also provides
916 other information about the generated keys.
921 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
923 printf ("%s\n", fpr);
927 gpgme_genkey_result_t result;
928 err = gpgme_op_genkey (ctx, NULL, NULL);
931 result = gpgme_op_genkey_result (ctx);
933 printf ("%s\n", result->fpr);
936 * The new gpgme_op_import_result function provides detailed
937 information about the result of an import operation in
938 gpgme_import_result_t and gpgme_import_status_t objects.
939 Thus, the gpgme_op_import_ext variant is deprecated.
941 * The new gpgme_op_sign_result function provides detailed information
942 about the result of a signing operation in gpgme_sign_result_t,
943 gpgme_invalid_key_t and gpgme_new_signature_t objects.
945 * The new gpgme_op_encrypt_result function provides detailed
946 information about the result of an encryption operation in
947 a GpgmeEncryptResult object.
949 * The new gpgme_op_decrypt_result function provides detailed
950 information about the result of a decryption operation in
951 a GpgmeDecryptResult object.
953 * The new gpgme_op_verify_result function provides detailed
954 information about the result of an verify operation in
955 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
956 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
957 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
958 and gpgme_get_notation is removed.
960 * GpgmeTrustItem objects have now directly accessible data, so the
961 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
962 accessor functions are deprecated. Also, reference counting is
963 available through gpgme_trust_item_ref and gpgme_trust_item_unref
964 (the gpgme_trust_item_release alias for the latter is deprecated).
966 * Keys are not cached internally anymore, so the force_update argument
967 to gpgme_get_key has been removed.
969 * GpgmeKey objects have now directly accessible data so the
970 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
971 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
972 functions are deprecated. Also, gpgme_key_release is now
973 deprecated. The gpgme_key_get_as_xml function has been dropped.
975 * Because all interfaces using attributes are deprecated, the
976 GpgmeAttr data type is also deprecated.
978 * The new gpgme_op_keylist_result function provides detailed
979 information about the result of a key listing operation in
980 a GpgmeKeyListResult object.
982 * Now that each function comes with its own result retrieval
983 interface, the generic gpgme_get_op_info interface is not useful
986 * The type and mode of data objects is not available anymore.
988 * Interface changes relative to the 0.4.0 release:
989 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
990 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
991 GpgmeData DEPRECATED: Use gpgme_data_t.
992 GpgmeError DEPRECATED: Use gpgme_error_t.
993 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
994 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
995 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
996 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
997 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
998 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
999 GpgmeKey DEPRECATED: Use gpgme_key_t.
1000 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
1001 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
1002 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
1003 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
1004 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
1005 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
1006 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
1007 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
1008 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
1009 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
1010 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
1011 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
1012 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
1013 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
1014 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
1017 gpgme_recipients_t NEW
1019 gpgme_data_encoding_t NEW
1020 gpgme_sig_stat_t NEW
1021 gpgme_sig_mode_t NEW
1023 gpgme_validity_t NEW
1024 gpgme_protocol_t NEW
1026 gpgme_passphrase_cb_t NEW
1027 gpgme_progress_cb_t NEW
1029 gpgme_register_io_cb_t NEW
1030 gpgme_remove_io_cb_t NEW
1031 gpgme_event_io_t NEW
1032 gpgme_event_io_cb_t NEW
1034 gpgme_data_read_cb_t NEW
1035 gpgme_data_write_cb_t NEW
1036 gpgme_data_seek_cb_t NEW
1037 gpgme_data_release_cb_t NEW
1038 gpgme_data_cbs_t NEW
1039 gpgme_trust_item_t NEW
1040 gpgme_status_code_t NEW
1041 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
1042 gpgme_err_code_t NEW
1043 gpgme_err_source_t NEW
1045 gpgme_err_source NEW
1048 gpgme_error_from_errno NEW
1049 gpgme_err_make_from_errno NEW
1050 gpgme_err_code_from_errno NEW
1051 gpgme_err_code_to_errno NEW
1053 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
1054 gpgme_event_io_t CHANGED: New event type (all numbers changed).
1055 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
1056 gpgme_edit_cb_t CHANGED: Write directly to FD.
1057 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
1058 gpgme_op_verify CHANGED: Drop R_STAT argument.
1059 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
1060 gpgme_wait CHANGED: Can return NULL even if hang is true.
1061 GpgmeIdleFunc REMOVED
1062 gpgme_register_idle REMOVED
1063 GpgmeRecipients REMOVED
1064 gpgme_recipients_new REMOVED
1065 gpgme_recipients_release REMOVED
1066 gpgme_recipients_add_name REMOVED
1067 gpgme_recipients_add_name_with_validity REMOVED
1068 gpgme_recipients_count REMOVED
1069 gpgme_recipients_enum_open REMOVED
1070 gpgme_recipients_enum_read REMOVED
1071 gpgme_recipients_enum_close REMOVED
1072 gpgme_encrypt_flags_t NEW
1073 GPGME_ENCRYPT_ALWAYS_TRUST NEW
1074 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
1075 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
1076 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
1077 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
1078 gpgme_op_export_start CHANGED: User IDs passed as patterns.
1079 gpgme_op_export CHANGED: User IDs passed as patterns.
1080 gpgme_op_export_ext_start NEW
1081 gpgme_op_export_ext NEW
1082 gpgme_keylist_mode_t NEW
1084 gpgme_engine_info_t NEW
1085 gpgme_get_engine_info CHANGED: Return info structure instead XML.
1086 gpgme_get_protocol_name NEW
1087 gpgme_cancel REMOVED: Return error in callback directly.
1088 gpgme_op_genkey CHANGED: FPR argument dropped.
1089 gpgme_op_genkey_result NEW
1090 gpgme_genkey_result_t NEW
1091 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
1092 gpgme_op_import_result NEW
1093 gpgme_import_status_t NEW
1094 gpgme_import_result_t NEW
1095 gpgme_pubkey_algo_t NEW
1096 gpgme_hash_algo_t NEW
1097 gpgme_invalid_key_t NEW
1098 gpgme_new_signature_t NEW
1099 gpgme_sign_result_t NEW
1100 gpgme_op_sign_result NEW
1101 gpgme_pubkey_algo_name NEW
1102 gpgme_hash_algo_name NEW
1103 gpgme_encrypt_result_t NEW
1104 gpgme_op_encrypt_result NEW
1105 gpgme_decrypt_result_t NEW
1106 gpgme_op_decrypt_result NEW
1107 gpgme_verify_result_t NEW
1108 gpgme_op_verify_result NEW
1109 gpgme_get_notation REMOVED: Access verify result directly instead.
1110 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
1111 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
1112 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
1113 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
1114 gpgme_get_sig_status DEPRECATED: Use verify result directly.
1115 gpgme_trust_item_t CHANGED: Now has user accessible data members.
1116 gpgme_trust_item_ref NEW
1117 gpgme_trust_item_unref NEW
1118 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
1119 gpgme_trust_item_get_string_attr DEPRECATED
1120 gpgme_trust_item_get_ulong_attr DEPRECATED
1121 gpgme_get_key CHANGED: Removed force_update argument.
1125 gpgme_key_t CHANGED: Now has user accessible data members.
1126 gpgme_key_get_string_attr DEPRECATED
1127 gpgme_key_get_ulong_attr DEPRECATED
1128 gpgme_key_sig_get_string_attr DEPRECATED
1129 gpgme_key_sig_get_ulong_attr DEPRECATED
1130 gpgme_key_get_as_xml REMOVED
1131 gpgme_key_list_result_t NEW
1132 gpgme_op_keylist_result NEW
1133 gpgme_get_op_info REMOVED
1134 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1136 Noteworthy changes in version 0.4.0 (2002-12-23)
1137 ------------------------------------------------
1139 * Key generation returns the fingerprint of the generated key.
1141 * New convenience function gpgme_get_key.
1143 * Supports signatures of user IDs in keys via the new
1144 GPGME_KEYLIST_MODE_SIGS keylist mode and the
1145 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
1146 interfaces. The XML info about a key also includes the signatures
1149 * New data object interface, which is more flexible and transparent.
1151 * Interface changes relative to the 0.3.9 release:
1152 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1154 GpgmeDataWriteCb NEW
1156 GpgmeDataReleaseCb NEW
1158 gpgme_data_read CHANGED: Match read() closely.
1159 gpgme_data_write CHANGED: Match write() closely.
1161 gpgme_data_new_from_fd NEW
1162 gpgme_data_new_from_stream NEW
1163 gpgme_data_new_from_cbs NEW
1164 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
1165 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
1166 gpgme_data_get_type REMOVED: No replacement.
1167 gpgme_op_verify CHANGED: Take different data objects for
1168 signed text and plain text.
1169 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
1170 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
1171 gpgme_op_genkey CHANGED: New parameter FPR.
1172 GPGME_KEYLIST_MODE_SIGS NEW
1173 gpgme_key_sig_get_string_attr NEW
1174 gpgme_key_sig_get_ulong_attr NEW
1176 GPGME_ATTR_SIG_CLASS NEW
1177 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1179 Noteworthy changes in version 0.3.16 (2003-11-19)
1180 -------------------------------------------------
1182 * Compatibility fixes for GnuPG 1.9.x
1184 Noteworthy changes in version 0.3.15 (2003-02-18)
1185 -------------------------------------------------
1187 * The progress status is sent via the progress callbacks in
1190 * Bug fix for signing operations with explicit signer settings for
1193 Noteworthy changes in version 0.3.14 (2002-12-04)
1194 -------------------------------------------------
1196 * GPGME-Plug is now in its own package "cryptplug".
1198 * Workaround for a setlocale problem. Fixed a segv related to not
1199 correctly as closed marked file descriptors.
1201 Noteworthy changes in version 0.3.13 (2002-11-20)
1202 -------------------------------------------------
1204 * Release due to changes in gpgmeplug.
1206 Noteworthy changes in version 0.3.12 (2002-10-15)
1207 -------------------------------------------------
1209 * Fixed some bux with key listings.
1211 * The development has been branched to clean up some API issues.
1212 This 0.3 series will be kept for compatibility reasons; so do don't
1213 expect new features.
1215 Noteworthy changes in version 0.3.11 (2002-09-20)
1216 -------------------------------------------------
1220 Noteworthy changes in version 0.3.10 (2002-09-02)
1221 -------------------------------------------------
1223 * Setting the signing keys for the CMS protocol does now work.
1225 * The signers setting is honoured by gpgme_op_edit.
1227 Noteworthy changes in version 0.3.9 (2002-08-21)
1228 ------------------------------------------------
1230 * A spec file for creating RPMs has been added.
1232 * An experimental interface to GnuPG's --edit-key functionality is
1233 introduced, see gpgme_op_edit.
1235 * The new gpgme_import_ext function provides a convenient access to
1236 the number of processed keys.
1238 * Interface changes relative to the 0.3.8 release:
1239 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1242 gpgme_op_edit_start NEW
1244 gpgme_op_import_ext NEW
1245 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1247 Noteworthy changes in version 0.3.8 (2002-06-25)
1248 ------------------------------------------------
1250 * It is possible to use an outside event loop for the I/O to the
1251 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1253 * Interface changes relative to the 0.3.6 release:
1254 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1256 GpgmeRegisterIOCb NEW
1260 struct GpgmeIOCbs NEW
1261 gpgme_set_io_cbs NEW
1262 gpgme_get_io_cbs NEW
1263 GPGME_ATTR_ERRTOK NEW
1264 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1266 Noteworthy changes in version 0.3.7 (2002-06-04)
1267 ------------------------------------------------
1269 * GPGME_ATTR_OTRUST is implemented now.
1271 * A first step toward thread safeness has been achieved, see the
1272 documentation for details. Supported thread libraries are pthread
1275 Noteworthy changes in version 0.3.6 (2002-05-03)
1276 ------------------------------------------------
1278 * All error output of the gpgsm backend is send to the bit bucket.
1280 * The signature verification functions are extended. Instead of
1281 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1282 expired signatures. 2 new functions may be used to retrieve more
1283 detailed information like the signature expiration time and a
1284 validity information of the key without an extra key looking.
1286 * The current passphrase callback and progress meter callback can be
1287 retrieved with the new functions gpgme_get_passphrase_cb and
1288 gpgme_get_progress_cb respectively.
1290 * Interface changes relative to the 0.3.5 release:
1291 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1292 gpgme_get_passphrase_cb NEW
1293 gpgme_get_progress_cb NEW
1294 GpgmeDataEncoding NEW
1295 gpgme_data_set_encoding NEW
1296 gpgme_data_get_encoding NEW
1297 GPGME_SIG_STAT_GOOD_EXP NEW
1298 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1299 gpgme_op_verify CHANGED: Returns more status codes.
1300 GPGME_ATTR_SIG_STATUS NEW
1301 gpgme_get_sig_string_attr NEW
1302 gpgme_get_sig_ulong_attr NEW
1303 gpgme_get_protocol NEW
1304 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1306 Noteworthy changes in version 0.3.5 (2002-04-01)
1307 ------------------------------------------------
1309 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1310 case, symmetric encryption is performed. Note that this requires a
1311 passphrase from the user.
1313 * More information is returned for X.509 certificates.
1315 * Interface changes relative to the 0.3.4 release:
1316 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1317 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1318 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1320 Noteworthy changes in version 0.3.4 (2002-03-04)
1321 ------------------------------------------------
1323 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1324 some recipients have been invalid, whereas earlier versions
1325 succeeded in this case. The plaintext is still encrypted for all valid
1326 recipients, so the application might take this error as a hint that
1327 the ciphertext is not usable for all requested recipients.
1328 Information about invalid recipients is available with gpgme_get_op_info.
1330 * gpgme_op_verify now allows to pass an uninitialized data object as
1331 its plaintext argument to check for normal and cleartext
1332 signatures. The plaintext is then returned in the data object.
1334 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1335 to set and get the number of certifications to include in S/MIME
1338 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1339 to encrypt and sign a message in a combined operation.
1341 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1343 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1345 * Interface changes relative to the 0.3.3 release:
1346 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1347 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1348 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1349 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1350 gpgme_set_include_certs NEW
1351 gpgme_get_include_certs NEW
1352 gpgme_op_encrypt_sign NEW
1353 gpgme_op_encrypt_sign_start NEW
1354 gpgme_op_keylist_ext_start NEW
1355 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1357 Noteworthy changes in version 0.3.3 (2002-02-12)
1358 ------------------------------------------------
1360 * Fix the Makefile in jnlib.
1362 * Fix the test suite (hopefully). It should clean up all its state
1363 with `make check' now.
1366 Noteworthy changes in version 0.3.2 (2002-02-10)
1367 ------------------------------------------------
1369 * Remove erroneous dependency on libgcrypt in jnlib.
1372 Noteworthy changes in version 0.3.1 (2002-02-09)
1373 ------------------------------------------------
1375 * There is a Texinfo manual documenting the API.
1377 * The gpgme_set_keylist_mode function returns an error, and changed
1378 its meaning. It is no longer usable to select between normal and
1379 fast mode (newer versions of GnuPG will always be fast), but
1380 selects between local keyring, remote keyserver, or both.
1381 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1382 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1383 current setting, a fucntion gpgme_get_keylist_mode was added to
1384 retrieve the current mode.
1386 * gpgme_wait accepts a new argument STATUS to return the error status
1387 of the operation on the context. Its definition is closer to
1388 waitpid() now than before.
1390 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1391 type from off_t to the unsigned size_t.
1393 * The R_HD argument to the GpgmePassphraseCb type changed its type
1394 from void* to void**.
1396 * New interface gpgme_op_trustlist_end() to match
1397 gpgme_op_keylist_end().
1399 * The CryptPlug modules have been renamed to gpgme-openpgp and
1400 gpgme-smime, and they are installed in pkglibdir by `make install'.
1402 * An idle function can be registered with gpgme_register_idle().
1404 * The GpgSM backend supports key generation with gpgme_op_genkey().
1406 * Interface changes relative to the 0.3.0 release:
1407 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1408 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1409 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1410 gpgme_wait CHANGED: New argument STATUS.
1411 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1412 The function has a new meaning!
1413 gpgme_get_keylist_mode NEW
1414 GPGME_KEYLIST_MODE_LOCAL NEW
1415 GPGME_KEYLIST_MODE_EXTERN NEW
1416 gpgme_op_trustlist_next NEW
1418 gpgme_register_idle NEW
1419 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1421 Noteworthy changes in version 0.3.0 (2001-12-19)
1422 ------------------------------------------------
1424 * New interface gpgme_set_protocol() to set the protocol and thus the
1425 crypto engine to be used by the context. Currently, the OpenPGP
1426 and the CMS protocols are supported. They are specified by the new
1427 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1428 A new context uses the OpenPGP engine by default.
1430 * gpgme_get_engine_info() returns information for all crypto engines
1431 compiled into the library. The XML format has changed. To
1432 reliably get the version of a crypto engine, the <version> tag
1433 after the appropriate <protocol> tag has to be looked for.
1435 * New interface gpgme_engine_check_version(), obsoleting
1436 gpgme_check_engine(). Check the version of all engines you are
1437 supporting in your software.
1439 * GpgmeKey lists the user ids in the order as they are returned by
1440 GnuPG, first the primary key with index 0, then the sub-user ids.
1442 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1443 signatures simultaneously.
1445 * The new interface gpgme_op_keylist_end() terminates a pending
1446 keylist operation. A keylist operation is also terminated when
1447 gpgme_op_keylist_next() returns GPGME_EOF.
1449 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1450 cross-compiled, or even compiled without support for GnuPG
1453 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1454 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1455 in the path, but it can also be compiled without support for GpgSM
1456 (`--without-gpgsm').
1458 * CryptPlug modules for GPGME are included and can be enabled at
1459 configure time (`--enable-gpgmeplug'). There is one module which
1460 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1461 GpgSM engine (`gpgsmplug').
1463 * Interface changes relative to the latest 0.2.x release:
1464 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1465 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1466 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1467 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1468 gpgme_get_engine_info CHANGED: New format, extended content.
1469 gpgme_engine_check_version NEW
1470 gpgme_decrypt_verify_start NEW
1471 gpgme_decrypt_verify NEW
1472 gpgme_op_keylist_next NEW
1473 gpgme_set_protocol NEW
1474 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1477 Noteworthy changes in version 0.2.3 (2001-09-17)
1478 ------------------------------------------------
1480 * New function gpgme_get_op_info which can be used to get the micalg
1481 parameter needed for MOSS.
1483 * New functions gpgme_get_armor and gpgme_get_textmode.
1485 * The usual bug fixes and some minor functionality improvements.
1487 * Added a simple encryption component for MS-Windows; however the
1488 build procedure might have some problems.
1491 Noteworthy changes in version 0.2.2 (2001-06-12)
1492 ------------------------------------------------
1494 * Implemented a key cache.
1496 * Fixed a race condition under W32 and some other bug fixes.
1499 Noteworthy changes in version 0.2.1 (2001-04-02)
1500 ------------------------------------------------
1502 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1504 * Handle GnuPG's new key capabilities output and support revocation
1507 * Made the W32 support more robust.
1510 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008, 2009,
1513 This file is free software; as a special exception the author gives
1514 unlimited permission to copy and/or distribute it, with or without
1515 modifications, as long as this notice is preserved.
1517 This file is distributed in the hope that it will be useful, but
1518 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1519 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.