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