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