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