1 Noteworthy changes in version 1.2.0 (2009-06-18)
2 ------------------------------------------------
4 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
7 * gpgme_new will fail if gpgme_check_version was not called, or a
8 selftest failed (for example, if -mms-bitfields was not used on
11 * New functions gpgme_io_read and gpgme_io_write for use with
12 gpgme_passphrase_cb_t and gpgme_edit_cb_t functions.
14 * New functions gpgme_result_ref and gpgme_result_unref to detach
15 result structures from a context.
17 * New functions gpgme_op_export_keys_start and gpgme_op_export_keys
18 that allow to specify exported keys through gpgme_key_t objects
21 * New mode of operation gpgme_export_mode_t that allows exporting
24 * Interface changes relative to the 1.1.7 release:
25 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
26 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
27 GPGME_PROTOCOL_ASSUAN NEW.
28 gpgme_assuan_data_cb_t NEW.
29 gpgme_assuan_inquire_cb_t NEW.
30 gpgme_assuan_status_cb_t NEW.
31 gpgme_op_assuan_transact_start NEW.
32 gpgme_op_assuan_transact NEW.
33 gpgme_op_assuan_result NEW.
34 gpgme_op_import_keys NEW.
35 gpgme_op_import_keys_start NEW.
36 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
37 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
38 gpgme_check_version CHANGED: Is now a macro.
39 gpgme_new EXTENDED: More failure codes.
43 gpgme_result_unref NEW.
44 gpgme_export_mode_t NEW.
45 gpgme_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
46 gpgme_op_export EXTENDED: Arg RESERVED is now a MODE flag.
47 gpgme_op_export_ext_start EXTENDED: Arg RESERVED is now a MODE flag.
48 gpgme_op_export_ext EXTENDED: Arg RESERVED is now a MODE flag.
49 gpgme_op_export_keys_start NEW.
50 gpgme_op_export_keys NEW.
51 GPGME_DATA_ENCODING_URL NEW.
52 GPGME_DATA_ENCODING_URL0 NEW.
53 GPGME_DATA_ENCODING_URLESC NEW.
54 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
57 Noteworthy changes in version 1.1.8 (2008-12-08)
58 ------------------------------------------------
60 * SIGPIPE is now again ignored as described in the manual. Fixes
61 regresion introduced with 1.1.6.
64 Noteworthy changes in version 1.1.7 (2008-10-17)
65 ------------------------------------------------
67 * Using GPGME_KEYLIST_MODE_LOCAL combined with
68 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
69 --locate-keys feature of gpg (>= 2.0.10).
71 * The encoding of gpgme_data_t objects can affect the output encoding
72 of export, sign and encrypt operations now (the same operations
73 that are also affected by the ASCII mode switch). We believe this
74 change in the ABI is innocent enough not to break existing
75 applications (it only affects the S/MIME backend on certain
78 * The reference manual now includes the specification of "The GnuPG
81 * A new function gpgme_cancel_async can be used to asynchronously
82 cancel any pending operation at any time, from any thread.
84 * Interface changes relative to the 1.1.6 release:
85 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
86 gpgme_op_encrypt CHANGED: Output encoding can affect result.
87 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
88 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
89 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
90 gpgme_op_sign CHANGED: Output encoding can affect result.
91 gpgme_op_sign_start CHANGED: Output encoding can affect result.
92 gpgme_op_export CHANGED: Output encoding can affect result.
93 gpgme_op_export_start CHANGED: Output encoding can affect result.
94 gpgme_op_export_ext CHANGED: Output encoding can affect result.
95 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
96 gpgme_cancel_async NEW
97 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
100 Noteworthy changes in version 1.1.6 (2008-01-04)
101 ------------------------------------------------
103 * Bug fixes for for W32.
105 * A new, experimental (and thus undocumented and potentially
106 unstable) interface for accessing gpg-conf through GPGME has been
109 * Interface changes relative to the 1.1.1 release:
110 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
111 gpgme_signature_t EXTENDED: New field chain_model.
112 gpgme_op_getauditlog_start NEW.
113 gpgme_op_getauditlog NEW.
114 GPGME_AUDITLOG_HTML NEW.
115 GPGME_AUDITLOG_WITH_HELP NEW.
116 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
119 Noteworthy changes in version 1.1.5 (2007-07-09)
120 ------------------------------------------------
122 * Bug and portability fixes (mainly for W32).
125 Noteworthy changes in version 1.1.4 (2007-03-05)
126 ------------------------------------------------
128 * Detect and bail out on double plaintext messages. This is required
129 so that applications can properly detect the signed parts of a
130 message. Actual there is now a double protection as GnuPG 1.4.7
131 will detect this case too.
134 Noteworthy changes in version 1.1.3 (2007-01-29)
135 ------------------------------------------------
137 * Fixed a memory leak in gpgme_data_release_and_get_mem.
139 * Fixed a bug in Windows command line quoting.
142 Noteworthy changes in version 1.1.2 (2006-03-02)
143 ------------------------------------------------
145 * Fixed a bug in the W32 glib backend.
148 Noteworthy changes in version 1.1.1 (2006-02-23)
149 ------------------------------------------------
151 * Fixed a bug in that the fingerprints of subkeys are not available.
153 * Clarified usage of the SECRET flag in key listings. It is now
156 * Reading signature notations and policy URLs on key signatures is
157 supported. They can be found in the new field notations of the
158 gpgme_key_sig_t structure. This has to be enabled with the keylist
159 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
161 * A new gpgme_free() function solves the problem of using different
162 allocators in a single program. This function should now be used
163 instead calling free() to release the buffer returned by
164 gpgme_data_release_and_get_mem. It is recommended that you always
165 do this, but it is only necessary on certain platforms, so backwards
166 compatibility is provided. In other words: If free() worked for
167 you before, it will keep working.
169 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
170 They are analyzed by the verify handlers and made available in the
171 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
173 * Interface changes relative to the 1.1.0 release:
174 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
175 gpgme_key_sig_t EXTENDED: New field notations.
176 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
178 GPGME_STATUS_PKA_TRUST_BAD NEW
179 GPGME_STATUS_PKA_TRUST_GOOD NEW
180 gpgme_signature_t EXTENDED: New field pka_trust.
181 gpgme_signature_t EXTENDED: New field pka_address.
182 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
185 Noteworthy changes in version 1.1.0 (2005-10-01)
186 ------------------------------------------------
188 * You can now configure the backend engine file name and home
189 directory to be used, as default and per context.
191 * Information about the recipients of an encrypted text is now
192 available at decryption time.
194 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
195 and verify handlers, the information about the plaintext filename,
196 if available is made available in the new field file_name of the
197 respective result structure.
199 * The code for "automagically detecting the thread library" has been
200 removed from libgpgme. It is deprecated since version 0.4.3.
201 Since then, you had to link against libgpgme-pthread for
202 applications using pthread and libgpgme-pth for applications using
205 The code was removed because it caused compilation problems on
206 systems where the pthread.h header from GNU Pth is available in
207 addition to the system header (FreeBSD 6 and later for example).
209 * "./autogen.sh --build-w32" does now build gpgme.dll.
211 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
212 delimiter. The standard install directory is used when locating
213 gpg or gpgsm before finally falling back to the hardwired name.
215 * There is a new flag for keys and subkeys, is_qualified, which
216 indicates if a key can be used for qualified signatures according
217 to local government regulations.
219 * You can associate a filename with a data object using the new
220 function gpgme_data_set_file_name(). This filename will be stored
221 in the output when encrypting or signing the data and will be
222 returned when decrypting or verifying the output data.
224 * You can now set notation data at signature creation with the new
225 function gpgme_sig_notation_add().
227 * Interface changes relative to the 1.0.3 release:
228 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
229 gpgme_set_engine_info NEW
230 gpgme_ctx_get_engine_info NEW
231 gpgme_ctx_set_engine_info NEW
232 gpgme_recipient_t NEW
233 gpgme_decrypt_result_t EXTENDED: New field recipients.
234 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
235 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
236 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
237 GPGME_STATUS_PLAINTEXT NEW
238 gpgme_key_t EXTENDED: New field is_qualified.
239 gpgme_subkey_t EXTENDED: New field is_qualified.
240 gpgme_data_get_file_name NEW
241 gpgme_data_set_file_name NEW
242 gpgme_sig_notation_flags_t NEW
243 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
244 GPGME_SIG_NOTATAION_CRITICAL NEW
245 gpgme_sig_notation_clear NEW
246 gpgme_sig_notation_add NEW
247 gpgme_sig_notation_get NEW
248 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
251 Noteworthy changes in version 1.0.3 (2005-06-20)
252 ------------------------------------------------
254 * Previousy, GPGME would use a default "include certs" of 1. This
255 has been changed. Now GPGME will use the crypto backend engines
256 default unless you set the value with gpgme_set_include_certs()
257 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
258 as a value to explicitely request the new default behaviour.
260 Because the default changes, this is a slight change of the API
261 semantics. We consider it to be a bug fix.
263 * A bug which made GPGME hang has been fixed. If you have
264 experienced hanging before, please try out this version and let me
265 know if you still experience hanging problems.
267 * Interface changes relative to the 0.9.0 release:
268 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
269 gpgme_set_include_certs CHANGED DEFAULT
270 GPGME_INCLUDE_CERTS_DEFAULT NEW
271 GPGME_STATUS_SIG_SUBPACKET NEW
272 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
273 GPGME_STATUS_SC_OP_FAILURE NEW
274 GPGME_STATUS_SC_OP_SUCCESS NEW
275 GPGME_STATUS_CARDCTRL NEW
276 GPGME_STATUS_BACKUP_KEY_CREATED NEW
277 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
280 Noteworthy changes in version 1.0.2 (2004-12-28)
281 ------------------------------------------------
283 * Changed the license of the library to the GNU Lesser General Public
284 License (LGPL), version 2.1 or later.
287 Noteworthy changes in version 1.0.1 (2004-10-22)
288 ------------------------------------------------
293 Noteworthy changes in version 1.0.0 (2004-09-30)
294 ------------------------------------------------
296 * Version 1.0.0! We are proud to present you with a thoroughly
297 tested and stable version of the GPGME library. A big Thank You!
298 to all the people who made this possible.
300 The development will be branched into a stable 1.x.y series and the
303 * The gpgme.m4 macro supports checking the API version. Just prepend
304 it to the required version string, separated by a colon. For
305 example, this release has the version "1:1.0.0". The last release
306 to which this version is (mostly) ABI compatible is "1:0.4.2",
307 which is the default required version.
310 Noteworthy changes in version 0.9.0 (2004-06-08)
311 ------------------------------------------------
313 * The type gpgme_key_t has now a new field keylist_mode that contains
314 the keylist mode that was active at the time the key was retrieved.
316 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
317 that contains a flag indicating that the key should not have been
320 * Verifying a signature of a revoked key gives the correct result now
321 (GPG_ERR_CERT_REVOKED error code).
323 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
324 verify operations still allows you to look at the signature
327 * Clarified that patterns in keylisting operations have an upper
328 limit, and thus are not suited to list many keys at once by their
329 fingerprint. Also improve the error message if the pattern is too
330 long for the CMS protocol to handle.
332 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
333 gpgme_key_t EXTENDED: New field keylist_mode.
334 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
335 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
338 Noteworthy changes in version 0.4.7 (2004-04-29)
339 ------------------------------------------------
341 * Correctly initialize the fields expired, revoked, invalid, and
342 disabled in the gpgme_key_t structures.
344 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
345 accidently of type int instead unsigned int.
347 * Interface changes relative to the 0.4.5 release:
348 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
349 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
350 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
352 Noteworthy changes in version 0.4.6 (2004-04-06)
353 ------------------------------------------------
358 Noteworthy changes in version 0.4.5 (2004-03-07)
359 ------------------------------------------------
361 * GPGME is now compiled with LFS (large file support) by default.
362 This means that _all_ programs using GPGME must be compiled with
363 LFS support enabled by default. You can do this easily with
364 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
365 without autoconf by defining the preprocessor symbol
366 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
367 the C compiler command line, or by defining this preprocessor
368 symbol before including any system header files). For more
369 details, read the section on LFS in the manual.
371 Up to now, it was undocumented that GPGME was not using LFS.
372 But the public interfaces use off_t, and file descriptors are
373 exchanged between the application and GPGME. This was an oversight,
374 and bound to cause troubles in the future.
376 Writing GPGME as a dual mode library that seamlessly supports LFS
377 while keeping backwards compatibility is possible, but does not
378 solve the problem: Many applications already expect GPGME to have
379 LFS (they are compiled with off_t being a 64bit value). This is true
380 in particular for the popular Gtk+ and Qt programs.
382 So, although this is an ABI (but not an API) break, we will not
383 change the library version to reflect that. Because the interfaces
384 affected are probably not used yet in any GPGME 0.4 based
385 application, we don't expect any real failures from this change.
386 In fact, applications already using LFS will have some subtle bugs
389 However, if you encounter an application using GPGME 0.4.x that
390 does _not_ use LFS by default (off_t is a 32bit value), _and_
391 uses at least one of the functions gpgme_data_seek,
392 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
393 gpgme_data_new_from_cbs, then indeed this library will be ABI
394 incompatible with the program. As said above, we don't believe
395 such a program exists. If we are in error, then you have two
396 options: As a quick hack, you can configure GPGME with the
397 --disable-largefile option. This will revert the change, and GPGME
398 will not use LFS. However, GPGME will be incompatible with
399 programs that expect GPGME to use LFS. All applications are
400 required to use LFS when using GPGME, so this is only good as a
401 temporary local work-around.
403 The other option is to change the versioning of the library and
404 recompile all applications. We have reserved a special version of
405 the library for that, so you can do that without expecting a
406 version clash in the future. Furthermore, everyone who does this
407 will agree on the version to use (this is important for
408 distribution makers). Read the comment in configure.ac (before
409 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
410 blindly: As stated above, we think it is unlikely this measure is
411 needed. Still, it is there if necessary. If in doubt, contact us
412 and we will give our advise for your specific situation.
414 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
417 * New interface gpgme_cancel() that can be used to cancel
418 asynchronous operations.
420 * Interface changes relative to the 0.4.4 release:
421 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
422 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
423 gpgme_data_seek CHANGED: off_t is now a largefile type.
424 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
425 GPGME_KEYLIST_MODE_VALIDATE NEW
427 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
429 Noteworthy changes in version 0.4.4 (2004-01-12)
430 ------------------------------------------------
432 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
433 been renamed to "sig_class", to avoid clash with C++ compilers. In
434 the C API, the old name "class" has been preserved for backwards
435 compatibility, but is deprecated.
437 * Interface changes relative to the 0.4.3 release:
438 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
439 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
440 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
441 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
443 Noteworthy changes in version 0.4.3 (2003-10-06)
444 ------------------------------------------------
446 * libgpgme should not be used for threaded programs anymore. This
447 never worked reliably in all cases, because you had to
448 be careful about the linking order and libtool wouldn't do that for
449 you automatically. Instead, now you have to link against
450 libgpgme-pthread for applications using pthread and libgpgme-pth for
451 applications using GNU Pth.
453 The old code for automagically detecting the thread library is
454 still part of libgpgme, but it is DEPRECATED.
456 * There are new automake macros AM_PATH_GPGME_PTH and
457 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
458 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
459 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
460 variables of course also include the configuration for the thread
461 package itself. Alternatively, use libtool.
463 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
466 * gpgme-config doesn't support setting the prefix or exec prefix
467 anymore. I don't think it ever worked correctly, and it seems to
470 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
471 provided was not unique, instead returning the first matching key.
473 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
474 that indicates if the key can be used for authentication.
476 * gpgme_signature_t's status field is now correctly set to an error
477 with error code GPG_ERR_NO_PUBKEY if public key is not found.
479 * gpgme_new_signature_t's class field is now an unsigned int, rather
480 than an unsigned long (the old class field is preserved for
481 backwards compatibility).
483 * A new function gpgme_set_locale() is provided to allow configuring
484 the locale for the crypto backend. This is necessary for text
485 terminals so that programs like the pinentry can be started with
486 the right locale settings for the terminal the application is running
487 on, in case the terminal has different settings than the system
488 default (for example, if it is a remote terminal). You are highly
489 recommended to call the following functions directly after
494 setlocale (LC_ALL, "");
495 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
496 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
498 GPGME can not do this for you, as setlocale is not thread safe, and
499 there is no alternative.
501 * The signal action for SIGPIPE is now set to SIG_IGN by
502 gpgme_check_version, instead the first time a crypto engine is
503 started (which is not well defined).
505 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
506 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
507 to CRC24RFC2440. For now, these strings can be used as the MIC
508 parameter for PGP/MIME (if appropriately modified).
510 * Interface changes relative to the 0.4.2 release:
511 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
513 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
514 gpgme_key_t EXTENDED: New field can_authenticate.
515 gpgme_subkey_t EXTENDED: New field can_authenticate.
516 gpgme_new_signature_t CHANGED: New type for class field.
518 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
519 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
521 Noteworthy changes in version 0.4.2 (2003-07-30)
522 ------------------------------------------------
524 * Allow gpg-error to be in non-standard place when linking the test suite.
526 * Configure will fail now if gpg-error can not be found.
528 * Fixed initialized memory backed data objects for writing, which
529 caused the test program to crash (but only on Mac OS, surprisingly).
531 * Eliminate use of C99 constructs.
533 * Small improvements to the manual.
536 Noteworthy changes in version 0.4.1 (2003-06-06)
537 ------------------------------------------------
539 This is the release that 0.4.0 should have been. There are many
540 interface changes, please see below for the details. The changes are
541 sometimes the result of new functionality, but more often express a
542 paradigm shift. Others are an overdue cleanup to get GPGME in line
543 with the GNU coding standards and to make the interface more
544 self-consistent. Here is an overview on the changes:
546 All types have been renamed to conform to the GNU coding standards,
547 most of the time by keeping the whole name in lowercase and inserting
548 underscores between words.
550 All operations consistently only accept input parameters in their
551 invocation function, and return only an error code directly. Further
552 information about the result of the operation has to be retrieved
553 afterwards by calling one of the result functions. This unifies the
554 synchronous and the asynchronous interface.
556 The error values have been completely replaced by a more
557 sophisticated model that allows GPGME to transparently and accurately
558 report all errors from the other GnuPG components, irregardless of
559 process boundaries. This is achieved by using the library
560 libgpg-errors, which is shared by all GnuPG components. This library
561 is now required for GPGME.
563 The results of all operations are now provided by pointers to C
564 structs rather than by XML structs or in other ways.
566 Objects which used to be opaque (for example a key) are now pointers
567 to accessible structs, so no accessor functions are necessary.
569 Backward compatibility is provided where it was possible without too
570 much effort and did not collide with the overall sanitization effort.
571 However, this is only for ease of transition. NO DEPRECATED FUNCTION
572 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
573 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
574 Recommendations how to replace deprecated or removed functionality
575 can be found within the description of each change.
577 What follows are all changes to the interface and behaviour of GPGME
580 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
581 deprecated attributes will warn about use of obsolete functions and
582 type definitions. You can suppress these warnings by passing
583 -Wno-deprecated-declarations to the gcc command.
585 * The following types have been renamed. The old types are still
586 available as aliases, but they are deprecated now:
589 GpgmeData gpgme_data_t
590 GpgmeError gpgme_error_t
591 GpgmeDataEncoding gpgme_data_encoding_t
592 GpgmeSigStat gpgme_sig_stat_t
593 GpgmeSigMode gpgme_sig_mode_t
594 GpgmeAttr gpgme_attr_t
595 GpgmeValidity gpgme_validity_t
596 GpgmeProtocol gpgme_protocol_t
598 GpgmePassphraseCb gpgme_passphrase_cb_t
599 GpgmeProgressCb gpgme_progress_cb_t
600 GpgmeIOCb gpgme_io_cb_t
601 GpgmeRegisterIOCb gpgme_register_io_cb_t
602 GpgmeRemoveIOCb gpgme_remove_io_cb_t
603 GpgmeEventIO gpgme_event_io_t
604 GpgmeEventIOCb gpgme_event_io_cb_t
605 GpgmeIOCbs gpgme_io_cbs
606 GpgmeDataReadCb gpgme_data_read_cb_t
607 GpgmeDataWriteCb gpgme_data_write_cb_t
608 GpgmeDataSeekCb gpgme_data_seek_cb_t
609 GpgmeDataReleaseCb gpgme_data_release_cb_t
610 GpgmeDataCbs gpgme_data_cbs_t
611 GpgmeTrustItem gpgme_trust_item_t
612 GpgmeStatusCode gpgme_status_code_t
614 * gpgme_error_t is now identical to gpg_error_t, the error type
615 provided by libgpg-error. More about using libgpg-error with GPGME
616 can be found in the manual. All error symbols have been removed!
618 * All functions and types in libgpg-error have been wrapped in GPGME.
619 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
620 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
621 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
622 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
625 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
627 * GnuPG 1.2.2 is required. The progress callback is now also invoked
628 for encrypt, sign, encrypt-sign, decrypt, verify, and
629 decrypt-verify operations. For verify operations on detached
630 signatures, the progress callback is invoked for both the detached
631 signature and the plaintext message, though.
633 * gpgme_passphrase_cb_t has been changed to not provide a complete
634 description, but the UID hint, passphrase info and a flag
635 indicating if this is a repeated attempt individually, so the user
636 can compose his own description from this information.
638 The passphrase is not returned as a C string, but must be written
639 to a file descriptor directly. This allows for secure passphrase
642 The return type has been changed to gpgme_error_t value. This
643 allowed to remove the gpgme_cancel function; just return
644 the error code GPG_ERR_CANCELED in the passphrase callback directly.
646 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
647 The user is expected to write the response to the file descriptor,
648 followed by a newline.
650 * The recipients interface has been removed. Instead, you use
651 NULL-terminated lists of keys for specifying the recipients of an
652 encryption operation. Use the new encryption flag
653 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
654 the keys (but note that in general this is not a good idea).
656 This change has been made to the prototypes of gpgme_op_encrypt,
657 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
658 gpgme_op_encrypt_sign_start.
660 The export interface has been changed to use pattern strings like
661 the keylist interface. Thus, new functions gpgme_op_export_ext and
662 gpgme_op_export_ext_start have been added as well. Now the
663 prototypes of gpgme_op_export_start and gpgme_op_export finally
666 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
667 summary anymore. Use gpgme_get_sig_status to retrieve the individual
670 * gpgme_io_cb_t changed from a void function to a function returning
671 a gpgme_error_t value. However, it will always return 0, so you
672 can safely ignore the return value.
674 * A new I/O callback event GPGME_EVENT_START has been added. The new
675 requirement is that you must wait until this event until you are
676 allowed to call the I/O callback handlers previously registered for
677 this context operation. Calling I/O callback functions for this
678 context operation before the start event happened is unsafe because
679 it can lead to race conditions in a multi-threaded environment.
681 * The idle function feature has been removed. It was not precisely
682 defined in a multi-threaded environment and is obsoleted by the
683 user I/O callback functions. If you still need a simple way to
684 call something while waiting on one or multiple asynchronous
685 operations to complete, don't set the HANG flag in gpgme_wait (note
686 that this will return to your program more often than the idle
689 * gpgme_wait can return NULL even if hang is true, if an error
690 occurs. In that case *status contains the error code.
692 * gpgme_get_engine_info was radically changed. Instead an XML
693 string, an info structure of the new type gpgme_engine_info_t is
694 returned. This makes it easier and more robust to evaluate the
695 information in an application.
697 * The new function gpgme_get_protocol_name can be used to convert a
698 gpgme_protocol_t value into a string.
700 * The status of a context operation is not checked anymore. Starting
701 a new operation will silently cancel the previous one. Calling a
702 function that requires you to have started an operation before without
703 doing so is undefined.
705 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
706 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
707 pointer to a structure which contains the fingerprint. This also
708 works with gpgme_op_genkey_start. The structure also provides
709 other information about the generated keys.
714 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
716 printf ("%s\n", fpr);
720 gpgme_genkey_result_t result;
721 err = gpgme_op_genkey (ctx, NULL, NULL);
724 result = gpgme_op_genkey_result (ctx);
726 printf ("%s\n", result->fpr);
729 * The new gpgme_op_import_result function provides detailed
730 information about the result of an import operation in
731 gpgme_import_result_t and gpgme_import_status_t objects.
732 Thus, the gpgme_op_import_ext variant is deprecated.
734 * The new gpgme_op_sign_result function provides detailed information
735 about the result of a signing operation in gpgme_sign_result_t,
736 gpgme_invalid_key_t and gpgme_new_signature_t objects.
738 * The new gpgme_op_encrypt_result function provides detailed
739 information about the result of an encryption operation in
740 a GpgmeEncryptResult object.
742 * The new gpgme_op_decrypt_result function provides detailed
743 information about the result of a decryption operation in
744 a GpgmeDecryptResult object.
746 * The new gpgme_op_verify_result function provides detailed
747 information about the result of an verify operation in
748 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
749 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
750 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
751 and gpgme_get_notation is removed.
753 * GpgmeTrustItem objects have now directly accessible data, so the
754 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
755 accessor functions are deprecated. Also, reference counting is
756 available through gpgme_trust_item_ref and gpgme_trust_item_unref
757 (the gpgme_trust_item_release alias for the latter is deprecated).
759 * Keys are not cached internally anymore, so the force_update argument
760 to gpgme_get_key has been removed.
762 * GpgmeKey objects have now directly accessible data so the
763 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
764 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
765 functions are deprecated. Also, gpgme_key_release is now
766 deprecated. The gpgme_key_get_as_xml function has been dropped.
768 * Because all interfaces using attributes are deprecated, the
769 GpgmeAttr data type is also deprecated.
771 * The new gpgme_op_keylist_result function provides detailed
772 information about the result of a key listing operation in
773 a GpgmeKeyListResult object.
775 * Now that each function comes with its own result retrieval
776 interface, the generic gpgme_get_op_info interface is not useful
779 * The type and mode of data objects is not available anymore.
781 * Interface changes relative to the 0.4.0 release:
782 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
783 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
784 GpgmeData DEPRECATED: Use gpgme_data_t.
785 GpgmeError DEPRECATED: Use gpgme_error_t.
786 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
787 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
788 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
789 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
790 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
791 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
792 GpgmeKey DEPRECATED: Use gpgme_key_t.
793 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
794 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
795 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
796 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
797 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
798 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
799 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
800 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
801 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
802 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
803 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
804 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
805 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
806 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
807 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
810 gpgme_recipients_t NEW
812 gpgme_data_encoding_t NEW
819 gpgme_passphrase_cb_t NEW
820 gpgme_progress_cb_t NEW
822 gpgme_register_io_cb_t NEW
823 gpgme_remove_io_cb_t NEW
825 gpgme_event_io_cb_t NEW
827 gpgme_data_read_cb_t NEW
828 gpgme_data_write_cb_t NEW
829 gpgme_data_seek_cb_t NEW
830 gpgme_data_release_cb_t NEW
832 gpgme_trust_item_t NEW
833 gpgme_status_code_t NEW
834 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
836 gpgme_err_source_t NEW
841 gpgme_error_from_errno NEW
842 gpgme_err_make_from_errno NEW
843 gpgme_err_code_from_errno NEW
844 gpgme_err_code_to_errno NEW
846 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
847 gpgme_event_io_t CHANGED: New event type (all numbers changed).
848 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
849 gpgme_edit_cb_t CHANGED: Write directly to FD.
850 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
851 gpgme_op_verify CHANGED: Drop R_STAT argument.
852 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
853 gpgme_wait CHANGED: Can return NULL even if hang is true.
854 GpgmeIdleFunc REMOVED
855 gpgme_register_idle REMOVED
856 GpgmeRecipients REMOVED
857 gpgme_recipients_new REMOVED
858 gpgme_recipients_release REMOVED
859 gpgme_recipients_add_name REMOVED
860 gpgme_recipients_add_name_with_validity REMOVED
861 gpgme_recipients_count REMOVED
862 gpgme_recipients_enum_open REMOVED
863 gpgme_recipients_enum_read REMOVED
864 gpgme_recipients_enum_close REMOVED
865 gpgme_encrypt_flags_t NEW
866 GPGME_ENCRYPT_ALWAYS_TRUST NEW
867 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
868 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
869 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
870 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
871 gpgme_op_export_start CHANGED: User IDs passed as patterns.
872 gpgme_op_export CHANGED: User IDs passed as patterns.
873 gpgme_op_export_ext_start NEW
874 gpgme_op_export_ext NEW
875 gpgme_keylist_mode_t NEW
877 gpgme_engine_info_t NEW
878 gpgme_get_engine_info CHANGED: Return info structure instead XML.
879 gpgme_get_protocol_name NEW
880 gpgme_cancel REMOVED: Return error in callback directly.
881 gpgme_op_genkey CHANGED: FPR argument dropped.
882 gpgme_op_genkey_result NEW
883 gpgme_genkey_result_t NEW
884 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
885 gpgme_op_import_result NEW
886 gpgme_import_status_t NEW
887 gpgme_import_result_t NEW
888 gpgme_pubkey_algo_t NEW
889 gpgme_hash_algo_t NEW
890 gpgme_invalid_key_t NEW
891 gpgme_new_signature_t NEW
892 gpgme_sign_result_t NEW
893 gpgme_op_sign_result NEW
894 gpgme_pubkey_algo_name NEW
895 gpgme_hash_algo_name NEW
896 gpgme_encrypt_result_t NEW
897 gpgme_op_encrypt_result NEW
898 gpgme_decrypt_result_t NEW
899 gpgme_op_decrypt_result NEW
900 gpgme_verify_result_t NEW
901 gpgme_op_verify_result NEW
902 gpgme_get_notation REMOVED: Access verify result directly instead.
903 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
904 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
905 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
906 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
907 gpgme_get_sig_status DEPRECATED: Use verify result directly.
908 gpgme_trust_item_t CHANGED: Now has user accessible data members.
909 gpgme_trust_item_ref NEW
910 gpgme_trust_item_unref NEW
911 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
912 gpgme_trust_item_get_string_attr DEPRECATED
913 gpgme_trust_item_get_ulong_attr DEPRECATED
914 gpgme_get_key CHANGED: Removed force_update argument.
918 gpgme_key_t CHANGED: Now has user accessible data members.
919 gpgme_key_get_string_attr DEPRECATED
920 gpgme_key_get_ulong_attr DEPRECATED
921 gpgme_key_sig_get_string_attr DEPRECATED
922 gpgme_key_sig_get_ulong_attr DEPRECATED
923 gpgme_key_get_as_xml REMOVED
924 gpgme_key_list_result_t NEW
925 gpgme_op_keylist_result NEW
926 gpgme_get_op_info REMOVED
927 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
929 Noteworthy changes in version 0.4.0 (2002-12-23)
930 ------------------------------------------------
932 * Key generation returns the fingerprint of the generated key.
934 * New convenience function gpgme_get_key.
936 * Supports signatures of user IDs in keys via the new
937 GPGME_KEYLIST_MODE_SIGS keylist mode and the
938 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
939 interfaces. The XML info about a key also includes the signatures
942 * New data object interface, which is more flexible and transparent.
944 * Interface changes relative to the 0.3.9 release:
945 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
949 GpgmeDataReleaseCb NEW
951 gpgme_data_read CHANGED: Match read() closely.
952 gpgme_data_write CHANGED: Match write() closely.
954 gpgme_data_new_from_fd NEW
955 gpgme_data_new_from_stream NEW
956 gpgme_data_new_from_cbs NEW
957 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
958 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
959 gpgme_data_get_type REMOVED: No replacement.
960 gpgme_op_verify CHANGED: Take different data objects for
961 signed text and plain text.
962 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
963 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
964 gpgme_op_genkey CHANGED: New parameter FPR.
965 GPGME_KEYLIST_MODE_SIGS NEW
966 gpgme_key_sig_get_string_attr NEW
967 gpgme_key_sig_get_ulong_attr NEW
969 GPGME_ATTR_SIG_CLASS NEW
970 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
972 Noteworthy changes in version 0.3.16 (2003-11-19)
973 -------------------------------------------------
975 * Compatibility fixes for GnuPG 1.9.x
977 Noteworthy changes in version 0.3.15 (2003-02-18)
978 -------------------------------------------------
980 * The progress status is sent via the progress callbacks in
983 * Bug fix for signing operations with explicit signer settings for
986 Noteworthy changes in version 0.3.14 (2002-12-04)
987 -------------------------------------------------
989 * GPGME-Plug is now in its own package "cryptplug".
991 * Workaround for a setlocale problem. Fixed a segv related to not
992 correctly as closed marked file descriptors.
994 Noteworthy changes in version 0.3.13 (2002-11-20)
995 -------------------------------------------------
997 * Release due to changes in gpgmeplug.
999 Noteworthy changes in version 0.3.12 (2002-10-15)
1000 -------------------------------------------------
1002 * Fixed some bux with key listings.
1004 * The development has been branched to clean up some API issues.
1005 This 0.3 series will be kept for compatibility reasons; so do don't
1006 expect new features.
1008 Noteworthy changes in version 0.3.11 (2002-09-20)
1009 -------------------------------------------------
1013 Noteworthy changes in version 0.3.10 (2002-09-02)
1014 -------------------------------------------------
1016 * Setting the signing keys for the CMS protocol does now work.
1018 * The signers setting is honoured by gpgme_op_edit.
1020 Noteworthy changes in version 0.3.9 (2002-08-21)
1021 ------------------------------------------------
1023 * A spec file for creating RPMs has been added.
1025 * An experimental interface to GnuPG's --edit-key functionality is
1026 introduced, see gpgme_op_edit.
1028 * The new gpgme_import_ext function provides a convenient access to
1029 the number of processed keys.
1031 * Interface changes relative to the 0.3.8 release:
1032 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1035 gpgme_op_edit_start NEW
1037 gpgme_op_import_ext NEW
1038 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1040 Noteworthy changes in version 0.3.8 (2002-06-25)
1041 ------------------------------------------------
1043 * It is possible to use an outside event loop for the I/O to the
1044 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1046 * Interface changes relative to the 0.3.6 release:
1047 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1049 GpgmeRegisterIOCb NEW
1053 struct GpgmeIOCbs NEW
1054 gpgme_set_io_cbs NEW
1055 gpgme_get_io_cbs NEW
1056 GPGME_ATTR_ERRTOK NEW
1057 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1059 Noteworthy changes in version 0.3.7 (2002-06-04)
1060 ------------------------------------------------
1062 * GPGME_ATTR_OTRUST is implemented now.
1064 * A first step toward thread safeness has been achieved, see the
1065 documentation for details. Supported thread libraries are pthread
1068 Noteworthy changes in version 0.3.6 (2002-05-03)
1069 ------------------------------------------------
1071 * All error output of the gpgsm backend is send to the bit bucket.
1073 * The signature verification functions are extended. Instead of
1074 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1075 expired signatures. 2 new functions may be used to retrieve more
1076 detailed information like the signature expiration time and a
1077 validity information of the key without an extra key looking.
1079 * The current passphrase callback and progress meter callback can be
1080 retrieved with the new functions gpgme_get_passphrase_cb and
1081 gpgme_get_progress_cb respectively.
1083 * Interface changes relative to the 0.3.5 release:
1084 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1085 gpgme_get_passphrase_cb NEW
1086 gpgme_get_progress_cb NEW
1087 GpgmeDataEncoding NEW
1088 gpgme_data_set_encoding NEW
1089 gpgme_data_get_encoding NEW
1090 GPGME_SIG_STAT_GOOD_EXP NEW
1091 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1092 gpgme_op_verify CHANGED: Returns more status codes.
1093 GPGME_ATTR_SIG_STATUS NEW
1094 gpgme_get_sig_string_attr NEW
1095 gpgme_get_sig_ulong_attr NEW
1096 gpgme_get_protocol NEW
1097 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1099 Noteworthy changes in version 0.3.5 (2002-04-01)
1100 ------------------------------------------------
1102 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1103 case, symmetric encryption is performed. Note that this requires a
1104 passphrase from the user.
1106 * More information is returned for X.509 certificates.
1108 * Interface changes relative to the 0.3.4 release:
1109 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1110 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1111 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1113 Noteworthy changes in version 0.3.4 (2002-03-04)
1114 ------------------------------------------------
1116 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1117 some recipients have been invalid, whereas earlier versions
1118 succeeded in this case. The plaintext is still encrypted for all valid
1119 recipients, so the application might take this error as a hint that
1120 the ciphertext is not usable for all requested recipients.
1121 Information about invalid recipients is available with gpgme_get_op_info.
1123 * gpgme_op_verify now allows to pass an uninitialized data object as
1124 its plaintext argument to check for normal and cleartext
1125 signatures. The plaintext is then returned in the data object.
1127 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1128 to set and get the number of certifications to include in S/MIME
1131 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1132 to encrypt and sign a message in a combined operation.
1134 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1136 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1138 * Interface changes relative to the 0.3.3 release:
1139 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1140 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1141 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1142 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1143 gpgme_set_include_certs NEW
1144 gpgme_get_include_certs NEW
1145 gpgme_op_encrypt_sign NEW
1146 gpgme_op_encrypt_sign_start NEW
1147 gpgme_op_keylist_ext_start NEW
1148 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1150 Noteworthy changes in version 0.3.3 (2002-02-12)
1151 ------------------------------------------------
1153 * Fix the Makefile in jnlib.
1155 * Fix the test suite (hopefully). It should clean up all its state
1156 with `make check' now.
1159 Noteworthy changes in version 0.3.2 (2002-02-10)
1160 ------------------------------------------------
1162 * Remove erroneous dependency on libgcrypt in jnlib.
1165 Noteworthy changes in version 0.3.1 (2002-02-09)
1166 ------------------------------------------------
1168 * There is a Texinfo manual documenting the API.
1170 * The gpgme_set_keylist_mode function returns an error, and changed
1171 its meaning. It is no longer usable to select between normal and
1172 fast mode (newer versions of GnuPG will always be fast), but
1173 selects between local keyring, remote keyserver, or both.
1174 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1175 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1176 current setting, a fucntion gpgme_get_keylist_mode was added to
1177 retrieve the current mode.
1179 * gpgme_wait accepts a new argument STATUS to return the error status
1180 of the operation on the context. Its definition is closer to
1181 waitpid() now than before.
1183 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1184 type from off_t to the unsigned size_t.
1186 * The R_HD argument to the GpgmePassphraseCb type changed its type
1187 from void* to void**.
1189 * New interface gpgme_op_trustlist_end() to match
1190 gpgme_op_keylist_end().
1192 * The CryptPlug modules have been renamed to gpgme-openpgp and
1193 gpgme-smime, and they are installed in pkglibdir by `make install'.
1195 * An idle function can be registered with gpgme_register_idle().
1197 * The GpgSM backend supports key generation with gpgme_op_genkey().
1199 * Interface changes relative to the 0.3.0 release:
1200 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1201 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1202 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1203 gpgme_wait CHANGED: New argument STATUS.
1204 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1205 The function has a new meaning!
1206 gpgme_get_keylist_mode NEW
1207 GPGME_KEYLIST_MODE_LOCAL NEW
1208 GPGME_KEYLIST_MODE_EXTERN NEW
1209 gpgme_op_trustlist_next NEW
1211 gpgme_register_idle NEW
1212 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1214 Noteworthy changes in version 0.3.0 (2001-12-19)
1215 ------------------------------------------------
1217 * New interface gpgme_set_protocol() to set the protocol and thus the
1218 crypto engine to be used by the context. Currently, the OpenPGP
1219 and the CMS protocols are supported. They are specified by the new
1220 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1221 A new context uses the OpenPGP engine by default.
1223 * gpgme_get_engine_info() returns information for all crypto engines
1224 compiled into the library. The XML format has changed. To
1225 reliably get the version of a crypto engine, the <version> tag
1226 after the appropriate <protocol> tag has to be looked for.
1228 * New interface gpgme_engine_check_version(), obsoleting
1229 gpgme_check_engine(). Check the version of all engines you are
1230 supporting in your software.
1232 * GpgmeKey lists the user ids in the order as they are returned by
1233 GnuPG, first the primary key with index 0, then the sub-user ids.
1235 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1236 signatures simultaneously.
1238 * The new interface gpgme_op_keylist_end() terminates a pending
1239 keylist operation. A keylist operation is also terminated when
1240 gpgme_op_keylist_next() returns GPGME_EOF.
1242 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1243 cross-compiled, or even compiled without support for GnuPG
1246 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1247 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1248 in the path, but it can also be compiled without support for GpgSM
1249 (`--without-gpgsm').
1251 * CryptPlug modules for GPGME are included and can be enabled at
1252 configure time (`--enable-gpgmeplug'). There is one module which
1253 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1254 GpgSM engine (`gpgsmplug').
1256 * Interface changes relative to the latest 0.2.x release:
1257 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1258 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1259 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1260 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1261 gpgme_get_engine_info CHANGED: New format, extended content.
1262 gpgme_engine_check_version NEW
1263 gpgme_decrypt_verify_start NEW
1264 gpgme_decrypt_verify NEW
1265 gpgme_op_keylist_next NEW
1266 gpgme_set_protocol NEW
1267 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1270 Noteworthy changes in version 0.2.3 (2001-09-17)
1271 ------------------------------------------------
1273 * New function gpgme_get_op_info which can be used to get the micalg
1274 parameter needed for MOSS.
1276 * New functions gpgme_get_armor and gpgme_get_textmode.
1278 * The usual bug fixes and some minor functionality improvements.
1280 * Added a simple encryption component for MS-Windows; however the
1281 build procedure might have some problems.
1284 Noteworthy changes in version 0.2.2 (2001-06-12)
1285 ------------------------------------------------
1287 * Implemented a key cache.
1289 * Fixed a race condition under W32 and some other bug fixes.
1292 Noteworthy changes in version 0.2.1 (2001-04-02)
1293 ------------------------------------------------
1295 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1297 * Handle GnuPG's new key capabilities output and support revocation
1300 * Made the W32 support more robust.
1303 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008 g10 Code GmbH
1305 This file is free software; as a special exception the author gives
1306 unlimited permission to copy and/or distribute it, with or without
1307 modifications, as long as this notice is preserved.
1309 This file is distributed in the hope that it will be useful, but
1310 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1311 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.