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