1 Noteworthy changes in version 0.3.6 (2002-05-03)
2 ------------------------------------------------
4 * All error outout of the gpgsm backend is send to the bit bucket.
6 * The signature verification functions are extended. Instead of
7 always returning GPGME_SIG_STATUS_GOOD, the functions new codes for
8 expired signatures. 2 new functions may be used to retrieve more
9 detailed information like the signature expiration time and a
10 validity information of the key without an extra key looking.
12 * The current passphrase callback and progress meter callback can be
13 retrieved with the new functions gpgme_get_passphrase_cb and
14 gpgme_get_progress_cb respectively.
16 * Interface changes relative to the 0.3.5 release:
17 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18 gpgme_get_passphrase_cb NEW
19 gpgme_get_progress_cb NEW
21 gpgme_data_set_encoding NEW
22 gpgme_data_get_encoding NEW
23 GPGME_SIG_STAT_GOOD_EXP NEW
24 GPGME_SIG_STAT_GOOD_EXPKEY NEW
25 gpgme_op_verify CHANGED: Returns more status codes.
26 GPGME_ATTR_SIG_STATUS NEW
27 gpgme_get_sig_string_attr NEW
28 gpgme_get_sig_ulong_attr NEW
29 gpgme_get_protocol NEW
30 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
32 Noteworthy changes in version 0.3.5 (2002-04-01)
33 ------------------------------------------------
35 * gpgme_op_encrypt can be called with RECIPIENTS being 0. In this
36 case, symmetric encryption is performed. Note that this requires a
37 passphrase from the user.
39 * More information is returned for X.509 certificates.
41 * Interface changes relative to the 0.3.4 release:
42 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
43 gpgme_op_encrypt EXTENDED: Symmetric encryption possible
44 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
46 Noteworthy changes in version 0.3.4 (2002-03-04)
47 ------------------------------------------------
49 * gpgme_op_encrypt does now fail with GPGME_Invalid_Recipients if
50 some recipients have been invalid, whereas earlier versions
51 succeeded in this case. The plaintext is still encrypted for all valid
52 recipients, so the application might take this error as a hint that
53 the ciphertext is not usable for all requested recipients.
54 Information about invalid recipients is available with gpgme_get_op_info.
56 * gpgme_op_verify now allows to pass an uninitialized data object as
57 its plaintext argument to check for normal and cleartext
58 signatures. The plaintext is then returned in the data object.
60 * New interfaces gpgme_set_include_certs and gpgme_get_include_certs
61 to set and get the number of certifications to include in S/MIME
64 * New interfaces gpgme_op_encrypt_sign and gpgme_op_encrypt_sign_start
65 to encrypt and sign a message in a combined operation.
67 * New interface gpgme_op_keylist_ext_start to search for multiple patterns.
69 * gpgme_key_get_ulong_attr supports the GPGME_ATTR_EXPIRE attribute.
71 * Interface changes relative to the 0.3.3 release:
72 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
73 gpgme_op_encrypt CHANGED: Can fail with GPGME_Invalid_Recipients
74 gpgme_op_verify EXTENDED: Accepts uninitialized text argument
75 gpgme_key_get_ulong_attr EXTENDED: Supports GPGME_ATTR_EXPIRE
76 gpgme_set_include_certs NEW
77 gpgme_get_include_certs NEW
78 gpgme_op_encrypt_sign NEW
79 gpgme_op_encrypt_sign_start NEW
80 gpgme_op_keylist_ext_start NEW
81 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
83 Noteworthy changes in version 0.3.3 (2002-02-12)
84 ------------------------------------------------
86 * Fix the Makefile in jnlib.
88 * Fix the test suite (hopefully). It should clean up all its state
89 with `make check' now.
92 Noteworthy changes in version 0.3.2 (2002-02-10)
93 ------------------------------------------------
95 * Remove erroneous dependency on libgcrypt in jnlib.
98 Noteworthy changes in version 0.3.1 (2002-02-09)
99 ------------------------------------------------
101 * There is a Texinfo manual documenting the API.
103 * The gpgme_set_keylist_mode function returns an error, and changed
104 its meaning. It is no longer usable to select between normal and
105 fast mode (newer versions of GnuPG will always be fast), but
106 selects between local keyring, remote keyserver, or both.
107 For this, two new macros are defined, GPGME_KEYLIST_MODE_LOCAL
108 and GPGME_KEYLIST_MODE_EXTERN. To make it possible to modify the
109 current setting, a fucntion gpgme_get_keylist_mode was added to
110 retrieve the current mode.
112 * gpgme_wait accepts a new argument STATUS to return the error status
113 of the operation on the context. Its definition is closer to
114 waitpid() now than before.
116 * The LENGTH argument to gpgme_data_new_from_filepart changed its
117 type from off_t to the unsigned size_t.
119 * The R_HD argument to the GpgmePassphraseCb type changed its type
120 from void* to void**.
122 * New interface gpgme_op_trustlist_end() to match
123 gpgme_op_keylist_end().
125 * The CryptPlug modules have been renamed to gpgme-openpgp and
126 gpgme-smime, and they are installed in pkglibdir by `make install'.
128 * An idle function can be registered with gpgme_register_idle().
130 * The GpgSM backend supports key generation with gpgme_op_genkey().
132 * Interface changes relative to the 0.3.0 release:
133 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
134 gpgme_data_new_from_filepart CHANGED: Type of LENGTH is size_t.
135 GpgmePassphraseCb CHANGED: Type of R_HD is void **.
136 gpgme_wait CHANGED: New argument STATUS.
137 gpgme_set_keylist_mode CHANGED: Type of return value is GpgmeError.
138 The function has a new meaning!
139 gpgme_get_keylist_mode NEW
140 GPGME_KEYLIST_MODE_LOCAL NEW
141 GPGME_KEYLIST_MODE_EXTERN NEW
142 gpgme_op_trustlist_next NEW
144 gpgme_register_idle NEW
145 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
147 Noteworthy changes in version 0.3.0 (2001-12-19)
148 ------------------------------------------------
150 * New interface gpgme_set_protocol() to set the protocol and thus the
151 crypto engine to be used by the context. Currently, the OpenPGP
152 and the CMS protocols are supported. They are specified by the new
153 preprocessor symbols GPGME_PROTOCOL_OpenPGP and GPGME_PROTOCOL_CMS.
154 A new context uses the OpenPGP engine by default.
156 * gpgme_get_engine_info() returns information for all crypto engines
157 compiled into the library. The XML format has changed. To
158 reliably get the version of a crypto engine, the <version> tag
159 after the appropriate <protocol> tag has to be looked for.
161 * New interface gpgme_engine_check_version(), obsoleting
162 gpgme_check_engine(). Check the version of all engines you are
163 supporting in your software.
165 * GpgmeKey lists the user ids in the order as they are returned by
166 GnuPG, first the primary key with index 0, then the sub-user ids.
168 * New operation gpgme_op_decrypt_verify() to decrypt and verify
169 signatures simultaneously.
171 * The new interface gpgme_op_keylist_end() terminates a pending
172 keylist operation. A keylist operation is also terminated when
173 gpgme_op_keylist_next() returns GPGME_EOF.
175 * GPGME can be compiled without GnuPG being installed (`--with-gpg=PATH'),
176 cross-compiled, or even compiled without support for GnuPG
179 * GPGME can be compiled with support for GpgSM (GnuPG for S/MIME,
180 `--with-gpgsm=PATH'). It is enabled by default if the `gpgsm' is found
181 in the path, but it can also be compiled without support for GpgSM
184 * CryptPlug modules for GPGME are included and can be enabled at
185 configure time (`--enable-gpgmeplug'). There is one module which
186 uses the GnuPG engine (`gpgmeplug') and one module which uses the
187 GpgSM engine (`gpgsmplug').
189 * Interface changes relative to the latest 0.2.x release:
190 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
191 gpgme_key_get_as_xml CHANGED: Sub-user ids reversed in order.
192 gpgme_key_get_string_attr CHANGED: User ids reversed in order.
193 gpgme_key_get_ulong_attr CHANGED: User ids reversed in order.
194 gpgme_get_engine_info CHANGED: New format, extended content.
195 gpgme_engine_check_version NEW
196 gpgme_decrypt_verify_start NEW
197 gpgme_decrypt_verify NEW
198 gpgme_op_keylist_next NEW
199 gpgme_set_protocol NEW
200 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
203 Noteworthy changes in version 0.2.3 (2001-09-17)
204 ------------------------------------------------
206 * New function gpgme_get_op_info which can be used to get the micalg
207 parameter needed for MOSS.
209 * New functions gpgme_get_armor and gpgme_get_textmode.
211 * The usual bug fixes and some minor functionality improvements.
213 * Added a simple encryption component for MS-Windows; however the
214 build procedure might have some problems.
217 Noteworthy changes in version 0.2.2 (2001-06-12)
218 ------------------------------------------------
220 * Implemented a key cache.
222 * Fixed a race condition under W32 and some other bug fixes.
225 Noteworthy changes in version 0.2.1 (2001-04-02)
226 ------------------------------------------------
228 * Changed debug output and GPGME_DEBUG variable (gpgme/debug.c)
230 * Handle GnuPG's new key capabilities output and support revocation
233 * Made the W32 support more robust.
236 Copyright 2001, 2002 g10 Code GmbH
238 This file is free software; as a special exception the author gives
239 unlimited permission to copy and/or distribute it, with or without
240 modifications, as long as this notice is preserved.
242 This file is distributed in the hope that it will be useful, but
243 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
244 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.