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