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