5 Changes between 1.0.2g and 1.1.0 [xx XXX xxxx]
7 *) Change the ECC default curve list to be this, in order: x25519,
8 secp256r1, secp521r1, secp384r1.
11 *) RC4 based libssl ciphersuites are now classed as "weak" ciphers and are
12 disabled by default. They can be re-enabled using the
13 enable-weak-ssl-ciphers option to Configure.
16 *) If the server has ALPN configured, but supports no protocols that the
17 client advertises, send a fatal "no_application_protocol" alert.
18 This behaviour is SHALL in RFC 7301, though it isn't universally
19 implemented by other servers.
22 *) Add X25519 support.
23 Integrate support for X25519 into EC library. This includes support
24 for public and private key encoding using the format documented in
25 draft-josefsson-pkix-newcurves-01: specifically X25519 uses the
26 OID from that draft, encodes public keys using little endian
27 format in the ECPoint structure and private keys using
28 little endian form in the privateKey field of the ECPrivateKey
29 structure. TLS support complies with draft-ietf-tls-rfc4492bis-06
32 Note: the current version supports key generation, public and
33 private key encoding and ECDH key agreement using the EC API.
34 Low level point operations such as EC_POINT_add(), EC_POINT_mul()
38 *) Deprecate SRP_VBASE_get_by_user.
39 SRP_VBASE_get_by_user had inconsistent memory management behaviour.
40 In order to fix an unavoidable memory leak (CVE-2016-0798),
41 SRP_VBASE_get_by_user was changed to ignore the "fake user" SRP
42 seed, even if the seed is configured.
44 Users should use SRP_VBASE_get1_by_user instead. Note that in
45 SRP_VBASE_get1_by_user, caller must free the returned value. Note
46 also that even though configuring the SRP seed attempts to hide
47 invalid usernames by continuing the handshake with fake
48 credentials, this behaviour is not constant time and no strong
49 guarantees are made that the handshake is indistinguishable from
53 *) Configuration change; it's now possible to build dynamic engines
54 without having to build shared libraries and vice versa. This
55 only applies to the engines in engines/, those in crypto/engine/
56 will always be built into libcrypto (i.e. "static").
58 Building dynamic engines is enabled by default; to disable, use
59 the configuration option "disable-dynamic-engine".
61 The only requirements for building dynamic engines are the
62 presence of the DSO module and building with position independent
63 code, so they will also automatically be disabled if configuring
64 with "disable-dso" or "disable-pic".
66 The macros OPENSSL_NO_STATIC_ENGINE and OPENSSL_NO_DYNAMIC_ENGINE
67 are also taken away from openssl/opensslconf.h, as they are
71 *) Configuration change; if there is a known flag to compile
72 position independent code, it will always be applied on the
73 libcrypto and libssl object files, and never on the application
74 object files. This means other libraries that use routines from
75 libcrypto / libssl can be made into shared libraries regardless
76 of how OpenSSL was configured.
78 If this isn't desirable, the configuration options "disable-pic"
79 or "no-pic" can be used to disable the use of PIC. This will
80 also disable building shared libraries and dynamic engines.
83 *) Removed JPAKE code. It was experimental and has no wide use.
86 *) The INSTALL_PREFIX Makefile variable has been renamed to
87 DESTDIR. That makes for less confusion on what this variable
88 is for. Also, the configuration option --install_prefix is
92 *) Heartbeat for TLS has been removed and is disabled by default
93 for DTLS; configure with enable-heartbeats. Code that uses the
94 old #define's might need to be updated.
95 [Emilia Käsper, Rich Salz]
97 *) Rename REF_CHECK to REF_DEBUG.
100 *) New "unified" build system
102 The "unified" build system is aimed to be a common system for all
103 platforms we support. With it comes new support for VMS.
105 This system builds supports building in a different directory tree
106 than the source tree. It produces one Makefile (for unix family
107 or lookalikes), or one descrip.mms (for VMS).
109 The source of information to make the Makefile / descrip.mms is
110 small files called 'build.info', holding the necessary
111 information for each directory with source to compile, and a
112 template in Configurations, like unix-Makefile.tmpl or
115 We rely heavily on the perl module Text::Template.
118 *) Added support for auto-initialisation and de-initialisation of the library.
119 OpenSSL no longer requires explicit init or deinit routines to be called,
120 except in certain circumstances. See the OPENSSL_init_crypto() and
121 OPENSSL_init_ssl() man pages for further information.
124 *) The arguments to the DTLSv1_listen function have changed. Specifically the
125 "peer" argument is now expected to be a BIO_ADDR object.
127 *) Rewrite of BIO networking library. The BIO library lacked consistent
128 support of IPv6, and adding it required some more extensive
129 modifications. This introduces the BIO_ADDR and BIO_ADDRINFO types,
130 which hold all types of addresses and chains of address information.
131 It also introduces a new API, with functions like BIO_socket,
132 BIO_connect, BIO_listen, BIO_lookup and a rewrite of BIO_accept.
133 The source/sink BIOs BIO_s_connect, BIO_s_accept and BIO_s_datagram
134 have been adapted accordingly.
137 *) RSA_padding_check_PKCS1_type_1 now accepts inputs with and without
141 *) CRIME protection: disable compression by default, even if OpenSSL is
142 compiled with zlib enabled. Applications can still enable compression
143 by calling SSL_CTX_clear_options(ctx, SSL_OP_NO_COMPRESSION), or by
144 using the SSL_CONF library to configure compression.
147 *) The signature of the session callback configured with
148 SSL_CTX_sess_set_get_cb was changed. The read-only input buffer
149 was explicitly marked as 'const unsigned char*' instead of
153 *) Always DPURIFY. Remove the use of uninitialized memory in the
154 RNG, and other conditional uses of DPURIFY. This makes -DPURIFY a no-op.
157 *) Removed many obsolete configuration items, including
158 DES_PTR, DES_RISC1, DES_RISC2, DES_INT
159 MD2_CHAR, MD2_INT, MD2_LONG
161 IDEA_SHORT, IDEA_LONG
162 RC2_SHORT, RC2_LONG, RC4_LONG, RC4_CHUNK, RC4_INDEX
163 [Rich Salz, with advice from Andy Polyakov]
165 *) Many BN internals have been moved to an internal header file.
166 [Rich Salz with help from Andy Polyakov]
168 *) Configuration and writing out the results from it has changed.
169 Files such as Makefile include/openssl/opensslconf.h and are now
170 produced through general templates, such as Makefile.in and
171 crypto/opensslconf.h.in and some help from the perl module
174 Also, the center of configuration information is no longer
175 Makefile. Instead, Configure produces a perl module in
176 configdata.pm which holds most of the config data (in the hash
177 table %config), the target data that comes from the target
178 configuration in one of the Configurations/*.conf files (in
182 *) To clarify their intended purposes, the Configure options
183 --prefix and --openssldir change their semantics, and become more
184 straightforward and less interdependent.
186 --prefix shall be used exclusively to give the location INSTALLTOP
187 where programs, scripts, libraries, include files and manuals are
188 going to be installed. The default is now /usr/local.
190 --openssldir shall be used exclusively to give the default
191 location OPENSSLDIR where certificates, private keys, CRLs are
192 managed. This is also where the default openssl.cnf gets
194 If the directory given with this option is a relative path, the
195 values of both the --prefix value and the --openssldir value will
196 be combined to become OPENSSLDIR.
197 The default for --openssldir is INSTALLTOP/ssl.
199 Anyone who uses --openssldir to specify where OpenSSL is to be
200 installed MUST change to use --prefix instead.
203 *) The GOST engine was out of date and therefore it has been removed. An up
204 to date GOST engine is now being maintained in an external repository.
205 See: https://wiki.openssl.org/index.php/Binaries. Libssl still retains
206 support for GOST ciphersuites (these are only activated if a GOST engine
210 *) EGD is no longer supported by default; use enable-egd when
212 [Ben Kaduk and Rich Salz]
214 *) The distribution now has Makefile.in files, which are used to
215 create Makefile's when Configure is run. *Configure must be run
216 before trying to build now.*
219 *) The return value for SSL_CIPHER_description() for error conditions
223 *) Support for RFC6698/RFC7671 DANE TLSA peer authentication.
225 Obtaining and performing DNSSEC validation of TLSA records is
226 the application's responsibility. The application provides
227 the TLSA records of its choice to OpenSSL, and these are then
228 used to authenticate the peer.
230 The TLSA records need not even come from DNS. They can, for
231 example, be used to implement local end-entity certificate or
232 trust-anchor "pinning", where the "pin" data takes the form
233 of TLSA records, which can augment or replace verification
234 based on the usual WebPKI public certification authorities.
237 *) Revert default OPENSSL_NO_DEPRECATED setting. Instead OpenSSL
238 continues to support deprecated interfaces in default builds.
239 However, applications are strongly advised to compile their
240 source files with -DOPENSSL_API_COMPAT=0x10100000L, which hides
241 the declarations of all interfaces deprecated in 0.9.8, 1.0.0
242 or the 1.1.0 releases.
244 In environments in which all applications have been ported to
245 not use any deprecated interfaces OpenSSL's Configure script
246 should be used with the --api=1.1.0 option to entirely remove
247 support for the deprecated features from the library and
248 unconditionally disable them in the installed headers.
249 Essentially the same effect can be achieved with the "no-deprecated"
250 argument to Configure, except that this will always restrict
251 the build to just the latest API, rather than a fixed API
254 As applications are ported to future revisions of the API,
255 they should update their compile-time OPENSSL_API_COMPAT define
256 accordingly, but in most cases should be able to continue to
257 compile with later releases.
259 The OPENSSL_API_COMPAT versions for 1.0.0, and 0.9.8 are
260 0x10000000L and 0x00908000L, respectively. However those
261 versions did not support the OPENSSL_API_COMPAT feature, and
262 so applications are not typically tested for explicit support
263 of just the undeprecated features of either release.
266 *) Add support for setting the minimum and maximum supported protocol.
267 It can bet set via the SSL_set_min_proto_version() and
268 SSL_set_max_proto_version(), or via the SSL_CONF's MinProtocol and
269 MaxProtcol. It's recommended to use the new APIs to disable
270 protocols instead of disabling individual protocols using
271 SSL_set_options() or SSL_CONF's Protocol. This change also
272 removes support for disabling TLS 1.2 in the OpenSSL TLS
273 client at compile time by defining OPENSSL_NO_TLS1_2_CLIENT.
276 *) Support for ChaCha20 and Poly1305 added to libcrypto and libssl.
279 *) New EC_KEY_METHOD, this replaces the older ECDSA_METHOD and ECDH_METHOD
280 and integrates ECDSA and ECDH functionality into EC. Implementations can
281 now redirect key generation and no longer need to convert to or from
284 Note: the ecdsa.h and ecdh.h headers are now no longer needed and just
285 include the ec.h header file instead.
288 *) Remove support for all 40 and 56 bit ciphers. This includes all the export
289 ciphers who are no longer supported and drops support the ephemeral RSA key
290 exchange. The LOW ciphers currently doesn't have any ciphers in it.
293 *) Made EVP_MD_CTX, EVP_MD, EVP_CIPHER_CTX, EVP_CIPHER and HMAC_CTX
294 opaque. For HMAC_CTX, the following constructors and destructors
297 HMAC_CTX *HMAC_CTX_new(void);
298 void HMAC_CTX_free(HMAC_CTX *ctx);
300 For EVP_MD and EVP_CIPHER, complete APIs to create, fill and
301 destroy such methods has been added. See EVP_MD_meth_new(3) and
302 EVP_CIPHER_meth_new(3) for documentation.
305 1) EVP_MD_CTX_cleanup(), EVP_CIPHER_CTX_cleanup() and
306 HMAC_CTX_cleanup() were removed. HMAC_CTX_reset() and
307 EVP_MD_CTX_reset() should be called instead to reinitialise
308 an already created structure.
309 2) For consistency with the majority of our object creators and
310 destructors, EVP_MD_CTX_(create|destroy) were renamed to
311 EVP_MD_CTX_(new|free). The old names are retained as macros
312 for deprecated builds.
315 *) Added ASYNC support. Libcrypto now includes the async sub-library to enable
316 cryptographic operations to be performed asynchronously as long as an
317 asynchronous capable engine is used. See the ASYNC_start_job() man page for
318 further details. Libssl has also had this capability integrated with the
319 introduction of the new mode SSL_MODE_ASYNC and associated error
320 SSL_ERROR_WANT_ASYNC. See the SSL_CTX_set_mode() and SSL_get_error() man
321 pages. This work was developed in partnership with Intel Corp.
324 *) SSL_{CTX_}set_ecdh_auto() has been removed and ECDH is support is
325 always enabled now. If you want to disable the support you should
326 exclude it using the list of supported ciphers. This also means that the
327 "-no_ecdhe" option has been removed from s_server.
330 *) SSL_{CTX}_set_tmp_ecdh() which can set 1 EC curve now internally calls
331 SSL_{CTX_}set1_curves() which can set a list.
334 *) Remove support for SSL_{CTX_}set_tmp_ecdh_callback(). You should set the
335 curve you want to support using SSL_{CTX_}set1_curves().
338 *) State machine rewrite. The state machine code has been significantly
339 refactored in order to remove much duplication of code and solve issues
340 with the old code (see ssl/statem/README for further details). This change
341 does have some associated API changes. Notably the SSL_state() function
342 has been removed and replaced by SSL_get_state which now returns an
343 "OSSL_HANDSHAKE_STATE" instead of an int. SSL_set_state() has been removed
344 altogether. The previous handshake states defined in ssl.h and ssl3.h have
348 *) All instances of the string "ssleay" in the public API were replaced
349 with OpenSSL (case-matching; e.g., OPENSSL_VERSION for #define's)
350 Some error codes related to internal RSA_eay API's were renamed.
353 *) The demo files in crypto/threads were moved to demo/threads.
356 *) Removed obsolete engines: 4758cca, aep, atalla, cswift, nuron, gmp,
358 [Matt Caswell, Rich Salz]
360 *) New ASN.1 embed macro.
362 New ASN.1 macro ASN1_EMBED. This is the same as ASN1_SIMPLE except the
363 structure is not allocated: it is part of the parent. That is instead of
371 This reduces memory fragmentation and make it impossible to accidentally
372 set a mandatory field to NULL.
374 This currently only works for some fields specifically a SEQUENCE, CHOICE,
375 or ASN1_STRING type which is part of a parent SEQUENCE. Since it is
376 equivalent to ASN1_SIMPLE it cannot be tagged, OPTIONAL, SET OF or
380 *) Remove EVP_CHECK_DES_KEY, a compile-time option that never compiled.
383 *) Removed DES and RC4 ciphersuites from DEFAULT. Also removed RC2 although
384 in 1.0.2 EXPORT was already removed and the only RC2 ciphersuite is also
385 an EXPORT one. COMPLEMENTOFDEFAULT has been updated accordingly to add
386 DES and RC4 ciphersuites.
389 *) Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs.
390 This changes the decoding behaviour for some invalid messages,
391 though the change is mostly in the more lenient direction, and
392 legacy behaviour is preserved as much as possible.
395 *) Fix no-stdio build.
396 [ David Woodhouse <David.Woodhouse@intel.com> and also
397 Ivan Nestlerode <ivan.nestlerode@sonos.com> ]
399 *) New testing framework
400 The testing framework has been largely rewritten and is now using
401 perl and the perl modules Test::Harness and an extended variant of
402 Test::More called OpenSSL::Test to do its work. All test scripts in
403 test/ have been rewritten into test recipes, and all direct calls to
404 executables in test/Makefile have become individual recipes using the
405 simplified testing OpenSSL::Test::Simple.
407 For documentation on our testing modules, do:
409 perldoc test/testlib/OpenSSL/Test/Simple.pm
410 perldoc test/testlib/OpenSSL/Test.pm
414 *) Revamped memory debug; only -DCRYPTO_MDEBUG and -DCRYPTO_MDEBUG_ABORT
415 are used; the latter aborts on memory leaks (usually checked on exit).
416 Some undocumented "set malloc, etc., hooks" functions were removed
417 and others were changed. All are now documented.
420 *) In DSA_generate_parameters_ex, if the provided seed is too short,
422 [Rich Salz and Ismo Puustinen <ismo.puustinen@intel.com>]
424 *) Rewrite PSK to support ECDHE_PSK, DHE_PSK and RSA_PSK. Add ciphersuites
425 from RFC4279, RFC4785, RFC5487, RFC5489.
427 Thanks to Christian J. Dietrich and Giuseppe D'Angelo for the
428 original RSA_PSK patch.
431 *) Dropped support for the SSL3_FLAGS_DELAY_CLIENT_FINISHED flag. This SSLeay
432 era flag was never set throughout the codebase (only read). Also removed
433 SSL3_FLAGS_POP_BUFFER which was only used if
434 SSL3_FLAGS_DELAY_CLIENT_FINISHED was also set.
437 *) Changed the default name options in the "ca", "crl", "req" and "x509"
438 to be "oneline" instead of "compat".
441 *) Remove SSL_OP_TLS_BLOCK_PADDING_BUG. This is SSLeay legacy, we're
442 not aware of clients that still exhibit this bug, and the workaround
443 hasn't been working properly for a while.
446 *) The return type of BIO_number_read() and BIO_number_written() as well as
447 the corresponding num_read and num_write members in the BIO structure has
448 changed from unsigned long to uint64_t. On platforms where an unsigned
449 long is 32 bits (e.g. Windows) these counters could overflow if >4Gb is
453 *) Given the pervasive nature of TLS extensions it is inadvisable to run
454 OpenSSL without support for them. It also means that maintaining
455 the OPENSSL_NO_TLSEXT option within the code is very invasive (and probably
456 not well tested). Therefore the OPENSSL_NO_TLSEXT option has been removed.
459 *) Removed support for the two export grade static DH ciphersuites
460 EXP-DH-RSA-DES-CBC-SHA and EXP-DH-DSS-DES-CBC-SHA. These two ciphersuites
461 were newly added (along with a number of other static DH ciphersuites) to
462 1.0.2. However the two export ones have *never* worked since they were
463 introduced. It seems strange in any case to be adding new export
464 ciphersuites, and given "logjam" it also does not seem correct to fix them.
467 *) Version negotiation has been rewritten. In particular SSLv23_method(),
468 SSLv23_client_method() and SSLv23_server_method() have been deprecated,
469 and turned into macros which simply call the new preferred function names
470 TLS_method(), TLS_client_method() and TLS_server_method(). All new code
471 should use the new names instead. Also as part of this change the ssl23.h
472 header file has been removed.
475 *) Support for Kerberos ciphersuites in TLS (RFC2712) has been removed. This
476 code and the associated standard is no longer considered fit-for-purpose.
479 *) RT2547 was closed. When generating a private key, try to make the
480 output file readable only by the owner. This behavior change might
481 be noticeable when interacting with other software.
483 *) Documented all exdata functions. Added CRYPTO_free_ex_index.
487 *) Added HTTP GET support to the ocsp command.
490 *) Changed default digest for the dgst and enc commands from MD5 to
494 *) RAND_pseudo_bytes has been deprecated. Users should use RAND_bytes instead.
497 *) Added support for TLS extended master secret from
498 draft-ietf-tls-session-hash-03.txt. Thanks for Alfredo Pironti for an
499 initial patch which was a great help during development.
502 *) All libssl internal structures have been removed from the public header
503 files, and the OPENSSL_NO_SSL_INTERN option has been removed (since it is
504 now redundant). Users should not attempt to access internal structures
505 directly. Instead they should use the provided API functions.
508 *) config has been changed so that by default OPENSSL_NO_DEPRECATED is used.
509 Access to deprecated functions can be re-enabled by running config with
510 "enable-deprecated". In addition applications wishing to use deprecated
511 functions must define OPENSSL_USE_DEPRECATED. Note that this new behaviour
512 will, by default, disable some transitive includes that previously existed
513 in the header files (e.g. ec.h will no longer, by default, include bn.h)
516 *) Added support for OCB mode. OpenSSL has been granted a patent license
517 compatible with the OpenSSL license for use of OCB. Details are available
518 at https://www.openssl.org/source/OCB-patent-grant-OpenSSL.pdf. Support
519 for OCB can be removed by calling config with no-ocb.
522 *) SSLv2 support has been removed. It still supports receiving a SSLv2
523 compatible client hello.
526 *) Increased the minimal RSA keysize from 256 to 512 bits [Rich Salz],
527 done while fixing the error code for the key-too-small case.
528 [Annie Yousar <a.yousar@informatik.hu-berlin.de>]
530 *) CA.sh has been removmed; use CA.pl instead.
533 *) Removed old DES API.
536 *) Remove various unsupported platforms:
542 Sinix/ReliantUNIX RM400
547 16-bit platforms such as WIN16
550 *) Clean up OPENSSL_NO_xxx #define's
551 Use setbuf() and remove OPENSSL_NO_SETVBUF_IONBF
552 Rename OPENSSL_SYSNAME_xxx to OPENSSL_SYS_xxx
553 OPENSSL_NO_EC{DH,DSA} merged into OPENSSL_NO_EC
554 OPENSSL_NO_RIPEMD160, OPENSSL_NO_RIPEMD merged into OPENSSL_NO_RMD160
555 OPENSSL_NO_FP_API merged into OPENSSL_NO_STDIO
556 Remove OPENSSL_NO_BIO OPENSSL_NO_BUFFER OPENSSL_NO_CHAIN_VERIFY
557 OPENSSL_NO_EVP OPENSSL_NO_FIPS_ERR OPENSSL_NO_HASH_COMP
558 OPENSSL_NO_LHASH OPENSSL_NO_OBJECT OPENSSL_NO_SPEED OPENSSL_NO_STACK
559 OPENSSL_NO_X509 OPENSSL_NO_X509_VERIFY
560 Remove MS_STATIC; it's a relic from platforms <32 bits.
563 *) Cleaned up dead code
564 Remove all but one '#ifdef undef' which is to be looked at.
567 *) Clean up calling of xxx_free routines.
568 Just like free(), fix most of the xxx_free routines to accept
569 NULL. Remove the non-null checks from callers. Save much code.
572 *) Add secure heap for storage of private keys (when possible).
573 Add BIO_s_secmem(), CBIGNUM, etc.
574 Contributed by Akamai Technologies under our Corporate CLA.
577 *) Experimental support for a new, fast, unbiased prime candidate generator,
578 bn_probable_prime_dh_coprime(). Not currently used by any prime generator.
579 [Felix Laurie von Massenbach <felix@erbridge.co.uk>]
581 *) New output format NSS in the sess_id command line tool. This allows
582 exporting the session id and the master key in NSS keylog format.
583 [Martin Kaiser <martin@kaiser.cx>]
585 *) Harmonize version and its documentation. -f flag is used to display
587 [mancha <mancha1@zoho.com>]
589 *) Fix eckey_priv_encode so it immediately returns an error upon a failure
590 in i2d_ECPrivateKey. Thanks to Ted Unangst for feedback on this issue.
591 [mancha <mancha1@zoho.com>]
593 *) Fix some double frees. These are not thought to be exploitable.
594 [mancha <mancha1@zoho.com>]
596 *) A missing bounds check in the handling of the TLS heartbeat extension
597 can be used to reveal up to 64k of memory to a connected client or
600 Thanks for Neel Mehta of Google Security for discovering this bug and to
601 Adam Langley <agl@chromium.org> and Bodo Moeller <bmoeller@acm.org> for
602 preparing the fix (CVE-2014-0160)
603 [Adam Langley, Bodo Moeller]
605 *) Fix for the attack described in the paper "Recovering OpenSSL
606 ECDSA Nonces Using the FLUSH+RELOAD Cache Side-channel Attack"
607 by Yuval Yarom and Naomi Benger. Details can be obtained from:
608 http://eprint.iacr.org/2014/140
610 Thanks to Yuval Yarom and Naomi Benger for discovering this
611 flaw and to Yuval Yarom for supplying a fix (CVE-2014-0076)
612 [Yuval Yarom and Naomi Benger]
614 *) Use algorithm specific chains in SSL_CTX_use_certificate_chain_file():
615 this fixes a limitation in previous versions of OpenSSL.
618 *) Experimental encrypt-then-mac support.
620 Experimental support for encrypt then mac from
621 draft-gutmann-tls-encrypt-then-mac-02.txt
623 To enable it set the appropriate extension number (0x42 for the test
624 server) using e.g. -DTLSEXT_TYPE_encrypt_then_mac=0x42
626 For non-compliant peers (i.e. just about everything) this should have no
629 WARNING: EXPERIMENTAL, SUBJECT TO CHANGE.
633 *) Add EVP support for key wrapping algorithms, to avoid problems with
634 existing code the flag EVP_CIPHER_CTX_WRAP_ALLOW has to be set in
635 the EVP_CIPHER_CTX or an error is returned. Add AES and DES3 wrap
636 algorithms and include tests cases.
639 *) Extend CMS code to support RSA-PSS signatures and RSA-OAEP for
643 *) Extended RSA OAEP support via EVP_PKEY API. Options to specify digest,
644 MGF1 digest and OAEP label.
647 *) Make openssl verify return errors.
648 [Chris Palmer <palmer@google.com> and Ben Laurie]
650 *) New function ASN1_TIME_diff to calculate the difference between two
651 ASN1_TIME structures or one structure and the current time.
654 *) Update fips_test_suite to support multiple command line options. New
655 test to induce all self test errors in sequence and check expected
659 *) Add FIPS_{rsa,dsa,ecdsa}_{sign,verify} functions which digest and
660 sign or verify all in one operation.
663 *) Add fips_algvs: a multicall fips utility incorporating all the algorithm
664 test programs and fips_test_suite. Includes functionality to parse
665 the minimal script output of fipsalgest.pl directly.
668 *) Add authorisation parameter to FIPS_module_mode_set().
671 *) Add FIPS selftest for ECDH algorithm using P-224 and B-233 curves.
674 *) Use separate DRBG fields for internal and external flags. New function
675 FIPS_drbg_health_check() to perform on demand health checking. Add
676 generation tests to fips_test_suite with reduced health check interval to
677 demonstrate periodic health checking. Add "nodh" option to
678 fips_test_suite to skip very slow DH test.
681 *) New function FIPS_get_cipherbynid() to lookup FIPS supported ciphers
685 *) More extensive health check for DRBG checking many more failure modes.
686 New function FIPS_selftest_drbg_all() to handle every possible DRBG
687 combination: call this in fips_test_suite.
690 *) Add support for Dual EC DRBG from SP800-90. Update DRBG algorithm test
691 and POST to handle Dual EC cases.
694 *) Add support for canonical generation of DSA parameter 'g'. See
697 *) Add support for HMAC DRBG from SP800-90. Update DRBG algorithm test and
698 POST to handle HMAC cases.
701 *) Add functions FIPS_module_version() and FIPS_module_version_text()
702 to return numerical and string versions of the FIPS module number.
705 *) Rename FIPS_mode_set and FIPS_mode to FIPS_module_mode_set and
706 FIPS_module_mode. FIPS_mode and FIPS_mode_set will be implemented
707 outside the validated module in the FIPS capable OpenSSL.
710 *) Minor change to DRBG entropy callback semantics. In some cases
711 there is no multiple of the block length between min_len and
712 max_len. Allow the callback to return more than max_len bytes
713 of entropy but discard any extra: it is the callback's responsibility
714 to ensure that the extra data discarded does not impact the
715 requested amount of entropy.
718 *) Add PRNG security strength checks to RSA, DSA and ECDSA using
719 information in FIPS186-3, SP800-57 and SP800-131A.
722 *) CCM support via EVP. Interface is very similar to GCM case except we
723 must supply all data in one chunk (i.e. no update, final) and the
724 message length must be supplied if AAD is used. Add algorithm test
728 *) Initial version of POST overhaul. Add POST callback to allow the status
729 of POST to be monitored and/or failures induced. Modify fips_test_suite
730 to use callback. Always run all selftests even if one fails.
733 *) XTS support including algorithm test driver in the fips_gcmtest program.
734 Note: this does increase the maximum key length from 32 to 64 bytes but
735 there should be no binary compatibility issues as existing applications
736 will never use XTS mode.
739 *) Extensive reorganisation of FIPS PRNG behaviour. Remove all dependencies
740 to OpenSSL RAND code and replace with a tiny FIPS RAND API which also
741 performs algorithm blocking for unapproved PRNG types. Also do not
742 set PRNG type in FIPS_mode_set(): leave this to the application.
743 Add default OpenSSL DRBG handling: sets up FIPS PRNG and seeds with
744 the standard OpenSSL PRNG: set additional data to a date time vector.
747 *) Rename old X9.31 PRNG functions of the form FIPS_rand* to FIPS_x931*.
748 This shouldn't present any incompatibility problems because applications
749 shouldn't be using these directly and any that are will need to rethink
750 anyway as the X9.31 PRNG is now deprecated by FIPS 140-2
753 *) Extensive self tests and health checking required by SP800-90 DRBG.
754 Remove strength parameter from FIPS_drbg_instantiate and always
755 instantiate at maximum supported strength.
758 *) Add ECDH code to fips module and fips_ecdhvs for primitives only testing.
761 *) New algorithm test program fips_dhvs to handle DH primitives only testing.
764 *) New function DH_compute_key_padded() to compute a DH key and pad with
765 leading zeroes if needed: this complies with SP800-56A et al.
768 *) Initial implementation of SP800-90 DRBGs for Hash and CTR. Not used by
769 anything, incomplete, subject to change and largely untested at present.
772 *) Modify fipscanisteronly build option to only build the necessary object
773 files by filtering FIPS_EX_OBJ through a perl script in crypto/Makefile.
776 *) Add experimental option FIPSSYMS to give all symbols in
777 fipscanister.o and FIPS or fips prefix. This will avoid
778 conflicts with future versions of OpenSSL. Add perl script
779 util/fipsas.pl to preprocess assembly language source files
780 and rename any affected symbols.
783 *) Add selftest checks and algorithm block of non-fips algorithms in
784 FIPS mode. Remove DES2 from selftests.
787 *) Add ECDSA code to fips module. Add tiny fips_ecdsa_check to just
788 return internal method without any ENGINE dependencies. Add new
789 tiny fips sign and verify functions.
792 *) New build option no-ec2m to disable characteristic 2 code.
795 *) New build option "fipscanisteronly". This only builds fipscanister.o
796 and (currently) associated fips utilities. Uses the file Makefile.fips
797 instead of Makefile.org as the prototype.
800 *) Add some FIPS mode restrictions to GCM. Add internal IV generator.
801 Update fips_gcmtest to use IV generator.
804 *) Initial, experimental EVP support for AES-GCM. AAD can be input by
805 setting output buffer to NULL. The *Final function must be
806 called although it will not retrieve any additional data. The tag
807 can be set or retrieved with a ctrl. The IV length is by default 12
808 bytes (96 bits) but can be set to an alternative value. If the IV
809 length exceeds the maximum IV length (currently 16 bytes) it cannot be
813 *) New flag in ciphers: EVP_CIPH_FLAG_CUSTOM_CIPHER. This means the
814 underlying do_cipher function handles all cipher semantics itself
815 including padding and finalisation. This is useful if (for example)
816 an ENGINE cipher handles block padding itself. The behaviour of
817 do_cipher is subtly changed if this flag is set: the return value
818 is the number of characters written to the output buffer (zero is
819 no longer an error code) or a negative error code. Also if the
820 input buffer is NULL and length 0 finalisation should be performed.
823 *) If a candidate issuer certificate is already part of the constructed
824 path ignore it: new debug notification X509_V_ERR_PATH_LOOP for this case.
827 *) Improve forward-security support: add functions
829 void SSL_CTX_set_not_resumable_session_callback(SSL_CTX *ctx, int (*cb)(SSL *ssl, int is_forward_secure))
830 void SSL_set_not_resumable_session_callback(SSL *ssl, int (*cb)(SSL *ssl, int is_forward_secure))
832 for use by SSL/TLS servers; the callback function will be called whenever a
833 new session is created, and gets to decide whether the session may be
834 cached to make it resumable (return 0) or not (return 1). (As by the
835 SSL/TLS protocol specifications, the session_id sent by the server will be
836 empty to indicate that the session is not resumable; also, the server will
837 not generate RFC 4507 (RFC 5077) session tickets.)
839 A simple reasonable callback implementation is to return is_forward_secure.
840 This parameter will be set to 1 or 0 depending on the ciphersuite selected
841 by the SSL/TLS server library, indicating whether it can provide forward
843 [Emilia Käsper <emilia.kasper@esat.kuleuven.be> (Google)]
845 *) New -verify_name option in command line utilities to set verification
849 *) Initial CMAC implementation. WARNING: EXPERIMENTAL, API MAY CHANGE.
850 Add CMAC pkey methods.
853 *) Experimental renegotiation in s_server -www mode. If the client
854 browses /reneg connection is renegotiated. If /renegcert it is
855 renegotiated requesting a certificate.
858 *) Add an "external" session cache for debugging purposes to s_server. This
859 should help trace issues which normally are only apparent in deployed
860 multi-process servers.
863 *) Extensive audit of libcrypto with DEBUG_UNUSED. Fix many cases where
864 return value is ignored. NB. The functions RAND_add(), RAND_seed(),
865 BIO_set_cipher() and some obscure PEM functions were changed so they
866 can now return an error. The RAND changes required a change to the
867 RAND_METHOD structure.
870 *) New macro __owur for "OpenSSL Warn Unused Result". This makes use of
871 a gcc attribute to warn if the result of a function is ignored. This
872 is enable if DEBUG_UNUSED is set. Add to several functions in evp.h
873 whose return value is often ignored.
876 Changes between 1.0.2f and 1.0.2g [1 Mar 2016]
878 * Disable weak ciphers in SSLv3 and up in default builds of OpenSSL.
879 Builds that are not configured with "enable-weak-ssl-ciphers" will not
880 provide any "EXPORT" or "LOW" strength ciphers.
883 * Disable SSLv2 default build, default negotiation and weak ciphers. SSLv2
884 is by default disabled at build-time. Builds that are not configured with
885 "enable-ssl2" will not support SSLv2. Even if "enable-ssl2" is used,
886 users who want to negotiate SSLv2 via the version-flexible SSLv23_method()
887 will need to explicitly call either of:
889 SSL_CTX_clear_options(ctx, SSL_OP_NO_SSLv2);
891 SSL_clear_options(ssl, SSL_OP_NO_SSLv2);
893 as appropriate. Even if either of those is used, or the application
894 explicitly uses the version-specific SSLv2_method() or its client and
895 server variants, SSLv2 ciphers vulnerable to exhaustive search key
896 recovery have been removed. Specifically, the SSLv2 40-bit EXPORT
897 ciphers, and SSLv2 56-bit DES are no longer available.
901 *) Fix a double-free in DSA code
903 A double free bug was discovered when OpenSSL parses malformed DSA private
904 keys and could lead to a DoS attack or memory corruption for applications
905 that receive DSA private keys from untrusted sources. This scenario is
908 This issue was reported to OpenSSL by Adam Langley(Google/BoringSSL) using
913 *) Disable SRP fake user seed to address a server memory leak.
915 Add a new method SRP_VBASE_get1_by_user that handles the seed properly.
917 SRP_VBASE_get_by_user had inconsistent memory management behaviour.
918 In order to fix an unavoidable memory leak, SRP_VBASE_get_by_user
919 was changed to ignore the "fake user" SRP seed, even if the seed
922 Users should use SRP_VBASE_get1_by_user instead. Note that in
923 SRP_VBASE_get1_by_user, caller must free the returned value. Note
924 also that even though configuring the SRP seed attempts to hide
925 invalid usernames by continuing the handshake with fake
926 credentials, this behaviour is not constant time and no strong
927 guarantees are made that the handshake is indistinguishable from
928 that of a valid user.
932 *) Fix BN_hex2bn/BN_dec2bn NULL pointer deref/heap corruption
934 In the BN_hex2bn function the number of hex digits is calculated using an
935 int value |i|. Later |bn_expand| is called with a value of |i * 4|. For
936 large values of |i| this can result in |bn_expand| not allocating any
937 memory because |i * 4| is negative. This can leave the internal BIGNUM data
938 field as NULL leading to a subsequent NULL ptr deref. For very large values
939 of |i|, the calculation |i * 4| could be a positive value smaller than |i|.
940 In this case memory is allocated to the internal BIGNUM data field, but it
941 is insufficiently sized leading to heap corruption. A similar issue exists
942 in BN_dec2bn. This could have security consequences if BN_hex2bn/BN_dec2bn
943 is ever called by user applications with very large untrusted hex/dec data.
944 This is anticipated to be a rare occurrence.
946 All OpenSSL internal usage of these functions use data that is not expected
947 to be untrusted, e.g. config file data or application command line
948 arguments. If user developed applications generate config file data based
949 on untrusted data then it is possible that this could also lead to security
950 consequences. This is also anticipated to be rare.
952 This issue was reported to OpenSSL by Guido Vranken.
956 *) Fix memory issues in BIO_*printf functions
958 The internal |fmtstr| function used in processing a "%s" format string in
959 the BIO_*printf functions could overflow while calculating the length of a
960 string and cause an OOB read when printing very long strings.
962 Additionally the internal |doapr_outch| function can attempt to write to an
963 OOB memory location (at an offset from the NULL pointer) in the event of a
964 memory allocation failure. In 1.0.2 and below this could be caused where
965 the size of a buffer to be allocated is greater than INT_MAX. E.g. this
966 could be in processing a very long "%s" format string. Memory leaks can
969 The first issue may mask the second issue dependent on compiler behaviour.
970 These problems could enable attacks where large amounts of untrusted data
971 is passed to the BIO_*printf functions. If applications use these functions
972 in this way then they could be vulnerable. OpenSSL itself uses these
973 functions when printing out human-readable dumps of ASN.1 data. Therefore
974 applications that print this data could be vulnerable if the data is from
975 untrusted sources. OpenSSL command line applications could also be
976 vulnerable where they print out ASN.1 data, or if untrusted data is passed
977 as command line arguments.
979 Libssl is not considered directly vulnerable. Additionally certificates etc
980 received via remote connections via libssl are also unlikely to be able to
981 trigger these issues because of message size limits enforced within libssl.
983 This issue was reported to OpenSSL Guido Vranken.
987 *) Side channel attack on modular exponentiation
989 A side-channel attack was found which makes use of cache-bank conflicts on
990 the Intel Sandy-Bridge microarchitecture which could lead to the recovery
991 of RSA keys. The ability to exploit this issue is limited as it relies on
992 an attacker who has control of code in a thread running on the same
993 hyper-threaded core as the victim thread which is performing decryptions.
995 This issue was reported to OpenSSL by Yuval Yarom, The University of
996 Adelaide and NICTA, Daniel Genkin, Technion and Tel Aviv University, and
997 Nadia Heninger, University of Pennsylvania with more information at
998 http://cachebleed.info.
1002 *) Change the req app to generate a 2048-bit RSA/DSA key by default,
1003 if no keysize is specified with default_bits. This fixes an
1004 omission in an earlier change that changed all RSA/DSA key generation
1005 apps to use 2048 bits by default.
1008 Changes between 1.0.2e and 1.0.2f [28 Jan 2016]
1009 *) DH small subgroups
1011 Historically OpenSSL only ever generated DH parameters based on "safe"
1012 primes. More recently (in version 1.0.2) support was provided for
1013 generating X9.42 style parameter files such as those required for RFC 5114
1014 support. The primes used in such files may not be "safe". Where an
1015 application is using DH configured with parameters based on primes that are
1016 not "safe" then an attacker could use this fact to find a peer's private
1017 DH exponent. This attack requires that the attacker complete multiple
1018 handshakes in which the peer uses the same private DH exponent. For example
1019 this could be used to discover a TLS server's private DH exponent if it's
1020 reusing the private DH exponent or it's using a static DH ciphersuite.
1022 OpenSSL provides the option SSL_OP_SINGLE_DH_USE for ephemeral DH (DHE) in
1023 TLS. It is not on by default. If the option is not set then the server
1024 reuses the same private DH exponent for the life of the server process and
1025 would be vulnerable to this attack. It is believed that many popular
1026 applications do set this option and would therefore not be at risk.
1028 The fix for this issue adds an additional check where a "q" parameter is
1029 available (as is the case in X9.42 based parameters). This detects the
1030 only known attack, and is the only possible defense for static DH
1031 ciphersuites. This could have some performance impact.
1033 Additionally the SSL_OP_SINGLE_DH_USE option has been switched on by
1034 default and cannot be disabled. This could have some performance impact.
1036 This issue was reported to OpenSSL by Antonio Sanso (Adobe).
1040 *) SSLv2 doesn't block disabled ciphers
1042 A malicious client can negotiate SSLv2 ciphers that have been disabled on
1043 the server and complete SSLv2 handshakes even if all SSLv2 ciphers have
1044 been disabled, provided that the SSLv2 protocol was not also disabled via
1047 This issue was reported to OpenSSL on 26th December 2015 by Nimrod Aviram
1048 and Sebastian Schinzel.
1052 Changes between 1.0.2d and 1.0.2e [3 Dec 2015]
1054 *) BN_mod_exp may produce incorrect results on x86_64
1056 There is a carry propagating bug in the x86_64 Montgomery squaring
1057 procedure. No EC algorithms are affected. Analysis suggests that attacks
1058 against RSA and DSA as a result of this defect would be very difficult to
1059 perform and are not believed likely. Attacks against DH are considered just
1060 feasible (although very difficult) because most of the work necessary to
1061 deduce information about a private key may be performed offline. The amount
1062 of resources required for such an attack would be very significant and
1063 likely only accessible to a limited number of attackers. An attacker would
1064 additionally need online access to an unpatched system using the target
1065 private key in a scenario with persistent DH parameters and a private
1066 key that is shared between multiple clients. For example this can occur by
1067 default in OpenSSL DHE based SSL/TLS ciphersuites.
1069 This issue was reported to OpenSSL by Hanno Böck.
1073 *) Certificate verify crash with missing PSS parameter
1075 The signature verification routines will crash with a NULL pointer
1076 dereference if presented with an ASN.1 signature using the RSA PSS
1077 algorithm and absent mask generation function parameter. Since these
1078 routines are used to verify certificate signature algorithms this can be
1079 used to crash any certificate verification operation and exploited in a
1080 DoS attack. Any application which performs certificate verification is
1081 vulnerable including OpenSSL clients and servers which enable client
1084 This issue was reported to OpenSSL by Loïc Jonas Etienne (Qnective AG).
1088 *) X509_ATTRIBUTE memory leak
1090 When presented with a malformed X509_ATTRIBUTE structure OpenSSL will leak
1091 memory. This structure is used by the PKCS#7 and CMS routines so any
1092 application which reads PKCS#7 or CMS data from untrusted sources is
1093 affected. SSL/TLS is not affected.
1095 This issue was reported to OpenSSL by Adam Langley (Google/BoringSSL) using
1100 *) Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs.
1101 This changes the decoding behaviour for some invalid messages,
1102 though the change is mostly in the more lenient direction, and
1103 legacy behaviour is preserved as much as possible.
1106 *) In DSA_generate_parameters_ex, if the provided seed is too short,
1108 [Rich Salz and Ismo Puustinen <ismo.puustinen@intel.com>]
1110 Changes between 1.0.2c and 1.0.2d [9 Jul 2015]
1112 *) Alternate chains certificate forgery
1114 During certificate verfification, OpenSSL will attempt to find an
1115 alternative certificate chain if the first attempt to build such a chain
1116 fails. An error in the implementation of this logic can mean that an
1117 attacker could cause certain checks on untrusted certificates to be
1118 bypassed, such as the CA flag, enabling them to use a valid leaf
1119 certificate to act as a CA and "issue" an invalid certificate.
1121 This issue was reported to OpenSSL by Adam Langley/David Benjamin
1125 Changes between 1.0.2b and 1.0.2c [12 Jun 2015]
1127 *) Fix HMAC ABI incompatibility. The previous version introduced an ABI
1128 incompatibility in the handling of HMAC. The previous ABI has now been
1132 Changes between 1.0.2a and 1.0.2b [11 Jun 2015]
1134 *) Malformed ECParameters causes infinite loop
1136 When processing an ECParameters structure OpenSSL enters an infinite loop
1137 if the curve specified is over a specially malformed binary polynomial
1140 This can be used to perform denial of service against any
1141 system which processes public keys, certificate requests or
1142 certificates. This includes TLS clients and TLS servers with
1143 client authentication enabled.
1145 This issue was reported to OpenSSL by Joseph Barr-Pixton.
1149 *) Exploitable out-of-bounds read in X509_cmp_time
1151 X509_cmp_time does not properly check the length of the ASN1_TIME
1152 string and can read a few bytes out of bounds. In addition,
1153 X509_cmp_time accepts an arbitrary number of fractional seconds in the
1156 An attacker can use this to craft malformed certificates and CRLs of
1157 various sizes and potentially cause a segmentation fault, resulting in
1158 a DoS on applications that verify certificates or CRLs. TLS clients
1159 that verify CRLs are affected. TLS clients and servers with client
1160 authentication enabled may be affected if they use custom verification
1163 This issue was reported to OpenSSL by Robert Swiecki (Google), and
1164 independently by Hanno Böck.
1168 *) PKCS7 crash with missing EnvelopedContent
1170 The PKCS#7 parsing code does not handle missing inner EncryptedContent
1171 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs
1172 with missing content and trigger a NULL pointer dereference on parsing.
1174 Applications that decrypt PKCS#7 data or otherwise parse PKCS#7
1175 structures from untrusted sources are affected. OpenSSL clients and
1176 servers are not affected.
1178 This issue was reported to OpenSSL by Michal Zalewski (Google).
1182 *) CMS verify infinite loop with unknown hash function
1184 When verifying a signedData message the CMS code can enter an infinite loop
1185 if presented with an unknown hash function OID. This can be used to perform
1186 denial of service against any system which verifies signedData messages using
1188 This issue was reported to OpenSSL by Johannes Bauer.
1192 *) Race condition handling NewSessionTicket
1194 If a NewSessionTicket is received by a multi-threaded client when attempting to
1195 reuse a previous ticket then a race condition can occur potentially leading to
1196 a double free of the ticket data.
1200 *) Only support 256-bit or stronger elliptic curves with the
1201 'ecdh_auto' setting (server) or by default (client). Of supported
1202 curves, prefer P-256 (both).
1205 Changes between 1.0.2 and 1.0.2a [19 Mar 2015]
1207 *) ClientHello sigalgs DoS fix
1209 If a client connects to an OpenSSL 1.0.2 server and renegotiates with an
1210 invalid signature algorithms extension a NULL pointer dereference will
1211 occur. This can be exploited in a DoS attack against the server.
1213 This issue was was reported to OpenSSL by David Ramos of Stanford
1216 [Stephen Henson and Matt Caswell]
1218 *) Multiblock corrupted pointer fix
1220 OpenSSL 1.0.2 introduced the "multiblock" performance improvement. This
1221 feature only applies on 64 bit x86 architecture platforms that support AES
1222 NI instructions. A defect in the implementation of "multiblock" can cause
1223 OpenSSL's internal write buffer to become incorrectly set to NULL when
1224 using non-blocking IO. Typically, when the user application is using a
1225 socket BIO for writing, this will only result in a failed connection.
1226 However if some other BIO is used then it is likely that a segmentation
1227 fault will be triggered, thus enabling a potential DoS attack.
1229 This issue was reported to OpenSSL by Daniel Danner and Rainer Mueller.
1233 *) Segmentation fault in DTLSv1_listen fix
1235 The DTLSv1_listen function is intended to be stateless and processes the
1236 initial ClientHello from many peers. It is common for user code to loop
1237 over the call to DTLSv1_listen until a valid ClientHello is received with
1238 an associated cookie. A defect in the implementation of DTLSv1_listen means
1239 that state is preserved in the SSL object from one invocation to the next
1240 that can lead to a segmentation fault. Errors processing the initial
1241 ClientHello can trigger this scenario. An example of such an error could be
1242 that a DTLS1.0 only client is attempting to connect to a DTLS1.2 only
1245 This issue was reported to OpenSSL by Per Allansson.
1249 *) Segmentation fault in ASN1_TYPE_cmp fix
1251 The function ASN1_TYPE_cmp will crash with an invalid read if an attempt is
1252 made to compare ASN.1 boolean types. Since ASN1_TYPE_cmp is used to check
1253 certificate signature algorithm consistency this can be used to crash any
1254 certificate verification operation and exploited in a DoS attack. Any
1255 application which performs certificate verification is vulnerable including
1256 OpenSSL clients and servers which enable client authentication.
1260 *) Segmentation fault for invalid PSS parameters fix
1262 The signature verification routines will crash with a NULL pointer
1263 dereference if presented with an ASN.1 signature using the RSA PSS
1264 algorithm and invalid parameters. Since these routines are used to verify
1265 certificate signature algorithms this can be used to crash any
1266 certificate verification operation and exploited in a DoS attack. Any
1267 application which performs certificate verification is vulnerable including
1268 OpenSSL clients and servers which enable client authentication.
1270 This issue was was reported to OpenSSL by Brian Carpenter.
1274 *) ASN.1 structure reuse memory corruption fix
1276 Reusing a structure in ASN.1 parsing may allow an attacker to cause
1277 memory corruption via an invalid write. Such reuse is and has been
1278 strongly discouraged and is believed to be rare.
1280 Applications that parse structures containing CHOICE or ANY DEFINED BY
1281 components may be affected. Certificate parsing (d2i_X509 and related
1282 functions) are however not affected. OpenSSL clients and servers are
1287 *) PKCS7 NULL pointer dereferences fix
1289 The PKCS#7 parsing code does not handle missing outer ContentInfo
1290 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with
1291 missing content and trigger a NULL pointer dereference on parsing.
1293 Applications that verify PKCS#7 signatures, decrypt PKCS#7 data or
1294 otherwise parse PKCS#7 structures from untrusted sources are
1295 affected. OpenSSL clients and servers are not affected.
1297 This issue was reported to OpenSSL by Michal Zalewski (Google).
1301 *) DoS via reachable assert in SSLv2 servers fix
1303 A malicious client can trigger an OPENSSL_assert (i.e., an abort) in
1304 servers that both support SSLv2 and enable export cipher suites by sending
1305 a specially crafted SSLv2 CLIENT-MASTER-KEY message.
1307 This issue was discovered by Sean Burford (Google) and Emilia Käsper
1308 (OpenSSL development team).
1312 *) Empty CKE with client auth and DHE fix
1314 If client auth is used then a server can seg fault in the event of a DHE
1315 ciphersuite being selected and a zero length ClientKeyExchange message
1316 being sent by the client. This could be exploited in a DoS attack.
1320 *) Handshake with unseeded PRNG fix
1322 Under certain conditions an OpenSSL 1.0.2 client can complete a handshake
1323 with an unseeded PRNG. The conditions are:
1324 - The client is on a platform where the PRNG has not been seeded
1325 automatically, and the user has not seeded manually
1326 - A protocol specific client method version has been used (i.e. not
1327 SSL_client_methodv23)
1328 - A ciphersuite is used that does not require additional random data from
1329 the PRNG beyond the initial ClientHello client random (e.g. PSK-RC4-SHA).
1331 If the handshake succeeds then the client random that has been used will
1332 have been generated from a PRNG with insufficient entropy and therefore the
1333 output may be predictable.
1335 For example using the following command with an unseeded openssl will
1336 succeed on an unpatched platform:
1338 openssl s_client -psk 1a2b3c4d -tls1_2 -cipher PSK-RC4-SHA
1342 *) Use After Free following d2i_ECPrivatekey error fix
1344 A malformed EC private key file consumed via the d2i_ECPrivateKey function
1345 could cause a use after free condition. This, in turn, could cause a double
1346 free in several private key parsing functions (such as d2i_PrivateKey
1347 or EVP_PKCS82PKEY) and could lead to a DoS attack or memory corruption
1348 for applications that receive EC private keys from untrusted
1349 sources. This scenario is considered rare.
1351 This issue was discovered by the BoringSSL project and fixed in their
1356 *) X509_to_X509_REQ NULL pointer deref fix
1358 The function X509_to_X509_REQ will crash with a NULL pointer dereference if
1359 the certificate key is invalid. This function is rarely used in practice.
1361 This issue was discovered by Brian Carpenter.
1365 *) Removed the export ciphers from the DEFAULT ciphers
1368 Changes between 1.0.1l and 1.0.2 [22 Jan 2015]
1370 *) Facilitate "universal" ARM builds targeting range of ARM ISAs, e.g.
1371 ARMv5 through ARMv8, as opposite to "locking" it to single one.
1372 So far those who have to target multiple plaforms would compromise
1373 and argue that binary targeting say ARMv5 would still execute on
1374 ARMv8. "Universal" build resolves this compromise by providing
1375 near-optimal performance even on newer platforms.
1378 *) Accelerated NIST P-256 elliptic curve implementation for x86_64
1379 (other platforms pending).
1380 [Shay Gueron & Vlad Krasnov (Intel Corp), Andy Polyakov]
1382 *) Add support for the SignedCertificateTimestampList certificate and
1383 OCSP response extensions from RFC6962.
1386 *) Fix ec_GFp_simple_points_make_affine (thus, EC_POINTs_mul etc.)
1387 for corner cases. (Certain input points at infinity could lead to
1388 bogus results, with non-infinity inputs mapped to infinity too.)
1391 *) Initial support for PowerISA 2.0.7, first implemented in POWER8.
1392 This covers AES, SHA256/512 and GHASH. "Initial" means that most
1393 common cases are optimized and there still is room for further
1394 improvements. Vector Permutation AES for Altivec is also added.
1397 *) Add support for little-endian ppc64 Linux target.
1398 [Marcelo Cerri (IBM)]
1400 *) Initial support for AMRv8 ISA crypto extensions. This covers AES,
1401 SHA1, SHA256 and GHASH. "Initial" means that most common cases
1402 are optimized and there still is room for further improvements.
1403 Both 32- and 64-bit modes are supported.
1404 [Andy Polyakov, Ard Biesheuvel (Linaro)]
1406 *) Improved ARMv7 NEON support.
1409 *) Support for SPARC Architecture 2011 crypto extensions, first
1410 implemented in SPARC T4. This covers AES, DES, Camellia, SHA1,
1411 SHA256/512, MD5, GHASH and modular exponentiation.
1412 [Andy Polyakov, David Miller]
1414 *) Accelerated modular exponentiation for Intel processors, a.k.a.
1416 [Shay Gueron & Vlad Krasnov (Intel Corp)]
1418 *) Support for new and upcoming Intel processors, including AVX2,
1419 BMI and SHA ISA extensions. This includes additional "stitched"
1420 implementations, AESNI-SHA256 and GCM, and multi-buffer support
1423 This work was sponsored by Intel Corp.
1426 *) Support for DTLS 1.2. This adds two sets of DTLS methods: DTLS_*_method()
1427 supports both DTLS 1.2 and 1.0 and should use whatever version the peer
1428 supports and DTLSv1_2_*_method() which supports DTLS 1.2 only.
1431 *) Use algorithm specific chains in SSL_CTX_use_certificate_chain_file():
1432 this fixes a limiation in previous versions of OpenSSL.
1435 *) Extended RSA OAEP support via EVP_PKEY API. Options to specify digest,
1436 MGF1 digest and OAEP label.
1439 *) Add EVP support for key wrapping algorithms, to avoid problems with
1440 existing code the flag EVP_CIPHER_CTX_WRAP_ALLOW has to be set in
1441 the EVP_CIPHER_CTX or an error is returned. Add AES and DES3 wrap
1442 algorithms and include tests cases.
1445 *) Add functions to allocate and set the fields of an ECDSA_METHOD
1447 [Douglas E. Engert, Steve Henson]
1449 *) New functions OPENSSL_gmtime_diff and ASN1_TIME_diff to find the
1450 difference in days and seconds between two tm or ASN1_TIME structures.
1453 *) Add -rev test option to s_server to just reverse order of characters
1454 received by client and send back to server. Also prints an abbreviated
1455 summary of the connection parameters.
1458 *) New option -brief for s_client and s_server to print out a brief summary
1459 of connection parameters.
1462 *) Add callbacks for arbitrary TLS extensions.
1463 [Trevor Perrin <trevp@trevp.net> and Ben Laurie]
1465 *) New option -crl_download in several openssl utilities to download CRLs
1466 from CRLDP extension in certificates.
1469 *) New options -CRL and -CRLform for s_client and s_server for CRLs.
1472 *) New function X509_CRL_diff to generate a delta CRL from the difference
1473 of two full CRLs. Add support to "crl" utility.
1476 *) New functions to set lookup_crls function and to retrieve
1477 X509_STORE from X509_STORE_CTX.
1480 *) Print out deprecated issuer and subject unique ID fields in
1484 *) Extend OCSP I/O functions so they can be used for simple general purpose
1485 HTTP as well as OCSP. New wrapper function which can be used to download
1486 CRLs using the OCSP API.
1489 *) Delegate command line handling in s_client/s_server to SSL_CONF APIs.
1492 *) SSL_CONF* functions. These provide a common framework for application
1493 configuration using configuration files or command lines.
1496 *) SSL/TLS tracing code. This parses out SSL/TLS records using the
1497 message callback and prints the results. Needs compile time option
1498 "enable-ssl-trace". New options to s_client and s_server to enable
1502 *) New ctrl and macro to retrieve supported points extensions.
1503 Print out extension in s_server and s_client.
1506 *) New functions to retrieve certificate signature and signature
1510 *) Add functions to retrieve and manipulate the raw cipherlist sent by a
1514 *) New Suite B modes for TLS code. These use and enforce the requirements
1515 of RFC6460: restrict ciphersuites, only permit Suite B algorithms and
1516 only use Suite B curves. The Suite B modes can be set by using the
1517 strings "SUITEB128", "SUITEB192" or "SUITEB128ONLY" for the cipherstring.
1520 *) New chain verification flags for Suite B levels of security. Check
1521 algorithms are acceptable when flags are set in X509_verify_cert.
1524 *) Make tls1_check_chain return a set of flags indicating checks passed
1525 by a certificate chain. Add additional tests to handle client
1526 certificates: checks for matching certificate type and issuer name
1530 *) If an attempt is made to use a signature algorithm not in the peer
1531 preference list abort the handshake. If client has no suitable
1532 signature algorithms in response to a certificate request do not
1533 use the certificate.
1536 *) If server EC tmp key is not in client preference list abort handshake.
1539 *) Add support for certificate stores in CERT structure. This makes it
1540 possible to have different stores per SSL structure or one store in
1541 the parent SSL_CTX. Include distint stores for certificate chain
1542 verification and chain building. New ctrl SSL_CTRL_BUILD_CERT_CHAIN
1543 to build and store a certificate chain in CERT structure: returing
1544 an error if the chain cannot be built: this will allow applications
1545 to test if a chain is correctly configured.
1547 Note: if the CERT based stores are not set then the parent SSL_CTX
1548 store is used to retain compatibility with existing behaviour.
1552 *) New function ssl_set_client_disabled to set a ciphersuite disabled
1553 mask based on the current session, check mask when sending client
1554 hello and checking the requested ciphersuite.
1557 *) New ctrls to retrieve and set certificate types in a certificate
1558 request message. Print out received values in s_client. If certificate
1559 types is not set with custom values set sensible values based on
1560 supported signature algorithms.
1563 *) Support for distinct client and server supported signature algorithms.
1566 *) Add certificate callback. If set this is called whenever a certificate
1567 is required by client or server. An application can decide which
1568 certificate chain to present based on arbitrary criteria: for example
1569 supported signature algorithms. Add very simple example to s_server.
1570 This fixes many of the problems and restrictions of the existing client
1571 certificate callback: for example you can now clear an existing
1572 certificate and specify the whole chain.
1575 *) Add new "valid_flags" field to CERT_PKEY structure which determines what
1576 the certificate can be used for (if anything). Set valid_flags field
1577 in new tls1_check_chain function. Simplify ssl_set_cert_masks which used
1578 to have similar checks in it.
1580 Add new "cert_flags" field to CERT structure and include a "strict mode".
1581 This enforces some TLS certificate requirements (such as only permitting
1582 certificate signature algorithms contained in the supported algorithms
1583 extension) which some implementations ignore: this option should be used
1584 with caution as it could cause interoperability issues.
1587 *) Update and tidy signature algorithm extension processing. Work out
1588 shared signature algorithms based on preferences and peer algorithms
1589 and print them out in s_client and s_server. Abort handshake if no
1590 shared signature algorithms.
1593 *) Add new functions to allow customised supported signature algorithms
1594 for SSL and SSL_CTX structures. Add options to s_client and s_server
1598 *) New function SSL_certs_clear() to delete all references to certificates
1599 from an SSL structure. Before this once a certificate had been added
1600 it couldn't be removed.
1603 *) Integrate hostname, email address and IP address checking with certificate
1604 verification. New verify options supporting checking in opensl utility.
1607 *) Fixes and wildcard matching support to hostname and email checking
1608 functions. Add manual page.
1609 [Florian Weimer (Red Hat Product Security Team)]
1611 *) New functions to check a hostname email or IP address against a
1612 certificate. Add options x509 utility to print results of checks against
1616 *) Fix OCSP checking.
1617 [Rob Stradling <rob.stradling@comodo.com> and Ben Laurie]
1619 *) Initial experimental support for explicitly trusted non-root CAs.
1620 OpenSSL still tries to build a complete chain to a root but if an
1621 intermediate CA has a trust setting included that is used. The first
1622 setting is used: whether to trust (e.g., -addtrust option to the x509
1626 *) Add -trusted_first option which attempts to find certificates in the
1627 trusted store even if an untrusted chain is also supplied.
1630 *) MIPS assembly pack updates: support for MIPS32r2 and SmartMIPS ASE,
1631 platform support for Linux and Android.
1634 *) Support for linux-x32, ILP32 environment in x86_64 framework.
1637 *) Experimental multi-implementation support for FIPS capable OpenSSL.
1638 When in FIPS mode the approved implementations are used as normal,
1639 when not in FIPS mode the internal unapproved versions are used instead.
1640 This means that the FIPS capable OpenSSL isn't forced to use the
1641 (often lower performance) FIPS implementations outside FIPS mode.
1644 *) Transparently support X9.42 DH parameters when calling
1645 PEM_read_bio_DHparameters. This means existing applications can handle
1646 the new parameter format automatically.
1649 *) Initial experimental support for X9.42 DH parameter format: mainly
1650 to support use of 'q' parameter for RFC5114 parameters.
1653 *) Add DH parameters from RFC5114 including test data to dhtest.
1656 *) Support for automatic EC temporary key parameter selection. If enabled
1657 the most preferred EC parameters are automatically used instead of
1658 hardcoded fixed parameters. Now a server just has to call:
1659 SSL_CTX_set_ecdh_auto(ctx, 1) and the server will automatically
1660 support ECDH and use the most appropriate parameters.
1663 *) Enhance and tidy EC curve and point format TLS extension code. Use
1664 static structures instead of allocation if default values are used.
1665 New ctrls to set curves we wish to support and to retrieve shared curves.
1666 Print out shared curves in s_server. New options to s_server and s_client
1667 to set list of supported curves.
1670 *) New ctrls to retrieve supported signature algorithms and
1671 supported curve values as an array of NIDs. Extend openssl utility
1672 to print out received values.
1675 *) Add new APIs EC_curve_nist2nid and EC_curve_nid2nist which convert
1676 between NIDs and the more common NIST names such as "P-256". Enhance
1677 ecparam utility and ECC method to recognise the NIST names for curves.
1680 *) Enhance SSL/TLS certificate chain handling to support different
1681 chains for each certificate instead of one chain in the parent SSL_CTX.
1684 *) Support for fixed DH ciphersuite client authentication: where both
1685 server and client use DH certificates with common parameters.
1688 *) Support for fixed DH ciphersuites: those requiring DH server
1692 *) New function i2d_re_X509_tbs for re-encoding the TBS portion of
1694 Note: Related 1.0.2-beta specific macros X509_get_cert_info,
1695 X509_CINF_set_modified, X509_CINF_get_issuer, X509_CINF_get_extensions and
1696 X509_CINF_get_signature were reverted post internal team review.
1698 Changes between 1.0.1k and 1.0.1l [15 Jan 2015]
1700 *) Build fixes for the Windows and OpenVMS platforms
1701 [Matt Caswell and Richard Levitte]
1703 Changes between 1.0.1j and 1.0.1k [8 Jan 2015]
1705 *) Fix DTLS segmentation fault in dtls1_get_record. A carefully crafted DTLS
1706 message can cause a segmentation fault in OpenSSL due to a NULL pointer
1707 dereference. This could lead to a Denial Of Service attack. Thanks to
1708 Markus Stenberg of Cisco Systems, Inc. for reporting this issue.
1712 *) Fix DTLS memory leak in dtls1_buffer_record. A memory leak can occur in the
1713 dtls1_buffer_record function under certain conditions. In particular this
1714 could occur if an attacker sent repeated DTLS records with the same
1715 sequence number but for the next epoch. The memory leak could be exploited
1716 by an attacker in a Denial of Service attack through memory exhaustion.
1717 Thanks to Chris Mueller for reporting this issue.
1721 *) Fix issue where no-ssl3 configuration sets method to NULL. When openssl is
1722 built with the no-ssl3 option and a SSL v3 ClientHello is received the ssl
1723 method would be set to NULL which could later result in a NULL pointer
1724 dereference. Thanks to Frank Schmirler for reporting this issue.
1728 *) Abort handshake if server key exchange message is omitted for ephemeral
1731 Thanks to Karthikeyan Bhargavan of the PROSECCO team at INRIA for
1732 reporting this issue.
1736 *) Remove non-export ephemeral RSA code on client and server. This code
1737 violated the TLS standard by allowing the use of temporary RSA keys in
1738 non-export ciphersuites and could be used by a server to effectively
1739 downgrade the RSA key length used to a value smaller than the server
1740 certificate. Thanks for Karthikeyan Bhargavan of the PROSECCO team at
1741 INRIA or reporting this issue.
1745 *) Fixed issue where DH client certificates are accepted without verification.
1746 An OpenSSL server will accept a DH certificate for client authentication
1747 without the certificate verify message. This effectively allows a client to
1748 authenticate without the use of a private key. This only affects servers
1749 which trust a client certificate authority which issues certificates
1750 containing DH keys: these are extremely rare and hardly ever encountered.
1751 Thanks for Karthikeyan Bhargavan of the PROSECCO team at INRIA or reporting
1756 *) Ensure that the session ID context of an SSL is updated when its
1757 SSL_CTX is updated via SSL_set_SSL_CTX.
1759 The session ID context is typically set from the parent SSL_CTX,
1760 and can vary with the CTX.
1763 *) Fix various certificate fingerprint issues.
1765 By using non-DER or invalid encodings outside the signed portion of a
1766 certificate the fingerprint can be changed without breaking the signature.
1767 Although no details of the signed portion of the certificate can be changed
1768 this can cause problems with some applications: e.g. those using the
1769 certificate fingerprint for blacklists.
1771 1. Reject signatures with non zero unused bits.
1773 If the BIT STRING containing the signature has non zero unused bits reject
1774 the signature. All current signature algorithms require zero unused bits.
1776 2. Check certificate algorithm consistency.
1778 Check the AlgorithmIdentifier inside TBS matches the one in the
1779 certificate signature. NB: this will result in signature failure
1780 errors for some broken certificates.
1782 Thanks to Konrad Kraszewski from Google for reporting this issue.
1784 3. Check DSA/ECDSA signatures use DER.
1786 Reencode DSA/ECDSA signatures and compare with the original received
1787 signature. Return an error if there is a mismatch.
1789 This will reject various cases including garbage after signature
1790 (thanks to Antti Karjalainen and Tuomo Untinen from the Codenomicon CROSS
1791 program for discovering this case) and use of BER or invalid ASN.1 INTEGERs
1792 (negative or with leading zeroes).
1794 Further analysis was conducted and fixes were developed by Stephen Henson
1795 of the OpenSSL core team.
1800 *) Correct Bignum squaring. Bignum squaring (BN_sqr) may produce incorrect
1801 results on some platforms, including x86_64. This bug occurs at random
1802 with a very low probability, and is not known to be exploitable in any
1803 way, though its exact impact is difficult to determine. Thanks to Pieter
1804 Wuille (Blockstream) who reported this issue and also suggested an initial
1805 fix. Further analysis was conducted by the OpenSSL development team and
1806 Adam Langley of Google. The final fix was developed by Andy Polyakov of
1807 the OpenSSL core team.
1811 *) Do not resume sessions on the server if the negotiated protocol
1812 version does not match the session's version. Resuming with a different
1813 version, while not strictly forbidden by the RFC, is of questionable
1814 sanity and breaks all known clients.
1815 [David Benjamin, Emilia Käsper]
1817 *) Tighten handling of the ChangeCipherSpec (CCS) message: reject
1818 early CCS messages during renegotiation. (Note that because
1819 renegotiation is encrypted, this early CCS was not exploitable.)
1822 *) Tighten client-side session ticket handling during renegotiation:
1823 ensure that the client only accepts a session ticket if the server sends
1824 the extension anew in the ServerHello. Previously, a TLS client would
1825 reuse the old extension state and thus accept a session ticket if one was
1826 announced in the initial ServerHello.
1828 Similarly, ensure that the client requires a session ticket if one
1829 was advertised in the ServerHello. Previously, a TLS client would
1830 ignore a missing NewSessionTicket message.
1833 Changes between 1.0.1i and 1.0.1j [15 Oct 2014]
1835 *) SRTP Memory Leak.
1837 A flaw in the DTLS SRTP extension parsing code allows an attacker, who
1838 sends a carefully crafted handshake message, to cause OpenSSL to fail
1839 to free up to 64k of memory causing a memory leak. This could be
1840 exploited in a Denial Of Service attack. This issue affects OpenSSL
1841 1.0.1 server implementations for both SSL/TLS and DTLS regardless of
1842 whether SRTP is used or configured. Implementations of OpenSSL that
1843 have been compiled with OPENSSL_NO_SRTP defined are not affected.
1845 The fix was developed by the OpenSSL team.
1849 *) Session Ticket Memory Leak.
1851 When an OpenSSL SSL/TLS/DTLS server receives a session ticket the
1852 integrity of that ticket is first verified. In the event of a session
1853 ticket integrity check failing, OpenSSL will fail to free memory
1854 causing a memory leak. By sending a large number of invalid session
1855 tickets an attacker could exploit this issue in a Denial Of Service
1860 *) Build option no-ssl3 is incomplete.
1862 When OpenSSL is configured with "no-ssl3" as a build option, servers
1863 could accept and complete a SSL 3.0 handshake, and clients could be
1864 configured to send them.
1866 [Akamai and the OpenSSL team]
1868 *) Add support for TLS_FALLBACK_SCSV.
1869 Client applications doing fallback retries should call
1870 SSL_set_mode(s, SSL_MODE_SEND_FALLBACK_SCSV).
1872 [Adam Langley, Bodo Moeller]
1874 *) Add additional DigestInfo checks.
1876 Reencode DigestInto in DER and check against the original when
1877 verifying RSA signature: this will reject any improperly encoded
1878 DigestInfo structures.
1880 Note: this is a precautionary measure and no attacks are currently known.
1884 Changes between 1.0.1h and 1.0.1i [6 Aug 2014]
1886 *) Fix SRP buffer overrun vulnerability. Invalid parameters passed to the
1887 SRP code can be overrun an internal buffer. Add sanity check that
1888 g, A, B < N to SRP code.
1890 Thanks to Sean Devlin and Watson Ladd of Cryptography Services, NCC
1891 Group for discovering this issue.
1895 *) A flaw in the OpenSSL SSL/TLS server code causes the server to negotiate
1896 TLS 1.0 instead of higher protocol versions when the ClientHello message
1897 is badly fragmented. This allows a man-in-the-middle attacker to force a
1898 downgrade to TLS 1.0 even if both the server and the client support a
1899 higher protocol version, by modifying the client's TLS records.
1901 Thanks to David Benjamin and Adam Langley (Google) for discovering and
1902 researching this issue.
1906 *) OpenSSL DTLS clients enabling anonymous (EC)DH ciphersuites are subject
1907 to a denial of service attack. A malicious server can crash the client
1908 with a null pointer dereference (read) by specifying an anonymous (EC)DH
1909 ciphersuite and sending carefully crafted handshake messages.
1911 Thanks to Felix Gröbert (Google) for discovering and researching this
1916 *) By sending carefully crafted DTLS packets an attacker could cause openssl
1917 to leak memory. This can be exploited through a Denial of Service attack.
1918 Thanks to Adam Langley for discovering and researching this issue.
1922 *) An attacker can force openssl to consume large amounts of memory whilst
1923 processing DTLS handshake messages. This can be exploited through a
1924 Denial of Service attack.
1925 Thanks to Adam Langley for discovering and researching this issue.
1929 *) An attacker can force an error condition which causes openssl to crash
1930 whilst processing DTLS packets due to memory being freed twice. This
1931 can be exploited through a Denial of Service attack.
1932 Thanks to Adam Langley and Wan-Teh Chang for discovering and researching
1937 *) If a multithreaded client connects to a malicious server using a resumed
1938 session and the server sends an ec point format extension it could write
1939 up to 255 bytes to freed memory.
1941 Thanks to Gabor Tyukasz (LogMeIn Inc) for discovering and researching this
1946 *) A malicious server can crash an OpenSSL client with a null pointer
1947 dereference (read) by specifying an SRP ciphersuite even though it was not
1948 properly negotiated with the client. This can be exploited through a
1949 Denial of Service attack.
1951 Thanks to Joonas Kuorilehto and Riku Hietamäki (Codenomicon) for
1952 discovering and researching this issue.
1956 *) A flaw in OBJ_obj2txt may cause pretty printing functions such as
1957 X509_name_oneline, X509_name_print_ex et al. to leak some information
1958 from the stack. Applications may be affected if they echo pretty printing
1959 output to the attacker.
1961 Thanks to Ivan Fratric (Google) for discovering this issue.
1963 [Emilia Käsper, and Steve Henson]
1965 *) Fix ec_GFp_simple_points_make_affine (thus, EC_POINTs_mul etc.)
1966 for corner cases. (Certain input points at infinity could lead to
1967 bogus results, with non-infinity inputs mapped to infinity too.)
1970 Changes between 1.0.1g and 1.0.1h [5 Jun 2014]
1972 *) Fix for SSL/TLS MITM flaw. An attacker using a carefully crafted
1973 handshake can force the use of weak keying material in OpenSSL
1974 SSL/TLS clients and servers.
1976 Thanks to KIKUCHI Masashi (Lepidum Co. Ltd.) for discovering and
1977 researching this issue. (CVE-2014-0224)
1978 [KIKUCHI Masashi, Steve Henson]
1980 *) Fix DTLS recursion flaw. By sending an invalid DTLS handshake to an
1981 OpenSSL DTLS client the code can be made to recurse eventually crashing
1984 Thanks to Imre Rad (Search-Lab Ltd.) for discovering this issue.
1986 [Imre Rad, Steve Henson]
1988 *) Fix DTLS invalid fragment vulnerability. A buffer overrun attack can
1989 be triggered by sending invalid DTLS fragments to an OpenSSL DTLS
1990 client or server. This is potentially exploitable to run arbitrary
1991 code on a vulnerable client or server.
1993 Thanks to Jüri Aedla for reporting this issue. (CVE-2014-0195)
1994 [Jüri Aedla, Steve Henson]
1996 *) Fix bug in TLS code where clients enable anonymous ECDH ciphersuites
1997 are subject to a denial of service attack.
1999 Thanks to Felix Gröbert and Ivan Fratric at Google for discovering
2000 this issue. (CVE-2014-3470)
2001 [Felix Gröbert, Ivan Fratric, Steve Henson]
2003 *) Harmonize version and its documentation. -f flag is used to display
2005 [mancha <mancha1@zoho.com>]
2007 *) Fix eckey_priv_encode so it immediately returns an error upon a failure
2008 in i2d_ECPrivateKey.
2009 [mancha <mancha1@zoho.com>]
2011 *) Fix some double frees. These are not thought to be exploitable.
2012 [mancha <mancha1@zoho.com>]
2014 Changes between 1.0.1f and 1.0.1g [7 Apr 2014]
2016 *) A missing bounds check in the handling of the TLS heartbeat extension
2017 can be used to reveal up to 64k of memory to a connected client or
2020 Thanks for Neel Mehta of Google Security for discovering this bug and to
2021 Adam Langley <agl@chromium.org> and Bodo Moeller <bmoeller@acm.org> for
2022 preparing the fix (CVE-2014-0160)
2023 [Adam Langley, Bodo Moeller]
2025 *) Fix for the attack described in the paper "Recovering OpenSSL
2026 ECDSA Nonces Using the FLUSH+RELOAD Cache Side-channel Attack"
2027 by Yuval Yarom and Naomi Benger. Details can be obtained from:
2028 http://eprint.iacr.org/2014/140
2030 Thanks to Yuval Yarom and Naomi Benger for discovering this
2031 flaw and to Yuval Yarom for supplying a fix (CVE-2014-0076)
2032 [Yuval Yarom and Naomi Benger]
2034 *) TLS pad extension: draft-agl-tls-padding-03
2036 Workaround for the "TLS hang bug" (see FAQ and PR#2771): if the
2037 TLS client Hello record length value would otherwise be > 255 and
2038 less that 512 pad with a dummy extension containing zeroes so it
2039 is at least 512 bytes long.
2041 [Adam Langley, Steve Henson]
2043 Changes between 1.0.1e and 1.0.1f [6 Jan 2014]
2045 *) Fix for TLS record tampering bug. A carefully crafted invalid
2046 handshake could crash OpenSSL with a NULL pointer exception.
2047 Thanks to Anton Johansson for reporting this issues.
2050 *) Keep original DTLS digest and encryption contexts in retransmission
2051 structures so we can use the previous session parameters if they need
2052 to be resent. (CVE-2013-6450)
2055 *) Add option SSL_OP_SAFARI_ECDHE_ECDSA_BUG (part of SSL_OP_ALL) which
2056 avoids preferring ECDHE-ECDSA ciphers when the client appears to be
2057 Safari on OS X. Safari on OS X 10.8..10.8.3 advertises support for
2058 several ECDHE-ECDSA ciphers, but fails to negotiate them. The bug
2059 is fixed in OS X 10.8.4, but Apple have ruled out both hot fixing
2060 10.8..10.8.3 and forcing users to upgrade to 10.8.4 or newer.
2061 [Rob Stradling, Adam Langley]
2063 Changes between 1.0.1d and 1.0.1e [11 Feb 2013]
2065 *) Correct fix for CVE-2013-0169. The original didn't work on AES-NI
2066 supporting platforms or when small records were transferred.
2067 [Andy Polyakov, Steve Henson]
2069 Changes between 1.0.1c and 1.0.1d [5 Feb 2013]
2071 *) Make the decoding of SSLv3, TLS and DTLS CBC records constant time.
2073 This addresses the flaw in CBC record processing discovered by
2074 Nadhem Alfardan and Kenny Paterson. Details of this attack can be found
2075 at: http://www.isg.rhul.ac.uk/tls/
2077 Thanks go to Nadhem Alfardan and Kenny Paterson of the Information
2078 Security Group at Royal Holloway, University of London
2079 (www.isg.rhul.ac.uk) for discovering this flaw and Adam Langley and
2080 Emilia Käsper for the initial patch.
2082 [Emilia Käsper, Adam Langley, Ben Laurie, Andy Polyakov, Steve Henson]
2084 *) Fix flaw in AESNI handling of TLS 1.2 and 1.1 records for CBC mode
2085 ciphersuites which can be exploited in a denial of service attack.
2086 Thanks go to and to Adam Langley <agl@chromium.org> for discovering
2087 and detecting this bug and to Wolfgang Ettlinger
2088 <wolfgang.ettlinger@gmail.com> for independently discovering this issue.
2092 *) Return an error when checking OCSP signatures when key is NULL.
2093 This fixes a DoS attack. (CVE-2013-0166)
2096 *) Make openssl verify return errors.
2097 [Chris Palmer <palmer@google.com> and Ben Laurie]
2099 *) Call OCSP Stapling callback after ciphersuite has been chosen, so
2100 the right response is stapled. Also change SSL_get_certificate()
2101 so it returns the certificate actually sent.
2102 See http://rt.openssl.org/Ticket/Display.html?id=2836.
2103 [Rob Stradling <rob.stradling@comodo.com>]
2105 *) Fix possible deadlock when decoding public keys.
2108 *) Don't use TLS 1.0 record version number in initial client hello
2112 Changes between 1.0.1b and 1.0.1c [10 May 2012]
2114 *) Sanity check record length before skipping explicit IV in TLS
2115 1.2, 1.1 and DTLS to fix DoS attack.
2117 Thanks to Codenomicon for discovering this issue using Fuzz-o-Matic
2118 fuzzing as a service testing platform.
2122 *) Initialise tkeylen properly when encrypting CMS messages.
2123 Thanks to Solar Designer of Openwall for reporting this issue.
2126 *) In FIPS mode don't try to use composite ciphers as they are not
2130 Changes between 1.0.1a and 1.0.1b [26 Apr 2012]
2132 *) OpenSSL 1.0.0 sets SSL_OP_ALL to 0x80000FFFL and OpenSSL 1.0.1 and
2133 1.0.1a set SSL_OP_NO_TLSv1_1 to 0x00000400L which would unfortunately
2134 mean any application compiled against OpenSSL 1.0.0 headers setting
2135 SSL_OP_ALL would also set SSL_OP_NO_TLSv1_1, unintentionally disablng
2136 TLS 1.1 also. Fix this by changing the value of SSL_OP_NO_TLSv1_1 to
2137 0x10000000L Any application which was previously compiled against
2138 OpenSSL 1.0.1 or 1.0.1a headers and which cares about SSL_OP_NO_TLSv1_1
2139 will need to be recompiled as a result. Letting be results in
2140 inability to disable specifically TLS 1.1 and in client context,
2141 in unlike event, limit maximum offered version to TLS 1.0 [see below].
2144 *) In order to ensure interoperabilty SSL_OP_NO_protocolX does not
2145 disable just protocol X, but all protocols above X *if* there are
2146 protocols *below* X still enabled. In more practical terms it means
2147 that if application wants to disable TLS1.0 in favor of TLS1.1 and
2148 above, it's not sufficient to pass SSL_OP_NO_TLSv1, one has to pass
2149 SSL_OP_NO_TLSv1|SSL_OP_NO_SSLv3|SSL_OP_NO_SSLv2. This applies to
2153 Changes between 1.0.1 and 1.0.1a [19 Apr 2012]
2155 *) Check for potentially exploitable overflows in asn1_d2i_read_bio
2156 BUF_mem_grow and BUF_mem_grow_clean. Refuse attempts to shrink buffer
2157 in CRYPTO_realloc_clean.
2159 Thanks to Tavis Ormandy, Google Security Team, for discovering this
2160 issue and to Adam Langley <agl@chromium.org> for fixing it.
2162 [Adam Langley (Google), Tavis Ormandy, Google Security Team]
2164 *) Don't allow TLS 1.2 SHA-256 ciphersuites in TLS 1.0, 1.1 connections.
2167 *) Workarounds for some broken servers that "hang" if a client hello
2168 record length exceeds 255 bytes.
2170 1. Do not use record version number > TLS 1.0 in initial client
2171 hello: some (but not all) hanging servers will now work.
2172 2. If we set OPENSSL_MAX_TLS1_2_CIPHER_LENGTH this will truncate
2173 the number of ciphers sent in the client hello. This should be
2174 set to an even number, such as 50, for example by passing:
2175 -DOPENSSL_MAX_TLS1_2_CIPHER_LENGTH=50 to config or Configure.
2176 Most broken servers should now work.
2177 3. If all else fails setting OPENSSL_NO_TLS1_2_CLIENT will disable
2178 TLS 1.2 client support entirely.
2181 *) Fix SEGV in Vector Permutation AES module observed in OpenSSH.
2184 Changes between 1.0.0h and 1.0.1 [14 Mar 2012]
2186 *) Add compatibility with old MDC2 signatures which use an ASN1 OCTET
2187 STRING form instead of a DigestInfo.
2190 *) The format used for MDC2 RSA signatures is inconsistent between EVP
2191 and the RSA_sign/RSA_verify functions. This was made more apparent when
2192 OpenSSL used RSA_sign/RSA_verify for some RSA signatures in particular
2193 those which went through EVP_PKEY_METHOD in 1.0.0 and later. Detect
2194 the correct format in RSA_verify so both forms transparently work.
2197 *) Some servers which support TLS 1.0 can choke if we initially indicate
2198 support for TLS 1.2 and later renegotiate using TLS 1.0 in the RSA
2199 encrypted premaster secret. As a workaround use the maximum permitted
2200 client version in client hello, this should keep such servers happy
2201 and still work with previous versions of OpenSSL.
2204 *) Add support for TLS/DTLS heartbeats.
2205 [Robin Seggelmann <seggelmann@fh-muenster.de>]
2207 *) Add support for SCTP.
2208 [Robin Seggelmann <seggelmann@fh-muenster.de>]
2210 *) Improved PRNG seeding for VOS.
2211 [Paul Green <Paul.Green@stratus.com>]
2213 *) Extensive assembler packs updates, most notably:
2215 - x86[_64]: AES-NI, PCLMULQDQ, RDRAND support;
2216 - x86[_64]: SSSE3 support (SHA1, vector-permutation AES);
2217 - x86_64: bit-sliced AES implementation;
2218 - ARM: NEON support, contemporary platforms optimizations;
2219 - s390x: z196 support;
2220 - *: GHASH and GF(2^m) multiplication implementations;
2224 *) Make TLS-SRP code conformant with RFC 5054 API cleanup
2225 (removal of unnecessary code)
2226 [Peter Sylvester <peter.sylvester@edelweb.fr>]
2228 *) Add TLS key material exporter from RFC 5705.
2231 *) Add DTLS-SRTP negotiation from RFC 5764.
2234 *) Add Next Protocol Negotiation,
2235 http://tools.ietf.org/html/draft-agl-tls-nextprotoneg-00. Can be
2236 disabled with a no-npn flag to config or Configure. Code donated
2238 [Adam Langley <agl@google.com> and Ben Laurie]
2240 *) Add optional 64-bit optimized implementations of elliptic curves NIST-P224,
2241 NIST-P256, NIST-P521, with constant-time single point multiplication on
2242 typical inputs. Compiler support for the nonstandard type __uint128_t is
2243 required to use this (present in gcc 4.4 and later, for 64-bit builds).
2244 Code made available under Apache License version 2.0.
2246 Specify "enable-ec_nistp_64_gcc_128" on the Configure (or config) command
2247 line to include this in your build of OpenSSL, and run "make depend" (or
2248 "make update"). This enables the following EC_METHODs:
2250 EC_GFp_nistp224_method()
2251 EC_GFp_nistp256_method()
2252 EC_GFp_nistp521_method()
2254 EC_GROUP_new_by_curve_name() will automatically use these (while
2255 EC_GROUP_new_curve_GFp() currently prefers the more flexible
2257 [Emilia Käsper, Adam Langley, Bodo Moeller (Google)]
2259 *) Use type ossl_ssize_t instad of ssize_t which isn't available on
2260 all platforms. Move ssize_t definition from e_os.h to the public
2261 header file e_os2.h as it now appears in public header file cms.h
2264 *) New -sigopt option to the ca, req and x509 utilities. Additional
2265 signature parameters can be passed using this option and in
2269 *) Add RSA PSS signing function. This will generate and set the
2270 appropriate AlgorithmIdentifiers for PSS based on those in the
2271 corresponding EVP_MD_CTX structure. No application support yet.
2274 *) Support for companion algorithm specific ASN1 signing routines.
2275 New function ASN1_item_sign_ctx() signs a pre-initialised
2276 EVP_MD_CTX structure and sets AlgorithmIdentifiers based on
2277 the appropriate parameters.
2280 *) Add new algorithm specific ASN1 verification initialisation function
2281 to EVP_PKEY_ASN1_METHOD: this is not in EVP_PKEY_METHOD since the ASN1
2282 handling will be the same no matter what EVP_PKEY_METHOD is used.
2283 Add a PSS handler to support verification of PSS signatures: checked
2284 against a number of sample certificates.
2287 *) Add signature printing for PSS. Add PSS OIDs.
2288 [Steve Henson, Martin Kaiser <lists@kaiser.cx>]
2290 *) Add algorithm specific signature printing. An individual ASN1 method
2291 can now print out signatures instead of the standard hex dump.
2293 More complex signatures (e.g. PSS) can print out more meaningful
2294 information. Include DSA version that prints out the signature
2298 *) Password based recipient info support for CMS library: implementing
2302 *) Split password based encryption into PBES2 and PBKDF2 functions. This
2303 neatly separates the code into cipher and PBE sections and is required
2304 for some algorithms that split PBES2 into separate pieces (such as
2305 password based CMS).
2308 *) Session-handling fixes:
2309 - Fix handling of connections that are resuming with a session ID,
2310 but also support Session Tickets.
2311 - Fix a bug that suppressed issuing of a new ticket if the client
2312 presented a ticket with an expired session.
2313 - Try to set the ticket lifetime hint to something reasonable.
2314 - Make tickets shorter by excluding irrelevant information.
2315 - On the client side, don't ignore renewed tickets.
2316 [Adam Langley, Bodo Moeller (Google)]
2318 *) Fix PSK session representation.
2321 *) Add RC4-MD5 and AESNI-SHA1 "stitched" implementations.
2323 This work was sponsored by Intel.
2326 *) Add GCM support to TLS library. Some custom code is needed to split
2327 the IV between the fixed (from PRF) and explicit (from TLS record)
2328 portions. This adds all GCM ciphersuites supported by RFC5288 and
2329 RFC5289. Generalise some AES* cipherstrings to include GCM and
2330 add a special AESGCM string for GCM only.
2333 *) Expand range of ctrls for AES GCM. Permit setting invocation
2334 field on decrypt and retrieval of invocation field only on encrypt.
2337 *) Add HMAC ECC ciphersuites from RFC5289. Include SHA384 PRF support.
2338 As required by RFC5289 these ciphersuites cannot be used if for
2339 versions of TLS earlier than 1.2.
2342 *) For FIPS capable OpenSSL interpret a NULL default public key method
2343 as unset and return the appropriate default but do *not* set the default.
2344 This means we can return the appropriate method in applications that
2345 switch between FIPS and non-FIPS modes.
2348 *) Redirect HMAC and CMAC operations to FIPS module in FIPS mode. If an
2349 ENGINE is used then we cannot handle that in the FIPS module so we
2350 keep original code iff non-FIPS operations are allowed.
2353 *) Add -attime option to openssl utilities.
2354 [Peter Eckersley <pde@eff.org>, Ben Laurie and Steve Henson]
2356 *) Redirect DSA and DH operations to FIPS module in FIPS mode.
2359 *) Redirect ECDSA and ECDH operations to FIPS module in FIPS mode. Also use
2360 FIPS EC methods unconditionally for now.
2363 *) New build option no-ec2m to disable characteristic 2 code.
2366 *) Backport libcrypto audit of return value checking from 1.1.0-dev; not
2367 all cases can be covered as some introduce binary incompatibilities.
2370 *) Redirect RSA operations to FIPS module including keygen,
2371 encrypt, decrypt, sign and verify. Block use of non FIPS RSA methods.
2374 *) Add similar low level API blocking to ciphers.
2377 *) Low level digest APIs are not approved in FIPS mode: any attempt
2378 to use these will cause a fatal error. Applications that *really* want
2379 to use them can use the private_* version instead.
2382 *) Redirect cipher operations to FIPS module for FIPS builds.
2385 *) Redirect digest operations to FIPS module for FIPS builds.
2388 *) Update build system to add "fips" flag which will link in fipscanister.o
2389 for static and shared library builds embedding a signature if needed.
2392 *) Output TLS supported curves in preference order instead of numerical
2393 order. This is currently hardcoded for the highest order curves first.
2394 This should be configurable so applications can judge speed vs strength.
2397 *) Add TLS v1.2 server support for client authentication.
2400 *) Add support for FIPS mode in ssl library: disable SSLv3, non-FIPS ciphers
2404 *) Functions FIPS_mode_set() and FIPS_mode() which call the underlying
2405 FIPS modules versions.
2408 *) Add TLS v1.2 client side support for client authentication. Keep cache
2409 of handshake records longer as we don't know the hash algorithm to use
2410 until after the certificate request message is received.
2413 *) Initial TLS v1.2 client support. Add a default signature algorithms
2414 extension including all the algorithms we support. Parse new signature
2415 format in client key exchange. Relax some ECC signing restrictions for
2416 TLS v1.2 as indicated in RFC5246.
2419 *) Add server support for TLS v1.2 signature algorithms extension. Switch
2420 to new signature format when needed using client digest preference.
2421 All server ciphersuites should now work correctly in TLS v1.2. No client
2422 support yet and no support for client certificates.
2425 *) Initial TLS v1.2 support. Add new SHA256 digest to ssl code, switch
2426 to SHA256 for PRF when using TLS v1.2 and later. Add new SHA256 based
2427 ciphersuites. At present only RSA key exchange ciphersuites work with
2428 TLS v1.2. Add new option for TLS v1.2 replacing the old and obsolete
2429 SSL_OP_PKCS1_CHECK flags with SSL_OP_NO_TLSv1_2. New TLSv1.2 methods
2430 and version checking.
2433 *) New option OPENSSL_NO_SSL_INTERN. If an application can be compiled
2434 with this defined it will not be affected by any changes to ssl internal
2435 structures. Add several utility functions to allow openssl application
2436 to work with OPENSSL_NO_SSL_INTERN defined.
2440 [Tom Wu <tjw@cs.stanford.edu> and Ben Laurie]
2442 *) Add functions to copy EVP_PKEY_METHOD and retrieve flags and id.
2445 *) Permit abbreviated handshakes when renegotiating using the function
2446 SSL_renegotiate_abbreviated().
2447 [Robin Seggelmann <seggelmann@fh-muenster.de>]
2449 *) Add call to ENGINE_register_all_complete() to
2450 ENGINE_load_builtin_engines(), so some implementations get used
2451 automatically instead of needing explicit application support.
2454 *) Add support for TLS key exporter as described in RFC5705.
2455 [Robin Seggelmann <seggelmann@fh-muenster.de>, Steve Henson]
2457 *) Initial TLSv1.1 support. Since TLSv1.1 is very similar to TLS v1.0 only
2458 a few changes are required:
2460 Add SSL_OP_NO_TLSv1_1 flag.
2461 Add TLSv1_1 methods.
2462 Update version checking logic to handle version 1.1.
2463 Add explicit IV handling (ported from DTLS code).
2464 Add command line options to s_client/s_server.
2467 Changes between 1.0.0g and 1.0.0h [12 Mar 2012]
2469 *) Fix MMA (Bleichenbacher's attack on PKCS #1 v1.5 RSA padding) weakness
2470 in CMS and PKCS7 code. When RSA decryption fails use a random key for
2471 content decryption and always return the same error. Note: this attack
2472 needs on average 2^20 messages so it only affects automated senders. The
2473 old behaviour can be reenabled in the CMS code by setting the
2474 CMS_DEBUG_DECRYPT flag: this is useful for debugging and testing where
2475 an MMA defence is not necessary.
2476 Thanks to Ivan Nestlerode <inestlerode@us.ibm.com> for discovering
2477 this issue. (CVE-2012-0884)
2480 *) Fix CVE-2011-4619: make sure we really are receiving a
2481 client hello before rejecting multiple SGC restarts. Thanks to
2482 Ivan Nestlerode <inestlerode@us.ibm.com> for discovering this bug.
2485 Changes between 1.0.0f and 1.0.0g [18 Jan 2012]
2487 *) Fix for DTLS DoS issue introduced by fix for CVE-2011-4109.
2488 Thanks to Antonio Martin, Enterprise Secure Access Research and
2489 Development, Cisco Systems, Inc. for discovering this bug and
2490 preparing a fix. (CVE-2012-0050)
2493 Changes between 1.0.0e and 1.0.0f [4 Jan 2012]
2495 *) Nadhem Alfardan and Kenny Paterson have discovered an extension
2496 of the Vaudenay padding oracle attack on CBC mode encryption
2497 which enables an efficient plaintext recovery attack against
2498 the OpenSSL implementation of DTLS. Their attack exploits timing
2499 differences arising during decryption processing. A research
2500 paper describing this attack can be found at:
2501 http://www.isg.rhul.ac.uk/~kp/dtls.pdf
2502 Thanks go to Nadhem Alfardan and Kenny Paterson of the Information
2503 Security Group at Royal Holloway, University of London
2504 (www.isg.rhul.ac.uk) for discovering this flaw and to Robin Seggelmann
2505 <seggelmann@fh-muenster.de> and Michael Tuexen <tuexen@fh-muenster.de>
2506 for preparing the fix. (CVE-2011-4108)
2507 [Robin Seggelmann, Michael Tuexen]
2509 *) Clear bytes used for block padding of SSL 3.0 records.
2511 [Adam Langley (Google)]
2513 *) Only allow one SGC handshake restart for SSL/TLS. Thanks to George
2514 Kadianakis <desnacked@gmail.com> for discovering this issue and
2515 Adam Langley for preparing the fix. (CVE-2011-4619)
2516 [Adam Langley (Google)]
2518 *) Check parameters are not NULL in GOST ENGINE. (CVE-2012-0027)
2519 [Andrey Kulikov <amdeich@gmail.com>]
2521 *) Prevent malformed RFC3779 data triggering an assertion failure.
2522 Thanks to Andrew Chi, BBN Technologies, for discovering the flaw
2523 and Rob Austein <sra@hactrn.net> for fixing it. (CVE-2011-4577)
2524 [Rob Austein <sra@hactrn.net>]
2526 *) Improved PRNG seeding for VOS.
2527 [Paul Green <Paul.Green@stratus.com>]
2529 *) Fix ssl_ciph.c set-up race.
2530 [Adam Langley (Google)]
2532 *) Fix spurious failures in ecdsatest.c.
2533 [Emilia Käsper (Google)]
2535 *) Fix the BIO_f_buffer() implementation (which was mixing different
2536 interpretations of the '..._len' fields).
2537 [Adam Langley (Google)]
2539 *) Fix handling of BN_BLINDING: now BN_BLINDING_invert_ex (rather than
2540 BN_BLINDING_invert_ex) calls BN_BLINDING_update, ensuring that concurrent
2541 threads won't reuse the same blinding coefficients.
2543 This also avoids the need to obtain the CRYPTO_LOCK_RSA_BLINDING
2544 lock to call BN_BLINDING_invert_ex, and avoids one use of
2545 BN_BLINDING_update for each BN_BLINDING structure (previously,
2546 the last update always remained unused).
2547 [Emilia Käsper (Google)]
2549 *) In ssl3_clear, preserve s3->init_extra along with s3->rbuf.
2550 [Bob Buckholz (Google)]
2552 Changes between 1.0.0d and 1.0.0e [6 Sep 2011]
2554 *) Fix bug where CRLs with nextUpdate in the past are sometimes accepted
2555 by initialising X509_STORE_CTX properly. (CVE-2011-3207)
2556 [Kaspar Brand <ossl@velox.ch>]
2558 *) Fix SSL memory handling for (EC)DH ciphersuites, in particular
2559 for multi-threaded use of ECDH. (CVE-2011-3210)
2560 [Adam Langley (Google)]
2562 *) Fix x509_name_ex_d2i memory leak on bad inputs.
2565 *) Remove hard coded ecdsaWithSHA1 signature tests in ssl code and check
2566 signature public key algorithm by using OID xref utilities instead.
2567 Before this you could only use some ECC ciphersuites with SHA1 only.
2570 *) Add protection against ECDSA timing attacks as mentioned in the paper
2571 by Billy Bob Brumley and Nicola Tuveri, see:
2573 http://eprint.iacr.org/2011/232.pdf
2575 [Billy Bob Brumley and Nicola Tuveri]
2577 Changes between 1.0.0c and 1.0.0d [8 Feb 2011]
2579 *) Fix parsing of OCSP stapling ClientHello extension. CVE-2011-0014
2580 [Neel Mehta, Adam Langley, Bodo Moeller (Google)]
2582 *) Fix bug in string printing code: if *any* escaping is enabled we must
2583 escape the escape character (backslash) or the resulting string is
2587 Changes between 1.0.0b and 1.0.0c [2 Dec 2010]
2589 *) Disable code workaround for ancient and obsolete Netscape browsers
2590 and servers: an attacker can use it in a ciphersuite downgrade attack.
2591 Thanks to Martin Rex for discovering this bug. CVE-2010-4180
2594 *) Fixed J-PAKE implementation error, originally discovered by
2595 Sebastien Martini, further info and confirmation from Stefan
2596 Arentz and Feng Hao. Note that this fix is a security fix. CVE-2010-4252
2599 Changes between 1.0.0a and 1.0.0b [16 Nov 2010]
2601 *) Fix extension code to avoid race conditions which can result in a buffer
2602 overrun vulnerability: resumed sessions must not be modified as they can
2603 be shared by multiple threads. CVE-2010-3864
2606 *) Fix WIN32 build system to correctly link an ENGINE directory into
2610 Changes between 1.0.0 and 1.0.0a [01 Jun 2010]
2612 *) Check return value of int_rsa_verify in pkey_rsa_verifyrecover
2614 [Steve Henson, Peter-Michael Hager <hager@dortmund.net>]
2616 Changes between 0.9.8n and 1.0.0 [29 Mar 2010]
2618 *) Add "missing" function EVP_CIPHER_CTX_copy(). This copies a cipher
2619 context. The operation can be customised via the ctrl mechanism in
2620 case ENGINEs want to include additional functionality.
2623 *) Tolerate yet another broken PKCS#8 key format: private key value negative.
2626 *) Add new -subject_hash_old and -issuer_hash_old options to x509 utility to
2627 output hashes compatible with older versions of OpenSSL.
2628 [Willy Weisz <weisz@vcpc.univie.ac.at>]
2630 *) Fix compression algorithm handling: if resuming a session use the
2631 compression algorithm of the resumed session instead of determining
2632 it from client hello again. Don't allow server to change algorithm.
2635 *) Add load_crls() function to apps tidying load_certs() too. Add option
2636 to verify utility to allow additional CRLs to be included.
2639 *) Update OCSP request code to permit adding custom headers to the request:
2640 some responders need this.
2643 *) The function EVP_PKEY_sign() returns <=0 on error: check return code
2645 [Julia Lawall <julia@diku.dk>]
2647 *) Update verify callback code in apps/s_cb.c and apps/verify.c, it
2648 needlessly dereferenced structures, used obsolete functions and
2649 didn't handle all updated verify codes correctly.
2652 *) Disable MD2 in the default configuration.
2655 *) In BIO_pop() and BIO_push() use the ctrl argument (which was NULL) to
2656 indicate the initial BIO being pushed or popped. This makes it possible
2657 to determine whether the BIO is the one explicitly called or as a result
2658 of the ctrl being passed down the chain. Fix BIO_pop() and SSL BIOs so
2659 it handles reference counts correctly and doesn't zero out the I/O bio
2660 when it is not being explicitly popped. WARNING: applications which
2661 included workarounds for the old buggy behaviour will need to be modified
2662 or they could free up already freed BIOs.
2665 *) Extend the uni2asc/asc2uni => OPENSSL_uni2asc/OPENSSL_asc2uni
2666 renaming to all platforms (within the 0.9.8 branch, this was
2667 done conditionally on Netware platforms to avoid a name clash).
2668 [Guenter <lists@gknw.net>]
2670 *) Add ECDHE and PSK support to DTLS.
2671 [Michael Tuexen <tuexen@fh-muenster.de>]
2673 *) Add CHECKED_STACK_OF macro to safestack.h, otherwise safestack can't
2677 *) Add "missing" function EVP_MD_flags() (without this the only way to
2678 retrieve a digest flags is by accessing the structure directly. Update
2679 EVP_MD_do_all*() and EVP_CIPHER_do_all*() to include the name a digest
2680 or cipher is registered as in the "from" argument. Print out all
2681 registered digests in the dgst usage message instead of manually
2682 attempting to work them out.
2685 *) If no SSLv2 ciphers are used don't use an SSLv2 compatible client hello:
2686 this allows the use of compression and extensions. Change default cipher
2687 string to remove SSLv2 ciphersuites. This effectively avoids ancient SSLv2
2688 by default unless an application cipher string requests it.
2691 *) Alter match criteria in PKCS12_parse(). It used to try to use local
2692 key ids to find matching certificates and keys but some PKCS#12 files
2693 don't follow the (somewhat unwritten) rules and this strategy fails.
2694 Now just gather all certificates together and the first private key
2695 then look for the first certificate that matches the key.
2698 *) Support use of registered digest and cipher names for dgst and cipher
2699 commands instead of having to add each one as a special case. So now
2706 openssl dgst -sha256 foo
2708 and this works for ENGINE based algorithms too.
2712 *) Update Gost ENGINE to support parameter files.
2713 [Victor B. Wagner <vitus@cryptocom.ru>]
2715 *) Support GeneralizedTime in ca utility.
2716 [Oliver Martin <oliver@volatilevoid.net>, Steve Henson]
2718 *) Enhance the hash format used for certificate directory links. The new
2719 form uses the canonical encoding (meaning equivalent names will work
2720 even if they aren't identical) and uses SHA1 instead of MD5. This form
2721 is incompatible with the older format and as a result c_rehash should
2722 be used to rebuild symbolic links.
2725 *) Make PKCS#8 the default write format for private keys, replacing the
2726 traditional format. This form is standardised, more secure and doesn't
2727 include an implicit MD5 dependency.
2730 *) Add a $gcc_devteam_warn option to Configure. The idea is that any code
2731 committed to OpenSSL should pass this lot as a minimum.
2734 *) Add session ticket override functionality for use by EAP-FAST.
2735 [Jouni Malinen <j@w1.fi>]
2737 *) Modify HMAC functions to return a value. Since these can be implemented
2738 in an ENGINE errors can occur.
2741 *) Type-checked OBJ_bsearch_ex.
2744 *) Type-checked OBJ_bsearch. Also some constification necessitated
2745 by type-checking. Still to come: TXT_DB, bsearch(?),
2746 OBJ_bsearch_ex, qsort, CRYPTO_EX_DATA, ASN1_VALUE, ASN1_STRING,
2750 *) New function OPENSSL_gmtime_adj() to add a specific number of days and
2751 seconds to a tm structure directly, instead of going through OS
2752 specific date routines. This avoids any issues with OS routines such
2753 as the year 2038 bug. New *_adj() functions for ASN1 time structures
2754 and X509_time_adj_ex() to cover the extended range. The existing
2755 X509_time_adj() is still usable and will no longer have any date issues.
2758 *) Delta CRL support. New use deltas option which will attempt to locate
2759 and search any appropriate delta CRLs available.
2761 This work was sponsored by Google.
2764 *) Support for CRLs partitioned by reason code. Reorganise CRL processing
2765 code and add additional score elements. Validate alternate CRL paths
2766 as part of the CRL checking and indicate a new error "CRL path validation
2767 error" in this case. Applications wanting additional details can use
2768 the verify callback and check the new "parent" field. If this is not
2769 NULL CRL path validation is taking place. Existing applications wont
2770 see this because it requires extended CRL support which is off by
2773 This work was sponsored by Google.
2776 *) Support for freshest CRL extension.
2778 This work was sponsored by Google.
2781 *) Initial indirect CRL support. Currently only supported in the CRLs
2782 passed directly and not via lookup. Process certificate issuer
2783 CRL entry extension and lookup CRL entries by bother issuer name
2784 and serial number. Check and process CRL issuer entry in IDP extension.
2786 This work was sponsored by Google.
2789 *) Add support for distinct certificate and CRL paths. The CRL issuer
2790 certificate is validated separately in this case. Only enabled if
2791 an extended CRL support flag is set: this flag will enable additional
2792 CRL functionality in future.
2794 This work was sponsored by Google.
2797 *) Add support for policy mappings extension.
2799 This work was sponsored by Google.
2802 *) Fixes to pathlength constraint, self issued certificate handling,
2803 policy processing to align with RFC3280 and PKITS tests.
2805 This work was sponsored by Google.
2808 *) Support for name constraints certificate extension. DN, email, DNS
2809 and URI types are currently supported.
2811 This work was sponsored by Google.
2814 *) To cater for systems that provide a pointer-based thread ID rather
2815 than numeric, deprecate the current numeric thread ID mechanism and
2816 replace it with a structure and associated callback type. This
2817 mechanism allows a numeric "hash" to be extracted from a thread ID in
2818 either case, and on platforms where pointers are larger than 'long',
2819 mixing is done to help ensure the numeric 'hash' is usable even if it
2820 can't be guaranteed unique. The default mechanism is to use "&errno"
2821 as a pointer-based thread ID to distinguish between threads.
2823 Applications that want to provide their own thread IDs should now use
2824 CRYPTO_THREADID_set_callback() to register a callback that will call
2825 either CRYPTO_THREADID_set_numeric() or CRYPTO_THREADID_set_pointer().
2827 Note that ERR_remove_state() is now deprecated, because it is tied
2828 to the assumption that thread IDs are numeric. ERR_remove_state(0)
2829 to free the current thread's error state should be replaced by
2830 ERR_remove_thread_state(NULL).
2832 (This new approach replaces the functions CRYPTO_set_idptr_callback(),
2833 CRYPTO_get_idptr_callback(), and CRYPTO_thread_idptr() that existed in
2834 OpenSSL 0.9.9-dev between June 2006 and August 2008. Also, if an
2835 application was previously providing a numeric thread callback that
2836 was inappropriate for distinguishing threads, then uniqueness might
2837 have been obtained with &errno that happened immediately in the
2838 intermediate development versions of OpenSSL; this is no longer the
2839 case, the numeric thread callback will now override the automatic use
2841 [Geoff Thorpe, with help from Bodo Moeller]
2843 *) Initial support for different CRL issuing certificates. This covers a
2844 simple case where the self issued certificates in the chain exist and
2845 the real CRL issuer is higher in the existing chain.
2847 This work was sponsored by Google.
2850 *) Removed effectively defunct crypto/store from the build.
2853 *) Revamp of STACK to provide stronger type-checking. Still to come:
2854 TXT_DB, bsearch(?), OBJ_bsearch, qsort, CRYPTO_EX_DATA, ASN1_VALUE,
2855 ASN1_STRING, CONF_VALUE.
2858 *) Add a new SSL_MODE_RELEASE_BUFFERS mode flag to release unused buffer
2859 RAM on SSL connections. This option can save about 34k per idle SSL.
2862 *) Revamp of LHASH to provide stronger type-checking. Still to come:
2863 STACK, TXT_DB, bsearch, qsort.
2866 *) Initial support for Cryptographic Message Syntax (aka CMS) based
2867 on RFC3850, RFC3851 and RFC3852. New cms directory and cms utility,
2868 support for data, signedData, compressedData, digestedData and
2869 encryptedData, envelopedData types included. Scripts to check against
2870 RFC4134 examples draft and interop and consistency checks of many
2871 content types and variants.
2874 *) Add options to enc utility to support use of zlib compression BIO.
2877 *) Extend mk1mf to support importing of options and assembly language
2878 files from Configure script, currently only included in VC-WIN32.
2879 The assembly language rules can now optionally generate the source
2880 files from the associated perl scripts.
2883 *) Implement remaining functionality needed to support GOST ciphersuites.
2884 Interop testing has been performed using CryptoPro implementations.
2885 [Victor B. Wagner <vitus@cryptocom.ru>]
2887 *) s390x assembler pack.
2890 *) ARMv4 assembler pack. ARMv4 refers to v4 and later ISA, not CPU
2894 *) Implement Opaque PRF Input TLS extension as specified in
2895 draft-rescorla-tls-opaque-prf-input-00.txt. Since this is not an
2896 official specification yet and no extension type assignment by
2897 IANA exists, this extension (for now) will have to be explicitly
2898 enabled when building OpenSSL by providing the extension number
2899 to use. For example, specify an option
2901 -DTLSEXT_TYPE_opaque_prf_input=0x9527
2903 to the "config" or "Configure" script to enable the extension,
2904 assuming extension number 0x9527 (which is a completely arbitrary
2905 and unofficial assignment based on the MD5 hash of the Internet
2906 Draft). Note that by doing so, you potentially lose
2907 interoperability with other TLS implementations since these might
2908 be using the same extension number for other purposes.
2910 SSL_set_tlsext_opaque_prf_input(ssl, src, len) is used to set the
2911 opaque PRF input value to use in the handshake. This will create
2912 an interal copy of the length-'len' string at 'src', and will
2913 return non-zero for success.
2915 To get more control and flexibility, provide a callback function
2918 SSL_CTX_set_tlsext_opaque_prf_input_callback(ctx, cb)
2919 SSL_CTX_set_tlsext_opaque_prf_input_callback_arg(ctx, arg)
2923 int (*cb)(SSL *, void *peerinput, size_t len, void *arg);
2926 Callback function 'cb' will be called in handshakes, and is
2927 expected to use SSL_set_tlsext_opaque_prf_input() as appropriate.
2928 Argument 'arg' is for application purposes (the value as given to
2929 SSL_CTX_set_tlsext_opaque_prf_input_callback_arg() will directly
2930 be provided to the callback function). The callback function
2931 has to return non-zero to report success: usually 1 to use opaque
2932 PRF input just if possible, or 2 to enforce use of the opaque PRF
2933 input. In the latter case, the library will abort the handshake
2934 if opaque PRF input is not successfully negotiated.
2936 Arguments 'peerinput' and 'len' given to the callback function
2937 will always be NULL and 0 in the case of a client. A server will
2938 see the client's opaque PRF input through these variables if
2939 available (NULL and 0 otherwise). Note that if the server
2940 provides an opaque PRF input, the length must be the same as the
2941 length of the client's opaque PRF input.
2943 Note that the callback function will only be called when creating
2944 a new session (session resumption can resume whatever was
2945 previously negotiated), and will not be called in SSL 2.0
2946 handshakes; thus, SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv2) or
2947 SSL_set_options(ssl, SSL_OP_NO_SSLv2) is especially recommended
2948 for applications that need to enforce opaque PRF input.
2952 *) Update ssl code to support digests other than SHA1+MD5 for handshake
2955 [Victor B. Wagner <vitus@cryptocom.ru>]
2957 *) Add RFC4507 support to OpenSSL. This includes the corrections in
2958 RFC4507bis. The encrypted ticket format is an encrypted encoded
2959 SSL_SESSION structure, that way new session features are automatically
2962 If a client application caches session in an SSL_SESSION structure
2963 support is transparent because tickets are now stored in the encoded
2966 The SSL_CTX structure automatically generates keys for ticket
2967 protection in servers so again support should be possible
2968 with no application modification.
2970 If a client or server wishes to disable RFC4507 support then the option
2971 SSL_OP_NO_TICKET can be set.
2973 Add a TLS extension debugging callback to allow the contents of any client
2974 or server extensions to be examined.
2976 This work was sponsored by Google.
2979 *) Final changes to avoid use of pointer pointer casts in OpenSSL.
2980 OpenSSL should now compile cleanly on gcc 4.2
2981 [Peter Hartley <pdh@utter.chaos.org.uk>, Steve Henson]
2983 *) Update SSL library to use new EVP_PKEY MAC API. Include generic MAC
2984 support including streaming MAC support: this is required for GOST
2985 ciphersuite support.
2986 [Victor B. Wagner <vitus@cryptocom.ru>, Steve Henson]
2988 *) Add option -stream to use PKCS#7 streaming in smime utility. New
2989 function i2d_PKCS7_bio_stream() and PEM_write_PKCS7_bio_stream()
2990 to output in BER and PEM format.
2993 *) Experimental support for use of HMAC via EVP_PKEY interface. This
2994 allows HMAC to be handled via the EVP_DigestSign*() interface. The
2995 EVP_PKEY "key" in this case is the HMAC key, potentially allowing
2996 ENGINE support for HMAC keys which are unextractable. New -mac and
2997 -macopt options to dgst utility.
3000 *) New option -sigopt to dgst utility. Update dgst to use
3001 EVP_Digest{Sign,Verify}*. These two changes make it possible to use
3002 alternative signing parameters such as X9.31 or PSS in the dgst
3006 *) Change ssl_cipher_apply_rule(), the internal function that does
3007 the work each time a ciphersuite string requests enabling
3008 ("foo+bar"), moving ("+foo+bar"), disabling ("-foo+bar", or
3009 removing ("!foo+bar") a class of ciphersuites: Now it maintains
3010 the order of disabled ciphersuites such that those ciphersuites
3011 that most recently went from enabled to disabled not only stay
3012 in order with respect to each other, but also have higher priority
3013 than other disabled ciphersuites the next time ciphersuites are
3016 This means that you can now say, e.g., "PSK:-PSK:HIGH" to enable
3017 the same ciphersuites as with "HIGH" alone, but in a specific
3018 order where the PSK ciphersuites come first (since they are the
3019 most recently disabled ciphersuites when "HIGH" is parsed).
3021 Also, change ssl_create_cipher_list() (using this new
3022 funcionality) such that between otherwise identical
3023 cihpersuites, ephemeral ECDH is preferred over ephemeral DH in
3027 *) Change ssl_create_cipher_list() so that it automatically
3028 arranges the ciphersuites in reasonable order before starting
3029 to process the rule string. Thus, the definition for "DEFAULT"
3030 (SSL_DEFAULT_CIPHER_LIST) now is just "ALL:!aNULL:!eNULL", but
3031 remains equivalent to "AES:ALL:!aNULL:!eNULL:+aECDH:+kRSA:+RC4:@STRENGTH".
3032 This makes it much easier to arrive at a reasonable default order
3033 in applications for which anonymous ciphers are OK (meaning
3034 that you can't actually use DEFAULT).
3035 [Bodo Moeller; suggested by Victor Duchovni]
3037 *) Split the SSL/TLS algorithm mask (as used for ciphersuite string
3038 processing) into multiple integers instead of setting
3039 "SSL_MKEY_MASK" bits, "SSL_AUTH_MASK" bits, "SSL_ENC_MASK",
3040 "SSL_MAC_MASK", and "SSL_SSL_MASK" bits all in a single integer.
3041 (These masks as well as the individual bit definitions are hidden
3042 away into the non-exported interface ssl/ssl_locl.h, so this
3043 change to the definition of the SSL_CIPHER structure shouldn't
3044 affect applications.) This give us more bits for each of these
3045 categories, so there is no longer a need to coagulate AES128 and
3046 AES256 into a single algorithm bit, and to coagulate Camellia128
3047 and Camellia256 into a single algorithm bit, which has led to all
3050 Thus, among other things, the kludge introduced in 0.9.7m and
3051 0.9.8e for masking out AES256 independently of AES128 or masking
3052 out Camellia256 independently of AES256 is not needed here in 0.9.9.
3054 With the change, we also introduce new ciphersuite aliases that
3055 so far were missing: "AES128", "AES256", "CAMELLIA128", and
3059 *) Add support for dsa-with-SHA224 and dsa-with-SHA256.
3060 Use the leftmost N bytes of the signature input if the input is
3061 larger than the prime q (with N being the size in bytes of q).
3064 *) Very *very* experimental PKCS#7 streaming encoder support. Nothing uses
3065 it yet and it is largely untested.
3068 *) Add support for the ecdsa-with-SHA224/256/384/512 signature types.
3071 *) Initial incomplete changes to avoid need for function casts in OpenSSL
3072 some compilers (gcc 4.2 and later) reject their use. Safestack is
3073 reimplemented. Update ASN1 to avoid use of legacy functions.
3076 *) Win32/64 targets are linked with Winsock2.
3079 *) Add an X509_CRL_METHOD structure to allow CRL processing to be redirected
3080 to external functions. This can be used to increase CRL handling
3081 efficiency especially when CRLs are very large by (for example) storing
3082 the CRL revoked certificates in a database.
3085 *) Overhaul of by_dir code. Add support for dynamic loading of CRLs so
3086 new CRLs added to a directory can be used. New command line option
3087 -verify_return_error to s_client and s_server. This causes real errors
3088 to be returned by the verify callback instead of carrying on no matter
3089 what. This reflects the way a "real world" verify callback would behave.
3092 *) GOST engine, supporting several GOST algorithms and public key formats.
3093 Kindly donated by Cryptocom.
3096 *) Partial support for Issuing Distribution Point CRL extension. CRLs
3097 partitioned by DP are handled but no indirect CRL or reason partitioning
3098 (yet). Complete overhaul of CRL handling: now the most suitable CRL is
3099 selected via a scoring technique which handles IDP and AKID in CRLs.
3102 *) New X509_STORE_CTX callbacks lookup_crls() and lookup_certs() which
3103 will ultimately be used for all verify operations: this will remove the
3104 X509_STORE dependency on certificate verification and allow alternative
3105 lookup methods. X509_STORE based implementations of these two callbacks.
3108 *) Allow multiple CRLs to exist in an X509_STORE with matching issuer names.
3109 Modify get_crl() to find a valid (unexpired) CRL if possible.
3112 *) New function X509_CRL_match() to check if two CRLs are identical. Normally
3113 this would be called X509_CRL_cmp() but that name is already used by
3114 a function that just compares CRL issuer names. Cache several CRL
3115 extensions in X509_CRL structure and cache CRLDP in X509.
3118 *) Store a "canonical" representation of X509_NAME structure (ASN1 Name)
3119 this maps equivalent X509_NAME structures into a consistent structure.
3120 Name comparison can then be performed rapidly using memcmp().
3123 *) Non-blocking OCSP request processing. Add -timeout option to ocsp
3127 *) Allow digests to supply their own micalg string for S/MIME type using
3128 the ctrl EVP_MD_CTRL_MICALG.
3131 *) During PKCS7 signing pass the PKCS7 SignerInfo structure to the
3132 EVP_PKEY_METHOD before and after signing via the EVP_PKEY_CTRL_PKCS7_SIGN
3133 ctrl. It can then customise the structure before and/or after signing
3137 *) New function OBJ_add_sigid() to allow application defined signature OIDs
3138 to be added to OpenSSLs internal tables. New function OBJ_sigid_free()
3139 to free up any added signature OIDs.
3142 *) New functions EVP_CIPHER_do_all(), EVP_CIPHER_do_all_sorted(),
3143 EVP_MD_do_all() and EVP_MD_do_all_sorted() to enumerate internal
3144 digest and cipher tables. New options added to openssl utility:
3145 list-message-digest-algorithms and list-cipher-algorithms.
3148 *) Change the array representation of binary polynomials: the list
3149 of degrees of non-zero coefficients is now terminated with -1.
3150 Previously it was terminated with 0, which was also part of the
3151 value; thus, the array representation was not applicable to
3152 polynomials where t^0 has coefficient zero. This change makes
3153 the array representation useful in a more general context.
3156 *) Various modifications and fixes to SSL/TLS cipher string
3157 handling. For ECC, the code now distinguishes between fixed ECDH
3158 with RSA certificates on the one hand and with ECDSA certificates
3159 on the other hand, since these are separate ciphersuites. The
3160 unused code for Fortezza ciphersuites has been removed.
3162 For consistency with EDH, ephemeral ECDH is now called "EECDH"
3163 (not "ECDHE"). For consistency with the code for DH
3164 certificates, use of ECDH certificates is now considered ECDH
3165 authentication, not RSA or ECDSA authentication (the latter is
3166 merely the CA's signing algorithm and not actively used in the
3169 The temporary ciphersuite alias "ECCdraft" is no longer
3170 available, and ECC ciphersuites are no longer excluded from "ALL"
3171 and "DEFAULT". The following aliases now exist for RFC 4492
3172 ciphersuites, most of these by analogy with the DH case:
3174 kECDHr - ECDH cert, signed with RSA
3175 kECDHe - ECDH cert, signed with ECDSA
3176 kECDH - ECDH cert (signed with either RSA or ECDSA)
3177 kEECDH - ephemeral ECDH
3178 ECDH - ECDH cert or ephemeral ECDH
3184 AECDH - anonymous ECDH
3185 EECDH - non-anonymous ephemeral ECDH (equivalent to "kEECDH:-AECDH")
3189 *) Add additional S/MIME capabilities for AES and GOST ciphers if supported.
3190 Use correct micalg parameters depending on digest(s) in signed message.
3193 *) Add engine support for EVP_PKEY_ASN1_METHOD. Add functions to process
3194 an ENGINE asn1 method. Support ENGINE lookups in the ASN1 code.
3197 *) Initial engine support for EVP_PKEY_METHOD. New functions to permit
3198 an engine to register a method. Add ENGINE lookups for methods and
3199 functional reference processing.
3202 *) New functions EVP_Digest{Sign,Verify)*. These are enchance versions of
3203 EVP_{Sign,Verify}* which allow an application to customise the signature
3207 *) New -resign option to smime utility. This adds one or more signers
3208 to an existing PKCS#7 signedData structure. Also -md option to use an
3209 alternative message digest algorithm for signing.
3212 *) Tidy up PKCS#7 routines and add new functions to make it easier to
3213 create PKCS7 structures containing multiple signers. Update smime
3214 application to support multiple signers.
3217 *) New -macalg option to pkcs12 utility to allow setting of an alternative
3221 *) Initial support for PKCS#5 v2.0 PRFs other than default SHA1 HMAC.
3222 Reorganize PBE internals to lookup from a static table using NIDs,
3223 add support for HMAC PBE OID translation. Add a EVP_CIPHER ctrl:
3224 EVP_CTRL_PBE_PRF_NID this allows a cipher to specify an alternative
3225 PRF which will be automatically used with PBES2.
3228 *) Replace the algorithm specific calls to generate keys in "req" with the
3232 *) Update PKCS#7 enveloped data routines to use new API. This is now
3233 supported by any public key method supporting the encrypt operation. A
3234 ctrl is added to allow the public key algorithm to examine or modify
3235 the PKCS#7 RecipientInfo structure if it needs to: for RSA this is
3239 *) Add a ctrl to asn1 method to allow a public key algorithm to express
3240 a default digest type to use. In most cases this will be SHA1 but some
3241 algorithms (such as GOST) need to specify an alternative digest. The
3242 return value indicates how strong the preference is 1 means optional and
3243 2 is mandatory (that is it is the only supported type). Modify
3244 ASN1_item_sign() to accept a NULL digest argument to indicate it should
3245 use the default md. Update openssl utilities to use the default digest
3246 type for signing if it is not explicitly indicated.
3249 *) Use OID cross reference table in ASN1_sign() and ASN1_verify(). New
3250 EVP_MD flag EVP_MD_FLAG_PKEY_METHOD_SIGNATURE. This uses the relevant
3251 signing method from the key type. This effectively removes the link
3252 between digests and public key types.
3255 *) Add an OID cross reference table and utility functions. Its purpose is to
3256 translate between signature OIDs such as SHA1WithrsaEncryption and SHA1,
3257 rsaEncryption. This will allow some of the algorithm specific hackery
3258 needed to use the correct OID to be removed.
3261 *) Remove algorithm specific dependencies when setting PKCS7_SIGNER_INFO
3262 structures for PKCS7_sign(). They are now set up by the relevant public
3266 *) Add provisional EC pkey method with support for ECDSA and ECDH.
3269 *) Add support for key derivation (agreement) in the API, DH method and
3273 *) Add DSA pkey method and DH pkey methods, extend DH ASN1 method to support
3274 public and private key formats. As a side effect these add additional
3275 command line functionality not previously available: DSA signatures can be
3276 generated and verified using pkeyutl and DH key support and generation in
3281 [Oliver Tappe <zooey@hirschkaefer.de>]
3283 *) New make target "install_html_docs" installs HTML renditions of the
3285 [Oliver Tappe <zooey@hirschkaefer.de>]
3287 *) New utility "genpkey" this is analogous to "genrsa" etc except it can
3288 generate keys for any algorithm. Extend and update EVP_PKEY_METHOD to
3289 support key and parameter generation and add initial key generation
3290 functionality for RSA.
3293 *) Add functions for main EVP_PKEY_method operations. The undocumented
3294 functions EVP_PKEY_{encrypt,decrypt} have been renamed to
3295 EVP_PKEY_{encrypt,decrypt}_old.
3298 *) Initial definitions for EVP_PKEY_METHOD. This will be a high level public
3299 key API, doesn't do much yet.
3302 *) New function EVP_PKEY_asn1_get0_info() to retrieve information about
3303 public key algorithms. New option to openssl utility:
3304 "list-public-key-algorithms" to print out info.
3307 *) Implement the Supported Elliptic Curves Extension for
3308 ECC ciphersuites from draft-ietf-tls-ecc-12.txt.
3311 *) Don't free up OIDs in OBJ_cleanup() if they are in use by EVP_MD or
3312 EVP_CIPHER structures to avoid later problems in EVP_cleanup().
3315 *) New utilities pkey and pkeyparam. These are similar to algorithm specific
3316 utilities such as rsa, dsa, dsaparam etc except they process any key
3320 *) Transfer public key printing routines to EVP_PKEY_ASN1_METHOD. New
3321 functions EVP_PKEY_print_public(), EVP_PKEY_print_private(),
3322 EVP_PKEY_print_param() to print public key data from an EVP_PKEY
3326 *) Initial support for pluggable public key ASN1.
3327 De-spaghettify the public key ASN1 handling. Move public and private
3328 key ASN1 handling to a new EVP_PKEY_ASN1_METHOD structure. Relocate
3329 algorithm specific handling to a single module within the relevant
3330 algorithm directory. Add functions to allow (near) opaque processing
3331 of public and private key structures.
3334 *) Implement the Supported Point Formats Extension for
3335 ECC ciphersuites from draft-ietf-tls-ecc-12.txt.
3338 *) Add initial support for RFC 4279 PSK TLS ciphersuites. Add members
3339 for the psk identity [hint] and the psk callback functions to the
3340 SSL_SESSION, SSL and SSL_CTX structure.
3343 PSK-RC4-SHA, PSK-3DES-EDE-CBC-SHA, PSK-AES128-CBC-SHA,
3347 SSL_CTX_use_psk_identity_hint
3348 SSL_get_psk_identity_hint
3349 SSL_get_psk_identity
3350 SSL_use_psk_identity_hint
3352 [Mika Kousa and Pasi Eronen of Nokia Corporation]
3354 *) Add RFC 3161 compliant time stamp request creation, response generation
3355 and response verification functionality.
3356 [Zoltán Glózik <zglozik@opentsa.org>, The OpenTSA Project]
3358 *) Add initial support for TLS extensions, specifically for the server_name
3359 extension so far. The SSL_SESSION, SSL_CTX, and SSL data structures now
3360 have new members for a host name. The SSL data structure has an
3361 additional member SSL_CTX *initial_ctx so that new sessions can be
3362 stored in that context to allow for session resumption, even after the
3363 SSL has been switched to a new SSL_CTX in reaction to a client's
3364 server_name extension.
3366 New functions (subject to change):
3368 SSL_get_servername()
3369 SSL_get_servername_type()
3372 New CTRL codes and macros (subject to change):
3374 SSL_CTRL_SET_TLSEXT_SERVERNAME_CB
3375 - SSL_CTX_set_tlsext_servername_callback()
3376 SSL_CTRL_SET_TLSEXT_SERVERNAME_ARG
3377 - SSL_CTX_set_tlsext_servername_arg()
3378 SSL_CTRL_SET_TLSEXT_HOSTNAME - SSL_set_tlsext_host_name()
3380 openssl s_client has a new '-servername ...' option.
3382 openssl s_server has new options '-servername_host ...', '-cert2 ...',
3383 '-key2 ...', '-servername_fatal' (subject to change). This allows
3384 testing the HostName extension for a specific single host name ('-cert'
3385 and '-key' remain fallbacks for handshakes without HostName
3386 negotiation). If the unrecognized_name alert has to be sent, this by
3387 default is a warning; it becomes fatal with the '-servername_fatal'
3390 [Peter Sylvester, Remy Allais, Christophe Renou]
3392 *) Whirlpool hash implementation is added.
3395 *) BIGNUM code on 64-bit SPARCv9 targets is switched from bn(64,64) to
3396 bn(64,32). Because of instruction set limitations it doesn't have
3397 any negative impact on performance. This was done mostly in order
3398 to make it possible to share assembler modules, such as bn_mul_mont
3399 implementations, between 32- and 64-bit builds without hassle.
3402 *) Move code previously exiled into file crypto/ec/ec2_smpt.c
3403 to ec2_smpl.c, and no longer require the OPENSSL_EC_BIN_PT_COMP
3407 *) New candidate for BIGNUM assembler implementation, bn_mul_mont,
3408 dedicated Montgomery multiplication procedure, is introduced.
3409 BN_MONT_CTX is modified to allow bn_mul_mont to reach for higher
3410 "64-bit" performance on certain 32-bit targets.
3413 *) New option SSL_OP_NO_COMP to disable use of compression selectively
3414 in SSL structures. New SSL ctrl to set maximum send fragment size.
3415 Save memory by seeting the I/O buffer sizes dynamically instead of
3416 using the maximum available value.
3419 *) New option -V for 'openssl ciphers'. This prints the ciphersuite code
3420 in addition to the text details.
3423 *) Very, very preliminary EXPERIMENTAL support for printing of general
3424 ASN1 structures. This currently produces rather ugly output and doesn't
3425 handle several customised structures at all.
3428 *) Integrated support for PVK file format and some related formats such
3429 as MS PUBLICKEYBLOB and PRIVATEKEYBLOB. Command line switches to support
3430 these in the 'rsa' and 'dsa' utilities.
3433 *) Support for PKCS#1 RSAPublicKey format on rsa utility command line.
3436 *) Remove the ancient ASN1_METHOD code. This was only ever used in one
3437 place for the (very old) "NETSCAPE" format certificates which are now
3438 handled using new ASN1 code equivalents.
3441 *) Let the TLSv1_method() etc. functions return a 'const' SSL_METHOD
3442 pointer and make the SSL_METHOD parameter in SSL_CTX_new,
3443 SSL_CTX_set_ssl_version and SSL_set_ssl_method 'const'.
3446 *) Modify CRL distribution points extension code to print out previously
3447 unsupported fields. Enhance extension setting code to allow setting of
3451 *) Add print and set support for Issuing Distribution Point CRL extension.
3454 *) Change 'Configure' script to enable Camellia by default.
3457 Changes between 0.9.8m and 0.9.8n [24 Mar 2010]
3459 *) When rejecting SSL/TLS records due to an incorrect version number, never
3460 update s->server with a new major version number. As of
3461 - OpenSSL 0.9.8m if 'short' is a 16-bit type,
3462 - OpenSSL 0.9.8f if 'short' is longer than 16 bits,
3463 the previous behavior could result in a read attempt at NULL when
3464 receiving specific incorrect SSL/TLS records once record payload
3465 protection is active. (CVE-2010-0740)
3466 [Bodo Moeller, Adam Langley <agl@chromium.org>]
3468 *) Fix for CVE-2010-0433 where some kerberos enabled versions of OpenSSL
3469 could be crashed if the relevant tables were not present (e.g. chrooted).
3470 [Tomas Hoger <thoger@redhat.com>]
3472 Changes between 0.9.8l and 0.9.8m [25 Feb 2010]
3474 *) Always check bn_wexpend() return values for failure. (CVE-2009-3245)
3475 [Martin Olsson, Neel Mehta]
3477 *) Fix X509_STORE locking: Every 'objs' access requires a lock (to
3478 accommodate for stack sorting, always a write lock!).
3481 *) On some versions of WIN32 Heap32Next is very slow. This can cause
3482 excessive delays in the RAND_poll(): over a minute. As a workaround
3483 include a time check in the inner Heap32Next loop too.
3486 *) The code that handled flushing of data in SSL/TLS originally used the
3487 BIO_CTRL_INFO ctrl to see if any data was pending first. This caused
3488 the problem outlined in PR#1949. The fix suggested there however can
3489 trigger problems with buggy BIO_CTRL_WPENDING (e.g. some versions
3490 of Apache). So instead simplify the code to flush unconditionally.
3491 This should be fine since flushing with no data to flush is a no op.
3494 *) Handle TLS versions 2.0 and later properly and correctly use the
3495 highest version of TLS/SSL supported. Although TLS >= 2.0 is some way
3496 off ancient servers have a habit of sticking around for a while...
3499 *) Modify compression code so it frees up structures without using the
3500 ex_data callbacks. This works around a problem where some applications
3501 call CRYPTO_cleanup_all_ex_data() before application exit (e.g. when
3502 restarting) then use compression (e.g. SSL with compression) later.
3503 This results in significant per-connection memory leaks and
3504 has caused some security issues including CVE-2008-1678 and
3508 *) Constify crypto/cast (i.e., <openssl/cast.h>): a CAST_KEY doesn't
3509 change when encrypting or decrypting.
3512 *) Add option SSL_OP_LEGACY_SERVER_CONNECT which will allow clients to
3513 connect and renegotiate with servers which do not support RI.
3514 Until RI is more widely deployed this option is enabled by default.
3517 *) Add "missing" ssl ctrls to clear options and mode.
3520 *) If client attempts to renegotiate and doesn't support RI respond with
3521 a no_renegotiation alert as required by RFC5746. Some renegotiating
3522 TLS clients will continue a connection gracefully when they receive
3523 the alert. Unfortunately OpenSSL mishandled this alert and would hang
3524 waiting for a server hello which it will never receive. Now we treat a
3525 received no_renegotiation alert as a fatal error. This is because
3526 applications requesting a renegotiation might well expect it to succeed
3527 and would have no code in place to handle the server denying it so the
3528 only safe thing to do is to terminate the connection.
3531 *) Add ctrl macro SSL_get_secure_renegotiation_support() which returns 1 if
3532 peer supports secure renegotiation and 0 otherwise. Print out peer
3533 renegotiation support in s_client/s_server.
3536 *) Replace the highly broken and deprecated SPKAC certification method with
3537 the updated NID creation version. This should correctly handle UTF8.
3540 *) Implement RFC5746. Re-enable renegotiation but require the extension
3541 as needed. Unfortunately, SSL3_FLAGS_ALLOW_UNSAFE_LEGACY_RENEGOTIATION
3542 turns out to be a bad idea. It has been replaced by
3543 SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION which can be set with
3544 SSL_CTX_set_options(). This is really not recommended unless you
3545 know what you are doing.
3546 [Eric Rescorla <ekr@networkresonance.com>, Ben Laurie, Steve Henson]
3548 *) Fixes to stateless session resumption handling. Use initial_ctx when
3549 issuing and attempting to decrypt tickets in case it has changed during
3550 servername handling. Use a non-zero length session ID when attempting
3551 stateless session resumption: this makes it possible to determine if
3552 a resumption has occurred immediately after receiving server hello
3553 (several places in OpenSSL subtly assume this) instead of later in
3557 *) The functions ENGINE_ctrl(), OPENSSL_isservice(),
3558 CMS_get1_RecipientRequest() and RAND_bytes() can return <=0 on error
3559 fixes for a few places where the return code is not checked
3561 [Julia Lawall <julia@diku.dk>]
3563 *) Add --strict-warnings option to Configure script to include devteam
3564 warnings in other configurations.
3567 *) Add support for --libdir option and LIBDIR variable in makefiles. This
3568 makes it possible to install openssl libraries in locations which
3569 have names other than "lib", for example "/usr/lib64" which some
3571 [Steve Henson, based on patch from Jeremy Utley]
3573 *) Don't allow the use of leading 0x80 in OIDs. This is a violation of
3574 X690 8.9.12 and can produce some misleading textual output of OIDs.
3575 [Steve Henson, reported by Dan Kaminsky]
3577 *) Delete MD2 from algorithm tables. This follows the recommendation in
3578 several standards that it is not used in new applications due to
3579 several cryptographic weaknesses. For binary compatibility reasons
3580 the MD2 API is still compiled in by default.
3583 *) Add compression id to {d2i,i2d}_SSL_SESSION so it is correctly saved
3587 *) Rename uni2asc and asc2uni functions to OPENSSL_uni2asc and
3588 OPENSSL_asc2uni conditionally on Netware platforms to avoid a name
3590 [Guenter <lists@gknw.net>]
3592 *) Fix the server certificate chain building code to use X509_verify_cert(),
3593 it used to have an ad-hoc builder which was unable to cope with anything
3594 other than a simple chain.
3595 [David Woodhouse <dwmw2@infradead.org>, Steve Henson]
3597 *) Don't check self signed certificate signatures in X509_verify_cert()
3598 by default (a flag can override this): it just wastes time without
3599 adding any security. As a useful side effect self signed root CAs
3600 with non-FIPS digests are now usable in FIPS mode.
3603 *) In dtls1_process_out_of_seq_message() the check if the current message
3604 is already buffered was missing. For every new message was memory
3605 allocated, allowing an attacker to perform an denial of service attack
3606 with sending out of seq handshake messages until there is no memory
3607 left. Additionally every future messege was buffered, even if the
3608 sequence number made no sense and would be part of another handshake.
3609 So only messages with sequence numbers less than 10 in advance will be
3610 buffered. (CVE-2009-1378)
3611 [Robin Seggelmann, discovered by Daniel Mentz]
3613 *) Records are buffered if they arrive with a future epoch to be
3614 processed after finishing the corresponding handshake. There is
3615 currently no limitation to this buffer allowing an attacker to perform
3616 a DOS attack with sending records with future epochs until there is no
3617 memory left. This patch adds the pqueue_size() function to determine
3618 the size of a buffer and limits the record buffer to 100 entries.
3620 [Robin Seggelmann, discovered by Daniel Mentz]
3622 *) Keep a copy of frag->msg_header.frag_len so it can be used after the
3623 parent structure is freed. (CVE-2009-1379)
3626 *) Handle non-blocking I/O properly in SSL_shutdown() call.
3627 [Darryl Miles <darryl-mailinglists@netbauds.net>]