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