1 Noteworthy changes in version 0.4.1 (unreleased)
2 ------------------------------------------------
4 * GPGME_ATTR_IS_SECRET is not anymore representable as a string.
6 * gpgme_op_verify and gpgme_op_decrypt_verify don't return a status
7 summary anymore. Use gpgme_get_sig_status to retrieve the individual
10 * GpgmeIOCb changed from a void function to a function returning a
11 GpgmeError value. However, it will always return 0, so you can
12 safely ignore the return value.
14 * A new I/O callback event GPGME_EVENT_START has been added. The new
15 requirement is that you must wait until this event until you are
16 allowed to call the I/O callback handlers previously registered for
17 this context operation. Calling I/O callback functions for this
18 context operation before the start event happened is unsafe because
19 it can lead to race conditions in a multi-threaded environment.
21 * The idle function feature has been removed. It was not precisely
22 defined in a multi-threaded environment and is obsoleted by the
23 user I/O callback functions. If you still need a simple way to
24 call something while waiting on one or multiple asynchronous
25 operations to complete, don't set the HANG flag in gpgme_wait (note
26 that this will return to your program more often than the idle
29 * gpgme_wait can return NULL even if hang is true, if an error
30 occurs. In that case *status contains the error code.
32 * gpgme_get_engine_info was radically changed. Instead an XML
33 string, an info structure of the new type GpgmeEngineInfo is
34 returned. This makes it easier and more robust to evaluate the
35 information in an application.
37 * The new function gpgme_get_protocol_name can be used to convert a
38 GpgmeProtocol value into a string.
40 * The GpgmePassphraseCb type now returns a GpgmeError value, and
41 returns the password string in a new parameter. The gpgme_cancel
42 function has been removed, just return GPGME_Canceled in the
43 passphrase callback directly.
45 * The status of a context operation is not checked anymore, so the
46 errors GPGME_Busy and GPGME_No_Request can not occur anymore.
48 * For clarity and better reusability, the error codes
49 GPGME_No_Recipients, GPGME_Invalid_Recipient and
50 GPGME_No_Passphrase have been renamed to GPGME_No_UserID,
51 GPGME_Invalid_UserID and GPGME_Bad_Passphrase resp.
53 * The FPR argument to gpgme_op_genkey was removed. Instead, use the
54 gpgme_op_genkey_result function to retrieve a GpgmeGenKeyResult
55 pointer to a structure which contains the fingerprint. This also
56 works with gpgme_op_genkey. The structure also provides other
57 information about the generated keys.
62 err = gpgme_op_genkey (ctx, NULL, NULL, &fpr);
68 GpgmeGenKeyResult result;
69 err = gpgme_op_genkey (ctx, NULL, NULL);
72 result = gpgme_op_genkey_result (ctx);
74 printf ("%s\n", result->fpr);
77 * The new gpgme_op_import_result function provides detailed
78 information about the result of an import operation in
79 GpgmeImportResult and GpgmeImportStatus objects. Thus, the
80 gpgme_op_import_ext variant is deprecated.
82 * The new gpgme_op_sign_result function provides detailed information
83 about the result of a signing operation in GpgmeSignResult,
84 GpgmeInvalidUserID and GpgmeNewSignature objects.
86 * The new gpgme_op_encrypt_result function provides detailed
87 information about the result of an encryption operation in
88 a GpgmeEncryptResult object.
90 * The new gpgme_op_decrypt_result function provides detailed
91 information about the result of a decryption operation in
92 a GpgmeDecryptResult object.
94 * The new gpgme_op_verify_result function provides detailed
95 information about the result of an verify operation in
96 a GpgmeVerifyResult object. Because of this, the GPGME_SIG_STAT_*
97 values, gpgme_get_sig_status, gpgme_get_sig_ulong_attr,
98 gpgme_get_sig_string_attr and gpgme_get_sig_key are now deprecated,
99 and gpgme_get_notation is removed.
101 * GpgmeTrustItem objects have now directly accessible data, so the
102 gpgme_trust_item_get_string_attr and gpgme_trust_item_get_ulong_attr
103 accessor functions are deprecated. Also, reference counting is
104 available through gpgme_trust_item_ref and gpgme_trust_item_unref
105 (the gpgme_trust_item_release alias for the latter is deprecated).
107 * Keys are not cached internally anymore, so the force_update argument
108 to gpgme_get_key has been removed.
110 * GpgmeKey objects have now directly accessible data so the
111 gpgme_key_get_string_attr, gpgme_key_get_ulong_attr,
112 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
113 functions are deprecated. Also, gpgme_key_release is now
114 deprecated. The gpgme_key_get_as_xml function has been dropped.
116 * Because all interfaces using attributes are deprecated, the
117 GpgmeAttr data type is also deprecated.
119 * The new gpgme_op_keylist_result function provides detailed
120 information about the result of a key listing operation in
121 a GpgmeKeyListResult object.
123 * Interface changes relative to the 0.4.0 release:
124 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
125 GpgmeIOCb CHANGED: Return type from void to GpgmeError.
126 GpgmeEventIO CHANGED: New event type (all numbers changed).
127 gpgme_key_get_string_attr CHANGED: Don't handle GPGME_ATTR_IS_SECRET.
128 gpgme_op_verify CHANGED: Drop R_STAT argument.
129 gpgme_op_decrypt_verify CHANGED: Drop R_STAT argument.
130 gpgme_wait CHANGED: Can return NULL even if hang is true.
131 GpgmeIdleFunc REMOVED
132 gpgme_register_idle REMOVED
134 gpgme_get_engine_info CHANGED: Return info structure instead XML.
135 gpgme_get_protocol_name NEW
136 GpgmePassphraseCb CHANGED: Return error value, new argument.
137 gpgme_cancel REMOVED: Return error in callback directly.
138 GPGME_Busy DEPRECATED: Not in use.
139 GPGME_No_Request DEPRECATED: Not in use.
140 GPGME_No_Recipients DEPRECATED: Use GPGME_No_UserID.
142 GPGME_Invalid_Recipient DEPRECATED: Use GPGME_Invalid_UserID.
143 GPGME_Invalid_UserID NEW
144 GPGME_No_Passphrase DEPRECATED: Use GPGME_Bad_Passphrase.
145 GPGME_Bad_Passphrase NEW
146 gpgme_op_genkey CHANGED: FPR argument dropped.
147 gpgme_op_genkey_result NEW
148 GpgmeGenKeyResult NEW
149 gpgme_op_import_ext DEPRECATED: Use gpgme_op_import_result.
150 gpgme_op_import_result NEW
151 GpgmeImportStatus NEW
152 GpgmeImportResult NEW
155 GpgmeInvalidUserID NEW
156 GpgmeNewSignature NEW
158 gpgme_op_sign_result NEW
159 gpgme_pubkey_algo_name NEW
160 gpgme_hash_algo_name NEW
161 GpgmeEncryptResult NEW
162 gpgme_op_encrypt_result NEW
163 GpgmeDecryptResult NEW
164 gpgme_op_decrypt_result NEW
165 GpgmeVerifyResult NEW
166 gpgme_op_verify_result NEW
167 gpgme_get_notation REMOVED: Access verify result directly instead.
168 gpgme_get_sig_key DEPRECATED: Use gpgme_get_key with fingerprint.
169 gpgme_get_sig_ulong_attr DEPRECATED: Use verify result directly.
170 gpgme_get_sig_string_attr DEPRECATED: Use verify result directly.
171 GPGME_SIG_STAT_* DEPRECATED: Use error value in sig status.
172 gpgme_get_sig_status DEPRECATED: Use verify result directly.
173 GpgmeTrustItem CHANGED: Now has user accessible data members.
174 gpgme_trust_item_ref NEW
175 gpgme_trust_item_unref NEW
176 gpgme_trust_item_release DEPRECATED: Use gpgme_trust_item_unref.
177 gpgme_trust_item_get_string_attr DEPRECATED
178 gpgme_trust_item_get_ulong_attr DEPRECATED
179 gpgme_get_key CHANGED: Removed force_update argument.
183 GpgmeKey CHANGED: Now has user accessible data members.
184 gpgme_key_get_string_attr DEPRECATED
185 gpgme_key_get_ulong_attr DEPRECATED
186 gpgme_key_sig_get_string_attr DEPRECATED
187 gpgme_key_sig_get_ulong_attr DEPRECATED
188 gpgme_key_get_as_xml REMOVED
189 GpgmeKeyListResult NEW
190 gpgme_op_keylist_result NEW
191 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
193 Noteworthy changes in version 0.4.0 (2002-12-23)
194 ------------------------------------------------
196 * Key generation returns the fingerprint of the generated key.
198 * New convenience function gpgme_get_key.
200 * Supports signatures of user IDs in keys via the new
201 GPGME_KEYLIST_MODE_SIGS keylist mode and the
202 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
203 interfaces. The XML info about a key also includes the signatures
206 * New data object interface, which is more flexible and transparent.
208 * Interface changes relative to the 0.3.9 release:
209 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
213 GpgmeDataReleaseCb NEW
215 gpgme_data_read CHANGED: Match read() closely.
216 gpgme_data_write CHANGED: Match write() closely.
218 gpgme_data_new_from_fd NEW
219 gpgme_data_new_from_stream NEW
220 gpgme_data_new_from_cbs NEW
221 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
222 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
223 gpgme_data_get_type REMOVED: No replacement.
224 gpgme_op_verify CHANGED: Take different data objects for
225 signed text and plain text.
226 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
227 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
228 gpgme_op_genkey CHANGED: New parameter FPR.
229 GPGME_KEYLIST_MODE_SIGS NEW
230 gpgme_key_sig_get_string_attr NEW
231 gpgme_key_sig_get_ulong_attr NEW
233 GPGME_ATTR_SIG_CLASS NEW
234 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
236 Noteworthy changes in version 0.3.15 (2003-02-18)
237 -------------------------------------------------
239 * The progress status is sent via the progress callbacks in
242 * Bug fix for signing operations with explicit signer settings for
245 Noteworthy changes in version 0.3.14 (2002-12-04)
246 -------------------------------------------------
248 * GPGME-Plug is now in its own package "cryptplug".
250 * Workaround for a setlocale problem. Fixed a segv related to not
251 correctly as closed marked file descriptors.
253 Noteworthy changes in version 0.3.13 (2002-11-20)
254 -------------------------------------------------
256 * Release due to changes in gpgmeplug.
258 Noteworthy changes in version 0.3.12 (2002-10-15)
259 -------------------------------------------------
261 * Fixed some bux with key listings.
263 * The development has been branched to clean up some API issues.
264 This 0.3 series will be kept for compatibility reasons; so do don't
267 Noteworthy changes in version 0.3.11 (2002-09-20)
268 -------------------------------------------------
272 Noteworthy changes in version 0.3.10 (2002-09-02)
273 -------------------------------------------------
275 * Setting the signing keys for the CMS protocol does now work.
277 * The signers setting is honoured by gpgme_op_edit.
279 Noteworthy changes in version 0.3.9 (2002-08-21)
280 ------------------------------------------------
282 * A spec file for creating RPMs has been added.
284 * An experimental interface to GnuPG's --edit-key functionality is
285 introduced, see gpgme_op_edit.
287 * The new gpgme_import_ext function provides a convenient access to
288 the number of processed keys.
290 * Interface changes relative to the 0.3.8 release:
291 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
294 gpgme_op_edit_start NEW
296 gpgme_op_import_ext NEW
297 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
299 Noteworthy changes in version 0.3.8 (2002-06-25)
300 ------------------------------------------------
302 * It is possible to use an outside event loop for the I/O to the
303 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
305 * Interface changes relative to the 0.3.6 release:
306 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
308 GpgmeRegisterIOCb NEW
312 struct GpgmeIOCbs NEW
315 GPGME_ATTR_ERRTOK NEW
316 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
318 Noteworthy changes in version 0.3.7 (2002-06-04)
319 ------------------------------------------------
321 * GPGME_ATTR_OTRUST is implemented now.
323 * A first step toward thread safeness has been achieved, see the
324 documentation for details. Supported thread libraries are pthread
327 Noteworthy changes in version 0.3.6 (2002-05-03)
328 ------------------------------------------------
330 * All error output of the gpgsm backend is send to the bit bucket.
332 * The signature verification functions are extended. Instead of
333 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
334 expired signatures. 2 new functions may be used to retrieve more
335 detailed information like the signature expiration time and a
336 validity information of the key without an extra key looking.
338 * The current passphrase callback and progress meter callback can be
339 retrieved with the new functions gpgme_get_passphrase_cb and
340 gpgme_get_progress_cb respectively.
342 * Interface changes relative to the 0.3.5 release:
343 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
344 gpgme_get_passphrase_cb NEW
345 gpgme_get_progress_cb NEW
346 GpgmeDataEncoding NEW
347 gpgme_data_set_encoding NEW
348 gpgme_data_get_encoding NEW
349 GPGME_SIG_STAT_GOOD_EXP NEW
350 GPGME_SIG_STAT_GOOD_EXPKEY NEW
351 gpgme_op_verify CHANGED: Returns more status codes.
352 GPGME_ATTR_SIG_STATUS NEW
353 gpgme_get_sig_string_attr NEW
354 gpgme_get_sig_ulong_attr NEW
355 gpgme_get_protocol NEW
356 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
358 Noteworthy changes in version 0.3.5 (2002-04-01)
359 ------------------------------------------------
361 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
362 case, symmetric encryption is performed. Note that this requires a
363 passphrase from the user.
365 * More information is returned for X.509 certificates.
367 * Interface changes relative to the 0.3.4 release:
368 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
369 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
370 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
372 Noteworthy changes in version 0.3.4 (2002-03-04)
373 ------------------------------------------------
375 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
376 some recipients have been invalid, whereas earlier versions
377 succeeded in this case. The plaintext is still encrypted for all valid
378 recipients, so the application might take this error as a hint that
379 the ciphertext is not usable for all requested recipients.
380 Information about invalid recipients is available with gpgme_get_op_info.
382 * gpgme_op_verify now allows to pass an uninitialized data object as
383 its plaintext argument to check for normal and cleartext
384 signatures. The plaintext is then returned in the data object.
386 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
387 to set and get the number of certifications to include in S/MIME
390 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
391 to encrypt and sign a message in a combined operation.
393 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
395 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
397 * Interface changes relative to the 0.3.3 release:
398 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
399 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
400 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
401 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
402 gpgme_set_include_certs NEW
403 gpgme_get_include_certs NEW
404 gpgme_op_encrypt_sign NEW
405 gpgme_op_encrypt_sign_start NEW
406 gpgme_op_keylist_ext_start NEW
407 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
409 Noteworthy changes in version 0.3.3 (2002-02-12)
410 ------------------------------------------------
412 * Fix the Makefile in jnlib.
414 * Fix the test suite (hopefully). It should clean up all its state
415 with `make check' now.
418 Noteworthy changes in version 0.3.2 (2002-02-10)
419 ------------------------------------------------
421 * Remove erroneous dependency on libgcrypt in jnlib.
424 Noteworthy changes in version 0.3.1 (2002-02-09)
425 ------------------------------------------------
427 * There is a Texinfo manual documenting the API.
429 * The gpgme_set_keylist_mode function returns an error, and changed
430 its meaning. It is no longer usable to select between normal and
431 fast mode (newer versions of GnuPG will always be fast), but
432 selects between local keyring, remote keyserver, or both.
433 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
434 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
435 current setting, a fucntion gpgme_get_keylist_mode was added to
436 retrieve the current mode.
438 * gpgme_wait accepts a new argument STATUS to return the error status
439 of the operation on the context. Its definition is closer to
440 waitpid() now than before.
442 * The LENGTH argument to gpgme_data_new_from_filepart changed its
443 type from off_t to the unsigned size_t.
445 * The R_HD argument to the GpgmePassphraseCb type changed its type
446 from void* to void**.
448 * New interface gpgme_op_trustlist_end() to match
449 gpgme_op_keylist_end().
451 * The CryptPlug modules have been renamed to gpgme-openpgp and
452 gpgme-smime, and they are installed in pkglibdir by `make install'.
454 * An idle function can be registered with gpgme_register_idle().
456 * The GpgSM backend supports key generation with gpgme_op_genkey().
458 * Interface changes relative to the 0.3.0 release:
459 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
460 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
461 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
462 gpgme_wait CHANGED: New argument STATUS.
463 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
464 The function has a new meaning!
465 gpgme_get_keylist_mode NEW
466 GPGME_KEYLIST_MODE_LOCAL NEW
467 GPGME_KEYLIST_MODE_EXTERN NEW
468 gpgme_op_trustlist_next NEW
470 gpgme_register_idle NEW
471 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
473 Noteworthy changes in version 0.3.0 (2001-12-19)
474 ------------------------------------------------
476 * New interface gpgme_set_protocol() to set the protocol and thus the
477 crypto engine to be used by the context. Currently, the OpenPGP
478 and the CMS protocols are supported. They are specified by the new
479 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
480 A new context uses the OpenPGP engine by default.
482 * gpgme_get_engine_info() returns information for all crypto engines
483 compiled into the library. The XML format has changed. To
484 reliably get the version of a crypto engine, the <version> tag
485 after the appropriate <protocol> tag has to be looked for.
487 * New interface gpgme_engine_check_version(), obsoleting
488 gpgme_check_engine(). Check the version of all engines you are
489 supporting in your software.
491 * GpgmeKey lists the user ids in the order as they are returned by
492 GnuPG, first the primary key with index 0, then the sub-user ids.
494 * New operation gpgme_op_decrypt_verify() to decrypt and verify
495 signatures simultaneously.
497 * The new interface gpgme_op_keylist_end() terminates a pending
498 keylist operation. A keylist operation is also terminated when
499 gpgme_op_keylist_next() returns GPGME_EOF.
501 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
502 cross-compiled, or even compiled without support for GnuPG
505 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
506 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
507 in the path, but it can also be compiled without support for GpgSM
510 * CryptPlug modules for GPGME are included and can be enabled at
511 configure time (`--enable-gpgmeplug'). There is one module which
512 uses the GnuPG engine (`gpgmeplug') and one module which uses the
513 GpgSM engine (`gpgsmplug').
515 * Interface changes relative to the latest 0.2.x release:
516 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
517 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
518 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
519 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
520 gpgme_get_engine_info CHANGED: New format, extended content.
521 gpgme_engine_check_version NEW
522 gpgme_decrypt_verify_start NEW
523 gpgme_decrypt_verify NEW
524 gpgme_op_keylist_next NEW
525 gpgme_set_protocol NEW
526 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
529 Noteworthy changes in version 0.2.3 (2001-09-17)
530 ------------------------------------------------
532 * New function gpgme_get_op_info which can be used to get the micalg
533 parameter needed for MOSS.
535 * New functions gpgme_get_armor and gpgme_get_textmode.
537 * The usual bug fixes and some minor functionality improvements.
539 * Added a simple encryption component for MS-Windows; however the
540 build procedure might have some problems.
543 Noteworthy changes in version 0.2.2 (2001-06-12)
544 ------------------------------------------------
546 * Implemented a key cache.
548 * Fixed a race condition under W32 and some other bug fixes.
551 Noteworthy changes in version 0.2.1 (2001-04-02)
552 ------------------------------------------------
554 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
556 * Handle GnuPG's new key capabilities output and support revocation
559 * Made the W32 support more robust.
562 Copyright 2001, 2002 g10 Code GmbH
564 This file is free software; as a special exception the author gives
565 unlimited permission to copy and/or distribute it, with or without
566 modifications, as long as this notice is preserved.
568 This file is distributed in the hope that it will be useful, but
569 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
570 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.