1 Noteworthy changes in version 1.1.0 (unreleased)
2 ------------------------------------------------
4 * You can now configure the backend engine file name and home
5 directory to be used, as default and per context.
7 * Previousy, GPGME would use a default "include certs" of 1. This
8 has been changed. Now GPGME will use the crypto backend engines
9 default unless you set the value with gpgme_set_include_certs()
10 explicitely. A new macro GPGME_INCLUDE_CERTS_DEFAULT can be used
11 as a value to explicitely request the new default behaviour.
13 Because the default changes, this is a slight change of the API
14 semantics. We consider it to be a bug fix.
16 * Information about the recipients of an encrypted text is now
17 available at decryption time.
19 * New status GPGME_STATUS_PLAINTEXT. This is analyzed by the decrypt
20 and verify handlers, the information about the plaintext filename,
21 if available is made available in the new field plaintext_filename
22 of the respective result structure.
24 * The code for "automagically detecting the thread library" has been
25 removed from libgpgme. It is deprecated since version 0.4.3.
26 Since then, you had to link against libgpgme-pthread for
27 applications using pthread and libgpgme-pth for applications using
30 The code was removed because it caused compilation problems on
31 systems where the pthread.h header from GNU Pth is available in
32 addition to the system header (FreeBSD 6 and later for example).
34 * "./autogen.sh --build-w32" does now build gpgme.dll.
36 * [W32] The environment variable GPGME_DEBUG now uses a semicolon as
37 delimiter. The standard install directory is used when locating
38 gpg or gpgsm before finally falling back to the hardwired name.
40 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
41 gpgme_set_engine_info NEW
42 gpgme_ctx_get_engine_info NEW
43 gpgme_ctx_set_engine_info NEW
44 gpgme_set_include_certs CHANGED DEFAULT
45 GPGME_INCLUDE_CERTS_DEFAULT NEW
47 gpgme_decrypt_result_t EXTENDED: New field recipients.
48 gpgme_verify_result_t EXTENDED: New fields pubkey_algo, hash_algo.
49 GPGME_STATUS_SIG_SUBPACKET NEW
50 GPGME_STATUS_NEED_PASSPHRASE_PIN NEW
51 GPGME_STATUS_SC_OP_FAILURE NEW
52 GPGME_STATUS_SC_OP_SUCCESS NEW
53 GPGME_STATUS_CARDCTRL NEW
54 GPGME_STATUS_BACKUP_KEY_CREATED NEW
55 gpgme_decrypt_result_t EXTENDED: New field plaintext_filename.
56 gpgme_verify_result_t EXTENDED: New field plaintext_filename.
57 GPGME_STATUS_PLAINTEXT NEW
58 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
61 Noteworthy changes in version 1.0.2 (2004-12-28)
62 ------------------------------------------------
64 * Changed the license of the library to the GNU Lesser General Public
65 License (LGPL), version 2.1 or later.
68 Noteworthy changes in version 1.0.1 (2004-10-22)
69 ------------------------------------------------
74 Noteworthy changes in version 1.0.0 (2004-09-30)
75 ------------------------------------------------
77 * Version 1.0.0! We are proud to present you with a thoroughly
78 tested and stable version of the GPGME library. A big Thank You!
79 to all the people who made this possible.
81 The development will be branched into a stable 1.x.y series and the
84 * The gpgme.m4 macro supports checking the API version. Just prepend
85 it to the required version string, separated by a colon. For
86 example, this release has the version "1:1.0.0". The last release
87 to which this version is (mostly) ABI compatible is "1:0.4.2",
88 which is the default required version.
91 Noteworthy changes in version 0.9.0 (2004-06-08)
92 ------------------------------------------------
94 * The type gpgme_key_t has now a new field keylist_mode that contains
95 the keylist mode that was active at the time the key was retrieved.
97 * The type gpgme_decrypt_result_t has a new field "wrong_key_usage"
98 that contains a flag indicating that the key should not have been
101 * Verifying a signature of a revoked key gives the correct result now
102 (GPG_ERR_CERT_REVOKED error code).
104 * Clarified that the error code GPG_ERR_NO_DATA from the decrypt &
105 verify operations still allows you to look at the signature
108 * Clarified that patterns in keylisting operations have an upper
109 limit, and thus are not suited to list many keys at once by their
110 fingerprint. Also improve the error message if the pattern is too
111 long for the CMS protocol to handle.
113 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
114 gpgme_key_t EXTENDED: New field keylist_mode.
115 gpgme_decrypt_result_t EXTENDED: New field wrong_key_usage.
116 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
119 Noteworthy changes in version 0.4.7 (2004-04-29)
120 ------------------------------------------------
122 * Correctly initialize the fields expired, revoked, invalid, and
123 disabled in the gpgme_key_t structures.
125 * A bug fix: The flag wrong_key_usage of gpgme_signature_t was
126 accidently of type int instead unsigned int.
128 * Interface changes relative to the 0.4.5 release:
129 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
130 gpgme_signature_t CHANGED: wrong_key_usage is unsigned int now.
131 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
133 Noteworthy changes in version 0.4.6 (2004-04-06)
134 ------------------------------------------------
139 Noteworthy changes in version 0.4.5 (2004-03-07)
140 ------------------------------------------------
142 * GPGME is now compiled with LFS (large file support) by default.
143 This means that _all_ programs using GPGME must be compiled with
144 LFS support enabled by default. You can do this easily with
145 autoconf, by using the AC_SYS_LARGEFILE macro. Or you can do this
146 without autoconf by defining the preprocessor symbol
147 _FILE_OFFSET_BITS to 64 (by passing the -D_FILE_OFFSET_BITS=64 to
148 the C compiler command line, or by defining this preprocessor
149 symbol before including any system header files). For more
150 details, read the section on LFS in the manual.
152 Up to now, it was undocumented that GPGME was not using LFS.
153 But the public interfaces use off_t, and file descriptors are
154 exchanged between the application and GPGME. This was an oversight,
155 and bound to cause troubles in the future.
157 Writing GPGME as a dual mode library that seamlessly supports LFS
158 while keeping backwards compatibility is possible, but does not
159 solve the problem: Many applications already expect GPGME to have
160 LFS (they are compiled with off_t being a 64bit value). This is true
161 in particular for the popular Gtk+ and Qt programs.
163 So, although this is an ABI (but not an API) break, we will not
164 change the library version to reflect that. Because the interfaces
165 affected are probably not used yet in any GPGME 0.4 based
166 application, we don't expect any real failures from this change.
167 In fact, applications already using LFS will have some subtle bugs
170 However, if you encounter an application using GPGME 0.4.x that
171 does _not_ use LFS by default (off_t is a 32bit value), _and_
172 uses at least one of the functions gpgme_data_seek,
173 gpgme_data_new_from_filepart, or a gpgme_data_seek_cb_t with
174 gpgme_data_new_from_cbs, then indeed this library will be ABI
175 incompatible with the program. As said above, we don't believe
176 such a program exists. If we are in error, then you have two
177 options: As a quick hack, you can configure GPGME with the
178 --disable-largefile option. This will revert the change, and GPGME
179 will not use LFS. However, GPGME will be incompatible with
180 programs that expect GPGME to use LFS. All applications are
181 required to use LFS when using GPGME, so this is only good as a
182 temporary local work-around.
184 The other option is to change the versioning of the library and
185 recompile all applications. We have reserved a special version of
186 the library for that, so you can do that without expecting a
187 version clash in the future. Furthermore, everyone who does this
188 will agree on the version to use (this is important for
189 distribution makers). Read the comment in configure.ac (before
190 LIBGPGME_LT_AGE) if you want to do this. Please don't do this
191 blindly: As stated above, we think it is unlikely this measure is
192 needed. Still, it is there if necessary. If in doubt, contact us
193 and we will give our advise for your specific situation.
195 * New key listing mode GPGME_KEYLIST_MODE_VALIDATE for validation of
198 * New interface gpgme_cancel() that can be used to cancel
199 asynchronous operations.
201 * Interface changes relative to the 0.4.4 release:
202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
203 gpgme_data_seek_cb_t CHANGED: off_t is now a largefile type.
204 gpgme_data_seek CHANGED: off_t is now a largefile type.
205 gpgme_data_new_from_filepart CHANGED: off_t is now a largefile type.
206 GPGME_KEYLIST_MODE_VALIDATE NEW
208 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
210 Noteworthy changes in version 0.4.4 (2004-01-12)
211 ------------------------------------------------
213 * The member "class" in gpgme_key_sig_t and gpgme_new_signature_t has
214 been renamed to "sig_class", to avoid clash with C++ compilers. In
215 the C API, the old name "class" has been preserved for backwards
216 compatibility, but is deprecated.
218 * Interface changes relative to the 0.4.3 release:
219 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
220 gpgme_key_sig_t CHANGED: class deprecated, use new sig_class.
221 gpgme_new_signature_t CHANGED: class deprecated, use new sig_class.
222 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
224 Noteworthy changes in version 0.4.3 (2003-10-06)
225 ------------------------------------------------
227 * libgpgme should not be used for threaded programs anymore. This
228 never worked reliably in all cases, because you had to
229 be careful about the linking order and libtool wouldn't do that for
230 you automatically. Instead, now you have to link against
231 libgpgme-pthread for applications using pthread and libgpgme-pth for
232 applications using GNU Pth.
234 The old code for automagically detecting the thread library is
235 still part of libgpgme, but it is DEPRECATED.
237 * There are new automake macros AM_PATH_GPGME_PTH and
238 AM_PATH_GPGME_PTHREAD, which support checking for thread-enabled
239 versions of GPGME. They define GPGME_PTH_CFLAGS, GPGME_PTH_LIBS,
240 GPGME_PTHREAD_CFLAGS and GPGME_PTHREAD_LIBS respectively. These
241 variables of course also include the configuration for the thread
242 package itself. Alternatively, use libtool.
244 * gpgme_strerror_r as a thread safe variant of gpgme_strerror was
247 * gpgme-config doesn't support setting the prefix or exec prefix
248 anymore. I don't think it ever worked correctly, and it seems to
251 * gpgme_get_key fails with GPG_ERR_AMBIGUOUS_NAME if the key ID
252 provided was not unique, instead returning the first matching key.
254 * gpgme_key_t and gpgme_subkey_t have a new field, can_authenticate,
255 that indicates if the key can be used for authentication.
257 * gpgme_signature_t's status field is now correctly set to an error
258 with error code GPG_ERR_NO_PUBKEY if public key is not found.
260 * gpgme_new_signature_t's class field is now an unsigned int, rather
261 than an unsigned long (the old class field is preserved for
262 backwards compatibility).
264 * A new function gpgme_set_locale() is provided to allow configuring
265 the locale for the crypto backend. This is necessary for text
266 terminals so that programs like the pinentry can be started with
267 the right locale settings for the terminal the application is running
268 on, in case the terminal has different settings than the system
269 default (for example, if it is a remote terminal). You are highly
270 recommended to call the following functions directly after
275 setlocale (LC_ALL, "");
276 gpgme_set_locale (NULL, LC_CTYPE, setlocale (LC_CTYPE, NULL));
277 gpgme_set_locale (NULL, LC_MESSAGES, setlocale (LC_MESSAGES, NULL));
279 GPGME can not do this for you, as setlocale is not thread safe, and
280 there is no alternative.
282 * The signal action for SIGPIPE is now set to SIG_IGN by
283 gpgme_check_version, instead the first time a crypto engine is
284 started (which is not well defined).
286 * In the output of gpgme_hash_algo_name, change RMD160 to RIPEMD160,
287 TIGER to TIGER192, CRC32-RFC1510 to CRC32RFC1510, and CRC24-RFC2440
288 to CRC24RFC2440. For now, these strings can be used as the MIC
289 parameter for PGP/MIME (if appropriately modified).
291 * Interface changes relative to the 0.4.2 release:
292 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
294 gpgme_get_key CHANGED: Fails correctly if key ID not unique.
295 gpgme_key_t EXTENDED: New field can_authenticate.
296 gpgme_subkey_t EXTENDED: New field can_authenticate.
297 gpgme_new_signature_t CHANGED: New type for class field.
299 gpgme_hash_algo_name CHANGED: Slight adjustment of algo names.
300 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
302 Noteworthy changes in version 0.4.2 (2003-07-30)
303 ------------------------------------------------
305 * Allow gpg-error to be in non-standard place when linking the test suite.
307 * Configure will fail now if gpg-error can not be found.
309 * Fixed initialized memory backed data objects for writing, which
310 caused the test program to crash (but only on Mac OS, surprisingly).
312 * Eliminate use of C99 constructs.
314 * Small improvements to the manual.
317 Noteworthy changes in version 0.4.1 (2003-06-06)
318 ------------------------------------------------
320 This is the release that 0.4.0 should have been. There are many
321 interface changes, please see below for the details. The changes are
322 sometimes the result of new functionality, but more often express a
323 paradigm shift. Others are an overdue cleanup to get GPGME in line
324 with the GNU coding standards and to make the interface more
325 self-consistent. Here is an overview on the changes:
327 All types have been renamed to conform to the GNU coding standards,
328 most of the time by keeping the whole name in lowercase and inserting
329 underscores between words.
331 All operations consistently only accept input parameters in their
332 invocation function, and return only an error code directly. Further
333 information about the result of the operation has to be retrieved
334 afterwards by calling one of the result functions. This unifies the
335 synchronous and the asynchronous interface.
337 The error values have been completely replaced by a more
338 sophisticated model that allows GPGME to transparently and accurately
339 report all errors from the other GnuPG components, irregardless of
340 process boundaries. This is achieved by using the library
341 libgpg-errors, which is shared by all GnuPG components. This library
342 is now required for GPGME.
344 The results of all operations are now provided by pointers to C
345 structs rather than by XML structs or in other ways.
347 Objects which used to be opaque (for example a key) are now pointers
348 to accessible structs, so no accessor functions are necessary.
350 Backward compatibility is provided where it was possible without too
351 much effort and did not collide with the overall sanitization effort.
352 However, this is only for ease of transition. NO DEPRECATED FUNCTION
353 OR DATA TYPE IS CONSIDERED A PART OF THE API OR ABI AND WILL BE
354 DROPPED IN THE FUTURE WITHOUT CHANGING THE SONAME OF THE LIBRARY.
355 Recommendations how to replace deprecated or removed functionality
356 can be found within the description of each change.
358 What follows are all changes to the interface and behaviour of GPGME
361 * If gpgme.h is included in sources compiled by GCC 3.1 or later,
362 deprecated attributes will warn about use of obsolete functions and
363 type definitions. You can suppress these warnings by passing
364 -Wno-deprecated-declarations to the gcc command.
366 * The following types have been renamed. The old types are still
367 available as aliases, but they are deprecated now:
370 GpgmeData gpgme_data_t
371 GpgmeError gpgme_error_t
372 GpgmeDataEncoding gpgme_data_encoding_t
373 GpgmeSigStat gpgme_sig_stat_t
374 GpgmeSigMode gpgme_sig_mode_t
375 GpgmeAttr gpgme_attr_t
376 GpgmeValidity gpgme_validity_t
377 GpgmeProtocol gpgme_protocol_t
379 GpgmePassphraseCb gpgme_passphrase_cb_t
380 GpgmeProgressCb gpgme_progress_cb_t
381 GpgmeIOCb gpgme_io_cb_t
382 GpgmeRegisterIOCb gpgme_register_io_cb_t
383 GpgmeRemoveIOCb gpgme_remove_io_cb_t
384 GpgmeEventIO gpgme_event_io_t
385 GpgmeEventIOCb gpgme_event_io_cb_t
386 GpgmeIOCbs gpgme_io_cbs
387 GpgmeDataReadCb gpgme_data_read_cb_t
388 GpgmeDataWriteCb gpgme_data_write_cb_t
389 GpgmeDataSeekCb gpgme_data_seek_cb_t
390 GpgmeDataReleaseCb gpgme_data_release_cb_t
391 GpgmeDataCbs gpgme_data_cbs_t
392 GpgmeTrustItem gpgme_trust_item_t
393 GpgmeStatusCode gpgme_status_code_t
395 * gpgme_error_t is now identical to gpg_error_t, the error type
396 provided by libgpg-error. More about using libgpg-error with GPGME
397 can be found in the manual. All error symbols have been removed!
399 * All functions and types in libgpg-error have been wrapped in GPGME.
400 The new types are gpgme_err_code_t and gpgme_err_source_t. The new
401 functions are gpgme_err_code, gpgme_err_source, gpgme_error,
402 gpgme_err_make, gpgme_error_from_errno, gpgme_err_make_from_errno,
403 gpgme_err_code_from_errno, gpgme_err_code_to_errno,
406 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
408 * GnuPG 1.2.2 is required. The progress callback is now also invoked
409 for encrypt, sign, encrypt-sign, decrypt, verify, and
410 decrypt-verify operations. For verify operations on detached
411 signatures, the progress callback is invoked for both the detached
412 signature and the plaintext message, though.
414 * gpgme_passphrase_cb_t has been changed to not provide a complete
415 description, but the UID hint, passphrase info and a flag
416 indicating if this is a repeated attempt individually, so the user
417 can compose his own description from this information.
419 The passphrase is not returned as a C string, but must be written
420 to a file descriptor directly. This allows for secure passphrase
423 The return type has been changed to gpgme_error_t value. This
424 allowed to remove the gpgme_cancel function; just return
425 the error code GPG_ERR_CANCELED in the passphrase callback directly.
427 * gpgme_edit_cb_t has been changed to take a file descriptor argument.
428 The user is expected to write the response to the file descriptor,
429 followed by a newline.
431 * The recipients interface has been removed. Instead, you use
432 NULL-terminated lists of keys for specifying the recipients of an
433 encryption operation. Use the new encryption flag
434 GPGME_ENCRYPT_ALWAYS_TRUST if you want to override the validity of
435 the keys (but note that in general this is not a good idea).
437 This change has been made to the prototypes of gpgme_op_encrypt,
438 gpgme_op_encrypt_start, gpgme_op_encrypt_sign and
439 gpgme_op_encrypt_sign_start.
441 The export interface has been changed to use pattern strings like
442 the keylist interface. Thus, new functions gpgme_op_export_ext and
443 gpgme_op_export_ext_start have been added as well. Now the
444 prototypes of gpgme_op_export_start and gpgme_op_export finally
447 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
448 summary anymore. Use gpgme_get_sig_status to retrieve the individual
451 * gpgme_io_cb_t changed from a void function to a function returning
452 a gpgme_error_t value. However, it will always return 0, so you
453 can safely ignore the return value.
455 * A new I/O callback event GPGME_EVENT_START has been added. The new
456 requirement is that you must wait until this event until you are
457 allowed to call the I/O callback handlers previously registered for
458 this context operation. Calling I/O callback functions for this
459 context operation before the start event happened is unsafe because
460 it can lead to race conditions in a multi-threaded environment.
462 * The idle function feature has been removed. It was not precisely
463 defined in a multi-threaded environment and is obsoleted by the
464 user I/O callback functions. If you still need a simple way to
465 call something while waiting on one or multiple asynchronous
466 operations to complete, don't set the HANG flag in gpgme_wait (note
467 that this will return to your program more often than the idle
470 * gpgme_wait can return NULL even if hang is true, if an error
471 occurs. In that case *status contains the error code.
473 * gpgme_get_engine_info was radically changed. Instead an XML
474 string, an info structure of the new type gpgme_engine_info_t is
475 returned. This makes it easier and more robust to evaluate the
476 information in an application.
478 * The new function gpgme_get_protocol_name can be used to convert a
479 gpgme_protocol_t value into a string.
481 * The status of a context operation is not checked anymore. Starting
482 a new operation will silently cancel the previous one. Calling a
483 function that requires you to have started an operation before without
484 doing so is undefined.
486 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
487 gpgme_op_genkey_result function to retrieve a gpgme_genkey_result_t
488 pointer to a structure which contains the fingerprint. This also
489 works with gpgme_op_genkey_start. The structure also provides
490 other information about the generated keys.
495 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
497 printf ("%s\n", fpr);
501 gpgme_genkey_result_t result;
502 err = gpgme_op_genkey (ctx, NULL, NULL);
505 result = gpgme_op_genkey_result (ctx);
507 printf ("%s\n", result->fpr);
510 * The new gpgme_op_import_result function provides detailed
511 information about the result of an import operation in
512 gpgme_import_result_t and gpgme_import_status_t objects.
513 Thus, the gpgme_op_import_ext variant is deprecated.
515 * The new gpgme_op_sign_result function provides detailed information
516 about the result of a signing operation in gpgme_sign_result_t,
517 gpgme_invalid_key_t and gpgme_new_signature_t objects.
519 * The new gpgme_op_encrypt_result function provides detailed
520 information about the result of an encryption operation in
521 a GpgmeEncryptResult object.
523 * The new gpgme_op_decrypt_result function provides detailed
524 information about the result of a decryption operation in
525 a GpgmeDecryptResult object.
527 * The new gpgme_op_verify_result function provides detailed
528 information about the result of an verify operation in
529 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
530 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
531 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
532 and gpgme_get_notation is removed.
534 * GpgmeTrustItem objects have now directly accessible data, so the
535 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
536 accessor functions are deprecated. Also, reference counting is
537 available through gpgme_trust_item_ref and gpgme_trust_item_unref
538 (the gpgme_trust_item_release alias for the latter is deprecated).
540 * Keys are not cached internally anymore, so the force_update argument
541 to gpgme_get_key has been removed.
543 * GpgmeKey objects have now directly accessible data so the
544 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
545 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
546 functions are deprecated. Also, gpgme_key_release is now
547 deprecated. The gpgme_key_get_as_xml function has been dropped.
549 * Because all interfaces using attributes are deprecated, the
550 GpgmeAttr data type is also deprecated.
552 * The new gpgme_op_keylist_result function provides detailed
553 information about the result of a key listing operation in
554 a GpgmeKeyListResult object.
556 * Now that each function comes with its own result retrieval
557 interface, the generic gpgme_get_op_info interface is not useful
560 * The type and mode of data objects is not available anymore.
562 * Interface changes relative to the 0.4.0 release:
563 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
564 GpgmeCtx DEPRECATED: Use gpgme_ctx_t.
565 GpgmeData DEPRECATED: Use gpgme_data_t.
566 GpgmeError DEPRECATED: Use gpgme_error_t.
567 GpgmeDataEncoding DEPRECATED: Use gpgme_data_encoding_t.
568 GpgmeSigStat DEPRECATED: Use gpgme_sig_stat_t.
569 GpgmeSigMode DEPRECATED: Use gpgme_sig_mode_t.
570 GpgmeAttr DEPRECATED: Use gpgme_attr_t.
571 GpgmeValidity DEPRECATED: Use gpgme_validity_t.
572 GpgmeProtocol DEPRECATED: Use gpgme_protocol_t.
573 GpgmeKey DEPRECATED: Use gpgme_key_t.
574 GpgmePassphraseCb DEPRECATED: Use gpgme_passphrase_cb_t.
575 GpgmeProgressCb DEPRECATED: Use gpgme_progress_cb_t.
576 GpgmeIOCb DEPRECATED: Use gpgme_io_cb_t.
577 GpgmeRegisterIOCb DEPRECATED: Use gpgme_register_io_cb_t.
578 GpgmeRemoveIOCb DEPRECATED: Use gpgme_remove_io_cb_t.
579 GpgmeEventIO DEPRECATED: Use gpgme_event_io_t.
580 GpgmeEventIOCb DEPRECATED: Use gpgme_event_io_cb_t.
581 GpgmeIOCbs DEPRECATED: Use gpgme_io_cbs.
582 GpgmeDataReadCb DEPRECATED: Use gpgme_data_read_cb_t.
583 GpgmeDataWriteCb DEPRECATED: Use gpgme_data_write_cb_t.
584 GpgmeDataSeekCb DEPRECATED: Use gpgme_data_seek_cb_t.
585 GpgmeDataReleaseCb DEPRECATED: Use gpgme_data_release_cb_t.
586 GpgmeDataCbs DEPRECATED: Use gpgme_data_cbs_t.
587 GpgmeTrustItem DEPRECATED: Use gpgme_trust_item_t.
588 GpgmeStatusCode DEPRECATED: Use gpgme_status_code_t.
591 gpgme_recipients_t NEW
593 gpgme_data_encoding_t NEW
600 gpgme_passphrase_cb_t NEW
601 gpgme_progress_cb_t NEW
603 gpgme_register_io_cb_t NEW
604 gpgme_remove_io_cb_t NEW
606 gpgme_event_io_cb_t NEW
608 gpgme_data_read_cb_t NEW
609 gpgme_data_write_cb_t NEW
610 gpgme_data_seek_cb_t NEW
611 gpgme_data_release_cb_t NEW
613 gpgme_trust_item_t NEW
614 gpgme_status_code_t NEW
615 GPGME_{some error code} REMOVED! Use GPG_ERR_* from libgpg-error.
617 gpgme_err_source_t NEW
622 gpgme_error_from_errno NEW
623 gpgme_err_make_from_errno NEW
624 gpgme_err_code_from_errno NEW
625 gpgme_err_code_to_errno NEW
627 gpgme_io_cb_t CHANGED: Return type from void to GpgmeError.
628 gpgme_event_io_t CHANGED: New event type (all numbers changed).
629 gpgme_passphrase_cb_t CHANGED: Desc decomposed, write directly to FD.
630 gpgme_edit_cb_t CHANGED: Write directly to FD.
631 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
632 gpgme_op_verify CHANGED: Drop R_STAT argument.
633 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
634 gpgme_wait CHANGED: Can return NULL even if hang is true.
635 GpgmeIdleFunc REMOVED
636 gpgme_register_idle REMOVED
637 GpgmeRecipients REMOVED
638 gpgme_recipients_new REMOVED
639 gpgme_recipients_release REMOVED
640 gpgme_recipients_add_name REMOVED
641 gpgme_recipients_add_name_with_validity REMOVED
642 gpgme_recipients_count REMOVED
643 gpgme_recipients_enum_open REMOVED
644 gpgme_recipients_enum_read REMOVED
645 gpgme_recipients_enum_close REMOVED
646 gpgme_encrypt_flags_t NEW
647 GPGME_ENCRYPT_ALWAYS_TRUST NEW
648 gpgme_op_encrypt CHANGED: Recipients passed as gpgme_key_t[].
649 gpgme_op_encrypt_start CHANGED: Recipients passed as gpgme_key_t[].
650 gpgme_op_encrypt_sign CHANGED: Recipients passed as gpgme_key_t[].
651 gpgme_op_encrypt_sign_start CHANGED: Recipients passed as gpgme_key_t[].
652 gpgme_op_export_start CHANGED: User IDs passed as patterns.
653 gpgme_op_export CHANGED: User IDs passed as patterns.
654 gpgme_op_export_ext_start NEW
655 gpgme_op_export_ext NEW
656 gpgme_keylist_mode_t NEW
658 gpgme_engine_info_t NEW
659 gpgme_get_engine_info CHANGED: Return info structure instead XML.
660 gpgme_get_protocol_name NEW
661 gpgme_cancel REMOVED: Return error in callback directly.
662 gpgme_op_genkey CHANGED: FPR argument dropped.
663 gpgme_op_genkey_result NEW
664 gpgme_genkey_result_t NEW
665 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
666 gpgme_op_import_result NEW
667 gpgme_import_status_t NEW
668 gpgme_import_result_t NEW
669 gpgme_pubkey_algo_t NEW
670 gpgme_hash_algo_t NEW
671 gpgme_invalid_key_t NEW
672 gpgme_new_signature_t NEW
673 gpgme_sign_result_t NEW
674 gpgme_op_sign_result NEW
675 gpgme_pubkey_algo_name NEW
676 gpgme_hash_algo_name NEW
677 gpgme_encrypt_result_t NEW
678 gpgme_op_encrypt_result NEW
679 gpgme_decrypt_result_t NEW
680 gpgme_op_decrypt_result NEW
681 gpgme_verify_result_t NEW
682 gpgme_op_verify_result NEW
683 gpgme_get_notation REMOVED: Access verify result directly instead.
684 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
685 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
686 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
687 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
688 gpgme_get_sig_status DEPRECATED: Use verify result directly.
689 gpgme_trust_item_t CHANGED: Now has user accessible data members.
690 gpgme_trust_item_ref NEW
691 gpgme_trust_item_unref NEW
692 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
693 gpgme_trust_item_get_string_attr DEPRECATED
694 gpgme_trust_item_get_ulong_attr DEPRECATED
695 gpgme_get_key CHANGED: Removed force_update argument.
699 gpgme_key_t CHANGED: Now has user accessible data members.
700 gpgme_key_get_string_attr DEPRECATED
701 gpgme_key_get_ulong_attr DEPRECATED
702 gpgme_key_sig_get_string_attr DEPRECATED
703 gpgme_key_sig_get_ulong_attr DEPRECATED
704 gpgme_key_get_as_xml REMOVED
705 gpgme_key_list_result_t NEW
706 gpgme_op_keylist_result NEW
707 gpgme_get_op_info REMOVED
708 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
710 Noteworthy changes in version 0.4.0 (2002-12-23)
711 ------------------------------------------------
713 * Key generation returns the fingerprint of the generated key.
715 * New convenience function gpgme_get_key.
717 * Supports signatures of user IDs in keys via the new
718 GPGME_KEYLIST_MODE_SIGS keylist mode and the
719 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
720 interfaces. The XML info about a key also includes the signatures
723 * New data object interface, which is more flexible and transparent.
725 * Interface changes relative to the 0.3.9 release:
726 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
730 GpgmeDataReleaseCb NEW
732 gpgme_data_read CHANGED: Match read() closely.
733 gpgme_data_write CHANGED: Match write() closely.
735 gpgme_data_new_from_fd NEW
736 gpgme_data_new_from_stream NEW
737 gpgme_data_new_from_cbs NEW
738 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
739 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
740 gpgme_data_get_type REMOVED: No replacement.
741 gpgme_op_verify CHANGED: Take different data objects for
742 signed text and plain text.
743 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
744 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
745 gpgme_op_genkey CHANGED: New parameter FPR.
746 GPGME_KEYLIST_MODE_SIGS NEW
747 gpgme_key_sig_get_string_attr NEW
748 gpgme_key_sig_get_ulong_attr NEW
750 GPGME_ATTR_SIG_CLASS NEW
751 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
753 Noteworthy changes in version 0.3.16 (2003-11-19)
754 -------------------------------------------------
756 * Compatibility fixes for GnuPG 1.9.x
758 Noteworthy changes in version 0.3.15 (2003-02-18)
759 -------------------------------------------------
761 * The progress status is sent via the progress callbacks in
764 * Bug fix for signing operations with explicit signer settings for
767 Noteworthy changes in version 0.3.14 (2002-12-04)
768 -------------------------------------------------
770 * GPGME-Plug is now in its own package "cryptplug".
772 * Workaround for a setlocale problem. Fixed a segv related to not
773 correctly as closed marked file descriptors.
775 Noteworthy changes in version 0.3.13 (2002-11-20)
776 -------------------------------------------------
778 * Release due to changes in gpgmeplug.
780 Noteworthy changes in version 0.3.12 (2002-10-15)
781 -------------------------------------------------
783 * Fixed some bux with key listings.
785 * The development has been branched to clean up some API issues.
786 This 0.3 series will be kept for compatibility reasons; so do don't
789 Noteworthy changes in version 0.3.11 (2002-09-20)
790 -------------------------------------------------
794 Noteworthy changes in version 0.3.10 (2002-09-02)
795 -------------------------------------------------
797 * Setting the signing keys for the CMS protocol does now work.
799 * The signers setting is honoured by gpgme_op_edit.
801 Noteworthy changes in version 0.3.9 (2002-08-21)
802 ------------------------------------------------
804 * A spec file for creating RPMs has been added.
806 * An experimental interface to GnuPG's --edit-key functionality is
807 introduced, see gpgme_op_edit.
809 * The new gpgme_import_ext function provides a convenient access to
810 the number of processed keys.
812 * Interface changes relative to the 0.3.8 release:
813 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
816 gpgme_op_edit_start NEW
818 gpgme_op_import_ext NEW
819 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
821 Noteworthy changes in version 0.3.8 (2002-06-25)
822 ------------------------------------------------
824 * It is possible to use an outside event loop for the I/O to the
825 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
827 * Interface changes relative to the 0.3.6 release:
828 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
830 GpgmeRegisterIOCb NEW
834 struct GpgmeIOCbs NEW
837 GPGME_ATTR_ERRTOK NEW
838 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
840 Noteworthy changes in version 0.3.7 (2002-06-04)
841 ------------------------------------------------
843 * GPGME_ATTR_OTRUST is implemented now.
845 * A first step toward thread safeness has been achieved, see the
846 documentation for details. Supported thread libraries are pthread
849 Noteworthy changes in version 0.3.6 (2002-05-03)
850 ------------------------------------------------
852 * All error output of the gpgsm backend is send to the bit bucket.
854 * The signature verification functions are extended. Instead of
855 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
856 expired signatures. 2 new functions may be used to retrieve more
857 detailed information like the signature expiration time and a
858 validity information of the key without an extra key looking.
860 * The current passphrase callback and progress meter callback can be
861 retrieved with the new functions gpgme_get_passphrase_cb and
862 gpgme_get_progress_cb respectively.
864 * Interface changes relative to the 0.3.5 release:
865 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
866 gpgme_get_passphrase_cb NEW
867 gpgme_get_progress_cb NEW
868 GpgmeDataEncoding NEW
869 gpgme_data_set_encoding NEW
870 gpgme_data_get_encoding NEW
871 GPGME_SIG_STAT_GOOD_EXP NEW
872 GPGME_SIG_STAT_GOOD_EXPKEY NEW
873 gpgme_op_verify CHANGED: Returns more status codes.
874 GPGME_ATTR_SIG_STATUS NEW
875 gpgme_get_sig_string_attr NEW
876 gpgme_get_sig_ulong_attr NEW
877 gpgme_get_protocol NEW
878 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
880 Noteworthy changes in version 0.3.5 (2002-04-01)
881 ------------------------------------------------
883 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
884 case, symmetric encryption is performed. Note that this requires a
885 passphrase from the user.
887 * More information is returned for X.509 certificates.
889 * Interface changes relative to the 0.3.4 release:
890 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
891 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
892 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
894 Noteworthy changes in version 0.3.4 (2002-03-04)
895 ------------------------------------------------
897 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
898 some recipients have been invalid, whereas earlier versions
899 succeeded in this case. The plaintext is still encrypted for all valid
900 recipients, so the application might take this error as a hint that
901 the ciphertext is not usable for all requested recipients.
902 Information about invalid recipients is available with gpgme_get_op_info.
904 * gpgme_op_verify now allows to pass an uninitialized data object as
905 its plaintext argument to check for normal and cleartext
906 signatures. The plaintext is then returned in the data object.
908 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
909 to set and get the number of certifications to include in S/MIME
912 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
913 to encrypt and sign a message in a combined operation.
915 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
917 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
919 * Interface changes relative to the 0.3.3 release:
920 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
921 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
922 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
923 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
924 gpgme_set_include_certs NEW
925 gpgme_get_include_certs NEW
926 gpgme_op_encrypt_sign NEW
927 gpgme_op_encrypt_sign_start NEW
928 gpgme_op_keylist_ext_start NEW
929 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
931 Noteworthy changes in version 0.3.3 (2002-02-12)
932 ------------------------------------------------
934 * Fix the Makefile in jnlib.
936 * Fix the test suite (hopefully). It should clean up all its state
937 with `make check' now.
940 Noteworthy changes in version 0.3.2 (2002-02-10)
941 ------------------------------------------------
943 * Remove erroneous dependency on libgcrypt in jnlib.
946 Noteworthy changes in version 0.3.1 (2002-02-09)
947 ------------------------------------------------
949 * There is a Texinfo manual documenting the API.
951 * The gpgme_set_keylist_mode function returns an error, and changed
952 its meaning. It is no longer usable to select between normal and
953 fast mode (newer versions of GnuPG will always be fast), but
954 selects between local keyring, remote keyserver, or both.
955 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
956 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
957 current setting, a fucntion gpgme_get_keylist_mode was added to
958 retrieve the current mode.
960 * gpgme_wait accepts a new argument STATUS to return the error status
961 of the operation on the context. Its definition is closer to
962 waitpid() now than before.
964 * The LENGTH argument to gpgme_data_new_from_filepart changed its
965 type from off_t to the unsigned size_t.
967 * The R_HD argument to the GpgmePassphraseCb type changed its type
968 from void* to void**.
970 * New interface gpgme_op_trustlist_end() to match
971 gpgme_op_keylist_end().
973 * The CryptPlug modules have been renamed to gpgme-openpgp and
974 gpgme-smime, and they are installed in pkglibdir by `make install'.
976 * An idle function can be registered with gpgme_register_idle().
978 * The GpgSM backend supports key generation with gpgme_op_genkey().
980 * Interface changes relative to the 0.3.0 release:
981 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
982 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
983 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
984 gpgme_wait CHANGED: New argument STATUS.
985 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
986 The function has a new meaning!
987 gpgme_get_keylist_mode NEW
988 GPGME_KEYLIST_MODE_LOCAL NEW
989 GPGME_KEYLIST_MODE_EXTERN NEW
990 gpgme_op_trustlist_next NEW
992 gpgme_register_idle NEW
993 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
995 Noteworthy changes in version 0.3.0 (2001-12-19)
996 ------------------------------------------------
998 * New interface gpgme_set_protocol() to set the protocol and thus the
999 crypto engine to be used by the context. Currently, the OpenPGP
1000 and the CMS protocols are supported. They are specified by the new
1001 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
1002 A new context uses the OpenPGP engine by default.
1004 * gpgme_get_engine_info() returns information for all crypto engines
1005 compiled into the library. The XML format has changed. To
1006 reliably get the version of a crypto engine, the <version> tag
1007 after the appropriate <protocol> tag has to be looked for.
1009 * New interface gpgme_engine_check_version(), obsoleting
1010 gpgme_check_engine(). Check the version of all engines you are
1011 supporting in your software.
1013 * GpgmeKey lists the user ids in the order as they are returned by
1014 GnuPG, first the primary key with index 0, then the sub-user ids.
1016 * New operation gpgme_op_decrypt_verify() to decrypt and verify
1017 signatures simultaneously.
1019 * The new interface gpgme_op_keylist_end() terminates a pending
1020 keylist operation. A keylist operation is also terminated when
1021 gpgme_op_keylist_next() returns GPGME_EOF.
1023 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
1024 cross-compiled, or even compiled without support for GnuPG
1027 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
1028 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
1029 in the path, but it can also be compiled without support for GpgSM
1030 (`--without-gpgsm').
1032 * CryptPlug modules for GPGME are included and can be enabled at
1033 configure time (`--enable-gpgmeplug'). There is one module which
1034 uses the GnuPG engine (`gpgmeplug') and one module which uses the
1035 GpgSM engine (`gpgsmplug').
1037 * Interface changes relative to the latest 0.2.x release:
1038 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1039 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
1040 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
1041 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
1042 gpgme_get_engine_info CHANGED: New format, extended content.
1043 gpgme_engine_check_version NEW
1044 gpgme_decrypt_verify_start NEW
1045 gpgme_decrypt_verify NEW
1046 gpgme_op_keylist_next NEW
1047 gpgme_set_protocol NEW
1048 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1051 Noteworthy changes in version 0.2.3 (2001-09-17)
1052 ------------------------------------------------
1054 * New function gpgme_get_op_info which can be used to get the micalg
1055 parameter needed for MOSS.
1057 * New functions gpgme_get_armor and gpgme_get_textmode.
1059 * The usual bug fixes and some minor functionality improvements.
1061 * Added a simple encryption component for MS-Windows; however the
1062 build procedure might have some problems.
1065 Noteworthy changes in version 0.2.2 (2001-06-12)
1066 ------------------------------------------------
1068 * Implemented a key cache.
1070 * Fixed a race condition under W32 and some other bug fixes.
1073 Noteworthy changes in version 0.2.1 (2001-04-02)
1074 ------------------------------------------------
1076 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
1078 * Handle GnuPG's new key capabilities output and support revocation
1081 * Made the W32 support more robust.
1084 Copyright 2001, 2002, 2003, 2004 g10 Code GmbH
1086 This file is free software; as a special exception the author gives
1087 unlimited permission to copy and/or distribute it, with or without
1088 modifications, as long as this notice is preserved.
1090 This file is distributed in the hope that it will be useful, but
1091 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
1092 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.