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.1 and 3.0.0 [xx XXX xxxx]
12 *) Removed include/openssl/opensslconf.h.in and replaced it with
13 include/openssl/configuration.h.in, which differs in not including
14 <openssl/macros.h>. A short header include/openssl/opensslconf.h
15 was added to include both.
17 This allows internal hacks where one might need to modify the set
18 of configured macros, for example this if deprecated symbols are
19 still supposed to be available internally:
21 #include <openssl/configuration.h>
23 #undef OPENSSL_NO_DEPRECATED
24 #define OPENSSL_SUPPRESS_DEPRECATED
26 #include <openssl/macros.h>
28 This should not be used by applications that use the exported
29 symbols, as that will lead to linking errors.
32 *) Fixed an an overflow bug in the x64_64 Montgomery squaring procedure
33 used in exponentiation with 512-bit moduli. No EC algorithms are
34 affected. Analysis suggests that attacks against 2-prime RSA1024,
35 3-prime RSA1536, and DSA1024 as a result of this defect would be very
36 difficult to perform and are not believed likely. Attacks against DH512
37 are considered just feasible. However, for an attack the target would
38 have to re-use the DH512 private key, which is not recommended anyway.
39 Also applications directly using the low level API BN_mod_exp may be
40 affected if they use BN_FLG_CONSTTIME.
44 *) Most memory-debug features have been deprecated, and the functionality
48 *) Introduced a new method type and API, OSSL_SERIALIZER, to
49 represent generic serializers. An implementation is expected to
50 be able to serialize an object associated with a given name (such
51 as an algorithm name for an asymmetric key) into forms given by
52 implementation properties.
54 Serializers are primarily used from inside libcrypto, through
55 calls to functions like EVP_PKEY_print_private(),
56 PEM_write_bio_PrivateKey() and similar.
58 Serializers are specified in such a way that they can be made to
59 directly handle the provider side portion of an object, if this
60 provider side part comes from the same provider as the serializer
61 itself, but can also be made to handle objects in parametrized
62 form (as an OSSL_PARAM array of data). This allows a provider to
63 offer generic serializers as a service for any other provider.
66 *) Added a .pragma directive to the syntax of configuration files, to
67 allow varying behavior in a supported and predictable manner.
68 Currently added pragma:
72 This allows dollar signs to be a keyword character unless it's
73 followed by a opening brace or parenthesis. This is useful for
74 platforms where dollar signs are commonly used in names, such as
75 volume names and system directory names on VMS.
78 *) Added functionality to create an EVP_PKEY from user data. This
79 is effectively the same as creating a RSA, DH or DSA object and
80 then assigning them to an EVP_PKEY, but directly using algorithm
81 agnostic EVP functions. A benefit is that this should be future
82 proof for public key algorithms to come.
85 *) Change the interpretation of the '--api' configuration option to
86 mean that this is a desired API compatibility level with no
87 further meaning. The previous interpretation, that this would
88 also mean to remove all deprecated symbols up to and including
89 the given version, no requires that 'no-deprecated' is also used
92 When building applications, the desired API compatibility level
93 can be set with the OPENSSL_API_COMPAT macro like before. For
94 API compatibility version below 3.0, the old style numerical
95 value is valid as before, such as -DOPENSSL_API_COMPAT=0x10100000L.
96 For version 3.0 and on, the value is expected to be the decimal
97 value calculated from the major and minor version like this:
99 MAJOR * 10000 + MINOR * 100
103 -DOPENSSL_API_COMPAT=30000 For 3.0
104 -DOPENSSL_API_COMPAT=30200 For 3.2
106 To hide declarations that are deprecated up to and including the
107 given API compatibility level, -DOPENSSL_NO_DEPRECATED must be
108 given when building the application as well.
111 *) Added the X509_LOOKUP_METHOD called X509_LOOKUP_store, to allow
112 access to certificate and CRL stores via URIs and OSSL_STORE
115 This adds the following functions:
118 X509_STORE_load_file()
119 X509_STORE_load_path()
120 X509_STORE_load_store()
121 SSL_add_store_cert_subjects_to_stack()
122 SSL_CTX_set_default_verify_store()
123 SSL_CTX_load_verify_file()
124 SSL_CTX_load_verify_dir()
125 SSL_CTX_load_verify_store()
127 Also, the following functions are now deprecated:
129 - X509_STORE_load_locations() (use X509_STORE_load_file(),
130 X509_STORE_load_path() or X509_STORE_load_store() instead)
131 - SSL_CTX_load_verify_locations() (use SSL_CTX_load_verify_file(),
132 SSL_CTX_load_verify_dir() or SSL_CTX_load_verify_store() instead)
135 *) Added a new method to gather entropy on VMS, based on SYS$GET_ENTROPY.
136 The presence of this system service is determined at run-time.
139 *) Added functionality to create an EVP_PKEY context based on data
140 for methods from providers. This takes an algorithm name and a
141 property query string and simply stores them, with the intent
142 that any operation that uses this context will use those strings
143 to fetch the needed methods implicitly, thereby making the port
144 of application written for pre-3.0 OpenSSL easier.
147 *) The undocumented function NCONF_WIN32() has been deprecated; for
148 conversion details see the HISTORY section of doc/man5/config.pod
151 *) Introduced the new functions EVP_DigestSignInit_ex() and
152 EVP_DigestVerifyInit_ex(). The macros EVP_DigestSignUpdate() and
153 EVP_DigestVerifyUpdate() have been converted to functions. See the man
154 pages for further details.
157 *) Most common options (such as -rand/-writerand, TLS version control, etc)
158 were refactored and point to newly-enhanced descriptions in openssl.pod
161 *) Over two thousand fixes were made to the documentation, including:
162 adding missing command flags, better style conformance, documentation
164 [Rich Salz, Richard Levitte]
166 *) s390x assembly pack: add hardware-support for P-256, P-384, P-521,
167 X25519, X448, Ed25519 and Ed448.
170 *) Print all values for a PKCS#12 attribute with 'openssl pkcs12', not just
174 *) Deprecated the public definition of ERR_STATE as well as the function
175 ERR_get_state(). This is done in preparation of making ERR_STATE an
179 *) Added ERR functionality to give callers access to the stored function
180 names that have replaced the older function code based functions.
182 New functions are ERR_get_error_func(), ERR_peek_error_func(),
183 ERR_peek_last_error_func(), ERR_get_error_data(), ERR_peek_error_data(),
184 ERR_peek_last_error_data(), ERR_get_error_all(), ERR_peek_error_all()
185 and ERR_peek_last_error_all().
187 These functions have become deprecated: ERR_get_error_line_data(),
188 ERR_peek_error_line_data(), ERR_peek_last_error_line_data() and
189 ERR_func_error_string().
192 *) Extended testing to be verbose for failing tests only. The make variables
193 VERBOSE_FAILURE or VF can be used to enable this:
195 $ make VF=1 test # Unix
196 $ mms /macro=(VF=1) test ! OpenVMS
197 $ nmake VF=1 test # Windows
201 *) For built-in EC curves, ensure an EC_GROUP built from the curve name is
202 used even when parsing explicit parameters, when loading a serialized key
203 or calling `EC_GROUP_new_from_ecpkparameters()`/
204 `EC_GROUP_new_from_ecparameters()`.
205 This prevents bypass of security hardening and performance gains,
206 especially for curves with specialized EC_METHODs.
207 By default, if a key encoded with explicit parameters is loaded and later
208 serialized, the output is still encoded with explicit parameters, even if
209 internally a "named" EC_GROUP is used for computation.
212 *) Compute ECC cofactors if not provided during EC_GROUP construction. Before
213 this change, EC_GROUP_set_generator would accept order and/or cofactor as
214 NULL. After this change, only the cofactor parameter can be NULL. It also
215 does some minimal sanity checks on the passed order.
219 *) Fixed a padding oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey.
220 An attack is simple, if the first CMS_recipientInfo is valid but the
221 second CMS_recipientInfo is chosen ciphertext. If the second
222 recipientInfo decodes to PKCS #1 v1.5 form plaintext, the correct
223 encryption key will be replaced by garbage, and the message cannot be
224 decoded, but if the RSA decryption fails, the correct encryption key is
225 used and the recipient will not notice the attack.
226 As a work around for this potential attack the length of the decrypted
227 key must be equal to the cipher default key length, in case the
228 certifiate is not given and all recipientInfo are tried out.
229 The old behaviour can be re-enabled in the CMS code by setting the
230 CMS_DEBUG_DECRYPT flag.
233 *) Early start up entropy quality from the DEVRANDOM seed source has been
234 improved for older Linux systems. The RAND subsystem will wait for
235 /dev/random to be producing output before seeding from /dev/urandom.
236 The seeded state is stored for future library initialisations using
237 a system global shared memory segment. The shared memory identifier
238 can be configured by defining OPENSSL_RAND_SEED_DEVRANDOM_SHM_ID to
239 the desired value. The default identifier is 114.
242 *) Revised BN_generate_prime_ex to not avoid factors 2..17863 in p-1
243 when primes for RSA keys are computed.
244 Since we previously always generated primes == 2 (mod 3) for RSA keys,
245 the 2-prime and 3-prime RSA modules were easy to distinguish, since
246 N = p*q = 1 (mod 3), but N = p*q*r = 2 (mod 3). Therefore fingerprinting
247 2-prime vs. 3-prime RSA keys was possible by computing N mod 3.
248 This avoids possible fingerprinting of newly generated RSA modules.
251 *) Correct the extended master secret constant on EBCDIC systems. Without this
252 fix TLS connections between an EBCDIC system and a non-EBCDIC system that
253 negotiate EMS will fail. Unfortunately this also means that TLS connections
254 between EBCDIC systems with this fix, and EBCDIC systems without this
255 fix will fail if they negotiate EMS.
258 *) Changed the library initialisation so that the config file is now loaded
259 by default. This was already the case for libssl. It now occurs for both
260 libcrypto and libssl. Use the OPENSSL_INIT_NO_LOAD_CONFIG option to
261 OPENSSL_init_crypto() to suppress automatic loading of a config file.
264 *) Introduced new error raising macros, ERR_raise() and ERR_raise_data(),
265 where the former acts as a replacement for ERR_put_error(), and the
266 latter replaces the combination ERR_put_error()+ERR_add_error_data().
267 ERR_raise_data() adds more flexibility by taking a format string and
268 an arbitrary number of arguments following it, to be processed with
272 *) Introduced a new function, OSSL_PROVIDER_available(), which can be used
273 to check if a named provider is loaded and available. When called, it
274 will also activate all fallback providers if such are still present.
277 *) Enforce a minimum DH modulus size of 512 bits.
280 *) Changed DH parameters to generate the order q subgroup instead of 2q.
281 Previously generated DH parameters are still accepted by DH_check
282 but DH_generate_key works around that by clearing bit 0 of the
283 private key for those. This avoids leaking bit 0 of the private key.
286 *) Significantly reduce secure memory usage by the randomness pools.
289 *) {CRYPTO,OPENSSL}_mem_debug_{push,pop} are now no-ops and have been
293 *) A new type, EVP_KEYEXCH, has been introduced to represent key exchange
294 algorithms. An implementation of a key exchange algorithm can be obtained
295 by using the function EVP_KEYEXCH_fetch(). An EVP_KEYEXCH algorithm can be
296 used in a call to EVP_PKEY_derive_init_ex() which works in a similar way to
297 the older EVP_PKEY_derive_init() function. See the man pages for the new
298 functions for further details.
301 *) The EVP_PKEY_CTX_set_dh_pad() macro has now been converted to a function.
304 *) Removed the function names from error messages and deprecated the
307 *) Removed NextStep support and the macro OPENSSL_UNISTD
310 *) Removed DES_check_key. Also removed OPENSSL_IMPLEMENT_GLOBAL,
311 OPENSSL_GLOBAL_REF, OPENSSL_DECLARE_GLOBAL.
312 Also removed "export var as function" capability; we do not export
313 variables, only functions.
316 *) RC5_32_set_key has been changed to return an int type, with 0 indicating
317 an error and 1 indicating success. In previous versions of OpenSSL this
318 was a void type. If a key was set longer than the maximum possible this
322 *) Support SM2 signing and verification schemes with X509 certificate.
325 *) Use SHA256 as the default digest for TS query in the ts app.
328 *) Change PBKDF2 to conform to SP800-132 instead of the older PKCS5 RFC2898.
329 This checks that the salt length is at least 128 bits, the derived key
330 length is at least 112 bits, and that the iteration count is at least 1000.
331 For backwards compatibility these checks are disabled by default in the
332 default provider, but are enabled by default in the fips provider.
333 To enable or disable these checks use the control
334 EVP_KDF_CTRL_SET_PBKDF2_PKCS5_MODE.
337 *) Default cipher lists/suites are now available via a function, the
338 #defines are deprecated.
341 *) Add target VC-WIN32-UWP, VC-WIN64A-UWP, VC-WIN32-ARM-UWP and
342 VC-WIN64-ARM-UWP in Windows OneCore target for making building libraries
343 for Windows Store apps easier. Also, the "no-uplink" option has been added.
346 *) Join the directories crypto/x509 and crypto/x509v3
349 *) Change the default RSA, DSA and DH size to 2048 bit instead of 1024.
350 This changes the size when using the genpkey app when no size is given. It
351 fixes an omission in earlier changes that changed all RSA, DSA and DH
352 generation apps to use 2048 bits by default.
355 *) Added command 'openssl kdf' that uses the EVP_KDF API.
358 *) Added command 'openssl mac' that uses the EVP_MAC API.
361 *) Added OPENSSL_info() to get diverse built-in OpenSSL data, such
362 as default directories. Also added the command 'openssl info'
363 for scripting purposes.
366 *) All of the low level AES functions have been deprecated including:
367 AES_options, AES_set_encrypt_key, AES_set_decrypt_key, AES_encrypt,
368 AES_decrypt, AES_ecb_encrypt, AES_cbc_encrypt, AES_cfb128_encrypt,
369 AES_cfb1_encrypt, AES_cfb8_encrypt, AES_ofb128_encrypt, AES_wrap_key and
371 Use of these low level functions has been informally discouraged for a long
372 time. Instead applications should use the high level EVP APIs, e.g.
373 EVP_EncryptInit_ex, EVP_EncryptUpdate, EVP_EncryptFinal_ex, and the
374 equivalently named decrypt functions.
376 The functions AES_ige_encrypt() and AES_bi_ige_encrypt() have also been
377 deprecated. These undocumented functions were never integrated into the EVP
378 layer and implement the AES Infinite Garble Extension (IGE) mode and AES
379 Bi-directional IGE mode. These modes were never formally standardised and
380 usage of these functions is believed to be very small. In particular
381 AES_bi_ige_encrypt() has a known bug. It accepts 2 AES keys, but only one
382 is ever used. The security implications are believed to be minimal, but
383 this issue was never fixed for backwards compatibility reasons. New code
384 should not use these modes.
387 *) Add prediction resistance to the DRBG reseeding process.
390 *) Limit the number of blocks in a data unit for AES-XTS to 2^20 as
391 mandated by IEEE Std 1619-2018.
394 *) Added newline escaping functionality to a filename when using openssl dgst.
395 This output format is to replicate the output format found in the '*sum'
396 checksum programs. This aims to preserve backward compatibility.
397 [Matt Eaton, Richard Levitte, and Paul Dale]
399 *) Removed the heartbeat message in DTLS feature, as it has very
400 little usage and doesn't seem to fulfill a valuable purpose.
401 The configuration option is now deprecated.
404 *) Changed the output of 'openssl {digestname} < file' to display the
405 digest name in its output.
408 *) Added a new generic trace API which provides support for enabling
409 instrumentation through trace output. This feature is mainly intended
410 as an aid for developers and is disabled by default. To utilize it,
411 OpenSSL needs to be configured with the `enable-trace` option.
413 If the tracing API is enabled, the application can activate trace output
414 by registering BIOs as trace channels for a number of tracing and debugging
417 The 'openssl' application has been expanded to enable any of the types
418 available via environment variables defined by the user, and serves as
419 one possible example on how to use this functionality.
420 [Richard Levitte & Matthias St. Pierre]
422 *) Added build tests for C++. These are generated files that only do one
423 thing, to include one public OpenSSL head file each. This tests that
424 the public header files can be usefully included in a C++ application.
426 This test isn't enabled by default. It can be enabled with the option
427 'enable-buildtest-c++'.
430 *) Add Single Step KDF (EVP_KDF_SS) to EVP_KDF.
433 *) Add KMAC to EVP_MAC.
436 *) Added property based algorithm implementation selection framework to
440 *) Added SCA hardening for modular field inversion in EC_GROUP through
441 a new dedicated field_inv() pointer in EC_METHOD.
442 This also addresses a leakage affecting conversions from projective
443 to affine coordinates.
444 [Billy Bob Brumley, Nicola Tuveri]
446 *) Added EVP_KDF, an EVP layer KDF API, to simplify adding KDF and PRF
447 implementations. This includes an EVP_PKEY to EVP_KDF bridge for
448 those algorithms that were already supported through the EVP_PKEY API
449 (scrypt, TLS1 PRF and HKDF). The low-level KDF functions for PBKDF2
450 and scrypt are now wrappers that call EVP_KDF.
453 *) Build devcrypto engine as a dynamic engine.
456 *) Add keyed BLAKE2 to EVP_MAC.
459 *) Fix a bug in the computation of the endpoint-pair shared secret used
460 by DTLS over SCTP. This breaks interoperability with older versions
461 of OpenSSL like OpenSSL 1.1.0 and OpenSSL 1.0.2. There is a runtime
462 switch SSL_MODE_DTLS_SCTP_LABEL_LENGTH_BUG (off by default) enabling
463 interoperability with such broken implementations. However, enabling
464 this switch breaks interoperability with correct implementations.
466 *) Fix a use after free bug in d2i_X509_PUBKEY when overwriting a
467 re-used X509_PUBKEY object if the second PUBKEY is malformed.
470 *) Move strictness check from EVP_PKEY_asn1_new() to EVP_PKEY_asn1_add0().
473 *) Change the license to the Apache License v2.0.
476 *) Switch to a new version scheme using three numbers MAJOR.MINOR.PATCH.
478 o Major releases (indicated by incrementing the MAJOR release number)
479 may introduce incompatible API/ABI changes.
480 o Minor releases (indicated by incrementing the MINOR release number)
481 may introduce new features but retain API/ABI compatibility.
482 o Patch releases (indicated by incrementing the PATCH number)
483 are intended for bug fixes and other improvements of existing
484 features only (like improving performance or adding documentation)
485 and retain API/ABI compatibility.
488 *) Add support for RFC5297 SIV mode (siv128), including AES-SIV.
491 *) Remove the 'dist' target and add a tarball building script. The
492 'dist' target has fallen out of use, and it shouldn't be
493 necessary to configure just to create a source distribution.
496 *) Recreate the OS390-Unix config target. It no longer relies on a
497 special script like it did for OpenSSL pre-1.1.0.
500 *) Instead of having the source directories listed in Configure, add
501 a 'build.info' keyword SUBDIRS to indicate what sub-directories to
505 *) Add GMAC to EVP_MAC.
508 *) Ported the HMAC, CMAC and SipHash EVP_PKEY_METHODs to EVP_MAC.
511 *) Added EVP_MAC, an EVP layer MAC API, to simplify adding MAC
512 implementations. This includes a generic EVP_PKEY to EVP_MAC bridge,
513 to facilitate the continued use of MACs through raw private keys in
514 functionality such as EVP_DigestSign* and EVP_DigestVerify*.
517 *) Deprecate ECDH_KDF_X9_62() and mark its replacement as internal. Users
518 should use the EVP interface instead (EVP_PKEY_CTX_set_ecdh_kdf_type).
521 *) Added EVP_PKEY_ECDH_KDF_X9_63 and ecdh_KDF_X9_63() as replacements for
522 the EVP_PKEY_ECDH_KDF_X9_62 KDF type and ECDH_KDF_X9_62(). The old names
523 are retained for backwards compatibility.
526 *) AES-XTS mode now enforces that its two keys are different to mitigate
527 the attacked described in "Efficient Instantiations of Tweakable
528 Blockciphers and Refinements to Modes OCB and PMAC" by Phillip Rogaway.
529 Details of this attack can be obtained from:
530 http://web.cs.ucdavis.edu/%7Erogaway/papers/offsets.pdf
533 *) Rename the object files, i.e. give them other names than in previous
534 versions. Their names now include the name of the final product, as
535 well as its type mnemonic (bin, lib, shlib).
538 *) Added new option for 'openssl list', '-objects', which will display the
539 list of built in objects, i.e. OIDs with names.
542 *) Added support for Linux Kernel TLS data-path. The Linux Kernel data-path
543 improves application performance by removing data copies and providing
544 applications with zero-copy system calls such as sendfile and splice.
547 Changes between 1.1.1a and 1.1.1b [xx XXX xxxx]
549 *) Change the info callback signals for the start and end of a post-handshake
550 message exchange in TLSv1.3. In 1.1.1/1.1.1a we used SSL_CB_HANDSHAKE_START
551 and SSL_CB_HANDSHAKE_DONE. Experience has shown that many applications get
552 confused by this and assume that a TLSv1.2 renegotiation has started. This
553 can break KeyUpdate handling. Instead we no longer signal the start and end
554 of a post handshake message exchange (although the messages themselves are
555 still signalled). This could break some applications that were expecting
556 the old signals. However without this KeyUpdate is not usable for many
560 Changes between 1.1.1 and 1.1.1a [20 Nov 2018]
562 *) Timing vulnerability in DSA signature generation
564 The OpenSSL DSA signature algorithm has been shown to be vulnerable to a
565 timing side channel attack. An attacker could use variations in the signing
566 algorithm to recover the private key.
568 This issue was reported to OpenSSL on 16th October 2018 by Samuel Weiser.
572 *) Timing vulnerability in ECDSA signature generation
574 The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a
575 timing side channel attack. An attacker could use variations in the signing
576 algorithm to recover the private key.
578 This issue was reported to OpenSSL on 25th October 2018 by Samuel Weiser.
582 *) Fixed the issue that RAND_add()/RAND_seed() silently discards random input
583 if its length exceeds 4096 bytes. The limit has been raised to a buffer size
584 of two gigabytes and the error handling improved.
586 This issue was reported to OpenSSL by Dr. Falko Strenzke. It has been
587 categorized as a normal bug, not a security issue, because the DRBG reseeds
588 automatically and is fully functional even without additional randomness
589 provided by the application.
591 Changes between 1.1.0i and 1.1.1 [11 Sep 2018]
593 *) Add a new ClientHello callback. Provides a callback interface that gives
594 the application the ability to adjust the nascent SSL object at the
595 earliest stage of ClientHello processing, immediately after extensions have
596 been collected but before they have been processed. In particular, this
597 callback can adjust the supported TLS versions in response to the contents
601 *) Add SM2 base algorithm support.
604 *) s390x assembly pack: add (improved) hardware-support for the following
605 cryptographic primitives: sha3, shake, aes-gcm, aes-ccm, aes-ctr, aes-ofb,
606 aes-cfb/cfb8, aes-ecb.
609 *) Make EVP_PKEY_asn1_new() a bit stricter about its input. A NULL pem_str
610 parameter is no longer accepted, as it leads to a corrupt table. NULL
611 pem_str is reserved for alias entries only.
614 *) Use the new ec_scalar_mul_ladder scaffold to implement a specialized ladder
615 step for prime curves. The new implementation is based on formulae from
616 differential addition-and-doubling in homogeneous projective coordinates
617 from Izu-Takagi "A fast parallel elliptic curve multiplication resistant
618 against side channel attacks" and Brier-Joye "Weierstrass Elliptic Curves
619 and Side-Channel Attacks" Eq. (8) for y-coordinate recovery, modified
620 to work in projective coordinates.
621 [Billy Bob Brumley, Nicola Tuveri]
623 *) Change generating and checking of primes so that the error rate of not
624 being prime depends on the intended use based on the size of the input.
625 For larger primes this will result in more rounds of Miller-Rabin.
626 The maximal error rate for primes with more than 1080 bits is lowered
628 [Kurt Roeckx, Annie Yousar]
630 *) Increase the number of Miller-Rabin rounds for DSA key generating to 64.
633 *) The 'tsget' script is renamed to 'tsget.pl', to avoid confusion when
634 moving between systems, and to avoid confusion when a Windows build is
635 done with mingw vs with MSVC. For POSIX installs, there's still a
636 symlink or copy named 'tsget' to avoid that confusion as well.
639 *) Revert blinding in ECDSA sign and instead make problematic addition
640 length-invariant. Switch even to fixed-length Montgomery multiplication.
643 *) Use the new ec_scalar_mul_ladder scaffold to implement a specialized ladder
644 step for binary curves. The new implementation is based on formulae from
645 differential addition-and-doubling in mixed Lopez-Dahab projective
646 coordinates, modified to independently blind the operands.
647 [Billy Bob Brumley, Sohaib ul Hassan, Nicola Tuveri]
649 *) Add a scaffold to optionally enhance the Montgomery ladder implementation
650 for `ec_scalar_mul_ladder` (formerly `ec_mul_consttime`) allowing
651 EC_METHODs to implement their own specialized "ladder step", to take
652 advantage of more favorable coordinate systems or more efficient
653 differential addition-and-doubling algorithms.
654 [Billy Bob Brumley, Sohaib ul Hassan, Nicola Tuveri]
656 *) Modified the random device based seed sources to keep the relevant
657 file descriptors open rather than reopening them on each access.
658 This allows such sources to operate in a chroot() jail without
659 the associated device nodes being available. This behaviour can be
660 controlled using RAND_keep_random_devices_open().
663 *) Numerous side-channel attack mitigations have been applied. This may have
664 performance impacts for some algorithms for the benefit of improved
665 security. Specific changes are noted in this change log by their respective
669 *) AIX shared library support overhaul. Switch to AIX "natural" way of
670 handling shared libraries, which means collecting shared objects of
671 different versions and bitnesses in one common archive. This allows to
672 mitigate conflict between 1.0 and 1.1 side-by-side installations. It
673 doesn't affect the way 3rd party applications are linked, only how
674 multi-version installation is managed.
677 *) Make ec_group_do_inverse_ord() more robust and available to other
678 EC cryptosystems, so that irrespective of BN_FLG_CONSTTIME, SCA
679 mitigations are applied to the fallback BN_mod_inverse().
680 When using this function rather than BN_mod_inverse() directly, new
681 EC cryptosystem implementations are then safer-by-default.
684 *) Add coordinate blinding for EC_POINT and implement projective
685 coordinate blinding for generic prime curves as a countermeasure to
686 chosen point SCA attacks.
687 [Sohaib ul Hassan, Nicola Tuveri, Billy Bob Brumley]
689 *) Add blinding to ECDSA and DSA signatures to protect against side channel
690 attacks discovered by Keegan Ryan (NCC Group).
693 *) Enforce checking in the pkeyutl command line app to ensure that the input
694 length does not exceed the maximum supported digest length when performing
695 a sign, verify or verifyrecover operation.
698 *) SSL_MODE_AUTO_RETRY is enabled by default. Applications that use blocking
699 I/O in combination with something like select() or poll() will hang. This
700 can be turned off again using SSL_CTX_clear_mode().
701 Many applications do not properly handle non-application data records, and
702 TLS 1.3 sends more of such records. Setting SSL_MODE_AUTO_RETRY works
703 around the problems in those applications, but can also break some.
704 It's recommended to read the manpages about SSL_read(), SSL_write(),
705 SSL_get_error(), SSL_shutdown(), SSL_CTX_set_mode() and
706 SSL_CTX_set_read_ahead() again.
709 *) When unlocking a pass phrase protected PEM file or PKCS#8 container, we
710 now allow empty (zero character) pass phrases.
713 *) Apply blinding to binary field modular inversion and remove patent
714 pending (OPENSSL_SUN_GF2M_DIV) BN_GF2m_mod_div implementation.
717 *) Deprecate ec2_mult.c and unify scalar multiplication code paths for
718 binary and prime elliptic curves.
721 *) Remove ECDSA nonce padding: EC_POINT_mul is now responsible for
722 constant time fixed point multiplication.
725 *) Revise elliptic curve scalar multiplication with timing attack
726 defenses: ec_wNAF_mul redirects to a constant time implementation
727 when computing fixed point and variable point multiplication (which
728 in OpenSSL are mostly used with secret scalars in keygen, sign,
729 ECDH derive operations).
730 [Billy Bob Brumley, Nicola Tuveri, Cesar Pereida García,
733 *) Updated CONTRIBUTING
736 *) Updated DRBG / RAND to request nonce and additional low entropy
737 randomness from the system.
738 [Matthias St. Pierre]
740 *) Updated 'openssl rehash' to use OpenSSL consistent default.
743 *) Moved the load of the ssl_conf module to libcrypto, which helps
744 loading engines that libssl uses before libssl is initialised.
747 *) Added EVP_PKEY_sign() and EVP_PKEY_verify() for EdDSA
750 *) Fixed X509_NAME_ENTRY_set to get multi-valued RDNs right in all cases.
751 [Ingo Schwarze, Rich Salz]
753 *) Added output of accepting IP address and port for 'openssl s_server'
756 *) Added a new API for TLSv1.3 ciphersuites:
757 SSL_CTX_set_ciphersuites()
758 SSL_set_ciphersuites()
761 *) Memory allocation failures consistently add an error to the error
765 *) Don't use OPENSSL_ENGINES and OPENSSL_CONF environment values
766 in libcrypto when run as setuid/setgid.
769 *) Load any config file by default when libssl is used.
772 *) Added new public header file <openssl/rand_drbg.h> and documentation
773 for the RAND_DRBG API. See manual page RAND_DRBG(7) for an overview.
774 [Matthias St. Pierre]
776 *) QNX support removed (cannot find contributors to get their approval
777 for the license change).
780 *) TLSv1.3 replay protection for early data has been implemented. See the
781 SSL_read_early_data() man page for further details.
784 *) Separated TLSv1.3 ciphersuite configuration out from TLSv1.2 ciphersuite
785 configuration. TLSv1.3 ciphersuites are not compatible with TLSv1.2 and
786 below. Similarly TLSv1.2 ciphersuites are not compatible with TLSv1.3.
787 In order to avoid issues where legacy TLSv1.2 ciphersuite configuration
788 would otherwise inadvertently disable all TLSv1.3 ciphersuites the
789 configuration has been separated out. See the ciphers man page or the
790 SSL_CTX_set_ciphersuites() man page for more information.
793 *) On POSIX (BSD, Linux, ...) systems the ocsp(1) command running
794 in responder mode now supports the new "-multi" option, which
795 spawns the specified number of child processes to handle OCSP
796 requests. The "-timeout" option now also limits the OCSP
797 responder's patience to wait to receive the full client request
798 on a newly accepted connection. Child processes are respawned
799 as needed, and the CA index file is automatically reloaded
800 when changed. This makes it possible to run the "ocsp" responder
801 as a long-running service, making the OpenSSL CA somewhat more
802 feature-complete. In this mode, most diagnostic messages logged
803 after entering the event loop are logged via syslog(3) rather than
807 *) Added support for X448 and Ed448. Heavily based on original work by
811 *) Extend OSSL_STORE with capabilities to search and to narrow the set of
812 objects loaded. This adds the functions OSSL_STORE_expect() and
813 OSSL_STORE_find() as well as needed tools to construct searches and
814 get the search data out of them.
817 *) Support for TLSv1.3 added. Note that users upgrading from an earlier
818 version of OpenSSL should review their configuration settings to ensure
819 that they are still appropriate for TLSv1.3. For further information see:
820 https://wiki.openssl.org/index.php/TLS1.3
823 *) Grand redesign of the OpenSSL random generator
825 The default RAND method now utilizes an AES-CTR DRBG according to
826 NIST standard SP 800-90Ar1. The new random generator is essentially
827 a port of the default random generator from the OpenSSL FIPS 2.0
828 object module. It is a hybrid deterministic random bit generator
829 using an AES-CTR bit stream and which seeds and reseeds itself
830 automatically using trusted system entropy sources.
832 Some of its new features are:
833 o Support for multiple DRBG instances with seed chaining.
834 o The default RAND method makes use of a DRBG.
835 o There is a public and private DRBG instance.
836 o The DRBG instances are fork-safe.
837 o Keep all global DRBG instances on the secure heap if it is enabled.
838 o The public and private DRBG instance are per thread for lock free
840 [Paul Dale, Benjamin Kaduk, Kurt Roeckx, Rich Salz, Matthias St. Pierre]
842 *) Changed Configure so it only says what it does and doesn't dump
843 so much data. Instead, ./configdata.pm should be used as a script
844 to display all sorts of configuration data.
847 *) Added processing of "make variables" to Configure.
850 *) Added SHA512/224 and SHA512/256 algorithm support.
853 *) The last traces of Netware support, first removed in 1.1.0, have
857 *) Get rid of Makefile.shared, and in the process, make the processing
858 of certain files (rc.obj, or the .def/.map/.opt files produced from
859 the ordinal files) more visible and hopefully easier to trace and
860 debug (or make silent).
863 *) Make it possible to have environment variable assignments as
864 arguments to config / Configure.
867 *) Add multi-prime RSA (RFC 8017) support.
870 *) Add SM3 implemented according to GB/T 32905-2016
871 [ Jack Lloyd <jack.lloyd@ribose.com>,
872 Ronald Tse <ronald.tse@ribose.com>,
873 Erick Borsboom <erick.borsboom@ribose.com> ]
875 *) Add 'Maximum Fragment Length' TLS extension negotiation and support
876 as documented in RFC6066.
877 Based on a patch from Tomasz Moń
878 [Filipe Raimundo da Silva]
880 *) Add SM4 implemented according to GB/T 32907-2016.
881 [ Jack Lloyd <jack.lloyd@ribose.com>,
882 Ronald Tse <ronald.tse@ribose.com>,
883 Erick Borsboom <erick.borsboom@ribose.com> ]
885 *) Reimplement -newreq-nodes and ERR_error_string_n; the
886 original author does not agree with the license change.
889 *) Add ARIA AEAD TLS support.
892 *) Some macro definitions to support VS6 have been removed. Visual
893 Studio 6 has not worked since 1.1.0
896 *) Add ERR_clear_last_mark(), to allow callers to clear the last mark
897 without clearing the errors.
900 *) Add "atfork" functions. If building on a system that without
901 pthreads, see doc/man3/OPENSSL_fork_prepare.pod for application
902 requirements. The RAND facility now uses/requires this.
908 *) The UI API becomes a permanent and integral part of libcrypto, i.e.
909 not possible to disable entirely. However, it's still possible to
910 disable the console reading UI method, UI_OpenSSL() (use UI_null()
913 To disable, configure with 'no-ui-console'. 'no-ui' is still
914 possible to use as an alias. Check at compile time with the
915 macro OPENSSL_NO_UI_CONSOLE. The macro OPENSSL_NO_UI is still
916 possible to check and is an alias for OPENSSL_NO_UI_CONSOLE.
919 *) Add a STORE module, which implements a uniform and URI based reader of
920 stores that can contain keys, certificates, CRLs and numerous other
921 objects. The main API is loosely based on a few stdio functions,
922 and includes OSSL_STORE_open, OSSL_STORE_load, OSSL_STORE_eof,
923 OSSL_STORE_error and OSSL_STORE_close.
924 The implementation uses backends called "loaders" to implement arbitrary
925 URI schemes. There is one built in "loader" for the 'file' scheme.
928 *) Add devcrypto engine. This has been implemented against cryptodev-linux,
929 then adjusted to work on FreeBSD 8.4 as well.
930 Enable by configuring with 'enable-devcryptoeng'. This is done by default
931 on BSD implementations, as cryptodev.h is assumed to exist on all of them.
934 *) Module names can prefixed with OSSL_ or OPENSSL_. This affects
935 util/mkerr.pl, which is adapted to allow those prefixes, leading to
936 error code calls like this:
938 OSSL_FOOerr(OSSL_FOO_F_SOMETHING, OSSL_FOO_R_WHATEVER);
940 With this change, we claim the namespaces OSSL and OPENSSL in a manner
941 that can be encoded in C. For the foreseeable future, this will only
943 [Richard Levitte and Tim Hudson]
945 *) Removed BSD cryptodev engine.
948 *) Add a build target 'build_all_generated', to build all generated files
949 and only that. This can be used to prepare everything that requires
950 things like perl for a system that lacks perl and then move everything
951 to that system and do the rest of the build there.
954 *) In the UI interface, make it possible to duplicate the user data. This
955 can be used by engines that need to retain the data for a longer time
956 than just the call where this user data is passed.
959 *) Ignore the '-named_curve auto' value for compatibility of applications
961 [Tomas Mraz <tmraz@fedoraproject.org>]
963 *) Fragmented SSL/TLS alerts are no longer accepted. An alert message is 2
964 bytes long. In theory it is permissible in SSLv3 - TLSv1.2 to fragment such
965 alerts across multiple records (some of which could be empty). In practice
966 it make no sense to send an empty alert record, or to fragment one. TLSv1.3
967 prohibts this altogether and other libraries (BoringSSL, NSS) do not
968 support this at all. Supporting it adds significant complexity to the
969 record layer, and its removal is unlikely to cause inter-operability
973 *) Add the ASN.1 types INT32, UINT32, INT64, UINT64 and variants prefixed
974 with Z. These are meant to replace LONG and ZLONG and to be size safe.
975 The use of LONG and ZLONG is discouraged and scheduled for deprecation
979 *) Add the 'z' and 'j' modifiers to BIO_printf() et al formatting string,
980 'z' is to be used for [s]size_t, and 'j' - with [u]int64_t.
981 [Richard Levitte, Andy Polyakov]
983 *) Add EC_KEY_get0_engine(), which does for EC_KEY what RSA_get0_engine()
987 *) Have 'config' recognise 64-bit mingw and choose 'mingw64' as the target
988 platform rather than 'mingw'.
991 *) The functions X509_STORE_add_cert and X509_STORE_add_crl return
992 success if they are asked to add an object which already exists
993 in the store. This change cascades to other functions which load
994 certificates and CRLs.
997 *) x86_64 assembly pack: annotate code with DWARF CFI directives to
998 facilitate stack unwinding even from assembly subroutines.
1001 *) Remove VAX C specific definitions of OPENSSL_EXPORT, OPENSSL_EXTERN.
1002 Also remove OPENSSL_GLOBAL entirely, as it became a no-op.
1005 *) Remove the VMS-specific reimplementation of gmtime from crypto/o_times.c.
1006 VMS C's RTL has a fully up to date gmtime() and gmtime_r() since V7.1,
1007 which is the minimum version we support.
1010 *) Certificate time validation (X509_cmp_time) enforces stricter
1011 compliance with RFC 5280. Fractional seconds and timezone offsets
1012 are no longer allowed.
1015 *) Add support for ARIA
1018 *) s_client will now send the Server Name Indication (SNI) extension by
1019 default unless the new "-noservername" option is used. The server name is
1020 based on the host provided to the "-connect" option unless overridden by
1021 using "-servername".
1024 *) Add support for SipHash
1027 *) OpenSSL now fails if it receives an unrecognised record type in TLS1.0
1028 or TLS1.1. Previously this only happened in SSLv3 and TLS1.2. This is to
1029 prevent issues where no progress is being made and the peer continually
1030 sends unrecognised record types, using up resources processing them.
1033 *) 'openssl passwd' can now produce SHA256 and SHA512 based output,
1034 using the algorithm defined in
1035 https://www.akkadia.org/drepper/SHA-crypt.txt
1038 *) Heartbeat support has been removed; the ABI is changed for now.
1039 [Richard Levitte, Rich Salz]
1041 *) Support for SSL_OP_NO_ENCRYPT_THEN_MAC in SSL_CONF_cmd.
1044 *) The RSA "null" method, which was partially supported to avoid patent
1045 issues, has been replaced to always returns NULL.
1049 Changes between 1.1.0h and 1.1.0i [xx XXX xxxx]
1051 *) Client DoS due to large DH parameter
1053 During key agreement in a TLS handshake using a DH(E) based ciphersuite a
1054 malicious server can send a very large prime value to the client. This will
1055 cause the client to spend an unreasonably long period of time generating a
1056 key for this prime resulting in a hang until the client has finished. This
1057 could be exploited in a Denial Of Service attack.
1059 This issue was reported to OpenSSL on 5th June 2018 by Guido Vranken
1063 *) Cache timing vulnerability in RSA Key Generation
1065 The OpenSSL RSA Key generation algorithm has been shown to be vulnerable to
1066 a cache timing side channel attack. An attacker with sufficient access to
1067 mount cache timing attacks during the RSA key generation process could
1068 recover the private key.
1070 This issue was reported to OpenSSL on 4th April 2018 by Alejandro Cabrera
1071 Aldaya, Billy Brumley, Cesar Pereida Garcia and Luis Manuel Alvarez Tapia.
1075 *) Make EVP_PKEY_asn1_new() a bit stricter about its input. A NULL pem_str
1076 parameter is no longer accepted, as it leads to a corrupt table. NULL
1077 pem_str is reserved for alias entries only.
1080 *) Revert blinding in ECDSA sign and instead make problematic addition
1081 length-invariant. Switch even to fixed-length Montgomery multiplication.
1084 *) Change generating and checking of primes so that the error rate of not
1085 being prime depends on the intended use based on the size of the input.
1086 For larger primes this will result in more rounds of Miller-Rabin.
1087 The maximal error rate for primes with more than 1080 bits is lowered
1089 [Kurt Roeckx, Annie Yousar]
1091 *) Increase the number of Miller-Rabin rounds for DSA key generating to 64.
1094 *) Add blinding to ECDSA and DSA signatures to protect against side channel
1095 attacks discovered by Keegan Ryan (NCC Group).
1098 *) When unlocking a pass phrase protected PEM file or PKCS#8 container, we
1099 now allow empty (zero character) pass phrases.
1102 *) Certificate time validation (X509_cmp_time) enforces stricter
1103 compliance with RFC 5280. Fractional seconds and timezone offsets
1104 are no longer allowed.
1107 *) Fixed a text canonicalisation bug in CMS
1109 Where a CMS detached signature is used with text content the text goes
1110 through a canonicalisation process first prior to signing or verifying a
1111 signature. This process strips trailing space at the end of lines, converts
1112 line terminators to CRLF and removes additional trailing line terminators
1113 at the end of a file. A bug in the canonicalisation process meant that
1114 some characters, such as form-feed, were incorrectly treated as whitespace
1115 and removed. This is contrary to the specification (RFC5485). This fix
1116 could mean that detached text data signed with an earlier version of
1117 OpenSSL 1.1.0 may fail to verify using the fixed version, or text data
1118 signed with a fixed OpenSSL may fail to verify with an earlier version of
1119 OpenSSL 1.1.0. A workaround is to only verify the canonicalised text data
1120 and use the "-binary" flag (for the "cms" command line application) or set
1121 the SMIME_BINARY/PKCS7_BINARY/CMS_BINARY flags (if using CMS_verify()).
1124 Changes between 1.1.0g and 1.1.0h [27 Mar 2018]
1126 *) Constructed ASN.1 types with a recursive definition could exceed the stack
1128 Constructed ASN.1 types with a recursive definition (such as can be found
1129 in PKCS7) could eventually exceed the stack given malicious input with
1130 excessive recursion. This could result in a Denial Of Service attack. There
1131 are no such structures used within SSL/TLS that come from untrusted sources
1132 so this is considered safe.
1134 This issue was reported to OpenSSL on 4th January 2018 by the OSS-fuzz
1139 *) Incorrect CRYPTO_memcmp on HP-UX PA-RISC
1141 Because of an implementation bug the PA-RISC CRYPTO_memcmp function is
1142 effectively reduced to only comparing the least significant bit of each
1143 byte. This allows an attacker to forge messages that would be considered as
1144 authenticated in an amount of tries lower than that guaranteed by the
1145 security claims of the scheme. The module can only be compiled by the
1146 HP-UX assembler, so that only HP-UX PA-RISC targets are affected.
1148 This issue was reported to OpenSSL on 2nd March 2018 by Peter Waltenberg
1153 *) Add a build target 'build_all_generated', to build all generated files
1154 and only that. This can be used to prepare everything that requires
1155 things like perl for a system that lacks perl and then move everything
1156 to that system and do the rest of the build there.
1159 *) Backport SSL_OP_NO_RENGOTIATION
1161 OpenSSL 1.0.2 and below had the ability to disable renegotiation using the
1162 (undocumented) SSL3_FLAGS_NO_RENEGOTIATE_CIPHERS flag. Due to the opacity
1163 changes this is no longer possible in 1.1.0. Therefore the new
1164 SSL_OP_NO_RENEGOTIATION option from 1.1.1-dev has been backported to
1165 1.1.0 to provide equivalent functionality.
1167 Note that if an application built against 1.1.0h headers (or above) is run
1168 using an older version of 1.1.0 (prior to 1.1.0h) then the option will be
1169 accepted but nothing will happen, i.e. renegotiation will not be prevented.
1172 *) Removed the OS390-Unix config target. It relied on a script that doesn't
1176 *) rsaz_1024_mul_avx2 overflow bug on x86_64
1178 There is an overflow bug in the AVX2 Montgomery multiplication procedure
1179 used in exponentiation with 1024-bit moduli. No EC algorithms are affected.
1180 Analysis suggests that attacks against RSA and DSA as a result of this
1181 defect would be very difficult to perform and are not believed likely.
1182 Attacks against DH1024 are considered just feasible, because most of the
1183 work necessary to deduce information about a private key may be performed
1184 offline. The amount of resources required for such an attack would be
1185 significant. However, for an attack on TLS to be meaningful, the server
1186 would have to share the DH1024 private key among multiple clients, which is
1187 no longer an option since CVE-2016-0701.
1189 This only affects processors that support the AVX2 but not ADX extensions
1190 like Intel Haswell (4th generation).
1192 This issue was reported to OpenSSL by David Benjamin (Google). The issue
1193 was originally found via the OSS-Fuzz project.
1197 Changes between 1.1.0f and 1.1.0g [2 Nov 2017]
1199 *) bn_sqrx8x_internal carry bug on x86_64
1201 There is a carry propagating bug in the x86_64 Montgomery squaring
1202 procedure. No EC algorithms are affected. Analysis suggests that attacks
1203 against RSA and DSA as a result of this defect would be very difficult to
1204 perform and are not believed likely. Attacks against DH are considered just
1205 feasible (although very difficult) because most of the work necessary to
1206 deduce information about a private key may be performed offline. The amount
1207 of resources required for such an attack would be very significant and
1208 likely only accessible to a limited number of attackers. An attacker would
1209 additionally need online access to an unpatched system using the target
1210 private key in a scenario with persistent DH parameters and a private
1211 key that is shared between multiple clients.
1213 This only affects processors that support the BMI1, BMI2 and ADX extensions
1214 like Intel Broadwell (5th generation) and later or AMD Ryzen.
1216 This issue was reported to OpenSSL by the OSS-Fuzz project.
1220 *) Malformed X.509 IPAddressFamily could cause OOB read
1222 If an X.509 certificate has a malformed IPAddressFamily extension,
1223 OpenSSL could do a one-byte buffer overread. The most likely result
1224 would be an erroneous display of the certificate in text format.
1226 This issue was reported to OpenSSL by the OSS-Fuzz project.
1230 Changes between 1.1.0e and 1.1.0f [25 May 2017]
1232 *) Have 'config' recognise 64-bit mingw and choose 'mingw64' as the target
1233 platform rather than 'mingw'.
1236 *) Remove the VMS-specific reimplementation of gmtime from crypto/o_times.c.
1237 VMS C's RTL has a fully up to date gmtime() and gmtime_r() since V7.1,
1238 which is the minimum version we support.
1241 Changes between 1.1.0d and 1.1.0e [16 Feb 2017]
1243 *) Encrypt-Then-Mac renegotiation crash
1245 During a renegotiation handshake if the Encrypt-Then-Mac extension is
1246 negotiated where it was not in the original handshake (or vice-versa) then
1247 this can cause OpenSSL to crash (dependant on ciphersuite). Both clients
1248 and servers are affected.
1250 This issue was reported to OpenSSL by Joe Orton (Red Hat).
1254 Changes between 1.1.0c and 1.1.0d [26 Jan 2017]
1256 *) Truncated packet could crash via OOB read
1258 If one side of an SSL/TLS path is running on a 32-bit host and a specific
1259 cipher is being used, then a truncated packet can cause that host to
1260 perform an out-of-bounds read, usually resulting in a crash.
1262 This issue was reported to OpenSSL by Robert Święcki of Google.
1266 *) Bad (EC)DHE parameters cause a client crash
1268 If a malicious server supplies bad parameters for a DHE or ECDHE key
1269 exchange then this can result in the client attempting to dereference a
1270 NULL pointer leading to a client crash. This could be exploited in a Denial
1273 This issue was reported to OpenSSL by Guido Vranken.
1277 *) BN_mod_exp may produce incorrect results on x86_64
1279 There is a carry propagating bug in the x86_64 Montgomery squaring
1280 procedure. No EC algorithms are affected. Analysis suggests that attacks
1281 against RSA and DSA as a result of this defect would be very difficult to
1282 perform and are not believed likely. Attacks against DH are considered just
1283 feasible (although very difficult) because most of the work necessary to
1284 deduce information about a private key may be performed offline. The amount
1285 of resources required for such an attack would be very significant and
1286 likely only accessible to a limited number of attackers. An attacker would
1287 additionally need online access to an unpatched system using the target
1288 private key in a scenario with persistent DH parameters and a private
1289 key that is shared between multiple clients. For example this can occur by
1290 default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very
1291 similar to CVE-2015-3193 but must be treated as a separate problem.
1293 This issue was reported to OpenSSL by the OSS-Fuzz project.
1297 Changes between 1.1.0b and 1.1.0c [10 Nov 2016]
1299 *) ChaCha20/Poly1305 heap-buffer-overflow
1301 TLS connections using *-CHACHA20-POLY1305 ciphersuites are susceptible to
1302 a DoS attack by corrupting larger payloads. This can result in an OpenSSL
1303 crash. This issue is not considered to be exploitable beyond a DoS.
1305 This issue was reported to OpenSSL by Robert Święcki (Google Security Team)
1309 *) CMS Null dereference
1311 Applications parsing invalid CMS structures can crash with a NULL pointer
1312 dereference. This is caused by a bug in the handling of the ASN.1 CHOICE
1313 type in OpenSSL 1.1.0 which can result in a NULL value being passed to the
1314 structure callback if an attempt is made to free certain invalid encodings.
1315 Only CHOICE structures using a callback which do not handle NULL value are
1318 This issue was reported to OpenSSL by Tyler Nighswander of ForAllSecure.
1322 *) Montgomery multiplication may produce incorrect results
1324 There is a carry propagating bug in the Broadwell-specific Montgomery
1325 multiplication procedure that handles input lengths divisible by, but
1326 longer than 256 bits. Analysis suggests that attacks against RSA, DSA
1327 and DH private keys are impossible. This is because the subroutine in
1328 question is not used in operations with the private key itself and an input
1329 of the attacker's direct choice. Otherwise the bug can manifest itself as
1330 transient authentication and key negotiation failures or reproducible
1331 erroneous outcome of public-key operations with specially crafted input.
1332 Among EC algorithms only Brainpool P-512 curves are affected and one
1333 presumably can attack ECDH key negotiation. Impact was not analyzed in
1334 detail, because pre-requisites for attack are considered unlikely. Namely
1335 multiple clients have to choose the curve in question and the server has to
1336 share the private key among them, neither of which is default behaviour.
1337 Even then only clients that chose the curve will be affected.
1339 This issue was publicly reported as transient failures and was not
1340 initially recognized as a security issue. Thanks to Richard Morgan for
1341 providing reproducible case.
1345 *) Removed automatic addition of RPATH in shared libraries and executables,
1346 as this was a remainder from OpenSSL 1.0.x and isn't needed any more.
1349 Changes between 1.1.0a and 1.1.0b [26 Sep 2016]
1351 *) Fix Use After Free for large message sizes
1353 The patch applied to address CVE-2016-6307 resulted in an issue where if a
1354 message larger than approx 16k is received then the underlying buffer to
1355 store the incoming message is reallocated and moved. Unfortunately a
1356 dangling pointer to the old location is left which results in an attempt to
1357 write to the previously freed location. This is likely to result in a
1358 crash, however it could potentially lead to execution of arbitrary code.
1360 This issue only affects OpenSSL 1.1.0a.
1362 This issue was reported to OpenSSL by Robert Święcki.
1366 Changes between 1.1.0 and 1.1.0a [22 Sep 2016]
1368 *) OCSP Status Request extension unbounded memory growth
1370 A malicious client can send an excessively large OCSP Status Request
1371 extension. If that client continually requests renegotiation, sending a
1372 large OCSP Status Request extension each time, then there will be unbounded
1373 memory growth on the server. This will eventually lead to a Denial Of
1374 Service attack through memory exhaustion. Servers with a default
1375 configuration are vulnerable even if they do not support OCSP. Builds using
1376 the "no-ocsp" build time option are not affected.
1378 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
1382 *) SSL_peek() hang on empty record
1384 OpenSSL 1.1.0 SSL/TLS will hang during a call to SSL_peek() if the peer
1385 sends an empty record. This could be exploited by a malicious peer in a
1386 Denial Of Service attack.
1388 This issue was reported to OpenSSL by Alex Gaynor.
1392 *) Excessive allocation of memory in tls_get_message_header() and
1393 dtls1_preprocess_fragment()
1395 A (D)TLS message includes 3 bytes for its length in the header for the
1396 message. This would allow for messages up to 16Mb in length. Messages of
1397 this length are excessive and OpenSSL includes a check to ensure that a
1398 peer is sending reasonably sized messages in order to avoid too much memory
1399 being consumed to service a connection. A flaw in the logic of version
1400 1.1.0 means that memory for the message is allocated too early, prior to
1401 the excessive message length check. Due to way memory is allocated in
1402 OpenSSL this could mean an attacker could force up to 21Mb to be allocated
1403 to service a connection. This could lead to a Denial of Service through
1404 memory exhaustion. However, the excessive message length check still takes
1405 place, and this would cause the connection to immediately fail. Assuming
1406 that the application calls SSL_free() on the failed connection in a timely
1407 manner then the 21Mb of allocated memory will then be immediately freed
1408 again. Therefore the excessive memory allocation will be transitory in
1409 nature. This then means that there is only a security impact if:
1411 1) The application does not call SSL_free() in a timely manner in the event
1412 that the connection fails
1414 2) The application is working in a constrained environment where there is
1415 very little free memory
1417 3) The attacker initiates multiple connection attempts such that there are
1418 multiple connections in a state where memory has been allocated for the
1419 connection; SSL_free() has not yet been called; and there is insufficient
1420 memory to service the multiple requests.
1422 Except in the instance of (1) above any Denial Of Service is likely to be
1423 transitory because as soon as the connection fails the memory is
1424 subsequently freed again in the SSL_free() call. However there is an
1425 increased risk during this period of application crashes due to the lack of
1426 memory - which would then mean a more serious Denial of Service.
1428 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
1429 (CVE-2016-6307 and CVE-2016-6308)
1432 *) solaris-x86-cc, i.e. 32-bit configuration with vendor compiler,
1433 had to be removed. Primary reason is that vendor assembler can't
1434 assemble our modules with -KPIC flag. As result it, assembly
1435 support, was not even available as option. But its lack means
1436 lack of side-channel resistant code, which is incompatible with
1437 security by todays standards. Fortunately gcc is readily available
1438 prepackaged option, which we firmly point at...
1441 Changes between 1.0.2h and 1.1.0 [25 Aug 2016]
1443 *) Windows command-line tool supports UTF-8 opt-in option for arguments
1444 and console input. Setting OPENSSL_WIN32_UTF8 environment variable
1445 (to any value) allows Windows user to access PKCS#12 file generated
1446 with Windows CryptoAPI and protected with non-ASCII password, as well
1447 as files generated under UTF-8 locale on Linux also protected with
1451 *) To mitigate the SWEET32 attack (CVE-2016-2183), 3DES cipher suites
1452 have been disabled by default and removed from DEFAULT, just like RC4.
1453 See the RC4 item below to re-enable both.
1456 *) The method for finding the storage location for the Windows RAND seed file
1457 has changed. First we check %RANDFILE%. If that is not set then we check
1458 the directories %HOME%, %USERPROFILE% and %SYSTEMROOT% in that order. If
1459 all else fails we fall back to C:\.
1462 *) The EVP_EncryptUpdate() function has had its return type changed from void
1463 to int. A return of 0 indicates and error while a return of 1 indicates
1467 *) The flags RSA_FLAG_NO_CONSTTIME, DSA_FLAG_NO_EXP_CONSTTIME and
1468 DH_FLAG_NO_EXP_CONSTTIME which previously provided the ability to switch
1469 off the constant time implementation for RSA, DSA and DH have been made
1470 no-ops and deprecated.
1473 *) Windows RAND implementation was simplified to only get entropy by
1474 calling CryptGenRandom(). Various other RAND-related tickets
1476 [Joseph Wylie Yandle, Rich Salz]
1478 *) The stack and lhash API's were renamed to start with OPENSSL_SK_
1479 and OPENSSL_LH_, respectively. The old names are available
1480 with API compatibility. They new names are now completely documented.
1483 *) Unify TYPE_up_ref(obj) methods signature.
1484 SSL_CTX_up_ref(), SSL_up_ref(), X509_up_ref(), EVP_PKEY_up_ref(),
1485 X509_CRL_up_ref(), X509_OBJECT_up_ref_count() methods are now returning an
1486 int (instead of void) like all others TYPE_up_ref() methods.
1487 So now these methods also check the return value of CRYPTO_atomic_add(),
1488 and the validity of object reference counter.
1489 [fdasilvayy@gmail.com]
1491 *) With Windows Visual Studio builds, the .pdb files are installed
1492 alongside the installed libraries and executables. For a static
1493 library installation, ossl_static.pdb is the associate compiler
1494 generated .pdb file to be used when linking programs.
1497 *) Remove openssl.spec. Packaging files belong with the packagers.
1500 *) Automatic Darwin/OSX configuration has had a refresh, it will now
1501 recognise x86_64 architectures automatically. You can still decide
1502 to build for a different bitness with the environment variable
1503 KERNEL_BITS (can be 32 or 64), for example:
1505 KERNEL_BITS=32 ./config
1509 *) Change default algorithms in pkcs8 utility to use PKCS#5 v2.0,
1510 256 bit AES and HMAC with SHA256.
1513 *) Remove support for MIPS o32 ABI on IRIX (and IRIX only).
1516 *) Triple-DES ciphers have been moved from HIGH to MEDIUM.
1519 *) To enable users to have their own config files and build file templates,
1520 Configure looks in the directory indicated by the environment variable
1521 OPENSSL_LOCAL_CONFIG_DIR as well as the in-source Configurations/
1522 directory. On VMS, OPENSSL_LOCAL_CONFIG_DIR is expected to be a logical
1523 name and is used as is.
1526 *) The following datatypes were made opaque: X509_OBJECT, X509_STORE_CTX,
1527 X509_STORE, X509_LOOKUP, and X509_LOOKUP_METHOD. The unused type
1528 X509_CERT_FILE_CTX was removed.
1531 *) "shared" builds are now the default. To create only static libraries use
1532 the "no-shared" Configure option.
1535 *) Remove the no-aes, no-hmac, no-rsa, no-sha and no-md5 Configure options.
1536 All of these option have not worked for some while and are fundamental
1540 *) Make various cleanup routines no-ops and mark them as deprecated. Most
1541 global cleanup functions are no longer required because they are handled
1542 via auto-deinit (see OPENSSL_init_crypto and OPENSSL_init_ssl man pages).
1543 Explicitly de-initing can cause problems (e.g. where a library that uses
1544 OpenSSL de-inits, but an application is still using it). The affected
1545 functions are CONF_modules_free(), ENGINE_cleanup(), OBJ_cleanup(),
1546 EVP_cleanup(), BIO_sock_cleanup(), CRYPTO_cleanup_all_ex_data(),
1547 RAND_cleanup(), SSL_COMP_free_compression_methods(), ERR_free_strings() and
1548 COMP_zlib_cleanup().
1551 *) --strict-warnings no longer enables runtime debugging options
1552 such as REF_DEBUG. Instead, debug options are automatically
1553 enabled with '--debug' builds.
1554 [Andy Polyakov, Emilia Käsper]
1556 *) Made DH and DH_METHOD opaque. The structures for managing DH objects
1557 have been moved out of the public header files. New functions for managing
1558 these have been added.
1561 *) Made RSA and RSA_METHOD opaque. The structures for managing RSA
1562 objects have been moved out of the public header files. New
1563 functions for managing these have been added.
1566 *) Made DSA and DSA_METHOD opaque. The structures for managing DSA objects
1567 have been moved out of the public header files. New functions for managing
1568 these have been added.
1571 *) Made BIO and BIO_METHOD opaque. The structures for managing BIOs have been
1572 moved out of the public header files. New functions for managing these
1576 *) Removed no-rijndael as a config option. Rijndael is an old name for AES.
1579 *) Removed the mk1mf build scripts.
1582 *) Headers are now wrapped, if necessary, with OPENSSL_NO_xxx, so
1583 it is always safe to #include a header now.
1586 *) Removed the aged BC-32 config and all its supporting scripts
1589 *) Removed support for Ultrix, Netware, and OS/2.
1592 *) Add support for HKDF.
1593 [Alessandro Ghedini]
1595 *) Add support for blake2b and blake2s
1598 *) Added support for "pipelining". Ciphers that have the
1599 EVP_CIPH_FLAG_PIPELINE flag set have a capability to process multiple
1600 encryptions/decryptions simultaneously. There are currently no built-in
1601 ciphers with this property but the expectation is that engines will be able
1602 to offer it to significantly improve throughput. Support has been extended
1603 into libssl so that multiple records for a single connection can be
1604 processed in one go (for >=TLS 1.1).
1607 *) Added the AFALG engine. This is an async capable engine which is able to
1608 offload work to the Linux kernel. In this initial version it only supports
1609 AES128-CBC. The kernel must be version 4.1.0 or greater.
1612 *) OpenSSL now uses a new threading API. It is no longer necessary to
1613 set locking callbacks to use OpenSSL in a multi-threaded environment. There
1614 are two supported threading models: pthreads and windows threads. It is
1615 also possible to configure OpenSSL at compile time for "no-threads". The
1616 old threading API should no longer be used. The functions have been
1617 replaced with "no-op" compatibility macros.
1618 [Alessandro Ghedini, Matt Caswell]
1620 *) Modify behavior of ALPN to invoke callback after SNI/servername
1621 callback, such that updates to the SSL_CTX affect ALPN.
1624 *) Add SSL_CIPHER queries for authentication and key-exchange.
1627 *) Changes to the DEFAULT cipherlist:
1628 - Prefer (EC)DHE handshakes over plain RSA.
1629 - Prefer AEAD ciphers over legacy ciphers.
1630 - Prefer ECDSA over RSA when both certificates are available.
1631 - Prefer TLSv1.2 ciphers/PRF.
1632 - Remove DSS, SEED, IDEA, CAMELLIA, and AES-CCM from the
1636 *) Change the ECC default curve list to be this, in order: x25519,
1637 secp256r1, secp521r1, secp384r1.
1640 *) RC4 based libssl ciphersuites are now classed as "weak" ciphers and are
1641 disabled by default. They can be re-enabled using the
1642 enable-weak-ssl-ciphers option to Configure.
1645 *) If the server has ALPN configured, but supports no protocols that the
1646 client advertises, send a fatal "no_application_protocol" alert.
1647 This behaviour is SHALL in RFC 7301, though it isn't universally
1648 implemented by other servers.
1651 *) Add X25519 support.
1652 Add ASN.1 and EVP_PKEY methods for X25519. This includes support
1653 for public and private key encoding using the format documented in
1654 draft-ietf-curdle-pkix-02. The corresponding EVP_PKEY method supports
1655 key generation and key derivation.
1657 TLS support complies with draft-ietf-tls-rfc4492bis-08 and uses
1661 *) Deprecate SRP_VBASE_get_by_user.
1662 SRP_VBASE_get_by_user had inconsistent memory management behaviour.
1663 In order to fix an unavoidable memory leak (CVE-2016-0798),
1664 SRP_VBASE_get_by_user was changed to ignore the "fake user" SRP
1665 seed, even if the seed is configured.
1667 Users should use SRP_VBASE_get1_by_user instead. Note that in
1668 SRP_VBASE_get1_by_user, caller must free the returned value. Note
1669 also that even though configuring the SRP seed attempts to hide
1670 invalid usernames by continuing the handshake with fake
1671 credentials, this behaviour is not constant time and no strong
1672 guarantees are made that the handshake is indistinguishable from
1673 that of a valid user.
1676 *) Configuration change; it's now possible to build dynamic engines
1677 without having to build shared libraries and vice versa. This
1678 only applies to the engines in engines/, those in crypto/engine/
1679 will always be built into libcrypto (i.e. "static").
1681 Building dynamic engines is enabled by default; to disable, use
1682 the configuration option "disable-dynamic-engine".
1684 The only requirements for building dynamic engines are the
1685 presence of the DSO module and building with position independent
1686 code, so they will also automatically be disabled if configuring
1687 with "disable-dso" or "disable-pic".
1689 The macros OPENSSL_NO_STATIC_ENGINE and OPENSSL_NO_DYNAMIC_ENGINE
1690 are also taken away from openssl/opensslconf.h, as they are
1694 *) Configuration change; if there is a known flag to compile
1695 position independent code, it will always be applied on the
1696 libcrypto and libssl object files, and never on the application
1697 object files. This means other libraries that use routines from
1698 libcrypto / libssl can be made into shared libraries regardless
1699 of how OpenSSL was configured.
1701 If this isn't desirable, the configuration options "disable-pic"
1702 or "no-pic" can be used to disable the use of PIC. This will
1703 also disable building shared libraries and dynamic engines.
1706 *) Removed JPAKE code. It was experimental and has no wide use.
1709 *) The INSTALL_PREFIX Makefile variable has been renamed to
1710 DESTDIR. That makes for less confusion on what this variable
1711 is for. Also, the configuration option --install_prefix is
1715 *) Heartbeat for TLS has been removed and is disabled by default
1716 for DTLS; configure with enable-heartbeats. Code that uses the
1717 old #define's might need to be updated.
1718 [Emilia Käsper, Rich Salz]
1720 *) Rename REF_CHECK to REF_DEBUG.
1723 *) New "unified" build system
1725 The "unified" build system is aimed to be a common system for all
1726 platforms we support. With it comes new support for VMS.
1728 This system builds supports building in a different directory tree
1729 than the source tree. It produces one Makefile (for unix family
1730 or lookalikes), or one descrip.mms (for VMS).
1732 The source of information to make the Makefile / descrip.mms is
1733 small files called 'build.info', holding the necessary
1734 information for each directory with source to compile, and a
1735 template in Configurations, like unix-Makefile.tmpl or
1738 With this change, the library names were also renamed on Windows
1739 and on VMS. They now have names that are closer to the standard
1740 on Unix, and include the major version number, and in certain
1741 cases, the architecture they are built for. See "Notes on shared
1742 libraries" in INSTALL.
1744 We rely heavily on the perl module Text::Template.
1747 *) Added support for auto-initialisation and de-initialisation of the library.
1748 OpenSSL no longer requires explicit init or deinit routines to be called,
1749 except in certain circumstances. See the OPENSSL_init_crypto() and
1750 OPENSSL_init_ssl() man pages for further information.
1753 *) The arguments to the DTLSv1_listen function have changed. Specifically the
1754 "peer" argument is now expected to be a BIO_ADDR object.
1756 *) Rewrite of BIO networking library. The BIO library lacked consistent
1757 support of IPv6, and adding it required some more extensive
1758 modifications. This introduces the BIO_ADDR and BIO_ADDRINFO types,
1759 which hold all types of addresses and chains of address information.
1760 It also introduces a new API, with functions like BIO_socket,
1761 BIO_connect, BIO_listen, BIO_lookup and a rewrite of BIO_accept.
1762 The source/sink BIOs BIO_s_connect, BIO_s_accept and BIO_s_datagram
1763 have been adapted accordingly.
1766 *) RSA_padding_check_PKCS1_type_1 now accepts inputs with and without
1770 *) CRIME protection: disable compression by default, even if OpenSSL is
1771 compiled with zlib enabled. Applications can still enable compression
1772 by calling SSL_CTX_clear_options(ctx, SSL_OP_NO_COMPRESSION), or by
1773 using the SSL_CONF library to configure compression.
1776 *) The signature of the session callback configured with
1777 SSL_CTX_sess_set_get_cb was changed. The read-only input buffer
1778 was explicitly marked as 'const unsigned char*' instead of
1782 *) Always DPURIFY. Remove the use of uninitialized memory in the
1783 RNG, and other conditional uses of DPURIFY. This makes -DPURIFY a no-op.
1786 *) Removed many obsolete configuration items, including
1787 DES_PTR, DES_RISC1, DES_RISC2, DES_INT
1788 MD2_CHAR, MD2_INT, MD2_LONG
1790 IDEA_SHORT, IDEA_LONG
1791 RC2_SHORT, RC2_LONG, RC4_LONG, RC4_CHUNK, RC4_INDEX
1792 [Rich Salz, with advice from Andy Polyakov]
1794 *) Many BN internals have been moved to an internal header file.
1795 [Rich Salz with help from Andy Polyakov]
1797 *) Configuration and writing out the results from it has changed.
1798 Files such as Makefile include/openssl/opensslconf.h and are now
1799 produced through general templates, such as Makefile.in and
1800 crypto/opensslconf.h.in and some help from the perl module
1803 Also, the center of configuration information is no longer
1804 Makefile. Instead, Configure produces a perl module in
1805 configdata.pm which holds most of the config data (in the hash
1806 table %config), the target data that comes from the target
1807 configuration in one of the Configurations/*.conf files (in
1811 *) To clarify their intended purposes, the Configure options
1812 --prefix and --openssldir change their semantics, and become more
1813 straightforward and less interdependent.
1815 --prefix shall be used exclusively to give the location INSTALLTOP
1816 where programs, scripts, libraries, include files and manuals are
1817 going to be installed. The default is now /usr/local.
1819 --openssldir shall be used exclusively to give the default
1820 location OPENSSLDIR where certificates, private keys, CRLs are
1821 managed. This is also where the default openssl.cnf gets
1823 If the directory given with this option is a relative path, the
1824 values of both the --prefix value and the --openssldir value will
1825 be combined to become OPENSSLDIR.
1826 The default for --openssldir is INSTALLTOP/ssl.
1828 Anyone who uses --openssldir to specify where OpenSSL is to be
1829 installed MUST change to use --prefix instead.
1832 *) The GOST engine was out of date and therefore it has been removed. An up
1833 to date GOST engine is now being maintained in an external repository.
1834 See: https://wiki.openssl.org/index.php/Binaries. Libssl still retains
1835 support for GOST ciphersuites (these are only activated if a GOST engine
1839 *) EGD is no longer supported by default; use enable-egd when
1841 [Ben Kaduk and Rich Salz]
1843 *) The distribution now has Makefile.in files, which are used to
1844 create Makefile's when Configure is run. *Configure must be run
1845 before trying to build now.*
1848 *) The return value for SSL_CIPHER_description() for error conditions
1852 *) Support for RFC6698/RFC7671 DANE TLSA peer authentication.
1854 Obtaining and performing DNSSEC validation of TLSA records is
1855 the application's responsibility. The application provides
1856 the TLSA records of its choice to OpenSSL, and these are then
1857 used to authenticate the peer.
1859 The TLSA records need not even come from DNS. They can, for
1860 example, be used to implement local end-entity certificate or
1861 trust-anchor "pinning", where the "pin" data takes the form
1862 of TLSA records, which can augment or replace verification
1863 based on the usual WebPKI public certification authorities.
1866 *) Revert default OPENSSL_NO_DEPRECATED setting. Instead OpenSSL
1867 continues to support deprecated interfaces in default builds.
1868 However, applications are strongly advised to compile their
1869 source files with -DOPENSSL_API_COMPAT=0x10100000L, which hides
1870 the declarations of all interfaces deprecated in 0.9.8, 1.0.0
1871 or the 1.1.0 releases.
1873 In environments in which all applications have been ported to
1874 not use any deprecated interfaces OpenSSL's Configure script
1875 should be used with the --api=1.1.0 option to entirely remove
1876 support for the deprecated features from the library and
1877 unconditionally disable them in the installed headers.
1878 Essentially the same effect can be achieved with the "no-deprecated"
1879 argument to Configure, except that this will always restrict
1880 the build to just the latest API, rather than a fixed API
1883 As applications are ported to future revisions of the API,
1884 they should update their compile-time OPENSSL_API_COMPAT define
1885 accordingly, but in most cases should be able to continue to
1886 compile with later releases.
1888 The OPENSSL_API_COMPAT versions for 1.0.0, and 0.9.8 are
1889 0x10000000L and 0x00908000L, respectively. However those
1890 versions did not support the OPENSSL_API_COMPAT feature, and
1891 so applications are not typically tested for explicit support
1892 of just the undeprecated features of either release.
1895 *) Add support for setting the minimum and maximum supported protocol.
1896 It can bet set via the SSL_set_min_proto_version() and
1897 SSL_set_max_proto_version(), or via the SSL_CONF's MinProtocol and
1898 MaxProtocol. It's recommended to use the new APIs to disable
1899 protocols instead of disabling individual protocols using
1900 SSL_set_options() or SSL_CONF's Protocol. This change also
1901 removes support for disabling TLS 1.2 in the OpenSSL TLS
1902 client at compile time by defining OPENSSL_NO_TLS1_2_CLIENT.
1905 *) Support for ChaCha20 and Poly1305 added to libcrypto and libssl.
1908 *) New EC_KEY_METHOD, this replaces the older ECDSA_METHOD and ECDH_METHOD
1909 and integrates ECDSA and ECDH functionality into EC. Implementations can
1910 now redirect key generation and no longer need to convert to or from
1913 Note: the ecdsa.h and ecdh.h headers are now no longer needed and just
1914 include the ec.h header file instead.
1917 *) Remove support for all 40 and 56 bit ciphers. This includes all the export
1918 ciphers who are no longer supported and drops support the ephemeral RSA key
1919 exchange. The LOW ciphers currently doesn't have any ciphers in it.
1922 *) Made EVP_MD_CTX, EVP_MD, EVP_CIPHER_CTX, EVP_CIPHER and HMAC_CTX
1923 opaque. For HMAC_CTX, the following constructors and destructors
1926 HMAC_CTX *HMAC_CTX_new(void);
1927 void HMAC_CTX_free(HMAC_CTX *ctx);
1929 For EVP_MD and EVP_CIPHER, complete APIs to create, fill and
1930 destroy such methods has been added. See EVP_MD_meth_new(3) and
1931 EVP_CIPHER_meth_new(3) for documentation.
1934 1) EVP_MD_CTX_cleanup(), EVP_CIPHER_CTX_cleanup() and
1935 HMAC_CTX_cleanup() were removed. HMAC_CTX_reset() and
1936 EVP_MD_CTX_reset() should be called instead to reinitialise
1937 an already created structure.
1938 2) For consistency with the majority of our object creators and
1939 destructors, EVP_MD_CTX_(create|destroy) were renamed to
1940 EVP_MD_CTX_(new|free). The old names are retained as macros
1941 for deprecated builds.
1944 *) Added ASYNC support. Libcrypto now includes the async sub-library to enable
1945 cryptographic operations to be performed asynchronously as long as an
1946 asynchronous capable engine is used. See the ASYNC_start_job() man page for
1947 further details. Libssl has also had this capability integrated with the
1948 introduction of the new mode SSL_MODE_ASYNC and associated error
1949 SSL_ERROR_WANT_ASYNC. See the SSL_CTX_set_mode() and SSL_get_error() man
1950 pages. This work was developed in partnership with Intel Corp.
1953 *) SSL_{CTX_}set_ecdh_auto() has been removed and ECDH is support is
1954 always enabled now. If you want to disable the support you should
1955 exclude it using the list of supported ciphers. This also means that the
1956 "-no_ecdhe" option has been removed from s_server.
1959 *) SSL_{CTX}_set_tmp_ecdh() which can set 1 EC curve now internally calls
1960 SSL_{CTX_}set1_curves() which can set a list.
1963 *) Remove support for SSL_{CTX_}set_tmp_ecdh_callback(). You should set the
1964 curve you want to support using SSL_{CTX_}set1_curves().
1967 *) State machine rewrite. The state machine code has been significantly
1968 refactored in order to remove much duplication of code and solve issues
1969 with the old code (see ssl/statem/README for further details). This change
1970 does have some associated API changes. Notably the SSL_state() function
1971 has been removed and replaced by SSL_get_state which now returns an
1972 "OSSL_HANDSHAKE_STATE" instead of an int. SSL_set_state() has been removed
1973 altogether. The previous handshake states defined in ssl.h and ssl3.h have
1977 *) All instances of the string "ssleay" in the public API were replaced
1978 with OpenSSL (case-matching; e.g., OPENSSL_VERSION for #define's)
1979 Some error codes related to internal RSA_eay API's were renamed.
1982 *) The demo files in crypto/threads were moved to demo/threads.
1985 *) Removed obsolete engines: 4758cca, aep, atalla, cswift, nuron, gmp,
1987 [Matt Caswell, Rich Salz]
1989 *) New ASN.1 embed macro.
1991 New ASN.1 macro ASN1_EMBED. This is the same as ASN1_SIMPLE except the
1992 structure is not allocated: it is part of the parent. That is instead of
2000 This reduces memory fragmentation and make it impossible to accidentally
2001 set a mandatory field to NULL.
2003 This currently only works for some fields specifically a SEQUENCE, CHOICE,
2004 or ASN1_STRING type which is part of a parent SEQUENCE. Since it is
2005 equivalent to ASN1_SIMPLE it cannot be tagged, OPTIONAL, SET OF or
2009 *) Remove EVP_CHECK_DES_KEY, a compile-time option that never compiled.
2012 *) Removed DES and RC4 ciphersuites from DEFAULT. Also removed RC2 although
2013 in 1.0.2 EXPORT was already removed and the only RC2 ciphersuite is also
2014 an EXPORT one. COMPLEMENTOFDEFAULT has been updated accordingly to add
2015 DES and RC4 ciphersuites.
2018 *) Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs.
2019 This changes the decoding behaviour for some invalid messages,
2020 though the change is mostly in the more lenient direction, and
2021 legacy behaviour is preserved as much as possible.
2024 *) Fix no-stdio build.
2025 [ David Woodhouse <David.Woodhouse@intel.com> and also
2026 Ivan Nestlerode <ivan.nestlerode@sonos.com> ]
2028 *) New testing framework
2029 The testing framework has been largely rewritten and is now using
2030 perl and the perl modules Test::Harness and an extended variant of
2031 Test::More called OpenSSL::Test to do its work. All test scripts in
2032 test/ have been rewritten into test recipes, and all direct calls to
2033 executables in test/Makefile have become individual recipes using the
2034 simplified testing OpenSSL::Test::Simple.
2036 For documentation on our testing modules, do:
2038 perldoc test/testlib/OpenSSL/Test/Simple.pm
2039 perldoc test/testlib/OpenSSL/Test.pm
2043 *) Revamped memory debug; only -DCRYPTO_MDEBUG and -DCRYPTO_MDEBUG_ABORT
2044 are used; the latter aborts on memory leaks (usually checked on exit).
2045 Some undocumented "set malloc, etc., hooks" functions were removed
2046 and others were changed. All are now documented.
2049 *) In DSA_generate_parameters_ex, if the provided seed is too short,
2051 [Rich Salz and Ismo Puustinen <ismo.puustinen@intel.com>]
2053 *) Rewrite PSK to support ECDHE_PSK, DHE_PSK and RSA_PSK. Add ciphersuites
2054 from RFC4279, RFC4785, RFC5487, RFC5489.
2056 Thanks to Christian J. Dietrich and Giuseppe D'Angelo for the
2057 original RSA_PSK patch.
2060 *) Dropped support for the SSL3_FLAGS_DELAY_CLIENT_FINISHED flag. This SSLeay
2061 era flag was never set throughout the codebase (only read). Also removed
2062 SSL3_FLAGS_POP_BUFFER which was only used if
2063 SSL3_FLAGS_DELAY_CLIENT_FINISHED was also set.
2066 *) Changed the default name options in the "ca", "crl", "req" and "x509"
2067 to be "oneline" instead of "compat".
2070 *) Remove SSL_OP_TLS_BLOCK_PADDING_BUG. This is SSLeay legacy, we're
2071 not aware of clients that still exhibit this bug, and the workaround
2072 hasn't been working properly for a while.
2075 *) The return type of BIO_number_read() and BIO_number_written() as well as
2076 the corresponding num_read and num_write members in the BIO structure has
2077 changed from unsigned long to uint64_t. On platforms where an unsigned
2078 long is 32 bits (e.g. Windows) these counters could overflow if >4Gb is
2082 *) Given the pervasive nature of TLS extensions it is inadvisable to run
2083 OpenSSL without support for them. It also means that maintaining
2084 the OPENSSL_NO_TLSEXT option within the code is very invasive (and probably
2085 not well tested). Therefore the OPENSSL_NO_TLSEXT option has been removed.
2088 *) Removed support for the two export grade static DH ciphersuites
2089 EXP-DH-RSA-DES-CBC-SHA and EXP-DH-DSS-DES-CBC-SHA. These two ciphersuites
2090 were newly added (along with a number of other static DH ciphersuites) to
2091 1.0.2. However the two export ones have *never* worked since they were
2092 introduced. It seems strange in any case to be adding new export
2093 ciphersuites, and given "logjam" it also does not seem correct to fix them.
2096 *) Version negotiation has been rewritten. In particular SSLv23_method(),
2097 SSLv23_client_method() and SSLv23_server_method() have been deprecated,
2098 and turned into macros which simply call the new preferred function names
2099 TLS_method(), TLS_client_method() and TLS_server_method(). All new code
2100 should use the new names instead. Also as part of this change the ssl23.h
2101 header file has been removed.
2104 *) Support for Kerberos ciphersuites in TLS (RFC2712) has been removed. This
2105 code and the associated standard is no longer considered fit-for-purpose.
2108 *) RT2547 was closed. When generating a private key, try to make the
2109 output file readable only by the owner. This behavior change might
2110 be noticeable when interacting with other software.
2112 *) Documented all exdata functions. Added CRYPTO_free_ex_index.
2116 *) Added HTTP GET support to the ocsp command.
2119 *) Changed default digest for the dgst and enc commands from MD5 to
2123 *) RAND_pseudo_bytes has been deprecated. Users should use RAND_bytes instead.
2126 *) Added support for TLS extended master secret from
2127 draft-ietf-tls-session-hash-03.txt. Thanks for Alfredo Pironti for an
2128 initial patch which was a great help during development.
2131 *) All libssl internal structures have been removed from the public header
2132 files, and the OPENSSL_NO_SSL_INTERN option has been removed (since it is
2133 now redundant). Users should not attempt to access internal structures
2134 directly. Instead they should use the provided API functions.
2137 *) config has been changed so that by default OPENSSL_NO_DEPRECATED is used.
2138 Access to deprecated functions can be re-enabled by running config with
2139 "enable-deprecated". In addition applications wishing to use deprecated
2140 functions must define OPENSSL_USE_DEPRECATED. Note that this new behaviour
2141 will, by default, disable some transitive includes that previously existed
2142 in the header files (e.g. ec.h will no longer, by default, include bn.h)
2145 *) Added support for OCB mode. OpenSSL has been granted a patent license
2146 compatible with the OpenSSL license for use of OCB. Details are available
2147 at https://www.openssl.org/source/OCB-patent-grant-OpenSSL.pdf. Support
2148 for OCB can be removed by calling config with no-ocb.
2151 *) SSLv2 support has been removed. It still supports receiving a SSLv2
2152 compatible client hello.
2155 *) Increased the minimal RSA keysize from 256 to 512 bits [Rich Salz],
2156 done while fixing the error code for the key-too-small case.
2157 [Annie Yousar <a.yousar@informatik.hu-berlin.de>]
2159 *) CA.sh has been removed; use CA.pl instead.
2162 *) Removed old DES API.
2165 *) Remove various unsupported platforms:
2171 Sinix/ReliantUNIX RM400
2176 16-bit platforms such as WIN16
2179 *) Clean up OPENSSL_NO_xxx #define's
2180 Use setbuf() and remove OPENSSL_NO_SETVBUF_IONBF
2181 Rename OPENSSL_SYSNAME_xxx to OPENSSL_SYS_xxx
2182 OPENSSL_NO_EC{DH,DSA} merged into OPENSSL_NO_EC
2183 OPENSSL_NO_RIPEMD160, OPENSSL_NO_RIPEMD merged into OPENSSL_NO_RMD160
2184 OPENSSL_NO_FP_API merged into OPENSSL_NO_STDIO
2185 Remove OPENSSL_NO_BIO OPENSSL_NO_BUFFER OPENSSL_NO_CHAIN_VERIFY
2186 OPENSSL_NO_EVP OPENSSL_NO_FIPS_ERR OPENSSL_NO_HASH_COMP
2187 OPENSSL_NO_LHASH OPENSSL_NO_OBJECT OPENSSL_NO_SPEED OPENSSL_NO_STACK
2188 OPENSSL_NO_X509 OPENSSL_NO_X509_VERIFY
2189 Remove MS_STATIC; it's a relic from platforms <32 bits.
2192 *) Cleaned up dead code
2193 Remove all but one '#ifdef undef' which is to be looked at.
2196 *) Clean up calling of xxx_free routines.
2197 Just like free(), fix most of the xxx_free routines to accept
2198 NULL. Remove the non-null checks from callers. Save much code.
2201 *) Add secure heap for storage of private keys (when possible).
2202 Add BIO_s_secmem(), CBIGNUM, etc.
2203 Contributed by Akamai Technologies under our Corporate CLA.
2206 *) Experimental support for a new, fast, unbiased prime candidate generator,
2207 bn_probable_prime_dh_coprime(). Not currently used by any prime generator.
2208 [Felix Laurie von Massenbach <felix@erbridge.co.uk>]
2210 *) New output format NSS in the sess_id command line tool. This allows
2211 exporting the session id and the master key in NSS keylog format.
2212 [Martin Kaiser <martin@kaiser.cx>]
2214 *) Harmonize version and its documentation. -f flag is used to display
2216 [mancha <mancha1@zoho.com>]
2218 *) Fix eckey_priv_encode so it immediately returns an error upon a failure
2219 in i2d_ECPrivateKey. Thanks to Ted Unangst for feedback on this issue.
2220 [mancha <mancha1@zoho.com>]
2222 *) Fix some double frees. These are not thought to be exploitable.
2223 [mancha <mancha1@zoho.com>]
2225 *) A missing bounds check in the handling of the TLS heartbeat extension
2226 can be used to reveal up to 64k of memory to a connected client or
2229 Thanks for Neel Mehta of Google Security for discovering this bug and to
2230 Adam Langley <agl@chromium.org> and Bodo Moeller <bmoeller@acm.org> for
2231 preparing the fix (CVE-2014-0160)
2232 [Adam Langley, Bodo Moeller]
2234 *) Fix for the attack described in the paper "Recovering OpenSSL
2235 ECDSA Nonces Using the FLUSH+RELOAD Cache Side-channel Attack"
2236 by Yuval Yarom and Naomi Benger. Details can be obtained from:
2237 http://eprint.iacr.org/2014/140
2239 Thanks to Yuval Yarom and Naomi Benger for discovering this
2240 flaw and to Yuval Yarom for supplying a fix (CVE-2014-0076)
2241 [Yuval Yarom and Naomi Benger]
2243 *) Use algorithm specific chains in SSL_CTX_use_certificate_chain_file():
2244 this fixes a limitation in previous versions of OpenSSL.
2247 *) Experimental encrypt-then-mac support.
2249 Experimental support for encrypt then mac from
2250 draft-gutmann-tls-encrypt-then-mac-02.txt
2252 To enable it set the appropriate extension number (0x42 for the test
2253 server) using e.g. -DTLSEXT_TYPE_encrypt_then_mac=0x42
2255 For non-compliant peers (i.e. just about everything) this should have no
2258 WARNING: EXPERIMENTAL, SUBJECT TO CHANGE.
2262 *) Add EVP support for key wrapping algorithms, to avoid problems with
2263 existing code the flag EVP_CIPHER_CTX_WRAP_ALLOW has to be set in
2264 the EVP_CIPHER_CTX or an error is returned. Add AES and DES3 wrap
2265 algorithms and include tests cases.
2268 *) Extend CMS code to support RSA-PSS signatures and RSA-OAEP for
2272 *) Extended RSA OAEP support via EVP_PKEY API. Options to specify digest,
2273 MGF1 digest and OAEP label.
2276 *) Make openssl verify return errors.
2277 [Chris Palmer <palmer@google.com> and Ben Laurie]
2279 *) New function ASN1_TIME_diff to calculate the difference between two
2280 ASN1_TIME structures or one structure and the current time.
2283 *) Update fips_test_suite to support multiple command line options. New
2284 test to induce all self test errors in sequence and check expected
2288 *) Add FIPS_{rsa,dsa,ecdsa}_{sign,verify} functions which digest and
2289 sign or verify all in one operation.
2292 *) Add fips_algvs: a multicall fips utility incorporating all the algorithm
2293 test programs and fips_test_suite. Includes functionality to parse
2294 the minimal script output of fipsalgest.pl directly.
2297 *) Add authorisation parameter to FIPS_module_mode_set().
2300 *) Add FIPS selftest for ECDH algorithm using P-224 and B-233 curves.
2303 *) Use separate DRBG fields for internal and external flags. New function
2304 FIPS_drbg_health_check() to perform on demand health checking. Add
2305 generation tests to fips_test_suite with reduced health check interval to
2306 demonstrate periodic health checking. Add "nodh" option to
2307 fips_test_suite to skip very slow DH test.
2310 *) New function FIPS_get_cipherbynid() to lookup FIPS supported ciphers
2314 *) More extensive health check for DRBG checking many more failure modes.
2315 New function FIPS_selftest_drbg_all() to handle every possible DRBG
2316 combination: call this in fips_test_suite.
2319 *) Add support for canonical generation of DSA parameter 'g'. See
2322 *) Add support for HMAC DRBG from SP800-90. Update DRBG algorithm test and
2323 POST to handle HMAC cases.
2326 *) Add functions FIPS_module_version() and FIPS_module_version_text()
2327 to return numerical and string versions of the FIPS module number.
2330 *) Rename FIPS_mode_set and FIPS_mode to FIPS_module_mode_set and
2331 FIPS_module_mode. FIPS_mode and FIPS_mode_set will be implemented
2332 outside the validated module in the FIPS capable OpenSSL.
2335 *) Minor change to DRBG entropy callback semantics. In some cases
2336 there is no multiple of the block length between min_len and
2337 max_len. Allow the callback to return more than max_len bytes
2338 of entropy but discard any extra: it is the callback's responsibility
2339 to ensure that the extra data discarded does not impact the
2340 requested amount of entropy.
2343 *) Add PRNG security strength checks to RSA, DSA and ECDSA using
2344 information in FIPS186-3, SP800-57 and SP800-131A.
2347 *) CCM support via EVP. Interface is very similar to GCM case except we
2348 must supply all data in one chunk (i.e. no update, final) and the
2349 message length must be supplied if AAD is used. Add algorithm test
2353 *) Initial version of POST overhaul. Add POST callback to allow the status
2354 of POST to be monitored and/or failures induced. Modify fips_test_suite
2355 to use callback. Always run all selftests even if one fails.
2358 *) XTS support including algorithm test driver in the fips_gcmtest program.
2359 Note: this does increase the maximum key length from 32 to 64 bytes but
2360 there should be no binary compatibility issues as existing applications
2361 will never use XTS mode.
2364 *) Extensive reorganisation of FIPS PRNG behaviour. Remove all dependencies
2365 to OpenSSL RAND code and replace with a tiny FIPS RAND API which also
2366 performs algorithm blocking for unapproved PRNG types. Also do not
2367 set PRNG type in FIPS_mode_set(): leave this to the application.
2368 Add default OpenSSL DRBG handling: sets up FIPS PRNG and seeds with
2369 the standard OpenSSL PRNG: set additional data to a date time vector.
2372 *) Rename old X9.31 PRNG functions of the form FIPS_rand* to FIPS_x931*.
2373 This shouldn't present any incompatibility problems because applications
2374 shouldn't be using these directly and any that are will need to rethink
2375 anyway as the X9.31 PRNG is now deprecated by FIPS 140-2
2378 *) Extensive self tests and health checking required by SP800-90 DRBG.
2379 Remove strength parameter from FIPS_drbg_instantiate and always
2380 instantiate at maximum supported strength.
2383 *) Add ECDH code to fips module and fips_ecdhvs for primitives only testing.
2386 *) New algorithm test program fips_dhvs to handle DH primitives only testing.
2389 *) New function DH_compute_key_padded() to compute a DH key and pad with
2390 leading zeroes if needed: this complies with SP800-56A et al.
2393 *) Initial implementation of SP800-90 DRBGs for Hash and CTR. Not used by
2394 anything, incomplete, subject to change and largely untested at present.
2397 *) Modify fipscanisteronly build option to only build the necessary object
2398 files by filtering FIPS_EX_OBJ through a perl script in crypto/Makefile.
2401 *) Add experimental option FIPSSYMS to give all symbols in
2402 fipscanister.o and FIPS or fips prefix. This will avoid
2403 conflicts with future versions of OpenSSL. Add perl script
2404 util/fipsas.pl to preprocess assembly language source files
2405 and rename any affected symbols.
2408 *) Add selftest checks and algorithm block of non-fips algorithms in
2409 FIPS mode. Remove DES2 from selftests.
2412 *) Add ECDSA code to fips module. Add tiny fips_ecdsa_check to just
2413 return internal method without any ENGINE dependencies. Add new
2414 tiny fips sign and verify functions.
2417 *) New build option no-ec2m to disable characteristic 2 code.
2420 *) New build option "fipscanisteronly". This only builds fipscanister.o
2421 and (currently) associated fips utilities. Uses the file Makefile.fips
2422 instead of Makefile.org as the prototype.
2425 *) Add some FIPS mode restrictions to GCM. Add internal IV generator.
2426 Update fips_gcmtest to use IV generator.
2429 *) Initial, experimental EVP support for AES-GCM. AAD can be input by
2430 setting output buffer to NULL. The *Final function must be
2431 called although it will not retrieve any additional data. The tag
2432 can be set or retrieved with a ctrl. The IV length is by default 12
2433 bytes (96 bits) but can be set to an alternative value. If the IV
2434 length exceeds the maximum IV length (currently 16 bytes) it cannot be
2438 *) New flag in ciphers: EVP_CIPH_FLAG_CUSTOM_CIPHER. This means the
2439 underlying do_cipher function handles all cipher semantics itself
2440 including padding and finalisation. This is useful if (for example)
2441 an ENGINE cipher handles block padding itself. The behaviour of
2442 do_cipher is subtly changed if this flag is set: the return value
2443 is the number of characters written to the output buffer (zero is
2444 no longer an error code) or a negative error code. Also if the
2445 input buffer is NULL and length 0 finalisation should be performed.
2448 *) If a candidate issuer certificate is already part of the constructed
2449 path ignore it: new debug notification X509_V_ERR_PATH_LOOP for this case.
2452 *) Improve forward-security support: add functions
2454 void SSL_CTX_set_not_resumable_session_callback(SSL_CTX *ctx, int (*cb)(SSL *ssl, int is_forward_secure))
2455 void SSL_set_not_resumable_session_callback(SSL *ssl, int (*cb)(SSL *ssl, int is_forward_secure))
2457 for use by SSL/TLS servers; the callback function will be called whenever a
2458 new session is created, and gets to decide whether the session may be
2459 cached to make it resumable (return 0) or not (return 1). (As by the
2460 SSL/TLS protocol specifications, the session_id sent by the server will be
2461 empty to indicate that the session is not resumable; also, the server will
2462 not generate RFC 4507 (RFC 5077) session tickets.)
2464 A simple reasonable callback implementation is to return is_forward_secure.
2465 This parameter will be set to 1 or 0 depending on the ciphersuite selected
2466 by the SSL/TLS server library, indicating whether it can provide forward
2468 [Emilia Käsper <emilia.kasper@esat.kuleuven.be> (Google)]
2470 *) New -verify_name option in command line utilities to set verification
2474 *) Initial CMAC implementation. WARNING: EXPERIMENTAL, API MAY CHANGE.
2475 Add CMAC pkey methods.
2478 *) Experimental renegotiation in s_server -www mode. If the client
2479 browses /reneg connection is renegotiated. If /renegcert it is
2480 renegotiated requesting a certificate.
2483 *) Add an "external" session cache for debugging purposes to s_server. This
2484 should help trace issues which normally are only apparent in deployed
2485 multi-process servers.
2488 *) Extensive audit of libcrypto with DEBUG_UNUSED. Fix many cases where
2489 return value is ignored. NB. The functions RAND_add(), RAND_seed(),
2490 BIO_set_cipher() and some obscure PEM functions were changed so they
2491 can now return an error. The RAND changes required a change to the
2492 RAND_METHOD structure.
2495 *) New macro __owur for "OpenSSL Warn Unused Result". This makes use of
2496 a gcc attribute to warn if the result of a function is ignored. This
2497 is enable if DEBUG_UNUSED is set. Add to several functions in evp.h
2498 whose return value is often ignored.
2501 *) New -noct, -requestct, -requirect and -ctlogfile options for s_client.
2502 These allow SCTs (signed certificate timestamps) to be requested and
2503 validated when establishing a connection.
2504 [Rob Percival <robpercival@google.com>]
2506 Changes between 1.0.2g and 1.0.2h [3 May 2016]
2508 *) Prevent padding oracle in AES-NI CBC MAC check
2510 A MITM attacker can use a padding oracle attack to decrypt traffic
2511 when the connection uses an AES CBC cipher and the server support
2514 This issue was introduced as part of the fix for Lucky 13 padding
2515 attack (CVE-2013-0169). The padding check was rewritten to be in
2516 constant time by making sure that always the same bytes are read and
2517 compared against either the MAC or padding bytes. But it no longer
2518 checked that there was enough data to have both the MAC and padding
2521 This issue was reported by Juraj Somorovsky using TLS-Attacker.
2525 *) Fix EVP_EncodeUpdate overflow
2527 An overflow can occur in the EVP_EncodeUpdate() function which is used for
2528 Base64 encoding of binary data. If an attacker is able to supply very large
2529 amounts of input data then a length check can overflow resulting in a heap
2532 Internally to OpenSSL the EVP_EncodeUpdate() function is primarily used by
2533 the PEM_write_bio* family of functions. These are mainly used within the
2534 OpenSSL command line applications, so any application which processes data
2535 from an untrusted source and outputs it as a PEM file should be considered
2536 vulnerable to this issue. User applications that call these APIs directly
2537 with large amounts of untrusted data may also be vulnerable.
2539 This issue was reported by Guido Vranken.
2543 *) Fix EVP_EncryptUpdate overflow
2545 An overflow can occur in the EVP_EncryptUpdate() function. If an attacker
2546 is able to supply very large amounts of input data after a previous call to
2547 EVP_EncryptUpdate() with a partial block then a length check can overflow
2548 resulting in a heap corruption. Following an analysis of all OpenSSL
2549 internal usage of the EVP_EncryptUpdate() function all usage is one of two
2550 forms. The first form is where the EVP_EncryptUpdate() call is known to be
2551 the first called function after an EVP_EncryptInit(), and therefore that
2552 specific call must be safe. The second form is where the length passed to
2553 EVP_EncryptUpdate() can be seen from the code to be some small value and
2554 therefore there is no possibility of an overflow. Since all instances are
2555 one of these two forms, it is believed that there can be no overflows in
2556 internal code due to this problem. It should be noted that
2557 EVP_DecryptUpdate() can call EVP_EncryptUpdate() in certain code paths.
2558 Also EVP_CipherUpdate() is a synonym for EVP_EncryptUpdate(). All instances
2559 of these calls have also been analysed too and it is believed there are no
2560 instances in internal usage where an overflow could occur.
2562 This issue was reported by Guido Vranken.
2566 *) Prevent ASN.1 BIO excessive memory allocation
2568 When ASN.1 data is read from a BIO using functions such as d2i_CMS_bio()
2569 a short invalid encoding can cause allocation of large amounts of memory
2570 potentially consuming excessive resources or exhausting memory.
2572 Any application parsing untrusted data through d2i BIO functions is
2573 affected. The memory based functions such as d2i_X509() are *not* affected.
2574 Since the memory based functions are used by the TLS library, TLS
2575 applications are not affected.
2577 This issue was reported by Brian Carpenter.
2583 ASN1 Strings that are over 1024 bytes can cause an overread in applications
2584 using the X509_NAME_oneline() function on EBCDIC systems. This could result
2585 in arbitrary stack data being returned in the buffer.
2587 This issue was reported by Guido Vranken.
2591 *) Modify behavior of ALPN to invoke callback after SNI/servername
2592 callback, such that updates to the SSL_CTX affect ALPN.
2595 *) Remove LOW from the DEFAULT cipher list. This removes singles DES from the
2599 *) Only remove the SSLv2 methods with the no-ssl2-method option. When the
2600 methods are enabled and ssl2 is disabled the methods return NULL.
2603 Changes between 1.0.2f and 1.0.2g [1 Mar 2016]
2605 * Disable weak ciphers in SSLv3 and up in default builds of OpenSSL.
2606 Builds that are not configured with "enable-weak-ssl-ciphers" will not
2607 provide any "EXPORT" or "LOW" strength ciphers.
2610 * Disable SSLv2 default build, default negotiation and weak ciphers. SSLv2
2611 is by default disabled at build-time. Builds that are not configured with
2612 "enable-ssl2" will not support SSLv2. Even if "enable-ssl2" is used,
2613 users who want to negotiate SSLv2 via the version-flexible SSLv23_method()
2614 will need to explicitly call either of:
2616 SSL_CTX_clear_options(ctx, SSL_OP_NO_SSLv2);
2618 SSL_clear_options(ssl, SSL_OP_NO_SSLv2);
2620 as appropriate. Even if either of those is used, or the application
2621 explicitly uses the version-specific SSLv2_method() or its client and
2622 server variants, SSLv2 ciphers vulnerable to exhaustive search key
2623 recovery have been removed. Specifically, the SSLv2 40-bit EXPORT
2624 ciphers, and SSLv2 56-bit DES are no longer available.
2628 *) Fix a double-free in DSA code
2630 A double free bug was discovered when OpenSSL parses malformed DSA private
2631 keys and could lead to a DoS attack or memory corruption for applications
2632 that receive DSA private keys from untrusted sources. This scenario is
2635 This issue was reported to OpenSSL by Adam Langley(Google/BoringSSL) using
2640 *) Disable SRP fake user seed to address a server memory leak.
2642 Add a new method SRP_VBASE_get1_by_user that handles the seed properly.
2644 SRP_VBASE_get_by_user had inconsistent memory management behaviour.
2645 In order to fix an unavoidable memory leak, SRP_VBASE_get_by_user
2646 was changed to ignore the "fake user" SRP seed, even if the seed
2649 Users should use SRP_VBASE_get1_by_user instead. Note that in
2650 SRP_VBASE_get1_by_user, caller must free the returned value. Note
2651 also that even though configuring the SRP seed attempts to hide
2652 invalid usernames by continuing the handshake with fake
2653 credentials, this behaviour is not constant time and no strong
2654 guarantees are made that the handshake is indistinguishable from
2655 that of a valid user.
2659 *) Fix BN_hex2bn/BN_dec2bn NULL pointer deref/heap corruption
2661 In the BN_hex2bn function the number of hex digits is calculated using an
2662 int value |i|. Later |bn_expand| is called with a value of |i * 4|. For
2663 large values of |i| this can result in |bn_expand| not allocating any
2664 memory because |i * 4| is negative. This can leave the internal BIGNUM data
2665 field as NULL leading to a subsequent NULL ptr deref. For very large values
2666 of |i|, the calculation |i * 4| could be a positive value smaller than |i|.
2667 In this case memory is allocated to the internal BIGNUM data field, but it
2668 is insufficiently sized leading to heap corruption. A similar issue exists
2669 in BN_dec2bn. This could have security consequences if BN_hex2bn/BN_dec2bn
2670 is ever called by user applications with very large untrusted hex/dec data.
2671 This is anticipated to be a rare occurrence.
2673 All OpenSSL internal usage of these functions use data that is not expected
2674 to be untrusted, e.g. config file data or application command line
2675 arguments. If user developed applications generate config file data based
2676 on untrusted data then it is possible that this could also lead to security
2677 consequences. This is also anticipated to be rare.
2679 This issue was reported to OpenSSL by Guido Vranken.
2683 *) Fix memory issues in BIO_*printf functions
2685 The internal |fmtstr| function used in processing a "%s" format string in
2686 the BIO_*printf functions could overflow while calculating the length of a
2687 string and cause an OOB read when printing very long strings.
2689 Additionally the internal |doapr_outch| function can attempt to write to an
2690 OOB memory location (at an offset from the NULL pointer) in the event of a
2691 memory allocation failure. In 1.0.2 and below this could be caused where
2692 the size of a buffer to be allocated is greater than INT_MAX. E.g. this
2693 could be in processing a very long "%s" format string. Memory leaks can
2696 The first issue may mask the second issue dependent on compiler behaviour.
2697 These problems could enable attacks where large amounts of untrusted data
2698 is passed to the BIO_*printf functions. If applications use these functions
2699 in this way then they could be vulnerable. OpenSSL itself uses these
2700 functions when printing out human-readable dumps of ASN.1 data. Therefore
2701 applications that print this data could be vulnerable if the data is from
2702 untrusted sources. OpenSSL command line applications could also be
2703 vulnerable where they print out ASN.1 data, or if untrusted data is passed
2704 as command line arguments.
2706 Libssl is not considered directly vulnerable. Additionally certificates etc
2707 received via remote connections via libssl are also unlikely to be able to
2708 trigger these issues because of message size limits enforced within libssl.
2710 This issue was reported to OpenSSL Guido Vranken.
2714 *) Side channel attack on modular exponentiation
2716 A side-channel attack was found which makes use of cache-bank conflicts on
2717 the Intel Sandy-Bridge microarchitecture which could lead to the recovery
2718 of RSA keys. The ability to exploit this issue is limited as it relies on
2719 an attacker who has control of code in a thread running on the same
2720 hyper-threaded core as the victim thread which is performing decryptions.
2722 This issue was reported to OpenSSL by Yuval Yarom, The University of
2723 Adelaide and NICTA, Daniel Genkin, Technion and Tel Aviv University, and
2724 Nadia Heninger, University of Pennsylvania with more information at
2725 http://cachebleed.info.
2729 *) Change the req app to generate a 2048-bit RSA/DSA key by default,
2730 if no keysize is specified with default_bits. This fixes an
2731 omission in an earlier change that changed all RSA/DSA key generation
2732 apps to use 2048 bits by default.
2735 Changes between 1.0.2e and 1.0.2f [28 Jan 2016]
2736 *) DH small subgroups
2738 Historically OpenSSL only ever generated DH parameters based on "safe"
2739 primes. More recently (in version 1.0.2) support was provided for
2740 generating X9.42 style parameter files such as those required for RFC 5114
2741 support. The primes used in such files may not be "safe". Where an
2742 application is using DH configured with parameters based on primes that are
2743 not "safe" then an attacker could use this fact to find a peer's private
2744 DH exponent. This attack requires that the attacker complete multiple
2745 handshakes in which the peer uses the same private DH exponent. For example
2746 this could be used to discover a TLS server's private DH exponent if it's
2747 reusing the private DH exponent or it's using a static DH ciphersuite.
2749 OpenSSL provides the option SSL_OP_SINGLE_DH_USE for ephemeral DH (DHE) in
2750 TLS. It is not on by default. If the option is not set then the server
2751 reuses the same private DH exponent for the life of the server process and
2752 would be vulnerable to this attack. It is believed that many popular
2753 applications do set this option and would therefore not be at risk.
2755 The fix for this issue adds an additional check where a "q" parameter is
2756 available (as is the case in X9.42 based parameters). This detects the
2757 only known attack, and is the only possible defense for static DH
2758 ciphersuites. This could have some performance impact.
2760 Additionally the SSL_OP_SINGLE_DH_USE option has been switched on by
2761 default and cannot be disabled. This could have some performance impact.
2763 This issue was reported to OpenSSL by Antonio Sanso (Adobe).
2767 *) SSLv2 doesn't block disabled ciphers
2769 A malicious client can negotiate SSLv2 ciphers that have been disabled on
2770 the server and complete SSLv2 handshakes even if all SSLv2 ciphers have
2771 been disabled, provided that the SSLv2 protocol was not also disabled via
2774 This issue was reported to OpenSSL on 26th December 2015 by Nimrod Aviram
2775 and Sebastian Schinzel.
2779 Changes between 1.0.2d and 1.0.2e [3 Dec 2015]
2781 *) BN_mod_exp may produce incorrect results on x86_64
2783 There is a carry propagating bug in the x86_64 Montgomery squaring
2784 procedure. No EC algorithms are affected. Analysis suggests that attacks
2785 against RSA and DSA as a result of this defect would be very difficult to
2786 perform and are not believed likely. Attacks against DH are considered just
2787 feasible (although very difficult) because most of the work necessary to
2788 deduce information about a private key may be performed offline. The amount
2789 of resources required for such an attack would be very significant and
2790 likely only accessible to a limited number of attackers. An attacker would
2791 additionally need online access to an unpatched system using the target
2792 private key in a scenario with persistent DH parameters and a private
2793 key that is shared between multiple clients. For example this can occur by
2794 default in OpenSSL DHE based SSL/TLS ciphersuites.
2796 This issue was reported to OpenSSL by Hanno Böck.
2800 *) Certificate verify crash with missing PSS parameter
2802 The signature verification routines will crash with a NULL pointer
2803 dereference if presented with an ASN.1 signature using the RSA PSS
2804 algorithm and absent mask generation function parameter. Since these
2805 routines are used to verify certificate signature algorithms this can be
2806 used to crash any certificate verification operation and exploited in a
2807 DoS attack. Any application which performs certificate verification is
2808 vulnerable including OpenSSL clients and servers which enable client
2811 This issue was reported to OpenSSL by Loïc Jonas Etienne (Qnective AG).
2815 *) X509_ATTRIBUTE memory leak
2817 When presented with a malformed X509_ATTRIBUTE structure OpenSSL will leak
2818 memory. This structure is used by the PKCS#7 and CMS routines so any
2819 application which reads PKCS#7 or CMS data from untrusted sources is
2820 affected. SSL/TLS is not affected.
2822 This issue was reported to OpenSSL by Adam Langley (Google/BoringSSL) using
2827 *) Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs.
2828 This changes the decoding behaviour for some invalid messages,
2829 though the change is mostly in the more lenient direction, and
2830 legacy behaviour is preserved as much as possible.
2833 *) In DSA_generate_parameters_ex, if the provided seed is too short,
2835 [Rich Salz and Ismo Puustinen <ismo.puustinen@intel.com>]
2837 Changes between 1.0.2c and 1.0.2d [9 Jul 2015]
2839 *) Alternate chains certificate forgery
2841 During certificate verification, OpenSSL will attempt to find an
2842 alternative certificate chain if the first attempt to build such a chain
2843 fails. An error in the implementation of this logic can mean that an
2844 attacker could cause certain checks on untrusted certificates to be
2845 bypassed, such as the CA flag, enabling them to use a valid leaf
2846 certificate to act as a CA and "issue" an invalid certificate.
2848 This issue was reported to OpenSSL by Adam Langley/David Benjamin
2852 Changes between 1.0.2b and 1.0.2c [12 Jun 2015]
2854 *) Fix HMAC ABI incompatibility. The previous version introduced an ABI
2855 incompatibility in the handling of HMAC. The previous ABI has now been
2859 Changes between 1.0.2a and 1.0.2b [11 Jun 2015]
2861 *) Malformed ECParameters causes infinite loop
2863 When processing an ECParameters structure OpenSSL enters an infinite loop
2864 if the curve specified is over a specially malformed binary polynomial
2867 This can be used to perform denial of service against any
2868 system which processes public keys, certificate requests or
2869 certificates. This includes TLS clients and TLS servers with
2870 client authentication enabled.
2872 This issue was reported to OpenSSL by Joseph Barr-Pixton.
2876 *) Exploitable out-of-bounds read in X509_cmp_time
2878 X509_cmp_time does not properly check the length of the ASN1_TIME
2879 string and can read a few bytes out of bounds. In addition,
2880 X509_cmp_time accepts an arbitrary number of fractional seconds in the
2883 An attacker can use this to craft malformed certificates and CRLs of
2884 various sizes and potentially cause a segmentation fault, resulting in
2885 a DoS on applications that verify certificates or CRLs. TLS clients
2886 that verify CRLs are affected. TLS clients and servers with client
2887 authentication enabled may be affected if they use custom verification
2890 This issue was reported to OpenSSL by Robert Swiecki (Google), and
2891 independently by Hanno Böck.
2895 *) PKCS7 crash with missing EnvelopedContent
2897 The PKCS#7 parsing code does not handle missing inner EncryptedContent
2898 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs
2899 with missing content and trigger a NULL pointer dereference on parsing.
2901 Applications that decrypt PKCS#7 data or otherwise parse PKCS#7
2902 structures from untrusted sources are affected. OpenSSL clients and
2903 servers are not affected.
2905 This issue was reported to OpenSSL by Michal Zalewski (Google).
2909 *) CMS verify infinite loop with unknown hash function
2911 When verifying a signedData message the CMS code can enter an infinite loop
2912 if presented with an unknown hash function OID. This can be used to perform
2913 denial of service against any system which verifies signedData messages using
2915 This issue was reported to OpenSSL by Johannes Bauer.
2919 *) Race condition handling NewSessionTicket
2921 If a NewSessionTicket is received by a multi-threaded client when attempting to
2922 reuse a previous ticket then a race condition can occur potentially leading to
2923 a double free of the ticket data.
2927 *) Only support 256-bit or stronger elliptic curves with the
2928 'ecdh_auto' setting (server) or by default (client). Of supported
2929 curves, prefer P-256 (both).
2932 Changes between 1.0.2 and 1.0.2a [19 Mar 2015]
2934 *) ClientHello sigalgs DoS fix
2936 If a client connects to an OpenSSL 1.0.2 server and renegotiates with an
2937 invalid signature algorithms extension a NULL pointer dereference will
2938 occur. This can be exploited in a DoS attack against the server.
2940 This issue was was reported to OpenSSL by David Ramos of Stanford
2943 [Stephen Henson and Matt Caswell]
2945 *) Multiblock corrupted pointer fix
2947 OpenSSL 1.0.2 introduced the "multiblock" performance improvement. This
2948 feature only applies on 64 bit x86 architecture platforms that support AES
2949 NI instructions. A defect in the implementation of "multiblock" can cause
2950 OpenSSL's internal write buffer to become incorrectly set to NULL when
2951 using non-blocking IO. Typically, when the user application is using a
2952 socket BIO for writing, this will only result in a failed connection.
2953 However if some other BIO is used then it is likely that a segmentation
2954 fault will be triggered, thus enabling a potential DoS attack.
2956 This issue was reported to OpenSSL by Daniel Danner and Rainer Mueller.
2960 *) Segmentation fault in DTLSv1_listen fix
2962 The DTLSv1_listen function is intended to be stateless and processes the
2963 initial ClientHello from many peers. It is common for user code to loop
2964 over the call to DTLSv1_listen until a valid ClientHello is received with
2965 an associated cookie. A defect in the implementation of DTLSv1_listen means
2966 that state is preserved in the SSL object from one invocation to the next
2967 that can lead to a segmentation fault. Errors processing the initial
2968 ClientHello can trigger this scenario. An example of such an error could be
2969 that a DTLS1.0 only client is attempting to connect to a DTLS1.2 only
2972 This issue was reported to OpenSSL by Per Allansson.
2976 *) Segmentation fault in ASN1_TYPE_cmp fix
2978 The function ASN1_TYPE_cmp will crash with an invalid read if an attempt is
2979 made to compare ASN.1 boolean types. Since ASN1_TYPE_cmp is used to check
2980 certificate signature algorithm consistency this can be used to crash any
2981 certificate verification operation and exploited in a DoS attack. Any
2982 application which performs certificate verification is vulnerable including
2983 OpenSSL clients and servers which enable client authentication.
2987 *) Segmentation fault for invalid PSS parameters fix
2989 The signature verification routines will crash with a NULL pointer
2990 dereference if presented with an ASN.1 signature using the RSA PSS
2991 algorithm and invalid parameters. Since these routines are used to verify
2992 certificate signature algorithms this can be used to crash any
2993 certificate verification operation and exploited in a DoS attack. Any
2994 application which performs certificate verification is vulnerable including
2995 OpenSSL clients and servers which enable client authentication.
2997 This issue was was reported to OpenSSL by Brian Carpenter.
3001 *) ASN.1 structure reuse memory corruption fix
3003 Reusing a structure in ASN.1 parsing may allow an attacker to cause
3004 memory corruption via an invalid write. Such reuse is and has been
3005 strongly discouraged and is believed to be rare.
3007 Applications that parse structures containing CHOICE or ANY DEFINED BY
3008 components may be affected. Certificate parsing (d2i_X509 and related
3009 functions) are however not affected. OpenSSL clients and servers are
3014 *) PKCS7 NULL pointer dereferences fix
3016 The PKCS#7 parsing code does not handle missing outer ContentInfo
3017 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with
3018 missing content and trigger a NULL pointer dereference on parsing.
3020 Applications that verify PKCS#7 signatures, decrypt PKCS#7 data or
3021 otherwise parse PKCS#7 structures from untrusted sources are
3022 affected. OpenSSL clients and servers are not affected.
3024 This issue was reported to OpenSSL by Michal Zalewski (Google).
3028 *) DoS via reachable assert in SSLv2 servers fix
3030 A malicious client can trigger an OPENSSL_assert (i.e., an abort) in
3031 servers that both support SSLv2 and enable export cipher suites by sending
3032 a specially crafted SSLv2 CLIENT-MASTER-KEY message.
3034 This issue was discovered by Sean Burford (Google) and Emilia Käsper
3035 (OpenSSL development team).
3039 *) Empty CKE with client auth and DHE fix
3041 If client auth is used then a server can seg fault in the event of a DHE
3042 ciphersuite being selected and a zero length ClientKeyExchange message
3043 being sent by the client. This could be exploited in a DoS attack.
3047 *) Handshake with unseeded PRNG fix
3049 Under certain conditions an OpenSSL 1.0.2 client can complete a handshake
3050 with an unseeded PRNG. The conditions are:
3051 - The client is on a platform where the PRNG has not been seeded
3052 automatically, and the user has not seeded manually
3053 - A protocol specific client method version has been used (i.e. not
3054 SSL_client_methodv23)
3055 - A ciphersuite is used that does not require additional random data from
3056 the PRNG beyond the initial ClientHello client random (e.g. PSK-RC4-SHA).
3058 If the handshake succeeds then the client random that has been used will
3059 have been generated from a PRNG with insufficient entropy and therefore the
3060 output may be predictable.
3062 For example using the following command with an unseeded openssl will
3063 succeed on an unpatched platform:
3065 openssl s_client -psk 1a2b3c4d -tls1_2 -cipher PSK-RC4-SHA
3069 *) Use After Free following d2i_ECPrivatekey error fix
3071 A malformed EC private key file consumed via the d2i_ECPrivateKey function
3072 could cause a use after free condition. This, in turn, could cause a double
3073 free in several private key parsing functions (such as d2i_PrivateKey
3074 or EVP_PKCS82PKEY) and could lead to a DoS attack or memory corruption
3075 for applications that receive EC private keys from untrusted
3076 sources. This scenario is considered rare.
3078 This issue was discovered by the BoringSSL project and fixed in their
3083 *) X509_to_X509_REQ NULL pointer deref fix
3085 The function X509_to_X509_REQ will crash with a NULL pointer dereference if
3086 the certificate key is invalid. This function is rarely used in practice.
3088 This issue was discovered by Brian Carpenter.
3092 *) Removed the export ciphers from the DEFAULT ciphers
3095 Changes between 1.0.1l and 1.0.2 [22 Jan 2015]
3097 *) Facilitate "universal" ARM builds targeting range of ARM ISAs, e.g.
3098 ARMv5 through ARMv8, as opposite to "locking" it to single one.
3099 So far those who have to target multiple platforms would compromise
3100 and argue that binary targeting say ARMv5 would still execute on
3101 ARMv8. "Universal" build resolves this compromise by providing
3102 near-optimal performance even on newer platforms.
3105 *) Accelerated NIST P-256 elliptic curve implementation for x86_64
3106 (other platforms pending).
3107 [Shay Gueron & Vlad Krasnov (Intel Corp), Andy Polyakov]
3109 *) Add support for the SignedCertificateTimestampList certificate and
3110 OCSP response extensions from RFC6962.
3113 *) Fix ec_GFp_simple_points_make_affine (thus, EC_POINTs_mul etc.)
3114 for corner cases. (Certain input points at infinity could lead to
3115 bogus results, with non-infinity inputs mapped to infinity too.)
3118 *) Initial support for PowerISA 2.0.7, first implemented in POWER8.
3119 This covers AES, SHA256/512 and GHASH. "Initial" means that most
3120 common cases are optimized and there still is room for further
3121 improvements. Vector Permutation AES for Altivec is also added.
3124 *) Add support for little-endian ppc64 Linux target.
3125 [Marcelo Cerri (IBM)]
3127 *) Initial support for AMRv8 ISA crypto extensions. This covers AES,
3128 SHA1, SHA256 and GHASH. "Initial" means that most common cases
3129 are optimized and there still is room for further improvements.
3130 Both 32- and 64-bit modes are supported.
3131 [Andy Polyakov, Ard Biesheuvel (Linaro)]
3133 *) Improved ARMv7 NEON support.
3136 *) Support for SPARC Architecture 2011 crypto extensions, first
3137 implemented in SPARC T4. This covers AES, DES, Camellia, SHA1,
3138 SHA256/512, MD5, GHASH and modular exponentiation.
3139 [Andy Polyakov, David Miller]
3141 *) Accelerated modular exponentiation for Intel processors, a.k.a.
3143 [Shay Gueron & Vlad Krasnov (Intel Corp)]
3145 *) Support for new and upcoming Intel processors, including AVX2,
3146 BMI and SHA ISA extensions. This includes additional "stitched"
3147 implementations, AESNI-SHA256 and GCM, and multi-buffer support
3150 This work was sponsored by Intel Corp.
3153 *) Support for DTLS 1.2. This adds two sets of DTLS methods: DTLS_*_method()
3154 supports both DTLS 1.2 and 1.0 and should use whatever version the peer
3155 supports and DTLSv1_2_*_method() which supports DTLS 1.2 only.
3158 *) Use algorithm specific chains in SSL_CTX_use_certificate_chain_file():
3159 this fixes a limitation in previous versions of OpenSSL.
3162 *) Extended RSA OAEP support via EVP_PKEY API. Options to specify digest,
3163 MGF1 digest and OAEP label.
3166 *) Add EVP support for key wrapping algorithms, to avoid problems with
3167 existing code the flag EVP_CIPHER_CTX_WRAP_ALLOW has to be set in
3168 the EVP_CIPHER_CTX or an error is returned. Add AES and DES3 wrap
3169 algorithms and include tests cases.
3172 *) Add functions to allocate and set the fields of an ECDSA_METHOD
3174 [Douglas E. Engert, Steve Henson]
3176 *) New functions OPENSSL_gmtime_diff and ASN1_TIME_diff to find the
3177 difference in days and seconds between two tm or ASN1_TIME structures.
3180 *) Add -rev test option to s_server to just reverse order of characters
3181 received by client and send back to server. Also prints an abbreviated
3182 summary of the connection parameters.
3185 *) New option -brief for s_client and s_server to print out a brief summary
3186 of connection parameters.
3189 *) Add callbacks for arbitrary TLS extensions.
3190 [Trevor Perrin <trevp@trevp.net> and Ben Laurie]
3192 *) New option -crl_download in several openssl utilities to download CRLs
3193 from CRLDP extension in certificates.
3196 *) New options -CRL and -CRLform for s_client and s_server for CRLs.
3199 *) New function X509_CRL_diff to generate a delta CRL from the difference
3200 of two full CRLs. Add support to "crl" utility.
3203 *) New functions to set lookup_crls function and to retrieve
3204 X509_STORE from X509_STORE_CTX.
3207 *) Print out deprecated issuer and subject unique ID fields in
3211 *) Extend OCSP I/O functions so they can be used for simple general purpose
3212 HTTP as well as OCSP. New wrapper function which can be used to download
3213 CRLs using the OCSP API.
3216 *) Delegate command line handling in s_client/s_server to SSL_CONF APIs.
3219 *) SSL_CONF* functions. These provide a common framework for application
3220 configuration using configuration files or command lines.
3223 *) SSL/TLS tracing code. This parses out SSL/TLS records using the
3224 message callback and prints the results. Needs compile time option
3225 "enable-ssl-trace". New options to s_client and s_server to enable
3229 *) New ctrl and macro to retrieve supported points extensions.
3230 Print out extension in s_server and s_client.
3233 *) New functions to retrieve certificate signature and signature
3237 *) Add functions to retrieve and manipulate the raw cipherlist sent by a
3241 *) New Suite B modes for TLS code. These use and enforce the requirements
3242 of RFC6460: restrict ciphersuites, only permit Suite B algorithms and
3243 only use Suite B curves. The Suite B modes can be set by using the
3244 strings "SUITEB128", "SUITEB192" or "SUITEB128ONLY" for the cipherstring.
3247 *) New chain verification flags for Suite B levels of security. Check
3248 algorithms are acceptable when flags are set in X509_verify_cert.
3251 *) Make tls1_check_chain return a set of flags indicating checks passed
3252 by a certificate chain. Add additional tests to handle client
3253 certificates: checks for matching certificate type and issuer name
3257 *) If an attempt is made to use a signature algorithm not in the peer
3258 preference list abort the handshake. If client has no suitable
3259 signature algorithms in response to a certificate request do not
3260 use the certificate.
3263 *) If server EC tmp key is not in client preference list abort handshake.
3266 *) Add support for certificate stores in CERT structure. This makes it
3267 possible to have different stores per SSL structure or one store in
3268 the parent SSL_CTX. Include distinct stores for certificate chain
3269 verification and chain building. New ctrl SSL_CTRL_BUILD_CERT_CHAIN
3270 to build and store a certificate chain in CERT structure: returning
3271 an error if the chain cannot be built: this will allow applications
3272 to test if a chain is correctly configured.
3274 Note: if the CERT based stores are not set then the parent SSL_CTX
3275 store is used to retain compatibility with existing behaviour.
3279 *) New function ssl_set_client_disabled to set a ciphersuite disabled
3280 mask based on the current session, check mask when sending client
3281 hello and checking the requested ciphersuite.
3284 *) New ctrls to retrieve and set certificate types in a certificate
3285 request message. Print out received values in s_client. If certificate
3286 types is not set with custom values set sensible values based on
3287 supported signature algorithms.
3290 *) Support for distinct client and server supported signature algorithms.
3293 *) Add certificate callback. If set this is called whenever a certificate
3294 is required by client or server. An application can decide which
3295 certificate chain to present based on arbitrary criteria: for example
3296 supported signature algorithms. Add very simple example to s_server.
3297 This fixes many of the problems and restrictions of the existing client
3298 certificate callback: for example you can now clear an existing
3299 certificate and specify the whole chain.
3302 *) Add new "valid_flags" field to CERT_PKEY structure which determines what
3303 the certificate can be used for (if anything). Set valid_flags field
3304 in new tls1_check_chain function. Simplify ssl_set_cert_masks which used
3305 to have similar checks in it.
3307 Add new "cert_flags" field to CERT structure and include a "strict mode".
3308 This enforces some TLS certificate requirements (such as only permitting
3309 certificate signature algorithms contained in the supported algorithms
3310 extension) which some implementations ignore: this option should be used
3311 with caution as it could cause interoperability issues.
3314 *) Update and tidy signature algorithm extension processing. Work out
3315 shared signature algorithms based on preferences and peer algorithms
3316 and print them out in s_client and s_server. Abort handshake if no
3317 shared signature algorithms.
3320 *) Add new functions to allow customised supported signature algorithms
3321 for SSL and SSL_CTX structures. Add options to s_client and s_server
3325 *) New function SSL_certs_clear() to delete all references to certificates
3326 from an SSL structure. Before this once a certificate had been added
3327 it couldn't be removed.
3330 *) Integrate hostname, email address and IP address checking with certificate
3331 verification. New verify options supporting checking in openssl utility.
3334 *) Fixes and wildcard matching support to hostname and email checking
3335 functions. Add manual page.
3336 [Florian Weimer (Red Hat Product Security Team)]
3338 *) New functions to check a hostname email or IP address against a
3339 certificate. Add options x509 utility to print results of checks against
3343 *) Fix OCSP checking.
3344 [Rob Stradling <rob.stradling@comodo.com> and Ben Laurie]
3346 *) Initial experimental support for explicitly trusted non-root CAs.
3347 OpenSSL still tries to build a complete chain to a root but if an
3348 intermediate CA has a trust setting included that is used. The first
3349 setting is used: whether to trust (e.g., -addtrust option to the x509
3353 *) Add -trusted_first option which attempts to find certificates in the
3354 trusted store even if an untrusted chain is also supplied.
3357 *) MIPS assembly pack updates: support for MIPS32r2 and SmartMIPS ASE,
3358 platform support for Linux and Android.
3361 *) Support for linux-x32, ILP32 environment in x86_64 framework.
3364 *) Experimental multi-implementation support for FIPS capable OpenSSL.
3365 When in FIPS mode the approved implementations are used as normal,
3366 when not in FIPS mode the internal unapproved versions are used instead.
3367 This means that the FIPS capable OpenSSL isn't forced to use the
3368 (often lower performance) FIPS implementations outside FIPS mode.
3371 *) Transparently support X9.42 DH parameters when calling
3372 PEM_read_bio_DHparameters. This means existing applications can handle
3373 the new parameter format automatically.
3376 *) Initial experimental support for X9.42 DH parameter format: mainly
3377 to support use of 'q' parameter for RFC5114 parameters.
3380 *) Add DH parameters from RFC5114 including test data to dhtest.
3383 *) Support for automatic EC temporary key parameter selection. If enabled
3384 the most preferred EC parameters are automatically used instead of
3385 hardcoded fixed parameters. Now a server just has to call:
3386 SSL_CTX_set_ecdh_auto(ctx, 1) and the server will automatically
3387 support ECDH and use the most appropriate parameters.
3390 *) Enhance and tidy EC curve and point format TLS extension code. Use
3391 static structures instead of allocation if default values are used.
3392 New ctrls to set curves we wish to support and to retrieve shared curves.
3393 Print out shared curves in s_server. New options to s_server and s_client
3394 to set list of supported curves.
3397 *) New ctrls to retrieve supported signature algorithms and
3398 supported curve values as an array of NIDs. Extend openssl utility
3399 to print out received values.
3402 *) Add new APIs EC_curve_nist2nid and EC_curve_nid2nist which convert
3403 between NIDs and the more common NIST names such as "P-256". Enhance
3404 ecparam utility and ECC method to recognise the NIST names for curves.
3407 *) Enhance SSL/TLS certificate chain handling to support different
3408 chains for each certificate instead of one chain in the parent SSL_CTX.
3411 *) Support for fixed DH ciphersuite client authentication: where both
3412 server and client use DH certificates with common parameters.
3415 *) Support for fixed DH ciphersuites: those requiring DH server
3419 *) New function i2d_re_X509_tbs for re-encoding the TBS portion of
3421 Note: Related 1.0.2-beta specific macros X509_get_cert_info,
3422 X509_CINF_set_modified, X509_CINF_get_issuer, X509_CINF_get_extensions and
3423 X509_CINF_get_signature were reverted post internal team review.
3425 Changes between 1.0.1k and 1.0.1l [15 Jan 2015]
3427 *) Build fixes for the Windows and OpenVMS platforms
3428 [Matt Caswell and Richard Levitte]
3430 Changes between 1.0.1j and 1.0.1k [8 Jan 2015]
3432 *) Fix DTLS segmentation fault in dtls1_get_record. A carefully crafted DTLS
3433 message can cause a segmentation fault in OpenSSL due to a NULL pointer
3434 dereference. This could lead to a Denial Of Service attack. Thanks to
3435 Markus Stenberg of Cisco Systems, Inc. for reporting this issue.
3439 *) Fix DTLS memory leak in dtls1_buffer_record. A memory leak can occur in the
3440 dtls1_buffer_record function under certain conditions. In particular this
3441 could occur if an attacker sent repeated DTLS records with the same
3442 sequence number but for the next epoch. The memory leak could be exploited
3443 by an attacker in a Denial of Service attack through memory exhaustion.
3444 Thanks to Chris Mueller for reporting this issue.
3448 *) Fix issue where no-ssl3 configuration sets method to NULL. When openssl is
3449 built with the no-ssl3 option and a SSL v3 ClientHello is received the ssl
3450 method would be set to NULL which could later result in a NULL pointer
3451 dereference. Thanks to Frank Schmirler for reporting this issue.
3455 *) Abort handshake if server key exchange message is omitted for ephemeral
3458 Thanks to Karthikeyan Bhargavan of the PROSECCO team at INRIA for
3459 reporting this issue.
3463 *) Remove non-export ephemeral RSA code on client and server. This code
3464 violated the TLS standard by allowing the use of temporary RSA keys in
3465 non-export ciphersuites and could be used by a server to effectively
3466 downgrade the RSA key length used to a value smaller than the server
3467 certificate. Thanks for Karthikeyan Bhargavan of the PROSECCO team at
3468 INRIA or reporting this issue.
3472 *) Fixed issue where DH client certificates are accepted without verification.
3473 An OpenSSL server will accept a DH certificate for client authentication
3474 without the certificate verify message. This effectively allows a client to
3475 authenticate without the use of a private key. This only affects servers
3476 which trust a client certificate authority which issues certificates
3477 containing DH keys: these are extremely rare and hardly ever encountered.
3478 Thanks for Karthikeyan Bhargavan of the PROSECCO team at INRIA or reporting
3483 *) Ensure that the session ID context of an SSL is updated when its
3484 SSL_CTX is updated via SSL_set_SSL_CTX.
3486 The session ID context is typically set from the parent SSL_CTX,
3487 and can vary with the CTX.
3490 *) Fix various certificate fingerprint issues.
3492 By using non-DER or invalid encodings outside the signed portion of a
3493 certificate the fingerprint can be changed without breaking the signature.
3494 Although no details of the signed portion of the certificate can be changed
3495 this can cause problems with some applications: e.g. those using the
3496 certificate fingerprint for blacklists.
3498 1. Reject signatures with non zero unused bits.
3500 If the BIT STRING containing the signature has non zero unused bits reject
3501 the signature. All current signature algorithms require zero unused bits.
3503 2. Check certificate algorithm consistency.
3505 Check the AlgorithmIdentifier inside TBS matches the one in the
3506 certificate signature. NB: this will result in signature failure
3507 errors for some broken certificates.
3509 Thanks to Konrad Kraszewski from Google for reporting this issue.
3511 3. Check DSA/ECDSA signatures use DER.
3513 Re-encode DSA/ECDSA signatures and compare with the original received
3514 signature. Return an error if there is a mismatch.
3516 This will reject various cases including garbage after signature
3517 (thanks to Antti Karjalainen and Tuomo Untinen from the Codenomicon CROSS
3518 program for discovering this case) and use of BER or invalid ASN.1 INTEGERs
3519 (negative or with leading zeroes).
3521 Further analysis was conducted and fixes were developed by Stephen Henson
3522 of the OpenSSL core team.
3527 *) Correct Bignum squaring. Bignum squaring (BN_sqr) may produce incorrect
3528 results on some platforms, including x86_64. This bug occurs at random
3529 with a very low probability, and is not known to be exploitable in any
3530 way, though its exact impact is difficult to determine. Thanks to Pieter
3531 Wuille (Blockstream) who reported this issue and also suggested an initial
3532 fix. Further analysis was conducted by the OpenSSL development team and
3533 Adam Langley of Google. The final fix was developed by Andy Polyakov of
3534 the OpenSSL core team.
3538 *) Do not resume sessions on the server if the negotiated protocol
3539 version does not match the session's version. Resuming with a different
3540 version, while not strictly forbidden by the RFC, is of questionable
3541 sanity and breaks all known clients.
3542 [David Benjamin, Emilia Käsper]
3544 *) Tighten handling of the ChangeCipherSpec (CCS) message: reject
3545 early CCS messages during renegotiation. (Note that because
3546 renegotiation is encrypted, this early CCS was not exploitable.)
3549 *) Tighten client-side session ticket handling during renegotiation:
3550 ensure that the client only accepts a session ticket if the server sends
3551 the extension anew in the ServerHello. Previously, a TLS client would
3552 reuse the old extension state and thus accept a session ticket if one was
3553 announced in the initial ServerHello.
3555 Similarly, ensure that the client requires a session ticket if one
3556 was advertised in the ServerHello. Previously, a TLS client would
3557 ignore a missing NewSessionTicket message.
3560 Changes between 1.0.1i and 1.0.1j [15 Oct 2014]
3562 *) SRTP Memory Leak.
3564 A flaw in the DTLS SRTP extension parsing code allows an attacker, who
3565 sends a carefully crafted handshake message, to cause OpenSSL to fail
3566 to free up to 64k of memory causing a memory leak. This could be
3567 exploited in a Denial Of Service attack. This issue affects OpenSSL
3568 1.0.1 server implementations for both SSL/TLS and DTLS regardless of
3569 whether SRTP is used or configured. Implementations of OpenSSL that
3570 have been compiled with OPENSSL_NO_SRTP defined are not affected.
3572 The fix was developed by the OpenSSL team.
3576 *) Session Ticket Memory Leak.
3578 When an OpenSSL SSL/TLS/DTLS server receives a session ticket the
3579 integrity of that ticket is first verified. In the event of a session
3580 ticket integrity check failing, OpenSSL will fail to free memory
3581 causing a memory leak. By sending a large number of invalid session
3582 tickets an attacker could exploit this issue in a Denial Of Service
3587 *) Build option no-ssl3 is incomplete.
3589 When OpenSSL is configured with "no-ssl3" as a build option, servers
3590 could accept and complete a SSL 3.0 handshake, and clients could be
3591 configured to send them.
3593 [Akamai and the OpenSSL team]
3595 *) Add support for TLS_FALLBACK_SCSV.
3596 Client applications doing fallback retries should call
3597 SSL_set_mode(s, SSL_MODE_SEND_FALLBACK_SCSV).
3599 [Adam Langley, Bodo Moeller]
3601 *) Add additional DigestInfo checks.
3603 Re-encode DigestInto in DER and check against the original when
3604 verifying RSA signature: this will reject any improperly encoded
3605 DigestInfo structures.
3607 Note: this is a precautionary measure and no attacks are currently known.
3611 Changes between 1.0.1h and 1.0.1i [6 Aug 2014]
3613 *) Fix SRP buffer overrun vulnerability. Invalid parameters passed to the
3614 SRP code can be overrun an internal buffer. Add sanity check that
3615 g, A, B < N to SRP code.
3617 Thanks to Sean Devlin and Watson Ladd of Cryptography Services, NCC
3618 Group for discovering this issue.
3622 *) A flaw in the OpenSSL SSL/TLS server code causes the server to negotiate
3623 TLS 1.0 instead of higher protocol versions when the ClientHello message
3624 is badly fragmented. This allows a man-in-the-middle attacker to force a
3625 downgrade to TLS 1.0 even if both the server and the client support a
3626 higher protocol version, by modifying the client's TLS records.
3628 Thanks to David Benjamin and Adam Langley (Google) for discovering and
3629 researching this issue.
3633 *) OpenSSL DTLS clients enabling anonymous (EC)DH ciphersuites are subject
3634 to a denial of service attack. A malicious server can crash the client
3635 with a null pointer dereference (read) by specifying an anonymous (EC)DH
3636 ciphersuite and sending carefully crafted handshake messages.
3638 Thanks to Felix Gröbert (Google) for discovering and researching this
3643 *) By sending carefully crafted DTLS packets an attacker could cause openssl
3644 to leak memory. This can be exploited through a Denial of Service attack.
3645 Thanks to Adam Langley for discovering and researching this issue.
3649 *) An attacker can force openssl to consume large amounts of memory whilst
3650 processing DTLS handshake messages. This can be exploited through a
3651 Denial of Service attack.
3652 Thanks to Adam Langley for discovering and researching this issue.
3656 *) An attacker can force an error condition which causes openssl to crash
3657 whilst processing DTLS packets due to memory being freed twice. This
3658 can be exploited through a Denial of Service attack.
3659 Thanks to Adam Langley and Wan-Teh Chang for discovering and researching
3664 *) If a multithreaded client connects to a malicious server using a resumed
3665 session and the server sends an ec point format extension it could write
3666 up to 255 bytes to freed memory.
3668 Thanks to Gabor Tyukasz (LogMeIn Inc) for discovering and researching this
3673 *) A malicious server can crash an OpenSSL client with a null pointer
3674 dereference (read) by specifying an SRP ciphersuite even though it was not
3675 properly negotiated with the client. This can be exploited through a
3676 Denial of Service attack.
3678 Thanks to Joonas Kuorilehto and Riku Hietamäki (Codenomicon) for
3679 discovering and researching this issue.
3683 *) A flaw in OBJ_obj2txt may cause pretty printing functions such as
3684 X509_name_oneline, X509_name_print_ex et al. to leak some information
3685 from the stack. Applications may be affected if they echo pretty printing
3686 output to the attacker.
3688 Thanks to Ivan Fratric (Google) for discovering this issue.
3690 [Emilia Käsper, and Steve Henson]
3692 *) Fix ec_GFp_simple_points_make_affine (thus, EC_POINTs_mul etc.)
3693 for corner cases. (Certain input points at infinity could lead to
3694 bogus results, with non-infinity inputs mapped to infinity too.)
3697 Changes between 1.0.1g and 1.0.1h [5 Jun 2014]
3699 *) Fix for SSL/TLS MITM flaw. An attacker using a carefully crafted
3700 handshake can force the use of weak keying material in OpenSSL
3701 SSL/TLS clients and servers.
3703 Thanks to KIKUCHI Masashi (Lepidum Co. Ltd.) for discovering and
3704 researching this issue. (CVE-2014-0224)
3705 [KIKUCHI Masashi, Steve Henson]
3707 *) Fix DTLS recursion flaw. By sending an invalid DTLS handshake to an
3708 OpenSSL DTLS client the code can be made to recurse eventually crashing
3711 Thanks to Imre Rad (Search-Lab Ltd.) for discovering this issue.
3713 [Imre Rad, Steve Henson]
3715 *) Fix DTLS invalid fragment vulnerability. A buffer overrun attack can
3716 be triggered by sending invalid DTLS fragments to an OpenSSL DTLS
3717 client or server. This is potentially exploitable to run arbitrary
3718 code on a vulnerable client or server.
3720 Thanks to Jüri Aedla for reporting this issue. (CVE-2014-0195)
3721 [Jüri Aedla, Steve Henson]
3723 *) Fix bug in TLS code where clients enable anonymous ECDH ciphersuites
3724 are subject to a denial of service attack.
3726 Thanks to Felix Gröbert and Ivan Fratric at Google for discovering
3727 this issue. (CVE-2014-3470)
3728 [Felix Gröbert, Ivan Fratric, Steve Henson]
3730 *) Harmonize version and its documentation. -f flag is used to display
3732 [mancha <mancha1@zoho.com>]
3734 *) Fix eckey_priv_encode so it immediately returns an error upon a failure
3735 in i2d_ECPrivateKey.
3736 [mancha <mancha1@zoho.com>]
3738 *) Fix some double frees. These are not thought to be exploitable.
3739 [mancha <mancha1@zoho.com>]
3741 Changes between 1.0.1f and 1.0.1g [7 Apr 2014]
3743 *) A missing bounds check in the handling of the TLS heartbeat extension
3744 can be used to reveal up to 64k of memory to a connected client or
3747 Thanks for Neel Mehta of Google Security for discovering this bug and to
3748 Adam Langley <agl@chromium.org> and Bodo Moeller <bmoeller@acm.org> for
3749 preparing the fix (CVE-2014-0160)
3750 [Adam Langley, Bodo Moeller]
3752 *) Fix for the attack described in the paper "Recovering OpenSSL
3753 ECDSA Nonces Using the FLUSH+RELOAD Cache Side-channel Attack"
3754 by Yuval Yarom and Naomi Benger. Details can be obtained from:
3755 http://eprint.iacr.org/2014/140
3757 Thanks to Yuval Yarom and Naomi Benger for discovering this
3758 flaw and to Yuval Yarom for supplying a fix (CVE-2014-0076)
3759 [Yuval Yarom and Naomi Benger]
3761 *) TLS pad extension: draft-agl-tls-padding-03
3763 Workaround for the "TLS hang bug" (see FAQ and PR#2771): if the
3764 TLS client Hello record length value would otherwise be > 255 and
3765 less that 512 pad with a dummy extension containing zeroes so it
3766 is at least 512 bytes long.
3768 [Adam Langley, Steve Henson]
3770 Changes between 1.0.1e and 1.0.1f [6 Jan 2014]
3772 *) Fix for TLS record tampering bug. A carefully crafted invalid
3773 handshake could crash OpenSSL with a NULL pointer exception.
3774 Thanks to Anton Johansson for reporting this issues.
3777 *) Keep original DTLS digest and encryption contexts in retransmission
3778 structures so we can use the previous session parameters if they need
3779 to be resent. (CVE-2013-6450)
3782 *) Add option SSL_OP_SAFARI_ECDHE_ECDSA_BUG (part of SSL_OP_ALL) which
3783 avoids preferring ECDHE-ECDSA ciphers when the client appears to be
3784 Safari on OS X. Safari on OS X 10.8..10.8.3 advertises support for
3785 several ECDHE-ECDSA ciphers, but fails to negotiate them. The bug
3786 is fixed in OS X 10.8.4, but Apple have ruled out both hot fixing
3787 10.8..10.8.3 and forcing users to upgrade to 10.8.4 or newer.
3788 [Rob Stradling, Adam Langley]
3790 Changes between 1.0.1d and 1.0.1e [11 Feb 2013]
3792 *) Correct fix for CVE-2013-0169. The original didn't work on AES-NI
3793 supporting platforms or when small records were transferred.
3794 [Andy Polyakov, Steve Henson]
3796 Changes between 1.0.1c and 1.0.1d [5 Feb 2013]
3798 *) Make the decoding of SSLv3, TLS and DTLS CBC records constant time.
3800 This addresses the flaw in CBC record processing discovered by
3801 Nadhem Alfardan and Kenny Paterson. Details of this attack can be found
3802 at: http://www.isg.rhul.ac.uk/tls/
3804 Thanks go to Nadhem Alfardan and Kenny Paterson of the Information
3805 Security Group at Royal Holloway, University of London
3806 (www.isg.rhul.ac.uk) for discovering this flaw and Adam Langley and
3807 Emilia Käsper for the initial patch.
3809 [Emilia Käsper, Adam Langley, Ben Laurie, Andy Polyakov, Steve Henson]
3811 *) Fix flaw in AESNI handling of TLS 1.2 and 1.1 records for CBC mode
3812 ciphersuites which can be exploited in a denial of service attack.
3813 Thanks go to and to Adam Langley <agl@chromium.org> for discovering
3814 and detecting this bug and to Wolfgang Ettlinger
3815 <wolfgang.ettlinger@gmail.com> for independently discovering this issue.
3819 *) Return an error when checking OCSP signatures when key is NULL.
3820 This fixes a DoS attack. (CVE-2013-0166)
3823 *) Make openssl verify return errors.
3824 [Chris Palmer <palmer@google.com> and Ben Laurie]
3826 *) Call OCSP Stapling callback after ciphersuite has been chosen, so
3827 the right response is stapled. Also change SSL_get_certificate()
3828 so it returns the certificate actually sent.
3829 See http://rt.openssl.org/Ticket/Display.html?id=2836.
3830 [Rob Stradling <rob.stradling@comodo.com>]
3832 *) Fix possible deadlock when decoding public keys.
3835 *) Don't use TLS 1.0 record version number in initial client hello
3839 Changes between 1.0.1b and 1.0.1c [10 May 2012]
3841 *) Sanity check record length before skipping explicit IV in TLS
3842 1.2, 1.1 and DTLS to fix DoS attack.
3844 Thanks to Codenomicon for discovering this issue using Fuzz-o-Matic
3845 fuzzing as a service testing platform.
3849 *) Initialise tkeylen properly when encrypting CMS messages.
3850 Thanks to Solar Designer of Openwall for reporting this issue.
3853 *) In FIPS mode don't try to use composite ciphers as they are not
3857 Changes between 1.0.1a and 1.0.1b [26 Apr 2012]
3859 *) OpenSSL 1.0.0 sets SSL_OP_ALL to 0x80000FFFL and OpenSSL 1.0.1 and
3860 1.0.1a set SSL_OP_NO_TLSv1_1 to 0x00000400L which would unfortunately
3861 mean any application compiled against OpenSSL 1.0.0 headers setting
3862 SSL_OP_ALL would also set SSL_OP_NO_TLSv1_1, unintentionally disabling
3863 TLS 1.1 also. Fix this by changing the value of SSL_OP_NO_TLSv1_1 to
3864 0x10000000L Any application which was previously compiled against
3865 OpenSSL 1.0.1 or 1.0.1a headers and which cares about SSL_OP_NO_TLSv1_1
3866 will need to be recompiled as a result. Letting be results in
3867 inability to disable specifically TLS 1.1 and in client context,
3868 in unlike event, limit maximum offered version to TLS 1.0 [see below].
3871 *) In order to ensure interoperability SSL_OP_NO_protocolX does not
3872 disable just protocol X, but all protocols above X *if* there are
3873 protocols *below* X still enabled. In more practical terms it means
3874 that if application wants to disable TLS1.0 in favor of TLS1.1 and
3875 above, it's not sufficient to pass SSL_OP_NO_TLSv1, one has to pass
3876 SSL_OP_NO_TLSv1|SSL_OP_NO_SSLv3|SSL_OP_NO_SSLv2. This applies to
3880 Changes between 1.0.1 and 1.0.1a [19 Apr 2012]
3882 *) Check for potentially exploitable overflows in asn1_d2i_read_bio
3883 BUF_mem_grow and BUF_mem_grow_clean. Refuse attempts to shrink buffer
3884 in CRYPTO_realloc_clean.
3886 Thanks to Tavis Ormandy, Google Security Team, for discovering this
3887 issue and to Adam Langley <agl@chromium.org> for fixing it.
3889 [Adam Langley (Google), Tavis Ormandy, Google Security Team]
3891 *) Don't allow TLS 1.2 SHA-256 ciphersuites in TLS 1.0, 1.1 connections.
3894 *) Workarounds for some broken servers that "hang" if a client hello
3895 record length exceeds 255 bytes.
3897 1. Do not use record version number > TLS 1.0 in initial client
3898 hello: some (but not all) hanging servers will now work.
3899 2. If we set OPENSSL_MAX_TLS1_2_CIPHER_LENGTH this will truncate
3900 the number of ciphers sent in the client hello. This should be
3901 set to an even number, such as 50, for example by passing:
3902 -DOPENSSL_MAX_TLS1_2_CIPHER_LENGTH=50 to config or Configure.
3903 Most broken servers should now work.
3904 3. If all else fails setting OPENSSL_NO_TLS1_2_CLIENT will disable
3905 TLS 1.2 client support entirely.
3908 *) Fix SEGV in Vector Permutation AES module observed in OpenSSH.
3911 Changes between 1.0.0h and 1.0.1 [14 Mar 2012]
3913 *) Add compatibility with old MDC2 signatures which use an ASN1 OCTET
3914 STRING form instead of a DigestInfo.
3917 *) The format used for MDC2 RSA signatures is inconsistent between EVP
3918 and the RSA_sign/RSA_verify functions. This was made more apparent when
3919 OpenSSL used RSA_sign/RSA_verify for some RSA signatures in particular
3920 those which went through EVP_PKEY_METHOD in 1.0.0 and later. Detect
3921 the correct format in RSA_verify so both forms transparently work.
3924 *) Some servers which support TLS 1.0 can choke if we initially indicate
3925 support for TLS 1.2 and later renegotiate using TLS 1.0 in the RSA
3926 encrypted premaster secret. As a workaround use the maximum permitted
3927 client version in client hello, this should keep such servers happy
3928 and still work with previous versions of OpenSSL.
3931 *) Add support for TLS/DTLS heartbeats.
3932 [Robin Seggelmann <seggelmann@fh-muenster.de>]
3934 *) Add support for SCTP.
3935 [Robin Seggelmann <seggelmann@fh-muenster.de>]
3937 *) Improved PRNG seeding for VOS.
3938 [Paul Green <Paul.Green@stratus.com>]
3940 *) Extensive assembler packs updates, most notably:
3942 - x86[_64]: AES-NI, PCLMULQDQ, RDRAND support;
3943 - x86[_64]: SSSE3 support (SHA1, vector-permutation AES);
3944 - x86_64: bit-sliced AES implementation;
3945 - ARM: NEON support, contemporary platforms optimizations;
3946 - s390x: z196 support;
3947 - *: GHASH and GF(2^m) multiplication implementations;
3951 *) Make TLS-SRP code conformant with RFC 5054 API cleanup
3952 (removal of unnecessary code)
3953 [Peter Sylvester <peter.sylvester@edelweb.fr>]
3955 *) Add TLS key material exporter from RFC 5705.
3958 *) Add DTLS-SRTP negotiation from RFC 5764.
3961 *) Add Next Protocol Negotiation,
3962 http://tools.ietf.org/html/draft-agl-tls-nextprotoneg-00. Can be
3963 disabled with a no-npn flag to config or Configure. Code donated
3965 [Adam Langley <agl@google.com> and Ben Laurie]
3967 *) Add optional 64-bit optimized implementations of elliptic curves NIST-P224,
3968 NIST-P256, NIST-P521, with constant-time single point multiplication on
3969 typical inputs. Compiler support for the nonstandard type __uint128_t is
3970 required to use this (present in gcc 4.4 and later, for 64-bit builds).
3971 Code made available under Apache License version 2.0.
3973 Specify "enable-ec_nistp_64_gcc_128" on the Configure (or config) command
3974 line to include this in your build of OpenSSL, and run "make depend" (or
3975 "make update"). This enables the following EC_METHODs:
3977 EC_GFp_nistp224_method()
3978 EC_GFp_nistp256_method()
3979 EC_GFp_nistp521_method()
3981 EC_GROUP_new_by_curve_name() will automatically use these (while
3982 EC_GROUP_new_curve_GFp() currently prefers the more flexible
3984 [Emilia Käsper, Adam Langley, Bodo Moeller (Google)]
3986 *) Use type ossl_ssize_t instad of ssize_t which isn't available on
3987 all platforms. Move ssize_t definition from e_os.h to the public
3988 header file e_os2.h as it now appears in public header file cms.h
3991 *) New -sigopt option to the ca, req and x509 utilities. Additional
3992 signature parameters can be passed using this option and in
3996 *) Add RSA PSS signing function. This will generate and set the
3997 appropriate AlgorithmIdentifiers for PSS based on those in the
3998 corresponding EVP_MD_CTX structure. No application support yet.
4001 *) Support for companion algorithm specific ASN1 signing routines.
4002 New function ASN1_item_sign_ctx() signs a pre-initialised
4003 EVP_MD_CTX structure and sets AlgorithmIdentifiers based on
4004 the appropriate parameters.
4007 *) Add new algorithm specific ASN1 verification initialisation function
4008 to EVP_PKEY_ASN1_METHOD: this is not in EVP_PKEY_METHOD since the ASN1
4009 handling will be the same no matter what EVP_PKEY_METHOD is used.
4010 Add a PSS handler to support verification of PSS signatures: checked
4011 against a number of sample certificates.
4014 *) Add signature printing for PSS. Add PSS OIDs.
4015 [Steve Henson, Martin Kaiser <lists@kaiser.cx>]
4017 *) Add algorithm specific signature printing. An individual ASN1 method
4018 can now print out signatures instead of the standard hex dump.
4020 More complex signatures (e.g. PSS) can print out more meaningful
4021 information. Include DSA version that prints out the signature
4025 *) Password based recipient info support for CMS library: implementing
4029 *) Split password based encryption into PBES2 and PBKDF2 functions. This
4030 neatly separates the code into cipher and PBE sections and is required
4031 for some algorithms that split PBES2 into separate pieces (such as
4032 password based CMS).
4035 *) Session-handling fixes:
4036 - Fix handling of connections that are resuming with a session ID,
4037 but also support Session Tickets.
4038 - Fix a bug that suppressed issuing of a new ticket if the client
4039 presented a ticket with an expired session.
4040 - Try to set the ticket lifetime hint to something reasonable.
4041 - Make tickets shorter by excluding irrelevant information.
4042 - On the client side, don't ignore renewed tickets.
4043 [Adam Langley, Bodo Moeller (Google)]
4045 *) Fix PSK session representation.
4048 *) Add RC4-MD5 and AESNI-SHA1 "stitched" implementations.
4050 This work was sponsored by Intel.
4053 *) Add GCM support to TLS library. Some custom code is needed to split
4054 the IV between the fixed (from PRF) and explicit (from TLS record)
4055 portions. This adds all GCM ciphersuites supported by RFC5288 and
4056 RFC5289. Generalise some AES* cipherstrings to include GCM and
4057 add a special AESGCM string for GCM only.
4060 *) Expand range of ctrls for AES GCM. Permit setting invocation
4061 field on decrypt and retrieval of invocation field only on encrypt.
4064 *) Add HMAC ECC ciphersuites from RFC5289. Include SHA384 PRF support.
4065 As required by RFC5289 these ciphersuites cannot be used if for
4066 versions of TLS earlier than 1.2.
4069 *) For FIPS capable OpenSSL interpret a NULL default public key method
4070 as unset and return the appropriate default but do *not* set the default.
4071 This means we can return the appropriate method in applications that
4072 switch between FIPS and non-FIPS modes.
4075 *) Redirect HMAC and CMAC operations to FIPS module in FIPS mode. If an
4076 ENGINE is used then we cannot handle that in the FIPS module so we
4077 keep original code iff non-FIPS operations are allowed.
4080 *) Add -attime option to openssl utilities.
4081 [Peter Eckersley <pde@eff.org>, Ben Laurie and Steve Henson]
4083 *) Redirect DSA and DH operations to FIPS module in FIPS mode.
4086 *) Redirect ECDSA and ECDH operations to FIPS module in FIPS mode. Also use
4087 FIPS EC methods unconditionally for now.
4090 *) New build option no-ec2m to disable characteristic 2 code.
4093 *) Backport libcrypto audit of return value checking from 1.1.0-dev; not
4094 all cases can be covered as some introduce binary incompatibilities.
4097 *) Redirect RSA operations to FIPS module including keygen,
4098 encrypt, decrypt, sign and verify. Block use of non FIPS RSA methods.
4101 *) Add similar low level API blocking to ciphers.
4104 *) Low level digest APIs are not approved in FIPS mode: any attempt
4105 to use these will cause a fatal error. Applications that *really* want
4106 to use them can use the private_* version instead.
4109 *) Redirect cipher operations to FIPS module for FIPS builds.
4112 *) Redirect digest operations to FIPS module for FIPS builds.
4115 *) Update build system to add "fips" flag which will link in fipscanister.o
4116 for static and shared library builds embedding a signature if needed.
4119 *) Output TLS supported curves in preference order instead of numerical
4120 order. This is currently hardcoded for the highest order curves first.
4121 This should be configurable so applications can judge speed vs strength.
4124 *) Add TLS v1.2 server support for client authentication.
4127 *) Add support for FIPS mode in ssl library: disable SSLv3, non-FIPS ciphers
4131 *) Functions FIPS_mode_set() and FIPS_mode() which call the underlying
4132 FIPS modules versions.
4135 *) Add TLS v1.2 client side support for client authentication. Keep cache
4136 of handshake records longer as we don't know the hash algorithm to use
4137 until after the certificate request message is received.
4140 *) Initial TLS v1.2 client support. Add a default signature algorithms
4141 extension including all the algorithms we support. Parse new signature
4142 format in client key exchange. Relax some ECC signing restrictions for
4143 TLS v1.2 as indicated in RFC5246.
4146 *) Add server support for TLS v1.2 signature algorithms extension. Switch
4147 to new signature format when needed using client digest preference.
4148 All server ciphersuites should now work correctly in TLS v1.2. No client
4149 support yet and no support for client certificates.
4152 *) Initial TLS v1.2 support. Add new SHA256 digest to ssl code, switch
4153 to SHA256 for PRF when using TLS v1.2 and later. Add new SHA256 based
4154 ciphersuites. At present only RSA key exchange ciphersuites work with
4155 TLS v1.2. Add new option for TLS v1.2 replacing the old and obsolete
4156 SSL_OP_PKCS1_CHECK flags with SSL_OP_NO_TLSv1_2. New TLSv1.2 methods
4157 and version checking.
4160 *) New option OPENSSL_NO_SSL_INTERN. If an application can be compiled
4161 with this defined it will not be affected by any changes to ssl internal
4162 structures. Add several utility functions to allow openssl application
4163 to work with OPENSSL_NO_SSL_INTERN defined.
4166 *) A long standing patch to add support for SRP from EdelWeb (Peter
4167 Sylvester and Christophe Renou) was integrated.
4168 [Christophe Renou <christophe.renou@edelweb.fr>, Peter Sylvester
4169 <peter.sylvester@edelweb.fr>, Tom Wu <tjw@cs.stanford.edu>, and
4172 *) Add functions to copy EVP_PKEY_METHOD and retrieve flags and id.
4175 *) Permit abbreviated handshakes when renegotiating using the function
4176 SSL_renegotiate_abbreviated().
4177 [Robin Seggelmann <seggelmann@fh-muenster.de>]
4179 *) Add call to ENGINE_register_all_complete() to
4180 ENGINE_load_builtin_engines(), so some implementations get used
4181 automatically instead of needing explicit application support.
4184 *) Add support for TLS key exporter as described in RFC5705.
4185 [Robin Seggelmann <seggelmann@fh-muenster.de>, Steve Henson]
4187 *) Initial TLSv1.1 support. Since TLSv1.1 is very similar to TLS v1.0 only
4188 a few changes are required:
4190 Add SSL_OP_NO_TLSv1_1 flag.
4191 Add TLSv1_1 methods.
4192 Update version checking logic to handle version 1.1.
4193 Add explicit IV handling (ported from DTLS code).
4194 Add command line options to s_client/s_server.
4197 Changes between 1.0.0g and 1.0.0h [12 Mar 2012]
4199 *) Fix MMA (Bleichenbacher's attack on PKCS #1 v1.5 RSA padding) weakness
4200 in CMS and PKCS7 code. When RSA decryption fails use a random key for
4201 content decryption and always return the same error. Note: this attack
4202 needs on average 2^20 messages so it only affects automated senders. The
4203 old behaviour can be re-enabled in the CMS code by setting the
4204 CMS_DEBUG_DECRYPT flag: this is useful for debugging and testing where
4205 an MMA defence is not necessary.
4206 Thanks to Ivan Nestlerode <inestlerode@us.ibm.com> for discovering
4207 this issue. (CVE-2012-0884)
4210 *) Fix CVE-2011-4619: make sure we really are receiving a
4211 client hello before rejecting multiple SGC restarts. Thanks to
4212 Ivan Nestlerode <inestlerode@us.ibm.com> for discovering this bug.
4215 Changes between 1.0.0f and 1.0.0g [18 Jan 2012]
4217 *) Fix for DTLS DoS issue introduced by fix for CVE-2011-4109.
4218 Thanks to Antonio Martin, Enterprise Secure Access Research and
4219 Development, Cisco Systems, Inc. for discovering this bug and
4220 preparing a fix. (CVE-2012-0050)
4223 Changes between 1.0.0e and 1.0.0f [4 Jan 2012]
4225 *) Nadhem Alfardan and Kenny Paterson have discovered an extension
4226 of the Vaudenay padding oracle attack on CBC mode encryption
4227 which enables an efficient plaintext recovery attack against
4228 the OpenSSL implementation of DTLS. Their attack exploits timing
4229 differences arising during decryption processing. A research
4230 paper describing this attack can be found at:
4231 http://www.isg.rhul.ac.uk/~kp/dtls.pdf
4232 Thanks go to Nadhem Alfardan and Kenny Paterson of the Information
4233 Security Group at Royal Holloway, University of London
4234 (www.isg.rhul.ac.uk) for discovering this flaw and to Robin Seggelmann
4235 <seggelmann@fh-muenster.de> and Michael Tuexen <tuexen@fh-muenster.de>
4236 for preparing the fix. (CVE-2011-4108)
4237 [Robin Seggelmann, Michael Tuexen]
4239 *) Clear bytes used for block padding of SSL 3.0 records.
4241 [Adam Langley (Google)]
4243 *) Only allow one SGC handshake restart for SSL/TLS. Thanks to George
4244 Kadianakis <desnacked@gmail.com> for discovering this issue and
4245 Adam Langley for preparing the fix. (CVE-2011-4619)
4246 [Adam Langley (Google)]
4248 *) Check parameters are not NULL in GOST ENGINE. (CVE-2012-0027)
4249 [Andrey Kulikov <amdeich@gmail.com>]
4251 *) Prevent malformed RFC3779 data triggering an assertion failure.
4252 Thanks to Andrew Chi, BBN Technologies, for discovering the flaw
4253 and Rob Austein <sra@hactrn.net> for fixing it. (CVE-2011-4577)
4254 [Rob Austein <sra@hactrn.net>]
4256 *) Improved PRNG seeding for VOS.
4257 [Paul Green <Paul.Green@stratus.com>]
4259 *) Fix ssl_ciph.c set-up race.
4260 [Adam Langley (Google)]
4262 *) Fix spurious failures in ecdsatest.c.
4263 [Emilia Käsper (Google)]
4265 *) Fix the BIO_f_buffer() implementation (which was mixing different
4266 interpretations of the '..._len' fields).
4267 [Adam Langley (Google)]
4269 *) Fix handling of BN_BLINDING: now BN_BLINDING_invert_ex (rather than
4270 BN_BLINDING_invert_ex) calls BN_BLINDING_update, ensuring that concurrent
4271 threads won't reuse the same blinding coefficients.
4273 This also avoids the need to obtain the CRYPTO_LOCK_RSA_BLINDING
4274 lock to call BN_BLINDING_invert_ex, and avoids one use of
projects / openssl.git / blob