1 Noteworthy changes in version 1.1.9
2 ------------------------------------------------
4 * New encryption flag GPGME_ENCRYPT_NO_ENCRYPT_TO to disable default
7 * Interface changes relative to the 1.1.7 release:
8 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9 GPGME_KEYLIST_MODE_EPHEMERAL NEW.
10 GPGME_PROTOCOL_ASSUAN NEW.
11 gpgme_assuan_data_cb_t NEW.
12 gpgme_assuan_inquire_cb_t NEW.
13 gpgme_assuan_status_cb_t NEW.
14 gpgme_op_assuan_transact_start NEW.
15 gpgme_op_assuan_transact NEW.
16 gpgme_op_assuan_result NEW.
17 gpgme_subkey_t EXTENDED: New fields is_cardkey, card_number.
18 GPGME_ENCRYPT_NO_ENCRYPT_TO NEW.
19 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
22 Noteworthy changes in version 1.1.8 (2008-12-08)
23 ------------------------------------------------
25 * SIGPIPE is now again ignored as described in the manual. Fixes
26 regresion introduced with 1.1.6.
29 Noteworthy changes in version 1.1.7 (2008-10-17)
30 ------------------------------------------------
32 * Using GPGME_KEYLIST_MODE_LOCAL combined with
33 GPGME_KEYLIST_MODE_EXTERN is now supported; it uses the
34 --locate-keys feature of gpg (>= 2.0.10).
36 * The encoding of gpgme_data_t objects can affect the output encoding
37 of export, sign and encrypt operations now (the same operations
38 that are also affected by the ASCII mode switch). We believe this
39 change in the ABI is innocent enough not to break existing
40 applications (it only affects the S/MIME backend on certain
43 * The reference manual now includes the specification of "The GnuPG
46 * A new function gpgme_cancel_async can be used to asynchronously
47 cancel any pending operation at any time, from any thread.
49 * Interface changes relative to the 1.1.6 release:
50 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
51 gpgme_op_encrypt CHANGED: Output encoding can affect result.
52 gpgme_op_encrypt_start CHANGED: Output encoding can affect result.
53 gpgme_op_encrypt_sign CHANGED: Output encoding can affect result.
54 gpgme_op_encrypt_sign_start CHANGED: Output encoding can affect result.
55 gpgme_op_sign CHANGED: Output encoding can affect result.
56 gpgme_op_sign_start CHANGED: Output encoding can affect result.
57 gpgme_op_export CHANGED: Output encoding can affect result.
58 gpgme_op_export_start CHANGED: Output encoding can affect result.
59 gpgme_op_export_ext CHANGED: Output encoding can affect result.
60 gpgme_op_export_ext_start CHANGED: Output encoding can affect result.
61 gpgme_cancel_async NEW
62 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
65 Noteworthy changes in version 1.1.6 (2008-01-04)
66 ------------------------------------------------
68 * Bug fixes for for W32.
70 * A new, experimental (and thus undocumented and potentially
71 unstable) interface for accessing gpg-conf through GPGME has been
74 * Interface changes relative to the 1.1.1 release:
75 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
76 gpgme_signature_t EXTENDED: New field chain_model.
77 gpgme_op_getauditlog_start NEW.
78 gpgme_op_getauditlog NEW.
79 GPGME_AUDITLOG_HTML NEW.
80 GPGME_AUDITLOG_WITH_HELP NEW.
81 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
84 Noteworthy changes in version 1.1.5 (2007-07-09)
85 ------------------------------------------------
87 * Bug and portability fixes (mainly for W32).
90 Noteworthy changes in version 1.1.4 (2007-03-05)
91 ------------------------------------------------
93 * Detect and bail out on double plaintext messages. This is required
94 so that applications can properly detect the signed parts of a
95 message. Actual there is now a double protection as GnuPG 1.4.7
96 will detect this case too.
99 Noteworthy changes in version 1.1.3 (2007-01-29)
100 ------------------------------------------------
102 * Fixed a memory leak in gpgme_data_release_and_get_mem.
104 * Fixed a bug in Windows command line quoting.
107 Noteworthy changes in version 1.1.2 (2006-03-02)
108 ------------------------------------------------
110 * Fixed a bug in the W32 glib backend.
113 Noteworthy changes in version 1.1.1 (2006-02-23)
114 ------------------------------------------------
116 * Fixed a bug in that the fingerprints of subkeys are not available.
118 * Clarified usage of the SECRET flag in key listings. It is now
121 * Reading signature notations and policy URLs on key signatures is
122 supported. They can be found in the new field notations of the
123 gpgme_key_sig_t structure. This has to be enabled with the keylist
124 mode flag GPGME_KEYLIST_MODE_SIG_NOTATIONS.
126 * A new gpgme_free() function solves the problem of using different
127 allocators in a single program. This function should now be used
128 instead calling free() to release the buffer returned by
129 gpgme_data_release_and_get_mem. It is recommended that you always
130 do this, but it is only necessary on certain platforms, so backwards
131 compatibility is provided. In other words: If free() worked for
132 you before, it will keep working.
134 * New status codes GPGME_PKA_TRUST_GOOD and GPGME_PKA_TRUST_BAD.
135 They are analyzed by the verify handlers and made available in the
136 new PKA_TRUST and PKA_ADDRESS fields of the signature result structure.
138 * Interface changes relative to the 1.1.0 release:
139 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
140 gpgme_key_sig_t EXTENDED: New field notations.
141 GPGME_KEYLIST_MODE_SIG_NOTATIONS NEW
143 GPGME_STATUS_PKA_TRUST_BAD NEW
144 GPGME_STATUS_PKA_TRUST_GOOD NEW
145 gpgme_signature_t EXTENDED: New field pka_trust.
146 gpgme_signature_t EXTENDED: New field pka_address.
147 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
150 Noteworthy changes in version 1.1.0 (2005-10-01)
151 ------------------------------------------------
153 * You can now configure the backend engine file name and home
154 directory to be used, as default and per context.
156 * Information about the recipients of an encrypted text is now
157 available at decryption time.
159 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
160 and verify handlers, the information about the plaintext filename,
161 if available is made available in the new field file_name of the
162 respective result structure.
164 * The code for "automagically detecting the thread library" has been
165 removed from libgpgme. It is deprecated since version 0.4.3.
166 Since then, you had to link against libgpgme-pthread for
167 applications using pthread and libgpgme-pth for applications using
170 The code was removed because it caused compilation problems on
171 systems where the pthread.h header from GNU Pth is available in
172 addition to the system header (FreeBSD 6 and later for example).
174 * "./autogen.sh --build-w32" does now build gpgme.dll.
176 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
177 delimiter. The standard install directory is used when locating
178 gpg or gpgsm before finally falling back to the hardwired name.
180 * There is a new flag for keys and subkeys, is_qualified, which
181 indicates if a key can be used for qualified signatures according
182 to local government regulations.
184 * You can associate a filename with a data object using the new
185 function gpgme_data_set_file_name(). This filename will be stored
186 in the output when encrypting or signing the data and will be
187 returned when decrypting or verifying the output data.
189 * You can now set notation data at signature creation with the new
190 function gpgme_sig_notation_add().
192 * Interface changes relative to the 1.0.3 release:
193 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
194 gpgme_set_engine_info NEW
195 gpgme_ctx_get_engine_info NEW
196 gpgme_ctx_set_engine_info NEW
197 gpgme_recipient_t NEW
198 gpgme_decrypt_result_t EXTENDED: New field recipients.
199 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
200 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
201 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
202 GPGME_STATUS_PLAINTEXT NEW
203 gpgme_key_t EXTENDED: New field is_qualified.
204 gpgme_subkey_t EXTENDED: New field is_qualified.
205 gpgme_data_get_file_name NEW
206 gpgme_data_set_file_name NEW
207 gpgme_sig_notation_flags_t NEW
208 GPGME_SIG_NOTATION_HUMAN_READABLE NEW
209 GPGME_SIG_NOTATAION_CRITICAL NEW
210 gpgme_sig_notation_clear NEW
211 gpgme_sig_notation_add NEW
212 gpgme_sig_notation_get NEW
213 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
216 Noteworthy changes in version 1.0.3 (2005-06-20)
217 ------------------------------------------------
219 * Previousy, GPGME would use a default "include certs" of 1. This
220 has been changed. Now GPGME will use the crypto backend engines
221 default unless you set the value with gpgme_set_include_certs()
222 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
223 as a value to explicitely request the new default behaviour.
225 Because the default changes, this is a slight change of the API
226 semantics. We consider it to be a bug fix.
228 * A bug which made GPGME hang has been fixed. If you have
229 experienced hanging before, please try out this version and let me
230 know if you still experience hanging problems.
232 * Interface changes relative to the 0.9.0 release:
233 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
234 gpgme_set_include_certs CHANGED DEFAULT
235 GPGME_INCLUDE_CERTS_DEFAULT NEW
236 GPGME_STATUS_SIG_SUBPACKET NEW
237 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
238 GPGME_STATUS_SC_OP_FAILURE NEW
239 GPGME_STATUS_SC_OP_SUCCESS NEW
240 GPGME_STATUS_CARDCTRL NEW
241 GPGME_STATUS_BACKUP_KEY_CREATED NEW
242 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
245 Noteworthy changes in version 1.0.2 (2004-12-28)
246 ------------------------------------------------
248 * Changed the license of the library to the GNU Lesser General Public
249 License (LGPL), version 2.1 or later.
252 Noteworthy changes in version 1.0.1 (2004-10-22)
253 ------------------------------------------------
258 Noteworthy changes in version 1.0.0 (2004-09-30)
259 ------------------------------------------------
261 * Version 1.0.0! We are proud to present you with a thoroughly
262 tested and stable version of the GPGME library. A big Thank You!
263 to all the people who made this possible.
265 The development will be branched into a stable 1.x.y series and the
268 * The gpgme.m4 macro supports checking the API version. Just prepend
269 it to the required version string, separated by a colon. For
270 example, this release has the version "1:1.0.0". The last release
271 to which this version is (mostly) ABI compatible is "1:0.4.2",
272 which is the default required version.
275 Noteworthy changes in version 0.9.0 (2004-06-08)
276 ------------------------------------------------
278 * The type gpgme_key_t has now a new field keylist_mode that contains
279 the keylist mode that was active at the time the key was retrieved.
281 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
282 that contains a flag indicating that the key should not have been
285 * Verifying a signature of a revoked key gives the correct result now
286 (GPG_ERR_CERT_REVOKED error code).
288 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
289 verify operations still allows you to look at the signature
292 * Clarified that patterns in keylisting operations have an upper
293 limit, and thus are not suited to list many keys at once by their
294 fingerprint. Also improve the error message if the pattern is too
295 long for the CMS protocol to handle.
297 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
298 gpgme_key_t EXTENDED: New field keylist_mode.
299 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
300 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
303 Noteworthy changes in version 0.4.7 (2004-04-29)
304 ------------------------------------------------
306 * Correctly initialize the fields expired, revoked, invalid, and
307 disabled in the gpgme_key_t structures.
309 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
310 accidently of type int instead unsigned int.
312 * Interface changes relative to the 0.4.5 release:
313 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
314 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
315 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
317 Noteworthy changes in version 0.4.6 (2004-04-06)
318 ------------------------------------------------
323 Noteworthy changes in version 0.4.5 (2004-03-07)
324 ------------------------------------------------
326 * GPGME is now compiled with LFS (large file support) by default.
327 This means that _all_ programs using GPGME must be compiled with
328 LFS support enabled by default. You can do this easily with
329 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
330 without autoconf by defining the preprocessor symbol
331 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
332 the C compiler command line, or by defining this preprocessor
333 symbol before including any system header files). For more
334 details, read the section on LFS in the manual.
336 Up to now, it was undocumented that GPGME was not using LFS.
337 But the public interfaces use off_t, and file descriptors are
338 exchanged between the application and GPGME. This was an oversight,
339 and bound to cause troubles in the future.
341 Writing GPGME as a dual mode library that seamlessly supports LFS
342 while keeping backwards compatibility is possible, but does not
343 solve the problem: Many applications already expect GPGME to have
344 LFS (they are compiled with off_t being a 64bit value). This is true
345 in particular for the popular Gtk+ and Qt programs.
347 So, although this is an ABI (but not an API) break, we will not
348 change the library version to reflect that. Because the interfaces
349 affected are probably not used yet in any GPGME 0.4 based
350 application, we don't expect any real failures from this change.
351 In fact, applications already using LFS will have some subtle bugs
354 However, if you encounter an application using GPGME 0.4.x that
355 does _not_ use LFS by default (off_t is a 32bit value), _and_
356 uses at least one of the functions gpgme_data_seek,
357 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
358 gpgme_data_new_from_cbs, then indeed this library will be ABI
359 incompatible with the program. As said above, we don't believe
360 such a program exists. If we are in error, then you have two
361 options: As a quick hack, you can configure GPGME with the
362 --disable-largefile option. This will revert the change, and GPGME
363 will not use LFS. However, GPGME will be incompatible with
364 programs that expect GPGME to use LFS. All applications are
365 required to use LFS when using GPGME, so this is only good as a
366 temporary local work-around.
368 The other option is to change the versioning of the library and
369 recompile all applications. We have reserved a special version of
370 the library for that, so you can do that without expecting a
371 version clash in the future. Furthermore, everyone who does this
372 will agree on the version to use (this is important for
373 distribution makers). Read the comment in configure.ac (before
374 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
375 blindly: As stated above, we think it is unlikely this measure is
376 needed. Still, it is there if necessary. If in doubt, contact us
377 and we will give our advise for your specific situation.
379 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
382 * New interface gpgme_cancel() that can be used to cancel
383 asynchronous operations.
385 * Interface changes relative to the 0.4.4 release:
386 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
387 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
388 gpgme_data_seek CHANGED: off_t is now a largefile type.
389 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
390 GPGME_KEYLIST_MODE_VALIDATE NEW
392 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
394 Noteworthy changes in version 0.4.4 (2004-01-12)
395 ------------------------------------------------
397 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
398 been renamed to "sig_class", to avoid clash with C++ compilers. In
399 the C API, the old name "class" has been preserved for backwards
400 compatibility, but is deprecated.
402 * Interface changes relative to the 0.4.3 release:
403 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
404 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
405 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
406 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
408 Noteworthy changes in version 0.4.3 (2003-10-06)
409 ------------------------------------------------
411 * libgpgme should not be used for threaded programs anymore. This
412 never worked reliably in all cases, because you had to
413 be careful about the linking order and libtool wouldn't do that for
414 you automatically. Instead, now you have to link against
415 libgpgme-pthread for applications using pthread and libgpgme-pth for
416 applications using GNU Pth.
418 The old code for automagically detecting the thread library is
419 still part of libgpgme, but it is DEPRECATED.
421 * There are new automake macros AM_PATH_GPGME_PTH and
422 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
423 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
424 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
425 variables of course also include the configuration for the thread
426 package itself. Alternatively, use libtool.
428 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
431 * gpgme-config doesn't support setting the prefix or exec prefix
432 anymore. I don't think it ever worked correctly, and it seems to
435 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
436 provided was not unique, instead returning the first matching key.
438 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
439 that indicates if the key can be used for authentication.
441 * gpgme_signature_t's status field is now correctly set to an error
442 with error code GPG_ERR_NO_PUBKEY if public key is not found.
444 * gpgme_new_signature_t's class field is now an unsigned int, rather
445 than an unsigned long (the old class field is preserved for
446 backwards compatibility).
448 * A new function gpgme_set_locale() is provided to allow configuring
449 the locale for the crypto backend. This is necessary for text
450 terminals so that programs like the pinentry can be started with
451 the right locale settings for the terminal the application is running
452 on, in case the terminal has different settings than the system
453 default (for example, if it is a remote terminal). You are highly
454 recommended to call the following functions directly after
459 setlocale (LC_ALL, "");
460 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
461 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
463 GPGME can not do this for you, as setlocale is not thread safe, and
464 there is no alternative.
466 * The signal action for SIGPIPE is now set to SIG_IGN by
467 gpgme_check_version, instead the first time a crypto engine is
468 started (which is not well defined).
470 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
471 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
472 to CRC24RFC2440. For now, these strings can be used as the MIC
473 parameter for PGP/MIME (if appropriately modified).
475 * Interface changes relative to the 0.4.2 release:
476 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
478 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
479 gpgme_key_t EXTENDED: New field can_authenticate.
480 gpgme_subkey_t EXTENDED: New field can_authenticate.
481 gpgme_new_signature_t CHANGED: New type for class field.
483 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
484 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
486 Noteworthy changes in version 0.4.2 (2003-07-30)
487 ------------------------------------------------
489 * Allow gpg-error to be in non-standard place when linking the test suite.
491 * Configure will fail now if gpg-error can not be found.
493 * Fixed initialized memory backed data objects for writing, which
494 caused the test program to crash (but only on Mac OS, surprisingly).
496 * Eliminate use of C99 constructs.
498 * Small improvements to the manual.
501 Noteworthy changes in version 0.4.1 (2003-06-06)
502 ------------------------------------------------
504 This is the release that 0.4.0 should have been. There are many
505 interface changes, please see below for the details. The changes are
506 sometimes the result of new functionality, but more often express a
507 paradigm shift. Others are an overdue cleanup to get GPGME in line
508 with the GNU coding standards and to make the interface more
509 self-consistent. Here is an overview on the changes:
511 All types have been renamed to conform to the GNU coding standards,
512 most of the time by keeping the whole name in lowercase and inserting
513 underscores between words.
515 All operations consistently only accept input parameters in their
516 invocation function, and return only an error code directly. Further
517 information about the result of the operation has to be retrieved
518 afterwards by calling one of the result functions. This unifies the
519 synchronous and the asynchronous interface.
521 The error values have been completely replaced by a more
522 sophisticated model that allows GPGME to transparently and accurately
523 report all errors from the other GnuPG components, irregardless of
524 process boundaries. This is achieved by using the library
525 libgpg-errors, which is shared by all GnuPG components. This library
526 is now required for GPGME.
528 The results of all operations are now provided by pointers to C
529 structs rather than by XML structs or in other ways.
531 Objects which used to be opaque (for example a key) are now pointers
532 to accessible structs, so no accessor functions are necessary.
534 Backward compatibility is provided where it was possible without too
535 much effort and did not collide with the overall sanitization effort.
536 However, this is only for ease of transition. NO DEPRECATED FUNCTION
537 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
538 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
539 Recommendations how to replace deprecated or removed functionality
540 can be found within the description of each change.
542 What follows are all changes to the interface and behaviour of GPGME
545 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
546 deprecated attributes will warn about use of obsolete functions and
547 type definitions. You can suppress these warnings by passing
548 -Wno-deprecated-declarations to the gcc command.
550 * The following types have been renamed. The old types are still
551 available as aliases, but they are deprecated now:
554 GpgmeData gpgme_data_t
555 GpgmeError gpgme_error_t
556 GpgmeDataEncoding gpgme_data_encoding_t
557 GpgmeSigStat gpgme_sig_stat_t
558 GpgmeSigMode gpgme_sig_mode_t
559 GpgmeAttr gpgme_attr_t
560 GpgmeValidity gpgme_validity_t
561 GpgmeProtocol gpgme_protocol_t
563 GpgmePassphraseCb gpgme_passphrase_cb_t
564 GpgmeProgressCb gpgme_progress_cb_t
565 GpgmeIOCb gpgme_io_cb_t
566 GpgmeRegisterIOCb gpgme_register_io_cb_t
567 GpgmeRemoveIOCb gpgme_remove_io_cb_t
568 GpgmeEventIO gpgme_event_io_t
569 GpgmeEventIOCb gpgme_event_io_cb_t
570 GpgmeIOCbs gpgme_io_cbs
571 GpgmeDataReadCb gpgme_data_read_cb_t
572 GpgmeDataWriteCb gpgme_data_write_cb_t
573 GpgmeDataSeekCb gpgme_data_seek_cb_t
574 GpgmeDataReleaseCb gpgme_data_release_cb_t
575 GpgmeDataCbs gpgme_data_cbs_t
576 GpgmeTrustItem gpgme_trust_item_t
577 GpgmeStatusCode gpgme_status_code_t
579 * gpgme_error_t is now identical to gpg_error_t, the error type
580 provided by libgpg-error. More about using libgpg-error with GPGME
581 can be found in the manual. All error symbols have been removed!
583 * All functions and types in libgpg-error have been wrapped in GPGME.
584 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
585 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
586 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
587 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
590 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
592 * GnuPG 1.2.2 is required. The progress callback is now also invoked
593 for encrypt, sign, encrypt-sign, decrypt, verify, and
594 decrypt-verify operations. For verify operations on detached
595 signatures, the progress callback is invoked for both the detached
596 signature and the plaintext message, though.
598 * gpgme_passphrase_cb_t has been changed to not provide a complete
599 description, but the UID hint, passphrase info and a flag
600 indicating if this is a repeated attempt individually, so the user
601 can compose his own description from this information.
603 The passphrase is not returned as a C string, but must be written
604 to a file descriptor directly. This allows for secure passphrase
607 The return type has been changed to gpgme_error_t value. This
608 allowed to remove the gpgme_cancel function; just return
609 the error code GPG_ERR_CANCELED in the passphrase callback directly.
611 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
612 The user is expected to write the response to the file descriptor,
613 followed by a newline.
615 * The recipients interface has been removed. Instead, you use
616 NULL-terminated lists of keys for specifying the recipients of an
617 encryption operation. Use the new encryption flag
618 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
619 the keys (but note that in general this is not a good idea).
621 This change has been made to the prototypes of gpgme_op_encrypt,
622 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
623 gpgme_op_encrypt_sign_start.
625 The export interface has been changed to use pattern strings like
626 the keylist interface. Thus, new functions gpgme_op_export_ext and
627 gpgme_op_export_ext_start have been added as well. Now the
628 prototypes of gpgme_op_export_start and gpgme_op_export finally
631 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
632 summary anymore. Use gpgme_get_sig_status to retrieve the individual
635 * gpgme_io_cb_t changed from a void function to a function returning
636 a gpgme_error_t value. However, it will always return 0, so you
637 can safely ignore the return value.
639 * A new I/O callback event GPGME_EVENT_START has been added. The new
640 requirement is that you must wait until this event until you are
641 allowed to call the I/O callback handlers previously registered for
642 this context operation. Calling I/O callback functions for this
643 context operation before the start event happened is unsafe because
644 it can lead to race conditions in a multi-threaded environment.
646 * The idle function feature has been removed. It was not precisely
647 defined in a multi-threaded environment and is obsoleted by the
648 user I/O callback functions. If you still need a simple way to
649 call something while waiting on one or multiple asynchronous
650 operations to complete, don't set the HANG flag in gpgme_wait (note
651 that this will return to your program more often than the idle
654 * gpgme_wait can return NULL even if hang is true, if an error
655 occurs. In that case *status contains the error code.
657 * gpgme_get_engine_info was radically changed. Instead an XML
658 string, an info structure of the new type gpgme_engine_info_t is
659 returned. This makes it easier and more robust to evaluate the
660 information in an application.
662 * The new function gpgme_get_protocol_name can be used to convert a
663 gpgme_protocol_t value into a string.
665 * The status of a context operation is not checked anymore. Starting
666 a new operation will silently cancel the previous one. Calling a
667 function that requires you to have started an operation before without
668 doing so is undefined.
670 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
671 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
672 pointer to a structure which contains the fingerprint. This also
673 works with gpgme_op_genkey_start. The structure also provides
674 other information about the generated keys.
679 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
681 printf ("%s\n", fpr);
685 gpgme_genkey_result_t result;
686 err = gpgme_op_genkey (ctx, NULL, NULL);
689 result = gpgme_op_genkey_result (ctx);
691 printf ("%s\n", result->fpr);
694 * The new gpgme_op_import_result function provides detailed
695 information about the result of an import operation in
696 gpgme_import_result_t and gpgme_import_status_t objects.
697 Thus, the gpgme_op_import_ext variant is deprecated.
699 * The new gpgme_op_sign_result function provides detailed information
700 about the result of a signing operation in gpgme_sign_result_t,
701 gpgme_invalid_key_t and gpgme_new_signature_t objects.
703 * The new gpgme_op_encrypt_result function provides detailed
704 information about the result of an encryption operation in
705 a GpgmeEncryptResult object.
707 * The new gpgme_op_decrypt_result function provides detailed
708 information about the result of a decryption operation in
709 a GpgmeDecryptResult object.
711 * The new gpgme_op_verify_result function provides detailed
712 information about the result of an verify operation in
713 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
714 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
715 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
716 and gpgme_get_notation is removed.
718 * GpgmeTrustItem objects have now directly accessible data, so the
719 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
720 accessor functions are deprecated. Also, reference counting is
721 available through gpgme_trust_item_ref and gpgme_trust_item_unref
722 (the gpgme_trust_item_release alias for the latter is deprecated).
724 * Keys are not cached internally anymore, so the force_update argument
725 to gpgme_get_key has been removed.
727 * GpgmeKey objects have now directly accessible data so the
728 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
729 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
730 functions are deprecated. Also, gpgme_key_release is now
731 deprecated. The gpgme_key_get_as_xml function has been dropped.
733 * Because all interfaces using attributes are deprecated, the
734 GpgmeAttr data type is also deprecated.
736 * The new gpgme_op_keylist_result function provides detailed
737 information about the result of a key listing operation in
738 a GpgmeKeyListResult object.
740 * Now that each function comes with its own result retrieval
741 interface, the generic gpgme_get_op_info interface is not useful
744 * The type and mode of data objects is not available anymore.
746 * Interface changes relative to the 0.4.0 release:
747 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
748 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
749 GpgmeData DEPRECATED: Use gpgme_data_t.
750 GpgmeError DEPRECATED: Use gpgme_error_t.
751 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
752 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
753 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
754 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
755 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
756 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
757 GpgmeKey DEPRECATED: Use gpgme_key_t.
758 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
759 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
760 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
761 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
762 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
763 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
764 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
765 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
766 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
767 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
768 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
769 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
770 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
771 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
772 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
775 gpgme_recipients_t NEW
777 gpgme_data_encoding_t NEW
784 gpgme_passphrase_cb_t NEW
785 gpgme_progress_cb_t NEW
787 gpgme_register_io_cb_t NEW
788 gpgme_remove_io_cb_t NEW
790 gpgme_event_io_cb_t NEW
792 gpgme_data_read_cb_t NEW
793 gpgme_data_write_cb_t NEW
794 gpgme_data_seek_cb_t NEW
795 gpgme_data_release_cb_t NEW
797 gpgme_trust_item_t NEW
798 gpgme_status_code_t NEW
799 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
801 gpgme_err_source_t NEW
806 gpgme_error_from_errno NEW
807 gpgme_err_make_from_errno NEW
808 gpgme_err_code_from_errno NEW
809 gpgme_err_code_to_errno NEW
811 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
812 gpgme_event_io_t CHANGED: New event type (all numbers changed).
813 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
814 gpgme_edit_cb_t CHANGED: Write directly to FD.
815 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
816 gpgme_op_verify CHANGED: Drop R_STAT argument.
817 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
818 gpgme_wait CHANGED: Can return NULL even if hang is true.
819 GpgmeIdleFunc REMOVED
820 gpgme_register_idle REMOVED
821 GpgmeRecipients REMOVED
822 gpgme_recipients_new REMOVED
823 gpgme_recipients_release REMOVED
824 gpgme_recipients_add_name REMOVED
825 gpgme_recipients_add_name_with_validity REMOVED
826 gpgme_recipients_count REMOVED
827 gpgme_recipients_enum_open REMOVED
828 gpgme_recipients_enum_read REMOVED
829 gpgme_recipients_enum_close REMOVED
830 gpgme_encrypt_flags_t NEW
831 GPGME_ENCRYPT_ALWAYS_TRUST NEW
832 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
833 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
834 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
835 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
836 gpgme_op_export_start CHANGED: User IDs passed as patterns.
837 gpgme_op_export CHANGED: User IDs passed as patterns.
838 gpgme_op_export_ext_start NEW
839 gpgme_op_export_ext NEW
840 gpgme_keylist_mode_t NEW
842 gpgme_engine_info_t NEW
843 gpgme_get_engine_info CHANGED: Return info structure instead XML.
844 gpgme_get_protocol_name NEW
845 gpgme_cancel REMOVED: Return error in callback directly.
846 gpgme_op_genkey CHANGED: FPR argument dropped.
847 gpgme_op_genkey_result NEW
848 gpgme_genkey_result_t NEW
849 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
850 gpgme_op_import_result NEW
851 gpgme_import_status_t NEW
852 gpgme_import_result_t NEW
853 gpgme_pubkey_algo_t NEW
854 gpgme_hash_algo_t NEW
855 gpgme_invalid_key_t NEW
856 gpgme_new_signature_t NEW
857 gpgme_sign_result_t NEW
858 gpgme_op_sign_result NEW
859 gpgme_pubkey_algo_name NEW
860 gpgme_hash_algo_name NEW
861 gpgme_encrypt_result_t NEW
862 gpgme_op_encrypt_result NEW
863 gpgme_decrypt_result_t NEW
864 gpgme_op_decrypt_result NEW
865 gpgme_verify_result_t NEW
866 gpgme_op_verify_result NEW
867 gpgme_get_notation REMOVED: Access verify result directly instead.
868 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
869 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
870 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
871 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
872 gpgme_get_sig_status DEPRECATED: Use verify result directly.
873 gpgme_trust_item_t CHANGED: Now has user accessible data members.
874 gpgme_trust_item_ref NEW
875 gpgme_trust_item_unref NEW
876 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
877 gpgme_trust_item_get_string_attr DEPRECATED
878 gpgme_trust_item_get_ulong_attr DEPRECATED
879 gpgme_get_key CHANGED: Removed force_update argument.
883 gpgme_key_t CHANGED: Now has user accessible data members.
884 gpgme_key_get_string_attr DEPRECATED
885 gpgme_key_get_ulong_attr DEPRECATED
886 gpgme_key_sig_get_string_attr DEPRECATED
887 gpgme_key_sig_get_ulong_attr DEPRECATED
888 gpgme_key_get_as_xml REMOVED
889 gpgme_key_list_result_t NEW
890 gpgme_op_keylist_result NEW
891 gpgme_get_op_info REMOVED
892 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
894 Noteworthy changes in version 0.4.0 (2002-12-23)
895 ------------------------------------------------
897 * Key generation returns the fingerprint of the generated key.
899 * New convenience function gpgme_get_key.
901 * Supports signatures of user IDs in keys via the new
902 GPGME_KEYLIST_MODE_SIGS keylist mode and the
903 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
904 interfaces. The XML info about a key also includes the signatures
907 * New data object interface, which is more flexible and transparent.
909 * Interface changes relative to the 0.3.9 release:
910 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
914 GpgmeDataReleaseCb NEW
916 gpgme_data_read CHANGED: Match read() closely.
917 gpgme_data_write CHANGED: Match write() closely.
919 gpgme_data_new_from_fd NEW
920 gpgme_data_new_from_stream NEW
921 gpgme_data_new_from_cbs NEW
922 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
923 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
924 gpgme_data_get_type REMOVED: No replacement.
925 gpgme_op_verify CHANGED: Take different data objects for
926 signed text and plain text.
927 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
928 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
929 gpgme_op_genkey CHANGED: New parameter FPR.
930 GPGME_KEYLIST_MODE_SIGS NEW
931 gpgme_key_sig_get_string_attr NEW
932 gpgme_key_sig_get_ulong_attr NEW
934 GPGME_ATTR_SIG_CLASS NEW
935 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
937 Noteworthy changes in version 0.3.16 (2003-11-19)
938 -------------------------------------------------
940 * Compatibility fixes for GnuPG 1.9.x
942 Noteworthy changes in version 0.3.15 (2003-02-18)
943 -------------------------------------------------
945 * The progress status is sent via the progress callbacks in
948 * Bug fix for signing operations with explicit signer settings for
951 Noteworthy changes in version 0.3.14 (2002-12-04)
952 -------------------------------------------------
954 * GPGME-Plug is now in its own package "cryptplug".
956 * Workaround for a setlocale problem. Fixed a segv related to not
957 correctly as closed marked file descriptors.
959 Noteworthy changes in version 0.3.13 (2002-11-20)
960 -------------------------------------------------
962 * Release due to changes in gpgmeplug.
964 Noteworthy changes in version 0.3.12 (2002-10-15)
965 -------------------------------------------------
967 * Fixed some bux with key listings.
969 * The development has been branched to clean up some API issues.
970 This 0.3 series will be kept for compatibility reasons; so do don't
973 Noteworthy changes in version 0.3.11 (2002-09-20)
974 -------------------------------------------------
978 Noteworthy changes in version 0.3.10 (2002-09-02)
979 -------------------------------------------------
981 * Setting the signing keys for the CMS protocol does now work.
983 * The signers setting is honoured by gpgme_op_edit.
985 Noteworthy changes in version 0.3.9 (2002-08-21)
986 ------------------------------------------------
988 * A spec file for creating RPMs has been added.
990 * An experimental interface to GnuPG's --edit-key functionality is
991 introduced, see gpgme_op_edit.
993 * The new gpgme_import_ext function provides a convenient access to
994 the number of processed keys.
996 * Interface changes relative to the 0.3.8 release:
997 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1000 gpgme_op_edit_start NEW
1002 gpgme_op_import_ext NEW
1003 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1005 Noteworthy changes in version 0.3.8 (2002-06-25)
1006 ------------------------------------------------
1008 * It is possible to use an outside event loop for the I/O to the
1009 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
1011 * Interface changes relative to the 0.3.6 release:
1012 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1014 GpgmeRegisterIOCb NEW
1018 struct GpgmeIOCbs NEW
1019 gpgme_set_io_cbs NEW
1020 gpgme_get_io_cbs NEW
1021 GPGME_ATTR_ERRTOK NEW
1022 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1024 Noteworthy changes in version 0.3.7 (2002-06-04)
1025 ------------------------------------------------
1027 * GPGME_ATTR_OTRUST is implemented now.
1029 * A first step toward thread safeness has been achieved, see the
1030 documentation for details. Supported thread libraries are pthread
1033 Noteworthy changes in version 0.3.6 (2002-05-03)
1034 ------------------------------------------------
1036 * All error output of the gpgsm backend is send to the bit bucket.
1038 * The signature verification functions are extended. Instead of
1039 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
1040 expired signatures. 2 new functions may be used to retrieve more
1041 detailed information like the signature expiration time and a
1042 validity information of the key without an extra key looking.
1044 * The current passphrase callback and progress meter callback can be
1045 retrieved with the new functions gpgme_get_passphrase_cb and
1046 gpgme_get_progress_cb respectively.
1048 * Interface changes relative to the 0.3.5 release:
1049 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1050 gpgme_get_passphrase_cb NEW
1051 gpgme_get_progress_cb NEW
1052 GpgmeDataEncoding NEW
1053 gpgme_data_set_encoding NEW
1054 gpgme_data_get_encoding NEW
1055 GPGME_SIG_STAT_GOOD_EXP NEW
1056 GPGME_SIG_STAT_GOOD_EXPKEY NEW
1057 gpgme_op_verify CHANGED: Returns more status codes.
1058 GPGME_ATTR_SIG_STATUS NEW
1059 gpgme_get_sig_string_attr NEW
1060 gpgme_get_sig_ulong_attr NEW
1061 gpgme_get_protocol NEW
1062 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1064 Noteworthy changes in version 0.3.5 (2002-04-01)
1065 ------------------------------------------------
1067 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
1068 case, symmetric encryption is performed. Note that this requires a
1069 passphrase from the user.
1071 * More information is returned for X.509 certificates.
1073 * Interface changes relative to the 0.3.4 release:
1074 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1075 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
1076 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1078 Noteworthy changes in version 0.3.4 (2002-03-04)
1079 ------------------------------------------------
1081 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
1082 some recipients have been invalid, whereas earlier versions
1083 succeeded in this case. The plaintext is still encrypted for all valid
1084 recipients, so the application might take this error as a hint that
1085 the ciphertext is not usable for all requested recipients.
1086 Information about invalid recipients is available with gpgme_get_op_info.
1088 * gpgme_op_verify now allows to pass an uninitialized data object as
1089 its plaintext argument to check for normal and cleartext
1090 signatures. The plaintext is then returned in the data object.
1092 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
1093 to set and get the number of certifications to include in S/MIME
1096 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
1097 to encrypt and sign a message in a combined operation.
1099 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
1101 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
1103 * Interface changes relative to the 0.3.3 release:
1104 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1105 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
1106 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
1107 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
1108 gpgme_set_include_certs NEW
1109 gpgme_get_include_certs NEW
1110 gpgme_op_encrypt_sign NEW
1111 gpgme_op_encrypt_sign_start NEW
1112 gpgme_op_keylist_ext_start NEW
1113 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1115 Noteworthy changes in version 0.3.3 (2002-02-12)
1116 ------------------------------------------------
1118 * Fix the Makefile in jnlib.
1120 * Fix the test suite (hopefully). It should clean up all its state
1121 with `make check' now.
1124 Noteworthy changes in version 0.3.2 (2002-02-10)
1125 ------------------------------------------------
1127 * Remove erroneous dependency on libgcrypt in jnlib.
1130 Noteworthy changes in version 0.3.1 (2002-02-09)
1131 ------------------------------------------------
1133 * There is a Texinfo manual documenting the API.
1135 * The gpgme_set_keylist_mode function returns an error, and changed
1136 its meaning. It is no longer usable to select between normal and
1137 fast mode (newer versions of GnuPG will always be fast), but
1138 selects between local keyring, remote keyserver, or both.
1139 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
1140 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
1141 current setting, a fucntion gpgme_get_keylist_mode was added to
1142 retrieve the current mode.
1144 * gpgme_wait accepts a new argument STATUS to return the error status
1145 of the operation on the context. Its definition is closer to
1146 waitpid() now than before.
1148 * The LENGTH argument to gpgme_data_new_from_filepart changed its
1149 type from off_t to the unsigned size_t.
1151 * The R_HD argument to the GpgmePassphraseCb type changed its type
1152 from void* to void**.
1154 * New interface gpgme_op_trustlist_end() to match
1155 gpgme_op_keylist_end().
1157 * The CryptPlug modules have been renamed to gpgme-openpgp and
1158 gpgme-smime, and they are installed in pkglibdir by `make install'.
1160 * An idle function can be registered with gpgme_register_idle().
1162 * The GpgSM backend supports key generation with gpgme_op_genkey().
1164 * Interface changes relative to the 0.3.0 release:
1165 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1166 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
1167 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
1168 gpgme_wait CHANGED: New argument STATUS.
1169 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
1170 The function has a new meaning!
1171 gpgme_get_keylist_mode NEW
1172 GPGME_KEYLIST_MODE_LOCAL NEW
1173 GPGME_KEYLIST_MODE_EXTERN NEW
1174 gpgme_op_trustlist_next NEW
1176 gpgme_register_idle NEW
1177 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1179 Noteworthy changes in version 0.3.0 (2001-12-19)
1180 ------------------------------------------------
1182 * New interface gpgme_set_protocol() to set the protocol and thus the
1183 crypto engine to be used by the context. Currently, the OpenPGP
1184 and the CMS protocols are supported. They are specified by the new
1185 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1186 A new context uses the OpenPGP engine by default.
1188 * gpgme_get_engine_info() returns information for all crypto engines
1189 compiled into the library. The XML format has changed. To
1190 reliably get the version of a crypto engine, the <version> tag
1191 after the appropriate <protocol> tag has to be looked for.
1193 * New interface gpgme_engine_check_version(), obsoleting
1194 gpgme_check_engine(). Check the version of all engines you are
1195 supporting in your software.
1197 * GpgmeKey lists the user ids in the order as they are returned by
1198 GnuPG, first the primary key with index 0, then the sub-user ids.
1200 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1201 signatures simultaneously.
1203 * The new interface gpgme_op_keylist_end() terminates a pending
1204 keylist operation. A keylist operation is also terminated when
1205 gpgme_op_keylist_next() returns GPGME_EOF.
1207 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1208 cross-compiled, or even compiled without support for GnuPG
1211 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1212 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1213 in the path, but it can also be compiled without support for GpgSM
1214 (`--without-gpgsm').
1216 * CryptPlug modules for GPGME are included and can be enabled at
1217 configure time (`--enable-gpgmeplug'). There is one module which
1218 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1219 GpgSM engine (`gpgsmplug').
1221 * Interface changes relative to the latest 0.2.x release:
1222 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1223 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1224 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1225 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1226 gpgme_get_engine_info CHANGED: New format, extended content.
1227 gpgme_engine_check_version NEW
1228 gpgme_decrypt_verify_start NEW
1229 gpgme_decrypt_verify NEW
1230 gpgme_op_keylist_next NEW
1231 gpgme_set_protocol NEW
1232 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1235 Noteworthy changes in version 0.2.3 (2001-09-17)
1236 ------------------------------------------------
1238 * New function gpgme_get_op_info which can be used to get the micalg
1239 parameter needed for MOSS.
1241 * New functions gpgme_get_armor and gpgme_get_textmode.
1243 * The usual bug fixes and some minor functionality improvements.
1245 * Added a simple encryption component for MS-Windows; however the
1246 build procedure might have some problems.
1249 Noteworthy changes in version 0.2.2 (2001-06-12)
1250 ------------------------------------------------
1252 * Implemented a key cache.
1254 * Fixed a race condition under W32 and some other bug fixes.
1257 Noteworthy changes in version 0.2.1 (2001-04-02)
1258 ------------------------------------------------
1260 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1262 * Handle GnuPG's new key capabilities output and support revocation
1265 * Made the W32 support more robust.
1268 Copyright 2001, 2002, 2003, 2004, 2005, 2007, 2008 g10 Code GmbH
1270 This file is free software; as a special exception the author gives
1271 unlimited permission to copy and/or distribute it, with or without
1272 modifications, as long as this notice is preserved.
1274 This file is distributed in the hope that it will be useful, but
1275 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1276 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.