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