1 Noteworthy changes in version 0.4.0 (unreleased)
2 ------------------------------------------------
4 * Supports signatures of user IDs in keys via the new
5 GPGME_KEYLIST_MODE_SIGS keylist mode and the
6 gpgme_key_sig_get_string_attr and gpgme_key_sig_get_ulong_attr
7 interfaces. The XML info about a key also includes the signatures
10 * New data object interface, which is more flexible and transparent.
12 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
16 GpgmeDataReleaseCb NEW
18 gpgme_data_read CHANGED: Match read() closely.
19 gpgme_data_write CHANGED: Match write() closely.
21 gpgme_data_new_from_fd NEW
22 gpgme_data_new_from_stream NEW
23 gpgme_data_new_from_cbs NEW
24 gpgme_data_rewind DEPRECATED: Replaced by gpgme_data_seek().
25 gpgme_data_new_from_read_cb DEPRECATED: Replaced by gpgme_data_from_cbs().
26 gpgme_data_get_type REMOVED: No replacement.
27 gpgme_op_verify CHANGED: Take different data objects for
28 signed text and plain text.
29 gpgme_op_verify_start CHANGED: See gpgme_op_verify.
30 gpgme_check_engine REMOVED: Deprecated since 0.3.0.
31 gpgme_op_genkey CHANGED: New parameter FPR.
32 GPGME_KEYLIST_MODE_SIGS NEW
33 gpgme_key_sig_get_string_attr NEW
34 gpgme_key_sig_get_ulong_attr NEW
36 GPGME_ATTR_SIG_CLASS NEW
37 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
39 Noteworthy changes in version 0.3.13 (2002-11-20)
40 -------------------------------------------------
42 * Release due to changes in gpgmeplug.
44 Noteworthy changes in version 0.3.12 (2002-10-15)
45 -------------------------------------------------
47 * Fixed some bux with key listings.
49 * The development has been branched to clean up some API issues.
50 This 0.3 series will be kept for compatibility reasons; so do don't
53 Noteworthy changes in version 0.3.11 (2002-09-20)
54 -------------------------------------------------
58 Noteworthy changes in version 0.3.10 (2002-09-02)
59 -------------------------------------------------
61 * Setting the signing keys for the CMS protocol does now work.
63 * The signers setting is honoured by gpgme_op_edit.
65 Noteworthy changes in version 0.3.9 (2002-08-21)
66 ------------------------------------------------
68 * A spec file for creating RPMs has been added.
70 * An experimental interface to GnuPG's --edit-key functionality is
71 introduced, see gpgme_op_edit.
73 * The new gpgme_import_ext function provides a convenient access to
74 the number of processed keys.
76 * Interface changes relative to the 0.3.8 release:
77 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
80 gpgme_op_edit_start NEW
82 gpgme_op_import_ext NEW
83 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
85 Noteworthy changes in version 0.3.8 (2002-06-25)
86 ------------------------------------------------
88 * It is possible to use an outside event loop for the I/O to the
89 crypto engine by setting the I/O callbacks with gpgme_set_io_cbs.
91 * Interface changes relative to the 0.3.6 release:
92 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
101 GPGME_ATTR_ERRTOK NEW
102 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
104 Noteworthy changes in version 0.3.7 (2002-06-04)
105 ------------------------------------------------
107 * GPGME_ATTR_OTRUST is implemented now.
109 * A first step toward thread safeness has been achieved, see the
110 documentation for details. Supported thread libraries are pthread
113 Noteworthy changes in version 0.3.6 (2002-05-03)
114 ------------------------------------------------
116 * All error output of the gpgsm backend is send to the bit bucket.
118 * The signature verification functions are extended. Instead of
119 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
120 expired signatures. 2 new functions may be used to retrieve more
121 detailed information like the signature expiration time and a
122 validity information of the key without an extra key looking.
124 * The current passphrase callback and progress meter callback can be
125 retrieved with the new functions gpgme_get_passphrase_cb and
126 gpgme_get_progress_cb respectively.
128 * Interface changes relative to the 0.3.5 release:
129 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
130 gpgme_get_passphrase_cb NEW
131 gpgme_get_progress_cb NEW
132 GpgmeDataEncoding NEW
133 gpgme_data_set_encoding NEW
134 gpgme_data_get_encoding NEW
135 GPGME_SIG_STAT_GOOD_EXP NEW
136 GPGME_SIG_STAT_GOOD_EXPKEY NEW
137 gpgme_op_verify CHANGED: Returns more status codes.
138 GPGME_ATTR_SIG_STATUS NEW
139 gpgme_get_sig_string_attr NEW
140 gpgme_get_sig_ulong_attr NEW
141 gpgme_get_protocol NEW
142 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
144 Noteworthy changes in version 0.3.5 (2002-04-01)
145 ------------------------------------------------
147 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
148 case, symmetric encryption is performed. Note that this requires a
149 passphrase from the user.
151 * More information is returned for X.509 certificates.
153 * Interface changes relative to the 0.3.4 release:
154 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
155 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
156 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
158 Noteworthy changes in version 0.3.4 (2002-03-04)
159 ------------------------------------------------
161 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
162 some recipients have been invalid, whereas earlier versions
163 succeeded in this case. The plaintext is still encrypted for all valid
164 recipients, so the application might take this error as a hint that
165 the ciphertext is not usable for all requested recipients.
166 Information about invalid recipients is available with gpgme_get_op_info.
168 * gpgme_op_verify now allows to pass an uninitialized data object as
169 its plaintext argument to check for normal and cleartext
170 signatures. The plaintext is then returned in the data object.
172 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
173 to set and get the number of certifications to include in S/MIME
176 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
177 to encrypt and sign a message in a combined operation.
179 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
181 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
183 * Interface changes relative to the 0.3.3 release:
184 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
185 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
186 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
187 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
188 gpgme_set_include_certs NEW
189 gpgme_get_include_certs NEW
190 gpgme_op_encrypt_sign NEW
191 gpgme_op_encrypt_sign_start NEW
192 gpgme_op_keylist_ext_start NEW
193 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
195 Noteworthy changes in version 0.3.3 (2002-02-12)
196 ------------------------------------------------
198 * Fix the Makefile in jnlib.
200 * Fix the test suite (hopefully). It should clean up all its state
201 with `make check' now.
204 Noteworthy changes in version 0.3.2 (2002-02-10)
205 ------------------------------------------------
207 * Remove erroneous dependency on libgcrypt in jnlib.
210 Noteworthy changes in version 0.3.1 (2002-02-09)
211 ------------------------------------------------
213 * There is a Texinfo manual documenting the API.
215 * The gpgme_set_keylist_mode function returns an error, and changed
216 its meaning. It is no longer usable to select between normal and
217 fast mode (newer versions of GnuPG will always be fast), but
218 selects between local keyring, remote keyserver, or both.
219 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
220 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
221 current setting, a fucntion gpgme_get_keylist_mode was added to
222 retrieve the current mode.
224 * gpgme_wait accepts a new argument STATUS to return the error status
225 of the operation on the context. Its definition is closer to
226 waitpid() now than before.
228 * The LENGTH argument to gpgme_data_new_from_filepart changed its
229 type from off_t to the unsigned size_t.
231 * The R_HD argument to the GpgmePassphraseCb type changed its type
232 from void* to void**.
234 * New interface gpgme_op_trustlist_end() to match
235 gpgme_op_keylist_end().
237 * The CryptPlug modules have been renamed to gpgme-openpgp and
238 gpgme-smime, and they are installed in pkglibdir by `make install'.
240 * An idle function can be registered with gpgme_register_idle().
242 * The GpgSM backend supports key generation with gpgme_op_genkey().
244 * Interface changes relative to the 0.3.0 release:
245 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
246 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
247 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
248 gpgme_wait CHANGED: New argument STATUS.
249 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
250 The function has a new meaning!
251 gpgme_get_keylist_mode NEW
252 GPGME_KEYLIST_MODE_LOCAL NEW
253 GPGME_KEYLIST_MODE_EXTERN NEW
254 gpgme_op_trustlist_next NEW
256 gpgme_register_idle NEW
257 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
259 Noteworthy changes in version 0.3.0 (2001-12-19)
260 ------------------------------------------------
262 * New interface gpgme_set_protocol() to set the protocol and thus the
263 crypto engine to be used by the context. Currently, the OpenPGP
264 and the CMS protocols are supported. They are specified by the new
265 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
266 A new context uses the OpenPGP engine by default.
268 * gpgme_get_engine_info() returns information for all crypto engines
269 compiled into the library. The XML format has changed. To
270 reliably get the version of a crypto engine, the <version> tag
271 after the appropriate <protocol> tag has to be looked for.
273 * New interface gpgme_engine_check_version(), obsoleting
274 gpgme_check_engine(). Check the version of all engines you are
275 supporting in your software.
277 * GpgmeKey lists the user ids in the order as they are returned by
278 GnuPG, first the primary key with index 0, then the sub-user ids.
280 * New operation gpgme_op_decrypt_verify() to decrypt and verify
281 signatures simultaneously.
283 * The new interface gpgme_op_keylist_end() terminates a pending
284 keylist operation. A keylist operation is also terminated when
285 gpgme_op_keylist_next() returns GPGME_EOF.
287 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
288 cross-compiled, or even compiled without support for GnuPG
291 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
292 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
293 in the path, but it can also be compiled without support for GpgSM
296 * CryptPlug modules for GPGME are included and can be enabled at
297 configure time (`--enable-gpgmeplug'). There is one module which
298 uses the GnuPG engine (`gpgmeplug') and one module which uses the
299 GpgSM engine (`gpgsmplug').
301 * Interface changes relative to the latest 0.2.x release:
302 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
303 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
304 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
305 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
306 gpgme_get_engine_info CHANGED: New format, extended content.
307 gpgme_engine_check_version NEW
308 gpgme_decrypt_verify_start NEW
309 gpgme_decrypt_verify NEW
310 gpgme_op_keylist_next NEW
311 gpgme_set_protocol NEW
312 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
315 Noteworthy changes in version 0.2.3 (2001-09-17)
316 ------------------------------------------------
318 * New function gpgme_get_op_info which can be used to get the micalg
319 parameter needed for MOSS.
321 * New functions gpgme_get_armor and gpgme_get_textmode.
323 * The usual bug fixes and some minor functionality improvements.
325 * Added a simple encryption component for MS-Windows; however the
326 build procedure might have some problems.
329 Noteworthy changes in version 0.2.2 (2001-06-12)
330 ------------------------------------------------
332 * Implemented a key cache.
334 * Fixed a race condition under W32 and some other bug fixes.
337 Noteworthy changes in version 0.2.1 (2001-04-02)
338 ------------------------------------------------
340 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
342 * Handle GnuPG's new key capabilities output and support revocation
345 * Made the W32 support more robust.
348 Copyright 2001, 2002 g10 Code GmbH
350 This file is free software; as a special exception the author gives
351 unlimited permission to copy and/or distribute it, with or without
352 modifications, as long as this notice is preserved.
354 This file is distributed in the hope that it will be useful, but
355 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
356 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.