5 This is a high-level summary of the most important changes.
6 For a full list of changes, see the git commit log; for example,
7 https://github.com/openssl/openssl/commits/ and pick the appropriate
10 Changes between 1.1.0f and 1.1.1 [xx XXX xxxx]
12 *) Support for TLSv1.3 added. Note that users upgrading from an earlier
13 version of OpenSSL should review their configuration settings to ensure
14 that they are still appropriate for TLSv1.3. In particular if no TLSv1.3
15 ciphersuites are enabled then OpenSSL will refuse to make a connection
16 unless (1) TLSv1.3 is explicitly disabled or (2) the ciphersuite
17 configuration is updated to include suitable ciphersuites. The DEFAULT
18 ciphersuite configuration does include TLSv1.3 ciphersuites. For further
19 information on this and other related issues please see:
20 https://www.openssl.org/blog/blog/2018/02/08/tlsv1.3/
22 NOTE: In this pre-release of OpenSSL a draft version of the
23 TLSv1.3 standard has been implemented. Implementations of different draft
24 versions of the standard do not inter-operate, and this version will not
25 inter-operate with an implementation of the final standard when it is
26 eventually published. Different pre-release versions may implement
27 different versions of the draft. The final version of OpenSSL 1.1.1 will
28 implement the final version of the standard.
29 TODO(TLS1.3): Remove the above note before final release
32 *) Grand redesign of the OpenSSL random generator
34 The default RAND method now utilizes an AES-CTR DRBG according to
35 NIST standard SP 800-90Ar1. The new random generator is essentially
36 a port of the default random generator from the OpenSSL FIPS 2.0
37 object module. It is a hybrid deterministic random bit generator
38 using an AES-CTR bit stream and which seeds and reseeds itself
39 automatically using trusted system entropy sources.
41 Some of its new features are:
42 o Support for multiple DRBG instances with seed chaining.
43 o Add a public DRBG instance for the default RAND method.
44 o Add a dedicated DRBG instance for generating long term private keys.
45 o Make the DRBG instances fork-safe.
46 o Keep all global DRBG instances on the secure heap if it is enabled.
47 o Add a DRBG instance to every SSL instance for lock free operation
48 and to increase unpredictability.
49 [Paul Dale, Benjamin Kaduk, Kurt Roeckx, Rich Salz, Matthias St. Pierre]
51 *) Changed Configure so it only says what it does and doesn't dump
52 so much data. Instead, ./configdata.pm should be used as a script
53 to display all sorts of configuration data.
56 *) Added processing of "make variables" to Configure.
59 *) Added SHA512/224 and SHA512/256 algorithm support.
62 *) The last traces of Netware support, first removed in 1.1.0, have
66 *) Get rid of Makefile.shared, and in the process, make the processing
67 of certain files (rc.obj, or the .def/.map/.opt files produced from
68 the ordinal files) more visible and hopefully easier to trace and
69 debug (or make silent).
72 *) Make it possible to have environment variable assignments as
73 arguments to config / Configure.
76 *) Add multi-prime RSA (RFC 8017) support.
79 *) Add SM3 implemented according to GB/T 32905-2016
80 [ Jack Lloyd <jack.lloyd@ribose.com>,
81 Ronald Tse <ronald.tse@ribose.com>,
82 Erick Borsboom <erick.borsboom@ribose.com> ]
84 *) Add 'Maximum Fragment Length' TLS extension negotiation and support
85 as documented in RFC6066.
86 Based on a patch from Tomasz Moń
87 [Filipe Raimundo da Silva]
89 *) Add SM4 implemented according to GB/T 32907-2016.
90 [ Jack Lloyd <jack.lloyd@ribose.com>,
91 Ronald Tse <ronald.tse@ribose.com>,
92 Erick Borsboom <erick.borsboom@ribose.com> ]
94 *) Reimplement -newreq-nodes and ERR_error_string_n; the
95 original author does not agree with the license change.
98 *) Add ARIA AEAD TLS support.
101 *) Some macro definitions to support VS6 have been removed. Visual
102 Studio 6 has not worked since 1.1.0
105 *) Add ERR_clear_last_mark(), to allow callers to clear the last mark
106 without clearing the errors.
109 *) Add "atfork" functions. If building on a system that without
110 pthreads, see doc/man3/OPENSSL_fork_prepare.pod for application
111 requirements. The RAND facility now uses/requires this.
117 *) The UI API becomes a permanent and integral part of libcrypto, i.e.
118 not possible to disable entirely. However, it's still possible to
119 disable the console reading UI method, UI_OpenSSL() (use UI_null()
122 To disable, configure with 'no-ui-console'. 'no-ui' is still
123 possible to use as an alias. Check at compile time with the
124 macro OPENSSL_NO_UI_CONSOLE. The macro OPENSSL_NO_UI is still
125 possible to check and is an alias for OPENSSL_NO_UI_CONSOLE.
128 *) Add a STORE module, which implements a uniform and URI based reader of
129 stores that can contain keys, certificates, CRLs and numerous other
130 objects. The main API is loosely based on a few stdio functions,
131 and includes OSSL_STORE_open, OSSL_STORE_load, OSSL_STORE_eof,
132 OSSL_STORE_error and OSSL_STORE_close.
133 The implementation uses backends called "loaders" to implement arbitrary
134 URI schemes. There is one built in "loader" for the 'file' scheme.
137 *) Add devcrypto engine. This has been implemented against cryptodev-linux,
138 then adjusted to work on FreeBSD 8.4 as well.
139 Enable by configuring with 'enable-devcryptoeng'. This is done by default
140 on BSD implementations, as cryptodev.h is assumed to exist on all of them.
143 *) Module names can prefixed with OSSL_ or OPENSSL_. This affects
144 util/mkerr.pl, which is adapted to allow those prefixes, leading to
145 error code calls like this:
147 OSSL_FOOerr(OSSL_FOO_F_SOMETHING, OSSL_FOO_R_WHATEVER);
149 With this change, we claim the namespaces OSSL and OPENSSL in a manner
150 that can be encoded in C. For the foreseeable future, this will only
152 [Richard Levitte and Tim Hudson]
154 *) Removed BSD cryptodev engine.
157 *) Add a build target 'build_all_generated', to build all generated files
158 and only that. This can be used to prepare everything that requires
159 things like perl for a system that lacks perl and then move everything
160 to that system and do the rest of the build there.
163 *) In the UI interface, make it possible to duplicate the user data. This
164 can be used by engines that need to retain the data for a longer time
165 than just the call where this user data is passed.
168 *) Ignore the '-named_curve auto' value for compatibility of applications
170 [Tomas Mraz <tmraz@fedoraproject.org>]
172 *) Fragmented SSL/TLS alerts are no longer accepted. An alert message is 2
173 bytes long. In theory it is permissible in SSLv3 - TLSv1.2 to fragment such
174 alerts across multiple records (some of which could be empty). In practice
175 it make no sense to send an empty alert record, or to fragment one. TLSv1.3
176 prohibts this altogether and other libraries (BoringSSL, NSS) do not
177 support this at all. Supporting it adds significant complexity to the
178 record layer, and its removal is unlikely to cause inter-operability
182 *) Add the ASN.1 types INT32, UINT32, INT64, UINT64 and variants prefixed
183 with Z. These are meant to replace LONG and ZLONG and to be size safe.
184 The use of LONG and ZLONG is discouraged and scheduled for deprecation
188 *) Add the 'z' and 'j' modifiers to BIO_printf() et al formatting string,
189 'z' is to be used for [s]size_t, and 'j' - with [u]int64_t.
190 [Richard Levitte, Andy Polyakov]
192 *) Add EC_KEY_get0_engine(), which does for EC_KEY what RSA_get0_engine()
196 *) Have 'config' recognise 64-bit mingw and choose 'mingw64' as the target
197 platform rather than 'mingw'.
200 *) The functions X509_STORE_add_cert and X509_STORE_add_crl return
201 success if they are asked to add an object which already exists
202 in the store. This change cascades to other functions which load
203 certificates and CRLs.
206 *) x86_64 assembly pack: annotate code with DWARF CFI directives to
207 facilitate stack unwinding even from assembly subroutines.
210 *) Remove VAX C specific definitions of OPENSSL_EXPORT, OPENSSL_EXTERN.
211 Also remove OPENSSL_GLOBAL entirely, as it became a no-op.
214 *) Remove the VMS-specific reimplementation of gmtime from crypto/o_times.c.
215 VMS C's RTL has a fully up to date gmtime() and gmtime_r() since V7.1,
216 which is the minimum version we support.
219 *) Certificate time validation (X509_cmp_time) enforces stricter
220 compliance with RFC 5280. Fractional seconds and timezone offsets
221 are no longer allowed.
224 *) Add support for ARIA
227 *) s_client will now send the Server Name Indication (SNI) extension by
228 default unless the new "-noservername" option is used. The server name is
229 based on the host provided to the "-connect" option unless overridden by
233 *) Add support for SipHash
236 *) OpenSSL now fails if it receives an unrecognised record type in TLS1.0
237 or TLS1.1. Previously this only happened in SSLv3 and TLS1.2. This is to
238 prevent issues where no progress is being made and the peer continually
239 sends unrecognised record types, using up resources processing them.
242 *) 'openssl passwd' can now produce SHA256 and SHA512 based output,
243 using the algorithm defined in
244 https://www.akkadia.org/drepper/SHA-crypt.txt
247 *) Heartbeat support has been removed; the ABI is changed for now.
248 [Richard Levitte, Rich Salz]
250 *) Support for SSL_OP_NO_ENCRYPT_THEN_MAC in SSL_CONF_cmd.
253 *) The RSA "null" method, which was partially supported to avoid patent
254 issues, has been replaced to always returns NULL.
257 Changes between 1.1.0g and 1.1.0h [xx XXX xxxx]
259 *) Removed the OS390-Unix config target. It relied on a script that doesn't
263 *) rsaz_1024_mul_avx2 overflow bug on x86_64
265 There is an overflow bug in the AVX2 Montgomery multiplication procedure
266 used in exponentiation with 1024-bit moduli. No EC algorithms are affected.
267 Analysis suggests that attacks against RSA and DSA as a result of this
268 defect would be very difficult to perform and are not believed likely.
269 Attacks against DH1024 are considered just feasible, because most of the
270 work necessary to deduce information about a private key may be performed
271 offline. The amount of resources required for such an attack would be
272 significant. However, for an attack on TLS to be meaningful, the server
273 would have to share the DH1024 private key among multiple clients, which is
274 no longer an option since CVE-2016-0701.
276 This only affects processors that support the AVX2 but not ADX extensions
277 like Intel Haswell (4th generation).
279 This issue was reported to OpenSSL by David Benjamin (Google). The issue
280 was originally found via the OSS-Fuzz project.
284 Changes between 1.1.0f and 1.1.0g [2 Nov 2017]
286 *) bn_sqrx8x_internal carry bug on x86_64
288 There is a carry propagating bug in the x86_64 Montgomery squaring
289 procedure. No EC algorithms are affected. Analysis suggests that attacks
290 against RSA and DSA as a result of this defect would be very difficult to
291 perform and are not believed likely. Attacks against DH are considered just
292 feasible (although very difficult) because most of the work necessary to
293 deduce information about a private key may be performed offline. The amount
294 of resources required for such an attack would be very significant and
295 likely only accessible to a limited number of attackers. An attacker would
296 additionally need online access to an unpatched system using the target
297 private key in a scenario with persistent DH parameters and a private
298 key that is shared between multiple clients.
300 This only affects processors that support the BMI1, BMI2 and ADX extensions
301 like Intel Broadwell (5th generation) and later or AMD Ryzen.
303 This issue was reported to OpenSSL by the OSS-Fuzz project.
307 *) Malformed X.509 IPAddressFamily could cause OOB read
309 If an X.509 certificate has a malformed IPAddressFamily extension,
310 OpenSSL could do a one-byte buffer overread. The most likely result
311 would be an erroneous display of the certificate in text format.
313 This issue was reported to OpenSSL by the OSS-Fuzz project.
317 Changes between 1.1.0e and 1.1.0f [25 May 2017]
319 *) Have 'config' recognise 64-bit mingw and choose 'mingw64' as the target
320 platform rather than 'mingw'.
323 *) Remove the VMS-specific reimplementation of gmtime from crypto/o_times.c.
324 VMS C's RTL has a fully up to date gmtime() and gmtime_r() since V7.1,
325 which is the minimum version we support.
328 Changes between 1.1.0d and 1.1.0e [16 Feb 2017]
330 *) Encrypt-Then-Mac renegotiation crash
332 During a renegotiation handshake if the Encrypt-Then-Mac extension is
333 negotiated where it was not in the original handshake (or vice-versa) then
334 this can cause OpenSSL to crash (dependant on ciphersuite). Both clients
335 and servers are affected.
337 This issue was reported to OpenSSL by Joe Orton (Red Hat).
341 Changes between 1.1.0c and 1.1.0d [26 Jan 2017]
343 *) Truncated packet could crash via OOB read
345 If one side of an SSL/TLS path is running on a 32-bit host and a specific
346 cipher is being used, then a truncated packet can cause that host to
347 perform an out-of-bounds read, usually resulting in a crash.
349 This issue was reported to OpenSSL by Robert Święcki of Google.
353 *) Bad (EC)DHE parameters cause a client crash
355 If a malicious server supplies bad parameters for a DHE or ECDHE key
356 exchange then this can result in the client attempting to dereference a
357 NULL pointer leading to a client crash. This could be exploited in a Denial
360 This issue was reported to OpenSSL by Guido Vranken.
364 *) BN_mod_exp may produce incorrect results on x86_64
366 There is a carry propagating bug in the x86_64 Montgomery squaring
367 procedure. No EC algorithms are affected. Analysis suggests that attacks
368 against RSA and DSA as a result of this defect would be very difficult to
369 perform and are not believed likely. Attacks against DH are considered just
370 feasible (although very difficult) because most of the work necessary to
371 deduce information about a private key may be performed offline. The amount
372 of resources required for such an attack would be very significant and
373 likely only accessible to a limited number of attackers. An attacker would
374 additionally need online access to an unpatched system using the target
375 private key in a scenario with persistent DH parameters and a private
376 key that is shared between multiple clients. For example this can occur by
377 default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very
378 similar to CVE-2015-3193 but must be treated as a separate problem.
380 This issue was reported to OpenSSL by the OSS-Fuzz project.
384 Changes between 1.1.0b and 1.1.0c [10 Nov 2016]
386 *) ChaCha20/Poly1305 heap-buffer-overflow
388 TLS connections using *-CHACHA20-POLY1305 ciphersuites are susceptible to
389 a DoS attack by corrupting larger payloads. This can result in an OpenSSL
390 crash. This issue is not considered to be exploitable beyond a DoS.
392 This issue was reported to OpenSSL by Robert Święcki (Google Security Team)
396 *) CMS Null dereference
398 Applications parsing invalid CMS structures can crash with a NULL pointer
399 dereference. This is caused by a bug in the handling of the ASN.1 CHOICE
400 type in OpenSSL 1.1.0 which can result in a NULL value being passed to the
401 structure callback if an attempt is made to free certain invalid encodings.
402 Only CHOICE structures using a callback which do not handle NULL value are
405 This issue was reported to OpenSSL by Tyler Nighswander of ForAllSecure.
409 *) Montgomery multiplication may produce incorrect results
411 There is a carry propagating bug in the Broadwell-specific Montgomery
412 multiplication procedure that handles input lengths divisible by, but
413 longer than 256 bits. Analysis suggests that attacks against RSA, DSA
414 and DH private keys are impossible. This is because the subroutine in
415 question is not used in operations with the private key itself and an input
416 of the attacker's direct choice. Otherwise the bug can manifest itself as
417 transient authentication and key negotiation failures or reproducible
418 erroneous outcome of public-key operations with specially crafted input.
419 Among EC algorithms only Brainpool P-512 curves are affected and one
420 presumably can attack ECDH key negotiation. Impact was not analyzed in
421 detail, because pre-requisites for attack are considered unlikely. Namely
422 multiple clients have to choose the curve in question and the server has to
423 share the private key among them, neither of which is default behaviour.
424 Even then only clients that chose the curve will be affected.
426 This issue was publicly reported as transient failures and was not
427 initially recognized as a security issue. Thanks to Richard Morgan for
428 providing reproducible case.
432 *) Removed automatic addition of RPATH in shared libraries and executables,
433 as this was a remainder from OpenSSL 1.0.x and isn't needed any more.
436 Changes between 1.1.0a and 1.1.0b [26 Sep 2016]
438 *) Fix Use After Free for large message sizes
440 The patch applied to address CVE-2016-6307 resulted in an issue where if a
441 message larger than approx 16k is received then the underlying buffer to
442 store the incoming message is reallocated and moved. Unfortunately a
443 dangling pointer to the old location is left which results in an attempt to
444 write to the previously freed location. This is likely to result in a
445 crash, however it could potentially lead to execution of arbitrary code.
447 This issue only affects OpenSSL 1.1.0a.
449 This issue was reported to OpenSSL by Robert Święcki.
453 Changes between 1.1.0 and 1.1.0a [22 Sep 2016]
455 *) OCSP Status Request extension unbounded memory growth
457 A malicious client can send an excessively large OCSP Status Request
458 extension. If that client continually requests renegotiation, sending a
459 large OCSP Status Request extension each time, then there will be unbounded
460 memory growth on the server. This will eventually lead to a Denial Of
461 Service attack through memory exhaustion. Servers with a default
462 configuration are vulnerable even if they do not support OCSP. Builds using
463 the "no-ocsp" build time option are not affected.
465 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
469 *) SSL_peek() hang on empty record
471 OpenSSL 1.1.0 SSL/TLS will hang during a call to SSL_peek() if the peer
472 sends an empty record. This could be exploited by a malicious peer in a
473 Denial Of Service attack.
475 This issue was reported to OpenSSL by Alex Gaynor.
479 *) Excessive allocation of memory in tls_get_message_header() and
480 dtls1_preprocess_fragment()
482 A (D)TLS message includes 3 bytes for its length in the header for the
483 message. This would allow for messages up to 16Mb in length. Messages of
484 this length are excessive and OpenSSL includes a check to ensure that a
485 peer is sending reasonably sized messages in order to avoid too much memory
486 being consumed to service a connection. A flaw in the logic of version
487 1.1.0 means that memory for the message is allocated too early, prior to
488 the excessive message length check. Due to way memory is allocated in
489 OpenSSL this could mean an attacker could force up to 21Mb to be allocated
490 to service a connection. This could lead to a Denial of Service through
491 memory exhaustion. However, the excessive message length check still takes
492 place, and this would cause the connection to immediately fail. Assuming
493 that the application calls SSL_free() on the failed connection in a timely
494 manner then the 21Mb of allocated memory will then be immediately freed
495 again. Therefore the excessive memory allocation will be transitory in
496 nature. This then means that there is only a security impact if:
498 1) The application does not call SSL_free() in a timely manner in the event
499 that the connection fails
501 2) The application is working in a constrained environment where there is
502 very little free memory
504 3) The attacker initiates multiple connection attempts such that there are
505 multiple connections in a state where memory has been allocated for the
506 connection; SSL_free() has not yet been called; and there is insufficient
507 memory to service the multiple requests.
509 Except in the instance of (1) above any Denial Of Service is likely to be
510 transitory because as soon as the connection fails the memory is
511 subsequently freed again in the SSL_free() call. However there is an
512 increased risk during this period of application crashes due to the lack of
513 memory - which would then mean a more serious Denial of Service.
515 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
516 (CVE-2016-6307 and CVE-2016-6308)
519 *) solaris-x86-cc, i.e. 32-bit configuration with vendor compiler,
520 had to be removed. Primary reason is that vendor assembler can't
521 assemble our modules with -KPIC flag. As result it, assembly
522 support, was not even available as option. But its lack means
523 lack of side-channel resistant code, which is incompatible with
524 security by todays standards. Fortunately gcc is readily available
525 prepackaged option, which we firmly point at...
528 Changes between 1.0.2h and 1.1.0 [25 Aug 2016]
530 *) Windows command-line tool supports UTF-8 opt-in option for arguments
531 and console input. Setting OPENSSL_WIN32_UTF8 environment variable
532 (to any value) allows Windows user to access PKCS#12 file generated
533 with Windows CryptoAPI and protected with non-ASCII password, as well
534 as files generated under UTF-8 locale on Linux also protected with
538 *) To mitigate the SWEET32 attack (CVE-2016-2183), 3DES cipher suites
539 have been disabled by default and removed from DEFAULT, just like RC4.
540 See the RC4 item below to re-enable both.
543 *) The method for finding the storage location for the Windows RAND seed file
544 has changed. First we check %RANDFILE%. If that is not set then we check
545 the directories %HOME%, %USERPROFILE% and %SYSTEMROOT% in that order. If
546 all else fails we fall back to C:\.
549 *) The EVP_EncryptUpdate() function has had its return type changed from void
550 to int. A return of 0 indicates and error while a return of 1 indicates
554 *) The flags RSA_FLAG_NO_CONSTTIME, DSA_FLAG_NO_EXP_CONSTTIME and
555 DH_FLAG_NO_EXP_CONSTTIME which previously provided the ability to switch
556 off the constant time implementation for RSA, DSA and DH have been made
557 no-ops and deprecated.
560 *) Windows RAND implementation was simplified to only get entropy by
561 calling CryptGenRandom(). Various other RAND-related tickets
563 [Joseph Wylie Yandle, Rich Salz]
565 *) The stack and lhash API's were renamed to start with OPENSSL_SK_
566 and OPENSSL_LH_, respectively. The old names are available
567 with API compatibility. They new names are now completely documented.
570 *) Unify TYPE_up_ref(obj) methods signature.
571 SSL_CTX_up_ref(), SSL_up_ref(), X509_up_ref(), EVP_PKEY_up_ref(),
572 X509_CRL_up_ref(), X509_OBJECT_up_ref_count() methods are now returning an
573 int (instead of void) like all others TYPE_up_ref() methods.
574 So now these methods also check the return value of CRYPTO_atomic_add(),
575 and the validity of object reference counter.
576 [fdasilvayy@gmail.com]
578 *) With Windows Visual Studio builds, the .pdb files are installed
579 alongside the installed libraries and executables. For a static
580 library installation, ossl_static.pdb is the associate compiler
581 generated .pdb file to be used when linking programs.
584 *) Remove openssl.spec. Packaging files belong with the packagers.
587 *) Automatic Darwin/OSX configuration has had a refresh, it will now
588 recognise x86_64 architectures automatically. You can still decide
589 to build for a different bitness with the environment variable
590 KERNEL_BITS (can be 32 or 64), for example:
592 KERNEL_BITS=32 ./config
596 *) Change default algorithms in pkcs8 utility to use PKCS#5 v2.0,
597 256 bit AES and HMAC with SHA256.
600 *) Remove support for MIPS o32 ABI on IRIX (and IRIX only).
603 *) Triple-DES ciphers have been moved from HIGH to MEDIUM.
606 *) To enable users to have their own config files and build file templates,
607 Configure looks in the directory indicated by the environment variable
608 OPENSSL_LOCAL_CONFIG_DIR as well as the in-source Configurations/
609 directory. On VMS, OPENSSL_LOCAL_CONFIG_DIR is expected to be a logical
610 name and is used as is.
613 *) The following datatypes were made opaque: X509_OBJECT, X509_STORE_CTX,
614 X509_STORE, X509_LOOKUP, and X509_LOOKUP_METHOD. The unused type
615 X509_CERT_FILE_CTX was removed.
618 *) "shared" builds are now the default. To create only static libraries use
619 the "no-shared" Configure option.
622 *) Remove the no-aes, no-hmac, no-rsa, no-sha and no-md5 Configure options.
623 All of these option have not worked for some while and are fundamental
627 *) Make various cleanup routines no-ops and mark them as deprecated. Most
628 global cleanup functions are no longer required because they are handled
629 via auto-deinit (see OPENSSL_init_crypto and OPENSSL_init_ssl man pages).
630 Explicitly de-initing can cause problems (e.g. where a library that uses
631 OpenSSL de-inits, but an application is still using it). The affected
632 functions are CONF_modules_free(), ENGINE_cleanup(), OBJ_cleanup(),
633 EVP_cleanup(), BIO_sock_cleanup(), CRYPTO_cleanup_all_ex_data(),
634 RAND_cleanup(), SSL_COMP_free_compression_methods(), ERR_free_strings() and
638 *) --strict-warnings no longer enables runtime debugging options
639 such as REF_DEBUG. Instead, debug options are automatically
640 enabled with '--debug' builds.
641 [Andy Polyakov, Emilia Käsper]
643 *) Made DH and DH_METHOD opaque. The structures for managing DH objects
644 have been moved out of the public header files. New functions for managing
645 these have been added.
648 *) Made RSA and RSA_METHOD opaque. The structures for managing RSA
649 objects have been moved out of the public header files. New
650 functions for managing these have been added.
653 *) Made DSA and DSA_METHOD opaque. The structures for managing DSA objects
654 have been moved out of the public header files. New functions for managing
655 these have been added.
658 *) Made BIO and BIO_METHOD opaque. The structures for managing BIOs have been
659 moved out of the public header files. New functions for managing these
663 *) Removed no-rijndael as a config option. Rijndael is an old name for AES.
666 *) Removed the mk1mf build scripts.
669 *) Headers are now wrapped, if necessary, with OPENSSL_NO_xxx, so
670 it is always safe to #include a header now.
673 *) Removed the aged BC-32 config and all its supporting scripts
676 *) Removed support for Ultrix, Netware, and OS/2.
679 *) Add support for HKDF.
682 *) Add support for blake2b and blake2s
685 *) Added support for "pipelining". Ciphers that have the
686 EVP_CIPH_FLAG_PIPELINE flag set have a capability to process multiple
687 encryptions/decryptions simultaneously. There are currently no built-in
688 ciphers with this property but the expectation is that engines will be able
689 to offer it to significantly improve throughput. Support has been extended
690 into libssl so that multiple records for a single connection can be
691 processed in one go (for >=TLS 1.1).
694 *) Added the AFALG engine. This is an async capable engine which is able to
695 offload work to the Linux kernel. In this initial version it only supports
696 AES128-CBC. The kernel must be version 4.1.0 or greater.
699 *) OpenSSL now uses a new threading API. It is no longer necessary to
700 set locking callbacks to use OpenSSL in a multi-threaded environment. There
701 are two supported threading models: pthreads and windows threads. It is
702 also possible to configure OpenSSL at compile time for "no-threads". The
703 old threading API should no longer be used. The functions have been
704 replaced with "no-op" compatibility macros.
705 [Alessandro Ghedini, Matt Caswell]
707 *) Modify behavior of ALPN to invoke callback after SNI/servername
708 callback, such that updates to the SSL_CTX affect ALPN.
711 *) Add SSL_CIPHER queries for authentication and key-exchange.
714 *) Changes to the DEFAULT cipherlist:
715 - Prefer (EC)DHE handshakes over plain RSA.
716 - Prefer AEAD ciphers over legacy ciphers.
717 - Prefer ECDSA over RSA when both certificates are available.
718 - Prefer TLSv1.2 ciphers/PRF.
719 - Remove DSS, SEED, IDEA, CAMELLIA, and AES-CCM from the
723 *) Change the ECC default curve list to be this, in order: x25519,
724 secp256r1, secp521r1, secp384r1.
727 *) RC4 based libssl ciphersuites are now classed as "weak" ciphers and are
728 disabled by default. They can be re-enabled using the
729 enable-weak-ssl-ciphers option to Configure.
732 *) If the server has ALPN configured, but supports no protocols that the
733 client advertises, send a fatal "no_application_protocol" alert.
734 This behaviour is SHALL in RFC 7301, though it isn't universally
735 implemented by other servers.
738 *) Add X25519 support.
739 Add ASN.1 and EVP_PKEY methods for X25519. This includes support
740 for public and private key encoding using the format documented in
741 draft-ietf-curdle-pkix-02. The corresponding EVP_PKEY method supports
742 key generation and key derivation.
744 TLS support complies with draft-ietf-tls-rfc4492bis-08 and uses
748 *) Deprecate SRP_VBASE_get_by_user.
749 SRP_VBASE_get_by_user had inconsistent memory management behaviour.
750 In order to fix an unavoidable memory leak (CVE-2016-0798),
751 SRP_VBASE_get_by_user was changed to ignore the "fake user" SRP
752 seed, even if the seed is configured.
754 Users should use SRP_VBASE_get1_by_user instead. Note that in
755 SRP_VBASE_get1_by_user, caller must free the returned value. Note
756 also that even though configuring the SRP seed attempts to hide
757 invalid usernames by continuing the handshake with fake
758 credentials, this behaviour is not constant time and no strong
759 guarantees are made that the handshake is indistinguishable from
760 that of a valid user.
763 *) Configuration change; it's now possible to build dynamic engines
764 without having to build shared libraries and vice versa. This
765 only applies to the engines in engines/, those in crypto/engine/
766 will always be built into libcrypto (i.e. "static").
768 Building dynamic engines is enabled by default; to disable, use
769 the configuration option "disable-dynamic-engine".
771 The only requirements for building dynamic engines are the
772 presence of the DSO module and building with position independent
773 code, so they will also automatically be disabled if configuring
774 with "disable-dso" or "disable-pic".
776 The macros OPENSSL_NO_STATIC_ENGINE and OPENSSL_NO_DYNAMIC_ENGINE
777 are also taken away from openssl/opensslconf.h, as they are
781 *) Configuration change; if there is a known flag to compile
782 position independent code, it will always be applied on the
783 libcrypto and libssl object files, and never on the application
784 object files. This means other libraries that use routines from
785 libcrypto / libssl can be made into shared libraries regardless
786 of how OpenSSL was configured.
788 If this isn't desirable, the configuration options "disable-pic"
789 or "no-pic" can be used to disable the use of PIC. This will
790 also disable building shared libraries and dynamic engines.
793 *) Removed JPAKE code. It was experimental and has no wide use.
796 *) The INSTALL_PREFIX Makefile variable has been renamed to
797 DESTDIR. That makes for less confusion on what this variable
798 is for. Also, the configuration option --install_prefix is
802 *) Heartbeat for TLS has been removed and is disabled by default
803 for DTLS; configure with enable-heartbeats. Code that uses the
804 old #define's might need to be updated.
805 [Emilia Käsper, Rich Salz]
807 *) Rename REF_CHECK to REF_DEBUG.
810 *) New "unified" build system
812 The "unified" build system is aimed to be a common system for all
813 platforms we support. With it comes new support for VMS.
815 This system builds supports building in a different directory tree
816 than the source tree. It produces one Makefile (for unix family
817 or lookalikes), or one descrip.mms (for VMS).
819 The source of information to make the Makefile / descrip.mms is
820 small files called 'build.info', holding the necessary
821 information for each directory with source to compile, and a
822 template in Configurations, like unix-Makefile.tmpl or
825 With this change, the library names were also renamed on Windows
826 and on VMS. They now have names that are closer to the standard
827 on Unix, and include the major version number, and in certain
828 cases, the architecture they are built for. See "Notes on shared
829 libraries" in INSTALL.
831 We rely heavily on the perl module Text::Template.
834 *) Added support for auto-initialisation and de-initialisation of the library.
835 OpenSSL no longer requires explicit init or deinit routines to be called,
836 except in certain circumstances. See the OPENSSL_init_crypto() and
837 OPENSSL_init_ssl() man pages for further information.
840 *) The arguments to the DTLSv1_listen function have changed. Specifically the
841 "peer" argument is now expected to be a BIO_ADDR object.
843 *) Rewrite of BIO networking library. The BIO library lacked consistent
844 support of IPv6, and adding it required some more extensive
845 modifications. This introduces the BIO_ADDR and BIO_ADDRINFO types,
846 which hold all types of addresses and chains of address information.
847 It also introduces a new API, with functions like BIO_socket,
848 BIO_connect, BIO_listen, BIO_lookup and a rewrite of BIO_accept.
849 The source/sink BIOs BIO_s_connect, BIO_s_accept and BIO_s_datagram
850 have been adapted accordingly.
853 *) RSA_padding_check_PKCS1_type_1 now accepts inputs with and without
857 *) CRIME protection: disable compression by default, even if OpenSSL is
858 compiled with zlib enabled. Applications can still enable compression
859 by calling SSL_CTX_clear_options(ctx, SSL_OP_NO_COMPRESSION), or by
860 using the SSL_CONF library to configure compression.
863 *) The signature of the session callback configured with
864 SSL_CTX_sess_set_get_cb was changed. The read-only input buffer
865 was explicitly marked as 'const unsigned char*' instead of
869 *) Always DPURIFY. Remove the use of uninitialized memory in the
870 RNG, and other conditional uses of DPURIFY. This makes -DPURIFY a no-op.
873 *) Removed many obsolete configuration items, including
874 DES_PTR, DES_RISC1, DES_RISC2, DES_INT
875 MD2_CHAR, MD2_INT, MD2_LONG
877 IDEA_SHORT, IDEA_LONG
878 RC2_SHORT, RC2_LONG, RC4_LONG, RC4_CHUNK, RC4_INDEX
879 [Rich Salz, with advice from Andy Polyakov]
881 *) Many BN internals have been moved to an internal header file.
882 [Rich Salz with help from Andy Polyakov]
884 *) Configuration and writing out the results from it has changed.
885 Files such as Makefile include/openssl/opensslconf.h and are now
886 produced through general templates, such as Makefile.in and
887 crypto/opensslconf.h.in and some help from the perl module
890 Also, the center of configuration information is no longer
891 Makefile. Instead, Configure produces a perl module in
892 configdata.pm which holds most of the config data (in the hash
893 table %config), the target data that comes from the target
894 configuration in one of the Configurations/*.conf files (in
898 *) To clarify their intended purposes, the Configure options
899 --prefix and --openssldir change their semantics, and become more
900 straightforward and less interdependent.
902 --prefix shall be used exclusively to give the location INSTALLTOP
903 where programs, scripts, libraries, include files and manuals are
904 going to be installed. The default is now /usr/local.
906 --openssldir shall be used exclusively to give the default
907 location OPENSSLDIR where certificates, private keys, CRLs are
908 managed. This is also where the default openssl.cnf gets
910 If the directory given with this option is a relative path, the
911 values of both the --prefix value and the --openssldir value will
912 be combined to become OPENSSLDIR.
913 The default for --openssldir is INSTALLTOP/ssl.
915 Anyone who uses --openssldir to specify where OpenSSL is to be
916 installed MUST change to use --prefix instead.
919 *) The GOST engine was out of date and therefore it has been removed. An up
920 to date GOST engine is now being maintained in an external repository.
921 See: https://wiki.openssl.org/index.php/Binaries. Libssl still retains
922 support for GOST ciphersuites (these are only activated if a GOST engine
926 *) EGD is no longer supported by default; use enable-egd when
928 [Ben Kaduk and Rich Salz]
930 *) The distribution now has Makefile.in files, which are used to
931 create Makefile's when Configure is run. *Configure must be run
932 before trying to build now.*
935 *) The return value for SSL_CIPHER_description() for error conditions
939 *) Support for RFC6698/RFC7671 DANE TLSA peer authentication.
941 Obtaining and performing DNSSEC validation of TLSA records is
942 the application's responsibility. The application provides
943 the TLSA records of its choice to OpenSSL, and these are then
944 used to authenticate the peer.
946 The TLSA records need not even come from DNS. They can, for
947 example, be used to implement local end-entity certificate or
948 trust-anchor "pinning", where the "pin" data takes the form
949 of TLSA records, which can augment or replace verification
950 based on the usual WebPKI public certification authorities.
953 *) Revert default OPENSSL_NO_DEPRECATED setting. Instead OpenSSL
954 continues to support deprecated interfaces in default builds.
955 However, applications are strongly advised to compile their
956 source files with -DOPENSSL_API_COMPAT=0x10100000L, which hides
957 the declarations of all interfaces deprecated in 0.9.8, 1.0.0
958 or the 1.1.0 releases.
960 In environments in which all applications have been ported to
961 not use any deprecated interfaces OpenSSL's Configure script
962 should be used with the --api=1.1.0 option to entirely remove
963 support for the deprecated features from the library and
964 unconditionally disable them in the installed headers.
965 Essentially the same effect can be achieved with the "no-deprecated"
966 argument to Configure, except that this will always restrict
967 the build to just the latest API, rather than a fixed API
970 As applications are ported to future revisions of the API,
971 they should update their compile-time OPENSSL_API_COMPAT define
972 accordingly, but in most cases should be able to continue to
973 compile with later releases.
975 The OPENSSL_API_COMPAT versions for 1.0.0, and 0.9.8 are
976 0x10000000L and 0x00908000L, respectively. However those
977 versions did not support the OPENSSL_API_COMPAT feature, and
978 so applications are not typically tested for explicit support
979 of just the undeprecated features of either release.
982 *) Add support for setting the minimum and maximum supported protocol.
983 It can bet set via the SSL_set_min_proto_version() and
984 SSL_set_max_proto_version(), or via the SSL_CONF's MinProtocol and
985 MaxProtocol. It's recommended to use the new APIs to disable
986 protocols instead of disabling individual protocols using
987 SSL_set_options() or SSL_CONF's Protocol. This change also
988 removes support for disabling TLS 1.2 in the OpenSSL TLS
989 client at compile time by defining OPENSSL_NO_TLS1_2_CLIENT.
992 *) Support for ChaCha20 and Poly1305 added to libcrypto and libssl.
995 *) New EC_KEY_METHOD, this replaces the older ECDSA_METHOD and ECDH_METHOD
996 and integrates ECDSA and ECDH functionality into EC. Implementations can
997 now redirect key generation and no longer need to convert to or from
1000 Note: the ecdsa.h and ecdh.h headers are now no longer needed and just
1001 include the ec.h header file instead.
1004 *) Remove support for all 40 and 56 bit ciphers. This includes all the export
1005 ciphers who are no longer supported and drops support the ephemeral RSA key
1006 exchange. The LOW ciphers currently doesn't have any ciphers in it.
1009 *) Made EVP_MD_CTX, EVP_MD, EVP_CIPHER_CTX, EVP_CIPHER and HMAC_CTX
1010 opaque. For HMAC_CTX, the following constructors and destructors
1013 HMAC_CTX *HMAC_CTX_new(void);
1014 void HMAC_CTX_free(HMAC_CTX *ctx);
1016 For EVP_MD and EVP_CIPHER, complete APIs to create, fill and
1017 destroy such methods has been added. See EVP_MD_meth_new(3) and
1018 EVP_CIPHER_meth_new(3) for documentation.
1021 1) EVP_MD_CTX_cleanup(), EVP_CIPHER_CTX_cleanup() and
1022 HMAC_CTX_cleanup() were removed. HMAC_CTX_reset() and
1023 EVP_MD_CTX_reset() should be called instead to reinitialise
1024 an already created structure.
1025 2) For consistency with the majority of our object creators and
1026 destructors, EVP_MD_CTX_(create|destroy) were renamed to
1027 EVP_MD_CTX_(new|free). The old names are retained as macros
1028 for deprecated builds.
1031 *) Added ASYNC support. Libcrypto now includes the async sub-library to enable
1032 cryptographic operations to be performed asynchronously as long as an
1033 asynchronous capable engine is used. See the ASYNC_start_job() man page for
1034 further details. Libssl has also had this capability integrated with the
1035 introduction of the new mode SSL_MODE_ASYNC and associated error
1036 SSL_ERROR_WANT_ASYNC. See the SSL_CTX_set_mode() and SSL_get_error() man
1037 pages. This work was developed in partnership with Intel Corp.
1040 *) SSL_{CTX_}set_ecdh_auto() has been removed and ECDH is support is
1041 always enabled now. If you want to disable the support you should
1042 exclude it using the list of supported ciphers. This also means that the
1043 "-no_ecdhe" option has been removed from s_server.
1046 *) SSL_{CTX}_set_tmp_ecdh() which can set 1 EC curve now internally calls
1047 SSL_{CTX_}set1_curves() which can set a list.
1050 *) Remove support for SSL_{CTX_}set_tmp_ecdh_callback(). You should set the
1051 curve you want to support using SSL_{CTX_}set1_curves().
1054 *) State machine rewrite. The state machine code has been significantly
1055 refactored in order to remove much duplication of code and solve issues
1056 with the old code (see ssl/statem/README for further details). This change
1057 does have some associated API changes. Notably the SSL_state() function
1058 has been removed and replaced by SSL_get_state which now returns an
1059 "OSSL_HANDSHAKE_STATE" instead of an int. SSL_set_state() has been removed
1060 altogether. The previous handshake states defined in ssl.h and ssl3.h have
1064 *) All instances of the string "ssleay" in the public API were replaced
1065 with OpenSSL (case-matching; e.g., OPENSSL_VERSION for #define's)
1066 Some error codes related to internal RSA_eay API's were renamed.
1069 *) The demo files in crypto/threads were moved to demo/threads.
1072 *) Removed obsolete engines: 4758cca, aep, atalla, cswift, nuron, gmp,
1074 [Matt Caswell, Rich Salz]
1076 *) New ASN.1 embed macro.
1078 New ASN.1 macro ASN1_EMBED. This is the same as ASN1_SIMPLE except the
1079 structure is not allocated: it is part of the parent. That is instead of
1087 This reduces memory fragmentation and make it impossible to accidentally
1088 set a mandatory field to NULL.
1090 This currently only works for some fields specifically a SEQUENCE, CHOICE,
1091 or ASN1_STRING type which is part of a parent SEQUENCE. Since it is
1092 equivalent to ASN1_SIMPLE it cannot be tagged, OPTIONAL, SET OF or
1096 *) Remove EVP_CHECK_DES_KEY, a compile-time option that never compiled.
1099 *) Removed DES and RC4 ciphersuites from DEFAULT. Also removed RC2 although
1100 in 1.0.2 EXPORT was already removed and the only RC2 ciphersuite is also
1101 an EXPORT one. COMPLEMENTOFDEFAULT has been updated accordingly to add
1102 DES and RC4 ciphersuites.
1105 *) Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs.
1106 This changes the decoding behaviour for some invalid messages,
1107 though the change is mostly in the more lenient direction, and
1108 legacy behaviour is preserved as much as possible.
1111 *) Fix no-stdio build.
1112 [ David Woodhouse <David.Woodhouse@intel.com> and also
1113 Ivan Nestlerode <ivan.nestlerode@sonos.com> ]
1115 *) New testing framework
1116 The testing framework has been largely rewritten and is now using
1117 perl and the perl modules Test::Harness and an extended variant of
1118 Test::More called OpenSSL::Test to do its work. All test scripts in
1119 test/ have been rewritten into test recipes, and all direct calls to
1120 executables in test/Makefile have become individual recipes using the
1121 simplified testing OpenSSL::Test::Simple.
1123 For documentation on our testing modules, do:
1125 perldoc test/testlib/OpenSSL/Test/Simple.pm
1126 perldoc test/testlib/OpenSSL/Test.pm
1130 *) Revamped memory debug; only -DCRYPTO_MDEBUG and -DCRYPTO_MDEBUG_ABORT
1131 are used; the latter aborts on memory leaks (usually checked on exit).
1132 Some undocumented "set malloc, etc., hooks" functions were removed
1133 and others were changed. All are now documented.
1136 *) In DSA_generate_parameters_ex, if the provided seed is too short,
1138 [Rich Salz and Ismo Puustinen <ismo.puustinen@intel.com>]
1140 *) Rewrite PSK to support ECDHE_PSK, DHE_PSK and RSA_PSK. Add ciphersuites
1141 from RFC4279, RFC4785, RFC5487, RFC5489.
1143 Thanks to Christian J. Dietrich and Giuseppe D'Angelo for the
1144 original RSA_PSK patch.
1147 *) Dropped support for the SSL3_FLAGS_DELAY_CLIENT_FINISHED flag. This SSLeay
1148 era flag was never set throughout the codebase (only read). Also removed
1149 SSL3_FLAGS_POP_BUFFER which was only used if
1150 SSL3_FLAGS_DELAY_CLIENT_FINISHED was also set.
1153 *) Changed the default name options in the "ca", "crl", "req" and "x509"
1154 to be "oneline" instead of "compat".
1157 *) Remove SSL_OP_TLS_BLOCK_PADDING_BUG. This is SSLeay legacy, we're
1158 not aware of clients that still exhibit this bug, and the workaround
1159 hasn't been working properly for a while.
1162 *) The return type of BIO_number_read() and BIO_number_written() as well as
1163 the corresponding num_read and num_write members in the BIO structure has
1164 changed from unsigned long to uint64_t. On platforms where an unsigned
1165 long is 32 bits (e.g. Windows) these counters could overflow if >4Gb is
1169 *) Given the pervasive nature of TLS extensions it is inadvisable to run
1170 OpenSSL without support for them. It also means that maintaining
1171 the OPENSSL_NO_TLSEXT option within the code is very invasive (and probably
1172 not well tested). Therefore the OPENSSL_NO_TLSEXT option has been removed.
1175 *) Removed support for the two export grade static DH ciphersuites
1176 EXP-DH-RSA-DES-CBC-SHA and EXP-DH-DSS-DES-CBC-SHA. These two ciphersuites
1177 were newly added (along with a number of other static DH ciphersuites) to
1178 1.0.2. However the two export ones have *never* worked since they were
1179 introduced. It seems strange in any case to be adding new export
1180 ciphersuites, and given "logjam" it also does not seem correct to fix them.
1183 *) Version negotiation has been rewritten. In particular SSLv23_method(),
1184 SSLv23_client_method() and SSLv23_server_method() have been deprecated,
1185 and turned into macros which simply call the new preferred function names
1186 TLS_method(), TLS_client_method() and TLS_server_method(). All new code
1187 should use the new names instead. Also as part of this change the ssl23.h
1188 header file has been removed.
1191 *) Support for Kerberos ciphersuites in TLS (RFC2712) has been removed. This
1192 code and the associated standard is no longer considered fit-for-purpose.
1195 *) RT2547 was closed. When generating a private key, try to make the
1196 output file readable only by the owner. This behavior change might
1197 be noticeable when interacting with other software.
1199 *) Documented all exdata functions. Added CRYPTO_free_ex_index.
1203 *) Added HTTP GET support to the ocsp command.
1206 *) Changed default digest for the dgst and enc commands from MD5 to
1210 *) RAND_pseudo_bytes has been deprecated. Users should use RAND_bytes instead.
1213 *) Added support for TLS extended master secret from
1214 draft-ietf-tls-session-hash-03.txt. Thanks for Alfredo Pironti for an
1215 initial patch which was a great help during development.
1218 *) All libssl internal structures have been removed from the public header
1219 files, and the OPENSSL_NO_SSL_INTERN option has been removed (since it is
1220 now redundant). Users should not attempt to access internal structures
1221 directly. Instead they should use the provided API functions.
1224 *) config has been changed so that by default OPENSSL_NO_DEPRECATED is used.
1225 Access to deprecated functions can be re-enabled by running config with
1226 "enable-deprecated". In addition applications wishing to use deprecated
1227 functions must define OPENSSL_USE_DEPRECATED. Note that this new behaviour
1228 will, by default, disable some transitive includes that previously existed
1229 in the header files (e.g. ec.h will no longer, by default, include bn.h)
1232 *) Added support for OCB mode. OpenSSL has been granted a patent license
1233 compatible with the OpenSSL license for use of OCB. Details are available
1234 at https://www.openssl.org/source/OCB-patent-grant-OpenSSL.pdf. Support
1235 for OCB can be removed by calling config with no-ocb.
1238 *) SSLv2 support has been removed. It still supports receiving a SSLv2
1239 compatible client hello.
1242 *) Increased the minimal RSA keysize from 256 to 512 bits [Rich Salz],
1243 done while fixing the error code for the key-too-small case.
1244 [Annie Yousar <a.yousar@informatik.hu-berlin.de>]
1246 *) CA.sh has been removed; use CA.pl instead.
1249 *) Removed old DES API.
1252 *) Remove various unsupported platforms:
1258 Sinix/ReliantUNIX RM400
1263 16-bit platforms such as WIN16
1266 *) Clean up OPENSSL_NO_xxx #define's
1267 Use setbuf() and remove OPENSSL_NO_SETVBUF_IONBF
1268 Rename OPENSSL_SYSNAME_xxx to OPENSSL_SYS_xxx
1269 OPENSSL_NO_EC{DH,DSA} merged into OPENSSL_NO_EC
1270 OPENSSL_NO_RIPEMD160, OPENSSL_NO_RIPEMD merged into OPENSSL_NO_RMD160
1271 OPENSSL_NO_FP_API merged into OPENSSL_NO_STDIO
1272 Remove OPENSSL_NO_BIO OPENSSL_NO_BUFFER OPENSSL_NO_CHAIN_VERIFY
1273 OPENSSL_NO_EVP OPENSSL_NO_FIPS_ERR OPENSSL_NO_HASH_COMP
1274 OPENSSL_NO_LHASH OPENSSL_NO_OBJECT OPENSSL_NO_SPEED OPENSSL_NO_STACK
1275 OPENSSL_NO_X509 OPENSSL_NO_X509_VERIFY
1276 Remove MS_STATIC; it's a relic from platforms <32 bits.
1279 *) Cleaned up dead code
1280 Remove all but one '#ifdef undef' which is to be looked at.
1283 *) Clean up calling of xxx_free routines.
1284 Just like free(), fix most of the xxx_free routines to accept
1285 NULL. Remove the non-null checks from callers. Save much code.
1288 *) Add secure heap for storage of private keys (when possible).
1289 Add BIO_s_secmem(), CBIGNUM, etc.
1290 Contributed by Akamai Technologies under our Corporate CLA.
1293 *) Experimental support for a new, fast, unbiased prime candidate generator,
1294 bn_probable_prime_dh_coprime(). Not currently used by any prime generator.
1295 [Felix Laurie von Massenbach <felix@erbridge.co.uk>]
1297 *) New output format NSS in the sess_id command line tool. This allows
1298 exporting the session id and the master key in NSS keylog format.
1299 [Martin Kaiser <martin@kaiser.cx>]
1301 *) Harmonize version and its documentation. -f flag is used to display
1303 [mancha <mancha1@zoho.com>]
1305 *) Fix eckey_priv_encode so it immediately returns an error upon a failure
1306 in i2d_ECPrivateKey. Thanks to Ted Unangst for feedback on this issue.
1307 [mancha <mancha1@zoho.com>]
1309 *) Fix some double frees. These are not thought to be exploitable.
1310 [mancha <mancha1@zoho.com>]
1312 *) A missing bounds check in the handling of the TLS heartbeat extension
1313 can be used to reveal up to 64k of memory to a connected client or
1316 Thanks for Neel Mehta of Google Security for discovering this bug and to
1317 Adam Langley <agl@chromium.org> and Bodo Moeller <bmoeller@acm.org> for
1318 preparing the fix (CVE-2014-0160)
1319 [Adam Langley, Bodo Moeller]
1321 *) Fix for the attack described in the paper "Recovering OpenSSL
1322 ECDSA Nonces Using the FLUSH+RELOAD Cache Side-channel Attack"
1323 by Yuval Yarom and Naomi Benger. Details can be obtained from:
1324 http://eprint.iacr.org/2014/140
1326 Thanks to Yuval Yarom and Naomi Benger for discovering this
1327 flaw and to Yuval Yarom for supplying a fix (CVE-2014-0076)
1328 [Yuval Yarom and Naomi Benger]
1330 *) Use algorithm specific chains in SSL_CTX_use_certificate_chain_file():
1331 this fixes a limitation in previous versions of OpenSSL.
1334 *) Experimental encrypt-then-mac support.
1336 Experimental support for encrypt then mac from
1337 draft-gutmann-tls-encrypt-then-mac-02.txt
1339 To enable it set the appropriate extension number (0x42 for the test
1340 server) using e.g. -DTLSEXT_TYPE_encrypt_then_mac=0x42
1342 For non-compliant peers (i.e. just about everything) this should have no
1345 WARNING: EXPERIMENTAL, SUBJECT TO CHANGE.
1349 *) Add EVP support for key wrapping algorithms, to avoid problems with
1350 existing code the flag EVP_CIPHER_CTX_WRAP_ALLOW has to be set in
1351 the EVP_CIPHER_CTX or an error is returned. Add AES and DES3 wrap
1352 algorithms and include tests cases.
1355 *) Extend CMS code to support RSA-PSS signatures and RSA-OAEP for
1359 *) Extended RSA OAEP support via EVP_PKEY API. Options to specify digest,
1360 MGF1 digest and OAEP label.
1363 *) Make openssl verify return errors.
1364 [Chris Palmer <palmer@google.com> and Ben Laurie]
1366 *) New function ASN1_TIME_diff to calculate the difference between two
1367 ASN1_TIME structures or one structure and the current time.
1370 *) Update fips_test_suite to support multiple command line options. New
1371 test to induce all self test errors in sequence and check expected
1375 *) Add FIPS_{rsa,dsa,ecdsa}_{sign,verify} functions which digest and
1376 sign or verify all in one operation.
1379 *) Add fips_algvs: a multicall fips utility incorporating all the algorithm
1380 test programs and fips_test_suite. Includes functionality to parse
1381 the minimal script output of fipsalgest.pl directly.
1384 *) Add authorisation parameter to FIPS_module_mode_set().
1387 *) Add FIPS selftest for ECDH algorithm using P-224 and B-233 curves.
1390 *) Use separate DRBG fields for internal and external flags. New function
1391 FIPS_drbg_health_check() to perform on demand health checking. Add
1392 generation tests to fips_test_suite with reduced health check interval to
1393 demonstrate periodic health checking. Add "nodh" option to
1394 fips_test_suite to skip very slow DH test.
1397 *) New function FIPS_get_cipherbynid() to lookup FIPS supported ciphers
1401 *) More extensive health check for DRBG checking many more failure modes.
1402 New function FIPS_selftest_drbg_all() to handle every possible DRBG
1403 combination: call this in fips_test_suite.
1406 *) Add support for canonical generation of DSA parameter 'g'. See
1409 *) Add support for HMAC DRBG from SP800-90. Update DRBG algorithm test and
1410 POST to handle HMAC cases.
1413 *) Add functions FIPS_module_version() and FIPS_module_version_text()
1414 to return numerical and string versions of the FIPS module number.
1417 *) Rename FIPS_mode_set and FIPS_mode to FIPS_module_mode_set and
1418 FIPS_module_mode. FIPS_mode and FIPS_mode_set will be implemented
1419 outside the validated module in the FIPS capable OpenSSL.
1422 *) Minor change to DRBG entropy callback semantics. In some cases
1423 there is no multiple of the block length between min_len and
1424 max_len. Allow the callback to return more than max_len bytes
1425 of entropy but discard any extra: it is the callback's responsibility
1426 to ensure that the extra data discarded does not impact the
1427 requested amount of entropy.
1430 *) Add PRNG security strength checks to RSA, DSA and ECDSA using
1431 information in FIPS186-3, SP800-57 and SP800-131A.
1434 *) CCM support via EVP. Interface is very similar to GCM case except we
1435 must supply all data in one chunk (i.e. no update, final) and the
1436 message length must be supplied if AAD is used. Add algorithm test
1440 *) Initial version of POST overhaul. Add POST callback to allow the status
1441 of POST to be monitored and/or failures induced. Modify fips_test_suite
1442 to use callback. Always run all selftests even if one fails.
1445 *) XTS support including algorithm test driver in the fips_gcmtest program.
1446 Note: this does increase the maximum key length from 32 to 64 bytes but
1447 there should be no binary compatibility issues as existing applications
1448 will never use XTS mode.
1451 *) Extensive reorganisation of FIPS PRNG behaviour. Remove all dependencies
1452 to OpenSSL RAND code and replace with a tiny FIPS RAND API which also
1453 performs algorithm blocking for unapproved PRNG types. Also do not
1454 set PRNG type in FIPS_mode_set(): leave this to the application.
1455 Add default OpenSSL DRBG handling: sets up FIPS PRNG and seeds with
1456 the standard OpenSSL PRNG: set additional data to a date time vector.
1459 *) Rename old X9.31 PRNG functions of the form FIPS_rand* to FIPS_x931*.
1460 This shouldn't present any incompatibility problems because applications
1461 shouldn't be using these directly and any that are will need to rethink
1462 anyway as the X9.31 PRNG is now deprecated by FIPS 140-2
1465 *) Extensive self tests and health checking required by SP800-90 DRBG.
1466 Remove strength parameter from FIPS_drbg_instantiate and always
1467 instantiate at maximum supported strength.
1470 *) Add ECDH code to fips module and fips_ecdhvs for primitives only testing.
1473 *) New algorithm test program fips_dhvs to handle DH primitives only testing.
1476 *) New function DH_compute_key_padded() to compute a DH key and pad with
1477 leading zeroes if needed: this complies with SP800-56A et al.
1480 *) Initial implementation of SP800-90 DRBGs for Hash and CTR. Not used by
1481 anything, incomplete, subject to change and largely untested at present.
1484 *) Modify fipscanisteronly build option to only build the necessary object
1485 files by filtering FIPS_EX_OBJ through a perl script in crypto/Makefile.
1488 *) Add experimental option FIPSSYMS to give all symbols in
1489 fipscanister.o and FIPS or fips prefix. This will avoid
1490 conflicts with future versions of OpenSSL. Add perl script
1491 util/fipsas.pl to preprocess assembly language source files
1492 and rename any affected symbols.
1495 *) Add selftest checks and algorithm block of non-fips algorithms in
1496 FIPS mode. Remove DES2 from selftests.
1499 *) Add ECDSA code to fips module. Add tiny fips_ecdsa_check to just
1500 return internal method without any ENGINE dependencies. Add new
1501 tiny fips sign and verify functions.
1504 *) New build option no-ec2m to disable characteristic 2 code.
1507 *) New build option "fipscanisteronly". This only builds fipscanister.o
1508 and (currently) associated fips utilities. Uses the file Makefile.fips
1509 instead of Makefile.org as the prototype.
1512 *) Add some FIPS mode restrictions to GCM. Add internal IV generator.
1513 Update fips_gcmtest to use IV generator.
1516 *) Initial, experimental EVP support for AES-GCM. AAD can be input by
1517 setting output buffer to NULL. The *Final function must be
1518 called although it will not retrieve any additional data. The tag
1519 can be set or retrieved with a ctrl. The IV length is by default 12
1520 bytes (96 bits) but can be set to an alternative value. If the IV
1521 length exceeds the maximum IV length (currently 16 bytes) it cannot be
1525 *) New flag in ciphers: EVP_CIPH_FLAG_CUSTOM_CIPHER. This means the
1526 underlying do_cipher function handles all cipher semantics itself
1527 including padding and finalisation. This is useful if (for example)
1528 an ENGINE cipher handles block padding itself. The behaviour of
1529 do_cipher is subtly changed if this flag is set: the return value
1530 is the number of characters written to the output buffer (zero is
1531 no longer an error code) or a negative error code. Also if the
1532 input buffer is NULL and length 0 finalisation should be performed.
1535 *) If a candidate issuer certificate is already part of the constructed
1536 path ignore it: new debug notification X509_V_ERR_PATH_LOOP for this case.
1539 *) Improve forward-security support: add functions
1541 void SSL_CTX_set_not_resumable_session_callback(SSL_CTX *ctx, int (*cb)(SSL *ssl, int is_forward_secure))
1542 void SSL_set_not_resumable_session_callback(SSL *ssl, int (*cb)(SSL *ssl, int is_forward_secure))
1544 for use by SSL/TLS servers; the callback function will be called whenever a
1545 new session is created, and gets to decide whether the session may be
1546 cached to make it resumable (return 0) or not (return 1). (As by the
1547 SSL/TLS protocol specifications, the session_id sent by the server will be
1548 empty to indicate that the session is not resumable; also, the server will
1549 not generate RFC 4507 (RFC 5077) session tickets.)
1551 A simple reasonable callback implementation is to return is_forward_secure.
1552 This parameter will be set to 1 or 0 depending on the ciphersuite selected
1553 by the SSL/TLS server library, indicating whether it can provide forward
1555 [Emilia Käsper <emilia.kasper@esat.kuleuven.be> (Google)]
1557 *) New -verify_name option in command line utilities to set verification
1561 *) Initial CMAC implementation. WARNING: EXPERIMENTAL, API MAY CHANGE.
1562 Add CMAC pkey methods.
1565 *) Experimental renegotiation in s_server -www mode. If the client
1566 browses /reneg connection is renegotiated. If /renegcert it is
1567 renegotiated requesting a certificate.
1570 *) Add an "external" session cache for debugging purposes to s_server. This
1571 should help trace issues which normally are only apparent in deployed
1572 multi-process servers.
1575 *) Extensive audit of libcrypto with DEBUG_UNUSED. Fix many cases where
1576 return value is ignored. NB. The functions RAND_add(), RAND_seed(),
1577 BIO_set_cipher() and some obscure PEM functions were changed so they
1578 can now return an error. The RAND changes required a change to the
1579 RAND_METHOD structure.
1582 *) New macro __owur for "OpenSSL Warn Unused Result". This makes use of
1583 a gcc attribute to warn if the result of a function is ignored. This
1584 is enable if DEBUG_UNUSED is set. Add to several functions in evp.h
1585 whose return value is often ignored.
1588 *) New -noct, -requestct, -requirect and -ctlogfile options for s_client.
1589 These allow SCTs (signed certificate timestamps) to be requested and
1590 validated when establishing a connection.
1591 [Rob Percival <robpercival@google.com>]
1593 Changes between 1.0.2g and 1.0.2h [3 May 2016]
1595 *) Prevent padding oracle in AES-NI CBC MAC check
1597 A MITM attacker can use a padding oracle attack to decrypt traffic
1598 when the connection uses an AES CBC cipher and the server support
1601 This issue was introduced as part of the fix for Lucky 13 padding
1602 attack (CVE-2013-0169). The padding check was rewritten to be in
1603 constant time by making sure that always the same bytes are read and
1604 compared against either the MAC or padding bytes. But it no longer
1605 checked that there was enough data to have both the MAC and padding
1608 This issue was reported by Juraj Somorovsky using TLS-Attacker.
1612 *) Fix EVP_EncodeUpdate overflow
1614 An overflow can occur in the EVP_EncodeUpdate() function which is used for
1615 Base64 encoding of binary data. If an attacker is able to supply very large
1616 amounts of input data then a length check can overflow resulting in a heap
1619 Internally to OpenSSL the EVP_EncodeUpdate() function is primarily used by
1620 the PEM_write_bio* family of functions. These are mainly used within the
1621 OpenSSL command line applications, so any application which processes data
1622 from an untrusted source and outputs it as a PEM file should be considered
1623 vulnerable to this issue. User applications that call these APIs directly
1624 with large amounts of untrusted data may also be vulnerable.
1626 This issue was reported by Guido Vranken.
1630 *) Fix EVP_EncryptUpdate overflow
1632 An overflow can occur in the EVP_EncryptUpdate() function. If an attacker
1633 is able to supply very large amounts of input data after a previous call to
1634 EVP_EncryptUpdate() with a partial block then a length check can overflow
1635 resulting in a heap corruption. Following an analysis of all OpenSSL
1636 internal usage of the EVP_EncryptUpdate() function all usage is one of two
1637 forms. The first form is where the EVP_EncryptUpdate() call is known to be
1638 the first called function after an EVP_EncryptInit(), and therefore that
1639 specific call must be safe. The second form is where the length passed to
1640 EVP_EncryptUpdate() can be seen from the code to be some small value and
1641 therefore there is no possibility of an overflow. Since all instances are
1642 one of these two forms, it is believed that there can be no overflows in
1643 internal code due to this problem. It should be noted that
1644 EVP_DecryptUpdate() can call EVP_EncryptUpdate() in certain code paths.
1645 Also EVP_CipherUpdate() is a synonym for EVP_EncryptUpdate(). All instances
1646 of these calls have also been analysed too and it is believed there are no
1647 instances in internal usage where an overflow could occur.
1649 This issue was reported by Guido Vranken.
1653 *) Prevent ASN.1 BIO excessive memory allocation
1655 When ASN.1 data is read from a BIO using functions such as d2i_CMS_bio()
1656 a short invalid encoding can cause allocation of large amounts of memory
1657 potentially consuming excessive resources or exhausting memory.
1659 Any application parsing untrusted data through d2i BIO functions is
1660 affected. The memory based functions such as d2i_X509() are *not* affected.
1661 Since the memory based functions are used by the TLS library, TLS
1662 applications are not affected.
1664 This issue was reported by Brian Carpenter.
1670 ASN1 Strings that are over 1024 bytes can cause an overread in applications
1671 using the X509_NAME_oneline() function on EBCDIC systems. This could result
1672 in arbitrary stack data being returned in the buffer.
1674 This issue was reported by Guido Vranken.
1678 *) Modify behavior of ALPN to invoke callback after SNI/servername
1679 callback, such that updates to the SSL_CTX affect ALPN.
1682 *) Remove LOW from the DEFAULT cipher list. This removes singles DES from the
1686 *) Only remove the SSLv2 methods with the no-ssl2-method option. When the
1687 methods are enabled and ssl2 is disabled the methods return NULL.
1690 Changes between 1.0.2f and 1.0.2g [1 Mar 2016]
1692 * Disable weak ciphers in SSLv3 and up in default builds of OpenSSL.
1693 Builds that are not configured with "enable-weak-ssl-ciphers" will not
1694 provide any "EXPORT" or "LOW" strength ciphers.
1697 * Disable SSLv2 default build, default negotiation and weak ciphers. SSLv2
1698 is by default disabled at build-time. Builds that are not configured with
1699 "enable-ssl2" will not support SSLv2. Even if "enable-ssl2" is used,
1700 users who want to negotiate SSLv2 via the version-flexible SSLv23_method()
1701 will need to explicitly call either of:
1703 SSL_CTX_clear_options(ctx, SSL_OP_NO_SSLv2);
1705 SSL_clear_options(ssl, SSL_OP_NO_SSLv2);
1707 as appropriate. Even if either of those is used, or the application
1708 explicitly uses the version-specific SSLv2_method() or its client and
1709 server variants, SSLv2 ciphers vulnerable to exhaustive search key
1710 recovery have been removed. Specifically, the SSLv2 40-bit EXPORT
1711 ciphers, and SSLv2 56-bit DES are no longer available.
1715 *) Fix a double-free in DSA code
1717 A double free bug was discovered when OpenSSL parses malformed DSA private
1718 keys and could lead to a DoS attack or memory corruption for applications
1719 that receive DSA private keys from untrusted sources. This scenario is
1722 This issue was reported to OpenSSL by Adam Langley(Google/BoringSSL) using
1727 *) Disable SRP fake user seed to address a server memory leak.
1729 Add a new method SRP_VBASE_get1_by_user that handles the seed properly.
1731 SRP_VBASE_get_by_user had inconsistent memory management behaviour.
1732 In order to fix an unavoidable memory leak, SRP_VBASE_get_by_user
1733 was changed to ignore the "fake user" SRP seed, even if the seed
1736 Users should use SRP_VBASE_get1_by_user instead. Note that in
1737 SRP_VBASE_get1_by_user, caller must free the returned value. Note
1738 also that even though configuring the SRP seed attempts to hide
1739 invalid usernames by continuing the handshake with fake
1740 credentials, this behaviour is not constant time and no strong
1741 guarantees are made that the handshake is indistinguishable from
1742 that of a valid user.
1746 *) Fix BN_hex2bn/BN_dec2bn NULL pointer deref/heap corruption
1748 In the BN_hex2bn function the number of hex digits is calculated using an
1749 int value |i|. Later |bn_expand| is called with a value of |i * 4|. For
1750 large values of |i| this can result in |bn_expand| not allocating any
1751 memory because |i * 4| is negative. This can leave the internal BIGNUM data
1752 field as NULL leading to a subsequent NULL ptr deref. For very large values
1753 of |i|, the calculation |i * 4| could be a positive value smaller than |i|.
1754 In this case memory is allocated to the internal BIGNUM data field, but it
1755 is insufficiently sized leading to heap corruption. A similar issue exists
1756 in BN_dec2bn. This could have security consequences if BN_hex2bn/BN_dec2bn
1757 is ever called by user applications with very large untrusted hex/dec data.
1758 This is anticipated to be a rare occurrence.
1760 All OpenSSL internal usage of these functions use data that is not expected
1761 to be untrusted, e.g. config file data or application command line
1762 arguments. If user developed applications generate config file data based
1763 on untrusted data then it is possible that this could also lead to security
1764 consequences. This is also anticipated to be rare.
1766 This issue was reported to OpenSSL by Guido Vranken.
1770 *) Fix memory issues in BIO_*printf functions
1772 The internal |fmtstr| function used in processing a "%s" format string in
1773 the BIO_*printf functions could overflow while calculating the length of a
1774 string and cause an OOB read when printing very long strings.
1776 Additionally the internal |doapr_outch| function can attempt to write to an
1777 OOB memory location (at an offset from the NULL pointer) in the event of a
1778 memory allocation failure. In 1.0.2 and below this could be caused where
1779 the size of a buffer to be allocated is greater than INT_MAX. E.g. this
1780 could be in processing a very long "%s" format string. Memory leaks can
1783 The first issue may mask the second issue dependent on compiler behaviour.
1784 These problems could enable attacks where large amounts of untrusted data
1785 is passed to the BIO_*printf functions. If applications use these functions
1786 in this way then they could be vulnerable. OpenSSL itself uses these
1787 functions when printing out human-readable dumps of ASN.1 data. Therefore
1788 applications that print this data could be vulnerable if the data is from
1789 untrusted sources. OpenSSL command line applications could also be
1790 vulnerable where they print out ASN.1 data, or if untrusted data is passed
1791 as command line arguments.
1793 Libssl is not considered directly vulnerable. Additionally certificates etc
1794 received via remote connections via libssl are also unlikely to be able to
1795 trigger these issues because of message size limits enforced within libssl.
1797 This issue was reported to OpenSSL Guido Vranken.
1801 *) Side channel attack on modular exponentiation
1803 A side-channel attack was found which makes use of cache-bank conflicts on
1804 the Intel Sandy-Bridge microarchitecture which could lead to the recovery
1805 of RSA keys. The ability to exploit this issue is limited as it relies on
1806 an attacker who has control of code in a thread running on the same
1807 hyper-threaded core as the victim thread which is performing decryptions.
1809 This issue was reported to OpenSSL by Yuval Yarom, The University of
1810 Adelaide and NICTA, Daniel Genkin, Technion and Tel Aviv University, and
1811 Nadia Heninger, University of Pennsylvania with more information at
1812 http://cachebleed.info.
1816 *) Change the req app to generate a 2048-bit RSA/DSA key by default,
1817 if no keysize is specified with default_bits. This fixes an
1818 omission in an earlier change that changed all RSA/DSA key generation
1819 apps to use 2048 bits by default.
1822 Changes between 1.0.2e and 1.0.2f [28 Jan 2016]
1823 *) DH small subgroups
1825 Historically OpenSSL only ever generated DH parameters based on "safe"
1826 primes. More recently (in version 1.0.2) support was provided for
1827 generating X9.42 style parameter files such as those required for RFC 5114
1828 support. The primes used in such files may not be "safe". Where an
1829 application is using DH configured with parameters based on primes that are
1830 not "safe" then an attacker could use this fact to find a peer's private
1831 DH exponent. This attack requires that the attacker complete multiple
1832 handshakes in which the peer uses the same private DH exponent. For example
1833 this could be used to discover a TLS server's private DH exponent if it's
1834 reusing the private DH exponent or it's using a static DH ciphersuite.
1836 OpenSSL provides the option SSL_OP_SINGLE_DH_USE for ephemeral DH (DHE) in
1837 TLS. It is not on by default. If the option is not set then the server
1838 reuses the same private DH exponent for the life of the server process and
1839 would be vulnerable to this attack. It is believed that many popular
1840 applications do set this option and would therefore not be at risk.
1842 The fix for this issue adds an additional check where a "q" parameter is
1843 available (as is the case in X9.42 based parameters). This detects the
1844 only known attack, and is the only possible defense for static DH
1845 ciphersuites. This could have some performance impact.
1847 Additionally the SSL_OP_SINGLE_DH_USE option has been switched on by
1848 default and cannot be disabled. This could have some performance impact.
1850 This issue was reported to OpenSSL by Antonio Sanso (Adobe).
1854 *) SSLv2 doesn't block disabled ciphers
1856 A malicious client can negotiate SSLv2 ciphers that have been disabled on
1857 the server and complete SSLv2 handshakes even if all SSLv2 ciphers have
1858 been disabled, provided that the SSLv2 protocol was not also disabled via
1861 This issue was reported to OpenSSL on 26th December 2015 by Nimrod Aviram
1862 and Sebastian Schinzel.
1866 Changes between 1.0.2d and 1.0.2e [3 Dec 2015]
1868 *) BN_mod_exp may produce incorrect results on x86_64
1870 There is a carry propagating bug in the x86_64 Montgomery squaring
1871 procedure. No EC algorithms are affected. Analysis suggests that attacks
1872 against RSA and DSA as a result of this defect would be very difficult to
1873 perform and are not believed likely. Attacks against DH are considered just
1874 feasible (although very difficult) because most of the work necessary to
1875 deduce information about a private key may be performed offline. The amount
1876 of resources required for such an attack would be very significant and
1877 likely only accessible to a limited number of attackers. An attacker would
1878 additionally need online access to an unpatched system using the target
1879 private key in a scenario with persistent DH parameters and a private
1880 key that is shared between multiple clients. For example this can occur by
1881 default in OpenSSL DHE based SSL/TLS ciphersuites.
1883 This issue was reported to OpenSSL by Hanno Böck.
1887 *) Certificate verify crash with missing PSS parameter
1889 The signature verification routines will crash with a NULL pointer
1890 dereference if presented with an ASN.1 signature using the RSA PSS
1891 algorithm and absent mask generation function parameter. Since these
1892 routines are used to verify certificate signature algorithms this can be
1893 used to crash any certificate verification operation and exploited in a
1894 DoS attack. Any application which performs certificate verification is
1895 vulnerable including OpenSSL clients and servers which enable client
1898 This issue was reported to OpenSSL by Loïc Jonas Etienne (Qnective AG).
1902 *) X509_ATTRIBUTE memory leak
1904 When presented with a malformed X509_ATTRIBUTE structure OpenSSL will leak
1905 memory. This structure is used by the PKCS#7 and CMS routines so any
1906 application which reads PKCS#7 or CMS data from untrusted sources is
1907 affected. SSL/TLS is not affected.
1909 This issue was reported to OpenSSL by Adam Langley (Google/BoringSSL) using
1914 *) Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs.
1915 This changes the decoding behaviour for some invalid messages,
1916 though the change is mostly in the more lenient direction, and
1917 legacy behaviour is preserved as much as possible.
1920 *) In DSA_generate_parameters_ex, if the provided seed is too short,
1922 [Rich Salz and Ismo Puustinen <ismo.puustinen@intel.com>]
1924 Changes between 1.0.2c and 1.0.2d [9 Jul 2015]
1926 *) Alternate chains certificate forgery
1928 During certificate verification, OpenSSL will attempt to find an
1929 alternative certificate chain if the first attempt to build such a chain
1930 fails. An error in the implementation of this logic can mean that an
1931 attacker could cause certain checks on untrusted certificates to be
1932 bypassed, such as the CA flag, enabling them to use a valid leaf
1933 certificate to act as a CA and "issue" an invalid certificate.
1935 This issue was reported to OpenSSL by Adam Langley/David Benjamin
1939 Changes between 1.0.2b and 1.0.2c [12 Jun 2015]
1941 *) Fix HMAC ABI incompatibility. The previous version introduced an ABI
1942 incompatibility in the handling of HMAC. The previous ABI has now been
1946 Changes between 1.0.2a and 1.0.2b [11 Jun 2015]
1948 *) Malformed ECParameters causes infinite loop
1950 When processing an ECParameters structure OpenSSL enters an infinite loop
1951 if the curve specified is over a specially malformed binary polynomial
1954 This can be used to perform denial of service against any
1955 system which processes public keys, certificate requests or
1956 certificates. This includes TLS clients and TLS servers with
1957 client authentication enabled.
1959 This issue was reported to OpenSSL by Joseph Barr-Pixton.
1963 *) Exploitable out-of-bounds read in X509_cmp_time
1965 X509_cmp_time does not properly check the length of the ASN1_TIME
1966 string and can read a few bytes out of bounds. In addition,
1967 X509_cmp_time accepts an arbitrary number of fractional seconds in the
1970 An attacker can use this to craft malformed certificates and CRLs of
1971 various sizes and potentially cause a segmentation fault, resulting in
1972 a DoS on applications that verify certificates or CRLs. TLS clients
1973 that verify CRLs are affected. TLS clients and servers with client
1974 authentication enabled may be affected if they use custom verification
1977 This issue was reported to OpenSSL by Robert Swiecki (Google), and
1978 independently by Hanno Böck.
1982 *) PKCS7 crash with missing EnvelopedContent
1984 The PKCS#7 parsing code does not handle missing inner EncryptedContent
1985 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs
1986 with missing content and trigger a NULL pointer dereference on parsing.
1988 Applications that decrypt PKCS#7 data or otherwise parse PKCS#7
1989 structures from untrusted sources are affected. OpenSSL clients and
1990 servers are not affected.
1992 This issue was reported to OpenSSL by Michal Zalewski (Google).
1996 *) CMS verify infinite loop with unknown hash function
1998 When verifying a signedData message the CMS code can enter an infinite loop
1999 if presented with an unknown hash function OID. This can be used to perform
2000 denial of service against any system which verifies signedData messages using
2002 This issue was reported to OpenSSL by Johannes Bauer.
2006 *) Race condition handling NewSessionTicket
2008 If a NewSessionTicket is received by a multi-threaded client when attempting to
2009 reuse a previous ticket then a race condition can occur potentially leading to
2010 a double free of the ticket data.
2014 *) Only support 256-bit or stronger elliptic curves with the
2015 'ecdh_auto' setting (server) or by default (client). Of supported
2016 curves, prefer P-256 (both).
2019 Changes between 1.0.2 and 1.0.2a [19 Mar 2015]
2021 *) ClientHello sigalgs DoS fix
2023 If a client connects to an OpenSSL 1.0.2 server and renegotiates with an
2024 invalid signature algorithms extension a NULL pointer dereference will
2025 occur. This can be exploited in a DoS attack against the server.
2027 This issue was was reported to OpenSSL by David Ramos of Stanford
2030 [Stephen Henson and Matt Caswell]
2032 *) Multiblock corrupted pointer fix
2034 OpenSSL 1.0.2 introduced the "multiblock" performance improvement. This
2035 feature only applies on 64 bit x86 architecture platforms that support AES
2036 NI instructions. A defect in the implementation of "multiblock" can cause
2037 OpenSSL's internal write buffer to become incorrectly set to NULL when
2038 using non-blocking IO. Typically, when the user application is using a
2039 socket BIO for writing, this will only result in a failed connection.
2040 However if some other BIO is used then it is likely that a segmentation
2041 fault will be triggered, thus enabling a potential DoS attack.
2043 This issue was reported to OpenSSL by Daniel Danner and Rainer Mueller.
2047 *) Segmentation fault in DTLSv1_listen fix
2049 The DTLSv1_listen function is intended to be stateless and processes the
2050 initial ClientHello from many peers. It is common for user code to loop
2051 over the call to DTLSv1_listen until a valid ClientHello is received with
2052 an associated cookie. A defect in the implementation of DTLSv1_listen means
2053 that state is preserved in the SSL object from one invocation to the next
2054 that can lead to a segmentation fault. Errors processing the initial
2055 ClientHello can trigger this scenario. An example of such an error could be
2056 that a DTLS1.0 only client is attempting to connect to a DTLS1.2 only
2059 This issue was reported to OpenSSL by Per Allansson.
2063 *) Segmentation fault in ASN1_TYPE_cmp fix
2065 The function ASN1_TYPE_cmp will crash with an invalid read if an attempt is
2066 made to compare ASN.1 boolean types. Since ASN1_TYPE_cmp is used to check
2067 certificate signature algorithm consistency this can be used to crash any
2068 certificate verification operation and exploited in a DoS attack. Any
2069 application which performs certificate verification is vulnerable including
2070 OpenSSL clients and servers which enable client authentication.
2074 *) Segmentation fault for invalid PSS parameters fix
2076 The signature verification routines will crash with a NULL pointer
2077 dereference if presented with an ASN.1 signature using the RSA PSS
2078 algorithm and invalid parameters. Since these routines are used to verify
2079 certificate signature algorithms this can be used to crash any
2080 certificate verification operation and exploited in a DoS attack. Any
2081 application which performs certificate verification is vulnerable including
2082 OpenSSL clients and servers which enable client authentication.
2084 This issue was was reported to OpenSSL by Brian Carpenter.
2088 *) ASN.1 structure reuse memory corruption fix
2090 Reusing a structure in ASN.1 parsing may allow an attacker to cause
2091 memory corruption via an invalid write. Such reuse is and has been
2092 strongly discouraged and is believed to be rare.
2094 Applications that parse structures containing CHOICE or ANY DEFINED BY
2095 components may be affected. Certificate parsing (d2i_X509 and related
2096 functions) are however not affected. OpenSSL clients and servers are
2101 *) PKCS7 NULL pointer dereferences fix
2103 The PKCS#7 parsing code does not handle missing outer ContentInfo
2104 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with
2105 missing content and trigger a NULL pointer dereference on parsing.
2107 Applications that verify PKCS#7 signatures, decrypt PKCS#7 data or
2108 otherwise parse PKCS#7 structures from untrusted sources are
2109 affected. OpenSSL clients and servers are not affected.
2111 This issue was reported to OpenSSL by Michal Zalewski (Google).
2115 *) DoS via reachable assert in SSLv2 servers fix
2117 A malicious client can trigger an OPENSSL_assert (i.e., an abort) in
2118 servers that both support SSLv2 and enable export cipher suites by sending
2119 a specially crafted SSLv2 CLIENT-MASTER-KEY message.
2121 This issue was discovered by Sean Burford (Google) and Emilia Käsper
2122 (OpenSSL development team).
2126 *) Empty CKE with client auth and DHE fix
2128 If client auth is used then a server can seg fault in the event of a DHE
2129 ciphersuite being selected and a zero length ClientKeyExchange message
2130 being sent by the client. This could be exploited in a DoS attack.
2134 *) Handshake with unseeded PRNG fix
2136 Under certain conditions an OpenSSL 1.0.2 client can complete a handshake
2137 with an unseeded PRNG. The conditions are:
2138 - The client is on a platform where the PRNG has not been seeded
2139 automatically, and the user has not seeded manually
2140 - A protocol specific client method version has been used (i.e. not
2141 SSL_client_methodv23)
2142 - A ciphersuite is used that does not require additional random data from
2143 the PRNG beyond the initial ClientHello client random (e.g. PSK-RC4-SHA).
2145 If the handshake succeeds then the client random that has been used will
2146 have been generated from a PRNG with insufficient entropy and therefore the
2147 output may be predictable.
2149 For example using the following command with an unseeded openssl will
2150 succeed on an unpatched platform:
2152 openssl s_client -psk 1a2b3c4d -tls1_2 -cipher PSK-RC4-SHA
2156 *) Use After Free following d2i_ECPrivatekey error fix
2158 A malformed EC private key file consumed via the d2i_ECPrivateKey function
2159 could cause a use after free condition. This, in turn, could cause a double
2160 free in several private key parsing functions (such as d2i_PrivateKey
2161 or EVP_PKCS82PKEY) and could lead to a DoS attack or memory corruption
2162 for applications that receive EC private keys from untrusted
2163 sources. This scenario is considered rare.
2165 This issue was discovered by the BoringSSL project and fixed in their
2170 *) X509_to_X509_REQ NULL pointer deref fix
2172 The function X509_to_X509_REQ will crash with a NULL pointer dereference if
2173 the certificate key is invalid. This function is rarely used in practice.
2175 This issue was discovered by Brian Carpenter.
2179 *) Removed the export ciphers from the DEFAULT ciphers
2182 Changes between 1.0.1l and 1.0.2 [22 Jan 2015]
2184 *) Facilitate "universal" ARM builds targeting range of ARM ISAs, e.g.
2185 ARMv5 through ARMv8, as opposite to "locking" it to single one.
2186 So far those who have to target multiple platforms would compromise
2187 and argue that binary targeting say ARMv5 would still execute on
2188 ARMv8. "Universal" build resolves this compromise by providing
2189 near-optimal performance even on newer platforms.
2192 *) Accelerated NIST P-256 elliptic curve implementation for x86_64
2193 (other platforms pending).
2194 [Shay Gueron & Vlad Krasnov (Intel Corp), Andy Polyakov]
2196 *) Add support for the SignedCertificateTimestampList certificate and
2197 OCSP response extensions from RFC6962.
2200 *) Fix ec_GFp_simple_points_make_affine (thus, EC_POINTs_mul etc.)
2201 for corner cases. (Certain input points at infinity could lead to
2202 bogus results, with non-infinity inputs mapped to infinity too.)
2205 *) Initial support for PowerISA 2.0.7, first implemented in POWER8.
2206 This covers AES, SHA256/512 and GHASH. "Initial" means that most
2207 common cases are optimized and there still is room for further
2208 improvements. Vector Permutation AES for Altivec is also added.
2211 *) Add support for little-endian ppc64 Linux target.
2212 [Marcelo Cerri (IBM)]
2214 *) Initial support for AMRv8 ISA crypto extensions. This covers AES,
2215 SHA1, SHA256 and GHASH. "Initial" means that most common cases
2216 are optimized and there still is room for further improvements.
2217 Both 32- and 64-bit modes are supported.
2218 [Andy Polyakov, Ard Biesheuvel (Linaro)]
2220 *) Improved ARMv7 NEON support.
2223 *) Support for SPARC Architecture 2011 crypto extensions, first
2224 implemented in SPARC T4. This covers AES, DES, Camellia, SHA1,
2225 SHA256/512, MD5, GHASH and modular exponentiation.
2226 [Andy Polyakov, David Miller]
2228 *) Accelerated modular exponentiation for Intel processors, a.k.a.
2230 [Shay Gueron & Vlad Krasnov (Intel Corp)]
2232 *) Support for new and upcoming Intel processors, including AVX2,
2233 BMI and SHA ISA extensions. This includes additional "stitched"
2234 implementations, AESNI-SHA256 and GCM, and multi-buffer support
2237 This work was sponsored by Intel Corp.
2240 *) Support for DTLS 1.2. This adds two sets of DTLS methods: DTLS_*_method()
2241 supports both DTLS 1.2 and 1.0 and should use whatever version the peer
2242 supports and DTLSv1_2_*_method() which supports DTLS 1.2 only.
2245 *) Use algorithm specific chains in SSL_CTX_use_certificate_chain_file():
2246 this fixes a limitation in previous versions of OpenSSL.
2249 *) Extended RSA OAEP support via EVP_PKEY API. Options to specify digest,
2250 MGF1 digest and OAEP label.
2253 *) Add EVP support for key wrapping algorithms, to avoid problems with
2254 existing code the flag EVP_CIPHER_CTX_WRAP_ALLOW has to be set in
2255 the EVP_CIPHER_CTX or an error is returned. Add AES and DES3 wrap
2256 algorithms and include tests cases.
2259 *) Add functions to allocate and set the fields of an ECDSA_METHOD
2261 [Douglas E. Engert, Steve Henson]
2263 *) New functions OPENSSL_gmtime_diff and ASN1_TIME_diff to find the
2264 difference in days and seconds between two tm or ASN1_TIME structures.
2267 *) Add -rev test option to s_server to just reverse order of characters
2268 received by client and send back to server. Also prints an abbreviated
2269 summary of the connection parameters.
2272 *) New option -brief for s_client and s_server to print out a brief summary
2273 of connection parameters.
2276 *) Add callbacks for arbitrary TLS extensions.
2277 [Trevor Perrin <trevp@trevp.net> and Ben Laurie]
2279 *) New option -crl_download in several openssl utilities to download CRLs
2280 from CRLDP extension in certificates.
2283 *) New options -CRL and -CRLform for s_client and s_server for CRLs.
2286 *) New function X509_CRL_diff to generate a delta CRL from the difference
2287 of two full CRLs. Add support to "crl" utility.
2290 *) New functions to set lookup_crls function and to retrieve
2291 X509_STORE from X509_STORE_CTX.
2294 *) Print out deprecated issuer and subject unique ID fields in
2298 *) Extend OCSP I/O functions so they can be used for simple general purpose
2299 HTTP as well as OCSP. New wrapper function which can be used to download
2300 CRLs using the OCSP API.
2303 *) Delegate command line handling in s_client/s_server to SSL_CONF APIs.
2306 *) SSL_CONF* functions. These provide a common framework for application
2307 configuration using configuration files or command lines.
2310 *) SSL/TLS tracing code. This parses out SSL/TLS records using the
2311 message callback and prints the results. Needs compile time option
2312 "enable-ssl-trace". New options to s_client and s_server to enable
2316 *) New ctrl and macro to retrieve supported points extensions.
2317 Print out extension in s_server and s_client.
2320 *) New functions to retrieve certificate signature and signature
2324 *) Add functions to retrieve and manipulate the raw cipherlist sent by a
2328 *) New Suite B modes for TLS code. These use and enforce the requirements
2329 of RFC6460: restrict ciphersuites, only permit Suite B algorithms and
2330 only use Suite B curves. The Suite B modes can be set by using the
2331 strings "SUITEB128", "SUITEB192" or "SUITEB128ONLY" for the cipherstring.
2334 *) New chain verification flags for Suite B levels of security. Check
2335 algorithms are acceptable when flags are set in X509_verify_cert.
2338 *) Make tls1_check_chain return a set of flags indicating checks passed
2339 by a certificate chain. Add additional tests to handle client
2340 certificates: checks for matching certificate type and issuer name
2344 *) If an attempt is made to use a signature algorithm not in the peer
2345 preference list abort the handshake. If client has no suitable
2346 signature algorithms in response to a certificate request do not
2347 use the certificate.
2350 *) If server EC tmp key is not in client preference list abort handshake.
2353 *) Add support for certificate stores in CERT structure. This makes it
2354 possible to have different stores per SSL structure or one store in
2355 the parent SSL_CTX. Include distinct stores for certificate chain
2356 verification and chain building. New ctrl SSL_CTRL_BUILD_CERT_CHAIN
2357 to build and store a certificate chain in CERT structure: returning
2358 an error if the chain cannot be built: this will allow applications
2359 to test if a chain is correctly configured.
2361 Note: if the CERT based stores are not set then the parent SSL_CTX
2362 store is used to retain compatibility with existing behaviour.
2366 *) New function ssl_set_client_disabled to set a ciphersuite disabled
2367 mask based on the current session, check mask when sending client
2368 hello and checking the requested ciphersuite.
2371 *) New ctrls to retrieve and set certificate types in a certificate
2372 request message. Print out received values in s_client. If certificate
2373 types is not set with custom values set sensible values based on
2374 supported signature algorithms.
2377 *) Support for distinct client and server supported signature algorithms.
2380 *) Add certificate callback. If set this is called whenever a certificate
2381 is required by client or server. An application can decide which
2382 certificate chain to present based on arbitrary criteria: for example
2383 supported signature algorithms. Add very simple example to s_server.
2384 This fixes many of the problems and restrictions of the existing client
2385 certificate callback: for example you can now clear an existing
2386 certificate and specify the whole chain.
2389 *) Add new "valid_flags" field to CERT_PKEY structure which determines what
2390 the certificate can be used for (if anything). Set valid_flags field
2391 in new tls1_check_chain function. Simplify ssl_set_cert_masks which used
2392 to have similar checks in it.
2394 Add new "cert_flags" field to CERT structure and include a "strict mode".
2395 This enforces some TLS certificate requirements (such as only permitting
2396 certificate signature algorithms contained in the supported algorithms
2397 extension) which some implementations ignore: this option should be used
2398 with caution as it could cause interoperability issues.
2401 *) Update and tidy signature algorithm extension processing. Work out
2402 shared signature algorithms based on preferences and peer algorithms
2403 and print them out in s_client and s_server. Abort handshake if no
2404 shared signature algorithms.
2407 *) Add new functions to allow customised supported signature algorithms
2408 for SSL and SSL_CTX structures. Add options to s_client and s_server
2412 *) New function SSL_certs_clear() to delete all references to certificates
2413 from an SSL structure. Before this once a certificate had been added
2414 it couldn't be removed.
2417 *) Integrate hostname, email address and IP address checking with certificate
2418 verification. New verify options supporting checking in openssl utility.
2421 *) Fixes and wildcard matching support to hostname and email checking
2422 functions. Add manual page.
2423 [Florian Weimer (Red Hat Product Security Team)]
2425 *) New functions to check a hostname email or IP address against a
2426 certificate. Add options x509 utility to print results of checks against
2430 *) Fix OCSP checking.
2431 [Rob Stradling <rob.stradling@comodo.com> and Ben Laurie]
2433 *) Initial experimental support for explicitly trusted non-root CAs.
2434 OpenSSL still tries to build a complete chain to a root but if an
2435 intermediate CA has a trust setting included that is used. The first
2436 setting is used: whether to trust (e.g., -addtrust option to the x509
2440 *) Add -trusted_first option which attempts to find certificates in the
2441 trusted store even if an untrusted chain is also supplied.
2444 *) MIPS assembly pack updates: support for MIPS32r2 and SmartMIPS ASE,
2445 platform support for Linux and Android.
2448 *) Support for linux-x32, ILP32 environment in x86_64 framework.
2451 *) Experimental multi-implementation support for FIPS capable OpenSSL.
2452 When in FIPS mode the approved implementations are used as normal,
2453 when not in FIPS mode the internal unapproved versions are used instead.
2454 This means that the FIPS capable OpenSSL isn't forced to use the
2455 (often lower performance) FIPS implementations outside FIPS mode.
2458 *) Transparently support X9.42 DH parameters when calling
2459 PEM_read_bio_DHparameters. This means existing applications can handle
2460 the new parameter format automatically.
2463 *) Initial experimental support for X9.42 DH parameter format: mainly
2464 to support use of 'q' parameter for RFC5114 parameters.
2467 *) Add DH parameters from RFC5114 including test data to dhtest.
2470 *) Support for automatic EC temporary key parameter selection. If enabled
2471 the most preferred EC parameters are automatically used instead of
2472 hardcoded fixed parameters. Now a server just has to call:
2473 SSL_CTX_set_ecdh_auto(ctx, 1) and the server will automatically
2474 support ECDH and use the most appropriate parameters.
2477 *) Enhance and tidy EC curve and point format TLS extension code. Use
2478 static structures instead of allocation if default values are used.
2479 New ctrls to set curves we wish to support and to retrieve shared curves.
2480 Print out shared curves in s_server. New options to s_server and s_client
2481 to set list of supported curves.
2484 *) New ctrls to retrieve supported signature algorithms and
2485 supported curve values as an array of NIDs. Extend openssl utility
2486 to print out received values.
2489 *) Add new APIs EC_curve_nist2nid and EC_curve_nid2nist which convert
2490 between NIDs and the more common NIST names such as "P-256". Enhance
2491 ecparam utility and ECC method to recognise the NIST names for curves.
2494 *) Enhance SSL/TLS certificate chain handling to support different
2495 chains for each certificate instead of one chain in the parent SSL_CTX.
2498 *) Support for fixed DH ciphersuite client authentication: where both
2499 server and client use DH certificates with common parameters.
2502 *) Support for fixed DH ciphersuites: those requiring DH server
2506 *) New function i2d_re_X509_tbs for re-encoding the TBS portion of
2508 Note: Related 1.0.2-beta specific macros X509_get_cert_info,
2509 X509_CINF_set_modified, X509_CINF_get_issuer, X509_CINF_get_extensions and
2510 X509_CINF_get_signature were reverted post internal team review.
2512 Changes between 1.0.1k and 1.0.1l [15 Jan 2015]
2514 *) Build fixes for the Windows and OpenVMS platforms
2515 [Matt Caswell and Richard Levitte]
2517 Changes between 1.0.1j and 1.0.1k [8 Jan 2015]
2519 *) Fix DTLS segmentation fault in dtls1_get_record. A carefully crafted DTLS
2520 message can cause a segmentation fault in OpenSSL due to a NULL pointer
2521 dereference. This could lead to a Denial Of Service attack. Thanks to
2522 Markus Stenberg of Cisco Systems, Inc. for reporting this issue.
2526 *) Fix DTLS memory leak in dtls1_buffer_record. A memory leak can occur in the
2527 dtls1_buffer_record function under certain conditions. In particular this
2528 could occur if an attacker sent repeated DTLS records with the same
2529 sequence number but for the next epoch. The memory leak could be exploited
2530 by an attacker in a Denial of Service attack through memory exhaustion.
2531 Thanks to Chris Mueller for reporting this issue.
2535 *) Fix issue where no-ssl3 configuration sets method to NULL. When openssl is
2536 built with the no-ssl3 option and a SSL v3 ClientHello is received the ssl
2537 method would be set to NULL which could later result in a NULL pointer
2538 dereference. Thanks to Frank Schmirler for reporting this issue.
2542 *) Abort handshake if server key exchange message is omitted for ephemeral
2545 Thanks to Karthikeyan Bhargavan of the PROSECCO team at INRIA for
2546 reporting this issue.
2550 *) Remove non-export ephemeral RSA code on client and server. This code
2551 violated the TLS standard by allowing the use of temporary RSA keys in
2552 non-export ciphersuites and could be used by a server to effectively
2553 downgrade the RSA key length used to a value smaller than the server
2554 certificate. Thanks for Karthikeyan Bhargavan of the PROSECCO team at
2555 INRIA or reporting this issue.
2559 *) Fixed issue where DH client certificates are accepted without verification.
2560 An OpenSSL server will accept a DH certificate for client authentication
2561 without the certificate verify message. This effectively allows a client to
2562 authenticate without the use of a private key. This only affects servers
2563 which trust a client certificate authority which issues certificates
2564 containing DH keys: these are extremely rare and hardly ever encountered.
2565 Thanks for Karthikeyan Bhargavan of the PROSECCO team at INRIA or reporting
2570 *) Ensure that the session ID context of an SSL is updated when its
2571 SSL_CTX is updated via SSL_set_SSL_CTX.
2573 The session ID context is typically set from the parent SSL_CTX,
2574 and can vary with the CTX.
2577 *) Fix various certificate fingerprint issues.
2579 By using non-DER or invalid encodings outside the signed portion of a
2580 certificate the fingerprint can be changed without breaking the signature.
2581 Although no details of the signed portion of the certificate can be changed
2582 this can cause problems with some applications: e.g. those using the
2583 certificate fingerprint for blacklists.
2585 1. Reject signatures with non zero unused bits.
2587 If the BIT STRING containing the signature has non zero unused bits reject
2588 the signature. All current signature algorithms require zero unused bits.
2590 2. Check certificate algorithm consistency.
2592 Check the AlgorithmIdentifier inside TBS matches the one in the
2593 certificate signature. NB: this will result in signature failure
2594 errors for some broken certificates.
2596 Thanks to Konrad Kraszewski from Google for reporting this issue.
2598 3. Check DSA/ECDSA signatures use DER.
2600 Re-encode DSA/ECDSA signatures and compare with the original received
2601 signature. Return an error if there is a mismatch.
2603 This will reject various cases including garbage after signature
2604 (thanks to Antti Karjalainen and Tuomo Untinen from the Codenomicon CROSS
2605 program for discovering this case) and use of BER or invalid ASN.1 INTEGERs
2606 (negative or with leading zeroes).
2608 Further analysis was conducted and fixes were developed by Stephen Henson
2609 of the OpenSSL core team.
2614 *) Correct Bignum squaring. Bignum squaring (BN_sqr) may produce incorrect
2615 results on some platforms, including x86_64. This bug occurs at random
2616 with a very low probability, and is not known to be exploitable in any
2617 way, though its exact impact is difficult to determine. Thanks to Pieter
2618 Wuille (Blockstream) who reported this issue and also suggested an initial
2619 fix. Further analysis was conducted by the OpenSSL development team and
2620 Adam Langley of Google. The final fix was developed by Andy Polyakov of
2621 the OpenSSL core team.
2625 *) Do not resume sessions on the server if the negotiated protocol
2626 version does not match the session's version. Resuming with a different
2627 version, while not strictly forbidden by the RFC, is of questionable
2628 sanity and breaks all known clients.
2629 [David Benjamin, Emilia Käsper]
2631 *) Tighten handling of the ChangeCipherSpec (CCS) message: reject
2632 early CCS messages during renegotiation. (Note that because
2633 renegotiation is encrypted, this early CCS was not exploitable.)
2636 *) Tighten client-side session ticket handling during renegotiation:
2637 ensure that the client only accepts a session ticket if the server sends
2638 the extension anew in the ServerHello. Previously, a TLS client would
2639 reuse the old extension state and thus accept a session ticket if one was
2640 announced in the initial ServerHello.
2642 Similarly, ensure that the client requires a session ticket if one
2643 was advertised in the ServerHello. Previously, a TLS client would
2644 ignore a missing NewSessionTicket message.
2647 Changes between 1.0.1i and 1.0.1j [15 Oct 2014]
2649 *) SRTP Memory Leak.
2651 A flaw in the DTLS SRTP extension parsing code allows an attacker, who
2652 sends a carefully crafted handshake message, to cause OpenSSL to fail
2653 to free up to 64k of memory causing a memory leak. This could be
2654 exploited in a Denial Of Service attack. This issue affects OpenSSL
2655 1.0.1 server implementations for both SSL/TLS and DTLS regardless of
2656 whether SRTP is used or configured. Implementations of OpenSSL that
2657 have been compiled with OPENSSL_NO_SRTP defined are not affected.
2659 The fix was developed by the OpenSSL team.
2663 *) Session Ticket Memory Leak.
2665 When an OpenSSL SSL/TLS/DTLS server receives a session ticket the
2666 integrity of that ticket is first verified. In the event of a session
2667 ticket integrity check failing, OpenSSL will fail to free memory
2668 causing a memory leak. By sending a large number of invalid session
2669 tickets an attacker could exploit this issue in a Denial Of Service
2674 *) Build option no-ssl3 is incomplete.
2676 When OpenSSL is configured with "no-ssl3" as a build option, servers
2677 could accept and complete a SSL 3.0 handshake, and clients could be
2678 configured to send them.
2680 [Akamai and the OpenSSL team]
2682 *) Add support for TLS_FALLBACK_SCSV.
2683 Client applications doing fallback retries should call
2684 SSL_set_mode(s, SSL_MODE_SEND_FALLBACK_SCSV).
2686 [Adam Langley, Bodo Moeller]
2688 *) Add additional DigestInfo checks.
2690 Re-encode DigestInto in DER and check against the original when
2691 verifying RSA signature: this will reject any improperly encoded
2692 DigestInfo structures.
2694 Note: this is a precautionary measure and no attacks are currently known.
2698 Changes between 1.0.1h and 1.0.1i [6 Aug 2014]
2700 *) Fix SRP buffer overrun vulnerability. Invalid parameters passed to the
2701 SRP code can be overrun an internal buffer. Add sanity check that
2702 g, A, B < N to SRP code.
2704 Thanks to Sean Devlin and Watson Ladd of Cryptography Services, NCC
2705 Group for discovering this issue.
2709 *) A flaw in the OpenSSL SSL/TLS server code causes the server to negotiate
2710 TLS 1.0 instead of higher protocol versions when the ClientHello message
2711 is badly fragmented. This allows a man-in-the-middle attacker to force a
2712 downgrade to TLS 1.0 even if both the server and the client support a
2713 higher protocol version, by modifying the client's TLS records.
2715 Thanks to David Benjamin and Adam Langley (Google) for discovering and
2716 researching this issue.
2720 *) OpenSSL DTLS clients enabling anonymous (EC)DH ciphersuites are subject
2721 to a denial of service attack. A malicious server can crash the client
2722 with a null pointer dereference (read) by specifying an anonymous (EC)DH
2723 ciphersuite and sending carefully crafted handshake messages.
2725 Thanks to Felix Gröbert (Google) for discovering and researching this
2730 *) By sending carefully crafted DTLS packets an attacker could cause openssl
2731 to leak memory. This can be exploited through a Denial of Service attack.
2732 Thanks to Adam Langley for discovering and researching this issue.
2736 *) An attacker can force openssl to consume large amounts of memory whilst
2737 processing DTLS handshake messages. This can be exploited through a
2738 Denial of Service attack.
2739 Thanks to Adam Langley for discovering and researching this issue.
2743 *) An attacker can force an error condition which causes openssl to crash
2744 whilst processing DTLS packets due to memory being freed twice. This
2745 can be exploited through a Denial of Service attack.
2746 Thanks to Adam Langley and Wan-Teh Chang for discovering and researching
2751 *) If a multithreaded client connects to a malicious server using a resumed
2752 session and the server sends an ec point format extension it could write
2753 up to 255 bytes to freed memory.
2755 Thanks to Gabor Tyukasz (LogMeIn Inc) for discovering and researching this
2760 *) A malicious server can crash an OpenSSL client with a null pointer
2761 dereference (read) by specifying an SRP ciphersuite even though it was not
2762 properly negotiated with the client. This can be exploited through a
2763 Denial of Service attack.
2765 Thanks to Joonas Kuorilehto and Riku Hietamäki (Codenomicon) for
2766 discovering and researching this issue.
2770 *) A flaw in OBJ_obj2txt may cause pretty printing functions such as
2771 X509_name_oneline, X509_name_print_ex et al. to leak some information
2772 from the stack. Applications may be affected if they echo pretty printing
2773 output to the attacker.
2775 Thanks to Ivan Fratric (Google) for discovering this issue.
2777 [Emilia Käsper, and Steve Henson]
2779 *) Fix ec_GFp_simple_points_make_affine (thus, EC_POINTs_mul etc.)
2780 for corner cases. (Certain input points at infinity could lead to
2781 bogus results, with non-infinity inputs mapped to infinity too.)
2784 Changes between 1.0.1g and 1.0.1h [5 Jun 2014]
2786 *) Fix for SSL/TLS MITM flaw. An attacker using a carefully crafted
2787 handshake can force the use of weak keying material in OpenSSL
2788 SSL/TLS clients and servers.
2790 Thanks to KIKUCHI Masashi (Lepidum Co. Ltd.) for discovering and
2791 researching this issue. (CVE-2014-0224)
2792 [KIKUCHI Masashi, Steve Henson]
2794 *) Fix DTLS recursion flaw. By sending an invalid DTLS handshake to an
2795 OpenSSL DTLS client the code can be made to recurse eventually crashing
2798 Thanks to Imre Rad (Search-Lab Ltd.) for discovering this issue.
2800 [Imre Rad, Steve Henson]
2802 *) Fix DTLS invalid fragment vulnerability. A buffer overrun attack can
2803 be triggered by sending invalid DTLS fragments to an OpenSSL DTLS
2804 client or server. This is potentially exploitable to run arbitrary
2805 code on a vulnerable client or server.
2807 Thanks to Jüri Aedla for reporting this issue. (CVE-2014-0195)
2808 [Jüri Aedla, Steve Henson]
2810 *) Fix bug in TLS code where clients enable anonymous ECDH ciphersuites
2811 are subject to a denial of service attack.
2813 Thanks to Felix Gröbert and Ivan Fratric at Google for discovering
2814 this issue. (CVE-2014-3470)
2815 [Felix Gröbert, Ivan Fratric, Steve Henson]
2817 *) Harmonize version and its documentation. -f flag is used to display
2819 [mancha <mancha1@zoho.com>]
2821 *) Fix eckey_priv_encode so it immediately returns an error upon a failure
2822 in i2d_ECPrivateKey.
2823 [mancha <mancha1@zoho.com>]
2825 *) Fix some double frees. These are not thought to be exploitable.
2826 [mancha <mancha1@zoho.com>]
2828 Changes between 1.0.1f and 1.0.1g [7 Apr 2014]
2830 *) A missing bounds check in the handling of the TLS heartbeat extension
2831 can be used to reveal up to 64k of memory to a connected client or
2834 Thanks for Neel Mehta of Google Security for discovering this bug and to
2835 Adam Langley <agl@chromium.org> and Bodo Moeller <bmoeller@acm.org> for
2836 preparing the fix (CVE-2014-0160)
2837 [Adam Langley, Bodo Moeller]
2839 *) Fix for the attack described in the paper "Recovering OpenSSL
2840 ECDSA Nonces Using the FLUSH+RELOAD Cache Side-channel Attack"
2841 by Yuval Yarom and Naomi Benger. Details can be obtained from:
2842 http://eprint.iacr.org/2014/140
2844 Thanks to Yuval Yarom and Naomi Benger for discovering this
2845 flaw and to Yuval Yarom for supplying a fix (CVE-2014-0076)
2846 [Yuval Yarom and Naomi Benger]
2848 *) TLS pad extension: draft-agl-tls-padding-03
2850 Workaround for the "TLS hang bug" (see FAQ and PR#2771): if the
2851 TLS client Hello record length value would otherwise be > 255 and
2852 less that 512 pad with a dummy extension containing zeroes so it
2853 is at least 512 bytes long.
2855 [Adam Langley, Steve Henson]
2857 Changes between 1.0.1e and 1.0.1f [6 Jan 2014]
2859 *) Fix for TLS record tampering bug. A carefully crafted invalid
2860 handshake could crash OpenSSL with a NULL pointer exception.
2861 Thanks to Anton Johansson for reporting this issues.
2864 *) Keep original DTLS digest and encryption contexts in retransmission
2865 structures so we can use the previous session parameters if they need
2866 to be resent. (CVE-2013-6450)
2869 *) Add option SSL_OP_SAFARI_ECDHE_ECDSA_BUG (part of SSL_OP_ALL) which
2870 avoids preferring ECDHE-ECDSA ciphers when the client appears to be
2871 Safari on OS X. Safari on OS X 10.8..10.8.3 advertises support for
2872 several ECDHE-ECDSA ciphers, but fails to negotiate them. The bug
2873 is fixed in OS X 10.8.4, but Apple have ruled out both hot fixing
2874 10.8..10.8.3 and forcing users to upgrade to 10.8.4 or newer.
2875 [Rob Stradling, Adam Langley]
2877 Changes between 1.0.1d and 1.0.1e [11 Feb 2013]
2879 *) Correct fix for CVE-2013-0169. The original didn't work on AES-NI
2880 supporting platforms or when small records were transferred.
2881 [Andy Polyakov, Steve Henson]
2883 Changes between 1.0.1c and 1.0.1d [5 Feb 2013]
2885 *) Make the decoding of SSLv3, TLS and DTLS CBC records constant time.
2887 This addresses the flaw in CBC record processing discovered by
2888 Nadhem Alfardan and Kenny Paterson. Details of this attack can be found
2889 at: http://www.isg.rhul.ac.uk/tls/
2891 Thanks go to Nadhem Alfardan and Kenny Paterson of the Information
2892 Security Group at Royal Holloway, University of London
2893 (www.isg.rhul.ac.uk) for discovering this flaw and Adam Langley and
2894 Emilia Käsper for the initial patch.
2896 [Emilia Käsper, Adam Langley, Ben Laurie, Andy Polyakov, Steve Henson]
2898 *) Fix flaw in AESNI handling of TLS 1.2 and 1.1 records for CBC mode
2899 ciphersuites which can be exploited in a denial of service attack.
2900 Thanks go to and to Adam Langley <agl@chromium.org> for discovering
2901 and detecting this bug and to Wolfgang Ettlinger
2902 <wolfgang.ettlinger@gmail.com> for independently discovering this issue.
2906 *) Return an error when checking OCSP signatures when key is NULL.
2907 This fixes a DoS attack. (CVE-2013-0166)
2910 *) Make openssl verify return errors.
2911 [Chris Palmer <palmer@google.com> and Ben Laurie]
2913 *) Call OCSP Stapling callback after ciphersuite has been chosen, so
2914 the right response is stapled. Also change SSL_get_certificate()
2915 so it returns the certificate actually sent.
2916 See http://rt.openssl.org/Ticket/Display.html?id=2836.
2917 [Rob Stradling <rob.stradling@comodo.com>]
2919 *) Fix possible deadlock when decoding public keys.
2922 *) Don't use TLS 1.0 record version number in initial client hello
2926 Changes between 1.0.1b and 1.0.1c [10 May 2012]
2928 *) Sanity check record length before skipping explicit IV in TLS
2929 1.2, 1.1 and DTLS to fix DoS attack.
2931 Thanks to Codenomicon for discovering this issue using Fuzz-o-Matic
2932 fuzzing as a service testing platform.
2936 *) Initialise tkeylen properly when encrypting CMS messages.
2937 Thanks to Solar Designer of Openwall for reporting this issue.
2940 *) In FIPS mode don't try to use composite ciphers as they are not
2944 Changes between 1.0.1a and 1.0.1b [26 Apr 2012]
2946 *) OpenSSL 1.0.0 sets SSL_OP_ALL to 0x80000FFFL and OpenSSL 1.0.1 and
2947 1.0.1a set SSL_OP_NO_TLSv1_1 to 0x00000400L which would unfortunately
2948 mean any application compiled against OpenSSL 1.0.0 headers setting
2949 SSL_OP_ALL would also set SSL_OP_NO_TLSv1_1, unintentionally disabling
2950 TLS 1.1 also. Fix this by changing the value of SSL_OP_NO_TLSv1_1 to
2951 0x10000000L Any application which was previously compiled against
2952 OpenSSL 1.0.1 or 1.0.1a headers and which cares about SSL_OP_NO_TLSv1_1
2953 will need to be recompiled as a result. Letting be results in
2954 inability to disable specifically TLS 1.1 and in client context,
2955 in unlike event, limit maximum offered version to TLS 1.0 [see below].
2958 *) In order to ensure interoperability SSL_OP_NO_protocolX does not
2959 disable just protocol X, but all protocols above X *if* there are
2960 protocols *below* X still enabled. In more practical terms it means
2961 that if application wants to disable TLS1.0 in favor of TLS1.1 and
2962 above, it's not sufficient to pass SSL_OP_NO_TLSv1, one has to pass
2963 SSL_OP_NO_TLSv1|SSL_OP_NO_SSLv3|SSL_OP_NO_SSLv2. This applies to
2967 Changes between 1.0.1 and 1.0.1a [19 Apr 2012]
2969 *) Check for potentially exploitable overflows in asn1_d2i_read_bio
2970 BUF_mem_grow and BUF_mem_grow_clean. Refuse attempts to shrink buffer
2971 in CRYPTO_realloc_clean.
2973 Thanks to Tavis Ormandy, Google Security Team, for discovering this
2974 issue and to Adam Langley <agl@chromium.org> for fixing it.
2976 [Adam Langley (Google), Tavis Ormandy, Google Security Team]
2978 *) Don't allow TLS 1.2 SHA-256 ciphersuites in TLS 1.0, 1.1 connections.
2981 *) Workarounds for some broken servers that "hang" if a client hello
2982 record length exceeds 255 bytes.
2984 1. Do not use record version number > TLS 1.0 in initial client
2985 hello: some (but not all) hanging servers will now work.
2986 2. If we set OPENSSL_MAX_TLS1_2_CIPHER_LENGTH this will truncate
2987 the number of ciphers sent in the client hello. This should be
2988 set to an even number, such as 50, for example by passing:
2989 -DOPENSSL_MAX_TLS1_2_CIPHER_LENGTH=50 to config or Configure.
2990 Most broken servers should now work.
2991 3. If all else fails setting OPENSSL_NO_TLS1_2_CLIENT will disable
2992 TLS 1.2 client support entirely.
2995 *) Fix SEGV in Vector Permutation AES module observed in OpenSSH.
2998 Changes between 1.0.0h and 1.0.1 [14 Mar 2012]
3000 *) Add compatibility with old MDC2 signatures which use an ASN1 OCTET
3001 STRING form instead of a DigestInfo.
3004 *) The format used for MDC2 RSA signatures is inconsistent between EVP
3005 and the RSA_sign/RSA_verify functions. This was made more apparent when
3006 OpenSSL used RSA_sign/RSA_verify for some RSA signatures in particular
3007 those which went through EVP_PKEY_METHOD in 1.0.0 and later. Detect
3008 the correct format in RSA_verify so both forms transparently work.
3011 *) Some servers which support TLS 1.0 can choke if we initially indicate
3012 support for TLS 1.2 and later renegotiate using TLS 1.0 in the RSA
3013 encrypted premaster secret. As a workaround use the maximum permitted
3014 client version in client hello, this should keep such servers happy
3015 and still work with previous versions of OpenSSL.
3018 *) Add support for TLS/DTLS heartbeats.
3019 [Robin Seggelmann <seggelmann@fh-muenster.de>]
3021 *) Add support for SCTP.
3022 [Robin Seggelmann <seggelmann@fh-muenster.de>]
3024 *) Improved PRNG seeding for VOS.
3025 [Paul Green <Paul.Green@stratus.com>]
3027 *) Extensive assembler packs updates, most notably:
3029 - x86[_64]: AES-NI, PCLMULQDQ, RDRAND support;
3030 - x86[_64]: SSSE3 support (SHA1, vector-permutation AES);
3031 - x86_64: bit-sliced AES implementation;
3032 - ARM: NEON support, contemporary platforms optimizations;
3033 - s390x: z196 support;
3034 - *: GHASH and GF(2^m) multiplication implementations;
3038 *) Make TLS-SRP code conformant with RFC 5054 API cleanup
3039 (removal of unnecessary code)
3040 [Peter Sylvester <peter.sylvester@edelweb.fr>]
3042 *) Add TLS key material exporter from RFC 5705.
3045 *) Add DTLS-SRTP negotiation from RFC 5764.
3048 *) Add Next Protocol Negotiation,
3049 http://tools.ietf.org/html/draft-agl-tls-nextprotoneg-00. Can be
3050 disabled with a no-npn flag to config or Configure. Code donated
3052 [Adam Langley <agl@google.com> and Ben Laurie]
3054 *) Add optional 64-bit optimized implementations of elliptic curves NIST-P224,
3055 NIST-P256, NIST-P521, with constant-time single point multiplication on
3056 typical inputs. Compiler support for the nonstandard type __uint128_t is
3057 required to use this (present in gcc 4.4 and later, for 64-bit builds).
3058 Code made available under Apache License version 2.0.
3060 Specify "enable-ec_nistp_64_gcc_128" on the Configure (or config) command
3061 line to include this in your build of OpenSSL, and run "make depend" (or
3062 "make update"). This enables the following EC_METHODs:
3064 EC_GFp_nistp224_method()
3065 EC_GFp_nistp256_method()
3066 EC_GFp_nistp521_method()
3068 EC_GROUP_new_by_curve_name() will automatically use these (while
3069 EC_GROUP_new_curve_GFp() currently prefers the more flexible
3071 [Emilia Käsper, Adam Langley, Bodo Moeller (Google)]
3073 *) Use type ossl_ssize_t instad of ssize_t which isn't available on
3074 all platforms. Move ssize_t definition from e_os.h to the public
3075 header file e_os2.h as it now appears in public header file cms.h
3078 *) New -sigopt option to the ca, req and x509 utilities. Additional
3079 signature parameters can be passed using this option and in
3083 *) Add RSA PSS signing function. This will generate and set the
3084 appropriate AlgorithmIdentifiers for PSS based on those in the
3085 corresponding EVP_MD_CTX structure. No application support yet.
3088 *) Support for companion algorithm specific ASN1 signing routines.
3089 New function ASN1_item_sign_ctx() signs a pre-initialised
3090 EVP_MD_CTX structure and sets AlgorithmIdentifiers based on
3091 the appropriate parameters.
3094 *) Add new algorithm specific ASN1 verification initialisation function
3095 to EVP_PKEY_ASN1_METHOD: this is not in EVP_PKEY_METHOD since the ASN1
3096 handling will be the same no matter what EVP_PKEY_METHOD is used.
3097 Add a PSS handler to support verification of PSS signatures: checked
3098 against a number of sample certificates.
3101 *) Add signature printing for PSS. Add PSS OIDs.
3102 [Steve Henson, Martin Kaiser <lists@kaiser.cx>]
3104 *) Add algorithm specific signature printing. An individual ASN1 method
3105 can now print out signatures instead of the standard hex dump.
3107 More complex signatures (e.g. PSS) can print out more meaningful
3108 information. Include DSA version that prints out the signature
3112 *) Password based recipient info support for CMS library: implementing
3116 *) Split password based encryption into PBES2 and PBKDF2 functions. This
3117 neatly separates the code into cipher and PBE sections and is required
3118 for some algorithms that split PBES2 into separate pieces (such as
3119 password based CMS).
3122 *) Session-handling fixes:
3123 - Fix handling of connections that are resuming with a session ID,
3124 but also support Session Tickets.
3125 - Fix a bug that suppressed issuing of a new ticket if the client
3126 presented a ticket with an expired session.
3127 - Try to set the ticket lifetime hint to something reasonable.
3128 - Make tickets shorter by excluding irrelevant information.
3129 - On the client side, don't ignore renewed tickets.
3130 [Adam Langley, Bodo Moeller (Google)]
3132 *) Fix PSK session representation.
3135 *) Add RC4-MD5 and AESNI-SHA1 "stitched" implementations.
3137 This work was sponsored by Intel.
3140 *) Add GCM support to TLS library. Some custom code is needed to split
3141 the IV between the fixed (from PRF) and explicit (from TLS record)
3142 portions. This adds all GCM ciphersuites supported by RFC5288 and
3143 RFC5289. Generalise some AES* cipherstrings to include GCM and
3144 add a special AESGCM string for GCM only.
3147 *) Expand range of ctrls for AES GCM. Permit setting invocation
3148 field on decrypt and retrieval of invocation field only on encrypt.
3151 *) Add HMAC ECC ciphersuites from RFC5289. Include SHA384 PRF support.
3152 As required by RFC5289 these ciphersuites cannot be used if for
3153 versions of TLS earlier than 1.2.
3156 *) For FIPS capable OpenSSL interpret a NULL default public key method
3157 as unset and return the appropriate default but do *not* set the default.
3158 This means we can return the appropriate method in applications that
3159 switch between FIPS and non-FIPS modes.
3162 *) Redirect HMAC and CMAC operations to FIPS module in FIPS mode. If an
3163 ENGINE is used then we cannot handle that in the FIPS module so we
3164 keep original code iff non-FIPS operations are allowed.
3167 *) Add -attime option to openssl utilities.
3168 [Peter Eckersley <pde@eff.org>, Ben Laurie and Steve Henson]
3170 *) Redirect DSA and DH operations to FIPS module in FIPS mode.
3173 *) Redirect ECDSA and ECDH operations to FIPS module in FIPS mode. Also use
3174 FIPS EC methods unconditionally for now.
3177 *) New build option no-ec2m to disable characteristic 2 code.
3180 *) Backport libcrypto audit of return value checking from 1.1.0-dev; not
3181 all cases can be covered as some introduce binary incompatibilities.
3184 *) Redirect RSA operations to FIPS module including keygen,
3185 encrypt, decrypt, sign and verify. Block use of non FIPS RSA methods.
3188 *) Add similar low level API blocking to ciphers.
3191 *) Low level digest APIs are not approved in FIPS mode: any attempt
3192 to use these will cause a fatal error. Applications that *really* want
3193 to use them can use the private_* version instead.
3196 *) Redirect cipher operations to FIPS module for FIPS builds.
3199 *) Redirect digest operations to FIPS module for FIPS builds.
3202 *) Update build system to add "fips" flag which will link in fipscanister.o
3203 for static and shared library builds embedding a signature if needed.
3206 *) Output TLS supported curves in preference order instead of numerical
3207 order. This is currently hardcoded for the highest order curves first.
3208 This should be configurable so applications can judge speed vs strength.
3211 *) Add TLS v1.2 server support for client authentication.
3214 *) Add support for FIPS mode in ssl library: disable SSLv3, non-FIPS ciphers
3218 *) Functions FIPS_mode_set() and FIPS_mode() which call the underlying
3219 FIPS modules versions.
3222 *) Add TLS v1.2 client side support for client authentication. Keep cache
3223 of handshake records longer as we don't know the hash algorithm to use
3224 until after the certificate request message is received.
3227 *) Initial TLS v1.2 client support. Add a default signature algorithms
3228 extension including all the algorithms we support. Parse new signature
3229 format in client key exchange. Relax some ECC signing restrictions for
3230 TLS v1.2 as indicated in RFC5246.
3233 *) Add server support for TLS v1.2 signature algorithms extension. Switch
3234 to new signature format when needed using client digest preference.
3235 All server ciphersuites should now work correctly in TLS v1.2. No client
3236 support yet and no support for client certificates.
3239 *) Initial TLS v1.2 support. Add new SHA256 digest to ssl code, switch
3240 to SHA256 for PRF when using TLS v1.2 and later. Add new SHA256 based
3241 ciphersuites. At present only RSA key exchange ciphersuites work with
3242 TLS v1.2. Add new option for TLS v1.2 replacing the old and obsolete
3243 SSL_OP_PKCS1_CHECK flags with SSL_OP_NO_TLSv1_2. New TLSv1.2 methods
3244 and version checking.
3247 *) New option OPENSSL_NO_SSL_INTERN. If an application can be compiled
3248 with this defined it will not be affected by any changes to ssl internal
3249 structures. Add several utility functions to allow openssl application
3250 to work with OPENSSL_NO_SSL_INTERN defined.
3254 [Tom Wu <tjw@cs.stanford.edu> and Ben Laurie]
3256 *) Add functions to copy EVP_PKEY_METHOD and retrieve flags and id.
3259 *) Permit abbreviated handshakes when renegotiating using the function
3260 SSL_renegotiate_abbreviated().
3261 [Robin Seggelmann <seggelmann@fh-muenster.de>]
3263 *) Add call to ENGINE_register_all_complete() to
3264 ENGINE_load_builtin_engines(), so some implementations get used
3265 automatically instead of needing explicit application support.
3268 *) Add support for TLS key exporter as described in RFC5705.
3269 [Robin Seggelmann <seggelmann@fh-muenster.de>, Steve Henson]
3271 *) Initial TLSv1.1 support. Since TLSv1.1 is very similar to TLS v1.0 only
3272 a few changes are required:
3274 Add SSL_OP_NO_TLSv1_1 flag.
3275 Add TLSv1_1 methods.
3276 Update version checking logic to handle version 1.1.
3277 Add explicit IV handling (ported from DTLS code).
3278 Add command line options to s_client/s_server.
3281 Changes between 1.0.0g and 1.0.0h [12 Mar 2012]
3283 *) Fix MMA (Bleichenbacher's attack on PKCS #1 v1.5 RSA padding) weakness
3284 in CMS and PKCS7 code. When RSA decryption fails use a random key for
3285 content decryption and always return the same error. Note: this attack
3286 needs on average 2^20 messages so it only affects automated senders. The
3287 old behaviour can be re-enabled in the CMS code by setting the
3288 CMS_DEBUG_DECRYPT flag: this is useful for debugging and testing where
3289 an MMA defence is not necessary.
3290 Thanks to Ivan Nestlerode <inestlerode@us.ibm.com> for discovering
3291 this issue. (CVE-2012-0884)
3294 *) Fix CVE-2011-4619: make sure we really are receiving a
3295 client hello before rejecting multiple SGC restarts. Thanks to
3296 Ivan Nestlerode <inestlerode@us.ibm.com> for discovering this bug.
3299 Changes between 1.0.0f and 1.0.0g [18 Jan 2012]
3301 *) Fix for DTLS DoS issue introduced by fix for CVE-2011-4109.
3302 Thanks to Antonio Martin, Enterprise Secure Access Research and
3303 Development, Cisco Systems, Inc. for discovering this bug and
3304 preparing a fix. (CVE-2012-0050)
3307 Changes between 1.0.0e and 1.0.0f [4 Jan 2012]
3309 *) Nadhem Alfardan and Kenny Paterson have discovered an extension
3310 of the Vaudenay padding oracle attack on CBC mode encryption
3311 which enables an efficient plaintext recovery attack against
3312 the OpenSSL implementation of DTLS. Their attack exploits timing
3313 differences arising during decryption processing. A research
3314 paper describing this attack can be found at:
3315 http://www.isg.rhul.ac.uk/~kp/dtls.pdf
3316 Thanks go to Nadhem Alfardan and Kenny Paterson of the Information
3317 Security Group at Royal Holloway, University of London
3318 (www.isg.rhul.ac.uk) for discovering this flaw and to Robin Seggelmann
3319 <seggelmann@fh-muenster.de> and Michael Tuexen <tuexen@fh-muenster.de>
3320 for preparing the fix. (CVE-2011-4108)
3321 [Robin Seggelmann, Michael Tuexen]
3323 *) Clear bytes used for block padding of SSL 3.0 records.
3325 [Adam Langley (Google)]
3327 *) Only allow one SGC handshake restart for SSL/TLS. Thanks to George
3328 Kadianakis <desnacked@gmail.com> for discovering this issue and
3329 Adam Langley for preparing the fix. (CVE-2011-4619)
3330 [Adam Langley (Google)]
3332 *) Check parameters are not NULL in GOST ENGINE. (CVE-2012-0027)
3333 [Andrey Kulikov <amdeich@gmail.com>]
3335 *) Prevent malformed RFC3779 data triggering an assertion failure.
3336 Thanks to Andrew Chi, BBN Technologies, for discovering the flaw
3337 and Rob Austein <sra@hactrn.net> for fixing it. (CVE-2011-4577)
3338 [Rob Austein <sra@hactrn.net>]
3340 *) Improved PRNG seeding for VOS.
3341 [Paul Green <Paul.Green@stratus.com>]
3343 *) Fix ssl_ciph.c set-up race.
3344 [Adam Langley (Google)]
3346 *) Fix spurious failures in ecdsatest.c.
3347 [Emilia Käsper (Google)]
3349 *) Fix the BIO_f_buffer() implementation (which was mixing different
3350 interpretations of the '..._len' fields).
3351 [Adam Langley (Google)]
3353 *) Fix handling of BN_BLINDING: now BN_BLINDING_invert_ex (rather than
3354 BN_BLINDING_invert_ex) calls BN_BLINDING_update, ensuring that concurrent
3355 threads won't reuse the same blinding coefficients.
3357 This also avoids the need to obtain the CRYPTO_LOCK_RSA_BLINDING
3358 lock to call BN_BLINDING_invert_ex, and avoids one use of
3359 BN_BLINDING_update for each BN_BLINDING structure (previously,
3360 the last update always remained unused).
3361 [Emilia Käsper (Google)]
3363 *) In ssl3_clear, preserve s3->init_extra along with s3->rbuf.
3364 [Bob Buckholz (Google)]
3366 Changes between 1.0.0d and 1.0.0e [6 Sep 2011]
3368 *) Fix bug where CRLs with nextUpdate in the past are sometimes accepted
3369 by initialising X509_STORE_CTX properly. (CVE-2011-3207)
3370 [Kaspar Brand <ossl@velox.ch>]
3372 *) Fix SSL memory handling for (EC)DH ciphersuites, in particular
3373 for multi-threaded use of ECDH. (CVE-2011-3210)
3374 [Adam Langley (Google)]
3376 *) Fix x509_name_ex_d2i memory leak on bad inputs.
3379 *) Remove hard coded ecdsaWithSHA1 signature tests in ssl code and check
3380 signature public key algorithm by using OID xref utilities instead.
3381 Before this you could only use some ECC ciphersuites with SHA1 only.
3384 *) Add protection against ECDSA timing attacks as mentioned in the paper
3385 by Billy Bob Brumley and Nicola Tuveri, see:
3387 http://eprint.iacr.org/2011/232.pdf
3389 [Billy Bob Brumley and Nicola Tuveri]
3391 Changes between 1.0.0c and 1.0.0d [8 Feb 2011]
3393 *) Fix parsing of OCSP stapling ClientHello extension. CVE-2011-0014
3394 [Neel Mehta, Adam Langley, Bodo Moeller (Google)]
3396 *) Fix bug in string printing code: if *any* escaping is enabled we must
3397 escape the escape character (backslash) or the resulting string is
3401 Changes between 1.0.0b and 1.0.0c [2 Dec 2010]
3403 *) Disable code workaround for ancient and obsolete Netscape browsers
3404 and servers: an attacker can use it in a ciphersuite downgrade attack.
3405 Thanks to Martin Rex for discovering this bug. CVE-2010-4180
3408 *) Fixed J-PAKE implementation error, originally discovered by
3409 Sebastien Martini, further info and confirmation from Stefan
3410 Arentz and Feng Hao. Note that this fix is a security fix. CVE-2010-4252
3413 Changes between 1.0.0a and 1.0.0b [16 Nov 2010]
3415 *) Fix extension code to avoid race conditions which can result in a buffer
3416 overrun vulnerability: resumed sessions must not be modified as they can
3417 be shared by multiple threads. CVE-2010-3864
3420 *) Fix WIN32 build system to correctly link an ENGINE directory into
3424 Changes between 1.0.0 and 1.0.0a [01 Jun 2010]
3426 *) Check return value of int_rsa_verify in pkey_rsa_verifyrecover
3428 [Steve Henson, Peter-Michael Hager <hager@dortmund.net>]
3430 Changes between 0.9.8n and 1.0.0 [29 Mar 2010]
3432 *) Add "missing" function EVP_CIPHER_CTX_copy(). This copies a cipher
3433 context. The operation can be customised via the ctrl mechanism in
3434 case ENGINEs want to include additional functionality.
3437 *) Tolerate yet another broken PKCS#8 key format: private key value negative.
3440 *) Add new -subject_hash_old and -issuer_hash_old options to x509 utility to
3441 output hashes compatible with older versions of OpenSSL.
3442 [Willy Weisz <weisz@vcpc.univie.ac.at>]
3444 *) Fix compression algorithm handling: if resuming a session use the
3445 compression algorithm of the resumed session instead of determining
3446 it from client hello again. Don't allow server to change algorithm.
3449 *) Add load_crls() function to apps tidying load_certs() too. Add option
3450 to verify utility to allow additional CRLs to be included.
3453 *) Update OCSP request code to permit adding custom headers to the request:
3454 some responders need this.
3457 *) The function EVP_PKEY_sign() returns <=0 on error: check return code
3459 [Julia Lawall <julia@diku.dk>]
3461 *) Update verify callback code in apps/s_cb.c and apps/verify.c, it
3462 needlessly dereferenced structures, used obsolete functions and
3463 didn't handle all updated verify codes correctly.
3466 *) Disable MD2 in the default configuration.
3469 *) In BIO_pop() and BIO_push() use the ctrl argument (which was NULL) to
3470 indicate the initial BIO being pushed or popped. This makes it possible
3471 to determine whether the BIO is the one explicitly called or as a result
3472 of the ctrl being passed down the chain. Fix BIO_pop() and SSL BIOs so
3473 it handles reference counts correctly and doesn't zero out the I/O bio
3474 when it is not being explicitly popped. WARNING: applications which
3475 included workarounds for the old buggy behaviour will need to be modified
3476 or they could free up already freed BIOs.
3479 *) Extend the uni2asc/asc2uni => OPENSSL_uni2asc/OPENSSL_asc2uni
3480 renaming to all platforms (within the 0.9.8 branch, this was
3481 done conditionally on Netware platforms to avoid a name clash).
3482 [Guenter <lists@gknw.net>]
3484 *) Add ECDHE and PSK support to DTLS.
3485 [Michael Tuexen <tuexen@fh-muenster.de>]
3487 *) Add CHECKED_STACK_OF macro to safestack.h, otherwise safestack can't
3491 *) Add "missing" function EVP_MD_flags() (without this the only way to
3492 retrieve a digest flags is by accessing the structure directly. Update
3493 EVP_MD_do_all*() and EVP_CIPHER_do_all*() to include the name a digest
3494 or cipher is registered as in the "from" argument. Print out all
3495 registered digests in the dgst usage message instead of manually
3496 attempting to work them out.
3499 *) If no SSLv2 ciphers are used don't use an SSLv2 compatible client hello:
3500 this allows the use of compression and extensions. Change default cipher
3501 string to remove SSLv2 ciphersuites. This effectively avoids ancient SSLv2
3502 by default unless an application cipher string requests it.
3505 *) Alter match criteria in PKCS12_parse(). It used to try to use local
3506 key ids to find matching certificates and keys but some PKCS#12 files
3507 don't follow the (somewhat unwritten) rules and this strategy fails.
3508 Now just gather all certificates together and the first private key
3509 then look for the first certificate that matches the key.
3512 *) Support use of registered digest and cipher names for dgst and cipher
3513 commands instead of having to add each one as a special case. So now
3520 openssl dgst -sha256 foo
3522 and this works for ENGINE based algorithms too.
3526 *) Update Gost ENGINE to support parameter files.
3527 [Victor B. Wagner <vitus@cryptocom.ru>]
3529 *) Support GeneralizedTime in ca utility.
3530 [Oliver Martin <oliver@volatilevoid.net>, Steve Henson]
3532 *) Enhance the hash format used for certificate directory links. The new
3533 form uses the canonical encoding (meaning equivalent names will work
3534 even if they aren't identical) and uses SHA1 instead of MD5. This form
3535 is incompatible with the older format and as a result c_rehash should
3536 be used to rebuild symbolic links.
3539 *) Make PKCS#8 the default write format for private keys, replacing the
3540 traditional format. This form is standardised, more secure and doesn't
3541 include an implicit MD5 dependency.
3544 *) Add a $gcc_devteam_warn option to Configure. The idea is that any code
3545 committed to OpenSSL should pass this lot as a minimum.
3548 *) Add session ticket override functionality for use by EAP-FAST.
3549 [Jouni Malinen <j@w1.fi>]
3551 *) Modify HMAC functions to return a value. Since these can be implemented
3552 in an ENGINE errors can occur.
3555 *) Type-checked OBJ_bsearch_ex.
3558 *) Type-checked OBJ_bsearch. Also some constification necessitated
3559 by type-checking. Still to come: TXT_DB, bsearch(?),
3560 OBJ_bsearch_ex, qsort, CRYPTO_EX_DATA, ASN1_VALUE, ASN1_STRING,
3564 *) New function OPENSSL_gmtime_adj() to add a specific number of days and
3565 seconds to a tm structure directly, instead of going through OS
3566 specific date routines. This avoids any issues with OS routines such
3567 as the year 2038 bug. New *_adj() functions for ASN1 time structures
3568 and X509_time_adj_ex() to cover the extended range. The existing
3569 X509_time_adj() is still usable and will no longer have any date issues.
3572 *) Delta CRL support. New use deltas option which will attempt to locate
3573 and search any appropriate delta CRLs available.
3575 This work was sponsored by Google.
3578 *) Support for CRLs partitioned by reason code. Reorganise CRL processing
3579 code and add additional score elements. Validate alternate CRL paths
3580 as part of the CRL checking and indicate a new error "CRL path validation
3581 error" in this case. Applications wanting additional details can use
3582 the verify callback and check the new "parent" field. If this is not
3583 NULL CRL path validation is taking place. Existing applications won't
3584 see this because it requires extended CRL support which is off by
3587 This work was sponsored by Google.
3590 *) Support for freshest CRL extension.
3592 This work was sponsored by Google.
3595 *) Initial indirect CRL support. Currently only supported in the CRLs
3596 passed directly and not via lookup. Process certificate issuer
3597 CRL entry extension and lookup CRL entries by bother issuer name
3598 and serial number. Check and process CRL issuer entry in IDP extension.
3600 This work was sponsored by Google.
3603 *) Add support for distinct certificate and CRL paths. The CRL issuer
3604 certificate is validated separately in this case. Only enabled if
3605 an extended CRL support flag is set: this flag will enable additional
3606 CRL functionality in future.
3608 This work was sponsored by Google.
3611 *) Add support for policy mappings extension.
3613 This work was sponsored by Google.
3616 *) Fixes to pathlength constraint, self issued certificate handling,
3617 policy processing to align with RFC3280 and PKITS tests.
3619 This work was sponsored by Google.
3622 *) Support for name constraints certificate extension. DN, email, DNS
3623 and URI types are currently supported.
3625 This work was sponsored by Google.
3628 *) To cater for systems that provide a pointer-based thread ID rather
3629 than numeric, deprecate the current numeric thread ID mechanism and
3630 replace it with a structure and associated callback type. This
3631 mechanism allows a numeric "hash" to be extracted from a thread ID in
3632 either case, and on platforms where pointers are larger than 'long',
3633 mixing is done to help ensure the numeric 'hash' is usable even if it
projects / openssl.git / blob