1 Noteworthy changes in version 1.1.3 (unreleased)
2 ------------------------------------------------
4 * Interface changes relative to the 1.1.1 release:
5 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9 Noteworthy changes in version 1.1.2 (2006-03-02)
10 ------------------------------------------------
12 * Fixed a bug in the W32 glib backend.
15 Noteworthy changes in version 1.1.1 (2006-02-23)
16 ------------------------------------------------
18 * Fixed a bug in that the fingerprints of subkeys are not available.
20 * Clarified usage of the SECRET flag in key listings. It is now
23 * Reading signature notations and policy URLs on key signatures is
24 supported. They can be found in the new field notations of the
25 gpgme_key_sig_t structure. This has to be enabled with the keylist
26 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
28 * A new gpgme_free() function solves the problem of using different
29 allocators in a single program. This function should now be used
30 instead calling free() to release the buffer returned by
31 gpgme_data_release_and_get_mem. It is recommended that you always
32 do this, but it is only necessary on certain platforms, so backwards
33 compatibility is provided. In other words: If free() worked for
34 you before, it will keep working.
36 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
37 They are analyzed by the verify handlers and made available in the
38 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
40 * Interface changes relative to the 1.1.0 release:
41 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
42 gpgme_key_sig_t EXTENDED: New field notations.
43 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
45 GPGME_STATUS_PKA_TRUST_BAD NEW
46 GPGME_STATUS_PKA_TRUST_GOOD NEW
47 gpgme_signature_t EXTENDED: New field pka_trust.
48 gpgme_signature_t EXTENDED: New field pka_address.
49 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
52 Noteworthy changes in version 1.1.0 (2005-10-01)
53 ------------------------------------------------
55 * You can now configure the backend engine file name and home
56 directory to be used, as default and per context.
58 * Information about the recipients of an encrypted text is now
59 available at decryption time.
61 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
62 and verify handlers, the information about the plaintext filename,
63 if available is made available in the new field file_name of the
64 respective result structure.
66 * The code for "automagically detecting the thread library" has been
67 removed from libgpgme. It is deprecated since version 0.4.3.
68 Since then, you had to link against libgpgme-pthread for
69 applications using pthread and libgpgme-pth for applications using
72 The code was removed because it caused compilation problems on
73 systems where the pthread.h header from GNU Pth is available in
74 addition to the system header (FreeBSD 6 and later for example).
76 * "./autogen.sh --build-w32" does now build gpgme.dll.
78 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
79 delimiter. The standard install directory is used when locating
80 gpg or gpgsm before finally falling back to the hardwired name.
82 * There is a new flag for keys and subkeys, is_qualified, which
83 indicates if a key can be used for qualified signatures according
84 to local government regulations.
86 * You can associate a filename with a data object using the new
87 function gpgme_data_set_file_name(). This filename will be stored
88 in the output when encrypting or signing the data and will be
89 returned when decrypting or verifying the output data.
91 * You can now set notation data at signature creation with the new
92 function gpgme_sig_notation_add().
94 * Interface changes relative to the 1.0.3 release:
95 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
96 gpgme_set_engine_info NEW
97 gpgme_ctx_get_engine_info NEW
98 gpgme_ctx_set_engine_info NEW
100 gpgme_decrypt_result_t EXTENDED: New field recipients.
101 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
102 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
103 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
104 GPGME_STATUS_PLAINTEXT NEW
105 gpgme_key_t EXTENDED: New field is_qualified.
106 gpgme_subkey_t EXTENDED: New field is_qualified.
107 gpgme_data_get_file_name NEW
108 gpgme_data_set_file_name NEW
109 gpgme_sig_notation_flags_t NEW
110 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
111 GPGME_SIG_NOTATAION_CRITICAL NEW
112 gpgme_sig_notation_clear NEW
113 gpgme_sig_notation_add NEW
114 gpgme_sig_notation_get NEW
115 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
118 Noteworthy changes in version 1.0.3 (2005-06-20)
119 ------------------------------------------------
121 * Previousy, GPGME would use a default "include certs" of 1. This
122 has been changed. Now GPGME will use the crypto backend engines
123 default unless you set the value with gpgme_set_include_certs()
124 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
125 as a value to explicitely request the new default behaviour.
127 Because the default changes, this is a slight change of the API
128 semantics. We consider it to be a bug fix.
130 * A bug which made GPGME hang has been fixed. If you have
131 experienced hanging before, please try out this version and let me
132 know if you still experience hanging problems.
134 * Interface changes relative to the 0.9.0 release:
135 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
136 gpgme_set_include_certs CHANGED DEFAULT
137 GPGME_INCLUDE_CERTS_DEFAULT NEW
138 GPGME_STATUS_SIG_SUBPACKET NEW
139 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
140 GPGME_STATUS_SC_OP_FAILURE NEW
141 GPGME_STATUS_SC_OP_SUCCESS NEW
142 GPGME_STATUS_CARDCTRL NEW
143 GPGME_STATUS_BACKUP_KEY_CREATED NEW
144 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
147 Noteworthy changes in version 1.0.2 (2004-12-28)
148 ------------------------------------------------
150 * Changed the license of the library to the GNU Lesser General Public
151 License (LGPL), version 2.1 or later.
154 Noteworthy changes in version 1.0.1 (2004-10-22)
155 ------------------------------------------------
160 Noteworthy changes in version 1.0.0 (2004-09-30)
161 ------------------------------------------------
163 * Version 1.0.0! We are proud to present you with a thoroughly
164 tested and stable version of the GPGME library. A big Thank You!
165 to all the people who made this possible.
167 The development will be branched into a stable 1.x.y series and the
170 * The gpgme.m4 macro supports checking the API version. Just prepend
171 it to the required version string, separated by a colon. For
172 example, this release has the version "1:1.0.0". The last release
173 to which this version is (mostly) ABI compatible is "1:0.4.2",
174 which is the default required version.
177 Noteworthy changes in version 0.9.0 (2004-06-08)
178 ------------------------------------------------
180 * The type gpgme_key_t has now a new field keylist_mode that contains
181 the keylist mode that was active at the time the key was retrieved.
183 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
184 that contains a flag indicating that the key should not have been
187 * Verifying a signature of a revoked key gives the correct result now
188 (GPG_ERR_CERT_REVOKED error code).
190 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
191 verify operations still allows you to look at the signature
194 * Clarified that patterns in keylisting operations have an upper
195 limit, and thus are not suited to list many keys at once by their
196 fingerprint. Also improve the error message if the pattern is too
197 long for the CMS protocol to handle.
199 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
200 gpgme_key_t EXTENDED: New field keylist_mode.
201 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
205 Noteworthy changes in version 0.4.7 (2004-04-29)
206 ------------------------------------------------
208 * Correctly initialize the fields expired, revoked, invalid, and
209 disabled in the gpgme_key_t structures.
211 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
212 accidently of type int instead unsigned int.
214 * Interface changes relative to the 0.4.5 release:
215 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
216 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
217 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
219 Noteworthy changes in version 0.4.6 (2004-04-06)
220 ------------------------------------------------
225 Noteworthy changes in version 0.4.5 (2004-03-07)
226 ------------------------------------------------
228 * GPGME is now compiled with LFS (large file support) by default.
229 This means that _all_ programs using GPGME must be compiled with
230 LFS support enabled by default. You can do this easily with
231 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
232 without autoconf by defining the preprocessor symbol
233 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
234 the C compiler command line, or by defining this preprocessor
235 symbol before including any system header files). For more
236 details, read the section on LFS in the manual.
238 Up to now, it was undocumented that GPGME was not using LFS.
239 But the public interfaces use off_t, and file descriptors are
240 exchanged between the application and GPGME. This was an oversight,
241 and bound to cause troubles in the future.
243 Writing GPGME as a dual mode library that seamlessly supports LFS
244 while keeping backwards compatibility is possible, but does not
245 solve the problem: Many applications already expect GPGME to have
246 LFS (they are compiled with off_t being a 64bit value). This is true
247 in particular for the popular Gtk+ and Qt programs.
249 So, although this is an ABI (but not an API) break, we will not
250 change the library version to reflect that. Because the interfaces
251 affected are probably not used yet in any GPGME 0.4 based
252 application, we don't expect any real failures from this change.
253 In fact, applications already using LFS will have some subtle bugs
256 However, if you encounter an application using GPGME 0.4.x that
257 does _not_ use LFS by default (off_t is a 32bit value), _and_
258 uses at least one of the functions gpgme_data_seek,
259 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
260 gpgme_data_new_from_cbs, then indeed this library will be ABI
261 incompatible with the program. As said above, we don't believe
262 such a program exists. If we are in error, then you have two
263 options: As a quick hack, you can configure GPGME with the
264 --disable-largefile option. This will revert the change, and GPGME
265 will not use LFS. However, GPGME will be incompatible with
266 programs that expect GPGME to use LFS. All applications are
267 required to use LFS when using GPGME, so this is only good as a
268 temporary local work-around.
270 The other option is to change the versioning of the library and
271 recompile all applications. We have reserved a special version of
272 the library for that, so you can do that without expecting a
273 version clash in the future. Furthermore, everyone who does this
274 will agree on the version to use (this is important for
275 distribution makers). Read the comment in configure.ac (before
276 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
277 blindly: As stated above, we think it is unlikely this measure is
278 needed. Still, it is there if necessary. If in doubt, contact us
279 and we will give our advise for your specific situation.
281 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
284 * New interface gpgme_cancel() that can be used to cancel
285 asynchronous operations.
287 * Interface changes relative to the 0.4.4 release:
288 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
289 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
290 gpgme_data_seek CHANGED: off_t is now a largefile type.
291 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
292 GPGME_KEYLIST_MODE_VALIDATE NEW
294 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
296 Noteworthy changes in version 0.4.4 (2004-01-12)
297 ------------------------------------------------
299 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
300 been renamed to "sig_class", to avoid clash with C++ compilers. In
301 the C API, the old name "class" has been preserved for backwards
302 compatibility, but is deprecated.
304 * Interface changes relative to the 0.4.3 release:
305 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
306 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
307 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
308 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
310 Noteworthy changes in version 0.4.3 (2003-10-06)
311 ------------------------------------------------
313 * libgpgme should not be used for threaded programs anymore. This
314 never worked reliably in all cases, because you had to
315 be careful about the linking order and libtool wouldn't do that for
316 you automatically. Instead, now you have to link against
317 libgpgme-pthread for applications using pthread and libgpgme-pth for
318 applications using GNU Pth.
320 The old code for automagically detecting the thread library is
321 still part of libgpgme, but it is DEPRECATED.
323 * There are new automake macros AM_PATH_GPGME_PTH and
324 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
325 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
326 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
327 variables of course also include the configuration for the thread
328 package itself. Alternatively, use libtool.
330 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
333 * gpgme-config doesn't support setting the prefix or exec prefix
334 anymore. I don't think it ever worked correctly, and it seems to
337 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
338 provided was not unique, instead returning the first matching key.
340 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
341 that indicates if the key can be used for authentication.
343 * gpgme_signature_t's status field is now correctly set to an error
344 with error code GPG_ERR_NO_PUBKEY if public key is not found.
346 * gpgme_new_signature_t's class field is now an unsigned int, rather
347 than an unsigned long (the old class field is preserved for
348 backwards compatibility).
350 * A new function gpgme_set_locale() is provided to allow configuring
351 the locale for the crypto backend. This is necessary for text
352 terminals so that programs like the pinentry can be started with
353 the right locale settings for the terminal the application is running
354 on, in case the terminal has different settings than the system
355 default (for example, if it is a remote terminal). You are highly
356 recommended to call the following functions directly after
361 setlocale (LC_ALL, "");
362 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
363 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
365 GPGME can not do this for you, as setlocale is not thread safe, and
366 there is no alternative.
368 * The signal action for SIGPIPE is now set to SIG_IGN by
369 gpgme_check_version, instead the first time a crypto engine is
370 started (which is not well defined).
372 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
373 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
374 to CRC24RFC2440. For now, these strings can be used as the MIC
375 parameter for PGP/MIME (if appropriately modified).
377 * Interface changes relative to the 0.4.2 release:
378 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
380 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
381 gpgme_key_t EXTENDED: New field can_authenticate.
382 gpgme_subkey_t EXTENDED: New field can_authenticate.
383 gpgme_new_signature_t CHANGED: New type for class field.
385 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
386 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
388 Noteworthy changes in version 0.4.2 (2003-07-30)
389 ------------------------------------------------
391 * Allow gpg-error to be in non-standard place when linking the test suite.
393 * Configure will fail now if gpg-error can not be found.
395 * Fixed initialized memory backed data objects for writing, which
396 caused the test program to crash (but only on Mac OS, surprisingly).
398 * Eliminate use of C99 constructs.
400 * Small improvements to the manual.
403 Noteworthy changes in version 0.4.1 (2003-06-06)
404 ------------------------------------------------
406 This is the release that 0.4.0 should have been. There are many
407 interface changes, please see below for the details. The changes are
408 sometimes the result of new functionality, but more often express a
409 paradigm shift. Others are an overdue cleanup to get GPGME in line
410 with the GNU coding standards and to make the interface more
411 self-consistent. Here is an overview on the changes:
413 All types have been renamed to conform to the GNU coding standards,
414 most of the time by keeping the whole name in lowercase and inserting
415 underscores between words.
417 All operations consistently only accept input parameters in their
418 invocation function, and return only an error code directly. Further
419 information about the result of the operation has to be retrieved
420 afterwards by calling one of the result functions. This unifies the
421 synchronous and the asynchronous interface.
423 The error values have been completely replaced by a more
424 sophisticated model that allows GPGME to transparently and accurately
425 report all errors from the other GnuPG components, irregardless of
426 process boundaries. This is achieved by using the library
427 libgpg-errors, which is shared by all GnuPG components. This library
428 is now required for GPGME.
430 The results of all operations are now provided by pointers to C
431 structs rather than by XML structs or in other ways.
433 Objects which used to be opaque (for example a key) are now pointers
434 to accessible structs, so no accessor functions are necessary.
436 Backward compatibility is provided where it was possible without too
437 much effort and did not collide with the overall sanitization effort.
438 However, this is only for ease of transition. NO DEPRECATED FUNCTION
439 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
440 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
441 Recommendations how to replace deprecated or removed functionality
442 can be found within the description of each change.
444 What follows are all changes to the interface and behaviour of GPGME
447 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
448 deprecated attributes will warn about use of obsolete functions and
449 type definitions. You can suppress these warnings by passing
450 -Wno-deprecated-declarations to the gcc command.
452 * The following types have been renamed. The old types are still
453 available as aliases, but they are deprecated now:
456 GpgmeData gpgme_data_t
457 GpgmeError gpgme_error_t
458 GpgmeDataEncoding gpgme_data_encoding_t
459 GpgmeSigStat gpgme_sig_stat_t
460 GpgmeSigMode gpgme_sig_mode_t
461 GpgmeAttr gpgme_attr_t
462 GpgmeValidity gpgme_validity_t
463 GpgmeProtocol gpgme_protocol_t
465 GpgmePassphraseCb gpgme_passphrase_cb_t
466 GpgmeProgressCb gpgme_progress_cb_t
467 GpgmeIOCb gpgme_io_cb_t
468 GpgmeRegisterIOCb gpgme_register_io_cb_t
469 GpgmeRemoveIOCb gpgme_remove_io_cb_t
470 GpgmeEventIO gpgme_event_io_t
471 GpgmeEventIOCb gpgme_event_io_cb_t
472 GpgmeIOCbs gpgme_io_cbs
473 GpgmeDataReadCb gpgme_data_read_cb_t
474 GpgmeDataWriteCb gpgme_data_write_cb_t
475 GpgmeDataSeekCb gpgme_data_seek_cb_t
476 GpgmeDataReleaseCb gpgme_data_release_cb_t
477 GpgmeDataCbs gpgme_data_cbs_t
478 GpgmeTrustItem gpgme_trust_item_t
479 GpgmeStatusCode gpgme_status_code_t
481 * gpgme_error_t is now identical to gpg_error_t, the error type
482 provided by libgpg-error. More about using libgpg-error with GPGME
483 can be found in the manual. All error symbols have been removed!
485 * All functions and types in libgpg-error have been wrapped in GPGME.
486 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
487 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
488 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
489 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
492 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
494 * GnuPG 1.2.2 is required. The progress callback is now also invoked
495 for encrypt, sign, encrypt-sign, decrypt, verify, and
496 decrypt-verify operations. For verify operations on detached
497 signatures, the progress callback is invoked for both the detached
498 signature and the plaintext message, though.
500 * gpgme_passphrase_cb_t has been changed to not provide a complete
501 description, but the UID hint, passphrase info and a flag
502 indicating if this is a repeated attempt individually, so the user
503 can compose his own description from this information.
505 The passphrase is not returned as a C string, but must be written
506 to a file descriptor directly. This allows for secure passphrase
509 The return type has been changed to gpgme_error_t value. This
510 allowed to remove the gpgme_cancel function; just return
511 the error code GPG_ERR_CANCELED in the passphrase callback directly.
513 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
514 The user is expected to write the response to the file descriptor,
515 followed by a newline.
517 * The recipients interface has been removed. Instead, you use
518 NULL-terminated lists of keys for specifying the recipients of an
519 encryption operation. Use the new encryption flag
520 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
521 the keys (but note that in general this is not a good idea).
523 This change has been made to the prototypes of gpgme_op_encrypt,
524 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
525 gpgme_op_encrypt_sign_start.
527 The export interface has been changed to use pattern strings like
528 the keylist interface. Thus, new functions gpgme_op_export_ext and
529 gpgme_op_export_ext_start have been added as well. Now the
530 prototypes of gpgme_op_export_start and gpgme_op_export finally
533 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
534 summary anymore. Use gpgme_get_sig_status to retrieve the individual
537 * gpgme_io_cb_t changed from a void function to a function returning
538 a gpgme_error_t value. However, it will always return 0, so you
539 can safely ignore the return value.
541 * A new I/O callback event GPGME_EVENT_START has been added. The new
542 requirement is that you must wait until this event until you are
543 allowed to call the I/O callback handlers previously registered for
544 this context operation. Calling I/O callback functions for this
545 context operation before the start event happened is unsafe because
546 it can lead to race conditions in a multi-threaded environment.
548 * The idle function feature has been removed. It was not precisely
549 defined in a multi-threaded environment and is obsoleted by the
550 user I/O callback functions. If you still need a simple way to
551 call something while waiting on one or multiple asynchronous
552 operations to complete, don't set the HANG flag in gpgme_wait (note
553 that this will return to your program more often than the idle
556 * gpgme_wait can return NULL even if hang is true, if an error
557 occurs. In that case *status contains the error code.
559 * gpgme_get_engine_info was radically changed. Instead an XML
560 string, an info structure of the new type gpgme_engine_info_t is
561 returned. This makes it easier and more robust to evaluate the
562 information in an application.
564 * The new function gpgme_get_protocol_name can be used to convert a
565 gpgme_protocol_t value into a string.
567 * The status of a context operation is not checked anymore. Starting
568 a new operation will silently cancel the previous one. Calling a
569 function that requires you to have started an operation before without
570 doing so is undefined.
572 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
573 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
574 pointer to a structure which contains the fingerprint. This also
575 works with gpgme_op_genkey_start. The structure also provides
576 other information about the generated keys.
581 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
583 printf ("%s\n", fpr);
587 gpgme_genkey_result_t result;
588 err = gpgme_op_genkey (ctx, NULL, NULL);
591 result = gpgme_op_genkey_result (ctx);
593 printf ("%s\n", result->fpr);
596 * The new gpgme_op_import_result function provides detailed
597 information about the result of an import operation in
598 gpgme_import_result_t and gpgme_import_status_t objects.
599 Thus, the gpgme_op_import_ext variant is deprecated.
601 * The new gpgme_op_sign_result function provides detailed information
602 about the result of a signing operation in gpgme_sign_result_t,
603 gpgme_invalid_key_t and gpgme_new_signature_t objects.
605 * The new gpgme_op_encrypt_result function provides detailed
606 information about the result of an encryption operation in
607 a GpgmeEncryptResult object.
609 * The new gpgme_op_decrypt_result function provides detailed
610 information about the result of a decryption operation in
611 a GpgmeDecryptResult object.
613 * The new gpgme_op_verify_result function provides detailed
614 information about the result of an verify operation in
615 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
616 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
617 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
618 and gpgme_get_notation is removed.
620 * GpgmeTrustItem objects have now directly accessible data, so the
621 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
622 accessor functions are deprecated. Also, reference counting is
623 available through gpgme_trust_item_ref and gpgme_trust_item_unref
624 (the gpgme_trust_item_release alias for the latter is deprecated).
626 * Keys are not cached internally anymore, so the force_update argument
627 to gpgme_get_key has been removed.
629 * GpgmeKey objects have now directly accessible data so the
630 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
631 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
632 functions are deprecated. Also, gpgme_key_release is now
633 deprecated. The gpgme_key_get_as_xml function has been dropped.
635 * Because all interfaces using attributes are deprecated, the
636 GpgmeAttr data type is also deprecated.
638 * The new gpgme_op_keylist_result function provides detailed
639 information about the result of a key listing operation in
640 a GpgmeKeyListResult object.
642 * Now that each function comes with its own result retrieval
643 interface, the generic gpgme_get_op_info interface is not useful
646 * The type and mode of data objects is not available anymore.
648 * Interface changes relative to the 0.4.0 release:
649 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
650 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
651 GpgmeData DEPRECATED: Use gpgme_data_t.
652 GpgmeError DEPRECATED: Use gpgme_error_t.
653 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
654 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
655 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
656 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
657 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
658 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
659 GpgmeKey DEPRECATED: Use gpgme_key_t.
660 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
661 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
662 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
663 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
664 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
665 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
666 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
667 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
668 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
669 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
670 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
671 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
672 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
673 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
674 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
677 gpgme_recipients_t NEW
679 gpgme_data_encoding_t NEW
686 gpgme_passphrase_cb_t NEW
687 gpgme_progress_cb_t NEW
689 gpgme_register_io_cb_t NEW
690 gpgme_remove_io_cb_t NEW
692 gpgme_event_io_cb_t NEW
694 gpgme_data_read_cb_t NEW
695 gpgme_data_write_cb_t NEW
696 gpgme_data_seek_cb_t NEW
697 gpgme_data_release_cb_t NEW
699 gpgme_trust_item_t NEW
700 gpgme_status_code_t NEW
701 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
703 gpgme_err_source_t NEW
708 gpgme_error_from_errno NEW
709 gpgme_err_make_from_errno NEW
710 gpgme_err_code_from_errno NEW
711 gpgme_err_code_to_errno NEW
713 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
714 gpgme_event_io_t CHANGED: New event type (all numbers changed).
715 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
716 gpgme_edit_cb_t CHANGED: Write directly to FD.
717 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
718 gpgme_op_verify CHANGED: Drop R_STAT argument.
719 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
720 gpgme_wait CHANGED: Can return NULL even if hang is true.
721 GpgmeIdleFunc REMOVED
722 gpgme_register_idle REMOVED
723 GpgmeRecipients REMOVED
724 gpgme_recipients_new REMOVED
725 gpgme_recipients_release REMOVED
726 gpgme_recipients_add_name REMOVED
727 gpgme_recipients_add_name_with_validity REMOVED
728 gpgme_recipients_count REMOVED
729 gpgme_recipients_enum_open REMOVED
730 gpgme_recipients_enum_read REMOVED
731 gpgme_recipients_enum_close REMOVED
732 gpgme_encrypt_flags_t NEW
733 GPGME_ENCRYPT_ALWAYS_TRUST NEW
734 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
735 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
736 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
737 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
738 gpgme_op_export_start CHANGED: User IDs passed as patterns.
739 gpgme_op_export CHANGED: User IDs passed as patterns.
740 gpgme_op_export_ext_start NEW
741 gpgme_op_export_ext NEW
742 gpgme_keylist_mode_t NEW
744 gpgme_engine_info_t NEW
745 gpgme_get_engine_info CHANGED: Return info structure instead XML.
746 gpgme_get_protocol_name NEW
747 gpgme_cancel REMOVED: Return error in callback directly.
748 gpgme_op_genkey CHANGED: FPR argument dropped.
749 gpgme_op_genkey_result NEW
750 gpgme_genkey_result_t NEW
751 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
752 gpgme_op_import_result NEW
753 gpgme_import_status_t NEW
754 gpgme_import_result_t NEW
755 gpgme_pubkey_algo_t NEW
756 gpgme_hash_algo_t NEW
757 gpgme_invalid_key_t NEW
758 gpgme_new_signature_t NEW
759 gpgme_sign_result_t NEW
760 gpgme_op_sign_result NEW
761 gpgme_pubkey_algo_name NEW
762 gpgme_hash_algo_name NEW
763 gpgme_encrypt_result_t NEW
764 gpgme_op_encrypt_result NEW
765 gpgme_decrypt_result_t NEW
766 gpgme_op_decrypt_result NEW
767 gpgme_verify_result_t NEW
768 gpgme_op_verify_result NEW
769 gpgme_get_notation REMOVED: Access verify result directly instead.
770 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
771 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
772 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
773 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
774 gpgme_get_sig_status DEPRECATED: Use verify result directly.
775 gpgme_trust_item_t CHANGED: Now has user accessible data members.
776 gpgme_trust_item_ref NEW
777 gpgme_trust_item_unref NEW
778 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
779 gpgme_trust_item_get_string_attr DEPRECATED
780 gpgme_trust_item_get_ulong_attr DEPRECATED
781 gpgme_get_key CHANGED: Removed force_update argument.
785 gpgme_key_t CHANGED: Now has user accessible data members.
786 gpgme_key_get_string_attr DEPRECATED
787 gpgme_key_get_ulong_attr DEPRECATED
788 gpgme_key_sig_get_string_attr DEPRECATED
789 gpgme_key_sig_get_ulong_attr DEPRECATED
790 gpgme_key_get_as_xml REMOVED
791 gpgme_key_list_result_t NEW
792 gpgme_op_keylist_result NEW
793 gpgme_get_op_info REMOVED
794 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
796 Noteworthy changes in version 0.4.0 (2002-12-23)
797 ------------------------------------------------
799 * Key generation returns the fingerprint of the generated key.
801 * New convenience function gpgme_get_key.
803 * Supports signatures of user IDs in keys via the new
804 GPGME_KEYLIST_MODE_SIGS keylist mode and the
805 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
806 interfaces. The XML info about a key also includes the signatures
809 * New data object interface, which is more flexible and transparent.
811 * Interface changes relative to the 0.3.9 release:
812 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
816 GpgmeDataReleaseCb NEW
818 gpgme_data_read CHANGED: Match read() closely.
819 gpgme_data_write CHANGED: Match write() closely.
821 gpgme_data_new_from_fd NEW
822 gpgme_data_new_from_stream NEW
823 gpgme_data_new_from_cbs NEW
824 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
825 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
826 gpgme_data_get_type REMOVED: No replacement.
827 gpgme_op_verify CHANGED: Take different data objects for
828 signed text and plain text.
829 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
830 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
831 gpgme_op_genkey CHANGED: New parameter FPR.
832 GPGME_KEYLIST_MODE_SIGS NEW
833 gpgme_key_sig_get_string_attr NEW
834 gpgme_key_sig_get_ulong_attr NEW
836 GPGME_ATTR_SIG_CLASS NEW
837 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
839 Noteworthy changes in version 0.3.16 (2003-11-19)
840 -------------------------------------------------
842 * Compatibility fixes for GnuPG 1.9.x
844 Noteworthy changes in version 0.3.15 (2003-02-18)
845 -------------------------------------------------
847 * The progress status is sent via the progress callbacks in
850 * Bug fix for signing operations with explicit signer settings for
853 Noteworthy changes in version 0.3.14 (2002-12-04)
854 -------------------------------------------------
856 * GPGME-Plug is now in its own package "cryptplug".
858 * Workaround for a setlocale problem. Fixed a segv related to not
859 correctly as closed marked file descriptors.
861 Noteworthy changes in version 0.3.13 (2002-11-20)
862 -------------------------------------------------
864 * Release due to changes in gpgmeplug.
866 Noteworthy changes in version 0.3.12 (2002-10-15)
867 -------------------------------------------------
869 * Fixed some bux with key listings.
871 * The development has been branched to clean up some API issues.
872 This 0.3 series will be kept for compatibility reasons; so do don't
875 Noteworthy changes in version 0.3.11 (2002-09-20)
876 -------------------------------------------------
880 Noteworthy changes in version 0.3.10 (2002-09-02)
881 -------------------------------------------------
883 * Setting the signing keys for the CMS protocol does now work.
885 * The signers setting is honoured by gpgme_op_edit.
887 Noteworthy changes in version 0.3.9 (2002-08-21)
888 ------------------------------------------------
890 * A spec file for creating RPMs has been added.
892 * An experimental interface to GnuPG's --edit-key functionality is
893 introduced, see gpgme_op_edit.
895 * The new gpgme_import_ext function provides a convenient access to
896 the number of processed keys.
898 * Interface changes relative to the 0.3.8 release:
899 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
902 gpgme_op_edit_start NEW
904 gpgme_op_import_ext NEW
905 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
907 Noteworthy changes in version 0.3.8 (2002-06-25)
908 ------------------------------------------------
910 * It is possible to use an outside event loop for the I/O to the
911 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
913 * Interface changes relative to the 0.3.6 release:
914 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
916 GpgmeRegisterIOCb NEW
920 struct GpgmeIOCbs NEW
923 GPGME_ATTR_ERRTOK NEW
924 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
926 Noteworthy changes in version 0.3.7 (2002-06-04)
927 ------------------------------------------------
929 * GPGME_ATTR_OTRUST is implemented now.
931 * A first step toward thread safeness has been achieved, see the
932 documentation for details. Supported thread libraries are pthread
935 Noteworthy changes in version 0.3.6 (2002-05-03)
936 ------------------------------------------------
938 * All error output of the gpgsm backend is send to the bit bucket.
940 * The signature verification functions are extended. Instead of
941 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
942 expired signatures. 2 new functions may be used to retrieve more
943 detailed information like the signature expiration time and a
944 validity information of the key without an extra key looking.
946 * The current passphrase callback and progress meter callback can be
947 retrieved with the new functions gpgme_get_passphrase_cb and
948 gpgme_get_progress_cb respectively.
950 * Interface changes relative to the 0.3.5 release:
951 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
952 gpgme_get_passphrase_cb NEW
953 gpgme_get_progress_cb NEW
954 GpgmeDataEncoding NEW
955 gpgme_data_set_encoding NEW
956 gpgme_data_get_encoding NEW
957 GPGME_SIG_STAT_GOOD_EXP NEW
958 GPGME_SIG_STAT_GOOD_EXPKEY NEW
959 gpgme_op_verify CHANGED: Returns more status codes.
960 GPGME_ATTR_SIG_STATUS NEW
961 gpgme_get_sig_string_attr NEW
962 gpgme_get_sig_ulong_attr NEW
963 gpgme_get_protocol NEW
964 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
966 Noteworthy changes in version 0.3.5 (2002-04-01)
967 ------------------------------------------------
969 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
970 case, symmetric encryption is performed. Note that this requires a
971 passphrase from the user.
973 * More information is returned for X.509 certificates.
975 * Interface changes relative to the 0.3.4 release:
976 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
977 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
978 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
980 Noteworthy changes in version 0.3.4 (2002-03-04)
981 ------------------------------------------------
983 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
984 some recipients have been invalid, whereas earlier versions
985 succeeded in this case. The plaintext is still encrypted for all valid
986 recipients, so the application might take this error as a hint that
987 the ciphertext is not usable for all requested recipients.
988 Information about invalid recipients is available with gpgme_get_op_info.
990 * gpgme_op_verify now allows to pass an uninitialized data object as
991 its plaintext argument to check for normal and cleartext
992 signatures. The plaintext is then returned in the data object.
994 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
995 to set and get the number of certifications to include in S/MIME
998 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
999 to encrypt and sign a message in a combined operation.
1001 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1003 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1005 * Interface changes relative to the 0.3.3 release:
1006 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1007 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1008 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1009 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1010 gpgme_set_include_certs NEW
1011 gpgme_get_include_certs NEW
1012 gpgme_op_encrypt_sign NEW
1013 gpgme_op_encrypt_sign_start NEW
1014 gpgme_op_keylist_ext_start NEW
1015 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1017 Noteworthy changes in version 0.3.3 (2002-02-12)
1018 ------------------------------------------------
1020 * Fix the Makefile in jnlib.
1022 * Fix the test suite (hopefully). It should clean up all its state
1023 with `make check' now.
1026 Noteworthy changes in version 0.3.2 (2002-02-10)
1027 ------------------------------------------------
1029 * Remove erroneous dependency on libgcrypt in jnlib.
1032 Noteworthy changes in version 0.3.1 (2002-02-09)
1033 ------------------------------------------------
1035 * There is a Texinfo manual documenting the API.
1037 * The gpgme_set_keylist_mode function returns an error, and changed
1038 its meaning. It is no longer usable to select between normal and
1039 fast mode (newer versions of GnuPG will always be fast), but
1040 selects between local keyring, remote keyserver, or both.
1041 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1042 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1043 current setting, a fucntion gpgme_get_keylist_mode was added to
1044 retrieve the current mode.
1046 * gpgme_wait accepts a new argument STATUS to return the error status
1047 of the operation on the context. Its definition is closer to
1048 waitpid() now than before.
1050 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1051 type from off_t to the unsigned size_t.
1053 * The R_HD argument to the GpgmePassphraseCb type changed its type
1054 from void* to void**.
1056 * New interface gpgme_op_trustlist_end() to match
1057 gpgme_op_keylist_end().
1059 * The CryptPlug modules have been renamed to gpgme-openpgp and
1060 gpgme-smime, and they are installed in pkglibdir by `make install'.
1062 * An idle function can be registered with gpgme_register_idle().
1064 * The GpgSM backend supports key generation with gpgme_op_genkey().
1066 * Interface changes relative to the 0.3.0 release:
1067 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1068 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1069 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1070 gpgme_wait CHANGED: New argument STATUS.
1071 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1072 The function has a new meaning!
1073 gpgme_get_keylist_mode NEW
1074 GPGME_KEYLIST_MODE_LOCAL NEW
1075 GPGME_KEYLIST_MODE_EXTERN NEW
1076 gpgme_op_trustlist_next NEW
1078 gpgme_register_idle NEW
1079 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1081 Noteworthy changes in version 0.3.0 (2001-12-19)
1082 ------------------------------------------------
1084 * New interface gpgme_set_protocol() to set the protocol and thus the
1085 crypto engine to be used by the context. Currently, the OpenPGP
1086 and the CMS protocols are supported. They are specified by the new
1087 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1088 A new context uses the OpenPGP engine by default.
1090 * gpgme_get_engine_info() returns information for all crypto engines
1091 compiled into the library. The XML format has changed. To
1092 reliably get the version of a crypto engine, the <version> tag
1093 after the appropriate <protocol> tag has to be looked for.
1095 * New interface gpgme_engine_check_version(), obsoleting
1096 gpgme_check_engine(). Check the version of all engines you are
1097 supporting in your software.
1099 * GpgmeKey lists the user ids in the order as they are returned by
1100 GnuPG, first the primary key with index 0, then the sub-user ids.
1102 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1103 signatures simultaneously.
1105 * The new interface gpgme_op_keylist_end() terminates a pending
1106 keylist operation. A keylist operation is also terminated when
1107 gpgme_op_keylist_next() returns GPGME_EOF.
1109 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1110 cross-compiled, or even compiled without support for GnuPG
1113 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1114 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1115 in the path, but it can also be compiled without support for GpgSM
1116 (`--without-gpgsm').
1118 * CryptPlug modules for GPGME are included and can be enabled at
1119 configure time (`--enable-gpgmeplug'). There is one module which
1120 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1121 GpgSM engine (`gpgsmplug').
1123 * Interface changes relative to the latest 0.2.x release:
1124 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1125 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1126 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1127 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1128 gpgme_get_engine_info CHANGED: New format, extended content.
1129 gpgme_engine_check_version NEW
1130 gpgme_decrypt_verify_start NEW
1131 gpgme_decrypt_verify NEW
1132 gpgme_op_keylist_next NEW
1133 gpgme_set_protocol NEW
1134 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1137 Noteworthy changes in version 0.2.3 (2001-09-17)
1138 ------------------------------------------------
1140 * New function gpgme_get_op_info which can be used to get the micalg
1141 parameter needed for MOSS.
1143 * New functions gpgme_get_armor and gpgme_get_textmode.
1145 * The usual bug fixes and some minor functionality improvements.
1147 * Added a simple encryption component for MS-Windows; however the
1148 build procedure might have some problems.
1151 Noteworthy changes in version 0.2.2 (2001-06-12)
1152 ------------------------------------------------
1154 * Implemented a key cache.
1156 * Fixed a race condition under W32 and some other bug fixes.
1159 Noteworthy changes in version 0.2.1 (2001-04-02)
1160 ------------------------------------------------
1162 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1164 * Handle GnuPG's new key capabilities output and support revocation
1167 * Made the W32 support more robust.
1170 Copyright 2001, 2002, 2003, 2004, 2005 g10 Code GmbH
1172 This file is free software; as a special exception the author gives
1173 unlimited permission to copy and/or distribute it, with or without
1174 modifications, as long as this notice is preserved.
1176 This file is distributed in the hope that it will be useful, but
1177 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1178 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.