1 Noteworthy changes in version 0.3.10 (2002-09-02)
2 -------------------------------------------------
4 * Setting the signing keys for the CMS protocol does now work.
6 * The signers setting is honoured by gpgme_op_edit.
8 Noteworthy changes in version 0.3.9 (2002-08-21)
9 ------------------------------------------------
11 * A spec file for creating RPMs has been added.
13 * An experimental interface to GnuPG's --edit-key functionality is
14 introduced, see gpgme_op_edit.
16 * The new gpgme_import_ext function provides a convenient access to
17 the number of processed keys.
19 * Interface changes relative to the 0.3.8 release:
20 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
23 gpgme_op_edit_start NEW
25 gpgme_op_import_ext NEW
26 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
28 Noteworthy changes in version 0.3.8 (2002-06-25)
29 ------------------------------------------------
31 * It is possible to use an outside event loop for the I/O to the
32 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
34 * Interface changes relative to the 0.3.6 release:
35 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
45 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
47 Noteworthy changes in version 0.3.7 (2002-06-04)
48 ------------------------------------------------
50 * GPGME_ATTR_OTRUST is implemented now.
52 * A first step toward thread safeness has been achieved, see the
53 documentation for details. Supported thread libraries are pthread
56 Noteworthy changes in version 0.3.6 (2002-05-03)
57 ------------------------------------------------
59 * All error output of the gpgsm backend is send to the bit bucket.
61 * The signature verification functions are extended. Instead of
62 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
63 expired signatures. 2 new functions may be used to retrieve more
64 detailed information like the signature expiration time and a
65 validity information of the key without an extra key looking.
67 * The current passphrase callback and progress meter callback can be
68 retrieved with the new functions gpgme_get_passphrase_cb and
69 gpgme_get_progress_cb respectively.
71 * Interface changes relative to the 0.3.5 release:
72 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
73 gpgme_get_passphrase_cb NEW
74 gpgme_get_progress_cb NEW
76 gpgme_data_set_encoding NEW
77 gpgme_data_get_encoding NEW
78 GPGME_SIG_STAT_GOOD_EXP NEW
79 GPGME_SIG_STAT_GOOD_EXPKEY NEW
80 gpgme_op_verify CHANGED: Returns more status codes.
81 GPGME_ATTR_SIG_STATUS NEW
82 gpgme_get_sig_string_attr NEW
83 gpgme_get_sig_ulong_attr NEW
84 gpgme_get_protocol NEW
85 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
87 Noteworthy changes in version 0.3.5 (2002-04-01)
88 ------------------------------------------------
90 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
91 case, symmetric encryption is performed. Note that this requires a
92 passphrase from the user.
94 * More information is returned for X.509 certificates.
96 * Interface changes relative to the 0.3.4 release:
97 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
98 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
99 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
101 Noteworthy changes in version 0.3.4 (2002-03-04)
102 ------------------------------------------------
104 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
105 some recipients have been invalid, whereas earlier versions
106 succeeded in this case. The plaintext is still encrypted for all valid
107 recipients, so the application might take this error as a hint that
108 the ciphertext is not usable for all requested recipients.
109 Information about invalid recipients is available with gpgme_get_op_info.
111 * gpgme_op_verify now allows to pass an uninitialized data object as
112 its plaintext argument to check for normal and cleartext
113 signatures. The plaintext is then returned in the data object.
115 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
116 to set and get the number of certifications to include in S/MIME
119 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
120 to encrypt and sign a message in a combined operation.
122 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
124 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
126 * Interface changes relative to the 0.3.3 release:
127 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
128 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
129 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
130 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
131 gpgme_set_include_certs NEW
132 gpgme_get_include_certs NEW
133 gpgme_op_encrypt_sign NEW
134 gpgme_op_encrypt_sign_start NEW
135 gpgme_op_keylist_ext_start NEW
136 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
138 Noteworthy changes in version 0.3.3 (2002-02-12)
139 ------------------------------------------------
141 * Fix the Makefile in jnlib.
143 * Fix the test suite (hopefully). It should clean up all its state
144 with `make check' now.
147 Noteworthy changes in version 0.3.2 (2002-02-10)
148 ------------------------------------------------
150 * Remove erroneous dependency on libgcrypt in jnlib.
153 Noteworthy changes in version 0.3.1 (2002-02-09)
154 ------------------------------------------------
156 * There is a Texinfo manual documenting the API.
158 * The gpgme_set_keylist_mode function returns an error, and changed
159 its meaning. It is no longer usable to select between normal and
160 fast mode (newer versions of GnuPG will always be fast), but
161 selects between local keyring, remote keyserver, or both.
162 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
163 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
164 current setting, a fucntion gpgme_get_keylist_mode was added to
165 retrieve the current mode.
167 * gpgme_wait accepts a new argument STATUS to return the error status
168 of the operation on the context. Its definition is closer to
169 waitpid() now than before.
171 * The LENGTH argument to gpgme_data_new_from_filepart changed its
172 type from off_t to the unsigned size_t.
174 * The R_HD argument to the GpgmePassphraseCb type changed its type
175 from void* to void**.
177 * New interface gpgme_op_trustlist_end() to match
178 gpgme_op_keylist_end().
180 * The CryptPlug modules have been renamed to gpgme-openpgp and
181 gpgme-smime, and they are installed in pkglibdir by `make install'.
183 * An idle function can be registered with gpgme_register_idle().
185 * The GpgSM backend supports key generation with gpgme_op_genkey().
187 * Interface changes relative to the 0.3.0 release:
188 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
189 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
190 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
191 gpgme_wait CHANGED: New argument STATUS.
192 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
193 The function has a new meaning!
194 gpgme_get_keylist_mode NEW
195 GPGME_KEYLIST_MODE_LOCAL NEW
196 GPGME_KEYLIST_MODE_EXTERN NEW
197 gpgme_op_trustlist_next NEW
199 gpgme_register_idle NEW
200 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
202 Noteworthy changes in version 0.3.0 (2001-12-19)
203 ------------------------------------------------
205 * New interface gpgme_set_protocol() to set the protocol and thus the
206 crypto engine to be used by the context. Currently, the OpenPGP
207 and the CMS protocols are supported. They are specified by the new
208 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
209 A new context uses the OpenPGP engine by default.
211 * gpgme_get_engine_info() returns information for all crypto engines
212 compiled into the library. The XML format has changed. To
213 reliably get the version of a crypto engine, the <version> tag
214 after the appropriate <protocol> tag has to be looked for.
216 * New interface gpgme_engine_check_version(), obsoleting
217 gpgme_check_engine(). Check the version of all engines you are
218 supporting in your software.
220 * GpgmeKey lists the user ids in the order as they are returned by
221 GnuPG, first the primary key with index 0, then the sub-user ids.
223 * New operation gpgme_op_decrypt_verify() to decrypt and verify
224 signatures simultaneously.
226 * The new interface gpgme_op_keylist_end() terminates a pending
227 keylist operation. A keylist operation is also terminated when
228 gpgme_op_keylist_next() returns GPGME_EOF.
230 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
231 cross-compiled, or even compiled without support for GnuPG
234 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
235 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
236 in the path, but it can also be compiled without support for GpgSM
239 * CryptPlug modules for GPGME are included and can be enabled at
240 configure time (`--enable-gpgmeplug'). There is one module which
241 uses the GnuPG engine (`gpgmeplug') and one module which uses the
242 GpgSM engine (`gpgsmplug').
244 * Interface changes relative to the latest 0.2.x release:
245 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
246 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
247 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
248 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
249 gpgme_get_engine_info CHANGED: New format, extended content.
250 gpgme_engine_check_version NEW
251 gpgme_decrypt_verify_start NEW
252 gpgme_decrypt_verify NEW
253 gpgme_op_keylist_next NEW
254 gpgme_set_protocol NEW
255 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
258 Noteworthy changes in version 0.2.3 (2001-09-17)
259 ------------------------------------------------
261 * New function gpgme_get_op_info which can be used to get the micalg
262 parameter needed for MOSS.
264 * New functions gpgme_get_armor and gpgme_get_textmode.
266 * The usual bug fixes and some minor functionality improvements.
268 * Added a simple encryption component for MS-Windows; however the
269 build procedure might have some problems.
272 Noteworthy changes in version 0.2.2 (2001-06-12)
273 ------------------------------------------------
275 * Implemented a key cache.
277 * Fixed a race condition under W32 and some other bug fixes.
280 Noteworthy changes in version 0.2.1 (2001-04-02)
281 ------------------------------------------------
283 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
285 * Handle GnuPG's new key capabilities output and support revocation
288 * Made the W32 support more robust.
291 Copyright 2001, 2002 g10 Code GmbH
293 This file is free software; as a special exception the author gives
294 unlimited permission to copy and/or distribute it, with or without
295 modifications, as long as this notice is preserved.
297 This file is distributed in the hope that it will be useful, but
298 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
299 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.