4 This is a high-level summary of the most important changes.
5 For a full list of changes, see the [git commit log][log] and
6 pick the appropriate release branch.
8 [log]: https://github.com/openssl/openssl/commits/
13 - [OpenSSL 3.1](#openssl-31)
14 - [OpenSSL 3.0](#openssl-30)
15 - [OpenSSL 1.1.1](#openssl-111)
16 - [OpenSSL 1.1.0](#openssl-110)
17 - [OpenSSL 1.0.2](#openssl-102)
18 - [OpenSSL 1.0.1](#openssl-101)
19 - [OpenSSL 1.0.0](#openssl-100)
20 - [OpenSSL 0.9.x](#openssl-09x)
25 ### Changes between 3.1.0 and 3.1.1 [xx XXX xxxx]
27 * Multiple algorithm implementation fixes for ARM BE platforms.
31 * Added a -pedantic option to fipsinstall that adjusts the various
32 settings to ensure strict FIPS compliance rather than backwards
37 * Fixed buffer overread in AES-XTS decryption on ARM 64 bit platforms which
38 happens if the buffer size is 4 mod 5 in 16 byte AES blocks. This can
39 trigger a crash of an application using AES-XTS decryption if the memory
40 just after the buffer being decrypted is not mapped.
41 Thanks to Anton Romanov (Amazon) for discovering the issue.
46 * Reworked the Fix for the Timing Oracle in RSA Decryption ([CVE-2022-4304]).
47 The previous fix for this timing side channel turned out to cause
48 a severe 2-3x performance regression in the typical use case
49 compared to 3.0.7. The new fix uses existing constant time
50 code paths, and restores the previous performance level while
51 fully eliminating all existing timing side channels.
52 The fix was developed by Bernd Edlinger with testing support
57 * Add FIPS provider configuration option to disallow the use of
58 truncated digests with Hash and HMAC DRBGs (q.v. FIPS 140-3 IG D.R.).
59 The option '-no_drbg_truncated_digests' can optionally be
60 supplied to 'openssl fipsinstall'.
64 * Corrected documentation of X509_VERIFY_PARAM_add0_policy() to mention
65 that it does not enable policy checking. Thanks to David Benjamin for
66 discovering this issue.
71 * Fixed an issue where invalid certificate policies in leaf certificates are
72 silently ignored by OpenSSL and other certificate policy checks are skipped
73 for that certificate. A malicious CA could use this to deliberately assert
74 invalid certificate policies in order to circumvent policy checking on the
75 certificate altogether.
80 * Limited the number of nodes created in a policy tree to mitigate
81 against CVE-2023-0464. The default limit is set to 1000 nodes, which
82 should be sufficient for most installations. If required, the limit
83 can be adjusted by setting the OPENSSL_POLICY_TREE_NODES_MAX build
84 time define to a desired maximum number of nodes or zero to allow
90 ### Changes between 3.0 and 3.1.0 [14 Mar 2023]
92 * Add FIPS provider configuration option to enforce the
93 Extended Master Secret (EMS) check during the TLS1_PRF KDF.
94 The option '-ems-check' can optionally be supplied to
95 'openssl fipsinstall'.
99 * The FIPS provider includes a few non-approved algorithms for
100 backward compatibility purposes and the "fips=yes" property query
101 must be used for all algorithm fetches to ensure FIPS compliance.
103 The algorithms that are included but not approved are Triple DES ECB,
104 Triple DES CBC and EdDSA.
108 * Added support for KMAC in KBKDF.
112 * RNDR and RNDRRS support in provider functions to provide
113 random number generation for Arm CPUs (aarch64).
117 * s_client and s_server apps now explicitly say when the TLS version
118 does not include the renegotiation mechanism. This avoids confusion
119 between that scenario versus when the TLS version includes secure
120 renegotiation but the peer lacks support for it.
124 * AES-GCM enabled with AVX512 vAES and vPCLMULQDQ.
126 *Tomasz Kantecki, Andrey Matyukov*
128 * The various OBJ_* functions have been made thread safe.
132 * Parallel dual-prime 1536/2048-bit modular exponentiation for
133 AVX512_IFMA capable processors.
135 *Sergey Kirillov, Andrey Matyukov (Intel Corp)*
137 * The functions `OPENSSL_LH_stats`, `OPENSSL_LH_node_stats`,
138 `OPENSSL_LH_node_usage_stats`, `OPENSSL_LH_stats_bio`,
139 `OPENSSL_LH_node_stats_bio` and `OPENSSL_LH_node_usage_stats_bio` are now
140 marked deprecated from OpenSSL 3.1 onwards and can be disabled by defining
141 `OPENSSL_NO_DEPRECATED_3_1`.
143 The macro `DEFINE_LHASH_OF` is now deprecated in favour of the macro
144 `DEFINE_LHASH_OF_EX`, which omits the corresponding type-specific function
145 definitions for these functions regardless of whether
146 `OPENSSL_NO_DEPRECATED_3_1` is defined.
148 Users of `DEFINE_LHASH_OF` may start receiving deprecation warnings for these
149 functions regardless of whether they are using them. It is recommended that
150 users transition to the new macro, `DEFINE_LHASH_OF_EX`.
154 * When generating safe-prime DH parameters set the recommended private key
155 length equivalent to minimum key lengths as in RFC 7919.
159 * Change the default salt length for PKCS#1 RSASSA-PSS signatures to the
160 maximum size that is smaller or equal to the digest length to comply with
161 FIPS 186-4 section 5. This is implemented by a new option
162 `OSSL_PKEY_RSA_PSS_SALT_LEN_AUTO_DIGEST_MAX` ("auto-digestmax") for the
163 `rsa_pss_saltlen` parameter, which is now the default. Signature
164 verification is not affected by this change and continues to work as before.
171 For OpenSSL 3.0 a [Migration guide][] has been added, so the CHANGES entries
172 listed here are only a brief description.
173 The migration guide contains more detailed information related to new features,
174 breaking changes, and mappings for the large list of deprecated functions.
176 [Migration guide]: https://github.com/openssl/openssl/tree/master/doc/man7/migration_guide.pod
178 ### Changes between 3.0.7 and 3.0.8 [7 Feb 2023]
180 * Fixed NULL dereference during PKCS7 data verification.
182 A NULL pointer can be dereferenced when signatures are being
183 verified on PKCS7 signed or signedAndEnveloped data. In case the hash
184 algorithm used for the signature is known to the OpenSSL library but
185 the implementation of the hash algorithm is not available the digest
186 initialization will fail. There is a missing check for the return
187 value from the initialization function which later leads to invalid
188 usage of the digest API most likely leading to a crash.
191 PKCS7 data is processed by the SMIME library calls and also by the
192 time stamp (TS) library calls. The TLS implementation in OpenSSL does
193 not call these functions however third party applications would be
194 affected if they call these functions to verify signatures on untrusted
199 * Fixed X.400 address type confusion in X.509 GeneralName.
201 There is a type confusion vulnerability relating to X.400 address processing
202 inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING
203 but the public structure definition for GENERAL_NAME incorrectly specified
204 the type of the x400Address field as ASN1_TYPE. This field is subsequently
205 interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather
208 When CRL checking is enabled (i.e. the application sets the
209 X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to
210 pass arbitrary pointers to a memcmp call, enabling them to read memory
211 contents or enact a denial of service.
216 * Fixed NULL dereference validating DSA public key.
218 An invalid pointer dereference on read can be triggered when an
219 application tries to check a malformed DSA public key by the
220 EVP_PKEY_public_check() function. This will most likely lead
221 to an application crash. This function can be called on public
222 keys supplied from untrusted sources which could allow an attacker
223 to cause a denial of service attack.
225 The TLS implementation in OpenSSL does not call this function
226 but applications might call the function if there are additional
227 security requirements imposed by standards such as FIPS 140-3.
230 *Shane Lontis, Tomáš Mráz*
232 * Fixed Invalid pointer dereference in d2i_PKCS7 functions.
234 An invalid pointer dereference on read can be triggered when an
235 application tries to load malformed PKCS7 data with the
236 d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions.
238 The result of the dereference is an application crash which could
239 lead to a denial of service attack. The TLS implementation in OpenSSL
240 does not call this function however third party applications might
241 call these functions on untrusted data.
246 * Fixed Use-after-free following BIO_new_NDEF.
248 The public API function BIO_new_NDEF is a helper function used for
249 streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL
250 to support the SMIME, CMS and PKCS7 streaming capabilities, but may also
251 be called directly by end user applications.
253 The function receives a BIO from the caller, prepends a new BIO_f_asn1
254 filter BIO onto the front of it to form a BIO chain, and then returns
255 the new head of the BIO chain to the caller. Under certain conditions,
256 for example if a CMS recipient public key is invalid, the new filter BIO
257 is freed and the function returns a NULL result indicating a failure.
258 However, in this case, the BIO chain is not properly cleaned up and the
259 BIO passed by the caller still retains internal pointers to the previously
260 freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO
261 then a use-after-free will occur. This will most likely result in a crash.
264 *Viktor Dukhovni, Matt Caswell*
266 * Fixed Double free after calling PEM_read_bio_ex.
268 The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and
269 decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload
270 data. If the function succeeds then the "name_out", "header" and "data"
271 arguments are populated with pointers to buffers containing the relevant
272 decoded data. The caller is responsible for freeing those buffers. It is
273 possible to construct a PEM file that results in 0 bytes of payload data.
274 In this case PEM_read_bio_ex() will return a failure code but will populate
275 the header argument with a pointer to a buffer that has already been freed.
276 If the caller also frees this buffer then a double free will occur. This
277 will most likely lead to a crash.
279 The functions PEM_read_bio() and PEM_read() are simple wrappers around
280 PEM_read_bio_ex() and therefore these functions are also directly affected.
282 These functions are also called indirectly by a number of other OpenSSL
283 functions including PEM_X509_INFO_read_bio_ex() and
284 SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL
285 internal uses of these functions are not vulnerable because the caller does
286 not free the header argument if PEM_read_bio_ex() returns a failure code.
289 *Kurt Roeckx, Matt Caswell*
291 * Fixed Timing Oracle in RSA Decryption.
293 A timing based side channel exists in the OpenSSL RSA Decryption
294 implementation which could be sufficient to recover a plaintext across
295 a network in a Bleichenbacher style attack. To achieve a successful
296 decryption an attacker would have to be able to send a very large number
297 of trial messages for decryption. The vulnerability affects all RSA padding
298 modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.
301 *Dmitry Belyavsky, Hubert Kario*
303 * Fixed X.509 Name Constraints Read Buffer Overflow.
305 A read buffer overrun can be triggered in X.509 certificate verification,
306 specifically in name constraint checking. The read buffer overrun might
307 result in a crash which could lead to a denial of service attack.
308 In a TLS client, this can be triggered by connecting to a malicious
309 server. In a TLS server, this can be triggered if the server requests
310 client authentication and a malicious client connects.
315 * Fixed X.509 Policy Constraints Double Locking security issue.
317 If an X.509 certificate contains a malformed policy constraint and
318 policy processing is enabled, then a write lock will be taken twice
319 recursively. On some operating systems (most widely: Windows) this
320 results in a denial of service when the affected process hangs. Policy
321 processing being enabled on a publicly facing server is not considered
322 to be a common setup.
327 * Our provider implementations of `OSSL_FUNC_KEYMGMT_EXPORT` and
328 `OSSL_FUNC_KEYMGMT_GET_PARAMS` for EC and SM2 keys now honor
329 `OSSL_PKEY_PARAM_EC_POINT_CONVERSION_FORMAT` as set (and
330 default to `POINT_CONVERSION_UNCOMPRESSED`) when exporting
331 `OSSL_PKEY_PARAM_PUB_KEY`, instead of unconditionally using
332 `POINT_CONVERSION_COMPRESSED` as in previous 3.x releases.
333 For symmetry, our implementation of `EVP_PKEY_ASN1_METHOD->export_to`
334 for legacy EC and SM2 keys is also changed similarly to honor the
335 equivalent conversion format flag as specified in the underlying
336 `EC_KEY` object being exported to a provider, when this function is
337 called through `EVP_PKEY_export()`.
341 * Fixed a type confusion vulnerability relating to X.400 address processing
342 inside an X.509 GeneralName. X.400 addresses were parsed as an `ASN1_STRING`
343 but subsequently interpreted by `GENERAL_NAME_cmp` as an `ASN1_TYPE`. This
344 vulnerability may allow an attacker who can provide a certificate chain and
345 CRL (neither of which need have a valid signature) to pass arbitrary pointers
346 to a `memcmp` call, creating a possible read primitive, subject to some
347 constraints. Refer to the advisory for more information. Thanks to David
348 Benjamin for discovering this issue. ([CVE-2023-0286])
350 This issue has been fixed by changing the public header file definition of
351 `GENERAL_NAME` so that `x400Address` reflects the implementation. It was not
352 possible for any existing application to successfully use the existing
353 definition; however, if any application references the `x400Address` field
354 (e.g. in dead code), note that the type of this field has changed. There is
359 ### Changes between 3.0.6 and 3.0.7 [1 Nov 2022]
361 * Fixed two buffer overflows in punycode decoding functions.
363 A buffer overrun can be triggered in X.509 certificate verification,
364 specifically in name constraint checking. Note that this occurs after
365 certificate chain signature verification and requires either a CA to
366 have signed the malicious certificate or for the application to continue
367 certificate verification despite failure to construct a path to a trusted
370 In a TLS client, this can be triggered by connecting to a malicious
371 server. In a TLS server, this can be triggered if the server requests
372 client authentication and a malicious client connects.
374 An attacker can craft a malicious email address to overflow
375 an arbitrary number of bytes containing the `.` character (decimal 46)
376 on the stack. This buffer overflow could result in a crash (causing a
380 An attacker can craft a malicious email address to overflow four
381 attacker-controlled bytes on the stack. This buffer overflow could
382 result in a crash (causing a denial of service) or potentially remote code
383 execution depending on stack layout for any given platform/compiler.
388 * Removed all references to invalid OSSL_PKEY_PARAM_RSA names for CRT
389 parameters in OpenSSL code.
390 Applications should not use the names OSSL_PKEY_PARAM_RSA_FACTOR,
391 OSSL_PKEY_PARAM_RSA_EXPONENT and OSSL_PKEY_PARAM_RSA_COEFFICIENT.
392 Use the numbered names such as OSSL_PKEY_PARAM_RSA_FACTOR1 instead.
393 Using these invalid names may cause algorithms to use slower methods
394 that ignore the CRT parameters.
398 * Fixed a regression introduced in 3.0.6 version raising errors on some stack
403 * Fixed a regression introduced in 3.0.6 version not refreshing the certificate
404 data to be signed before signing the certificate.
408 * Added RIPEMD160 to the default provider.
412 * Ensured that the key share group sent or accepted for the key exchange
413 is allowed for the protocol version.
417 ### Changes between 3.0.5 and 3.0.6 [11 Oct 2022]
419 * OpenSSL supports creating a custom cipher via the legacy
420 EVP_CIPHER_meth_new() function and associated function calls. This function
421 was deprecated in OpenSSL 3.0 and application authors are instead encouraged
422 to use the new provider mechanism in order to implement custom ciphers.
424 OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers
425 passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and
426 EVP_CipherInit_ex2() functions (as well as other similarly named encryption
427 and decryption initialisation functions). Instead of using the custom cipher
428 directly it incorrectly tries to fetch an equivalent cipher from the
429 available providers. An equivalent cipher is found based on the NID passed to
430 EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a
431 given cipher. However it is possible for an application to incorrectly pass
432 NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef
433 is used in this way the OpenSSL encryption/decryption initialisation function
434 will match the NULL cipher as being equivalent and will fetch this from the
435 available providers. This will succeed if the default provider has been
436 loaded (or if a third party provider has been loaded that offers this
437 cipher). Using the NULL cipher means that the plaintext is emitted as the
440 Applications are only affected by this issue if they call
441 EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an
442 encryption/decryption initialisation function. Applications that only use
443 SSL/TLS are not impacted by this issue.
448 * Fix LLVM vs Apple LLVM version numbering confusion that caused build failures
453 * Fixed the linux-mips64 Configure target which was missing the
454 SIXTY_FOUR_BIT bn_ops flag. This was causing heap corruption on that
459 * Fix handling of a ticket key callback that returns 0 in TLSv1.3 to not send a
464 * Correctly handle a retransmitted ClientHello in DTLS
468 * Fixed detection of ktls support in cross-compile environment on Linux
472 * Fixed some regressions and test failures when running the 3.0.0 FIPS provider
477 * Fixed SSL_pending() and SSL_has_pending() with DTLS which were failing to
478 report correct results in some cases
482 * Fix UWP builds by defining VirtualLock
486 * For known safe primes use the minimum key length according to RFC 7919.
487 Longer private key sizes unnecessarily raise the cycles needed to compute the
488 shared secret without any increase of the real security. This fixes a
489 regression from 1.1.1 where these shorter keys were generated for the known
494 * Added the loongarch64 target
498 * Fixed EC ASM flag passing. Flags for ASM implementations of EC curves were
499 only passed to the FIPS provider and not to the default or legacy provider.
503 * Fixed reported performance degradation on aarch64. Restored the
504 implementation prior to commit 2621751 ("aes/asm/aesv8-armx.pl: avoid
505 32-bit lane assignment in CTR mode") for 64bit targets only, since it is
506 reportedly 2-17% slower and the silicon errata only affects 32bit targets.
507 The new algorithm is still used for 32 bit targets.
511 * Added a missing header for memcmp that caused compilation failure on some
516 ### Changes between 3.0.4 and 3.0.5 [5 Jul 2022]
518 * The OpenSSL 3.0.4 release introduced a serious bug in the RSA
519 implementation for X86_64 CPUs supporting the AVX512IFMA instructions.
520 This issue makes the RSA implementation with 2048 bit private keys
521 incorrect on such machines and memory corruption will happen during
522 the computation. As a consequence of the memory corruption an attacker
523 may be able to trigger a remote code execution on the machine performing
526 SSL/TLS servers or other servers using 2048 bit RSA private keys running
527 on machines supporting AVX512IFMA instructions of the X86_64 architecture
528 are affected by this issue.
533 * AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised
534 implementation would not encrypt the entirety of the data under some
535 circumstances. This could reveal sixteen bytes of data that was
536 preexisting in the memory that wasn't written. In the special case of
537 "in place" encryption, sixteen bytes of the plaintext would be revealed.
539 Since OpenSSL does not support OCB based cipher suites for TLS and DTLS,
540 they are both unaffected.
543 *Alex Chernyakhovsky, David Benjamin, Alejandro Sedeño*
545 ### Changes between 3.0.3 and 3.0.4 [21 Jun 2022]
547 * In addition to the c_rehash shell command injection identified in
548 CVE-2022-1292, further bugs where the c_rehash script does not
549 properly sanitise shell metacharacters to prevent command injection have been
552 When the CVE-2022-1292 was fixed it was not discovered that there
553 are other places in the script where the file names of certificates
554 being hashed were possibly passed to a command executed through the shell.
556 This script is distributed by some operating systems in a manner where
557 it is automatically executed. On such operating systems, an attacker
558 could execute arbitrary commands with the privileges of the script.
560 Use of the c_rehash script is considered obsolete and should be replaced
561 by the OpenSSL rehash command line tool.
564 *Daniel Fiala, Tomáš Mráz*
566 * Case insensitive string comparison no longer uses locales. It has instead
567 been directly implemented.
571 ### Changes between 3.0.2 and 3.0.3 [3 May 2022]
573 * Case insensitive string comparison is reimplemented via new locale-agnostic
574 comparison functions OPENSSL_str[n]casecmp always using the POSIX locale for
575 comparison. The previous implementation had problems when the Turkish locale
580 * Fixed a bug in the c_rehash script which was not properly sanitising shell
581 metacharacters to prevent command injection. This script is distributed by
582 some operating systems in a manner where it is automatically executed. On
583 such operating systems, an attacker could execute arbitrary commands with the
584 privileges of the script.
586 Use of the c_rehash script is considered obsolete and should be replaced
587 by the OpenSSL rehash command line tool.
592 * Fixed a bug in the function `OCSP_basic_verify` that verifies the signer
593 certificate on an OCSP response. The bug caused the function in the case
594 where the (non-default) flag OCSP_NOCHECKS is used to return a postivie
595 response (meaning a successful verification) even in the case where the
596 response signing certificate fails to verify.
598 It is anticipated that most users of `OCSP_basic_verify` will not use the
599 OCSP_NOCHECKS flag. In this case the `OCSP_basic_verify` function will return
600 a negative value (indicating a fatal error) in the case of a certificate
601 verification failure. The normal expected return value in this case would be
604 This issue also impacts the command line OpenSSL "ocsp" application. When
605 verifying an ocsp response with the "-no_cert_checks" option the command line
606 application will report that the verification is successful even though it
607 has in fact failed. In this case the incorrect successful response will also
608 be accompanied by error messages showing the failure and contradicting the
609 apparently successful result.
614 * Fixed a bug where the RC4-MD5 ciphersuite incorrectly used the
615 AAD data as the MAC key. This made the MAC key trivially predictable.
617 An attacker could exploit this issue by performing a man-in-the-middle attack
618 to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such
619 that the modified data would still pass the MAC integrity check.
621 Note that data sent from an OpenSSL 3.0 endpoint to a non-OpenSSL 3.0
622 endpoint will always be rejected by the recipient and the connection will
623 fail at that point. Many application protocols require data to be sent from
624 the client to the server first. Therefore, in such a case, only an OpenSSL
625 3.0 server would be impacted when talking to a non-OpenSSL 3.0 client.
627 If both endpoints are OpenSSL 3.0 then the attacker could modify data being
628 sent in both directions. In this case both clients and servers could be
629 affected, regardless of the application protocol.
631 Note that in the absence of an attacker this bug means that an OpenSSL 3.0
632 endpoint communicating with a non-OpenSSL 3.0 endpoint will fail to complete
633 the handshake when using this ciphersuite.
635 The confidentiality of data is not impacted by this issue, i.e. an attacker
636 cannot decrypt data that has been encrypted using this ciphersuite - they can
639 In order for this attack to work both endpoints must legitimately negotiate
640 the RC4-MD5 ciphersuite. This ciphersuite is not compiled by default in
641 OpenSSL 3.0, and is not available within the default provider or the default
642 ciphersuite list. This ciphersuite will never be used if TLSv1.3 has been
643 negotiated. In order for an OpenSSL 3.0 endpoint to use this ciphersuite the
644 following must have occurred:
646 1) OpenSSL must have been compiled with the (non-default) compile time option
647 enable-weak-ssl-ciphers
649 2) OpenSSL must have had the legacy provider explicitly loaded (either
650 through application code or via configuration)
652 3) The ciphersuite must have been explicitly added to the ciphersuite list
654 4) The libssl security level must have been set to 0 (default is 1)
656 5) A version of SSL/TLS below TLSv1.3 must have been negotiated
658 6) Both endpoints must negotiate the RC4-MD5 ciphersuite in preference to any
659 others that both endpoints have in common
664 * Fix a bug in the OPENSSL_LH_flush() function that breaks reuse of the memory
665 occupied by the removed hash table entries.
667 This function is used when decoding certificates or keys. If a long lived
668 process periodically decodes certificates or keys its memory usage will
669 expand without bounds and the process might be terminated by the operating
670 system causing a denial of service. Also traversing the empty hash table
671 entries will take increasingly more time.
673 Typically such long lived processes might be TLS clients or TLS servers
674 configured to accept client certificate authentication.
677 *Hugo Landau, Aliaksei Levin*
679 * The functions `OPENSSL_LH_stats` and `OPENSSL_LH_stats_bio` now only report
680 the `num_items`, `num_nodes` and `num_alloc_nodes` statistics. All other
681 statistics are no longer supported. For compatibility, these statistics are
682 still listed in the output but are now always reported as zero.
686 ### Changes between 3.0.1 and 3.0.2 [15 Mar 2022]
688 * Fixed a bug in the BN_mod_sqrt() function that can cause it to loop forever
689 for non-prime moduli.
691 Internally this function is used when parsing certificates that contain
692 elliptic curve public keys in compressed form or explicit elliptic curve
693 parameters with a base point encoded in compressed form.
695 It is possible to trigger the infinite loop by crafting a certificate that
696 has invalid explicit curve parameters.
698 Since certificate parsing happens prior to verification of the certificate
699 signature, any process that parses an externally supplied certificate may thus
700 be subject to a denial of service attack. The infinite loop can also be
701 reached when parsing crafted private keys as they can contain explicit
702 elliptic curve parameters.
704 Thus vulnerable situations include:
706 - TLS clients consuming server certificates
707 - TLS servers consuming client certificates
708 - Hosting providers taking certificates or private keys from customers
709 - Certificate authorities parsing certification requests from subscribers
710 - Anything else which parses ASN.1 elliptic curve parameters
712 Also any other applications that use the BN_mod_sqrt() where the attacker
713 can control the parameter values are vulnerable to this DoS issue.
718 * Add ciphersuites based on DHE_PSK (RFC 4279) and ECDHE_PSK (RFC 5489)
719 to the list of ciphersuites providing Perfect Forward Secrecy as
720 required by SECLEVEL >= 3.
722 *Dmitry Belyavskiy, Nicola Tuveri*
724 * Made the AES constant time code for no-asm configurations
725 optional due to the resulting 95% performance degradation.
726 The AES constant time code can be enabled, for no assembly
727 builds, with: ./config no-asm -DOPENSSL_AES_CONST_TIME
731 * Fixed PEM_write_bio_PKCS8PrivateKey() to make it possible to use empty
736 * The negative return value handling of the certificate verification callback
737 was reverted. The replacement is to set the verification retry state with
738 the SSL_set_retry_verify() function.
742 ### Changes between 3.0.0 and 3.0.1 [14 Dec 2021]
744 * Fixed invalid handling of X509_verify_cert() internal errors in libssl
745 Internally libssl in OpenSSL calls X509_verify_cert() on the client side to
746 verify a certificate supplied by a server. That function may return a
747 negative return value to indicate an internal error (for example out of
748 memory). Such a negative return value is mishandled by OpenSSL and will cause
749 an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate
750 success and a subsequent call to SSL_get_error() to return the value
751 SSL_ERROR_WANT_RETRY_VERIFY. This return value is only supposed to be
752 returned by OpenSSL if the application has previously called
753 SSL_CTX_set_cert_verify_callback(). Since most applications do not do this
754 the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be
755 totally unexpected and applications may not behave correctly as a result. The
756 exact behaviour will depend on the application but it could result in
757 crashes, infinite loops or other similar incorrect responses.
759 This issue is made more serious in combination with a separate bug in OpenSSL
760 3.0 that will cause X509_verify_cert() to indicate an internal error when
761 processing a certificate chain. This will occur where a certificate does not
762 include the Subject Alternative Name extension but where a Certificate
763 Authority has enforced name constraints. This issue can occur even with valid
769 * Corrected a few file name and file reference bugs in the build,
770 installation and setup scripts, which lead to installation verification
771 failures. Slightly enhanced the installation verification script.
775 * Fixed EVP_PKEY_eq() to make it possible to use it with strictly private
780 * Fixed PVK encoder to properly query for the passphrase.
784 * Multiple fixes in the OSSL_HTTP API functions.
788 * Allow sign extension in OSSL_PARAM_allocate_from_text() for the
789 OSSL_PARAM_INTEGER data type and return error on negative numbers
790 used with the OSSL_PARAM_UNSIGNED_INTEGER data type. Make
791 OSSL_PARAM_BLD_push_BN{,_pad}() return an error on negative numbers.
795 * Allow copying uninitialized digest contexts with EVP_MD_CTX_copy_ex.
799 * Fixed detection of ARMv7 and ARM64 CPU features on FreeBSD.
803 * Multiple threading fixes.
807 * Added NULL digest implementation to keep compatibility with 1.1.1 version.
811 * Allow fetching an operation from the provider that owns an unexportable key
812 as a fallback if that is still allowed by the property query.
816 ### Changes between 1.1.1 and 3.0.0 [7 sep 2021]
818 * TLS_MAX_VERSION, DTLS_MAX_VERSION and DTLS_MIN_VERSION constants are now
823 * The `OPENSSL_s390xcap` environment variable can be used to set bits in the
824 S390X capability vector to zero. This simplifies testing of different code
825 paths on S390X architecture.
829 * Encrypting more than 2^64 TLS records with AES-GCM is disallowed
830 as per FIPS 140-2 IG A.5 "Key/IV Pair Uniqueness Requirements from
831 SP 800-38D". The communication will fail at this point.
835 * The EC_GROUP_clear_free() function is deprecated as there is nothing
836 confidential in EC_GROUP data.
840 * The byte order mark (BOM) character is ignored if encountered at the
841 beginning of a PEM-formatted file.
845 * Added CMS support for the Russian GOST algorithms.
849 * Due to move of the implementation of cryptographic operations
850 to the providers, validation of various operation parameters can
851 be postponed until the actual operation is executed where previously
852 it happened immediately when an operation parameter was set.
854 For example when setting an unsupported curve with
855 EVP_PKEY_CTX_set_ec_paramgen_curve_nid() this function call will not
856 fail but later keygen operations with the EVP_PKEY_CTX will fail.
858 *OpenSSL team members and many third party contributors*
860 * The EVP_get_cipherbyname() function will return NULL for algorithms such as
861 "AES-128-SIV", "AES-128-CBC-CTS" and "CAMELLIA-128-CBC-CTS" which were
862 previously only accessible via low-level interfaces. Use EVP_CIPHER_fetch()
863 instead to retrieve these algorithms from a provider.
867 * On build targets where the multilib postfix is set in the build
868 configuration the libdir directory was changing based on whether
869 the lib directory with the multilib postfix exists on the system
870 or not. This unpredictable behavior was removed and eventual
871 multilib postfix is now always added to the default libdir. Use
872 `--libdir=lib` to override the libdir if adding the postfix is
877 * The triple DES key wrap functionality now conforms to RFC 3217 but is
878 no longer interoperable with OpenSSL 1.1.1.
882 * The ERR_GET_FUNC() function was removed. With the loss of meaningful
883 function codes, this function can only cause problems for calling
888 * Add a configurable flag to output date formats as ISO 8601. Does not
889 change the default date format.
893 * Version of MSVC earlier than 1300 could get link warnings, which could
894 be suppressed if the undocumented -DI_CAN_LIVE_WITH_LNK4049 was set.
895 Support for this flag has been removed.
899 * Rework and make DEBUG macros consistent. Remove unused -DCONF_DEBUG,
900 -DBN_CTX_DEBUG, and REF_PRINT. Add a new tracing category and use it for
901 printing reference counts. Rename -DDEBUG_UNUSED to -DUNUSED_RESULT_DEBUG
902 Fix BN_DEBUG_RAND so it compiles and, when set, force DEBUG_RAND to be set
903 also. Rename engine_debug_ref to be ENGINE_REF_PRINT also for consistency.
907 * The signatures of the functions to get and set options on SSL and
908 SSL_CTX objects changed from "unsigned long" to "uint64_t" type.
909 Some source code changes may be required.
913 * The public definitions of conf_method_st and conf_st have been
914 deprecated. They will be made opaque in a future release.
916 *Rich Salz and Tomáš Mráz*
918 * Client-initiated renegotiation is disabled by default. To allow it, use
919 the -client_renegotiation option, the SSL_OP_ALLOW_CLIENT_RENEGOTIATION
920 flag, or the "ClientRenegotiation" config parameter as appropriate.
924 * Add "abspath" and "includedir" pragma's to config files, to prevent,
925 or modify relative pathname inclusion.
929 * OpenSSL includes a cryptographic module that is intended to be FIPS 140-2
930 validated. Please consult the README-FIPS and
931 README-PROVIDERS files, as well as the migration guide.
933 *OpenSSL team members and many third party contributors*
935 * For the key types DH and DHX the allowed settable parameters are now different.
939 * The openssl commands that read keys, certificates, and CRLs now
940 automatically detect the PEM or DER format of the input files.
942 *David von Oheimb, Richard Levitte, and Tomáš Mráz*
944 * Added enhanced PKCS#12 APIs which accept a library context.
948 * The default manual page suffix ($MANSUFFIX) has been changed to "ossl"
952 * Added support for Kernel TLS (KTLS).
954 *Boris Pismenny, John Baldwin and Andrew Gallatin*
956 * Support for RFC 5746 secure renegotiation is now required by default for
957 SSL or TLS connections to succeed.
961 * The signature of the `copy` functional parameter of the
962 EVP_PKEY_meth_set_copy() function has changed so its `src` argument is
963 now `const EVP_PKEY_CTX *` instead of `EVP_PKEY_CTX *`. Similarly
964 the signature of the `pub_decode` functional parameter of the
965 EVP_PKEY_asn1_set_public() function has changed so its `pub` argument is
966 now `const X509_PUBKEY *` instead of `X509_PUBKEY *`.
970 * The error return values from some control calls (ctrl) have changed.
974 * A public key check is now performed during EVP_PKEY_derive_set_peer().
978 * Many functions in the EVP_ namespace that are getters of values from
979 implementations or contexts were renamed to include get or get0 in their
980 names. Old names are provided as macro aliases for compatibility and
985 * The EVP_PKEY_CTRL_PKCS7_ENCRYPT, EVP_PKEY_CTRL_PKCS7_DECRYPT,
986 EVP_PKEY_CTRL_PKCS7_SIGN, EVP_PKEY_CTRL_CMS_ENCRYPT,
987 EVP_PKEY_CTRL_CMS_DECRYPT, and EVP_PKEY_CTRL_CMS_SIGN control operations
992 * The EVP_PKEY_public_check() and EVP_PKEY_param_check() functions now work for
995 * The output from the command line applications may have minor
1000 * The output from numerous "printing" may have minor changes.
1004 * Windows thread synchronization uses read/write primitives (SRWLock) when
1005 supported by the OS, otherwise CriticalSection continues to be used.
1009 * Add filter BIO BIO_f_readbuffer() that allows BIO_tell() and BIO_seek() to
1010 work on read only BIO source/sinks that do not support these functions.
1011 This allows piping or redirection of a file BIO using stdin to be buffered
1012 into memory. This is used internally in OSSL_DECODER_from_bio().
1016 * OSSL_STORE_INFO_get_type() may now return an additional value. In 1.1.1
1017 this function would return one of the values OSSL_STORE_INFO_NAME,
1018 OSSL_STORE_INFO_PKEY, OSSL_STORE_INFO_PARAMS, OSSL_STORE_INFO_CERT or
1019 OSSL_STORE_INFO_CRL. Decoded public keys would previously have been reported
1020 as type OSSL_STORE_INFO_PKEY in 1.1.1. In 3.0 decoded public keys are now
1021 reported as having the new type OSSL_STORE_INFO_PUBKEY. Applications
1022 using this function should be amended to handle the changed return value.
1026 * Improved adherence to Enhanced Security Services (ESS, RFC 2634 and RFC 5035)
1027 for the TSP and CMS Advanced Electronic Signatures (CAdES) implementations.
1028 As required by RFC 5035 check both ESSCertID and ESSCertIDv2 if both present.
1029 Correct the semantics of checking the validation chain in case ESSCertID{,v2}
1030 contains more than one certificate identifier: This means that all
1031 certificates referenced there MUST be part of the validation chain.
1035 * The implementation of older EVP ciphers related to CAST, IDEA, SEED, RC2, RC4,
1036 RC5, DESX and DES have been moved to the legacy provider.
1040 * The implementation of the EVP digests MD2, MD4, MDC2, WHIRLPOOL and
1041 RIPEMD-160 have been moved to the legacy provider.
1045 * The deprecated function EVP_PKEY_get0() now returns NULL being called for a
1050 * The deprecated functions EVP_PKEY_get0_RSA(),
1051 EVP_PKEY_get0_DSA(), EVP_PKEY_get0_EC_KEY(), EVP_PKEY_get0_DH(),
1052 EVP_PKEY_get0_hmac(), EVP_PKEY_get0_poly1305() and EVP_PKEY_get0_siphash() as
1053 well as the similarly named "get1" functions behave differently in
1058 * A number of functions handling low-level keys or engines were deprecated
1059 including EVP_PKEY_set1_engine(), EVP_PKEY_get0_engine(), EVP_PKEY_assign(),
1060 EVP_PKEY_get0(), EVP_PKEY_get0_hmac(), EVP_PKEY_get0_poly1305() and
1061 EVP_PKEY_get0_siphash().
1065 * PKCS#5 PBKDF1 key derivation has been moved from PKCS5_PBE_keyivgen() into
1066 the legacy crypto provider as an EVP_KDF. Applications requiring this KDF
1067 will need to load the legacy crypto provider. This includes these PBE
1068 algorithms which use this KDF:
1069 - NID_pbeWithMD2AndDES_CBC
1070 - NID_pbeWithMD5AndDES_CBC
1071 - NID_pbeWithSHA1AndRC2_CBC
1072 - NID_pbeWithMD2AndRC2_CBC
1073 - NID_pbeWithMD5AndRC2_CBC
1074 - NID_pbeWithSHA1AndDES_CBC
1078 * Deprecated obsolete BIO_set_callback(), BIO_get_callback(), and
1079 BIO_debug_callback() functions.
1083 * Deprecated obsolete EVP_PKEY_CTX_get0_dh_kdf_ukm() and
1084 EVP_PKEY_CTX_get0_ecdh_kdf_ukm() functions.
1088 * The RAND_METHOD APIs have been deprecated.
1092 * The SRP APIs have been deprecated.
1096 * Add a compile time option to prevent the caching of provider fetched
1097 algorithms. This is enabled by including the no-cached-fetch option
1098 at configuration time.
1102 * pkcs12 now uses defaults of PBKDF2, AES and SHA-256, with a MAC iteration
1103 count of PKCS12_DEFAULT_ITER.
1105 *Tomáš Mráz and Sahana Prasad*
1107 * The openssl speed command does not use low-level API calls anymore.
1111 * Parallel dual-prime 1024-bit modular exponentiation for AVX512_IFMA
1114 *Ilya Albrekht, Sergey Kirillov, Andrey Matyukov (Intel Corp)*
1116 * Combining the Configure options no-ec and no-dh no longer disables TLSv1.3.
1120 * Implemented support for fully "pluggable" TLSv1.3 groups. This means that
1121 providers may supply their own group implementations (using either the "key
1122 exchange" or the "key encapsulation" methods) which will automatically be
1123 detected and used by libssl.
1125 *Matt Caswell, Nicola Tuveri*
1127 * The undocumented function X509_certificate_type() has been deprecated;
1131 * Deprecated the obsolete BN_pseudo_rand() and BN_pseudo_rand_range().
1135 * Removed RSA padding mode for SSLv23 (which was only used for
1136 SSLv2). This includes the functions RSA_padding_check_SSLv23() and
1137 RSA_padding_add_SSLv23() and the `-ssl` option in the deprecated
1142 * Deprecated the obsolete X9.31 RSA key generation related functions.
1144 * While a callback function set via `SSL_CTX_set_cert_verify_callback()`
1145 is not allowed to return a value > 1, this is no more taken as failure.
1147 *Viktor Dukhovni and David von Oheimb*
1149 * Deprecated the obsolete X9.31 RSA key generation related functions
1150 BN_X931_generate_Xpq(), BN_X931_derive_prime_ex(), and
1151 BN_X931_generate_prime_ex().
1155 * The default key generation method for the regular 2-prime RSA keys was
1156 changed to the FIPS 186-4 B.3.6 method.
1160 * Deprecated the BN_is_prime_ex() and BN_is_prime_fasttest_ex() functions.
1164 * Deprecated EVP_MD_CTX_set_update_fn() and EVP_MD_CTX_update_fn().
1168 * Deprecated the type OCSP_REQ_CTX and the functions OCSP_REQ_CTX_*() and
1169 replaced with OSSL_HTTP_REQ_CTX and the functions OSSL_HTTP_REQ_CTX_*().
1171 *Rich Salz, Richard Levitte, and David von Oheimb*
1173 * Deprecated `X509_http_nbio()` and `X509_CRL_http_nbio()`.
1177 * Deprecated `OCSP_parse_url()`.
1181 * Validation of SM2 keys has been separated from the validation of regular EC
1186 * Behavior of the `pkey` app is changed, when using the `-check` or `-pubcheck`
1187 switches: a validation failure triggers an early exit, returning a failure
1188 exit status to the parent process.
1192 * Changed behavior of SSL_CTX_set_ciphersuites() and SSL_set_ciphersuites()
1193 to ignore unknown ciphers.
1197 * The `-cipher-commands` and `-digest-commands` options
1198 of the command line utility `list` have been deprecated.
1199 Instead use the `-cipher-algorithms` and `-digest-algorithms` options.
1203 * Added convenience functions for generating asymmetric key pairs:
1204 The 'quick' one-shot (yet somewhat limited) function L<EVP_PKEY_Q_keygen(3)>
1205 and macros for the most common cases: <EVP_RSA_gen(3)> and L<EVP_EC_gen(3)>.
1209 * All of the low-level EC_KEY functions have been deprecated.
1211 *Shane Lontis, Paul Dale, Richard Levitte, and Tomáš Mráz*
1213 * Deprecated all the libcrypto and libssl error string loading
1218 * The functions SSL_CTX_set_tmp_dh_callback and SSL_set_tmp_dh_callback, as
1219 well as the macros SSL_CTX_set_tmp_dh() and SSL_set_tmp_dh() have been
1224 * The `-crypt` option to the `passwd` command line tool has been removed.
1228 * The -C option to the `x509`, `dhparam`, `dsaparam`, and `ecparam` commands
1233 * Add support for AES Key Wrap inverse ciphers to the EVP layer.
1237 * Deprecated EVP_PKEY_set1_tls_encodedpoint() and
1238 EVP_PKEY_get1_tls_encodedpoint().
1242 * The security callback, which can be customised by application code, supports
1243 the security operation SSL_SECOP_TMP_DH. One location of the "other" parameter
1244 was incorrectly passing a DH object. It now passed an EVP_PKEY in all cases.
1248 * Add PKCS7_get_octet_string() and PKCS7_type_is_other() to the public
1249 interface. Their functionality remains unchanged.
1253 * Added new option for 'openssl list', '-providers', which will display the
1254 list of loaded providers, their names, version and status. It optionally
1255 displays their gettable parameters.
1259 * Removed EVP_PKEY_set_alias_type().
1263 * Deprecated `EVP_PKEY_CTX_set_rsa_keygen_pubexp()` and introduced
1264 `EVP_PKEY_CTX_set1_rsa_keygen_pubexp()`, which is now preferred.
1268 * Changed all "STACK" functions to be macros instead of inline functions. Macro
1269 parameters are still checked for type safety at compile time via helper
1274 * Remove the RAND_DRBG API
1276 *Paul Dale and Matthias St. Pierre*
1278 * Allow `SSL_set1_host()` and `SSL_add1_host()` to take IP literal addresses
1279 as well as actual hostnames.
1283 * The 'MinProtocol' and 'MaxProtocol' configuration commands now silently
1284 ignore TLS protocol version bounds when configuring DTLS-based contexts, and
1285 conversely, silently ignore DTLS protocol version bounds when configuring
1286 TLS-based contexts. The commands can be repeated to set bounds of both
1287 types. The same applies with the corresponding "min_protocol" and
1288 "max_protocol" command-line switches, in case some application uses both TLS
1291 SSL_CTX instances that are created for a fixed protocol version (e.g.
1292 `TLSv1_server_method()`) also silently ignore version bounds. Previously
1293 attempts to apply bounds to these protocol versions would result in an
1294 error. Now only the "version-flexible" SSL_CTX instances are subject to
1295 limits in configuration files in command-line options.
1299 * Deprecated the `ENGINE` API. Engines should be replaced with providers
1304 * Reworked the recorded ERR codes to make better space for system errors.
1305 To distinguish them, the macro `ERR_SYSTEM_ERROR()` indicates if the
1306 given code is a system error (true) or an OpenSSL error (false).
1310 * Reworked the test perl framework to better allow parallel testing.
1312 *Nicola Tuveri and David von Oheimb*
1314 * Added ciphertext stealing algorithms AES-128-CBC-CTS, AES-192-CBC-CTS and
1315 AES-256-CBC-CTS to the providers. CS1, CS2 and CS3 variants are supported.
1319 * 'Configure' has been changed to figure out the configuration target if
1320 none is given on the command line. Consequently, the 'config' script is
1321 now only a mere wrapper. All documentation is changed to only mention
1324 *Rich Salz and Richard Levitte*
1326 * Added a library context `OSSL_LIB_CTX` that applications as well as
1327 other libraries can use to form a separate context within which
1328 libcrypto operations are performed.
1332 * Added various `_ex` functions to the OpenSSL API that support using
1333 a non-default `OSSL_LIB_CTX`.
1337 * Handshake now fails if Extended Master Secret extension is dropped
1342 * Dropped interactive mode from the `openssl` program.
1346 * Deprecated `EVP_PKEY_cmp()` and `EVP_PKEY_cmp_parameters()`.
1348 *David von Oheimb and Shane Lontis*
1350 * Deprecated `EC_METHOD_get_field_type()`.
1354 * Deprecated EC_GFp_simple_method(), EC_GFp_mont_method(),
1355 EC_GF2m_simple_method(), EC_GFp_nist_method(), EC_GFp_nistp224_method()
1356 EC_GFp_nistp256_method(), and EC_GFp_nistp521_method().
1360 * Deprecated EC_GROUP_new(), EC_GROUP_method_of(), and EC_POINT_method_of().
1364 * Add CAdES-BES signature verification support, mostly derived
1365 from ESSCertIDv2 TS (RFC 5816) contribution by Marek Klein.
1367 *Filipe Raimundo da Silva*
1369 * Add CAdES-BES signature scheme and attributes support (RFC 5126) to CMS API.
1373 * Added the AuthEnvelopedData content type structure (RFC 5083) with AES-GCM
1374 parameter (RFC 5084) for the Cryptographic Message Syntax (CMS).
1378 * Deprecated EC_POINT_make_affine() and EC_POINTs_make_affine().
1382 * Deprecated EC_GROUP_precompute_mult(), EC_GROUP_have_precompute_mult(), and
1383 EC_KEY_precompute_mult().
1387 * Deprecated EC_POINTs_mul().
1391 * Removed FIPS_mode() and FIPS_mode_set().
1395 * The SSL option SSL_OP_IGNORE_UNEXPECTED_EOF is introduced.
1399 * Deprecated EC_POINT_set_Jprojective_coordinates_GFp() and
1400 EC_POINT_get_Jprojective_coordinates_GFp().
1404 * Added OSSL_PARAM_BLD to the public interface. This allows OSSL_PARAM
1405 arrays to be more easily constructed via a series of utility functions.
1406 Create a parameter builder using OSSL_PARAM_BLD_new(), add parameters using
1407 the various push functions and finally convert to a passable OSSL_PARAM
1408 array using OSSL_PARAM_BLD_to_param().
1412 * The security strength of SHA1 and MD5 based signatures in TLS has been
1417 * Added EVP_PKEY_set_type_by_keymgmt(), to initialise an EVP_PKEY to
1418 contain a provider side internal key.
1422 * ASN1_verify(), ASN1_digest() and ASN1_sign() have been deprecated.
1426 * Project text documents not yet having a proper file name extension
1427 (`HACKING`, `LICENSE`, `NOTES*`, `README*`, `VERSION`) have been renamed to
1428 `*.md` as far as reasonable, else `*.txt`, for better use with file managers.
1432 * The main project documents (README, NEWS, CHANGES, INSTALL, SUPPORT)
1433 have been converted to Markdown with the goal to produce documents
1434 which not only look pretty when viewed online in the browser, but
1435 remain well readable inside a plain text editor.
1437 To achieve this goal, a 'minimalistic' Markdown style has been applied
1438 which avoids formatting elements that interfere too much with the
1439 reading flow in the text file. For example, it
1441 * avoids [ATX headings][] and uses [setext headings][] instead
1442 (which works for `<h1>` and `<h2>` headings only).
1443 * avoids [inline links][] and uses [reference links][] instead.
1444 * avoids [fenced code blocks][] and uses [indented code blocks][] instead.
1446 [ATX headings]: https://github.github.com/gfm/#atx-headings
1447 [setext headings]: https://github.github.com/gfm/#setext-headings
1448 [inline links]: https://github.github.com/gfm/#inline-link
1449 [reference links]: https://github.github.com/gfm/#reference-link
1450 [fenced code blocks]: https://github.github.com/gfm/#fenced-code-blocks
1451 [indented code blocks]: https://github.github.com/gfm/#indented-code-blocks
1453 *Matthias St. Pierre*
1455 * The test suite is changed to preserve results of each test recipe.
1456 A new directory test-runs/ with subdirectories named like the
1457 test recipes are created in the build tree for this purpose.
1461 * Added an implementation of CMP and CRMF (RFC 4210, RFC 4211 RFC 6712).
1462 This adds `crypto/cmp/`, `crpyto/crmf/`, `apps/cmp.c`, and `test/cmp_*`.
1463 See L<openssl-cmp(1)> and L<OSSL_CMP_exec_IR_ses(3)> as starting points.
1465 *David von Oheimb, Martin Peylo*
1467 * Generalized the HTTP client code from `crypto/ocsp/` into `crpyto/http/`.
1468 It supports arbitrary request and response content types, GET redirection,
1469 TLS, connections via HTTP(S) proxies, connections and exchange via
1470 user-defined BIOs (allowing implicit connections), persistent connections,
1471 and timeout checks. See L<OSSL_HTTP_transfer(3)> etc. for details.
1472 The legacy OCSP-focused (and only partly documented) API
1473 is retained for backward compatibility, while most of it is deprecated.
1477 * Added `util/check-format.pl`, a tool for checking adherence to the
1478 OpenSSL coding style <https://www.openssl.org/policies/codingstyle.html>.
1479 The checks performed are incomplete and yield some false positives.
1480 Still the tool should be useful for detecting most typical glitches.
1484 * `BIO_do_connect()` and `BIO_do_handshake()` have been extended:
1485 If domain name resolution yields multiple IP addresses all of them are tried
1486 after `connect()` failures.
1490 * All of the low-level RSA functions have been deprecated.
1494 * X509 certificates signed using SHA1 are no longer allowed at security
1499 * The command line utilities dhparam, dsa, gendsa and dsaparam have been
1500 modified to use PKEY APIs. These commands are now in maintenance mode
1501 and no new features will be added to them.
1505 * The command line utility rsautl has been deprecated.
1509 * The command line utilities genrsa and rsa have been modified to use PKEY
1510 APIs. They now write PKCS#8 keys by default. These commands are now in
1511 maintenance mode and no new features will be added to them.
1515 * All of the low-level DH functions have been deprecated.
1517 *Paul Dale and Matt Caswell*
1519 * All of the low-level DSA functions have been deprecated.
1523 * Reworked the treatment of EC EVP_PKEYs with the SM2 curve to
1524 automatically become EVP_PKEY_SM2 rather than EVP_PKEY_EC.
1528 * Deprecated low-level ECDH and ECDSA functions.
1532 * Deprecated EVP_PKEY_decrypt_old() and EVP_PKEY_encrypt_old().
1536 * Enhanced the documentation of EVP_PKEY_get_size(), EVP_PKEY_get_bits()
1537 and EVP_PKEY_get_security_bits(). Especially EVP_PKEY_get_size() needed
1538 a new formulation to include all the things it can be used for,
1539 as well as words of caution.
1543 * The SSL_CTX_set_tlsext_ticket_key_cb(3) function has been deprecated.
1547 * All of the low-level HMAC functions have been deprecated.
1549 *Paul Dale and David von Oheimb*
1551 * Over two thousand fixes were made to the documentation, including:
1552 - Common options (such as -rand/-writerand, TLS version control, etc)
1553 were refactored and point to newly-enhanced descriptions in openssl.pod.
1554 - Added style conformance for all options (with help from Richard Levitte),
1555 documented all reported missing options, added a CI build to check
1556 that all options are documented and that no unimplemented options
1558 - Documented some internals, such as all use of environment variables.
1559 - Addressed all internal broken L<> references.
1563 * All of the low-level CMAC functions have been deprecated.
1567 * The low-level MD2, MD4, MD5, MDC2, RIPEMD160 and Whirlpool digest
1568 functions have been deprecated.
1570 *Paul Dale and David von Oheimb*
1572 * Corrected the documentation of the return values from the `EVP_DigestSign*`
1573 set of functions. The documentation mentioned negative values for some
1574 errors, but this was never the case, so the mention of negative values
1577 Code that followed the documentation and thereby check with something
1578 like `EVP_DigestSignInit(...) <= 0` will continue to work undisturbed.
1582 * All of the low-level cipher functions have been deprecated.
1584 *Matt Caswell and Paul Dale*
1586 * Removed include/openssl/opensslconf.h.in and replaced it with
1587 include/openssl/configuration.h.in, which differs in not including
1588 <openssl/macros.h>. A short header include/openssl/opensslconf.h
1589 was added to include both.
1591 This allows internal hacks where one might need to modify the set
1592 of configured macros, for example this if deprecated symbols are
1593 still supposed to be available internally:
1595 #include <openssl/configuration.h>
1597 #undef OPENSSL_NO_DEPRECATED
1598 #define OPENSSL_SUPPRESS_DEPRECATED
1600 #include <openssl/macros.h>
1602 This should not be used by applications that use the exported
1603 symbols, as that will lead to linking errors.
1607 * Fixed an overflow bug in the x64_64 Montgomery squaring procedure
1608 used in exponentiation with 512-bit moduli. No EC algorithms are
1609 affected. Analysis suggests that attacks against 2-prime RSA1024,
1610 3-prime RSA1536, and DSA1024 as a result of this defect would be very
1611 difficult to perform and are not believed likely. Attacks against DH512
1612 are considered just feasible. However, for an attack the target would
1613 have to re-use the DH512 private key, which is not recommended anyway.
1614 Also applications directly using the low-level API BN_mod_exp may be
1615 affected if they use BN_FLG_CONSTTIME.
1620 * Most memory-debug features have been deprecated, and the functionality
1621 replaced with no-ops.
1625 * Added documentation for the STACK API.
1629 * Introduced a new method type and API, OSSL_ENCODER, to represent
1630 generic encoders. These do the same sort of job that PEM writers
1631 and d2i functions do, but with support for methods supplied by
1632 providers, and the possibility for providers to support other
1637 * Introduced a new method type and API, OSSL_DECODER, to represent
1638 generic decoders. These do the same sort of job that PEM readers
1639 and i2d functions do, but with support for methods supplied by
1640 providers, and the possibility for providers to support other
1645 * Added a .pragma directive to the syntax of configuration files, to
1646 allow varying behavior in a supported and predictable manner.
1647 Currently added pragma:
1651 This allows dollar signs to be a keyword character unless it's
1652 followed by a opening brace or parenthesis. This is useful for
1653 platforms where dollar signs are commonly used in names, such as
1654 volume names and system directory names on VMS.
1658 * Added functionality to create an EVP_PKEY from user data.
1662 * Change the interpretation of the '--api' configuration option to
1663 mean that this is a desired API compatibility level with no
1664 further meaning. The previous interpretation, that this would
1665 also mean to remove all deprecated symbols up to and including
1666 the given version, no requires that 'no-deprecated' is also used
1667 in the configuration.
1669 When building applications, the desired API compatibility level
1670 can be set with the OPENSSL_API_COMPAT macro like before. For
1671 API compatibility version below 3.0, the old style numerical
1672 value is valid as before, such as -DOPENSSL_API_COMPAT=0x10100000L.
1673 For version 3.0 and on, the value is expected to be the decimal
1674 value calculated from the major and minor version like this:
1676 MAJOR * 10000 + MINOR * 100
1680 -DOPENSSL_API_COMPAT=30000 For 3.0
1681 -DOPENSSL_API_COMPAT=30200 For 3.2
1683 To hide declarations that are deprecated up to and including the
1684 given API compatibility level, -DOPENSSL_NO_DEPRECATED must be
1685 given when building the application as well.
1689 * Added the X509_LOOKUP_METHOD called X509_LOOKUP_store, to allow
1690 access to certificate and CRL stores via URIs and OSSL_STORE
1693 This adds the following functions:
1695 - X509_LOOKUP_store()
1696 - X509_STORE_load_file()
1697 - X509_STORE_load_path()
1698 - X509_STORE_load_store()
1699 - SSL_add_store_cert_subjects_to_stack()
1700 - SSL_CTX_set_default_verify_store()
1701 - SSL_CTX_load_verify_file()
1702 - SSL_CTX_load_verify_dir()
1703 - SSL_CTX_load_verify_store()
1707 * Added a new method to gather entropy on VMS, based on SYS$GET_ENTROPY.
1708 The presence of this system service is determined at run-time.
1712 * Added functionality to create an EVP_PKEY context based on data
1713 for methods from providers. This takes an algorithm name and a
1714 property query string and simply stores them, with the intent
1715 that any operation that uses this context will use those strings
1716 to fetch the needed methods implicitly, thereby making the port
1717 of application written for pre-3.0 OpenSSL easier.
1721 * The undocumented function NCONF_WIN32() has been deprecated; for
1722 conversion details see the HISTORY section of doc/man5/config.pod
1726 * Introduced the new functions EVP_DigestSignInit_ex() and
1727 EVP_DigestVerifyInit_ex(). The macros EVP_DigestSignUpdate() and
1728 EVP_DigestVerifyUpdate() have been converted to functions. See the man
1729 pages for further details.
1733 * Over two thousand fixes were made to the documentation, including:
1734 adding missing command flags, better style conformance, documentation
1737 *Rich Salz, Richard Levitte*
1739 * s390x assembly pack: add hardware-support for P-256, P-384, P-521,
1740 X25519, X448, Ed25519 and Ed448.
1744 * Print all values for a PKCS#12 attribute with 'openssl pkcs12', not just
1749 * Deprecated the public definition of `ERR_STATE` as well as the function
1750 `ERR_get_state()`. This is done in preparation of making `ERR_STATE` an
1755 * Added ERR functionality to give callers access to the stored function
1756 names that have replaced the older function code based functions.
1758 New functions are ERR_peek_error_func(), ERR_peek_last_error_func(),
1759 ERR_peek_error_data(), ERR_peek_last_error_data(), ERR_get_error_all(),
1760 ERR_peek_error_all() and ERR_peek_last_error_all().
1762 Deprecate ERR functions ERR_get_error_line(), ERR_get_error_line_data(),
1763 ERR_peek_error_line_data(), ERR_peek_last_error_line_data() and
1764 ERR_func_error_string().
1768 * Extended testing to be verbose for failing tests only. The make variables
1769 VERBOSE_FAILURE or VF can be used to enable this:
1771 $ make VF=1 test # Unix
1772 $ mms /macro=(VF=1) test ! OpenVMS
1773 $ nmake VF=1 test # Windows
1777 * Added the `-copy_extensions` option to the `x509` command for use with
1778 `-req` and `-x509toreq`. When given with the `copy` or `copyall` argument,
1779 all extensions in the request are copied to the certificate or vice versa.
1781 *David von Oheimb*, *Kirill Stefanenkov <kirill_stefanenkov@rambler.ru>*
1783 * Added the `-copy_extensions` option to the `req` command for use with
1784 `-x509`. When given with the `copy` or `copyall` argument,
1785 all extensions in the certification request are copied to the certificate.
1789 * The `x509`, `req`, and `ca` commands now make sure that X.509v3 certificates
1790 they generate are by default RFC 5280 compliant in the following sense:
1791 There is a subjectKeyIdentifier extension with a hash value of the public key
1792 and for not self-signed certs there is an authorityKeyIdentifier extension
1793 with a keyIdentifier field or issuer information identifying the signing key.
1794 This is done unless some configuration overrides the new default behavior,
1795 such as `subjectKeyIdentifier = none` and `authorityKeyIdentifier = none`.
1799 * Added several checks to `X509_verify_cert()` according to requirements in
1800 RFC 5280 in case `X509_V_FLAG_X509_STRICT` is set
1801 (which may be done by using the CLI option `-x509_strict`):
1802 * The basicConstraints of CA certificates must be marked critical.
1803 * CA certificates must explicitly include the keyUsage extension.
1804 * If a pathlenConstraint is given the key usage keyCertSign must be allowed.
1805 * The issuer name of any certificate must not be empty.
1806 * The subject name of CA certs, certs with keyUsage crlSign,
1807 and certs without subjectAlternativeName must not be empty.
1808 * If a subjectAlternativeName extension is given it must not be empty.
1809 * The signatureAlgorithm field and the cert signature must be consistent.
1810 * Any given authorityKeyIdentifier and any given subjectKeyIdentifier
1811 must not be marked critical.
1812 * The authorityKeyIdentifier must be given for X.509v3 certs
1813 unless they are self-signed.
1814 * The subjectKeyIdentifier must be given for all X.509v3 CA certs.
1818 * Certificate verification using `X509_verify_cert()` meanwhile rejects EC keys
1819 with explicit curve parameters (specifiedCurve) as required by RFC 5480.
1823 * For built-in EC curves, ensure an EC_GROUP built from the curve name is
1824 used even when parsing explicit parameters, when loading a encoded key
1825 or calling `EC_GROUP_new_from_ecpkparameters()`/
1826 `EC_GROUP_new_from_ecparameters()`.
1827 This prevents bypass of security hardening and performance gains,
1828 especially for curves with specialized EC_METHODs.
1829 By default, if a key encoded with explicit parameters is loaded and later
1830 encoded, the output is still encoded with explicit parameters, even if
1831 internally a "named" EC_GROUP is used for computation.
1835 * Compute ECC cofactors if not provided during EC_GROUP construction. Before
1836 this change, EC_GROUP_set_generator would accept order and/or cofactor as
1837 NULL. After this change, only the cofactor parameter can be NULL. It also
1838 does some minimal sanity checks on the passed order.
1843 * Fixed a padding oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey.
1844 An attack is simple, if the first CMS_recipientInfo is valid but the
1845 second CMS_recipientInfo is chosen ciphertext. If the second
1846 recipientInfo decodes to PKCS #1 v1.5 form plaintext, the correct
1847 encryption key will be replaced by garbage, and the message cannot be
1848 decoded, but if the RSA decryption fails, the correct encryption key is
1849 used and the recipient will not notice the attack.
1850 As a work around for this potential attack the length of the decrypted
1851 key must be equal to the cipher default key length, in case the
1852 certificate is not given and all recipientInfo are tried out.
1853 The old behaviour can be re-enabled in the CMS code by setting the
1854 CMS_DEBUG_DECRYPT flag.
1858 * Early start up entropy quality from the DEVRANDOM seed source has been
1859 improved for older Linux systems. The RAND subsystem will wait for
1860 /dev/random to be producing output before seeding from /dev/urandom.
1861 The seeded state is stored for future library initialisations using
1862 a system global shared memory segment. The shared memory identifier
1863 can be configured by defining OPENSSL_RAND_SEED_DEVRANDOM_SHM_ID to
1864 the desired value. The default identifier is 114.
1868 * Revised BN_generate_prime_ex to not avoid factors 2..17863 in p-1
1869 when primes for RSA keys are computed.
1870 Since we previously always generated primes == 2 (mod 3) for RSA keys,
1871 the 2-prime and 3-prime RSA modules were easy to distinguish, since
1872 `N = p*q = 1 (mod 3)`, but `N = p*q*r = 2 (mod 3)`. Therefore, fingerprinting
1873 2-prime vs. 3-prime RSA keys was possible by computing N mod 3.
1874 This avoids possible fingerprinting of newly generated RSA modules.
1878 * Correct the extended master secret constant on EBCDIC systems. Without this
1879 fix TLS connections between an EBCDIC system and a non-EBCDIC system that
1880 negotiate EMS will fail. Unfortunately this also means that TLS connections
1881 between EBCDIC systems with this fix, and EBCDIC systems without this
1882 fix will fail if they negotiate EMS.
1886 * Changed the library initialisation so that the config file is now loaded
1887 by default. This was already the case for libssl. It now occurs for both
1888 libcrypto and libssl. Use the OPENSSL_INIT_NO_LOAD_CONFIG option to
1889 `OPENSSL_init_crypto()` to suppress automatic loading of a config file.
1893 * Introduced new error raising macros, `ERR_raise()` and `ERR_raise_data()`,
1894 where the former acts as a replacement for `ERR_put_error()`, and the
1895 latter replaces the combination `ERR_put_error()` + `ERR_add_error_data()`.
1896 `ERR_raise_data()` adds more flexibility by taking a format string and
1897 an arbitrary number of arguments following it, to be processed with
1902 * Introduced a new function, `OSSL_PROVIDER_available()`, which can be used
1903 to check if a named provider is loaded and available. When called, it
1904 will also activate all fallback providers if such are still present.
1908 * Enforce a minimum DH modulus size of 512 bits.
1912 * Changed DH parameters to generate the order q subgroup instead of 2q.
1913 Previously generated DH parameters are still accepted by DH_check
1914 but DH_generate_key works around that by clearing bit 0 of the
1915 private key for those. This avoids leaking bit 0 of the private key.
1919 * Significantly reduce secure memory usage by the randomness pools.
1923 * `{CRYPTO,OPENSSL}_mem_debug_{push,pop}` are now no-ops and have been
1928 * A new type, EVP_KEYEXCH, has been introduced to represent key exchange
1929 algorithms. An implementation of a key exchange algorithm can be obtained
1930 by using the function EVP_KEYEXCH_fetch(). An EVP_KEYEXCH algorithm can be
1931 used in a call to EVP_PKEY_derive_init_ex() which works in a similar way to
1932 the older EVP_PKEY_derive_init() function. See the man pages for the new
1933 functions for further details.
1937 * The EVP_PKEY_CTX_set_dh_pad() macro has now been converted to a function.
1941 * Removed the function names from error messages and deprecated the
1946 * Removed NextStep support and the macro OPENSSL_UNISTD
1950 * Removed DES_check_key. Also removed OPENSSL_IMPLEMENT_GLOBAL,
1951 OPENSSL_GLOBAL_REF, OPENSSL_DECLARE_GLOBAL.
1952 Also removed "export var as function" capability; we do not export
1953 variables, only functions.
1957 * RC5_32_set_key has been changed to return an int type, with 0 indicating
1958 an error and 1 indicating success. In previous versions of OpenSSL this
1959 was a void type. If a key was set longer than the maximum possible this
1964 * Support SM2 signing and verification schemes with X509 certificate.
1968 * Use SHA256 as the default digest for TS query in the `ts` app.
1972 * Change PBKDF2 to conform to SP800-132 instead of the older PKCS5 RFC2898.
1976 * Default cipher lists/suites are now available via a function, the
1977 #defines are deprecated.
1981 * Add target VC-WIN32-UWP, VC-WIN64A-UWP, VC-WIN32-ARM-UWP and
1982 VC-WIN64-ARM-UWP in Windows OneCore target for making building libraries
1983 for Windows Store apps easier. Also, the "no-uplink" option has been added.
1987 * Join the directories crypto/x509 and crypto/x509v3
1991 * Added command 'openssl kdf' that uses the EVP_KDF API.
1995 * Added command 'openssl mac' that uses the EVP_MAC API.
1999 * Added OPENSSL_info() to get diverse built-in OpenSSL data, such
2000 as default directories. Also added the command 'openssl info'
2001 for scripting purposes.
2005 * The functions AES_ige_encrypt() and AES_bi_ige_encrypt() have been
2010 * Add prediction resistance to the DRBG reseeding process.
2014 * Limit the number of blocks in a data unit for AES-XTS to 2^20 as
2015 mandated by IEEE Std 1619-2018.
2019 * Added newline escaping functionality to a filename when using openssl dgst.
2020 This output format is to replicate the output format found in the `*sum`
2021 checksum programs. This aims to preserve backward compatibility.
2023 *Matt Eaton, Richard Levitte, and Paul Dale*
2025 * Removed the heartbeat message in DTLS feature, as it has very
2026 little usage and doesn't seem to fulfill a valuable purpose.
2027 The configuration option is now deprecated.
2031 * Changed the output of 'openssl {digestname} < file' to display the
2032 digest name in its output.
2036 * Added a new generic trace API which provides support for enabling
2037 instrumentation through trace output.
2039 *Richard Levitte & Matthias St. Pierre*
2041 * Added build tests for C++. These are generated files that only do one
2042 thing, to include one public OpenSSL head file each. This tests that
2043 the public header files can be usefully included in a C++ application.
2045 This test isn't enabled by default. It can be enabled with the option
2046 'enable-buildtest-c++'.
2050 * Added KB KDF (EVP_KDF_KB) to EVP_KDF.
2054 * Added SSH KDF (EVP_KDF_SSHKDF) and KRB5 KDF (EVP_KDF_KRB5KDF) to EVP_KDF.
2058 * Added Single Step KDF (EVP_KDF_SS), X963 KDF, and X942 KDF to EVP_KDF.
2062 * Added KMAC to EVP_MAC.
2066 * Added property based algorithm implementation selection framework to
2071 * Added SCA hardening for modular field inversion in EC_GROUP through
2072 a new dedicated field_inv() pointer in EC_METHOD.
2073 This also addresses a leakage affecting conversions from projective
2074 to affine coordinates.
2076 *Billy Bob Brumley, Nicola Tuveri*
2078 * Added EVP_KDF, an EVP layer KDF API, to simplify adding KDF and PRF
2079 implementations. This includes an EVP_PKEY to EVP_KDF bridge for
2080 those algorithms that were already supported through the EVP_PKEY API
2081 (scrypt, TLS1 PRF and HKDF). The low-level KDF functions for PBKDF2
2082 and scrypt are now wrappers that call EVP_KDF.
2086 * Build devcrypto engine as a dynamic engine.
2088 *Eneas U de Queiroz*
2090 * Add keyed BLAKE2 to EVP_MAC.
2094 * Fix a bug in the computation of the endpoint-pair shared secret used
2095 by DTLS over SCTP. This breaks interoperability with older versions
2096 of OpenSSL like OpenSSL 1.1.0 and OpenSSL 1.0.2. There is a runtime
2097 switch SSL_MODE_DTLS_SCTP_LABEL_LENGTH_BUG (off by default) enabling
2098 interoperability with such broken implementations. However, enabling
2099 this switch breaks interoperability with correct implementations.
2101 * Fix a use after free bug in d2i_X509_PUBKEY when overwriting a
2102 re-used X509_PUBKEY object if the second PUBKEY is malformed.
2106 * Move strictness check from EVP_PKEY_asn1_new() to EVP_PKEY_asn1_add0().
2110 * Changed the license to the Apache License v2.0.
2114 * Switch to a new version scheme using three numbers MAJOR.MINOR.PATCH.
2116 - Major releases (indicated by incrementing the MAJOR release number)
2117 may introduce incompatible API/ABI changes.
2118 - Minor releases (indicated by incrementing the MINOR release number)
2119 may introduce new features but retain API/ABI compatibility.
2120 - Patch releases (indicated by incrementing the PATCH number)
2121 are intended for bug fixes and other improvements of existing
2122 features only (like improving performance or adding documentation)
2123 and retain API/ABI compatibility.
2127 * Add support for RFC5297 SIV mode (siv128), including AES-SIV.
2131 * Remove the 'dist' target and add a tarball building script. The
2132 'dist' target has fallen out of use, and it shouldn't be
2133 necessary to configure just to create a source distribution.
2137 * Recreate the OS390-Unix config target. It no longer relies on a
2138 special script like it did for OpenSSL pre-1.1.0.
2142 * Instead of having the source directories listed in Configure, add
2143 a 'build.info' keyword SUBDIRS to indicate what sub-directories to
2148 * Add GMAC to EVP_MAC.
2152 * Ported the HMAC, CMAC and SipHash EVP_PKEY_METHODs to EVP_MAC.
2156 * Added EVP_MAC, an EVP layer MAC API, to simplify adding MAC
2157 implementations. This includes a generic EVP_PKEY to EVP_MAC bridge,
2158 to facilitate the continued use of MACs through raw private keys in
2159 functionality such as `EVP_DigestSign*` and `EVP_DigestVerify*`.
2163 * Deprecate ECDH_KDF_X9_62().
2167 * Added EVP_PKEY_ECDH_KDF_X9_63 and ecdh_KDF_X9_63() as replacements for
2168 the EVP_PKEY_ECDH_KDF_X9_62 KDF type and ECDH_KDF_X9_62(). The old names
2169 are retained for backwards compatibility.
2173 * AES-XTS mode now enforces that its two keys are different to mitigate
2174 the attacked described in "Efficient Instantiations of Tweakable
2175 Blockciphers and Refinements to Modes OCB and PMAC" by Phillip Rogaway.
2176 Details of this attack can be obtained from:
2177 <http://web.cs.ucdavis.edu/%7Erogaway/papers/offsets.pdf>
2181 * Rename the object files, i.e. give them other names than in previous
2182 versions. Their names now include the name of the final product, as
2183 well as its type mnemonic (bin, lib, shlib).
2187 * Added new option for 'openssl list', '-objects', which will display the
2188 list of built in objects, i.e. OIDs with names.
2192 * Added the options `-crl_lastupdate` and `-crl_nextupdate` to `openssl ca`,
2193 allowing the `lastUpdate` and `nextUpdate` fields in the generated CRL to
2198 * Added support for Linux Kernel TLS data-path. The Linux Kernel data-path
2199 improves application performance by removing data copies and providing
2200 applications with zero-copy system calls such as sendfile and splice.
2204 * The SSL option SSL_OP_CLEANSE_PLAINTEXT is introduced.
2208 * `PKCS12_parse` now maintains the order of the parsed certificates
2209 when outputting them via `*ca` (rather than reversing it).
2213 * Deprecated pthread fork support methods.
2217 * Added support for FFDHE key exchange in TLS 1.3.
2221 * Added a new concept for OpenSSL plugability: providers. This
2222 functionality is designed to replace the ENGINE API and ENGINE
2223 implementations, and to be much more dynamic, allowing provider
2224 authors to introduce new algorithms among other things, as long as
2225 there's an API that supports the algorithm type.
2227 With this concept comes a new core API for interaction between
2228 libcrypto and provider implementations. Public libcrypto functions
2229 that want to use providers do so through this core API.
2231 The main documentation for this core API is found in
2232 doc/man7/provider.pod, doc/man7/provider-base.pod, and they in turn
2233 refer to other manuals describing the API specific for supported
2234 algorithm types (also called operations).
2241 ### Changes between 1.1.1l and 1.1.1m [xx XXX xxxx]
2243 * Avoid loading of a dynamic engine twice.
2247 * Prioritise DANE TLSA issuer certs over peer certs
2251 * Fixed random API for MacOS prior to 10.12
2253 These MacOS versions don't support the CommonCrypto APIs
2257 ### Changes between 1.1.1k and 1.1.1l [24 Aug 2021]
2259 * Fixed an SM2 Decryption Buffer Overflow.
2261 In order to decrypt SM2 encrypted data an application is expected to
2262 call the API function EVP_PKEY_decrypt(). Typically an application will
2263 call this function twice. The first time, on entry, the "out" parameter
2264 can be NULL and, on exit, the "outlen" parameter is populated with the
2265 buffer size required to hold the decrypted plaintext. The application
2266 can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt()
2267 again, but this time passing a non-NULL value for the "out" parameter.
2269 A bug in the implementation of the SM2 decryption code means that the
2270 calculation of the buffer size required to hold the plaintext returned
2271 by the first call to EVP_PKEY_decrypt() can be smaller than the actual
2272 size required by the second call. This can lead to a buffer overflow
2273 when EVP_PKEY_decrypt() is called by the application a second time with
2274 a buffer that is too small.
2276 A malicious attacker who is able present SM2 content for decryption to
2277 an application could cause attacker chosen data to overflow the buffer
2278 by up to a maximum of 62 bytes altering the contents of other data held
2279 after the buffer, possibly changing application behaviour or causing
2280 the application to crash. The location of the buffer is application
2281 dependent but is typically heap allocated.
2286 * Fixed various read buffer overruns processing ASN.1 strings
2288 ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING
2289 structure which contains a buffer holding the string data and a field
2290 holding the buffer length. This contrasts with normal C strings which
2291 are represented as a buffer for the string data which is terminated
2292 with a NUL (0) byte.
2294 Although not a strict requirement, ASN.1 strings that are parsed using
2295 OpenSSL's own "d2i" functions (and other similar parsing functions) as
2296 well as any string whose value has been set with the ASN1_STRING_set()
2297 function will additionally NUL terminate the byte array in the
2298 ASN1_STRING structure.
2300 However, it is possible for applications to directly construct valid
2301 ASN1_STRING structures which do not NUL terminate the byte array by
2302 directly setting the "data" and "length" fields in the ASN1_STRING
2303 array. This can also happen by using the ASN1_STRING_set0() function.
2305 Numerous OpenSSL functions that print ASN.1 data have been found to
2306 assume that the ASN1_STRING byte array will be NUL terminated, even
2307 though this is not guaranteed for strings that have been directly
2308 constructed. Where an application requests an ASN.1 structure to be
2309 printed, and where that ASN.1 structure contains ASN1_STRINGs that have
2310 been directly constructed by the application without NUL terminating
2311 the "data" field, then a read buffer overrun can occur.
2313 The same thing can also occur during name constraints processing
2314 of certificates (for example if a certificate has been directly
2315 constructed by the application instead of loading it via the OpenSSL
2316 parsing functions, and the certificate contains non NUL terminated
2317 ASN1_STRING structures). It can also occur in the X509_get1_email(),
2318 X509_REQ_get1_email() and X509_get1_ocsp() functions.
2320 If a malicious actor can cause an application to directly construct an
2321 ASN1_STRING and then process it through one of the affected OpenSSL
2322 functions then this issue could be hit. This might result in a crash
2323 (causing a Denial of Service attack). It could also result in the
2324 disclosure of private memory contents (such as private keys, or
2325 sensitive plaintext).
2330 ### Changes between 1.1.1j and 1.1.1k [25 Mar 2021]
2332 * Fixed a problem with verifying a certificate chain when using the
2333 X509_V_FLAG_X509_STRICT flag. This flag enables additional security checks of
2334 the certificates present in a certificate chain. It is not set by default.
2336 Starting from OpenSSL version 1.1.1h a check to disallow certificates in
2337 the chain that have explicitly encoded elliptic curve parameters was added
2338 as an additional strict check.
2340 An error in the implementation of this check meant that the result of a
2341 previous check to confirm that certificates in the chain are valid CA
2342 certificates was overwritten. This effectively bypasses the check
2343 that non-CA certificates must not be able to issue other certificates.
2345 If a "purpose" has been configured then there is a subsequent opportunity
2346 for checks that the certificate is a valid CA. All of the named "purpose"
2347 values implemented in libcrypto perform this check. Therefore, where
2348 a purpose is set the certificate chain will still be rejected even when the
2349 strict flag has been used. A purpose is set by default in libssl client and
2350 server certificate verification routines, but it can be overridden or
2351 removed by an application.
2353 In order to be affected, an application must explicitly set the
2354 X509_V_FLAG_X509_STRICT verification flag and either not set a purpose
2355 for the certificate verification or, in the case of TLS client or server
2356 applications, override the default purpose.
2361 * Fixed an issue where an OpenSSL TLS server may crash if sent a maliciously
2362 crafted renegotiation ClientHello message from a client. If a TLSv1.2
2363 renegotiation ClientHello omits the signature_algorithms extension (where it
2364 was present in the initial ClientHello), but includes a
2365 signature_algorithms_cert extension then a NULL pointer dereference will
2366 result, leading to a crash and a denial of service attack.
2368 A server is only vulnerable if it has TLSv1.2 and renegotiation enabled
2369 (which is the default configuration). OpenSSL TLS clients are not impacted by
2373 *Peter Kästle and Samuel Sapalski*
2375 ### Changes between 1.1.1i and 1.1.1j [16 Feb 2021]
2377 * Fixed the X509_issuer_and_serial_hash() function. It attempts to
2378 create a unique hash value based on the issuer and serial number data
2379 contained within an X509 certificate. However, it was failing to correctly
2380 handle any errors that may occur while parsing the issuer field (which might
2381 occur if the issuer field is maliciously constructed). This may subsequently
2382 result in a NULL pointer deref and a crash leading to a potential denial of
2388 * Fixed the RSA_padding_check_SSLv23() function and the RSA_SSLV23_PADDING
2389 padding mode to correctly check for rollback attacks. This is considered a
2390 bug in OpenSSL 1.1.1 because it does not support SSLv2. In 1.0.2 this is
2395 Fixed the EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate
2396 functions. Previously they could overflow the output length argument in some
2397 cases where the input length is close to the maximum permissible length for
2398 an integer on the platform. In such cases the return value from the function
2399 call would be 1 (indicating success), but the output length value would be
2400 negative. This could cause applications to behave incorrectly or crash.
2405 * Fixed SRP_Calc_client_key so that it runs in constant time. The previous
2406 implementation called BN_mod_exp without setting BN_FLG_CONSTTIME. This
2407 could be exploited in a side channel attack to recover the password. Since
2408 the attack is local host only this is outside of the current OpenSSL
2409 threat model and therefore no CVE is assigned.
2411 Thanks to Mohammed Sabt and Daniel De Almeida Braga for reporting this
2416 ### Changes between 1.1.1h and 1.1.1i [8 Dec 2020]
2418 * Fixed NULL pointer deref in the GENERAL_NAME_cmp function
2419 This function could crash if both GENERAL_NAMEs contain an EDIPARTYNAME.
2420 If an attacker can control both items being compared then this could lead
2421 to a possible denial of service attack. OpenSSL itself uses the
2422 GENERAL_NAME_cmp function for two purposes:
2423 1) Comparing CRL distribution point names between an available CRL and a
2424 CRL distribution point embedded in an X509 certificate
2425 2) When verifying that a timestamp response token signer matches the
2426 timestamp authority name (exposed via the API functions
2427 TS_RESP_verify_response and TS_RESP_verify_token)
2432 ### Changes between 1.1.1g and 1.1.1h [22 Sep 2020]
2434 * Certificates with explicit curve parameters are now disallowed in
2435 verification chains if the X509_V_FLAG_X509_STRICT flag is used.
2439 * The 'MinProtocol' and 'MaxProtocol' configuration commands now silently
2440 ignore TLS protocol version bounds when configuring DTLS-based contexts, and
2441 conversely, silently ignore DTLS protocol version bounds when configuring
2442 TLS-based contexts. The commands can be repeated to set bounds of both
2443 types. The same applies with the corresponding "min_protocol" and
2444 "max_protocol" command-line switches, in case some application uses both TLS
2447 SSL_CTX instances that are created for a fixed protocol version (e.g.
2448 TLSv1_server_method()) also silently ignore version bounds. Previously
2449 attempts to apply bounds to these protocol versions would result in an
2450 error. Now only the "version-flexible" SSL_CTX instances are subject to
2451 limits in configuration files in command-line options.
2455 * Handshake now fails if Extended Master Secret extension is dropped
2460 * The Oracle Developer Studio compiler will start reporting deprecated APIs
2462 ### Changes between 1.1.1f and 1.1.1g [21 Apr 2020]
2464 * Fixed segmentation fault in SSL_check_chain()
2465 Server or client applications that call the SSL_check_chain() function
2466 during or after a TLS 1.3 handshake may crash due to a NULL pointer
2467 dereference as a result of incorrect handling of the
2468 "signature_algorithms_cert" TLS extension. The crash occurs if an invalid
2469 or unrecognised signature algorithm is received from the peer. This could
2470 be exploited by a malicious peer in a Denial of Service attack.
2475 * Added AES consttime code for no-asm configurations
2476 an optional constant time support for AES was added
2477 when building openssl for no-asm.
2478 Enable with: ./config no-asm -DOPENSSL_AES_CONST_TIME
2479 Disable with: ./config no-asm -DOPENSSL_NO_AES_CONST_TIME
2480 At this time this feature is by default disabled.
2481 It will be enabled by default in 3.0.
2485 ### Changes between 1.1.1e and 1.1.1f [31 Mar 2020]
2487 * Revert the change of EOF detection while reading in libssl to avoid
2488 regressions in applications depending on the current way of reporting
2489 the EOF. As the existing method is not fully accurate the change to
2490 reporting the EOF via SSL_ERROR_SSL is kept on the current development
2491 branch and will be present in the 3.0 release.
2495 * Revised BN_generate_prime_ex to not avoid factors 3..17863 in p-1
2496 when primes for RSA keys are computed.
2497 Since we previously always generated primes == 2 (mod 3) for RSA keys,
2498 the 2-prime and 3-prime RSA modules were easy to distinguish, since
2499 N = p*q = 1 (mod 3), but N = p*q*r = 2 (mod 3). Therefore, fingerprinting
2500 2-prime vs. 3-prime RSA keys was possible by computing N mod 3.
2501 This avoids possible fingerprinting of newly generated RSA modules.
2505 ### Changes between 1.1.1d and 1.1.1e [17 Mar 2020]
2507 * Properly detect EOF while reading in libssl. Previously if we hit an EOF
2508 while reading in libssl then we would report an error back to the
2509 application (SSL_ERROR_SYSCALL) but errno would be 0. We now add
2510 an error to the stack (which means we instead return SSL_ERROR_SSL) and
2511 therefore give a hint as to what went wrong.
2515 * Check that ed25519 and ed448 are allowed by the security level. Previously
2516 signature algorithms not using an MD were not being checked that they were
2517 allowed by the security level.
2521 * Fixed SSL_get_servername() behaviour. The behaviour of SSL_get_servername()
2522 was not quite right. The behaviour was not consistent between resumption
2523 and normal handshakes, and also not quite consistent with historical
2524 behaviour. The behaviour in various scenarios has been clarified and
2525 it has been updated to make it match historical behaviour as closely as
2530 * *[VMS only]* The header files that the VMS compilers include automatically,
2531 `__DECC_INCLUDE_PROLOGUE.H` and `__DECC_INCLUDE_EPILOGUE.H`, use pragmas
2532 that the C++ compiler doesn't understand. This is a shortcoming in the
2533 compiler, but can be worked around with `__cplusplus` guards.
2535 C++ applications that use OpenSSL libraries must be compiled using the
2536 qualifier `/NAMES=(AS_IS,SHORTENED)` to be able to use all the OpenSSL
2537 functions. Otherwise, only functions with symbols of less than 31
2538 characters can be used, as the linker will not be able to successfully
2539 resolve symbols with longer names.
2543 * Added a new method to gather entropy on VMS, based on SYS$GET_ENTROPY.
2544 The presence of this system service is determined at run-time.
2548 * Print all values for a PKCS#12 attribute with 'openssl pkcs12', not just
2553 ### Changes between 1.1.1c and 1.1.1d [10 Sep 2019]
2555 * Fixed a fork protection issue. OpenSSL 1.1.1 introduced a rewritten random
2556 number generator (RNG). This was intended to include protection in the
2557 event of a fork() system call in order to ensure that the parent and child
2558 processes did not share the same RNG state. However, this protection was not
2559 being used in the default case.
2561 A partial mitigation for this issue is that the output from a high
2562 precision timer is mixed into the RNG state so the likelihood of a parent
2563 and child process sharing state is significantly reduced.
2565 If an application already calls OPENSSL_init_crypto() explicitly using
2566 OPENSSL_INIT_ATFORK then this problem does not occur at all.
2569 *Matthias St. Pierre*
2571 * For built-in EC curves, ensure an EC_GROUP built from the curve name is
2572 used even when parsing explicit parameters, when loading a encoded key
2573 or calling `EC_GROUP_new_from_ecpkparameters()`/
2574 `EC_GROUP_new_from_ecparameters()`.
2575 This prevents bypass of security hardening and performance gains,
2576 especially for curves with specialized EC_METHODs.
2577 By default, if a key encoded with explicit parameters is loaded and later
2578 encoded, the output is still encoded with explicit parameters, even if
2579 internally a "named" EC_GROUP is used for computation.
2583 * Compute ECC cofactors if not provided during EC_GROUP construction. Before
2584 this change, EC_GROUP_set_generator would accept order and/or cofactor as
2585 NULL. After this change, only the cofactor parameter can be NULL. It also
2586 does some minimal sanity checks on the passed order.
2591 * Fixed a padding oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey.
2592 An attack is simple, if the first CMS_recipientInfo is valid but the
2593 second CMS_recipientInfo is chosen ciphertext. If the second
2594 recipientInfo decodes to PKCS #1 v1.5 form plaintext, the correct
2595 encryption key will be replaced by garbage, and the message cannot be
2596 decoded, but if the RSA decryption fails, the correct encryption key is
2597 used and the recipient will not notice the attack.
2598 As a work around for this potential attack the length of the decrypted
2599 key must be equal to the cipher default key length, in case the
2600 certificate is not given and all recipientInfo are tried out.
2601 The old behaviour can be re-enabled in the CMS code by setting the
2602 CMS_DEBUG_DECRYPT flag.
2607 * Early start up entropy quality from the DEVRANDOM seed source has been
2608 improved for older Linux systems. The RAND subsystem will wait for
2609 /dev/random to be producing output before seeding from /dev/urandom.
2610 The seeded state is stored for future library initialisations using
2611 a system global shared memory segment. The shared memory identifier
2612 can be configured by defining OPENSSL_RAND_SEED_DEVRANDOM_SHM_ID to
2613 the desired value. The default identifier is 114.
2617 * Correct the extended master secret constant on EBCDIC systems. Without this
2618 fix TLS connections between an EBCDIC system and a non-EBCDIC system that
2619 negotiate EMS will fail. Unfortunately this also means that TLS connections
2620 between EBCDIC systems with this fix, and EBCDIC systems without this
2621 fix will fail if they negotiate EMS.
2625 * Use Windows installation paths in the mingw builds
2627 Mingw isn't a POSIX environment per se, which means that Windows
2628 paths should be used for installation.
2633 * Changed DH_check to accept parameters with order q and 2q subgroups.
2634 With order 2q subgroups the bit 0 of the private key is not secret
2635 but DH_generate_key works around that by clearing bit 0 of the
2636 private key for those. This avoids leaking bit 0 of the private key.
2640 * Significantly reduce secure memory usage by the randomness pools.
2644 * Revert the DEVRANDOM_WAIT feature for Linux systems
2646 The DEVRANDOM_WAIT feature added a select() call to wait for the
2647 /dev/random device to become readable before reading from the
2648 /dev/urandom device.
2650 It turned out that this change had negative side effects on
2651 performance which were not acceptable. After some discussion it
2652 was decided to revert this feature and leave it up to the OS
2653 resp. the platform maintainer to ensure a proper initialization
2654 during early boot time.
2656 *Matthias St. Pierre*
2658 ### Changes between 1.1.1b and 1.1.1c [28 May 2019]
2660 * Add build tests for C++. These are generated files that only do one
2661 thing, to include one public OpenSSL head file each. This tests that
2662 the public header files can be usefully included in a C++ application.
2664 This test isn't enabled by default. It can be enabled with the option
2665 'enable-buildtest-c++'.
2669 * Enable SHA3 pre-hashing for ECDSA and DSA.
2673 * Change the default RSA, DSA and DH size to 2048 bit instead of 1024.
2674 This changes the size when using the `genpkey` command when no size is given.
2675 It fixes an omission in earlier changes that changed all RSA, DSA and DH
2676 generation commands to use 2048 bits by default.
2680 * Reorganize the manual pages to consistently have RETURN VALUES,
2681 EXAMPLES, SEE ALSO and HISTORY come in that order, and adjust
2682 util/fix-doc-nits accordingly.
2684 *Paul Yang, Joshua Lock*
2686 * Add the missing accessor EVP_PKEY_get0_engine()
2690 * Have commands like `s_client` and `s_server` output the signature scheme
2691 along with other cipher suite parameters when debugging.
2695 * Make OPENSSL_config() error agnostic again.
2699 * Do the error handling in RSA decryption constant time.
2703 * Prevent over long nonces in ChaCha20-Poly1305.
2705 ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input
2706 for every encryption operation. RFC 7539 specifies that the nonce value
2707 (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length
2708 and front pads the nonce with 0 bytes if it is less than 12
2709 bytes. However it also incorrectly allows a nonce to be set of up to 16
2710 bytes. In this case only the last 12 bytes are significant and any
2711 additional leading bytes are ignored.
2713 It is a requirement of using this cipher that nonce values are
2714 unique. Messages encrypted using a reused nonce value are susceptible to
2715 serious confidentiality and integrity attacks. If an application changes
2716 the default nonce length to be longer than 12 bytes and then makes a
2717 change to the leading bytes of the nonce expecting the new value to be a
2718 new unique nonce then such an application could inadvertently encrypt
2719 messages with a reused nonce.
2721 Additionally the ignored bytes in a long nonce are not covered by the
2722 integrity guarantee of this cipher. Any application that relies on the
2723 integrity of these ignored leading bytes of a long nonce may be further
2724 affected. Any OpenSSL internal use of this cipher, including in SSL/TLS,
2725 is safe because no such use sets such a long nonce value. However user
2726 applications that use this cipher directly and set a non-default nonce
2727 length to be longer than 12 bytes may be vulnerable.
2729 This issue was reported to OpenSSL on 16th of March 2019 by Joran Dirk
2735 * Add DEVRANDOM_WAIT feature for Linux systems
2737 On older Linux systems where the getrandom() system call is not available,
2738 OpenSSL normally uses the /dev/urandom device for seeding its CSPRNG.
2739 Contrary to getrandom(), the /dev/urandom device will not block during
2740 early boot when the kernel CSPRNG has not been seeded yet.
2742 To mitigate this known weakness, use select() to wait for /dev/random to
2743 become readable before reading from /dev/urandom.
2745 * Ensure that SM2 only uses SM3 as digest algorithm
2749 ### Changes between 1.1.1a and 1.1.1b [26 Feb 2019]
2751 * Change the info callback signals for the start and end of a post-handshake
2752 message exchange in TLSv1.3. In 1.1.1/1.1.1a we used SSL_CB_HANDSHAKE_START
2753 and SSL_CB_HANDSHAKE_DONE. Experience has shown that many applications get
2754 confused by this and assume that a TLSv1.2 renegotiation has started. This
2755 can break KeyUpdate handling. Instead we no longer signal the start and end
2756 of a post handshake message exchange (although the messages themselves are
2757 still signalled). This could break some applications that were expecting
2758 the old signals. However without this KeyUpdate is not usable for many
2763 ### Changes between 1.1.1 and 1.1.1a [20 Nov 2018]
2765 * Timing vulnerability in DSA signature generation
2767 The OpenSSL DSA signature algorithm has been shown to be vulnerable to a
2768 timing side channel attack. An attacker could use variations in the signing
2769 algorithm to recover the private key.
2771 This issue was reported to OpenSSL on 16th October 2018 by Samuel Weiser.
2776 * Timing vulnerability in ECDSA signature generation
2778 The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a
2779 timing side channel attack. An attacker could use variations in the signing
2780 algorithm to recover the private key.
2782 This issue was reported to OpenSSL on 25th October 2018 by Samuel Weiser.
2787 * Fixed the issue that RAND_add()/RAND_seed() silently discards random input
2788 if its length exceeds 4096 bytes. The limit has been raised to a buffer size
2789 of two gigabytes and the error handling improved.
2791 This issue was reported to OpenSSL by Dr. Falko Strenzke. It has been
2792 categorized as a normal bug, not a security issue, because the DRBG reseeds
2793 automatically and is fully functional even without additional randomness
2794 provided by the application.
2796 ### Changes between 1.1.0i and 1.1.1 [11 Sep 2018]
2798 * Add a new ClientHello callback. Provides a callback interface that gives
2799 the application the ability to adjust the nascent SSL object at the
2800 earliest stage of ClientHello processing, immediately after extensions have
2801 been collected but before they have been processed. In particular, this
2802 callback can adjust the supported TLS versions in response to the contents
2807 * Add SM2 base algorithm support.
2811 * s390x assembly pack: add (improved) hardware-support for the following
2812 cryptographic primitives: sha3, shake, aes-gcm, aes-ccm, aes-ctr, aes-ofb,
2813 aes-cfb/cfb8, aes-ecb.
2817 * Make EVP_PKEY_asn1_new() a bit stricter about its input. A NULL pem_str
2818 parameter is no longer accepted, as it leads to a corrupt table. NULL
2819 pem_str is reserved for alias entries only.
2823 * Use the new ec_scalar_mul_ladder scaffold to implement a specialized ladder
2824 step for prime curves. The new implementation is based on formulae from
2825 differential addition-and-doubling in homogeneous projective coordinates
2826 from Izu-Takagi "A fast parallel elliptic curve multiplication resistant
2827 against side channel attacks" and Brier-Joye "Weierstrass Elliptic Curves
2828 and Side-Channel Attacks" Eq. (8) for y-coordinate recovery, modified
2829 to work in projective coordinates.
2831 *Billy Bob Brumley, Nicola Tuveri*
2833 * Change generating and checking of primes so that the error rate of not
2834 being prime depends on the intended use based on the size of the input.
2835 For larger primes this will result in more rounds of Miller-Rabin.
2836 The maximal error rate for primes with more than 1080 bits is lowered
2839 *Kurt Roeckx, Annie Yousar*
2841 * Increase the number of Miller-Rabin rounds for DSA key generating to 64.
2845 * The 'tsget' script is renamed to 'tsget.pl', to avoid confusion when
2846 moving between systems, and to avoid confusion when a Windows build is
2847 done with mingw vs with MSVC. For POSIX installs, there's still a
2848 symlink or copy named 'tsget' to avoid that confusion as well.
2852 * Revert blinding in ECDSA sign and instead make problematic addition
2853 length-invariant. Switch even to fixed-length Montgomery multiplication.
2857 * Use the new ec_scalar_mul_ladder scaffold to implement a specialized ladder
2858 step for binary curves. The new implementation is based on formulae from
2859 differential addition-and-doubling in mixed Lopez-Dahab projective
2860 coordinates, modified to independently blind the operands.
2862 *Billy Bob Brumley, Sohaib ul Hassan, Nicola Tuveri*
2864 * Add a scaffold to optionally enhance the Montgomery ladder implementation
2865 for `ec_scalar_mul_ladder` (formerly `ec_mul_consttime`) allowing
2866 EC_METHODs to implement their own specialized "ladder step", to take
2867 advantage of more favorable coordinate systems or more efficient
2868 differential addition-and-doubling algorithms.
2870 *Billy Bob Brumley, Sohaib ul Hassan, Nicola Tuveri*
2872 * Modified the random device based seed sources to keep the relevant
2873 file descriptors open rather than reopening them on each access.
2874 This allows such sources to operate in a chroot() jail without
2875 the associated device nodes being available. This behaviour can be
2876 controlled using RAND_keep_random_devices_open().
2880 * Numerous side-channel attack mitigations have been applied. This may have
2881 performance impacts for some algorithms for the benefit of improved
2882 security. Specific changes are noted in this change log by their respective
2887 * AIX shared library support overhaul. Switch to AIX "natural" way of
2888 handling shared libraries, which means collecting shared objects of
2889 different versions and bitnesses in one common archive. This allows to
2890 mitigate conflict between 1.0 and 1.1 side-by-side installations. It
2891 doesn't affect the way 3rd party applications are linked, only how
2892 multi-version installation is managed.
2896 * Make ec_group_do_inverse_ord() more robust and available to other
2897 EC cryptosystems, so that irrespective of BN_FLG_CONSTTIME, SCA
2898 mitigations are applied to the fallback BN_mod_inverse().
2899 When using this function rather than BN_mod_inverse() directly, new
2900 EC cryptosystem implementations are then safer-by-default.
2904 * Add coordinate blinding for EC_POINT and implement projective
2905 coordinate blinding for generic prime curves as a countermeasure to
2906 chosen point SCA attacks.
2908 *Sohaib ul Hassan, Nicola Tuveri, Billy Bob Brumley*
2910 * Add blinding to ECDSA and DSA signatures to protect against side channel
2911 attacks discovered by Keegan Ryan (NCC Group).
2915 * Enforce checking in the `pkeyutl` command to ensure that the input
2916 length does not exceed the maximum supported digest length when performing
2917 a sign, verify or verifyrecover operation.
2921 * SSL_MODE_AUTO_RETRY is enabled by default. Applications that use blocking
2922 I/O in combination with something like select() or poll() will hang. This
2923 can be turned off again using SSL_CTX_clear_mode().
2924 Many applications do not properly handle non-application data records, and
2925 TLS 1.3 sends more of such records. Setting SSL_MODE_AUTO_RETRY works
2926 around the problems in those applications, but can also break some.
2927 It's recommended to read the manpages about SSL_read(), SSL_write(),
2928 SSL_get_error(), SSL_shutdown(), SSL_CTX_set_mode() and
2929 SSL_CTX_set_read_ahead() again.
2933 * When unlocking a pass phrase protected PEM file or PKCS#8 container, we
2934 now allow empty (zero character) pass phrases.
2938 * Apply blinding to binary field modular inversion and remove patent
2939 pending (OPENSSL_SUN_GF2M_DIV) BN_GF2m_mod_div implementation.
2943 * Deprecate ec2_mult.c and unify scalar multiplication code paths for
2944 binary and prime elliptic curves.
2948 * Remove ECDSA nonce padding: EC_POINT_mul is now responsible for
2949 constant time fixed point multiplication.
2953 * Revise elliptic curve scalar multiplication with timing attack
2954 defenses: ec_wNAF_mul redirects to a constant time implementation
2955 when computing fixed point and variable point multiplication (which
2956 in OpenSSL are mostly used with secret scalars in keygen, sign,
2957 ECDH derive operations).
2958 *Billy Bob Brumley, Nicola Tuveri, Cesar Pereida García,
2961 * Updated CONTRIBUTING
2965 * Updated DRBG / RAND to request nonce and additional low entropy
2966 randomness from the system.
2968 *Matthias St. Pierre*
2970 * Updated 'openssl rehash' to use OpenSSL consistent default.
2974 * Moved the load of the ssl_conf module to libcrypto, which helps
2975 loading engines that libssl uses before libssl is initialised.
2979 * Added EVP_PKEY_sign() and EVP_PKEY_verify() for EdDSA
2983 * Fixed X509_NAME_ENTRY_set to get multi-valued RDNs right in all cases.
2985 *Ingo Schwarze, Rich Salz*
2987 * Added output of accepting IP address and port for 'openssl s_server'
2991 * Added a new API for TLSv1.3 ciphersuites:
2992 SSL_CTX_set_ciphersuites()
2993 SSL_set_ciphersuites()
2997 * Memory allocation failures consistently add an error to the error
3002 * Don't use OPENSSL_ENGINES and OPENSSL_CONF environment values
3003 in libcrypto when run as setuid/setgid.
3007 * Load any config file by default when libssl is used.
3011 * Added new public header file <openssl/rand_drbg.h> and documentation
3012 for the RAND_DRBG API. See manual page RAND_DRBG(7) for an overview.
3014 *Matthias St. Pierre*
3016 * QNX support removed (cannot find contributors to get their approval
3017 for the license change).
3021 * TLSv1.3 replay protection for early data has been implemented. See the
3022 SSL_read_early_data() man page for further details.
3026 * Separated TLSv1.3 ciphersuite configuration out from TLSv1.2 ciphersuite
3027 configuration. TLSv1.3 ciphersuites are not compatible with TLSv1.2 and
3028 below. Similarly TLSv1.2 ciphersuites are not compatible with TLSv1.3.
3029 In order to avoid issues where legacy TLSv1.2 ciphersuite configuration
3030 would otherwise inadvertently disable all TLSv1.3 ciphersuites the
3031 configuration has been separated out. See the ciphers man page or the
3032 SSL_CTX_set_ciphersuites() man page for more information.
3036 * On POSIX (BSD, Linux, ...) systems the ocsp(1) command running
3037 in responder mode now supports the new "-multi" option, which
3038 spawns the specified number of child processes to handle OCSP
3039 requests. The "-timeout" option now also limits the OCSP
3040 responder's patience to wait to receive the full client request
3041 on a newly accepted connection. Child processes are respawned
3042 as needed, and the CA index file is automatically reloaded
3043 when changed. This makes it possible to run the "ocsp" responder
3044 as a long-running service, making the OpenSSL CA somewhat more
3045 feature-complete. In this mode, most diagnostic messages logged
3046 after entering the event loop are logged via syslog(3) rather than
3051 * Added support for X448 and Ed448. Heavily based on original work by
3056 * Extend OSSL_STORE with capabilities to search and to narrow the set of
3057 objects loaded. This adds the functions OSSL_STORE_expect() and
3058 OSSL_STORE_find() as well as needed tools to construct searches and
3059 get the search data out of them.
3063 * Support for TLSv1.3 added. Note that users upgrading from an earlier
3064 version of OpenSSL should review their configuration settings to ensure
3065 that they are still appropriate for TLSv1.3. For further information see:
3066 <https://wiki.openssl.org/index.php/TLS1.3>
3070 * Grand redesign of the OpenSSL random generator
3072 The default RAND method now utilizes an AES-CTR DRBG according to
3073 NIST standard SP 800-90Ar1. The new random generator is essentially
3074 a port of the default random generator from the OpenSSL FIPS 2.0
3075 object module. It is a hybrid deterministic random bit generator
3076 using an AES-CTR bit stream and which seeds and reseeds itself
3077 automatically using trusted system entropy sources.
3079 Some of its new features are:
3080 - Support for multiple DRBG instances with seed chaining.
3081 - The default RAND method makes use of a DRBG.
3082 - There is a public and private DRBG instance.
3083 - The DRBG instances are fork-safe.
3084 - Keep all global DRBG instances on the secure heap if it is enabled.
3085 - The public and private DRBG instance are per thread for lock free
3088 *Paul Dale, Benjamin Kaduk, Kurt Roeckx, Rich Salz, Matthias St. Pierre*
3090 * Changed Configure so it only says what it does and doesn't dump
3091 so much data. Instead, ./configdata.pm should be used as a script
3092 to display all sorts of configuration data.
3096 * Added processing of "make variables" to Configure.
3100 * Added SHA512/224 and SHA512/256 algorithm support.
3104 * The last traces of Netware support, first removed in 1.1.0, have
3109 * Get rid of Makefile.shared, and in the process, make the processing
3110 of certain files (rc.obj, or the .def/.map/.opt files produced from
3111 the ordinal files) more visible and hopefully easier to trace and
3112 debug (or make silent).
3116 * Make it possible to have environment variable assignments as
3117 arguments to config / Configure.
3121 * Add multi-prime RSA (RFC 8017) support.
3125 * Add SM3 implemented according to GB/T 32905-2016
3126 *Jack Lloyd <jack.lloyd@ribose.com>,*
3127 *Ronald Tse <ronald.tse@ribose.com>,*
3128 *Erick Borsboom <erick.borsboom@ribose.com>*
3130 * Add 'Maximum Fragment Length' TLS extension negotiation and support
3131 as documented in RFC6066.
3132 Based on a patch from Tomasz Moń
3134 *Filipe Raimundo da Silva*
3136 * Add SM4 implemented according to GB/T 32907-2016.
3137 *Jack Lloyd <jack.lloyd@ribose.com>,*
3138 *Ronald Tse <ronald.tse@ribose.com>,*
3139 *Erick Borsboom <erick.borsboom@ribose.com>*
3141 * Reimplement -newreq-nodes and ERR_error_string_n; the
3142 original author does not agree with the license change.
3146 * Add ARIA AEAD TLS support.
3150 * Some macro definitions to support VS6 have been removed. Visual
3151 Studio 6 has not worked since 1.1.0
3155 * Add ERR_clear_last_mark(), to allow callers to clear the last mark
3156 without clearing the errors.
3160 * Add "atfork" functions. If building on a system that without
3161 pthreads, see doc/man3/OPENSSL_fork_prepare.pod for application
3162 requirements. The RAND facility now uses/requires this.
3170 * The UI API becomes a permanent and integral part of libcrypto, i.e.
3171 not possible to disable entirely. However, it's still possible to
3172 disable the console reading UI method, UI_OpenSSL() (use UI_null()
3175 To disable, configure with 'no-ui-console'. 'no-ui' is still
3176 possible to use as an alias. Check at compile time with the
3177 macro OPENSSL_NO_UI_CONSOLE. The macro OPENSSL_NO_UI is still
3178 possible to check and is an alias for OPENSSL_NO_UI_CONSOLE.
3182 * Add a STORE module, which implements a uniform and URI based reader of
3183 stores that can contain keys, certificates, CRLs and numerous other
3184 objects. The main API is loosely based on a few stdio functions,
3185 and includes OSSL_STORE_open, OSSL_STORE_load, OSSL_STORE_eof,
3186 OSSL_STORE_error and OSSL_STORE_close.
3187 The implementation uses backends called "loaders" to implement arbitrary
3188 URI schemes. There is one built in "loader" for the 'file' scheme.
3192 * Add devcrypto engine. This has been implemented against cryptodev-linux,
3193 then adjusted to work on FreeBSD 8.4 as well.
3194 Enable by configuring with 'enable-devcryptoeng'. This is done by default
3195 on BSD implementations, as cryptodev.h is assumed to exist on all of them.
3199 * Module names can prefixed with OSSL_ or OPENSSL_. This affects
3200 util/mkerr.pl, which is adapted to allow those prefixes, leading to
3201 error code calls like this:
3203 OSSL_FOOerr(OSSL_FOO_F_SOMETHING, OSSL_FOO_R_WHATEVER);
3205 With this change, we claim the namespaces OSSL and OPENSSL in a manner
3206 that can be encoded in C. For the foreseeable future, this will only
3209 *Richard Levitte and Tim Hudson*
3211 * Removed BSD cryptodev engine.
3215 * Add a build target 'build_all_generated', to build all generated files
3216 and only that. This can be used to prepare everything that requires
3217 things like perl for a system that lacks perl and then move everything
3218 to that system and do the rest of the build there.
3222 * In the UI interface, make it possible to duplicate the user data. This
3223 can be used by engines that need to retain the data for a longer time
3224 than just the call where this user data is passed.
3228 * Ignore the '-named_curve auto' value for compatibility of applications
3231 *Tomáš Mráz <tmraz@fedoraproject.org>*
3233 * Fragmented SSL/TLS alerts are no longer accepted. An alert message is 2
3234 bytes long. In theory it is permissible in SSLv3 - TLSv1.2 to fragment such
3235 alerts across multiple records (some of which could be empty). In practice
3236 it make no sense to send an empty alert record, or to fragment one. TLSv1.3
3237 prohibits this altogether and other libraries (BoringSSL, NSS) do not
3238 support this at all. Supporting it adds significant complexity to the
3239 record layer, and its removal is unlikely to cause interoperability
3244 * Add the ASN.1 types INT32, UINT32, INT64, UINT64 and variants prefixed
3245 with Z. These are meant to replace LONG and ZLONG and to be size safe.
3246 The use of LONG and ZLONG is discouraged and scheduled for deprecation
3251 * Add the 'z' and 'j' modifiers to BIO_printf() et al formatting string,
3252 'z' is to be used for [s]size_t, and 'j' - with [u]int64_t.
3254 *Richard Levitte, Andy Polyakov*
3256 * Add EC_KEY_get0_engine(), which does for EC_KEY what RSA_get0_engine()
3261 * Have 'config' recognise 64-bit mingw and choose 'mingw64' as the target
3262 platform rather than 'mingw'.
3266 * The functions X509_STORE_add_cert and X509_STORE_add_crl return
3267 success if they are asked to add an object which already exists
3268 in the store. This change cascades to other functions which load
3269 certificates and CRLs.
3273 * x86_64 assembly pack: annotate code with DWARF CFI directives to
3274 facilitate stack unwinding even from assembly subroutines.
3278 * Remove VAX C specific definitions of OPENSSL_EXPORT, OPENSSL_EXTERN.
3279 Also remove OPENSSL_GLOBAL entirely, as it became a no-op.
3283 * Remove the VMS-specific reimplementation of gmtime from crypto/o_times.c.
3284 VMS C's RTL has a fully up to date gmtime() and gmtime_r() since V7.1,
3285 which is the minimum version we support.
3289 * Certificate time validation (X509_cmp_time) enforces stricter
3290 compliance with RFC 5280. Fractional seconds and timezone offsets
3291 are no longer allowed.
3295 * Add support for ARIA
3299 * s_client will now send the Server Name Indication (SNI) extension by
3300 default unless the new "-noservername" option is used. The server name is
3301 based on the host provided to the "-connect" option unless overridden by
3302 using "-servername".
3306 * Add support for SipHash
3310 * OpenSSL now fails if it receives an unrecognised record type in TLS1.0
3311 or TLS1.1. Previously this only happened in SSLv3 and TLS1.2. This is to
3312 prevent issues where no progress is being made and the peer continually
3313 sends unrecognised record types, using up resources processing them.
3317 * 'openssl passwd' can now produce SHA256 and SHA512 based output,
3318 using the algorithm defined in
3319 <https://www.akkadia.org/drepper/SHA-crypt.txt>
3323 * Heartbeat support has been removed; the ABI is changed for now.
3325 *Richard Levitte, Rich Salz*
3327 * Support for SSL_OP_NO_ENCRYPT_THEN_MAC in SSL_CONF_cmd.
3331 * The RSA "null" method, which was partially supported to avoid patent
3332 issues, has been replaced to always returns NULL.
3339 ### Changes between 1.1.0k and 1.1.0l [10 Sep 2019]
3341 * For built-in EC curves, ensure an EC_GROUP built from the curve name is
3342 used even when parsing explicit parameters, when loading a encoded key
3343 or calling `EC_GROUP_new_from_ecpkparameters()`/
3344 `EC_GROUP_new_from_ecparameters()`.
3345 This prevents bypass of security hardening and performance gains,
3346 especially for curves with specialized EC_METHODs.
3347 By default, if a key encoded with explicit parameters is loaded and later
3348 encoded, the output is still encoded with explicit parameters, even if
3349 internally a "named" EC_GROUP is used for computation.
3353 * Compute ECC cofactors if not provided during EC_GROUP construction. Before
3354 this change, EC_GROUP_set_generator would accept order and/or cofactor as
3355 NULL. After this change, only the cofactor parameter can be NULL. It also
3356 does some minimal sanity checks on the passed order.
3361 * Fixed a padding oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey.
3362 An attack is simple, if the first CMS_recipientInfo is valid but the
3363 second CMS_recipientInfo is chosen ciphertext. If the second
3364 recipientInfo decodes to PKCS #1 v1.5 form plaintext, the correct
3365 encryption key will be replaced by garbage, and the message cannot be
3366 decoded, but if the RSA decryption fails, the correct encryption key is
3367 used and the recipient will not notice the attack.
3368 As a work around for this potential attack the length of the decrypted
3369 key must be equal to the cipher default key length, in case the
3370 certificate is not given and all recipientInfo are tried out.
3371 The old behaviour can be re-enabled in the CMS code by setting the
3372 CMS_DEBUG_DECRYPT flag.
3377 * Use Windows installation paths in the mingw builds
3379 Mingw isn't a POSIX environment per se, which means that Windows
3380 paths should be used for installation.
3385 ### Changes between 1.1.0j and 1.1.0k [28 May 2019]
3387 * Change the default RSA, DSA and DH size to 2048 bit instead of 1024.
3388 This changes the size when using the `genpkey` command when no size is given.
3389 It fixes an omission in earlier changes that changed all RSA, DSA and DH
3390 generation commands to use 2048 bits by default.
3394 * Prevent over long nonces in ChaCha20-Poly1305.
3396 ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input
3397 for every encryption operation. RFC 7539 specifies that the nonce value
3398 (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length
3399 and front pads the nonce with 0 bytes if it is less than 12
3400 bytes. However it also incorrectly allows a nonce to be set of up to 16
3401 bytes. In this case only the last 12 bytes are significant and any
3402 additional leading bytes are ignored.
3404 It is a requirement of using this cipher that nonce values are
3405 unique. Messages encrypted using a reused nonce value are susceptible to
3406 serious confidentiality and integrity attacks. If an application changes
3407 the default nonce length to be longer than 12 bytes and then makes a
3408 change to the leading bytes of the nonce expecting the new value to be a
3409 new unique nonce then such an application could inadvertently encrypt
3410 messages with a reused nonce.
3412 Additionally the ignored bytes in a long nonce are not covered by the
3413 integrity guarantee of this cipher. Any application that relies on the
3414 integrity of these ignored leading bytes of a long nonce may be further
3415 affected. Any OpenSSL internal use of this cipher, including in SSL/TLS,
3416 is safe because no such use sets such a long nonce value. However user
3417 applications that use this cipher directly and set a non-default nonce
3418 length to be longer than 12 bytes may be vulnerable.
3420 This issue was reported to OpenSSL on 16th of March 2019 by Joran Dirk
3426 * Added SCA hardening for modular field inversion in EC_GROUP through
3427 a new dedicated field_inv() pointer in EC_METHOD.
3428 This also addresses a leakage affecting conversions from projective
3429 to affine coordinates.
3431 *Billy Bob Brumley, Nicola Tuveri*
3433 * Fix a use after free bug in d2i_X509_PUBKEY when overwriting a
3434 re-used X509_PUBKEY object if the second PUBKEY is malformed.
3438 * Move strictness check from EVP_PKEY_asn1_new() to EVP_PKEY_asn1_add0().
3442 * Remove the 'dist' target and add a tarball building script. The
3443 'dist' target has fallen out of use, and it shouldn't be
3444 necessary to configure just to create a source distribution.
3448 ### Changes between 1.1.0i and 1.1.0j [20 Nov 2018]
3450 * Timing vulnerability in DSA signature generation
3452 The OpenSSL DSA signature algorithm has been shown to be vulnerable to a
3453 timing side channel attack. An attacker could use variations in the signing
3454 algorithm to recover the private key.
3456 This issue was reported to OpenSSL on 16th October 2018 by Samuel Weiser.
3461 * Timing vulnerability in ECDSA signature generation
3463 The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a
3464 timing side channel attack. An attacker could use variations in the signing
3465 algorithm to recover the private key.
3467 This issue was reported to OpenSSL on 25th October 2018 by Samuel Weiser.
3472 * Add coordinate blinding for EC_POINT and implement projective
3473 coordinate blinding for generic prime curves as a countermeasure to
3474 chosen point SCA attacks.
3476 *Sohaib ul Hassan, Nicola Tuveri, Billy Bob Brumley*
3478 ### Changes between 1.1.0h and 1.1.0i [14 Aug 2018]
3480 * Client DoS due to large DH parameter
3482 During key agreement in a TLS handshake using a DH(E) based ciphersuite a
3483 malicious server can send a very large prime value to the client. This will
3484 cause the client to spend an unreasonably long period of time generating a
3485 key for this prime resulting in a hang until the client has finished. This
3486 could be exploited in a Denial Of Service attack.
3488 This issue was reported to OpenSSL on 5th June 2018 by Guido Vranken
3493 * Cache timing vulnerability in RSA Key Generation
3495 The OpenSSL RSA Key generation algorithm has been shown to be vulnerable to
3496 a cache timing side channel attack. An attacker with sufficient access to
3497 mount cache timing attacks during the RSA key generation process could
3498 recover the private key.
3500 This issue was reported to OpenSSL on 4th April 2018 by Alejandro Cabrera
3501 Aldaya, Billy Brumley, Cesar Pereida Garcia and Luis Manuel Alvarez Tapia.
3506 * Make EVP_PKEY_asn1_new() a bit stricter about its input. A NULL pem_str
3507 parameter is no longer accepted, as it leads to a corrupt table. NULL
3508 pem_str is reserved for alias entries only.
3512 * Revert blinding in ECDSA sign and instead make problematic addition
3513 length-invariant. Switch even to fixed-length Montgomery multiplication.
3517 * Change generating and checking of primes so that the error rate of not
3518 being prime depends on the intended use based on the size of the input.
3519 For larger primes this will result in more rounds of Miller-Rabin.
3520 The maximal error rate for primes with more than 1080 bits is lowered
3523 *Kurt Roeckx, Annie Yousar*
3525 * Increase the number of Miller-Rabin rounds for DSA key generating to 64.
3529 * Add blinding to ECDSA and DSA signatures to protect against side channel
3530 attacks discovered by Keegan Ryan (NCC Group).
3534 * When unlocking a pass phrase protected PEM file or PKCS#8 container, we
3535 now allow empty (zero character) pass phrases.
3539 * Certificate time validation (X509_cmp_time) enforces stricter
3540 compliance with RFC 5280. Fractional seconds and timezone offsets
3541 are no longer allowed.
3545 * Fixed a text canonicalisation bug in CMS
3547 Where a CMS detached signature is used with text content the text goes
3548 through a canonicalisation process first prior to signing or verifying a
3549 signature. This process strips trailing space at the end of lines, converts
3550 line terminators to CRLF and removes additional trailing line terminators
3551 at the end of a file. A bug in the canonicalisation process meant that
3552 some characters, such as form-feed, were incorrectly treated as whitespace
3553 and removed. This is contrary to the specification (RFC5485). This fix
3554 could mean that detached text data signed with an earlier version of
3555 OpenSSL 1.1.0 may fail to verify using the fixed version, or text data
3556 signed with a fixed OpenSSL may fail to verify with an earlier version of
3557 OpenSSL 1.1.0. A workaround is to only verify the canonicalised text data
3558 and use the "-binary" flag (for the "cms" command line application) or set
3559 the SMIME_BINARY/PKCS7_BINARY/CMS_BINARY flags (if using CMS_verify()).
3563 ### Changes between 1.1.0g and 1.1.0h [27 Mar 2018]
3565 * Constructed ASN.1 types with a recursive definition could exceed the stack
3567 Constructed ASN.1 types with a recursive definition (such as can be found
3568 in PKCS7) could eventually exceed the stack given malicious input with
3569 excessive recursion. This could result in a Denial Of Service attack. There
3570 are no such structures used within SSL/TLS that come from untrusted sources
3571 so this is considered safe.
3573 This issue was reported to OpenSSL on 4th January 2018 by the OSS-fuzz
3579 * Incorrect CRYPTO_memcmp on HP-UX PA-RISC
3581 Because of an implementation bug the PA-RISC CRYPTO_memcmp function is
3582 effectively reduced to only comparing the least significant bit of each
3583 byte. This allows an attacker to forge messages that would be considered as
3584 authenticated in an amount of tries lower than that guaranteed by the
3585 security claims of the scheme. The module can only be compiled by the
3586 HP-UX assembler, so that only HP-UX PA-RISC targets are affected.
3588 This issue was reported to OpenSSL on 2nd March 2018 by Peter Waltenberg
3594 * Add a build target 'build_all_generated', to build all generated files
3595 and only that. This can be used to prepare everything that requires
3596 things like perl for a system that lacks perl and then move everything
3597 to that system and do the rest of the build there.
3601 * Backport SSL_OP_NO_RENGOTIATION
3603 OpenSSL 1.0.2 and below had the ability to disable renegotiation using the
3604 (undocumented) SSL3_FLAGS_NO_RENEGOTIATE_CIPHERS flag. Due to the opacity
3605 changes this is no longer possible in 1.1.0. Therefore, the new
3606 SSL_OP_NO_RENEGOTIATION option from 1.1.1-dev has been backported to
3607 1.1.0 to provide equivalent functionality.
3609 Note that if an application built against 1.1.0h headers (or above) is run
3610 using an older version of 1.1.0 (prior to 1.1.0h) then the option will be
3611 accepted but nothing will happen, i.e. renegotiation will not be prevented.
3615 * Removed the OS390-Unix config target. It relied on a script that doesn't
3620 * rsaz_1024_mul_avx2 overflow bug on x86_64
3622 There is an overflow bug in the AVX2 Montgomery multiplication procedure
3623 used in exponentiation with 1024-bit moduli. No EC algorithms are affected.
3624 Analysis suggests that attacks against RSA and DSA as a result of this
3625 defect would be very difficult to perform and are not believed likely.
3626 Attacks against DH1024 are considered just feasible, because most of the
3627 work necessary to deduce information about a private key may be performed
3628 offline. The amount of resources required for such an attack would be
3629 significant. However, for an attack on TLS to be meaningful, the server
3630 would have to share the DH1024 private key among multiple clients, which is
3631 no longer an option since CVE-2016-0701.
3633 This only affects processors that support the AVX2 but not ADX extensions
3634 like Intel Haswell (4th generation).
3636 This issue was reported to OpenSSL by David Benjamin (Google). The issue
3637 was originally found via the OSS-Fuzz project.
3642 ### Changes between 1.1.0f and 1.1.0g [2 Nov 2017]
3644 * bn_sqrx8x_internal carry bug on x86_64
3646 There is a carry propagating bug in the x86_64 Montgomery squaring
3647 procedure. No EC algorithms are affected. Analysis suggests that attacks
3648 against RSA and DSA as a result of this defect would be very difficult to
3649 perform and are not believed likely. Attacks against DH are considered just
3650 feasible (although very difficult) because most of the work necessary to
3651 deduce information about a private key may be performed offline. The amount
3652 of resources required for such an attack would be very significant and
3653 likely only accessible to a limited number of attackers. An attacker would
3654 additionally need online access to an unpatched system using the target
3655 private key in a scenario with persistent DH parameters and a private
3656 key that is shared between multiple clients.
3658 This only affects processors that support the BMI1, BMI2 and ADX extensions
3659 like Intel Broadwell (5th generation) and later or AMD Ryzen.
3661 This issue was reported to OpenSSL by the OSS-Fuzz project.
3666 * Malformed X.509 IPAddressFamily could cause OOB read
3668 If an X.509 certificate has a malformed IPAddressFamily extension,
3669 OpenSSL could do a one-byte buffer overread. The most likely result
3670 would be an erroneous display of the certificate in text format.
3672 This issue was reported to OpenSSL by the OSS-Fuzz project.
3677 ### Changes between 1.1.0e and 1.1.0f [25 May 2017]
3679 * Have 'config' recognise 64-bit mingw and choose 'mingw64' as the target
3680 platform rather than 'mingw'.
3684 * Remove the VMS-specific reimplementation of gmtime from crypto/o_times.c.
3685 VMS C's RTL has a fully up to date gmtime() and gmtime_r() since V7.1,
3686 which is the minimum version we support.
3690 ### Changes between 1.1.0d and 1.1.0e [16 Feb 2017]
3692 * Encrypt-Then-Mac renegotiation crash
3694 During a renegotiation handshake if the Encrypt-Then-Mac extension is
3695 negotiated where it was not in the original handshake (or vice-versa) then
3696 this can cause OpenSSL to crash (dependent on ciphersuite). Both clients
3697 and servers are affected.
3699 This issue was reported to OpenSSL by Joe Orton (Red Hat).
3704 ### Changes between 1.1.0c and 1.1.0d [26 Jan 2017]
3706 * Truncated packet could crash via OOB read
3708 If one side of an SSL/TLS path is running on a 32-bit host and a specific
3709 cipher is being used, then a truncated packet can cause that host to
3710 perform an out-of-bounds read, usually resulting in a crash.
3712 This issue was reported to OpenSSL by Robert Święcki of Google.
3717 * Bad (EC)DHE parameters cause a client crash
3719 If a malicious server supplies bad parameters for a DHE or ECDHE key
3720 exchange then this can result in the client attempting to dereference a
3721 NULL pointer leading to a client crash. This could be exploited in a Denial
3724 This issue was reported to OpenSSL by Guido Vranken.
3729 * BN_mod_exp may produce incorrect results on x86_64
3731 There is a carry propagating bug in the x86_64 Montgomery squaring
3732 procedure. No EC algorithms are affected. Analysis suggests that attacks
3733 against RSA and DSA as a result of this defect would be very difficult to
3734 perform and are not believed likely. Attacks against DH are considered just
3735 feasible (although very difficult) because most of the work necessary to
3736 deduce information about a private key may be performed offline. The amount
3737 of resources required for such an attack would be very significant and
3738 likely only accessible to a limited number of attackers. An attacker would
3739 additionally need online access to an unpatched system using the target
3740 private key in a scenario with persistent DH parameters and a private
3741 key that is shared between multiple clients. For example this can occur by
3742 default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very
3743 similar to CVE-2015-3193 but must be treated as a separate problem.
3745 This issue was reported to OpenSSL by the OSS-Fuzz project.
3750 ### Changes between 1.1.0b and 1.1.0c [10 Nov 2016]
3752 * ChaCha20/Poly1305 heap-buffer-overflow
3754 TLS connections using `*-CHACHA20-POLY1305` ciphersuites are susceptible to
3755 a DoS attack by corrupting larger payloads. This can result in an OpenSSL
3756 crash. This issue is not considered to be exploitable beyond a DoS.
3758 This issue was reported to OpenSSL by Robert Święcki (Google Security Team)
3763 * CMS Null dereference
3765 Applications parsing invalid CMS structures can crash with a NULL pointer
3766 dereference. This is caused by a bug in the handling of the ASN.1 CHOICE
3767 type in OpenSSL 1.1.0 which can result in a NULL value being passed to the
3768 structure callback if an attempt is made to free certain invalid encodings.
3769 Only CHOICE structures using a callback which do not handle NULL value are
3772 This issue was reported to OpenSSL by Tyler Nighswander of ForAllSecure.
3777 * Montgomery multiplication may produce incorrect results
3779 There is a carry propagating bug in the Broadwell-specific Montgomery
3780 multiplication procedure that handles input lengths divisible by, but
3781 longer than 256 bits. Analysis suggests that attacks against RSA, DSA
3782 and DH private keys are impossible. This is because the subroutine in
3783 question is not used in operations with the private key itself and an input
3784 of the attacker's direct choice. Otherwise the bug can manifest itself as
3785 transient authentication and key negotiation failures or reproducible
3786 erroneous outcome of public-key operations with specially crafted input.
3787 Among EC algorithms only Brainpool P-512 curves are affected and one
3788 presumably can attack ECDH key negotiation. Impact was not analyzed in
3789 detail, because pre-requisites for attack are considered unlikely. Namely
3790 multiple clients have to choose the curve in question and the server has to
3791 share the private key among them, neither of which is default behaviour.
3792 Even then only clients that chose the curve will be affected.
3794 This issue was publicly reported as transient failures and was not
3795 initially recognized as a security issue. Thanks to Richard Morgan for
3796 providing reproducible case.
3801 * Removed automatic addition of RPATH in shared libraries and executables,
3802 as this was a remainder from OpenSSL 1.0.x and isn't needed any more.
3806 ### Changes between 1.1.0a and 1.1.0b [26 Sep 2016]
3808 * Fix Use After Free for large message sizes
3810 The patch applied to address CVE-2016-6307 resulted in an issue where if a
3811 message larger than approx 16k is received then the underlying buffer to
3812 store the incoming message is reallocated and moved. Unfortunately a
3813 dangling pointer to the old location is left which results in an attempt to
3814 write to the previously freed location. This is likely to result in a
3815 crash, however it could potentially lead to execution of arbitrary code.
3817 This issue only affects OpenSSL 1.1.0a.
3819 This issue was reported to OpenSSL by Robert Święcki.
3824 ### Changes between 1.1.0 and 1.1.0a [22 Sep 2016]
3826 * OCSP Status Request extension unbounded memory growth
3828 A malicious client can send an excessively large OCSP Status Request
3829 extension. If that client continually requests renegotiation, sending a
3830 large OCSP Status Request extension each time, then there will be unbounded
3831 memory growth on the server. This will eventually lead to a Denial Of
3832 Service attack through memory exhaustion. Servers with a default
3833 configuration are vulnerable even if they do not support OCSP. Builds using
3834 the "no-ocsp" build time option are not affected.
3836 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
3841 * SSL_peek() hang on empty record
3843 OpenSSL 1.1.0 SSL/TLS will hang during a call to SSL_peek() if the peer
3844 sends an empty record. This could be exploited by a malicious peer in a
3845 Denial Of Service attack.
3847 This issue was reported to OpenSSL by Alex Gaynor.
3852 * Excessive allocation of memory in tls_get_message_header() and
3853 dtls1_preprocess_fragment()
3855 A (D)TLS message includes 3 bytes for its length in the header for the
3856 message. This would allow for messages up to 16Mb in length. Messages of
3857 this length are excessive and OpenSSL includes a check to ensure that a
3858 peer is sending reasonably sized messages in order to avoid too much memory
3859 being consumed to service a connection. A flaw in the logic of version
3860 1.1.0 means that memory for the message is allocated too early, prior to
3861 the excessive message length check. Due to way memory is allocated in
3862 OpenSSL this could mean an attacker could force up to 21Mb to be allocated
3863 to service a connection. This could lead to a Denial of Service through
3864 memory exhaustion. However, the excessive message length check still takes
3865 place, and this would cause the connection to immediately fail. Assuming
3866 that the application calls SSL_free() on the failed connection in a timely
3867 manner then the 21Mb of allocated memory will then be immediately freed
3868 again. Therefore, the excessive memory allocation will be transitory in
3869 nature. This then means that there is only a security impact if:
3871 1) The application does not call SSL_free() in a timely manner in the event
3872 that the connection fails
3874 2) The application is working in a constrained environment where there is
3875 very little free memory
3877 3) The attacker initiates multiple connection attempts such that there are
3878 multiple connections in a state where memory has been allocated for the
3879 connection; SSL_free() has not yet been called; and there is insufficient
3880 memory to service the multiple requests.
3882 Except in the instance of (1) above any Denial Of Service is likely to be
3883 transitory because as soon as the connection fails the memory is
3884 subsequently freed again in the SSL_free() call. However there is an
3885 increased risk during this period of application crashes due to the lack of
3886 memory - which would then mean a more serious Denial of Service.
3888 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
3889 (CVE-2016-6307 and CVE-2016-6308)
3893 * solaris-x86-cc, i.e. 32-bit configuration with vendor compiler,
3894 had to be removed. Primary reason is that vendor assembler can't
3895 assemble our modules with -KPIC flag. As result it, assembly
3896 support, was not even available as option. But its lack means
3897 lack of side-channel resistant code, which is incompatible with
3898 security by todays standards. Fortunately gcc is readily available
3899 prepackaged option, which we firmly point at...
3903 ### Changes between 1.0.2h and 1.1.0 [25 Aug 2016]
3905 * Windows command-line tool supports UTF-8 opt-in option for arguments
3906 and console input. Setting OPENSSL_WIN32_UTF8 environment variable
3907 (to any value) allows Windows user to access PKCS#12 file generated
3908 with Windows CryptoAPI and protected with non-ASCII password, as well
3909 as files generated under UTF-8 locale on Linux also protected with
3914 * To mitigate the SWEET32 attack ([CVE-2016-2183]), 3DES cipher suites
3915 have been disabled by default and removed from DEFAULT, just like RC4.
3916 See the RC4 item below to re-enable both.
3920 * The method for finding the storage location for the Windows RAND seed file
3921 has changed. First we check %RANDFILE%. If that is not set then we check
3922 the directories %HOME%, %USERPROFILE% and %SYSTEMROOT% in that order. If
3923 all else fails we fall back to C:\.
3927 * The EVP_EncryptUpdate() function has had its return type changed from void
3928 to int. A return of 0 indicates and error while a return of 1 indicates
3933 * The flags RSA_FLAG_NO_CONSTTIME, DSA_FLAG_NO_EXP_CONSTTIME and
3934 DH_FLAG_NO_EXP_CONSTTIME which previously provided the ability to switch
3935 off the constant time implementation for RSA, DSA and DH have been made
3936 no-ops and deprecated.
3940 * Windows RAND implementation was simplified to only get entropy by
3941 calling CryptGenRandom(). Various other RAND-related tickets
3944 *Joseph Wylie Yandle, Rich Salz*
3946 * The stack and lhash API's were renamed to start with `OPENSSL_SK_`
3947 and `OPENSSL_LH_`, respectively. The old names are available
3948 with API compatibility. They new names are now completely documented.
3952 * Unify TYPE_up_ref(obj) methods signature.
3953 SSL_CTX_up_ref(), SSL_up_ref(), X509_up_ref(), EVP_PKEY_up_ref(),
3954 X509_CRL_up_ref(), X509_OBJECT_up_ref_count() methods are now returning an
3955 int (instead of void) like all others TYPE_up_ref() methods.
3956 So now these methods also check the return value of CRYPTO_atomic_add(),
3957 and the validity of object reference counter.
3959 *fdasilvayy@gmail.com*
3961 * With Windows Visual Studio builds, the .pdb files are installed
3962 alongside the installed libraries and executables. For a static
3963 library installation, ossl_static.pdb is the associate compiler
3964 generated .pdb file to be used when linking programs.
3968 * Remove openssl.spec. Packaging files belong with the packagers.
3972 * Automatic Darwin/OSX configuration has had a refresh, it will now
3973 recognise x86_64 architectures automatically. You can still decide
3974 to build for a different bitness with the environment variable
3975 KERNEL_BITS (can be 32 or 64), for example:
3977 KERNEL_BITS=32 ./config
3981 * Change default algorithms in pkcs8 utility to use PKCS#5 v2.0,
3982 256 bit AES and HMAC with SHA256.
3986 * Remove support for MIPS o32 ABI on IRIX (and IRIX only).
3990 * Triple-DES ciphers have been moved from HIGH to MEDIUM.
3994 * To enable users to have their own config files and build file templates,
3995 Configure looks in the directory indicated by the environment variable
3996 OPENSSL_LOCAL_CONFIG_DIR as well as the in-source Configurations/
3997 directory. On VMS, OPENSSL_LOCAL_CONFIG_DIR is expected to be a logical
3998 name and is used as is.
4002 * The following datatypes were made opaque: X509_OBJECT, X509_STORE_CTX,
4003 X509_STORE, X509_LOOKUP, and X509_LOOKUP_METHOD. The unused type
4004 X509_CERT_FILE_CTX was removed.
4008 * "shared" builds are now the default. To create only static libraries use
4009 the "no-shared" Configure option.
4013 * Remove the no-aes, no-hmac, no-rsa, no-sha and no-md5 Configure options.
4014 All of these option have not worked for some while and are fundamental
4019 * Make various cleanup routines no-ops and mark them as deprecated. Most
4020 global cleanup functions are no longer required because they are handled
4021 via auto-deinit (see OPENSSL_init_crypto and OPENSSL_init_ssl man pages).
4022 Explicitly de-initing can cause problems (e.g. where a library that uses
4023 OpenSSL de-inits, but an application is still using it). The affected
4024 functions are CONF_modules_free(), ENGINE_cleanup(), OBJ_cleanup(),
4025 EVP_cleanup(), BIO_sock_cleanup(), CRYPTO_cleanup_all_ex_data(),
4026 RAND_cleanup(), SSL_COMP_free_compression_methods(), ERR_free_strings() and
4027 COMP_zlib_cleanup().
4031 * --strict-warnings no longer enables runtime debugging options
4032 such as REF_DEBUG. Instead, debug options are automatically
4033 enabled with '--debug' builds.
4035 *Andy Polyakov, Emilia Käsper*
4037 * Made DH and DH_METHOD opaque. The structures for managing DH objects
4038 have been moved out of the public header files. New functions for managing
4039 these have been added.
4043 * Made RSA and RSA_METHOD opaque. The structures for managing RSA
4044 objects have been moved out of the public header files. New
4045 functions for managing these have been added.
4049 * Made DSA and DSA_METHOD opaque. The structures for managing DSA objects
4050 have been moved out of the public header files. New functions for managing
4051 these have been added.
4055 * Made BIO and BIO_METHOD opaque. The structures for managing BIOs have been
4056 moved out of the public header files. New functions for managing these
4061 * Removed no-rijndael as a config option. Rijndael is an old name for AES.
4065 * Removed the mk1mf build scripts.
4069 * Headers are now wrapped, if necessary, with OPENSSL_NO_xxx, so
4070 it is always safe to #include a header now.
4074 * Removed the aged BC-32 config and all its supporting scripts
4078 * Removed support for Ultrix, Netware, and OS/2.
4082 * Add support for HKDF.
4084 *Alessandro Ghedini*
4086 * Add support for blake2b and blake2s
4090 * Added support for "pipelining". Ciphers that have the
4091 EVP_CIPH_FLAG_PIPELINE flag set have a capability to process multiple
4092 encryptions/decryptions simultaneously. There are currently no built-in
4093 ciphers with this property but the expectation is that engines will be able
4094 to offer it to significantly improve throughput. Support has been extended
4095 into libssl so that multiple records for a single connection can be
4096 processed in one go (for >=TLS 1.1).
4100 * Added the AFALG engine. This is an async capable engine which is able to
4101 offload work to the Linux kernel. In this initial version it only supports
4102 AES128-CBC. The kernel must be version 4.1.0 or greater.
4106 * OpenSSL now uses a new threading API. It is no longer necessary to
4107 set locking callbacks to use OpenSSL in a multi-threaded environment. There
4108 are two supported threading models: pthreads and windows threads. It is
4109 also possible to configure OpenSSL at compile time for "no-threads". The
4110 old threading API should no longer be used. The functions have been
4111 replaced with "no-op" compatibility macros.
4113 *Alessandro Ghedini, Matt Caswell*
4115 * Modify behavior of ALPN to invoke callback after SNI/servername
4116 callback, such that updates to the SSL_CTX affect ALPN.
4120 * Add SSL_CIPHER queries for authentication and key-exchange.
4124 * Changes to the DEFAULT cipherlist:
4125 - Prefer (EC)DHE handshakes over plain RSA.
4126 - Prefer AEAD ciphers over legacy ciphers.
4127 - Prefer ECDSA over RSA when both certificates are available.
4128 - Prefer TLSv1.2 ciphers/PRF.
4129 - Remove DSS, SEED, IDEA, CAMELLIA, and AES-CCM from the
4134 * Change the ECC default curve list to be this, in order: x25519,
4135 secp256r1, secp521r1, secp384r1.
4139 * RC4 based libssl ciphersuites are now classed as "weak" ciphers and are
4140 disabled by default. They can be re-enabled using the
4141 enable-weak-ssl-ciphers option to Configure.
4145 * If the server has ALPN configured, but supports no protocols that the
4146 client advertises, send a fatal "no_application_protocol" alert.
4147 This behaviour is SHALL in RFC 7301, though it isn't universally
4148 implemented by other servers.
4152 * Add X25519 support.
4153 Add ASN.1 and EVP_PKEY methods for X25519. This includes support
4154 for public and private key encoding using the format documented in
4155 draft-ietf-curdle-pkix-02. The corresponding EVP_PKEY method supports
4156 key generation and key derivation.
4158 TLS support complies with draft-ietf-tls-rfc4492bis-08 and uses
4163 * Deprecate SRP_VBASE_get_by_user.
4164 SRP_VBASE_get_by_user had inconsistent memory management behaviour.
4165 In order to fix an unavoidable memory leak ([CVE-2016-0798]),
4166 SRP_VBASE_get_by_user was changed to ignore the "fake user" SRP
4167 seed, even if the seed is configured.
4169 Users should use SRP_VBASE_get1_by_user instead. Note that in
4170 SRP_VBASE_get1_by_user, caller must free the returned value. Note
4171 also that even though configuring the SRP seed attempts to hide
4172 invalid usernames by continuing the handshake with fake
4173 credentials, this behaviour is not constant time and no strong
4174 guarantees are made that the handshake is indistinguishable from
4175 that of a valid user.
4179 * Configuration change; it's now possible to build dynamic engines
4180 without having to build shared libraries and vice versa. This
4181 only applies to the engines in `engines/`, those in `crypto/engine/`
4182 will always be built into libcrypto (i.e. "static").
4184 Building dynamic engines is enabled by default; to disable, use
4185 the configuration option "disable-dynamic-engine".
4187 The only requirements for building dynamic engines are the
4188 presence of the DSO module and building with position independent
4189 code, so they will also automatically be disabled if configuring
4190 with "disable-dso" or "disable-pic".
4192 The macros OPENSSL_NO_STATIC_ENGINE and OPENSSL_NO_DYNAMIC_ENGINE
4193 are also taken away from openssl/opensslconf.h, as they are
4198 * Configuration change; if there is a known flag to compile
4199 position independent code, it will always be applied on the
4200 libcrypto and libssl object files, and never on the application
4201 object files. This means other libraries that use routines from
4202 libcrypto / libssl can be made into shared libraries regardless
4203 of how OpenSSL was configured.
4205 If this isn't desirable, the configuration options "disable-pic"
4206 or "no-pic" can be used to disable the use of PIC. This will
4207 also disable building shared libraries and dynamic engines.
4211 * Removed JPAKE code. It was experimental and has no wide use.
4215 * The INSTALL_PREFIX Makefile variable has been renamed to
4216 DESTDIR. That makes for less confusion on what this variable
4217 is for. Also, the configuration option --install_prefix is
4222 * Heartbeat for TLS has been removed and is disabled by default
4223 for DTLS; configure with enable-heartbeats. Code that uses the
4224 old #define's might need to be updated.
4226 *Emilia Käsper, Rich Salz*
4228 * Rename REF_CHECK to REF_DEBUG.
4232 * New "unified" build system
4234 The "unified" build system is aimed to be a common system for all
4235 platforms we support. With it comes new support for VMS.
4237 This system builds supports building in a different directory tree
4238 than the source tree. It produces one Makefile (for unix family
4239 or lookalikes), or one descrip.mms (for VMS).
4241 The source of information to make the Makefile / descrip.mms is
4242 small files called 'build.info', holding the necessary
4243 information for each directory with source to compile, and a
4244 template in Configurations, like unix-Makefile.tmpl or
4247 With this change, the library names were also renamed on Windows
4248 and on VMS. They now have names that are closer to the standard
4249 on Unix, and include the major version number, and in certain
4250 cases, the architecture they are built for. See "Notes on shared
4251 libraries" in INSTALL.
4253 We rely heavily on the perl module Text::Template.
4257 * Added support for auto-initialisation and de-initialisation of the library.
4258 OpenSSL no longer requires explicit init or deinit routines to be called,
4259 except in certain circumstances. See the OPENSSL_init_crypto() and
4260 OPENSSL_init_ssl() man pages for further information.
4264 * The arguments to the DTLSv1_listen function have changed. Specifically the
4265 "peer" argument is now expected to be a BIO_ADDR object.
4267 * Rewrite of BIO networking library. The BIO library lacked consistent
4268 support of IPv6, and adding it required some more extensive
4269 modifications. This introduces the BIO_ADDR and BIO_ADDRINFO types,
4270 which hold all types of addresses and chains of address information.
4271 It also introduces a new API, with functions like BIO_socket,
4272 BIO_connect, BIO_listen, BIO_lookup and a rewrite of BIO_accept.
4273 The source/sink BIOs BIO_s_connect, BIO_s_accept and BIO_s_datagram
4274 have been adapted accordingly.
4278 * RSA_padding_check_PKCS1_type_1 now accepts inputs with and without
4283 * CRIME protection: disable compression by default, even if OpenSSL is
4284 compiled with zlib enabled. Applications can still enable compression
4285 by calling SSL_CTX_clear_options(ctx, SSL_OP_NO_COMPRESSION), or by
4286 using the SSL_CONF library to configure compression.
4290 * The signature of the session callback configured with
4291 SSL_CTX_sess_set_get_cb was changed. The read-only input buffer
4292 was explicitly marked as `const unsigned char*` instead of
4297 * Always DPURIFY. Remove the use of uninitialized memory in the
4298 RNG, and other conditional uses of DPURIFY. This makes -DPURIFY a no-op.
4302 * Removed many obsolete configuration items, including
4303 DES_PTR, DES_RISC1, DES_RISC2, DES_INT
4304 MD2_CHAR, MD2_INT, MD2_LONG
4306 IDEA_SHORT, IDEA_LONG
4307 RC2_SHORT, RC2_LONG, RC4_LONG, RC4_CHUNK, RC4_INDEX
4309 *Rich Salz, with advice from Andy Polyakov*
4311 * Many BN internals have been moved to an internal header file.
4313 *Rich Salz with help from Andy Polyakov*
4315 * Configuration and writing out the results from it has changed.
4316 Files such as Makefile include/openssl/opensslconf.h and are now
4317 produced through general templates, such as Makefile.in and
4318 crypto/opensslconf.h.in and some help from the perl module
4321 Also, the center of configuration information is no longer
4322 Makefile. Instead, Configure produces a perl module in
4323 configdata.pm which holds most of the config data (in the hash
4324 table %config), the target data that comes from the target
4325 configuration in one of the `Configurations/*.conf` files (in
4330 * To clarify their intended purposes, the Configure options
4331 --prefix and --openssldir change their semantics, and become more
4332 straightforward and less interdependent.
4334 --prefix shall be used exclusively to give the location INSTALLTOP
4335 where programs, scripts, libraries, include files and manuals are
4336 going to be installed. The default is now /usr/local.
4338 --openssldir shall be used exclusively to give the default
4339 location OPENSSLDIR where certificates, private keys, CRLs are
4340 managed. This is also where the default openssl.cnf gets
4342 If the directory given with this option is a relative path, the
4343 values of both the --prefix value and the --openssldir value will
4344 be combined to become OPENSSLDIR.
4345 The default for --openssldir is INSTALLTOP/ssl.
4347 Anyone who uses --openssldir to specify where OpenSSL is to be
4348 installed MUST change to use --prefix instead.
4352 * The GOST engine was out of date and therefore it has been removed. An up
4353 to date GOST engine is now being maintained in an external repository.
4354 See: <https://wiki.openssl.org/index.php/Binaries>. Libssl still retains
4355 support for GOST ciphersuites (these are only activated if a GOST engine
4360 * EGD is no longer supported by default; use enable-egd when
4363 *Ben Kaduk and Rich Salz*
4365 * The distribution now has Makefile.in files, which are used to
4366 create Makefile's when Configure is run. *Configure must be run
4367 before trying to build now.*
4371 * The return value for SSL_CIPHER_description() for error conditions
4376 * Support for RFC6698/RFC7671 DANE TLSA peer authentication.
4378 Obtaining and performing DNSSEC validation of TLSA records is
4379 the application's responsibility. The application provides
4380 the TLSA records of its choice to OpenSSL, and these are then
4381 used to authenticate the peer.
4383 The TLSA records need not even come from DNS. They can, for
4384 example, be used to implement local end-entity certificate or
4385 trust-anchor "pinning", where the "pin" data takes the form
4386 of TLSA records, which can augment or replace verification
4387 based on the usual WebPKI public certification authorities.
4391 * Revert default OPENSSL_NO_DEPRECATED setting. Instead OpenSSL
4392 continues to support deprecated interfaces in default builds.
4393 However, applications are strongly advised to compile their
4394 source files with -DOPENSSL_API_COMPAT=0x10100000L, which hides
4395 the declarations of all interfaces deprecated in 0.9.8, 1.0.0
4396 or the 1.1.0 releases.
4398 In environments in which all applications have been ported to
4399 not use any deprecated interfaces OpenSSL's Configure script
4400 should be used with the --api=1.1.0 option to entirely remove
4401 support for the deprecated features from the library and
4402 unconditionally disable them in the installed headers.
4403 Essentially the same effect can be achieved with the "no-deprecated"
4404 argument to Configure, except that this will always restrict
4405 the build to just the latest API, rather than a fixed API
4408 As applications are ported to future revisions of the API,
4409 they should update their compile-time OPENSSL_API_COMPAT define
4410 accordingly, but in most cases should be able to continue to
4411 compile with later releases.
4413 The OPENSSL_API_COMPAT versions for 1.0.0, and 0.9.8 are
4414 0x10000000L and 0x00908000L, respectively. However those
4415 versions did not support the OPENSSL_API_COMPAT feature, and
4416 so applications are not typically tested for explicit support
4417 of just the undeprecated features of either release.
4421 * Add support for setting the minimum and maximum supported protocol.
4422 It can bet set via the SSL_set_min_proto_version() and
4423 SSL_set_max_proto_version(), or via the SSL_CONF's MinProtocol and
4424 MaxProtocol. It's recommended to use the new APIs to disable
4425 protocols instead of disabling individual protocols using
4426 SSL_set_options() or SSL_CONF's Protocol. This change also
4427 removes support for disabling TLS 1.2 in the OpenSSL TLS
4428 client at compile time by defining OPENSSL_NO_TLS1_2_CLIENT.
4432 * Support for ChaCha20 and Poly1305 added to libcrypto and libssl.
4436 * New EC_KEY_METHOD, this replaces the older ECDSA_METHOD and ECDH_METHOD
4437 and integrates ECDSA and ECDH functionality into EC. Implementations can
4438 now redirect key generation and no longer need to convert to or from
4441 Note: the ecdsa.h and ecdh.h headers are now no longer needed and just
4442 include the ec.h header file instead.
4446 * Remove support for all 40 and 56 bit ciphers. This includes all the export
4447 ciphers who are no longer supported and drops support the ephemeral RSA key
4448 exchange. The LOW ciphers currently doesn't have any ciphers in it.
4452 * Made EVP_MD_CTX, EVP_MD, EVP_CIPHER_CTX, EVP_CIPHER and HMAC_CTX
4453 opaque. For HMAC_CTX, the following constructors and destructors
4456 HMAC_CTX *HMAC_CTX_new(void);
4457 void HMAC_CTX_free(HMAC_CTX *ctx);
4459 For EVP_MD and EVP_CIPHER, complete APIs to create, fill and
4460 destroy such methods has been added. See EVP_MD_meth_new(3) and
4461 EVP_CIPHER_meth_new(3) for documentation.
4464 1) `EVP_MD_CTX_cleanup()`, `EVP_CIPHER_CTX_cleanup()` and
4465 `HMAC_CTX_cleanup()` were removed. `HMAC_CTX_reset()` and
4466 `EVP_MD_CTX_reset()` should be called instead to reinitialise
4467 an already created structure.
4468 2) For consistency with the majority of our object creators and
4469 destructors, `EVP_MD_CTX_(create|destroy)` were renamed to
4470 `EVP_MD_CTX_(new|free)`. The old names are retained as macros
4471 for deprecated builds.
4475 * Added ASYNC support. Libcrypto now includes the async sub-library to enable
4476 cryptographic operations to be performed asynchronously as long as an
4477 asynchronous capable engine is used. See the ASYNC_start_job() man page for
4478 further details. Libssl has also had this capability integrated with the
4479 introduction of the new mode SSL_MODE_ASYNC and associated error
4480 SSL_ERROR_WANT_ASYNC. See the SSL_CTX_set_mode() and SSL_get_error() man
4481 pages. This work was developed in partnership with Intel Corp.
4485 * SSL_{CTX_}set_ecdh_auto() has been removed and ECDH is support is
4486 always enabled now. If you want to disable the support you should
4487 exclude it using the list of supported ciphers. This also means that the
4488 "-no_ecdhe" option has been removed from s_server.
4492 * SSL_{CTX}_set_tmp_ecdh() which can set 1 EC curve now internally calls
4493 SSL_{CTX_}set1_curves() which can set a list.
4497 * Remove support for SSL_{CTX_}set_tmp_ecdh_callback(). You should set the
4498 curve you want to support using SSL_{CTX_}set1_curves().
4502 * State machine rewrite. The state machine code has been significantly
4503 refactored in order to remove much duplication of code and solve issues
4504 with the old code (see [ssl/statem/README.md](ssl/statem/README.md) for
4505 further details). This change does have some associated API changes.
4506 Notably the SSL_state() function has been removed and replaced by
4507 SSL_get_state which now returns an "OSSL_HANDSHAKE_STATE" instead of an int.
4508 SSL_set_state() has been removed altogether. The previous handshake states
4509 defined in ssl.h and ssl3.h have also been removed.
4513 * All instances of the string "ssleay" in the public API were replaced
4514 with OpenSSL (case-matching; e.g., OPENSSL_VERSION for #define's)
4515 Some error codes related to internal RSA_eay API's were renamed.
4519 * The demo files in crypto/threads were moved to demo/threads.
4523 * Removed obsolete engines: 4758cca, aep, atalla, cswift, nuron, gmp,
4526 *Matt Caswell, Rich Salz*
4528 * New ASN.1 embed macro.
4530 New ASN.1 macro ASN1_EMBED. This is the same as ASN1_SIMPLE except the
4531 structure is not allocated: it is part of the parent. That is instead of
4539 This reduces memory fragmentation and make it impossible to accidentally
4540 set a mandatory field to NULL.
4542 This currently only works for some fields specifically a SEQUENCE, CHOICE,
4543 or ASN1_STRING type which is part of a parent SEQUENCE. Since it is
4544 equivalent to ASN1_SIMPLE it cannot be tagged, OPTIONAL, SET OF or
4549 * Remove EVP_CHECK_DES_KEY, a compile-time option that never compiled.
4553 * Removed DES and RC4 ciphersuites from DEFAULT. Also removed RC2 although
4554 in 1.0.2 EXPORT was already removed and the only RC2 ciphersuite is also
4555 an EXPORT one. COMPLEMENTOFDEFAULT has been updated accordingly to add
4556 DES and RC4 ciphersuites.
4560 * Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs.
4561 This changes the decoding behaviour for some invalid messages,
4562 though the change is mostly in the more lenient direction, and
4563 legacy behaviour is preserved as much as possible.
4567 * Fix no-stdio build.
4568 *David Woodhouse <David.Woodhouse@intel.com> and also*
4569 *Ivan Nestlerode <ivan.nestlerode@sonos.com>*
4571 * New testing framework
4572 The testing framework has been largely rewritten and is now using
4573 perl and the perl modules Test::Harness and an extended variant of
4574 Test::More called OpenSSL::Test to do its work. All test scripts in
4575 test/ have been rewritten into test recipes, and all direct calls to
4576 executables in test/Makefile have become individual recipes using the
4577 simplified testing OpenSSL::Test::Simple.
4579 For documentation on our testing modules, do:
4581 perldoc test/testlib/OpenSSL/Test/Simple.pm
4582 perldoc test/testlib/OpenSSL/Test.pm
4586 * Revamped memory debug; only -DCRYPTO_MDEBUG and -DCRYPTO_MDEBUG_ABORT
4587 are used; the latter aborts on memory leaks (usually checked on exit).
4588 Some undocumented "set malloc, etc., hooks" functions were removed
4589 and others were changed. All are now documented.
4593 * In DSA_generate_parameters_ex, if the provided seed is too short,
4596 *Rich Salz and Ismo Puustinen <ismo.puustinen@intel.com>*
4598 * Rewrite PSK to support ECDHE_PSK, DHE_PSK and RSA_PSK. Add ciphersuites
4599 from RFC4279, RFC4785, RFC5487, RFC5489.
4601 Thanks to Christian J. Dietrich and Giuseppe D'Angelo for the
4602 original RSA_PSK patch.
4606 * Dropped support for the SSL3_FLAGS_DELAY_CLIENT_FINISHED flag. This SSLeay
4607 era flag was never set throughout the codebase (only read). Also removed
4608 SSL3_FLAGS_POP_BUFFER which was only used if
4609 SSL3_FLAGS_DELAY_CLIENT_FINISHED was also set.
4613 * Changed the default name options in the "ca", "crl", "req" and "x509"
4614 to be "oneline" instead of "compat".
4618 * Remove SSL_OP_TLS_BLOCK_PADDING_BUG. This is SSLeay legacy, we're
4619 not aware of clients that still exhibit this bug, and the workaround
4620 hasn't been working properly for a while.
4624 * The return type of BIO_number_read() and BIO_number_written() as well as
4625 the corresponding num_read and num_write members in the BIO structure has
4626 changed from unsigned long to uint64_t. On platforms where an unsigned
4627 long is 32 bits (e.g. Windows) these counters could overflow if >4Gb is
4632 * Given the pervasive nature of TLS extensions it is inadvisable to run
4633 OpenSSL without support for them. It also means that maintaining
4634 the OPENSSL_NO_TLSEXT option within the code is very invasive (and probably
4635 not well tested). Therefore, the OPENSSL_NO_TLSEXT option has been removed.
4639 * Removed support for the two export grade static DH ciphersuites
4640 EXP-DH-RSA-DES-CBC-SHA and EXP-DH-DSS-DES-CBC-SHA. These two ciphersuites
4641 were newly added (along with a number of other static DH ciphersuites) to
4642 1.0.2. However the two export ones have *never* worked since they were
4643 introduced. It seems strange in any case to be adding new export
4644 ciphersuites, and given "logjam" it also does not seem correct to fix them.
4648 * Version negotiation has been rewritten. In particular SSLv23_method(),
4649 SSLv23_client_method() and SSLv23_server_method() have been deprecated,
4650 and turned into macros which simply call the new preferred function names
4651 TLS_method(), TLS_client_method() and TLS_server_method(). All new code
4652 should use the new names instead. Also as part of this change the ssl23.h
4653 header file has been removed.
4657 * Support for Kerberos ciphersuites in TLS (RFC2712) has been removed. This
4658 code and the associated standard is no longer considered fit-for-purpose.
4662 * RT2547 was closed. When generating a private key, try to make the
4663 output file readable only by the owner. This behavior change might
4664 be noticeable when interacting with other software.
4666 * Documented all exdata functions. Added CRYPTO_free_ex_index.
4671 * Added HTTP GET support to the ocsp command.
4675 * Changed default digest for the dgst and enc commands from MD5 to
4680 * RAND_pseudo_bytes has been deprecated. Users should use RAND_bytes instead.
4684 * Added support for TLS extended master secret from
4685 draft-ietf-tls-session-hash-03.txt. Thanks for Alfredo Pironti for an
4686 initial patch which was a great help during development.
4690 * All libssl internal structures have been removed from the public header
4691 files, and the OPENSSL_NO_SSL_INTERN option has been removed (since it is
4692 now redundant). Users should not attempt to access internal structures
4693 directly. Instead they should use the provided API functions.
4697 * config has been changed so that by default OPENSSL_NO_DEPRECATED is used.
4698 Access to deprecated functions can be re-enabled by running config with
4699 "enable-deprecated". In addition applications wishing to use deprecated
4700 functions must define OPENSSL_USE_DEPRECATED. Note that this new behaviour
4701 will, by default, disable some transitive includes that previously existed
4702 in the header files (e.g. ec.h will no longer, by default, include bn.h)
4706 * Added support for OCB mode. OpenSSL has been granted a patent license
4707 compatible with the OpenSSL license for use of OCB. Details are available
4708 at <https://www.openssl.org/source/OCB-patent-grant-OpenSSL.pdf>. Support
4709 for OCB can be removed by calling config with no-ocb.
4713 * SSLv2 support has been removed. It still supports receiving an SSLv2
4714 compatible client hello.
4718 * Increased the minimal RSA keysize from 256 to 512 bits [Rich Salz],
4719 done while fixing the error code for the key-too-small case.
4721 *Annie Yousar <a.yousar@informatik.hu-berlin.de>*
4723 * CA.sh has been removed; use CA.pl instead.
4727 * Removed old DES API.
4731 * Remove various unsupported platforms:
4737 Sinix/ReliantUNIX RM400
4742 16-bit platforms such as WIN16
4746 * Clean up OPENSSL_NO_xxx #define's
4747 - Use setbuf() and remove OPENSSL_NO_SETVBUF_IONBF
4748 - Rename OPENSSL_SYSNAME_xxx to OPENSSL_SYS_xxx
4749 - OPENSSL_NO_EC{DH,DSA} merged into OPENSSL_NO_EC
4750 - OPENSSL_NO_RIPEMD160, OPENSSL_NO_RIPEMD merged into OPENSSL_NO_RMD160
4751 - OPENSSL_NO_FP_API merged into OPENSSL_NO_STDIO
4752 - Remove OPENSSL_NO_BIO OPENSSL_NO_BUFFER OPENSSL_NO_CHAIN_VERIFY
4753 OPENSSL_NO_EVP OPENSSL_NO_FIPS_ERR OPENSSL_NO_HASH_COMP
4754 OPENSSL_NO_LHASH OPENSSL_NO_OBJECT OPENSSL_NO_SPEED OPENSSL_NO_STACK
4755 OPENSSL_NO_X509 OPENSSL_NO_X509_VERIFY
4756 - Remove MS_STATIC; it's a relic from platforms <32 bits.
4760 * Cleaned up dead code
4761 Remove all but one '#ifdef undef' which is to be looked at.
4765 * Clean up calling of xxx_free routines.
4766 Just like free(), fix most of the xxx_free routines to accept
4767 NULL. Remove the non-null checks from callers. Save much code.
4771 * Add secure heap for storage of private keys (when possible).
4772 Add BIO_s_secmem(), CBIGNUM, etc.
4773 Contributed by Akamai Technologies under our Corporate CLA.
4777 * Experimental support for a new, fast, unbiased prime candidate generator,
4778 bn_probable_prime_dh_coprime(). Not currently used by any prime generator.
4780 *Felix Laurie von Massenbach <felix@erbridge.co.uk>*
4782 * New output format NSS in the sess_id command line tool. This allows
4783 exporting the session id and the master key in NSS keylog format.
4785 *Martin Kaiser <martin@kaiser.cx>*
4787 * Harmonize version and its documentation. -f flag is used to display
4790 *mancha <mancha1@zoho.com>*
4792 * Fix eckey_priv_encode so it immediately returns an error upon a failure
4793 in i2d_ECPrivateKey. Thanks to Ted Unangst for feedback on this issue.
4795 *mancha <mancha1@zoho.com>*
4797 * Fix some double frees. These are not thought to be exploitable.
4799 *mancha <mancha1@zoho.com>*
4801 * A missing bounds check in the handling of the TLS heartbeat extension
4802 can be used to reveal up to 64k of memory to a connected client or
4805 Thanks for Neel Mehta of Google Security for discovering this bug and to
4806 Adam Langley <agl@chromium.org> and Bodo Moeller <bmoeller@acm.org> for
4807 preparing the fix ([CVE-2014-0160])
4809 *Adam Langley, Bodo Moeller*
4811 * Fix for the attack described in the paper "Recovering OpenSSL
4812 ECDSA Nonces Using the FLUSH+RELOAD Cache Side-channel Attack"
4813 by Yuval Yarom and Naomi Benger. Details can be obtained from:
4814 <http://eprint.iacr.org/2014/140>
4816 Thanks to Yuval Yarom and Naomi Benger for discovering this
4817 flaw and to Yuval Yarom for supplying a fix ([CVE-2014-0076])
4819 *Yuval Yarom and Naomi Benger*
4821 * Use algorithm specific chains in SSL_CTX_use_certificate_chain_file():
4822 this fixes a limitation in previous versions of OpenSSL.
4826 * Experimental encrypt-then-mac support.
4828 Experimental support for encrypt then mac from
4829 draft-gutmann-tls-encrypt-then-mac-02.txt
4831 To enable it set the appropriate extension number (0x42 for the test
4832 server) using e.g. -DTLSEXT_TYPE_encrypt_then_mac=0x42
4834 For non-compliant peers (i.e. just about everything) this should have no
4837 WARNING: EXPERIMENTAL, SUBJECT TO CHANGE.
4841 * Add EVP support for key wrapping algorithms, to avoid problems with
4842 existing code the flag EVP_CIPHER_CTX_WRAP_ALLOW has to be set in
4843 the EVP_CIPHER_CTX or an error is returned. Add AES and DES3 wrap
4844 algorithms and include tests cases.
4848 * Extend CMS code to support RSA-PSS signatures and RSA-OAEP for
4853 * Extended RSA OAEP support via EVP_PKEY API. Options to specify digest,
4854 MGF1 digest and OAEP label.
4858 * Make openssl verify return errors.
4860 *Chris Palmer <palmer@google.com> and Ben Laurie*
4862 * New function ASN1_TIME_diff to calculate the difference between two
4863 ASN1_TIME structures or one structure and the current time.
4867 * Update fips_test_suite to support multiple command line options. New
4868 test to induce all self test errors in sequence and check expected
4873 * Add FIPS_{rsa,dsa,ecdsa}_{sign,verify} functions which digest and
4874 sign or verify all in one operation.
4878 * Add fips_algvs: a multicall fips utility incorporating all the algorithm
4879 test programs and fips_test_suite. Includes functionality to parse
4880 the minimal script output of fipsalgest.pl directly.
4884 * Add authorisation parameter to FIPS_module_mode_set().
4888 * Add FIPS selftest for ECDH algorithm using P-224 and B-233 curves.
4892 * Use separate DRBG fields for internal and external flags. New function
4893 FIPS_drbg_health_check() to perform on demand health checking. Add
4894 generation tests to fips_test_suite with reduced health check interval to
4895 demonstrate periodic health checking. Add "nodh" option to
4896 fips_test_suite to skip very slow DH test.
4900 * New function FIPS_get_cipherbynid() to lookup FIPS supported ciphers
4905 * More extensive health check for DRBG checking many more failure modes.
4906 New function FIPS_selftest_drbg_all() to handle every possible DRBG
4907 combination: call this in fips_test_suite.
4911 * Add support for canonical generation of DSA parameter 'g'. See
4914 * Add support for HMAC DRBG from SP800-90. Update DRBG algorithm test and
4915 POST to handle HMAC cases.
4919 * Add functions FIPS_module_version() and FIPS_module_version_text()
4920 to return numerical and string versions of the FIPS module number.
4924 * Rename FIPS_mode_set and FIPS_mode to FIPS_module_mode_set and
4925 FIPS_module_mode. FIPS_mode and FIPS_mode_set will be implemented
4926 outside the validated module in the FIPS capable OpenSSL.
4930 * Minor change to DRBG entropy callback semantics. In some cases
4931 there is no multiple of the block length between min_len and
4932 max_len. Allow the callback to return more than max_len bytes
4933 of entropy but discard any extra: it is the callback's responsibility
4934 to ensure that the extra data discarded does not impact the
4935 requested amount of entropy.
4939 * Add PRNG security strength checks to RSA, DSA and ECDSA using
4940 information in FIPS186-3, SP800-57 and SP800-131A.
4944 * CCM support via EVP. Interface is very similar to GCM case except we
4945 must supply all data in one chunk (i.e. no update, final) and the
4946 message length must be supplied if AAD is used. Add algorithm test
4951 * Initial version of POST overhaul. Add POST callback to allow the status
4952 of POST to be monitored and/or failures induced. Modify fips_test_suite
4953 to use callback. Always run all selftests even if one fails.
4957 * XTS support including algorithm test driver in the fips_gcmtest program.
4958 Note: this does increase the maximum key length from 32 to 64 bytes but
4959 there should be no binary compatibility issues as existing applications
4960 will never use XTS mode.
4964 * Extensive reorganisation of FIPS PRNG behaviour. Remove all dependencies
4965 to OpenSSL RAND code and replace with a tiny FIPS RAND API which also
4966 performs algorithm blocking for unapproved PRNG types. Also do not
4967 set PRNG type in FIPS_mode_set(): leave this to the application.
4968 Add default OpenSSL DRBG handling: sets up FIPS PRNG and seeds with
4969 the standard OpenSSL PRNG: set additional data to a date time vector.
4973 * Rename old X9.31 PRNG functions of the form `FIPS_rand*` to `FIPS_x931*`.
4974 This shouldn't present any incompatibility problems because applications
4975 shouldn't be using these directly and any that are will need to rethink
4976 anyway as the X9.31 PRNG is now deprecated by FIPS 140-2
4980 * Extensive self tests and health checking required by SP800-90 DRBG.
4981 Remove strength parameter from FIPS_drbg_instantiate and always
4982 instantiate at maximum supported strength.
4986 * Add ECDH code to fips module and fips_ecdhvs for primitives only testing.
4990 * New algorithm test program fips_dhvs to handle DH primitives only testing.
4994 * New function DH_compute_key_padded() to compute a DH key and pad with
4995 leading zeroes if needed: this complies with SP800-56A et al.
4999 * Initial implementation of SP800-90 DRBGs for Hash and CTR. Not used by
5000 anything, incomplete, subject to change and largely untested at present.
5004 * Modify fipscanisteronly build option to only build the necessary object
5005 files by filtering FIPS_EX_OBJ through a perl script in crypto/Makefile.
5009 * Add experimental option FIPSSYMS to give all symbols in
5010 fipscanister.o and FIPS or fips prefix. This will avoid
5011 conflicts with future versions of OpenSSL. Add perl script
5012 util/fipsas.pl to preprocess assembly language source files
5013 and rename any affected symbols.
5017 * Add selftest checks and algorithm block of non-fips algorithms in
5018 FIPS mode. Remove DES2 from selftests.
5022 * Add ECDSA code to fips module. Add tiny fips_ecdsa_check to just
5023 return internal method without any ENGINE dependencies. Add new
5024 tiny fips sign and verify functions.
5028 * New build option no-ec2m to disable characteristic 2 code.
5032 * New build option "fipscanisteronly". This only builds fipscanister.o
5033 and (currently) associated fips utilities. Uses the file Makefile.fips
5034 instead of Makefile.org as the prototype.
5038 * Add some FIPS mode restrictions to GCM. Add internal IV generator.
5039 Update fips_gcmtest to use IV generator.
5043 * Initial, experimental EVP support for AES-GCM. AAD can be input by
5044 setting output buffer to NULL. The `*Final` function must be
5045 called although it will not retrieve any additional data. The tag
5046 can be set or retrieved with a ctrl. The IV length is by default 12
5047 bytes (96 bits) but can be set to an alternative value. If the IV
5048 length exceeds the maximum IV length (currently 16 bytes) it cannot be
5053 * New flag in ciphers: EVP_CIPH_FLAG_CUSTOM_CIPHER. This means the
5054 underlying do_cipher function handles all cipher semantics itself
5055 including padding and finalisation. This is useful if (for example)
5056 an ENGINE cipher handles block padding itself. The behaviour of
5057 do_cipher is subtly changed if this flag is set: the return value
5058 is the number of characters written to the output buffer (zero is
5059 no longer an error code) or a negative error code. Also if the
5060 input buffer is NULL and length 0 finalisation should be performed.
5064 * If a candidate issuer certificate is already part of the constructed
5065 path ignore it: new debug notification X509_V_ERR_PATH_LOOP for this case.
5069 * Improve forward-security support: add functions
5071 void SSL_CTX_set_not_resumable_session_callback(
5072 SSL_CTX *ctx, int (*cb)(SSL *ssl, int is_forward_secure))
5073 void SSL_set_not_resumable_session_callback(
5074 SSL *ssl, int (*cb)(SSL *ssl, int is_forward_secure))
5076 for use by SSL/TLS servers; the callback function will be called whenever a
5077 new session is created, and gets to decide whether the session may be
5078 cached to make it resumable (return 0) or not (return 1). (As by the
5079 SSL/TLS protocol specifications, the session_id sent by the server will be
5080 empty to indicate that the session is not resumable; also, the server will
5081 not generate RFC 4507 (RFC 5077) session tickets.)
5083 A simple reasonable callback implementation is to return is_forward_secure.
5084 This parameter will be set to 1 or 0 depending on the ciphersuite selected
5085 by the SSL/TLS server library, indicating whether it can provide forward
5088 *Emilia Käsper <emilia.kasper@esat.kuleuven.be> (Google)*
5090 * New -verify_name option in command line utilities to set verification
5095 * Initial CMAC implementation. WARNING: EXPERIMENTAL, API MAY CHANGE.
5096 Add CMAC pkey methods.
5100 * Experimental renegotiation in s_server -www mode. If the client
5101 browses /reneg connection is renegotiated. If /renegcert it is
5102 renegotiated requesting a certificate.
5106 * Add an "external" session cache for debugging purposes to s_server. This
5107 should help trace issues which normally are only apparent in deployed
5108 multi-process servers.
5112 * Extensive audit of libcrypto with DEBUG_UNUSED. Fix many cases where
5113 return value is ignored. NB. The functions RAND_add(), RAND_seed(),
5114 BIO_set_cipher() and some obscure PEM functions were changed so they
5115 can now return an error. The RAND changes required a change to the
5116 RAND_METHOD structure.
5120 * New macro `__owur` for "OpenSSL Warn Unused Result". This makes use of
5121 a gcc attribute to warn if the result of a function is ignored. This
5122 is enable if DEBUG_UNUSED is set. Add to several functions in evp.h
5123 whose return value is often ignored.
5127 * New -noct, -requestct, -requirect and -ctlogfile options for s_client.
5128 These allow SCTs (signed certificate timestamps) to be requested and
5129 validated when establishing a connection.
5131 *Rob Percival <robpercival@google.com>*
5136 ### Changes between 1.0.2s and 1.0.2t [10 Sep 2019]
5138 * For built-in EC curves, ensure an EC_GROUP built from the curve name is
5139 used even when parsing explicit parameters, when loading a encoded key
5140 or calling `EC_GROUP_new_from_ecpkparameters()`/
5141 `EC_GROUP_new_from_ecparameters()`.
5142 This prevents bypass of security hardening and performance gains,
5143 especially for curves with specialized EC_METHODs.
5144 By default, if a key encoded with explicit parameters is loaded and later
5145 encoded, the output is still encoded with explicit parameters, even if
5146 internally a "named" EC_GROUP is used for computation.
5150 * Compute ECC cofactors if not provided during EC_GROUP construction. Before
5151 this change, EC_GROUP_set_generator would accept order and/or cofactor as
5152 NULL. After this change, only the cofactor parameter can be NULL. It also
5153 does some minimal sanity checks on the passed order.
5158 * Fixed a padding oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey.
5159 An attack is simple, if the first CMS_recipientInfo is valid but the
5160 second CMS_recipientInfo is chosen ciphertext. If the second
5161 recipientInfo decodes to PKCS #1 v1.5 form plaintext, the correct
5162 encryption key will be replaced by garbage, and the message cannot be
5163 decoded, but if the RSA decryption fails, the correct encryption key is
5164 used and the recipient will not notice the attack.
5165 As a work around for this potential attack the length of the decrypted
5166 key must be equal to the cipher default key length, in case the
5167 certificate is not given and all recipientInfo are tried out.
5168 The old behaviour can be re-enabled in the CMS code by setting the
5169 CMS_DEBUG_DECRYPT flag.
5174 * Document issue with installation paths in diverse Windows builds
5176 '/usr/local/ssl' is an unsafe prefix for location to install OpenSSL
5177 binaries and run-time config file.
5182 ### Changes between 1.0.2r and 1.0.2s [28 May 2019]
5184 * Change the default RSA, DSA and DH size to 2048 bit instead of 1024.
5185 This changes the size when using the `genpkey` command when no size is given.
5186 It fixes an omission in earlier changes that changed all RSA, DSA and DH
5187 generation commands to use 2048 bits by default.
5191 * Add FIPS support for Android Arm 64-bit
5193 Support for Android Arm 64-bit was added to the OpenSSL FIPS Object
5194 Module in Version 2.0.10. For some reason, the corresponding target
5195 'android64-aarch64' was missing OpenSSL 1.0.2, whence it could not be
5196 built with FIPS support on Android Arm 64-bit. This omission has been
5199 *Matthias St. Pierre*
5201 ### Changes between 1.0.2q and 1.0.2r [26 Feb 2019]
5203 * 0-byte record padding oracle
5205 If an application encounters a fatal protocol error and then calls
5206 SSL_shutdown() twice (once to send a close_notify, and once to receive one)
5207 then OpenSSL can respond differently to the calling application if a 0 byte
5208 record is received with invalid padding compared to if a 0 byte record is
5209 received with an invalid MAC. If the application then behaves differently
5210 based on that in a way that is detectable to the remote peer, then this
5211 amounts to a padding oracle that could be used to decrypt data.
5213 In order for this to be exploitable "non-stitched" ciphersuites must be in
5214 use. Stitched ciphersuites are optimised implementations of certain
5215 commonly used ciphersuites. Also the application must call SSL_shutdown()
5216 twice even if a protocol error has occurred (applications should not do
5217 this but some do anyway).
5219 This issue was discovered by Juraj Somorovsky, Robert Merget and Nimrod
5220 Aviram, with additional investigation by Steven Collison and Andrew
5221 Hourselt. It was reported to OpenSSL on 10th December 2018.
5226 * Move strictness check from EVP_PKEY_asn1_new() to EVP_PKEY_asn1_add0().
5230 ### Changes between 1.0.2p and 1.0.2q [20 Nov 2018]
5232 * Microarchitecture timing vulnerability in ECC scalar multiplication
5234 OpenSSL ECC scalar multiplication, used in e.g. ECDSA and ECDH, has been
5235 shown to be vulnerable to a microarchitecture timing side channel attack.
5236 An attacker with sufficient access to mount local timing attacks during
5237 ECDSA signature generation could recover the private key.
5239 This issue was reported to OpenSSL on 26th October 2018 by Alejandro
5240 Cabrera Aldaya, Billy Brumley, Sohaib ul Hassan, Cesar Pereida Garcia and
5246 * Timing vulnerability in DSA signature generation
5248 The OpenSSL DSA signature algorithm has been shown to be vulnerable to a
5249 timing side channel attack. An attacker could use variations in the signing
5250 algorithm to recover the private key.
5252 This issue was reported to OpenSSL on 16th October 2018 by Samuel Weiser.
5257 * Resolve a compatibility issue in EC_GROUP handling with the FIPS Object
5258 Module, accidentally introduced while backporting security fixes from the
5259 development branch and hindering the use of ECC in FIPS mode.
5263 ### Changes between 1.0.2o and 1.0.2p [14 Aug 2018]
5265 * Client DoS due to large DH parameter
5267 During key agreement in a TLS handshake using a DH(E) based ciphersuite a
5268 malicious server can send a very large prime value to the client. This will
5269 cause the client to spend an unreasonably long period of time generating a
5270 key for this prime resulting in a hang until the client has finished. This
5271 could be exploited in a Denial Of Service attack.
5273 This issue was reported to OpenSSL on 5th June 2018 by Guido Vranken
5278 * Cache timing vulnerability in RSA Key Generation
5280 The OpenSSL RSA Key generation algorithm has been shown to be vulnerable to
5281 a cache timing side channel attack. An attacker with sufficient access to
5282 mount cache timing attacks during the RSA key generation process could
5283 recover the private key.
5285 This issue was reported to OpenSSL on 4th April 2018 by Alejandro Cabrera
5286 Aldaya, Billy Brumley, Cesar Pereida Garcia and Luis Manuel Alvarez Tapia.
5291 * Make EVP_PKEY_asn1_new() a bit stricter about its input. A NULL pem_str
5292 parameter is no longer accepted, as it leads to a corrupt table. NULL
5293 pem_str is reserved for alias entries only.
5297 * Revert blinding in ECDSA sign and instead make problematic addition
5298 length-invariant. Switch even to fixed-length Montgomery multiplication.
5302 * Change generating and checking of primes so that the error rate of not
5303 being prime depends on the intended use based on the size of the input.
5304 For larger primes this will result in more rounds of Miller-Rabin.
5305 The maximal error rate for primes with more than 1080 bits is lowered
5308 *Kurt Roeckx, Annie Yousar*
5310 * Increase the number of Miller-Rabin rounds for DSA key generating to 64.
5314 * Add blinding to ECDSA and DSA signatures to protect against side channel
5315 attacks discovered by Keegan Ryan (NCC Group).
5319 * When unlocking a pass phrase protected PEM file or PKCS#8 container, we
5320 now allow empty (zero character) pass phrases.
5324 * Certificate time validation (X509_cmp_time) enforces stricter
5325 compliance with RFC 5280. Fractional seconds and timezone offsets
5326 are no longer allowed.
5330 ### Changes between 1.0.2n and 1.0.2o [27 Mar 2018]
5332 * Constructed ASN.1 types with a recursive definition could exceed the stack
5334 Constructed ASN.1 types with a recursive definition (such as can be found
5335 in PKCS7) could eventually exceed the stack given malicious input with
5336 excessive recursion. This could result in a Denial Of Service attack. There
5337 are no such structures used within SSL/TLS that come from untrusted sources
5338 so this is considered safe.
5340 This issue was reported to OpenSSL on 4th January 2018 by the OSS-fuzz
5346 ### Changes between 1.0.2m and 1.0.2n [7 Dec 2017]
5348 * Read/write after SSL object in error state
5350 OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state"
5351 mechanism. The intent was that if a fatal error occurred during a handshake
5352 then OpenSSL would move into the error state and would immediately fail if
5353 you attempted to continue the handshake. This works as designed for the
5354 explicit handshake functions (SSL_do_handshake(), SSL_accept() and
5355 SSL_connect()), however due to a bug it does not work correctly if
5356 SSL_read() or SSL_write() is called directly. In that scenario, if the
5357 handshake fails then a fatal error will be returned in the initial function
5358 call. If SSL_read()/SSL_write() is subsequently called by the application
5359 for the same SSL object then it will succeed and the data is passed without
5360 being decrypted/encrypted directly from the SSL/TLS record layer.
5362 In order to exploit this issue an application bug would have to be present
5363 that resulted in a call to SSL_read()/SSL_write() being issued after having
5364 already received a fatal error.
5366 This issue was reported to OpenSSL by David Benjamin (Google).
5371 * rsaz_1024_mul_avx2 overflow bug on x86_64
5373 There is an overflow bug in the AVX2 Montgomery multiplication procedure
5374 used in exponentiation with 1024-bit moduli. No EC algorithms are affected.
5375 Analysis suggests that attacks against RSA and DSA as a result of this
5376 defect would be very difficult to perform and are not believed likely.
5377 Attacks against DH1024 are considered just feasible, because most of the
5378 work necessary to deduce information about a private key may be performed
5379 offline. The amount of resources required for such an attack would be
5380 significant. However, for an attack on TLS to be meaningful, the server
5381 would have to share the DH1024 private key among multiple clients, which is
5382 no longer an option since CVE-2016-0701.
5384 This only affects processors that support the AVX2 but not ADX extensions
5385 like Intel Haswell (4th generation).
5387 This issue was reported to OpenSSL by David Benjamin (Google). The issue
5388 was originally found via the OSS-Fuzz project.
5393 ### Changes between 1.0.2l and 1.0.2m [2 Nov 2017]
5395 * bn_sqrx8x_internal carry bug on x86_64
5397 There is a carry propagating bug in the x86_64 Montgomery squaring
5398 procedure. No EC algorithms are affected. Analysis suggests that attacks
5399 against RSA and DSA as a result of this defect would be very difficult to
5400 perform and are not believed likely. Attacks against DH are considered just
5401 feasible (although very difficult) because most of the work necessary to
5402 deduce information about a private key may be performed offline. The amount
5403 of resources required for such an attack would be very significant and
5404 likely only accessible to a limited number of attackers. An attacker would
5405 additionally need online access to an unpatched system using the target
5406 private key in a scenario with persistent DH parameters and a private
5407 key that is shared between multiple clients.
5409 This only affects processors that support the BMI1, BMI2 and ADX extensions
5410 like Intel Broadwell (5th generation) and later or AMD Ryzen.
5412 This issue was reported to OpenSSL by the OSS-Fuzz project.
5417 * Malformed X.509 IPAddressFamily could cause OOB read
5419 If an X.509 certificate has a malformed IPAddressFamily extension,
5420 OpenSSL could do a one-byte buffer overread. The most likely result
5421 would be an erroneous display of the certificate in text format.
5423 This issue was reported to OpenSSL by the OSS-Fuzz project.
5427 ### Changes between 1.0.2k and 1.0.2l [25 May 2017]
5429 * Have 'config' recognise 64-bit mingw and choose 'mingw64' as the target
5430 platform rather than 'mingw'.
5434 ### Changes between 1.0.2j and 1.0.2k [26 Jan 2017]
5436 * Truncated packet could crash via OOB read
5438 If one side of an SSL/TLS path is running on a 32-bit host and a specific
5439 cipher is being used, then a truncated packet can cause that host to
5440 perform an out-of-bounds read, usually resulting in a crash.
5442 This issue was reported to OpenSSL by Robert Święcki of Google.
5447 * BN_mod_exp may produce incorrect results on x86_64
5449 There is a carry propagating bug in the x86_64 Montgomery squaring
5450 procedure. No EC algorithms are affected. Analysis suggests that attacks
5451 against RSA and DSA as a result of this defect would be very difficult to
5452 perform and are not believed likely. Attacks against DH are considered just
5453 feasible (although very difficult) because most of the work necessary to
5454 deduce information about a private key may be performed offline. The amount
5455 of resources required for such an attack would be very significant and
5456 likely only accessible to a limited number of attackers. An attacker would
5457 additionally need online access to an unpatched system using the target
5458 private key in a scenario with persistent DH parameters and a private
5459 key that is shared between multiple clients. For example this can occur by
5460 default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very
5461 similar to CVE-2015-3193 but must be treated as a separate problem.
5463 This issue was reported to OpenSSL by the OSS-Fuzz project.
5468 * Montgomery multiplication may produce incorrect results
5470 There is a carry propagating bug in the Broadwell-specific Montgomery
5471 multiplication procedure that handles input lengths divisible by, but
5472 longer than 256 bits. Analysis suggests that attacks against RSA, DSA
5473 and DH private keys are impossible. This is because the subroutine in
5474 question is not used in operations with the private key itself and an input
5475 of the attacker's direct choice. Otherwise the bug can manifest itself as
5476 transient authentication and key negotiation failures or reproducible
5477 erroneous outcome of public-key operations with specially crafted input.
5478 Among EC algorithms only Brainpool P-512 curves are affected and one
5479 presumably can attack ECDH key negotiation. Impact was not analyzed in
5480 detail, because pre-requisites for attack are considered unlikely. Namely
5481 multiple clients have to choose the curve in question and the server has to
5482 share the private key among them, neither of which is default behaviour.
5483 Even then only clients that chose the curve will be affected.
5485 This issue was publicly reported as transient failures and was not
5486 initially recognized as a security issue. Thanks to Richard Morgan for
5487 providing reproducible case.
5492 * OpenSSL now fails if it receives an unrecognised record type in TLS1.0
5493 or TLS1.1. Previously this only happened in SSLv3 and TLS1.2. This is to
5494 prevent issues where no progress is being made and the peer continually
5495 sends unrecognised record types, using up resources processing them.
5499 ### Changes between 1.0.2i and 1.0.2j [26 Sep 2016]
5501 * Missing CRL sanity check
5503 A bug fix which included a CRL sanity check was added to OpenSSL 1.1.0
5504 but was omitted from OpenSSL 1.0.2i. As a result any attempt to use
5505 CRLs in OpenSSL 1.0.2i will crash with a null pointer exception.
5507 This issue only affects the OpenSSL 1.0.2i
5512 ### Changes between 1.0.2h and 1.0.2i [22 Sep 2016]
5514 * OCSP Status Request extension unbounded memory growth
5516 A malicious client can send an excessively large OCSP Status Request
5517 extension. If that client continually requests renegotiation, sending a
5518 large OCSP Status Request extension each time, then there will be unbounded
5519 memory growth on the server. This will eventually lead to a Denial Of
5520 Service attack through memory exhaustion. Servers with a default
5521 configuration are vulnerable even if they do not support OCSP. Builds using
5522 the "no-ocsp" build time option are not affected.
5524 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
5529 * In order to mitigate the SWEET32 attack, the DES ciphers were moved from
5532 This issue was reported to OpenSSL Karthikeyan Bhargavan and Gaetan
5538 * OOB write in MDC2_Update()
5540 An overflow can occur in MDC2_Update() either if called directly or
5541 through the EVP_DigestUpdate() function using MDC2. If an attacker
5542 is able to supply very large amounts of input data after a previous
5543 call to EVP_EncryptUpdate() with a partial block then a length check
5544 can overflow resulting in a heap corruption.
5546 The amount of data needed is comparable to SIZE_MAX which is impractical
5549 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
5554 * Malformed SHA512 ticket DoS
5556 If a server uses SHA512 for TLS session ticket HMAC it is vulnerable to a
5557 DoS attack where a malformed ticket will result in an OOB read which will
5560 The use of SHA512 in TLS session tickets is comparatively rare as it requires
5561 a custom server callback and ticket lookup mechanism.
5563 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
5568 * OOB write in BN_bn2dec()
5570 The function BN_bn2dec() does not check the return value of BN_div_word().
5571 This can cause an OOB write if an application uses this function with an
5572 overly large BIGNUM. This could be a problem if an overly large certificate
5573 or CRL is printed out from an untrusted source. TLS is not affected because
5574 record limits will reject an oversized certificate before it is parsed.
5576 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
5581 * OOB read in TS_OBJ_print_bio()
5583 The function TS_OBJ_print_bio() misuses OBJ_obj2txt(): the return value is
5584 the total length the OID text representation would use and not the amount
5585 of data written. This will result in OOB reads when large OIDs are
5588 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
5593 * Pointer arithmetic undefined behaviour
5595 Avoid some undefined pointer arithmetic
5597 A common idiom in the codebase is to check limits in the following manner:
5600 Where "p" points to some malloc'd data of SIZE bytes and
5603 "len" here could be from some externally supplied data (e.g. from a TLS
5606 The rules of C pointer arithmetic are such that "p + len" is only well
5607 defined where len <= SIZE. Therefore the above idiom is actually
5608 undefined behaviour.
5610 For example this could cause problems if some malloc implementation
5611 provides an address for "p" such that "p + len" actually overflows for
5612 values of len that are too big and therefore p + len < limit.
5614 This issue was reported to OpenSSL by Guido Vranken
5619 * Constant time flag not preserved in DSA signing
5621 Operations in the DSA signing algorithm should run in constant time in
5622 order to avoid side channel attacks. A flaw in the OpenSSL DSA
5623 implementation means that a non-constant time codepath is followed for
5624 certain operations. This has been demonstrated through a cache-timing
5625 attack to be sufficient for an attacker to recover the private DSA key.
5627 This issue was reported by César Pereida (Aalto University), Billy Brumley
5628 (Tampere University of Technology), and Yuval Yarom (The University of
5629 Adelaide and NICTA).
5634 * DTLS buffered message DoS
5636 In a DTLS connection where handshake messages are delivered out-of-order
5637 those messages that OpenSSL is not yet ready to process will be buffered
5638 for later use. Under certain circumstances, a flaw in the logic means that
5639 those messages do not get removed from the buffer even though the handshake
5640 has been completed. An attacker could force up to approx. 15 messages to
5641 remain in the buffer when they are no longer required. These messages will
5642 be cleared when the DTLS connection is closed. The default maximum size for
5643 a message is 100k. Therefore, the attacker could force an additional 1500k
5644 to be consumed per connection. By opening many simultaneous connections an
5645 attacker could cause a DoS attack through memory exhaustion.
5647 This issue was reported to OpenSSL by Quan Luo.
5652 * DTLS replay protection DoS
5654 A flaw in the DTLS replay attack protection mechanism means that records
5655 that arrive for future epochs update the replay protection "window" before
5656 the MAC for the record has been validated. This could be exploited by an
5657 attacker by sending a record for the next epoch (which does not have to
5658 decrypt or have a valid MAC), with a very large sequence number. This means
5659 that all subsequent legitimate packets are dropped causing a denial of
5660 service for a specific DTLS connection.
5662 This issue was reported to OpenSSL by the OCAP audit team.
5667 * Certificate message OOB reads
5669 In OpenSSL 1.0.2 and earlier some missing message length checks can result
5670 in OOB reads of up to 2 bytes beyond an allocated buffer. There is a
5671 theoretical DoS risk but this has not been observed in practice on common
5674 The messages affected are client certificate, client certificate request
5675 and server certificate. As a result the attack can only be performed
5676 against a client or a server which enables client authentication.
5678 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
5683 ### Changes between 1.0.2g and 1.0.2h [3 May 2016]
5685 * Prevent padding oracle in AES-NI CBC MAC check
5687 A MITM attacker can use a padding oracle attack to decrypt traffic
5688 when the connection uses an AES CBC cipher and the server support
5691 This issue was introduced as part of the fix for Lucky 13 padding
5692 attack ([CVE-2013-0169]). The padding check was rewritten to be in
5693 constant time by making sure that always the same bytes are read and
5694 compared against either the MAC or padding bytes. But it no longer
5695 checked that there was enough data to have both the MAC and padding
5698 This issue was reported by Juraj Somorovsky using TLS-Attacker.
5702 * Fix EVP_EncodeUpdate overflow
5704 An overflow can occur in the EVP_EncodeUpdate() function which is used for
5705 Base64 encoding of binary data. If an attacker is able to supply very large
5706 amounts of input data then a length check can overflow resulting in a heap
5709 Internally to OpenSSL the EVP_EncodeUpdate() function is primarily used by
5710 the `PEM_write_bio*` family of functions. These are mainly used within the
5711 OpenSSL command line applications, so any application which processes data
5712 from an untrusted source and outputs it as a PEM file should be considered
5713 vulnerable to this issue. User applications that call these APIs directly
5714 with large amounts of untrusted data may also be vulnerable.
5716 This issue was reported by Guido Vranken.
5721 * Fix EVP_EncryptUpdate overflow
5723 An overflow can occur in the EVP_EncryptUpdate() function. If an attacker
5724 is able to supply very large amounts of input data after a previous call to
5725 EVP_EncryptUpdate() with a partial block then a length check can overflow
5726 resulting in a heap corruption. Following an analysis of all OpenSSL
5727 internal usage of the EVP_EncryptUpdate() function all usage is one of two
5728 forms. The first form is where the EVP_EncryptUpdate() call is known to be
5729 the first called function after an EVP_EncryptInit(), and therefore that
5730 specific call must be safe. The second form is where the length passed to
5731 EVP_EncryptUpdate() can be seen from the code to be some small value and
5732 therefore there is no possibility of an overflow. Since all instances are
5733 one of these two forms, it is believed that there can be no overflows in
5734 internal code due to this problem. It should be noted that
5735 EVP_DecryptUpdate() can call EVP_EncryptUpdate() in certain code paths.
5736 Also EVP_CipherUpdate() is a synonym for EVP_EncryptUpdate(). All instances
5737 of these calls have also been analysed too and it is believed there are no
5738 instances in internal usage where an overflow could occur.
5740 This issue was reported by Guido Vranken.
5745 * Prevent ASN.1 BIO excessive memory allocation
5747 When ASN.1 data is read from a BIO using functions such as d2i_CMS_bio()
5748 a short invalid encoding can cause allocation of large amounts of memory
5749 potentially consuming excessive resources or exhausting memory.
5751 Any application parsing untrusted data through d2i BIO functions is
5752 affected. The memory based functions such as d2i_X509() are *not* affected.
5753 Since the memory based functions are used by the TLS library, TLS
5754 applications are not affected.
5756 This issue was reported by Brian Carpenter.
5763 ASN1 Strings that are over 1024 bytes can cause an overread in applications
5764 using the X509_NAME_oneline() function on EBCDIC systems. This could result
5765 in arbitrary stack data being returned in the buffer.
5767 This issue was reported by Guido Vranken.
5772 * Modify behavior of ALPN to invoke callback after SNI/servername
5773 callback, such that updates to the SSL_CTX affect ALPN.
5777 * Remove LOW from the DEFAULT cipher list. This removes singles DES from the
5782 * Only remove the SSLv2 methods with the no-ssl2-method option. When the
5783 methods are enabled and ssl2 is disabled the methods return NULL.
5787 ### Changes between 1.0.2f and 1.0.2g [1 Mar 2016]
5789 * Disable weak ciphers in SSLv3 and up in default builds of OpenSSL.
5790 Builds that are not configured with "enable-weak-ssl-ciphers" will not
5791 provide any "EXPORT" or "LOW" strength ciphers.
5795 * Disable SSLv2 default build, default negotiation and weak ciphers. SSLv2
5796 is by default disabled at build-time. Builds that are not configured with
5797 "enable-ssl2" will not support SSLv2. Even if "enable-ssl2" is used,
5798 users who want to negotiate SSLv2 via the version-flexible SSLv23_method()
5799 will need to explicitly call either of:
5801 SSL_CTX_clear_options(ctx, SSL_OP_NO_SSLv2);
5803 SSL_clear_options(ssl, SSL_OP_NO_SSLv2);
5805 as appropriate. Even if either of those is used, or the application
5806 explicitly uses the version-specific SSLv2_method() or its client and
5807 server variants, SSLv2 ciphers vulnerable to exhaustive search key
5808 recovery have been removed. Specifically, the SSLv2 40-bit EXPORT
5809 ciphers, and SSLv2 56-bit DES are no longer available.
5814 * Fix a double-free in DSA code
5816 A double free bug was discovered when OpenSSL parses malformed DSA private
5817 keys and could lead to a DoS attack or memory corruption for applications
5818 that receive DSA private keys from untrusted sources. This scenario is
5821 This issue was reported to OpenSSL by Adam Langley(Google/BoringSSL) using
5827 * Disable SRP fake user seed to address a server memory leak.
5829 Add a new method SRP_VBASE_get1_by_user that handles the seed properly.
5831 SRP_VBASE_get_by_user had inconsistent memory management behaviour.
5832 In order to fix an unavoidable memory leak, SRP_VBASE_get_by_user
5833 was changed to ignore the "fake user" SRP seed, even if the seed
5836 Users should use SRP_VBASE_get1_by_user instead. Note that in
5837 SRP_VBASE_get1_by_user, caller must free the returned value. Note
5838 also that even though configuring the SRP seed attempts to hide
5839 invalid usernames by continuing the handshake with fake
5840 credentials, this behaviour is not constant time and no strong
5841 guarantees are made that the handshake is indistinguishable from
5842 that of a valid user.
5847 * Fix BN_hex2bn/BN_dec2bn NULL pointer deref/heap corruption
5849 In the BN_hex2bn function the number of hex digits is calculated using an
5850 int value `i`. Later `bn_expand` is called with a value of `i * 4`. For
5851 large values of `i` this can result in `bn_expand` not allocating any
5852 memory because `i * 4` is negative. This can leave the internal BIGNUM data
5853 field as NULL leading to a subsequent NULL ptr deref. For very large values
5854 of `i`, the calculation `i * 4` could be a positive value smaller than `i`.
5855 In this case memory is allocated to the internal BIGNUM data field, but it
5856 is insufficiently sized leading to heap corruption. A similar issue exists
5857 in BN_dec2bn. This could have security consequences if BN_hex2bn/BN_dec2bn
5858 is ever called by user applications with very large untrusted hex/dec data.
5859 This is anticipated to be a rare occurrence.
5861 All OpenSSL internal usage of these functions use data that is not expected
5862 to be untrusted, e.g. config file data or application command line
5863 arguments. If user developed applications generate config file data based
5864 on untrusted data then it is possible that this could also lead to security
5865 consequences. This is also anticipated to be rare.
5867 This issue was reported to OpenSSL by Guido Vranken.
5872 * Fix memory issues in `BIO_*printf` functions
5874 The internal `fmtstr` function used in processing a "%s" format string in
5875 the `BIO_*printf` functions could overflow while calculating the length of a
5876 string and cause an OOB read when printing very long strings.
5878 Additionally the internal `doapr_outch` function can attempt to write to an
5879 OOB memory location (at an offset from the NULL pointer) in the event of a
5880 memory allocation failure. In 1.0.2 and below this could be caused where
5881 the size of a buffer to be allocated is greater than INT_MAX. E.g. this
5882 could be in processing a very long "%s" format string. Memory leaks can
5885 The first issue may mask the second issue dependent on compiler behaviour.
5886 These problems could enable attacks where large amounts of untrusted data
5887 is passed to the `BIO_*printf` functions. If applications use these functions
5888 in this way then they could be vulnerable. OpenSSL itself uses these
5889 functions when printing out human-readable dumps of ASN.1 data. Therefore
5890 applications that print this data could be vulnerable if the data is from
5891 untrusted sources. OpenSSL command line applications could also be
5892 vulnerable where they print out ASN.1 data, or if untrusted data is passed
5893 as command line arguments.
5895 Libssl is not considered directly vulnerable. Additionally certificates etc
5896 received via remote connections via libssl are also unlikely to be able to
5897 trigger these issues because of message size limits enforced within libssl.
5899 This issue was reported to OpenSSL Guido Vranken.
5904 * Side channel attack on modular exponentiation
5906 A side-channel attack was found which makes use of cache-bank conflicts on
5907 the Intel Sandy-Bridge microarchitecture which could lead to the recovery
5908 of RSA keys. The ability to exploit this issue is limited as it relies on
5909 an attacker who has control of code in a thread running on the same
5910 hyper-threaded core as the victim thread which is performing decryptions.
5912 This issue was reported to OpenSSL by Yuval Yarom, The University of
5913 Adelaide and NICTA, Daniel Genkin, Technion and Tel Aviv University, and
5914 Nadia Heninger, University of Pennsylvania with more information at
5915 <http://cachebleed.info>.
5920 * Change the `req` command to generate a 2048-bit RSA/DSA key by default,
5921 if no keysize is specified with default_bits. This fixes an
5922 omission in an earlier change that changed all RSA/DSA key generation
5923 commands to use 2048 bits by default.
5927 ### Changes between 1.0.2e and 1.0.2f [28 Jan 2016]
5929 * DH small subgroups
5931 Historically OpenSSL only ever generated DH parameters based on "safe"
5932 primes. More recently (in version 1.0.2) support was provided for
5933 generating X9.42 style parameter files such as those required for RFC 5114
5934 support. The primes used in such files may not be "safe". Where an
5935 application is using DH configured with parameters based on primes that are
5936 not "safe" then an attacker could use this fact to find a peer's private
5937 DH exponent. This attack requires that the attacker complete multiple
5938 handshakes in which the peer uses the same private DH exponent. For example
5939 this could be used to discover a TLS server's private DH exponent if it's
5940 reusing the private DH exponent or it's using a static DH ciphersuite.
5942 OpenSSL provides the option SSL_OP_SINGLE_DH_USE for ephemeral DH (DHE) in
5943 TLS. It is not on by default. If the option is not set then the server
5944 reuses the same private DH exponent for the life of the server process and
5945 would be vulnerable to this attack. It is believed that many popular
5946 applications do set this option and would therefore not be at risk.
5948 The fix for this issue adds an additional check where a "q" parameter is
5949 available (as is the case in X9.42 based parameters). This detects the
5950 only known attack, and is the only possible defense for static DH
5951 ciphersuites. This could have some performance impact.
5953 Additionally the SSL_OP_SINGLE_DH_USE option has been switched on by
5954 default and cannot be disabled. This could have some performance impact.
5956 This issue was reported to OpenSSL by Antonio Sanso (Adobe).
5961 * SSLv2 doesn't block disabled ciphers
5963 A malicious client can negotiate SSLv2 ciphers that have been disabled on
5964 the server and complete SSLv2 handshakes even if all SSLv2 ciphers have
5965 been disabled, provided that the SSLv2 protocol was not also disabled via
5968 This issue was reported to OpenSSL on 26th December 2015 by Nimrod Aviram
5969 and Sebastian Schinzel.
5974 ### Changes between 1.0.2d and 1.0.2e [3 Dec 2015]
5976 * BN_mod_exp may produce incorrect results on x86_64
5978 There is a carry propagating bug in the x86_64 Montgomery squaring
5979 procedure. No EC algorithms are affected. Analysis suggests that attacks
5980 against RSA and DSA as a result of this defect would be very difficult to
5981 perform and are not believed likely. Attacks against DH are considered just
5982 feasible (although very difficult) because most of the work necessary to
5983 deduce information about a private key may be performed offline. The amount
5984 of resources required for such an attack would be very significant and
5985 likely only accessible to a limited number of attackers. An attacker would
5986 additionally need online access to an unpatched system using the target
5987 private key in a scenario with persistent DH parameters and a private
5988 key that is shared between multiple clients. For example this can occur by
5989 default in OpenSSL DHE based SSL/TLS ciphersuites.
5991 This issue was reported to OpenSSL by Hanno Böck.
5996 * Certificate verify crash with missing PSS parameter
5998 The signature verification routines will crash with a NULL pointer
5999 dereference if presented with an ASN.1 signature using the RSA PSS
6000 algorithm and absent mask generation function parameter. Since these
6001 routines are used to verify certificate signature algorithms this can be
6002 used to crash any certificate verification operation and exploited in a
6003 DoS attack. Any application which performs certificate verification is
6004 vulnerable including OpenSSL clients and servers which enable client
6007 This issue was reported to OpenSSL by Loïc Jonas Etienne (Qnective AG).
6012 * X509_ATTRIBUTE memory leak
6014 When presented with a malformed X509_ATTRIBUTE structure OpenSSL will leak
6015 memory. This structure is used by the PKCS#7 and CMS routines so any
6016 application which reads PKCS#7 or CMS data from untrusted sources is
6017 affected. SSL/TLS is not affected.
6019 This issue was reported to OpenSSL by Adam Langley (Google/BoringSSL) using
6025 * Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs.
6026 This changes the decoding behaviour for some invalid messages,
6027 though the change is mostly in the more lenient direction, and
6028 legacy behaviour is preserved as much as possible.
6032 * In DSA_generate_parameters_ex, if the provided seed is too short,
6035 *Rich Salz and Ismo Puustinen <ismo.puustinen@intel.com>*
6037 ### Changes between 1.0.2c and 1.0.2d [9 Jul 2015]
6039 * Alternate chains certificate forgery
6041 During certificate verification, OpenSSL will attempt to find an
6042 alternative certificate chain if the first attempt to build such a chain
6043 fails. An error in the implementation of this logic can mean that an
6044 attacker could cause certain checks on untrusted certificates to be
6045 bypassed, such as the CA flag, enabling them to use a valid leaf
6046 certificate to act as a CA and "issue" an invalid certificate.
6048 This issue was reported to OpenSSL by Adam Langley/David Benjamin
6053 ### Changes between 1.0.2b and 1.0.2c [12 Jun 2015]
6055 * Fix HMAC ABI incompatibility. The previous version introduced an ABI
6056 incompatibility in the handling of HMAC. The previous ABI has now been
6061 ### Changes between 1.0.2a and 1.0.2b [11 Jun 2015]
6063 * Malformed ECParameters causes infinite loop
6065 When processing an ECParameters structure OpenSSL enters an infinite loop
6066 if the curve specified is over a specially malformed binary polynomial
6069 This can be used to perform denial of service against any
6070 system which processes public keys, certificate requests or
6071 certificates. This includes TLS clients and TLS servers with
6072 client authentication enabled.
6074 This issue was reported to OpenSSL by Joseph Barr-Pixton.
6079 * Exploitable out-of-bounds read in X509_cmp_time
6081 X509_cmp_time does not properly check the length of the ASN1_TIME
6082 string and can read a few bytes out of bounds. In addition,
6083 X509_cmp_time accepts an arbitrary number of fractional seconds in the
6086 An attacker can use this to craft malformed certificates and CRLs of
6087 various sizes and potentially cause a segmentation fault, resulting in
6088 a DoS on applications that verify certificates or CRLs. TLS clients
6089 that verify CRLs are affected. TLS clients and servers with client
6090 authentication enabled may be affected if they use custom verification
6093 This issue was reported to OpenSSL by Robert Swiecki (Google), and
6094 independently by Hanno Böck.
6099 * PKCS7 crash with missing EnvelopedContent
6101 The PKCS#7 parsing code does not handle missing inner EncryptedContent
6102 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs
6103 with missing content and trigger a NULL pointer dereference on parsing.
6105 Applications that decrypt PKCS#7 data or otherwise parse PKCS#7
6106 structures from untrusted sources are affected. OpenSSL clients and
6107 servers are not affected.
6109 This issue was reported to OpenSSL by Michal Zalewski (Google).
6114 * CMS verify infinite loop with unknown hash function
6116 When verifying a signedData message the CMS code can enter an infinite loop
6117 if presented with an unknown hash function OID. This can be used to perform
6118 denial of service against any system which verifies signedData messages using
6120 This issue was reported to OpenSSL by Johannes Bauer.
6125 * Race condition handling NewSessionTicket
6127 If a NewSessionTicket is received by a multi-threaded client when attempting to
6128 reuse a previous ticket then a race condition can occur potentially leading to
6129 a double free of the ticket data.
6134 * Only support 256-bit or stronger elliptic curves with the
6135 'ecdh_auto' setting (server) or by default (client). Of supported
6136 curves, prefer P-256 (both).
6140 ### Changes between 1.0.2 and 1.0.2a [19 Mar 2015]
6142 * ClientHello sigalgs DoS fix
6144 If a client connects to an OpenSSL 1.0.2 server and renegotiates with an
6145 invalid signature algorithms extension a NULL pointer dereference will
6146 occur. This can be exploited in a DoS attack against the server.
6148 This issue was was reported to OpenSSL by David Ramos of Stanford
6152 *Stephen Henson and Matt Caswell*
6154 * Multiblock corrupted pointer fix
6156 OpenSSL 1.0.2 introduced the "multiblock" performance improvement. This
6157 feature only applies on 64 bit x86 architecture platforms that support AES
6158 NI instructions. A defect in the implementation of "multiblock" can cause
6159 OpenSSL's internal write buffer to become incorrectly set to NULL when
6160 using non-blocking IO. Typically, when the user application is using a
6161 socket BIO for writing, this will only result in a failed connection.
6162 However if some other BIO is used then it is likely that a segmentation
6163 fault will be triggered, thus enabling a potential DoS attack.
6165 This issue was reported to OpenSSL by Daniel Danner and Rainer Mueller.
6170 * Segmentation fault in DTLSv1_listen fix
6172 The DTLSv1_listen function is intended to be stateless and processes the
6173 initial ClientHello from many peers. It is common for user code to loop
6174 over the call to DTLSv1_listen until a valid ClientHello is received with
6175 an associated cookie. A defect in the implementation of DTLSv1_listen means
6176 that state is preserved in the SSL object from one invocation to the next
6177 that can lead to a segmentation fault. Errors processing the initial
6178 ClientHello can trigger this scenario. An example of such an error could be
6179 that a DTLS1.0 only client is attempting to connect to a DTLS1.2 only
6182 This issue was reported to OpenSSL by Per Allansson.
6187 * Segmentation fault in ASN1_TYPE_cmp fix
6189 The function ASN1_TYPE_cmp will crash with an invalid read if an attempt is
6190 made to compare ASN.1 boolean types. Since ASN1_TYPE_cmp is used to check
6191 certificate signature algorithm consistency this can be used to crash any
6192 certificate verification operation and exploited in a DoS attack. Any
6193 application which performs certificate verification is vulnerable including
6194 OpenSSL clients and servers which enable client authentication.
6199 * Segmentation fault for invalid PSS parameters fix
6201 The signature verification routines will crash with a NULL pointer
6202 dereference if presented with an ASN.1 signature using the RSA PSS
6203 algorithm and invalid parameters. Since these routines are used to verify
6204 certificate signature algorithms this can be used to crash any
6205 certificate verification operation and exploited in a DoS attack. Any
6206 application which performs certificate verification is vulnerable including
6207 OpenSSL clients and servers which enable client authentication.
6209 This issue was was reported to OpenSSL by Brian Carpenter.
6214 * ASN.1 structure reuse memory corruption fix
6216 Reusing a structure in ASN.1 parsing may allow an attacker to cause
6217 memory corruption via an invalid write. Such reuse is and has been
6218 strongly discouraged and is believed to be rare.
6220 Applications that parse structures containing CHOICE or ANY DEFINED BY
6221 components may be affected. Certificate parsing (d2i_X509 and related
6222 functions) are however not affected. OpenSSL clients and servers are
6228 * PKCS7 NULL pointer dereferences fix
6230 The PKCS#7 parsing code does not handle missing outer ContentInfo
6231 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with
6232 missing content and trigger a NULL pointer dereference on parsing.
6234 Applications that verify PKCS#7 signatures, decrypt PKCS#7 data or
6235 otherwise parse PKCS#7 structures from untrusted sources are
6236 affected. OpenSSL clients and servers are not affected.
6238 This issue was reported to OpenSSL by Michal Zalewski (Google).
6243 * DoS via reachable assert in SSLv2 servers fix
6245 A malicious client can trigger an OPENSSL_assert (i.e., an abort) in
6246 servers that both support SSLv2 and enable export cipher suites by sending
6247 a specially crafted SSLv2 CLIENT-MASTER-KEY message.
6249 This issue was discovered by Sean Burford (Google) and Emilia Käsper
6250 (OpenSSL development team).
6255 * Empty CKE with client auth and DHE fix
6257 If client auth is used then a server can seg fault in the event of a DHE
6258 ciphersuite being selected and a zero length ClientKeyExchange message
6259 being sent by the client. This could be exploited in a DoS attack.
6264 * Handshake with unseeded PRNG fix
6266 Under certain conditions an OpenSSL 1.0.2 client can complete a handshake
6267 with an unseeded PRNG. The conditions are:
6268 - The client is on a platform where the PRNG has not been seeded
6269 automatically, and the user has not seeded manually
6270 - A protocol specific client method version has been used (i.e. not
6271 SSL_client_methodv23)
6272 - A ciphersuite is used that does not require additional random data from
6273 the PRNG beyond the initial ClientHello client random (e.g. PSK-RC4-SHA).
6275 If the handshake succeeds then the client random that has been used will
6276 have been generated from a PRNG with insufficient entropy and therefore the
6277 output may be predictable.
6279 For example using the following command with an unseeded openssl will
6280 succeed on an unpatched platform:
6282 openssl s_client -psk 1a2b3c4d -tls1_2 -cipher PSK-RC4-SHA
6287 * Use After Free following d2i_ECPrivatekey error fix
6289 A malformed EC private key file consumed via the d2i_ECPrivateKey function
6290 could cause a use after free condition. This, in turn, could cause a double
6291 free in several private key parsing functions (such as d2i_PrivateKey
6292 or EVP_PKCS82PKEY) and could lead to a DoS attack or memory corruption
6293 for applications that receive EC private keys from untrusted
6294 sources. This scenario is considered rare.
6296 This issue was discovered by the BoringSSL project and fixed in their
6302 * X509_to_X509_REQ NULL pointer deref fix
6304 The function X509_to_X509_REQ will crash with a NULL pointer dereference if
6305 the certificate key is invalid. This function is rarely used in practice.
6307 This issue was discovered by Brian Carpenter.
6312 * Removed the export ciphers from the DEFAULT ciphers
6316 ### Changes between 1.0.1l and 1.0.2 [22 Jan 2015]
6318 * Facilitate "universal" ARM builds targeting range of ARM ISAs, e.g.
6319 ARMv5 through ARMv8, as opposite to "locking" it to single one.
6320 So far those who have to target multiple platforms would compromise
6321 and argue that binary targeting say ARMv5 would still execute on
6322 ARMv8. "Universal" build resolves this compromise by providing
6323 near-optimal performance even on newer platforms.
6327 * Accelerated NIST P-256 elliptic curve implementation for x86_64
6328 (other platforms pending).
6330 *Shay Gueron & Vlad Krasnov (Intel Corp), Andy Polyakov*
6332 * Add support for the SignedCertificateTimestampList certificate and
6333 OCSP response extensions from RFC6962.
6337 * Fix ec_GFp_simple_points_make_affine (thus, EC_POINTs_mul etc.)
6338 for corner cases. (Certain input points at infinity could lead to
6339 bogus results, with non-infinity inputs mapped to infinity too.)
6343 * Initial support for PowerISA 2.0.7, first implemented in POWER8.
6344 This covers AES, SHA256/512 and GHASH. "Initial" means that most
6345 common cases are optimized and there still is room for further
6346 improvements. Vector Permutation AES for Altivec is also added.
6350 * Add support for little-endian ppc64 Linux target.
6352 *Marcelo Cerri (IBM)*
6354 * Initial support for AMRv8 ISA crypto extensions. This covers AES,
6355 SHA1, SHA256 and GHASH. "Initial" means that most common cases
6356 are optimized and there still is room for further improvements.
6357 Both 32- and 64-bit modes are supported.
6359 *Andy Polyakov, Ard Biesheuvel (Linaro)*
6361 * Improved ARMv7 NEON support.
6365 * Support for SPARC Architecture 2011 crypto extensions, first
6366 implemented in SPARC T4. This covers AES, DES, Camellia, SHA1,
6367 SHA256/512, MD5, GHASH and modular exponentiation.
6369 *Andy Polyakov, David Miller*
6371 * Accelerated modular exponentiation for Intel processors, a.k.a.
6374 *Shay Gueron & Vlad Krasnov (Intel Corp)*
6376 * Support for new and upcoming Intel processors, including AVX2,
6377 BMI and SHA ISA extensions. This includes additional "stitched"
6378 implementations, AESNI-SHA256 and GCM, and multi-buffer support
6381 This work was sponsored by Intel Corp.
6385 * Support for DTLS 1.2. This adds two sets of DTLS methods: DTLS_*_method()
6386 supports both DTLS 1.2 and 1.0 and should use whatever version the peer
6387 supports and DTLSv1_2_*_method() which supports DTLS 1.2 only.
6391 * Use algorithm specific chains in SSL_CTX_use_certificate_chain_file():
6392 this fixes a limitation in previous versions of OpenSSL.
6396 * Extended RSA OAEP support via EVP_PKEY API. Options to specify digest,
6397 MGF1 digest and OAEP label.
6401 * Add EVP support for key wrapping algorithms, to avoid problems with
6402 existing code the flag EVP_CIPHER_CTX_WRAP_ALLOW has to be set in
6403 the EVP_CIPHER_CTX or an error is returned. Add AES and DES3 wrap
6404 algorithms and include tests cases.
6408 * Add functions to allocate and set the fields of an ECDSA_METHOD
6411 *Douglas E. Engert, Steve Henson*
6413 * New functions OPENSSL_gmtime_diff and ASN1_TIME_diff to find the
6414 difference in days and seconds between two tm or ASN1_TIME structures.
6418 * Add -rev test option to s_server to just reverse order of characters
6419 received by client and send back to server. Also prints an abbreviated
6420 summary of the connection parameters.
6424 * New option -brief for s_client and s_server to print out a brief summary
6425 of connection parameters.
6429 * Add callbacks for arbitrary TLS extensions.
6431 *Trevor Perrin <trevp@trevp.net> and Ben Laurie*
6433 * New option -crl_download in several openssl utilities to download CRLs
6434 from CRLDP extension in certificates.
6438 * New options -CRL and -CRLform for s_client and s_server for CRLs.
6442 * New function X509_CRL_diff to generate a delta CRL from the difference
6443 of two full CRLs. Add support to "crl" utility.
6447 * New functions to set lookup_crls function and to retrieve
6448 X509_STORE from X509_STORE_CTX.
6452 * Print out deprecated issuer and subject unique ID fields in
6457 * Extend OCSP I/O functions so they can be used for simple general purpose
6458 HTTP as well as OCSP. New wrapper function which can be used to download
6459 CRLs using the OCSP API.
6463 * Delegate command line handling in s_client/s_server to SSL_CONF APIs.
6467 * `SSL_CONF*` functions. These provide a common framework for application
6468 configuration using configuration files or command lines.
6472 * SSL/TLS tracing code. This parses out SSL/TLS records using the
6473 message callback and prints the results. Needs compile time option
6474 "enable-ssl-trace". New options to s_client and s_server to enable
6479 * New ctrl and macro to retrieve supported points extensions.
6480 Print out extension in s_server and s_client.
6484 * New functions to retrieve certificate signature and signature
6489 * Add functions to retrieve and manipulate the raw cipherlist sent by a
6494 * New Suite B modes for TLS code. These use and enforce the requirements
6495 of RFC6460: restrict ciphersuites, only permit Suite B algorithms and
6496 only use Suite B curves. The Suite B modes can be set by using the
6497 strings "SUITEB128", "SUITEB192" or "SUITEB128ONLY" for the cipherstring.
6501 * New chain verification flags for Suite B levels of security. Check
6502 algorithms are acceptable when flags are set in X509_verify_cert.
6506 * Make tls1_check_chain return a set of flags indicating checks passed
6507 by a certificate chain. Add additional tests to handle client
6508 certificates: checks for matching certificate type and issuer name
6513 * If an attempt is made to use a signature algorithm not in the peer
6514 preference list abort the handshake. If client has no suitable
6515 signature algorithms in response to a certificate request do not
6516 use the certificate.
6520 * If server EC tmp key is not in client preference list abort handshake.
6524 * Add support for certificate stores in CERT structure. This makes it
6525 possible to have different stores per SSL structure or one store in
6526 the parent SSL_CTX. Include distinct stores for certificate chain
6527 verification and chain building. New ctrl SSL_CTRL_BUILD_CERT_CHAIN
6528 to build and store a certificate chain in CERT structure: returning
6529 an error if the chain cannot be built: this will allow applications
6530 to test if a chain is correctly configured.
6532 Note: if the CERT based stores are not set then the parent SSL_CTX
6533 store is used to retain compatibility with existing behaviour.
6537 * New function ssl_set_client_disabled to set a ciphersuite disabled
6538 mask based on the current session, check mask when sending client
6539 hello and checking the requested ciphersuite.
6543 * New ctrls to retrieve and set certificate types in a certificate
6544 request message. Print out received values in s_client. If certificate
6545 types is not set with custom values set sensible values based on
6546 supported signature algorithms.
6550 * Support for distinct client and server supported signature algorithms.
6554 * Add certificate callback. If set this is called whenever a certificate
6555 is required by client or server. An application can decide which
6556 certificate chain to present based on arbitrary criteria: for example
6557 supported signature algorithms. Add very simple example to s_server.
6558 This fixes many of the problems and restrictions of the existing client
6559 certificate callback: for example you can now clear an existing
6560 certificate and specify the whole chain.
6564 * Add new "valid_flags" field to CERT_PKEY structure which determines what
6565 the certificate can be used for (if anything). Set valid_flags field
6566 in new tls1_check_chain function. Simplify ssl_set_cert_masks which used
6567 to have similar checks in it.
6569 Add new "cert_flags" field to CERT structure and include a "strict mode".
6570 This enforces some TLS certificate requirements (such as only permitting
6571 certificate signature algorithms contained in the supported algorithms
6572 extension) which some implementations ignore: this option should be used
6573 with caution as it could cause interoperability issues.
6577 * Update and tidy signature algorithm extension processing. Work out
6578 shared signature algorithms based on preferences and peer algorithms
6579 and print them out in s_client and s_server. Abort handshake if no
6580 shared signature algorithms.
6584 * Add new functions to allow customised supported signature algorithms
6585 for SSL and SSL_CTX structures. Add options to s_client and s_server
6590 * New function SSL_certs_clear() to delete all references to certificates
6591 from an SSL structure. Before this once a certificate had been added
6592 it couldn't be removed.
6596 * Integrate hostname, email address and IP address checking with certificate
6597 verification. New verify options supporting checking in openssl utility.
6601 * Fixes and wildcard matching support to hostname and email checking
6602 functions. Add manual page.
6604 *Florian Weimer (Red Hat Product Security Team)*
6606 * New functions to check a hostname email or IP address against a
6607 certificate. Add options x509 utility to print results of checks against
6612 * Fix OCSP checking.
6614 *Rob Stradling <rob.stradling@comodo.com> and Ben Laurie*
6616 * Initial experimental support for explicitly trusted non-root CAs.
6617 OpenSSL still tries to build a complete chain to a root but if an
6618 intermediate CA has a trust setting included that is used. The first
6619 setting is used: whether to trust (e.g., -addtrust option to the x509
6624 * Add -trusted_first option which attempts to find certificates in the
6625 trusted store even if an untrusted chain is also supplied.
6629 * MIPS assembly pack updates: support for MIPS32r2 and SmartMIPS ASE,
6630 platform support for Linux and Android.
6634 * Support for linux-x32, ILP32 environment in x86_64 framework.
6638 * Experimental multi-implementation support for FIPS capable OpenSSL.
6639 When in FIPS mode the approved implementations are used as normal,
6640 when not in FIPS mode the internal unapproved versions are used instead.
6641 This means that the FIPS capable OpenSSL isn't forced to use the
6642 (often lower performance) FIPS implementations outside FIPS mode.
6646 * Transparently support X9.42 DH parameters when calling
6647 PEM_read_bio_DHparameters. This means existing applications can handle
6648 the new parameter format automatically.
6652 * Initial experimental support for X9.42 DH parameter format: mainly
6653 to support use of 'q' parameter for RFC5114 parameters.
6657 * Add DH parameters from RFC5114 including test data to dhtest.
6661 * Support for automatic EC temporary key parameter selection. If enabled
6662 the most preferred EC parameters are automatically used instead of
6663 hardcoded fixed parameters. Now a server just has to call:
6664 SSL_CTX_set_ecdh_auto(ctx, 1) and the server will automatically
6665 support ECDH and use the most appropriate parameters.
6669 * Enhance and tidy EC curve and point format TLS extension code. Use
6670 static structures instead of allocation if default values are used.
6671 New ctrls to set curves we wish to support and to retrieve shared curves.
6672 Print out shared curves in s_server. New options to s_server and s_client
6673 to set list of supported curves.
6677 * New ctrls to retrieve supported signature algorithms and
6678 supported curve values as an array of NIDs. Extend openssl utility
6679 to print out received values.
6683 * Add new APIs EC_curve_nist2nid and EC_curve_nid2nist which convert
6684 between NIDs and the more common NIST names such as "P-256". Enhance
6685 ecparam utility and ECC method to recognise the NIST names for curves.
6689 * Enhance SSL/TLS certificate chain handling to support different
6690 chains for each certificate instead of one chain in the parent SSL_CTX.
6694 * Support for fixed DH ciphersuite client authentication: where both
6695 server and client use DH certificates with common parameters.
6699 * Support for fixed DH ciphersuites: those requiring DH server
6704 * New function i2d_re_X509_tbs for re-encoding the TBS portion of
6706 Note: Related 1.0.2-beta specific macros X509_get_cert_info,
6707 X509_CINF_set_modified, X509_CINF_get_issuer, X509_CINF_get_extensions and
6708 X509_CINF_get_signature were reverted post internal team review.
6713 ### Changes between 1.0.1t and 1.0.1u [22 Sep 2016]
6715 * OCSP Status Request extension unbounded memory growth
6717 A malicious client can send an excessively large OCSP Status Request
6718 extension. If that client continually requests renegotiation, sending a
6719 large OCSP Status Request extension each time, then there will be unbounded
6720 memory growth on the server. This will eventually lead to a Denial Of
6721 Service attack through memory exhaustion. Servers with a default
6722 configuration are vulnerable even if they do not support OCSP. Builds using
6723 the "no-ocsp" build time option are not affected.
6725 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
6730 * In order to mitigate the SWEET32 attack, the DES ciphers were moved from
6733 This issue was reported to OpenSSL Karthikeyan Bhargavan and Gaetan
6739 * OOB write in MDC2_Update()
6741 An overflow can occur in MDC2_Update() either if called directly or
6742 through the EVP_DigestUpdate() function using MDC2. If an attacker
6743 is able to supply very large amounts of input data after a previous
6744 call to EVP_EncryptUpdate() with a partial block then a length check
6745 can overflow resulting in a heap corruption.
6747 The amount of data needed is comparable to SIZE_MAX which is impractical
6750 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
6755 * Malformed SHA512 ticket DoS
6757 If a server uses SHA512 for TLS session ticket HMAC it is vulnerable to a
6758 DoS attack where a malformed ticket will result in an OOB read which will
6761 The use of SHA512 in TLS session tickets is comparatively rare as it requires
6762 a custom server callback and ticket lookup mechanism.
6764 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
6769 * OOB write in BN_bn2dec()
6771 The function BN_bn2dec() does not check the return value of BN_div_word().
6772 This can cause an OOB write if an application uses this function with an
6773 overly large BIGNUM. This could be a problem if an overly large certificate
6774 or CRL is printed out from an untrusted source. TLS is not affected because
6775 record limits will reject an oversized certificate before it is parsed.
6777 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
6782 * OOB read in TS_OBJ_print_bio()
6784 The function TS_OBJ_print_bio() misuses OBJ_obj2txt(): the return value is
6785 the total length the OID text representation would use and not the amount
6786 of data written. This will result in OOB reads when large OIDs are
6789 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
6794 * Pointer arithmetic undefined behaviour
6796 Avoid some undefined pointer arithmetic
6798 A common idiom in the codebase is to check limits in the following manner:
6801 Where "p" points to some malloc'd data of SIZE bytes and
6804 "len" here could be from some externally supplied data (e.g. from a TLS
6807 The rules of C pointer arithmetic are such that "p + len" is only well
6808 defined where len <= SIZE. Therefore, the above idiom is actually
6809 undefined behaviour.
6811 For example this could cause problems if some malloc implementation
6812 provides an address for "p" such that "p + len" actually overflows for
6813 values of len that are too big and therefore p + len < limit.
6815 This issue was reported to OpenSSL by Guido Vranken
6820 * Constant time flag not preserved in DSA signing
6822 Operations in the DSA signing algorithm should run in constant time in
6823 order to avoid side channel attacks. A flaw in the OpenSSL DSA
6824 implementation means that a non-constant time codepath is followed for
6825 certain operations. This has been demonstrated through a cache-timing
6826 attack to be sufficient for an attacker to recover the private DSA key.
6828 This issue was reported by César Pereida (Aalto University), Billy Brumley
6829 (Tampere University of Technology), and Yuval Yarom (The University of
6830 Adelaide and NICTA).
6835 * DTLS buffered message DoS
6837 In a DTLS connection where handshake messages are delivered out-of-order
6838 those messages that OpenSSL is not yet ready to process will be buffered
6839 for later use. Under certain circumstances, a flaw in the logic means that
6840 those messages do not get removed from the buffer even though the handshake
6841 has been completed. An attacker could force up to approx. 15 messages to
6842 remain in the buffer when they are no longer required. These messages will
6843 be cleared when the DTLS connection is closed. The default maximum size for
6844 a message is 100k. Therefore, the attacker could force an additional 1500k
6845 to be consumed per connection. By opening many simultaneous connections an
6846 attacker could cause a DoS attack through memory exhaustion.
6848 This issue was reported to OpenSSL by Quan Luo.
6853 * DTLS replay protection DoS
6855 A flaw in the DTLS replay attack protection mechanism means that records
6856 that arrive for future epochs update the replay protection "window" before
6857 the MAC for the record has been validated. This could be exploited by an
6858 attacker by sending a record for the next epoch (which does not have to
6859 decrypt or have a valid MAC), with a very large sequence number. This means
6860 that all subsequent legitimate packets are dropped causing a denial of
6861 service for a specific DTLS connection.
6863 This issue was reported to OpenSSL by the OCAP audit team.
6868 * Certificate message OOB reads
6870 In OpenSSL 1.0.2 and earlier some missing message length checks can result
6871 in OOB reads of up to 2 bytes beyond an allocated buffer. There is a
6872 theoretical DoS risk but this has not been observed in practice on common
6875 The messages affected are client certificate, client certificate request
6876 and server certificate. As a result the attack can only be performed
6877 against a client or a server which enables client authentication.
6879 This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.)
6884 ### Changes between 1.0.1s and 1.0.1t [3 May 2016]
6886 * Prevent padding oracle in AES-NI CBC MAC check
6888 A MITM attacker can use a padding oracle attack to decrypt traffic
6889 when the connection uses an AES CBC cipher and the server support
6892 This issue was introduced as part of the fix for Lucky 13 padding
6893 attack ([CVE-2013-0169]). The padding check was rewritten to be in
6894 constant time by making sure that always the same bytes are read and
6895 compared against either the MAC or padding bytes. But it no longer
6896 checked that there was enough data to have both the MAC and padding
6899 This issue was reported by Juraj Somorovsky using TLS-Attacker.
6904 * Fix EVP_EncodeUpdate overflow
6906 An overflow can occur in the EVP_EncodeUpdate() function which is used for
6907 Base64 encoding of binary data. If an attacker is able to supply very large
6908 amounts of input data then a length check can overflow resulting in a heap
6911 Internally to OpenSSL the EVP_EncodeUpdate() function is primarily used by
6912 the `PEM_write_bio*` family of functions. These are mainly used within the
6913 OpenSSL command line applications, so any application which processes data
6914 from an untrusted source and outputs it as a PEM file should be considered
6915 vulnerable to this issue. User applications that call these APIs directly
6916 with large amounts of untrusted data may also be vulnerable.
6918 This issue was reported by Guido Vranken.
6923 * Fix EVP_EncryptUpdate overflow
6925 An overflow can occur in the EVP_EncryptUpdate() function. If an attacker
6926 is able to supply very large amounts of input data after a previous call to
6927 EVP_EncryptUpdate() with a partial block then a length check can overflow
6928 resulting in a heap corruption. Following an analysis of all OpenSSL
6929 internal usage of the EVP_EncryptUpdate() function all usage is one of two
6930 forms. The first form is where the EVP_EncryptUpdate() call is known to be
6931 the first called function after an EVP_EncryptInit(), and therefore that
6932 specific call must be safe. The second form is where the length passed to
6933 EVP_EncryptUpdate() can be seen from the code to be some small value and
6934 therefore there is no possibility of an overflow. Since all instances are
6935 one of these two forms, it is believed that there can be no overflows in
6936 internal code due to this problem. It should be noted that
6937 EVP_DecryptUpdate() can call EVP_EncryptUpdate() in certain code paths.
6938 Also EVP_CipherUpdate() is a synonym for EVP_EncryptUpdate(). All instances
6939 of these calls have also been analysed too and it is believed there are no
6940 instances in internal usage where an overflow could occur.
6942 This issue was reported by Guido Vranken.
6947 * Prevent ASN.1 BIO excessive memory allocation
6949 When ASN.1 data is read from a BIO using functions such as d2i_CMS_bio()
6950 a short invalid encoding can casuse allocation of large amounts of memory
6951 potentially consuming excessive resources or exhausting memory.
6953 Any application parsing untrusted data through d2i BIO functions is
6954 affected. The memory based functions such as d2i_X509() are *not* affected.
6955 Since the memory based functions are used by the TLS library, TLS
6956 applications are not affected.
6958 This issue was reported by Brian Carpenter.
6965 ASN1 Strings that are over 1024 bytes can cause an overread in applications
6966 using the X509_NAME_oneline() function on EBCDIC systems. This could result
6967 in arbitrary stack data being returned in the buffer.
6969 This issue was reported by Guido Vranken.
6974 * Modify behavior of ALPN to invoke callback after SNI/servername
6975 callback, such that updates to the SSL_CTX affect ALPN.
6979 * Remove LOW from the DEFAULT cipher list. This removes singles DES from the
6984 * Only remove the SSLv2 methods with the no-ssl2-method option. When the
6985 methods are enabled and ssl2 is disabled the methods return NULL.
6989 ### Changes between 1.0.1r and 1.0.1s [1 Mar 2016]
6991 * Disable weak ciphers in SSLv3 and up in default builds of OpenSSL.
6992 Builds that are not configured with "enable-weak-ssl-ciphers" will not
6993 provide any "EXPORT" or "LOW" strength ciphers.
6997 * Disable SSLv2 default build, default negotiation and weak ciphers. SSLv2
6998 is by default disabled at build-time. Builds that are not configured with
6999 "enable-ssl2" will not support SSLv2. Even if "enable-ssl2" is used,
7000 users who want to negotiate SSLv2 via the version-flexible SSLv23_method()
7001 will need to explicitly call either of:
7003 SSL_CTX_clear_options(ctx, SSL_OP_NO_SSLv2);
7005 SSL_clear_options(ssl, SSL_OP_NO_SSLv2);
7007 as appropriate. Even if either of those is used, or the application
7008 explicitly uses the version-specific SSLv2_method() or its client and
7009 server variants, SSLv2 ciphers vulnerable to exhaustive search key
7010 recovery have been removed. Specifically, the SSLv2 40-bit EXPORT
7011 ciphers, and SSLv2 56-bit DES are no longer available.
7016 * Fix a double-free in DSA code
7018 A double free bug was discovered when OpenSSL parses malformed DSA private
7019 keys and could lead to a DoS attack or memory corruption for applications
7020 that receive DSA private keys from untrusted sources. This scenario is
7023 This issue was reported to OpenSSL by Adam Langley(Google/BoringSSL) using
7029 * Disable SRP fake user seed to address a server memory leak.
7031 Add a new method SRP_VBASE_get1_by_user that handles the seed properly.
7033 SRP_VBASE_get_by_user had inconsistent memory management behaviour.
7034 In order to fix an unavoidable memory leak, SRP_VBASE_get_by_user
7035 was changed to ignore the "fake user" SRP seed, even if the seed
7038 Users should use SRP_VBASE_get1_by_user instead. Note that in
7039 SRP_VBASE_get1_by_user, caller must free the returned value. Note
7040 also that even though configuring the SRP seed attempts to hide
7041 invalid usernames by continuing the handshake with fake
7042 credentials, this behaviour is not constant time and no strong
7043 guarantees are made that the handshake is indistinguishable from
7044 that of a valid user.
7049 * Fix BN_hex2bn/BN_dec2bn NULL pointer deref/heap corruption
7051 In the BN_hex2bn function the number of hex digits is calculated using an
7052 int value `i`. Later `bn_expand` is called with a value of `i * 4`. For
7053 large values of `i` this can result in `bn_expand` not allocating any
7054 memory because `i * 4` is negative. This can leave the internal BIGNUM data
7055 field as NULL leading to a subsequent NULL ptr deref. For very large values
7056 of `i`, the calculation `i * 4` could be a positive value smaller than `i`.
7057 In this case memory is allocated to the internal BIGNUM data field, but it
7058 is insufficiently sized leading to heap corruption. A similar issue exists
7059 in BN_dec2bn. This could have security consequences if BN_hex2bn/BN_dec2bn
7060 is ever called by user applications with very large untrusted hex/dec data.
7061 This is anticipated to be a rare occurrence.
7063 All OpenSSL internal usage of these functions use data that is not expected
7064 to be untrusted, e.g. config file data or application command line
7065 arguments. If user developed applications generate config file data based
7066 on untrusted data then it is possible that this could also lead to security
7067 consequences. This is also anticipated to be rare.
7069 This issue was reported to OpenSSL by Guido Vranken.
7074 * Fix memory issues in `BIO_*printf` functions
7076 The internal `fmtstr` function used in processing a "%s" format string in
7077 the `BIO_*printf` functions could overflow while calculating the length of a
7078 string and cause an OOB read when printing very long strings.
7080 Additionally the internal `doapr_outch` function can attempt to write to an
7081 OOB memory location (at an offset from the NULL pointer) in the event of a
7082 memory allocation failure. In 1.0.2 and below this could be caused where
7083 the size of a buffer to be allocated is greater than INT_MAX. E.g. this
7084 could be in processing a very long "%s" format string. Memory leaks can
7087 The first issue may mask the second issue dependent on compiler behaviour.
7088 These problems could enable attacks where large amounts of untrusted data
7089 is passed to the `BIO_*printf` functions. If applications use these functions
7090 in this way then they could be vulnerable. OpenSSL itself uses these
7091 functions when printing out human-readable dumps of ASN.1 data. Therefore
7092 applications that print this data could be vulnerable if the data is from
7093 untrusted sources. OpenSSL command line applications could also be
7094 vulnerable where they print out ASN.1 data, or if untrusted data is passed
7095 as command line arguments.
7097 Libssl is not considered directly vulnerable. Additionally certificates etc
7098 received via remote connections via libssl are also unlikely to be able to
7099 trigger these issues because of message size limits enforced within libssl.
7101 This issue was reported to OpenSSL Guido Vranken.
7106 * Side channel attack on modular exponentiation
7108 A side-channel attack was found which makes use of cache-bank conflicts on
7109 the Intel Sandy-Bridge microarchitecture which could lead to the recovery
7110 of RSA keys. The ability to exploit this issue is limited as it relies on
7111 an attacker who has control of code in a thread running on the same
7112 hyper-threaded core as the victim thread which is performing decryptions.
7114 This issue was reported to OpenSSL by Yuval Yarom, The University of
7115 Adelaide and NICTA, Daniel Genkin, Technion and Tel Aviv University, and
7116 Nadia Heninger, University of Pennsylvania with more information at
7117 <http://cachebleed.info>.
7122 * Change the req command to generate a 2048-bit RSA/DSA key by default,
7123 if no keysize is specified with default_bits. This fixes an
7124 omission in an earlier change that changed all RSA/DSA key generation
7125 commands to use 2048 bits by default.
7129 ### Changes between 1.0.1q and 1.0.1r [28 Jan 2016]
7131 * Protection for DH small subgroup attacks
7133 As a precautionary measure the SSL_OP_SINGLE_DH_USE option has been
7134 switched on by default and cannot be disabled. This could have some
7139 * SSLv2 doesn't block disabled ciphers
7141 A malicious client can negotiate SSLv2 ciphers that have been disabled on
7142 the server and complete SSLv2 handshakes even if all SSLv2 ciphers have
7143 been disabled, provided that the SSLv2 protocol was not also disabled via
7146 This issue was reported to OpenSSL on 26th December 2015 by Nimrod Aviram
7147 and Sebastian Schinzel.
7152 * Reject DH handshakes with parameters shorter than 1024 bits.
7156 ### Changes between 1.0.1p and 1.0.1q [3 Dec 2015]
7158 * Certificate verify crash with missing PSS parameter
7160 The signature verification routines will crash with a NULL pointer
7161 dereference if presented with an ASN.1 signature using the RSA PSS
7162 algorithm and absent mask generation function parameter. Since these
7163 routines are used to verify certificate signature algorithms this can be
7164 used to crash any certificate verification operation and exploited in a
7165 DoS attack. Any application which performs certificate verification is
7166 vulnerable including OpenSSL clients and servers which enable client
7169 This issue was reported to OpenSSL by Loïc Jonas Etienne (Qnective AG).
7174 * X509_ATTRIBUTE memory leak
7176 When presented with a malformed X509_ATTRIBUTE structure OpenSSL will leak
7177 memory. This structure is used by the PKCS#7 and CMS routines so any
7178 application which reads PKCS#7 or CMS data from untrusted sources is
7179 affected. SSL/TLS is not affected.
7181 This issue was reported to OpenSSL by Adam Langley (Google/BoringSSL) using
7187 * Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs.
7188 This changes the decoding behaviour for some invalid messages,
7189 though the change is mostly in the more lenient direction, and
7190 legacy behaviour is preserved as much as possible.
7194 * In DSA_generate_parameters_ex, if the provided seed is too short,
7195 use a random seed, as already documented.
7197 *Rich Salz and Ismo Puustinen <ismo.puustinen@intel.com>*
7199 ### Changes between 1.0.1o and 1.0.1p [9 Jul 2015]
7201 * Alternate chains certificate forgery
7203 During certificate verfification, OpenSSL will attempt to find an
7204 alternative certificate chain if the first attempt to build such a chain
7205 fails. An error in the implementation of this logic can mean that an
7206 attacker could cause certain checks on untrusted certificates to be
7207 bypassed, such as the CA flag, enabling them to use a valid leaf
7208 certificate to act as a CA and "issue" an invalid certificate.
7210 This issue was reported to OpenSSL by Adam Langley/David Benjamin
7216 * Race condition handling PSK identify hint
7218 If PSK identity hints are received by a multi-threaded client then
7219 the values are wrongly updated in the parent SSL_CTX structure. This can
7220 result in a race condition potentially leading to a double free of the
7226 ### Changes between 1.0.1n and 1.0.1o [12 Jun 2015]
7228 * Fix HMAC ABI incompatibility. The previous version introduced an ABI
7229 incompatibility in the handling of HMAC. The previous ABI has now been
7232 ### Changes between 1.0.1m and 1.0.1n [11 Jun 2015]
7234 * Malformed ECParameters causes infinite loop
7236 When processing an ECParameters structure OpenSSL enters an infinite loop
7237 if the curve specified is over a specially malformed binary polynomial
7240 This can be used to perform denial of service against any
7241 system which processes public keys, certificate requests or
7242 certificates. This includes TLS clients and TLS servers with
7243 client authentication enabled.
7245 This issue was reported to OpenSSL by Joseph Barr-Pixton.
7250 * Exploitable out-of-bounds read in X509_cmp_time
7252 X509_cmp_time does not properly check the length of the ASN1_TIME
7253 string and can read a few bytes out of bounds. In addition,
7254 X509_cmp_time accepts an arbitrary number of fractional seconds in the
7257 An attacker can use this to craft malformed certificates and CRLs of
7258 various sizes and potentially cause a segmentation fault, resulting in
7259 a DoS on applications that verify certificates or CRLs. TLS clients
7260 that verify CRLs are affected. TLS clients and servers with client
7261 authentication enabled may be affected if they use custom verification
7264 This issue was reported to OpenSSL by Robert Swiecki (Google), and
7265 independently by Hanno Böck.
7270 * PKCS7 crash with missing EnvelopedContent
7272 The PKCS#7 parsing code does not handle missing inner EncryptedContent
7273 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs
7274 with missing content and trigger a NULL pointer dereference on parsing.
7276 Applications that decrypt PKCS#7 data or otherwise parse PKCS#7
7277 structures from untrusted sources are affected. OpenSSL clients and
7278 servers are not affected.
7280 This issue was reported to OpenSSL by Michal Zalewski (Google).
7285 * CMS verify infinite loop with unknown hash function
7287 When verifying a signedData message the CMS code can enter an infinite loop
7288 if presented with an unknown hash function OID. This can be used to perform
7289 denial of service against any system which verifies signedData messages using
7291 This issue was reported to OpenSSL by Johannes Bauer.
7296 * Race condition handling NewSessionTicket
7298 If a NewSessionTicket is received by a multi-threaded client when attempting to
7299 reuse a previous ticket then a race condition can occur potentially leading to
7300 a double free of the ticket data.
7305 * Reject DH handshakes with parameters shorter than 768 bits.
7307 *Kurt Roeckx and Emilia Kasper*
7309 * dhparam: generate 2048-bit parameters by default.
7311 *Kurt Roeckx and Emilia Kasper*
7313 ### Changes between 1.0.1l and 1.0.1m [19 Mar 2015]
7315 * Segmentation fault in ASN1_TYPE_cmp fix
7317 The function ASN1_TYPE_cmp will crash with an invalid read if an attempt is
7318 made to compare ASN.1 boolean types. Since ASN1_TYPE_cmp is used to check
7319 certificate signature algorithm consistency this can be used to crash any
7320 certificate verification operation and exploited in a DoS attack. Any
7321 application which performs certificate verification is vulnerable including
7322 OpenSSL clients and servers which enable client authentication.
7327 * ASN.1 structure reuse memory corruption fix
7329 Reusing a structure in ASN.1 parsing may allow an attacker to cause
7330 memory corruption via an invalid write. Such reuse is and has been
7331 strongly discouraged and is believed to be rare.
7333 Applications that parse structures containing CHOICE or ANY DEFINED BY
7334 components may be affected. Certificate parsing (d2i_X509 and related
7335 functions) are however not affected. OpenSSL clients and servers are
7341 * PKCS7 NULL pointer dereferences fix
7343 The PKCS#7 parsing code does not handle missing outer ContentInfo
7344 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with
7345 missing content and trigger a NULL pointer dereference on parsing.
7347 Applications that verify PKCS#7 signatures, decrypt PKCS#7 data or
7348 otherwise parse PKCS#7 structures from untrusted sources are
7349 affected. OpenSSL clients and servers are not affected.
7351 This issue was reported to OpenSSL by Michal Zalewski (Google).
7356 * DoS via reachable assert in SSLv2 servers fix
7358 A malicious client can trigger an OPENSSL_assert (i.e., an abort) in
7359 servers that both support SSLv2 and enable export cipher suites by sending
7360 a specially crafted SSLv2 CLIENT-MASTER-KEY message.
7362 This issue was discovered by Sean Burford (Google) and Emilia Käsper
7363 (OpenSSL development team).
7368 * Use After Free following d2i_ECPrivatekey error fix
7370 A malformed EC private key file consumed via the d2i_ECPrivateKey function
7371 could cause a use after free condition. This, in turn, could cause a double
7372 free in several private key parsing functions (such as d2i_PrivateKey
7373 or EVP_PKCS82PKEY) and could lead to a DoS attack or memory corruption
7374 for applications that receive EC private keys from untrusted
7375 sources. This scenario is considered rare.
7377 This issue was discovered by the BoringSSL project and fixed in their
7383 * X509_to_X509_REQ NULL pointer deref fix
7385 The function X509_to_X509_REQ will crash with a NULL pointer dereference if
7386 the certificate key is invalid. This function is rarely used in practice.
7388 This issue was discovered by Brian Carpenter.
7393 * Removed the export ciphers from the DEFAULT ciphers
7397 ### Changes between 1.0.1k and 1.0.1l [15 Jan 2015]
7399 * Build fixes for the Windows and OpenVMS platforms
7401 *Matt Caswell and Richard Levitte*
7403 ### Changes between 1.0.1j and 1.0.1k [8 Jan 2015]
7405 * Fix DTLS segmentation fault in dtls1_get_record. A carefully crafted DTLS
7406 message can cause a segmentation fault in OpenSSL due to a NULL pointer
7407 dereference. This could lead to a Denial Of Service attack. Thanks to
7408 Markus Stenberg of Cisco Systems, Inc. for reporting this issue.
7413 * Fix DTLS memory leak in dtls1_buffer_record. A memory leak can occur in the
7414 dtls1_buffer_record function under certain conditions. In particular this
7415 could occur if an attacker sent repeated DTLS records with the same
7416 sequence number but for the next epoch. The memory leak could be exploited
7417 by an attacker in a Denial of Service attack through memory exhaustion.
7418 Thanks to Chris Mueller for reporting this issue.
7423 * Fix issue where no-ssl3 configuration sets method to NULL. When openssl is
7424 built with the no-ssl3 option and a SSL v3 ClientHello is received the ssl
7425 method would be set to NULL which could later result in a NULL pointer
7426 dereference. Thanks to Frank Schmirler for reporting this issue.
7431 * Abort handshake if server key exchange message is omitted for ephemeral
7434 Thanks to Karthikeyan Bhargavan of the PROSECCO team at INRIA for
7435 reporting this issue.
7440 * Remove non-export ephemeral RSA code on client and server. This code
7441 violated the TLS standard by allowing the use of temporary RSA keys in
7442 non-export ciphersuites and could be used by a server to effectively
7443 downgrade the RSA key length used to a value smaller than the server
7444 certificate. Thanks for Karthikeyan Bhargavan of the PROSECCO team at
7445 INRIA or reporting this issue.
7450 * Fixed issue where DH client certificates are accepted without verification.
7451 An OpenSSL server will accept a DH certificate for client authentication
7452 without the certificate verify message. This effectively allows a client to
7453 authenticate without the use of a private key. This only affects servers
7454 which trust a client certificate authority which issues certificates
7455 containing DH keys: these are extremely rare and hardly ever encountered.
7456 Thanks for Karthikeyan Bhargavan of the PROSECCO team at INRIA or reporting
7462 * Ensure that the session ID context of an SSL is updated when its
7463 SSL_CTX is updated via SSL_set_SSL_CTX.
7465 The session ID context is typically set from the parent SSL_CTX,
7466 and can vary with the CTX.
7470 * Fix various certificate fingerprint issues.
7472 By using non-DER or invalid encodings outside the signed portion of a
7473 certificate the fingerprint can be changed without breaking the signature.
7474 Although no details of the signed portion of the certificate can be changed
7475 this can cause problems with some applications: e.g. those using the
7476 certificate fingerprint for blacklists.
7478 1. Reject signatures with non zero unused bits.
7480 If the BIT STRING containing the signature has non zero unused bits reject
7481 the signature. All current signature algorithms require zero unused bits.
7483 2. Check certificate algorithm consistency.
7485 Check the AlgorithmIdentifier inside TBS matches the one in the
7486 certificate signature. NB: this will result in signature failure
7487 errors for some broken certificates.
7489 Thanks to Konrad Kraszewski from Google for reporting this issue.
7491 3. Check DSA/ECDSA signatures use DER.
7493 Re-encode DSA/ECDSA signatures and compare with the original received
7494 signature. Return an error if there is a mismatch.
7496 This will reject various cases including garbage after signature
7497 (thanks to Antti Karjalainen and Tuomo Untinen from the Codenomicon CROSS
7498 program for discovering this case) and use of BER or invalid ASN.1 INTEGERs
7499 (negative or with leading zeroes).
7501 Further analysis was conducted and fixes were developed by Stephen Henson
7502 of the OpenSSL core team.
7508 * Correct Bignum squaring. Bignum squaring (BN_sqr) may produce incorrect
7509 results on some platforms, including x86_64. This bug occurs at random
7510 with a very low probability, and is not known to be exploitable in any
7511 way, though its exact impact is difficult to determine. Thanks to Pieter
7512 Wuille (Blockstream) who reported this issue and also suggested an initial
7513 fix. Further analysis was conducted by the OpenSSL development team and
7514 Adam Langley of Google. The final fix was developed by Andy Polyakov of
7515 the OpenSSL core team.
7520 * Do not resume sessions on the server if the negotiated protocol
7521 version does not match the session's version. Resuming with a different
7522 version, while not strictly forbidden by the RFC, is of questionable
7523 sanity and breaks all known clients.
7525 *David Benjamin, Emilia Käsper*
7527 * Tighten handling of the ChangeCipherSpec (CCS) message: reject
7528 early CCS messages during renegotiation. (Note that because
7529 renegotiation is encrypted, this early CCS was not exploitable.)
7533 * Tighten client-side session ticket handling during renegotiation:
7534 ensure that the client only accepts a session ticket if the server sends
7535 the extension anew in the ServerHello. Previously, a TLS client would
7536 reuse the old extension state and thus accept a session ticket if one was
7537 announced in the initial ServerHello.
7539 Similarly, ensure that the client requires a session ticket if one
7540 was advertised in the ServerHello. Previously, a TLS client would
7541 ignore a missing NewSessionTicket message.
7545 ### Changes between 1.0.1i and 1.0.1j [15 Oct 2014]
7549 A flaw in the DTLS SRTP extension parsing code allows an attacker, who
7550 sends a carefully crafted handshake message, to cause OpenSSL to fail
7551 to free up to 64k of memory causing a memory leak. This could be
7552 exploited in a Denial Of Service attack. This issue affects OpenSSL
7553 1.0.1 server implementations for both SSL/TLS and DTLS regardless of
7554 whether SRTP is used or configured. Implementations of OpenSSL that
7555 have been compiled with OPENSSL_NO_SRTP defined are not affected.
7557 The fix was developed by the OpenSSL team.
7562 * Session Ticket Memory Leak.
7564 When an OpenSSL SSL/TLS/DTLS server receives a session ticket the
7565 integrity of that ticket is first verified. In the event of a session
7566 ticket integrity check failing, OpenSSL will fail to free memory
7567 causing a memory leak. By sending a large number of invalid session
7568 tickets an attacker could exploit this issue in a Denial Of Service
7574 * Build option no-ssl3 is incomplete.
7576 When OpenSSL is configured with "no-ssl3" as a build option, servers
7577 could accept and complete an SSL 3.0 handshake, and clients could be
7578 configured to send them.
7581 *Akamai and the OpenSSL team*
7583 * Add support for TLS_FALLBACK_SCSV.
7584 Client applications doing fallback retries should call
7585 SSL_set_mode(s, SSL_MODE_SEND_FALLBACK_SCSV).
7588 *Adam Langley, Bodo Moeller*
7590 * Add additional DigestInfo checks.
7592 Re-encode DigestInto in DER and check against the original when
7593 verifying RSA signature: this will reject any improperly encoded
7594 DigestInfo structures.
7596 Note: this is a precautionary measure and no attacks are currently known.
7600 ### Changes between 1.0.1h and 1.0.1i [6 Aug 2014]
7602 * Fix SRP buffer overrun vulnerability. Invalid parameters passed to the
7603 SRP code can be overrun an internal buffer. Add sanity check that
7604 g, A, B < N to SRP code.
7606 Thanks to Sean Devlin and Watson Ladd of Cryptography Services, NCC
7607 Group for discovering this issue.
7612 * A flaw in the OpenSSL SSL/TLS server code causes the server to negotiate
7613 TLS 1.0 instead of higher protocol versions when the ClientHello message
7614 is badly fragmented. This allows a man-in-the-middle attacker to force a
7615 downgrade to TLS 1.0 even if both the server and the client support a
7616 higher protocol version, by modifying the client's TLS records.
7618 Thanks to David Benjamin and Adam Langley (Google) for discovering and
7619 researching this issue.
7624 * OpenSSL DTLS clients enabling anonymous (EC)DH ciphersuites are subject
7625 to a denial of service attack. A malicious server can crash the client
7626 with a null pointer dereference (read) by specifying an anonymous (EC)DH
7627 ciphersuite and sending carefully crafted handshake messages.
7629 Thanks to Felix Gröbert (Google) for discovering and researching this
7635 * By sending carefully crafted DTLS packets an attacker could cause openssl
7636 to leak memory. This can be exploited through a Denial of Service attack.
7637 Thanks to Adam Langley for discovering and researching this issue.
7642 * An attacker can force openssl to consume large amounts of memory whilst
7643 processing DTLS handshake messages. This can be exploited through a
7644 Denial of Service attack.
7645 Thanks to Adam Langley for discovering and researching this issue.
7650 * An attacker can force an error condition which causes openssl to crash
7651 whilst processing DTLS packets due to memory being freed twice. This
7652 can be exploited through a Denial of Service attack.
7653 Thanks to Adam Langley and Wan-Teh Chang for discovering and researching
7659 * If a multithreaded client connects to a malicious server using a resumed
7660 session and the server sends an ec point format extension it could write
7661 up to 255 bytes to freed memory.
7663 Thanks to Gabor Tyukasz (LogMeIn Inc) for discovering and researching this
7669 * A malicious server can crash an OpenSSL client with a null pointer
7670 dereference (read) by specifying an SRP ciphersuite even though it was not
7671 properly negotiated with the client. This can be exploited through a
7672 Denial of Service attack.
7674 Thanks to Joonas Kuorilehto and Riku Hietamäki (Codenomicon) for
7675 discovering and researching this issue.
7680 * A flaw in OBJ_obj2txt may cause pretty printing functions such as
7681 X509_name_oneline, X509_name_print_ex et al. to leak some information
7682 from the stack. Applications may be affected if they echo pretty printing
7683 output to the attacker.
7685 Thanks to Ivan Fratric (Google) for discovering this issue.
7688 *Emilia Käsper, and Steve Henson*
7690 * Fix ec_GFp_simple_points_make_affine (thus, EC_POINTs_mul etc.)
7691 for corner cases. (Certain input points at infinity could lead to
7692 bogus results, with non-infinity inputs mapped to infinity too.)
7696 ### Changes between 1.0.1g and 1.0.1h [5 Jun 2014]
7698 * Fix for SSL/TLS MITM flaw. An attacker using a carefully crafted
7699 handshake can force the use of weak keying material in OpenSSL
7700 SSL/TLS clients and servers.
7702 Thanks to KIKUCHI Masashi (Lepidum Co. Ltd.) for discovering and
7703 researching this issue. ([CVE-2014-0224])
7705 *KIKUCHI Masashi, Steve Henson*
7707 * Fix DTLS recursion flaw. By sending an invalid DTLS handshake to an
7708 OpenSSL DTLS client the code can be made to recurse eventually crashing
7711 Thanks to Imre Rad (Search-Lab Ltd.) for discovering this issue.
7714 *Imre Rad, Steve Henson*
7716 * Fix DTLS invalid fragment vulnerability. A buffer overrun attack can
7717 be triggered by sending invalid DTLS fragments to an OpenSSL DTLS
7718 client or server. This is potentially exploitable to run arbitrary
7719 code on a vulnerable client or server.
7721 Thanks to Jüri Aedla for reporting this issue. ([CVE-2014-0195])
7723 *Jüri Aedla, Steve Henson*
7725 * Fix bug in TLS code where clients enable anonymous ECDH ciphersuites
7726 are subject to a denial of service attack.
7728 Thanks to Felix Gröbert and Ivan Fratric at Google for discovering
7729 this issue. ([CVE-2014-3470])
7731 *Felix Gröbert, Ivan Fratric, Steve Henson*
7733 * Harmonize version and its documentation. -f flag is used to display
7736 *mancha <mancha1@zoho.com>*
7738 * Fix eckey_priv_encode so it immediately returns an error upon a failure
7739 in i2d_ECPrivateKey.
7741 *mancha <mancha1@zoho.com>*
7743 * Fix some double frees. These are not thought to be exploitable.
7745 *mancha <mancha1@zoho.com>*
7747 ### Changes between 1.0.1f and 1.0.1g [7 Apr 2014]
7749 * A missing bounds check in the handling of the TLS heartbeat extension
7750 can be used to reveal up to 64k of memory to a connected client or
7753 Thanks for Neel Mehta of Google Security for discovering this bug and to
7754 Adam Langley <agl@chromium.org> and Bodo Moeller <bmoeller@acm.org> for
7755 preparing the fix ([CVE-2014-0160])
7757 *Adam Langley, Bodo Moeller*
7759 * Fix for the attack described in the paper "Recovering OpenSSL
7760 ECDSA Nonces Using the FLUSH+RELOAD Cache Side-channel Attack"
7761 by Yuval Yarom and Naomi Benger. Details can be obtained from:
7762 <http://eprint.iacr.org/2014/140>
7764 Thanks to Yuval Yarom and Naomi Benger for discovering this
7765 flaw and to Yuval Yarom for supplying a fix ([CVE-2014-0076])
7767 *Yuval Yarom and Naomi Benger*
7769 * TLS pad extension: draft-agl-tls-padding-03
7771 Workaround for the "TLS hang bug" (see FAQ and PR#2771): if the
7772 TLS client Hello record length value would otherwise be > 255 and
7773 less that 512 pad with a dummy extension containing zeroes so it
7774 is at least 512 bytes long.
7776 *Adam Langley, Steve Henson*
7778 ### Changes between 1.0.1e and 1.0.1f [6 Jan 2014]
7780 * Fix for TLS record tampering bug. A carefully crafted invalid
7781 handshake could crash OpenSSL with a NULL pointer exception.
7782 Thanks to Anton Johansson for reporting this issues.
7785 * Keep original DTLS digest and encryption contexts in retransmission
7786 structures so we can use the previous session parameters if they need
7787 to be resent. ([CVE-2013-6450])
7791 * Add option SSL_OP_SAFARI_ECDHE_ECDSA_BUG (part of SSL_OP_ALL) which
7792 avoids preferring ECDHE-ECDSA ciphers when the client appears to be
7793 Safari on OS X. Safari on OS X 10.8..10.8.3 advertises support for
7794 several ECDHE-ECDSA ciphers, but fails to negotiate them. The bug
7795 is fixed in OS X 10.8.4, but Apple have ruled out both hot fixing
7796 10.8..10.8.3 and forcing users to upgrade to 10.8.4 or newer.
7798 *Rob Stradling, Adam Langley*
7800 ### Changes between 1.0.1d and 1.0.1e [11 Feb 2013]
7802 * Correct fix for CVE-2013-0169. The original didn't work on AES-NI
7803 supporting platforms or when small records were transferred.
7805 *Andy Polyakov, Steve Henson*
7807 ### Changes between 1.0.1c and 1.0.1d [5 Feb 2013]
7809 * Make the decoding of SSLv3, TLS and DTLS CBC records constant time.
7811 This addresses the flaw in CBC record processing discovered by
7812 Nadhem Alfardan and Kenny Paterson. Details of this attack can be found
7813 at: <http://www.isg.rhul.ac.uk/tls/>
7815 Thanks go to Nadhem Alfardan and Kenny Paterson of the Information
7816 Security Group at Royal Holloway, University of London
7817 (www.isg.rhul.ac.uk) for discovering this flaw and Adam Langley and
7818 Emilia Käsper for the initial patch.
7821 *Emilia Käsper, Adam Langley, Ben Laurie, Andy Polyakov, Steve Henson*
7823 * Fix flaw in AESNI handling of TLS 1.2 and 1.1 records for CBC mode
7824 ciphersuites which can be exploited in a denial of service attack.
7825 Thanks go to and to Adam Langley <agl@chromium.org> for discovering
7826 and detecting this bug and to Wolfgang Ettlinger
7827 <wolfgang.ettlinger@gmail.com> for independently discovering this issue.
7832 * Return an error when checking OCSP signatures when key is NULL.
7833 This fixes a DoS attack. ([CVE-2013-0166])
7837 * Make openssl verify return errors.
7839 *Chris Palmer <palmer@google.com> and Ben Laurie*
7841 * Call OCSP Stapling callback after ciphersuite has been chosen, so
7842 the right response is stapled. Also change SSL_get_certificate()
7843 so it returns the certificate actually sent.
7844 See <http://rt.openssl.org/Ticket/Display.html?id=2836>.
7846 *Rob Stradling <rob.stradling@comodo.com>*
7848 * Fix possible deadlock when decoding public keys.
7852 * Don't use TLS 1.0 record version number in initial client hello
7857 ### Changes between 1.0.1b and 1.0.1c [10 May 2012]
7859 * Sanity check record length before skipping explicit IV in TLS
7860 1.2, 1.1 and DTLS to fix DoS attack.
7862 Thanks to Codenomicon for discovering this issue using Fuzz-o-Matic
7863 fuzzing as a service testing platform.
7868 * Initialise tkeylen properly when encrypting CMS messages.
7869 Thanks to Solar Designer of Openwall for reporting this issue.
7873 * In FIPS mode don't try to use composite ciphers as they are not
7878 ### Changes between 1.0.1a and 1.0.1b [26 Apr 2012]
7880 * OpenSSL 1.0.0 sets SSL_OP_ALL to 0x80000FFFL and OpenSSL 1.0.1 and
7881 1.0.1a set SSL_OP_NO_TLSv1_1 to 0x00000400L which would unfortunately
7882 mean any application compiled against OpenSSL 1.0.0 headers setting
7883 SSL_OP_ALL would also set SSL_OP_NO_TLSv1_1, unintentionally disabling
7884 TLS 1.1 also. Fix this by changing the value of SSL_OP_NO_TLSv1_1 to
7885 0x10000000L Any application which was previously compiled against
7886 OpenSSL 1.0.1 or 1.0.1a headers and which cares about SSL_OP_NO_TLSv1_1
7887 will need to be recompiled as a result. Letting be results in
7888 inability to disable specifically TLS 1.1 and in client context,
7889 in unlike event, limit maximum offered version to TLS 1.0 [see below].
7893 * In order to ensure interoperability SSL_OP_NO_protocolX does not
7894 disable just protocol X, but all protocols above X *if* there are
7895 protocols *below* X still enabled. In more practical terms it means
7896 that if application wants to disable TLS1.0 in favor of TLS1.1 and
7897 above, it's not sufficient to pass `SSL_OP_NO_TLSv1`, one has to pass
7898 `SSL_OP_NO_TLSv1|SSL_OP_NO_SSLv3|SSL_OP_NO_SSLv2`. This applies to
7903 ### Changes between 1.0.1 and 1.0.1a [19 Apr 2012]
7905 * Check for potentially exploitable overflows in asn1_d2i_read_bio
7906 BUF_mem_grow and BUF_mem_grow_clean. Refuse attempts to shrink buffer
7907 in CRYPTO_realloc_clean.
7909 Thanks to Tavis Ormandy, Google Security Team, for discovering this
7910 issue and to Adam Langley <agl@chromium.org> for fixing it.
7913 *Adam Langley (Google), Tavis Ormandy, Google Security Team*
7915 * Don't allow TLS 1.2 SHA-256 ciphersuites in TLS 1.0, 1.1 connections.
7919 * Workarounds for some broken servers that "hang" if a client hello
7920 record length exceeds 255 bytes.
7922 1. Do not use record version number > TLS 1.0 in initial client
7923 hello: some (but not all) hanging servers will now work.
7924 2. If we set OPENSSL_MAX_TLS1_2_CIPHER_LENGTH this will truncate
7925 the number of ciphers sent in the client hello. This should be
7926 set to an even number, such as 50, for example by passing:
7927 -DOPENSSL_MAX_TLS1_2_CIPHER_LENGTH=50 to config or Configure.
7928 Most broken servers should now work.
7929 3. If all else fails setting OPENSSL_NO_TLS1_2_CLIENT will disable
7930 TLS 1.2 client support entirely.
7934 * Fix SEGV in Vector Permutation AES module observed in OpenSSH.
7938 ### Changes between 1.0.0h and 1.0.1 [14 Mar 2012]
7940 * Add compatibility with old MDC2 signatures which use an ASN1 OCTET
7941 STRING form instead of a DigestInfo.
7945 * The format used for MDC2 RSA signatures is inconsistent between EVP
7946 and the RSA_sign/RSA_verify functions. This was made more apparent when
7947 OpenSSL used RSA_sign/RSA_verify for some RSA signatures in particular
7948 those which went through EVP_PKEY_METHOD in 1.0.0 and later. Detect
7949 the correct format in RSA_verify so both forms transparently work.
7953 * Some servers which support TLS 1.0 can choke if we initially indicate
7954 support for TLS 1.2 and later renegotiate using TLS 1.0 in the RSA
7955 encrypted premaster secret. As a workaround use the maximum permitted
7956 client version in client hello, this should keep such servers happy
7957 and still work with previous versions of OpenSSL.
7961 * Add support for TLS/DTLS heartbeats.
7963 *Robin Seggelmann <seggelmann@fh-muenster.de>*
7965 * Add support for SCTP.
7967 *Robin Seggelmann <seggelmann@fh-muenster.de>*
7969 * Improved PRNG seeding for VOS.
7971 *Paul Green <Paul.Green@stratus.com>*
7973 * Extensive assembler packs updates, most notably:
7975 - x86[_64]: AES-NI, PCLMULQDQ, RDRAND support;
7976 - x86[_64]: SSSE3 support (SHA1, vector-permutation AES);
7977 - x86_64: bit-sliced AES implementation;
7978 - ARM: NEON support, contemporary platforms optimizations;
7979 - s390x: z196 support;
7980 - `*`: GHASH and GF(2^m) multiplication implementations;
7984 * Make TLS-SRP code conformant with RFC 5054 API cleanup
7985 (removal of unnecessary code)
7987 *Peter Sylvester <peter.sylvester@edelweb.fr>*
7989 * Add TLS key material exporter from RFC 5705.
7993 * Add DTLS-SRTP negotiation from RFC 5764.
7997 * Add Next Protocol Negotiation,
7998 <http://tools.ietf.org/html/draft-agl-tls-nextprotoneg-00>. Can be
7999 disabled with a no-npn flag to config or Configure. Code donated
8002 *Adam Langley <agl@google.com> and Ben Laurie*
8004 * Add optional 64-bit optimized implementations of elliptic curves NIST-P224,
8005 NIST-P256, NIST-P521, with constant-time single point multiplication on
8006 typical inputs. Compiler support for the nonstandard type `__uint128_t` is
8007 required to use this (present in gcc 4.4 and later, for 64-bit builds).
8008 Code made available under Apache License version 2.0.
8010 Specify "enable-ec_nistp_64_gcc_128" on the Configure (or config) command
8011 line to include this in your build of OpenSSL, and run "make depend" (or
8012 "make update"). This enables the following EC_METHODs:
8014 EC_GFp_nistp224_method()
8015 EC_GFp_nistp256_method()
8016 EC_GFp_nistp521_method()
8018 EC_GROUP_new_by_curve_name() will automatically use these (while
8019 EC_GROUP_new_curve_GFp() currently prefers the more flexible
8022 *Emilia Käsper, Adam Langley, Bodo Moeller (Google)*
8024 * Use type ossl_ssize_t instead of ssize_t which isn't available on
8025 all platforms. Move ssize_t definition from e_os.h to the public
8026 header file e_os2.h as it now appears in public header file cms.h
8030 * New -sigopt option to the ca, req and x509 utilities. Additional
8031 signature parameters can be passed using this option and in
8036 * Add RSA PSS signing function. This will generate and set the
8037 appropriate AlgorithmIdentifiers for PSS based on those in the
8038 corresponding EVP_MD_CTX structure. No application support yet.
8042 * Support for companion algorithm specific ASN1 signing routines.
8043 New function ASN1_item_sign_ctx() signs a pre-initialised
8044 EVP_MD_CTX structure and sets AlgorithmIdentifiers based on
8045 the appropriate parameters.
8049 * Add new algorithm specific ASN1 verification initialisation function
8050 to EVP_PKEY_ASN1_METHOD: this is not in EVP_PKEY_METHOD since the ASN1
8051 handling will be the same no matter what EVP_PKEY_METHOD is used.
8052 Add a PSS handler to support verification of PSS signatures: checked
8053 against a number of sample certificates.
8057 * Add signature printing for PSS. Add PSS OIDs.
8059 *Steve Henson, Martin Kaiser <lists@kaiser.cx>*
8061 * Add algorithm specific signature printing. An individual ASN1 method
8062 can now print out signatures instead of the standard hex dump.
8064 More complex signatures (e.g. PSS) can print out more meaningful
8065 information. Include DSA version that prints out the signature
8070 * Password based recipient info support for CMS library: implementing
8075 * Split password based encryption into PBES2 and PBKDF2 functions. This
8076 neatly separates the code into cipher and PBE sections and is required
8077 for some algorithms that split PBES2 into separate pieces (such as
8078 password based CMS).
8082 * Session-handling fixes:
8083 - Fix handling of connections that are resuming with a session ID,
8084 but also support Session Tickets.
8085 - Fix a bug that suppressed issuing of a new ticket if the client
8086 presented a ticket with an expired session.
8087 - Try to set the ticket lifetime hint to something reasonable.
8088 - Make tickets shorter by excluding irrelevant information.
8089 - On the client side, don't ignore renewed tickets.
8091 *Adam Langley, Bodo Moeller (Google)*
8093 * Fix PSK session representation.
8097 * Add RC4-MD5 and AESNI-SHA1 "stitched" implementations.
8099 This work was sponsored by Intel.
8103 * Add GCM support to TLS library. Some custom code is needed to split
8104 the IV between the fixed (from PRF) and explicit (from TLS record)
8105 portions. This adds all GCM ciphersuites supported by RFC5288 and
8106 RFC5289. Generalise some `AES*` cipherstrings to include GCM and
8107 add a special AESGCM string for GCM only.
8111 * Expand range of ctrls for AES GCM. Permit setting invocation
8112 field on decrypt and retrieval of invocation field only on encrypt.
8116 * Add HMAC ECC ciphersuites from RFC5289. Include SHA384 PRF support.
8117 As required by RFC5289 these ciphersuites cannot be used if for
8118 versions of TLS earlier than 1.2.
8122 * For FIPS capable OpenSSL interpret a NULL default public key method
8123 as unset and return the appropriate default but do *not* set the default.
8124 This means we can return the appropriate method in applications that
8125 switch between FIPS and non-FIPS modes.
8129 * Redirect HMAC and CMAC operations to FIPS module in FIPS mode. If an
8130 ENGINE is used then we cannot handle that in the FIPS module so we
8131 keep original code iff non-FIPS operations are allowed.
8135 * Add -attime option to openssl utilities.
8137 *Peter Eckersley <pde@eff.org>, Ben Laurie and Steve Henson*
8139 * Redirect DSA and DH operations to FIPS module in FIPS mode.
8143 * Redirect ECDSA and ECDH operations to FIPS module in FIPS mode. Also use
8144 FIPS EC methods unconditionally for now.
8148 * New build option no-ec2m to disable characteristic 2 code.
8152 * Backport libcrypto audit of return value checking from 1.1.0-dev; not
8153 all cases can be covered as some introduce binary incompatibilities.
8157 * Redirect RSA operations to FIPS module including keygen,
8158 encrypt, decrypt, sign and verify. Block use of non FIPS RSA methods.
8162 * Add similar low-level API blocking to ciphers.
8166 * low-level digest APIs are not approved in FIPS mode: any attempt
8167 to use these will cause a fatal error. Applications that *really* want
8168 to use them can use the `private_*` version instead.
8172 * Redirect cipher operations to FIPS module for FIPS builds.
8176 * Redirect digest operations to FIPS module for FIPS builds.
8180 * Update build system to add "fips" flag which will link in fipscanister.o
8181 for static and shared library builds embedding a signature if needed.
8185 * Output TLS supported curves in preference order instead of numerical
8186 order. This is currently hardcoded for the highest order curves first.
8187 This should be configurable so applications can judge speed vs strength.
8191 * Add TLS v1.2 server support for client authentication.
8195 * Add support for FIPS mode in ssl library: disable SSLv3, non-FIPS ciphers
8200 * Functions FIPS_mode_set() and FIPS_mode() which call the underlying
8201 FIPS modules versions.
8205 * Add TLS v1.2 client side support for client authentication. Keep cache
8206 of handshake records longer as we don't know the hash algorithm to use
8207 until after the certificate request message is received.
8211 * Initial TLS v1.2 client support. Add a default signature algorithms
8212 extension including all the algorithms we support. Parse new signature
8213 format in client key exchange. Relax some ECC signing restrictions for
8214 TLS v1.2 as indicated in RFC5246.
8218 * Add server support for TLS v1.2 signature algorithms extension. Switch
8219 to new signature format when needed using client digest preference.
8220 All server ciphersuites should now work correctly in TLS v1.2. No client
8221 support yet and no support for client certificates.
8225 * Initial TLS v1.2 support. Add new SHA256 digest to ssl code, switch
8226 to SHA256 for PRF when using TLS v1.2 and later. Add new SHA256 based
8227 ciphersuites. At present only RSA key exchange ciphersuites work with
8228 TLS v1.2. Add new option for TLS v1.2 replacing the old and obsolete
8229 SSL_OP_PKCS1_CHECK flags with SSL_OP_NO_TLSv1_2. New TLSv1.2 methods
8230 and version checking.
8234 * New option OPENSSL_NO_SSL_INTERN. If an application can be compiled
8235 with this defined it will not be affected by any changes to ssl internal
8236 structures. Add several utility functions to allow openssl application
8237 to work with OPENSSL_NO_SSL_INTERN defined.
8241 * A long standing patch to add support for SRP from EdelWeb (Peter
8242 Sylvester and Christophe Renou) was integrated.
8243 *Christophe Renou <christophe.renou@edelweb.fr>, Peter Sylvester
8244 <peter.sylvester@edelweb.fr>, Tom Wu <tjw@cs.stanford.edu>, and
8247 * Add functions to copy EVP_PKEY_METHOD and retrieve flags and id.
8251 * Permit abbreviated handshakes when renegotiating using the function
8252 SSL_renegotiate_abbreviated().
8254 *Robin Seggelmann <seggelmann@fh-muenster.de>*
8256 * Add call to ENGINE_register_all_complete() to
8257 ENGINE_load_builtin_engines(), so some implementations get used
8258 automatically instead of needing explicit application support.
8262 * Add support for TLS key exporter as described in RFC5705.
8264 *Robin Seggelmann <seggelmann@fh-muenster.de>, Steve Henson*
8266 * Initial TLSv1.1 support. Since TLSv1.1 is very similar to TLS v1.0 only
8267 a few changes are required:
8269 Add SSL_OP_NO_TLSv1_1 flag.
8270 Add TLSv1_1 methods.
8271 Update version checking logic to handle version 1.1.
8272 Add explicit IV handling (ported from DTLS code).
8273 Add command line options to s_client/s_server.
8280 ### Changes between 1.0.0s and 1.0.0t [3 Dec 2015]
8282 * X509_ATTRIBUTE memory leak
8284 When presented with a malformed X509_ATTRIBUTE structure OpenSSL will leak
8285 memory. This structure is used by the PKCS#7 and CMS routines so any
8286 application which reads PKCS#7 or CMS data from untrusted sources is
8287 affected. SSL/TLS is not affected.
8289 This issue was reported to OpenSSL by Adam Langley (Google/BoringSSL) using
8295 * Race condition handling PSK identify hint
8297 If PSK identity hints are received by a multi-threaded client then
8298 the values are wrongly updated in the parent SSL_CTX structure. This can
8299 result in a race condition potentially leading to a double free of the
8305 ### Changes between 1.0.0r and 1.0.0s [11 Jun 2015]
8307 * Malformed ECParameters causes infinite loop
8309 When processing an ECParameters structure OpenSSL enters an infinite loop
8310 if the curve specified is over a specially malformed binary polynomial
8313 This can be used to perform denial of service against any
8314 system which processes public keys, certificate requests or
8315 certificates. This includes TLS clients and TLS servers with
8316 client authentication enabled.
8318 This issue was reported to OpenSSL by Joseph Barr-Pixton.
8323 * Exploitable out-of-bounds read in X509_cmp_time
8325 X509_cmp_time does not properly check the length of the ASN1_TIME
8326 string and can read a few bytes out of bounds. In addition,
8327 X509_cmp_time accepts an arbitrary number of fractional seconds in the
8330 An attacker can use this to craft malformed certificates and CRLs of
8331 various sizes and potentially cause a segmentation fault, resulting in
8332 a DoS on applications that verify certificates or CRLs. TLS clients
8333 that verify CRLs are affected. TLS clients and servers with client
8334 authentication enabled may be affected if they use custom verification
8337 This issue was reported to OpenSSL by Robert Swiecki (Google), and
8338 independently by Hanno Böck.
8343 * PKCS7 crash with missing EnvelopedContent
8345 The PKCS#7 parsing code does not handle missing inner EncryptedContent
8346 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs
8347 with missing content and trigger a NULL pointer dereference on parsing.
8349 Applications that decrypt PKCS#7 data or otherwise parse PKCS#7
8350 structures from untrusted sources are affected. OpenSSL clients and
8351 servers are not affected.
8353 This issue was reported to OpenSSL by Michal Zalewski (Google).
8358 * CMS verify infinite loop with unknown hash function
8360 When verifying a signedData message the CMS code can enter an infinite loop
8361 if presented with an unknown hash function OID. This can be used to perform
8362 denial of service against any system which verifies signedData messages using
8364 This issue was reported to OpenSSL by Johannes Bauer.
8369 * Race condition handling NewSessionTicket
8371 If a NewSessionTicket is received by a multi-threaded client when attempting to
8372 reuse a previous ticket then a race condition can occur potentially leading to
8373 a double free of the ticket data.
8378 ### Changes between 1.0.0q and 1.0.0r [19 Mar 2015]
8380 * Segmentation fault in ASN1_TYPE_cmp fix
8382 The function ASN1_TYPE_cmp will crash with an invalid read if an attempt is
8383 made to compare ASN.1 boolean types. Since ASN1_TYPE_cmp is used to check
8384 certificate signature algorithm consistency this can be used to crash any
8385 certificate verification operation and exploited in a DoS attack. Any
8386 application which performs certificate verification is vulnerable including
8387 OpenSSL clients and servers which enable client authentication.
8392 * ASN.1 structure reuse memory corruption fix
8394 Reusing a structure in ASN.1 parsing may allow an attacker to cause
8395 memory corruption via an invalid write. Such reuse is and has been
8396 strongly discouraged and is believed to be rare.
8398 Applications that parse structures containing CHOICE or ANY DEFINED BY
8399 components may be affected. Certificate parsing (d2i_X509 and related
8400 functions) are however not affected. OpenSSL clients and servers are
8406 * PKCS7 NULL pointer dereferences fix
8408 The PKCS#7 parsing code does not handle missing outer ContentInfo
8409 correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with
8410 missing content and trigger a NULL pointer dereference on parsing.
8412 Applications that verify PKCS#7 signatures, decrypt PKCS#7 data or
8413 otherwise parse PKCS#7 structures from untrusted sources are
8414 affected. OpenSSL clients and servers are not affected.
8416 This issue was reported to OpenSSL by Michal Zalewski (Google).
8421 * DoS via reachable assert in SSLv2 servers fix
8423 A malicious client can trigger an OPENSSL_assert (i.e., an abort) in
8424 servers that both support SSLv2 and enable export cipher suites by sending
8425 a specially crafted SSLv2 CLIENT-MASTER-KEY message.
8427 This issue was discovered by Sean Burford (Google) and Emilia Käsper
8428 (OpenSSL development team).
8433 * Use After Free following d2i_ECPrivatekey error fix
8435 A malformed EC private key file consumed via the d2i_ECPrivateKey function
8436 could cause a use after free condition. This, in turn, could cause a double
8437 free in several private key parsing functions (such as d2i_PrivateKey
8438 or EVP_PKCS82PKEY) and could lead to a DoS attack or memory corruption
8439 for applications that receive EC private keys from untrusted
8440 sources. This scenario is considered rare.
8442 This issue was discovered by the BoringSSL project and fixed in their
8448 * X509_to_X509_REQ NULL pointer deref fix
8450 The function X509_to_X509_REQ will crash with a NULL pointer dereference if
8451 the certificate key is invalid. This function is rarely used in practice.
8453 This issue was discovered by Brian Carpenter.
8458 * Removed the export ciphers from the DEFAULT ciphers
8462 ### Changes between 1.0.0p and 1.0.0q [15 Jan 2015]
8464 * Build fixes for the Windows and OpenVMS platforms
8466 *Matt Caswell and Richard Levitte*
8468 ### Changes between 1.0.0o and 1.0.0p [8 Jan 2015]
8470 * Fix DTLS segmentation fault in dtls1_get_record. A carefully crafted DTLS
8471 message can cause a segmentation fault in OpenSSL due to a NULL pointer
8472 dereference. This could lead to a Denial Of Service attack. Thanks to
8473 Markus Stenberg of Cisco Systems, Inc. for reporting this issue.
8478 * Fix DTLS memory leak in dtls1_buffer_record. A memory leak can occur in the
8479 dtls1_buffer_record function under certain conditions. In particular this
8480 could occur if an attacker sent repeated DTLS records with the same
8481 sequence number but for the next epoch. The memory leak could be exploited
8482 by an attacker in a Denial of Service attack through memory exhaustion.
8483 Thanks to Chris Mueller for reporting this issue.
8488 * Fix issue where no-ssl3 configuration sets method to NULL. When openssl is
8489 built with the no-ssl3 option and a SSL v3 ClientHello is received the ssl
8490 method would be set to NULL which could later result in a NULL pointer
8491 dereference. Thanks to Frank Schmirler for reporting this issue.
8496 * Abort handshake if server key exchange message is omitted for ephemeral
8499 Thanks to Karthikeyan Bhargavan of the PROSECCO team at INRIA for
8500 reporting this issue.
8505 * Remove non-export ephemeral RSA code on client and server. This code
8506 violated the TLS standard by allowing the use of temporary RSA keys in
8507 non-export ciphersuites and could be used by a server to effectively
8508 downgrade the RSA key length used to a value smaller than the server
8509 certificate. Thanks for Karthikeyan Bhargavan of the PROSECCO team at
8510 INRIA or reporting this issue.
8515 * Fixed issue where DH client certificates are accepted without verification.
8516 An OpenSSL server will accept a DH certificate for client authentication
8517 without the certificate verify message. This effectively allows a client to
8518 authenticate without the use of a private key. This only affects servers
8519 which trust a client certificate authority which issues certificates
8520 containing DH keys: these are extremely rare and hardly ever encountered.
8521 Thanks for Karthikeyan Bhargavan of the PROSECCO team at INRIA or reporting
8527 * Correct Bignum squaring. Bignum squaring (BN_sqr) may produce incorrect
8528 results on some platforms, including x86_64. This bug occurs at random
8529 with a very low probability, and is not known to be exploitable in any
8530 way, though its exact impact is difficult to determine. Thanks to Pieter
8531 Wuille (Blockstream) who reported this issue and also suggested an initial
8532 fix. Further analysis was conducted by the OpenSSL development team and
8533 Adam Langley of Google. The final fix was developed by Andy Polyakov of
8534 the OpenSSL core team.
8539 * Fix various certificate fingerprint issues.
8541 By using non-DER or invalid encodings outside the signed portion of a
8542 certificate the fingerprint can be changed without breaking the signature.
8543 Although no details of the signed portion of the certificate can be changed
8544 this can cause problems with some applications: e.g. those using the
8545 certificate fingerprint for blacklists.
8547 1. Reject signatures with non zero unused bits.
8549 If the BIT STRING containing the signature has non zero unused bits reject
8550 the signature. All current signature algorithms require zero unused bits.
8552 2. Check certificate algorithm consistency.
8554 Check the AlgorithmIdentifier inside TBS matches the one in the
8555 certificate signature. NB: this will result in signature failure
8556 errors for some broken certificates.
8558 Thanks to Konrad Kraszewski from Google for reporting this issue.
8560 3. Check DSA/ECDSA signatures use DER.
8562 Reencode DSA/ECDSA signatures and compare with the original received
8563 signature. Return an error if there is a mismatch.
8565 This will reject various cases including garbage after signature
8566 (thanks to Antti Karjalainen and Tuomo Untinen from the Codenomicon CROSS
8567 program for discovering this case) and use of BER or invalid ASN.1 INTEGERs
8568 (negative or with leading zeroes).
8570 Further analysis was conducted and fixes were developed by Stephen Henson
8571 of the OpenSSL core team.
8577 ### Changes between 1.0.0n and 1.0.0o [15 Oct 2014]
8579 * Session Ticket Memory Leak.
8581 When an OpenSSL SSL/TLS/DTLS server receives a session ticket the
8582 integrity of that ticket is first verified. In the event of a session
8583 ticket integrity check failing, OpenSSL will fail to free memory
8584 causing a memory leak. By sending a large number of invalid session
8585 tickets an attacker could exploit this issue in a Denial Of Service
8591 * Build option no-ssl3 is incomplete.
8593 When OpenSSL is configured with "no-ssl3" as a build option, servers
8594 could accept and complete an SSL 3.0 handshake, and clients could be
8595 configured to send them.
8598 *Akamai and the OpenSSL team*
8600 * Add support for TLS_FALLBACK_SCSV.
8601 Client applications doing fallback retries should call
8602 SSL_set_mode(s, SSL_MODE_SEND_FALLBACK_SCSV).
8605 *Adam Langley, Bodo Moeller*
8607 * Add additional DigestInfo checks.
8609 Reencode DigestInto in DER and check against the original when
8610 verifying RSA signature: this will reject any improperly encoded
8611 DigestInfo structures.
8613 Note: this is a precautionary measure and no attacks are currently known.
8617 ### Changes between 1.0.0m and 1.0.0n [6 Aug 2014]
8619 * OpenSSL DTLS clients enabling anonymous (EC)DH ciphersuites are subject
8620 to a denial of service attack. A malicious server can crash the client
8621 with a null pointer dereference (read) by specifying an anonymous (EC)DH
8622 ciphersuite and sending carefully crafted handshake messages.
8624 Thanks to Felix Gröbert (Google) for discovering and researching this
8630 * By sending carefully crafted DTLS packets an attacker could cause openssl
8631 to leak memory. This can be exploited through a Denial of Service attack.
8632 Thanks to Adam Langley for discovering and researching this issue.
8637 * An attacker can force openssl to consume large amounts of memory whilst
8638 processing DTLS handshake messages. This can be exploited through a
8639 Denial of Service attack.
8640 Thanks to Adam Langley for discovering and researching this issue.
8645 * An attacker can force an error condition which causes openssl to crash
8646 whilst processing DTLS packets due to memory being freed twice. This
8647 can be exploited through a Denial of Service attack.
8648 Thanks to Adam Langley and Wan-Teh Chang for discovering and researching
8654 * If a multithreaded client connects to a malicious server using a resumed
8655 session and the server sends an ec point format extension it could write
8656 up to 255 bytes to freed memory.
8658 Thanks to Gabor Tyukasz (LogMeIn Inc) for discovering and researching this
8664 * A flaw in OBJ_obj2txt may cause pretty printing functions such as
8665 X509_name_oneline, X509_name_print_ex et al. to leak some information
8666 from the stack. Applications may be affected if they echo pretty printing
8667 output to the attacker.
8669 Thanks to Ivan Fratric (Google) for discovering this issue.
8672 *Emilia Käsper, and Steve Henson*
8674 * Fix ec_GFp_simple_points_make_affine (thus, EC_POINTs_mul etc.)
8675 for corner cases. (Certain input points at infinity could lead to
8676 bogus results, with non-infinity inputs mapped to infinity too.)
8680 ### Changes between 1.0.0l and 1.0.0m [5 Jun 2014]
8682 * Fix for SSL/TLS MITM flaw. An attacker using a carefully crafted
8683 handshake can force the use of weak keying material in OpenSSL
8684 SSL/TLS clients and servers.
8686 Thanks to KIKUCHI Masashi (Lepidum Co. Ltd.) for discovering and
8687 researching this issue. ([CVE-2014-0224])
8689 *KIKUCHI Masashi, Steve Henson*
8691 * Fix DTLS recursion flaw. By sending an invalid DTLS handshake to an
8692 OpenSSL DTLS client the code can be made to recurse eventually crashing
8695 Thanks to Imre Rad (Search-Lab Ltd.) for discovering this issue.
8698 *Imre Rad, Steve Henson*
8700 * Fix DTLS invalid fragment vulnerability. A buffer overrun attack can
8701 be triggered by sending invalid DTLS fragments to an OpenSSL DTLS
8702 client or server. This is potentially exploitable to run arbitrary
8703 code on a vulnerable client or server.
8705 Thanks to Jüri Aedla for reporting this issue. ([CVE-2014-0195])
8707 *Jüri Aedla, Steve Henson*
8709 * Fix bug in TLS code where clients enable anonymous ECDH ciphersuites
8710 are subject to a denial of service attack.
8712 Thanks to Felix Gröbert and Ivan Fratric at Google for discovering
8713 this issue. ([CVE-2014-3470])
8715 *Felix Gröbert, Ivan Fratric, Steve Henson*
8717 * Harmonize version and its documentation. -f flag is used to display
8720 *mancha <mancha1@zoho.com>*
8722 * Fix eckey_priv_encode so it immediately returns an error upon a failure
8723 in i2d_ECPrivateKey.
8725 *mancha <mancha1@zoho.com>*
8727 * Fix some double frees. These are not thought to be exploitable.
8729 *mancha <mancha1@zoho.com>*
8731 * Fix for the attack described in the paper "Recovering OpenSSL
8732 ECDSA Nonces Using the FLUSH+RELOAD Cache Side-channel Attack"
8733 by Yuval Yarom and Naomi Benger. Details can be obtained from:
8734 <http://eprint.iacr.org/2014/140>
8736 Thanks to Yuval Yarom and Naomi Benger for discovering this
8737 flaw and to Yuval Yarom for supplying a fix ([CVE-2014-0076])
8739 *Yuval Yarom and Naomi Benger*
8741 ### Changes between 1.0.0k and 1.0.0l [6 Jan 2014]
8743 * Keep original DTLS digest and encryption contexts in retransmission
8744 structures so we can use the previous session parameters if they need
8745 to be resent. ([CVE-2013-6450])
8749 * Add option SSL_OP_SAFARI_ECDHE_ECDSA_BUG (part of SSL_OP_ALL) which
8750 avoids preferring ECDHE-ECDSA ciphers when the client appears to be
8751 Safari on OS X. Safari on OS X 10.8..10.8.3 advertises support for
8752 several ECDHE-ECDSA ciphers, but fails to negotiate them. The bug
8753 is fixed in OS X 10.8.4, but Apple have ruled out both hot fixing
8754 10.8..10.8.3 and forcing users to upgrade to 10.8.4 or newer.
8756 *Rob Stradling, Adam Langley*
8758 ### Changes between 1.0.0j and 1.0.0k [5 Feb 2013]
8760 * Make the decoding of SSLv3, TLS and DTLS CBC records constant time.
8762 This addresses the flaw in CBC record processing discovered by
8763 Nadhem Alfardan and Kenny Paterson. Details of this attack can be found
8764 at: <http://www.isg.rhul.ac.uk/tls/>
8766 Thanks go to Nadhem Alfardan and Kenny Paterson of the Information
8767 Security Group at Royal Holloway, University of London
8768 (www.isg.rhul.ac.uk) for discovering this flaw and Adam Langley and
8769 Emilia Käsper for the initial patch.
8772 *Emilia Käsper, Adam Langley, Ben Laurie, Andy Polyakov, Steve Henson*
8774 * Return an error when checking OCSP signatures when key is NULL.
8775 This fixes a DoS attack. ([CVE-2013-0166])
8779 * Call OCSP Stapling callback after ciphersuite has been chosen, so
8780 the right response is stapled. Also change SSL_get_certificate()
8781 so it returns the certificate actually sent.
8782 See <http://rt.openssl.org/Ticket/Display.html?id=2836>.
8783 (This is a backport)
8785 *Rob Stradling <rob.stradling@comodo.com>*
8787 * Fix possible deadlock when decoding public keys.
8791 ### Changes between 1.0.0i and 1.0.0j [10 May 2012]
8793 [NB: OpenSSL 1.0.0i and later 1.0.0 patch levels were released after
8796 * Sanity check record length before skipping explicit IV in DTLS
8799 Thanks to Codenomicon for discovering this issue using Fuzz-o-Matic
8800 fuzzing as a service testing platform.
8805 * Initialise tkeylen properly when encrypting CMS messages.
8806 Thanks to Solar Designer of Openwall for reporting this issue.
8810 ### Changes between 1.0.0h and 1.0.0i [19 Apr 2012]
8812 * Check for potentially exploitable overflows in asn1_d2i_read_bio
8813 BUF_mem_grow and BUF_mem_grow_clean. Refuse attempts to shrink buffer
8814 in CRYPTO_realloc_clean.
8816 Thanks to Tavis Ormandy, Google Security Team, for discovering this
8817 issue and to Adam Langley <agl@chromium.org> for fixing it.
8820 *Adam Langley (Google), Tavis Ormandy, Google Security Team*
8822 ### Changes between 1.0.0g and 1.0.0h [12 Mar 2012]
8824 * Fix MMA (Bleichenbacher's attack on PKCS #1 v1.5 RSA padding) weakness
8825 in CMS and PKCS7 code. When RSA decryption fails use a random key for
8826 content decryption and always return the same error. Note: this attack
8827 needs on average 2^20 messages so it only affects automated senders. The
8828 old behaviour can be re-enabled in the CMS code by setting the
8829 CMS_DEBUG_DECRYPT flag: this is useful for debugging and testing where
8830 an MMA defence is not necessary.
8831 Thanks to Ivan Nestlerode <inestlerode@us.ibm.com> for discovering
8832 this issue. ([CVE-2012-0884])
8836 * Fix CVE-2011-4619: make sure we really are receiving a
8837 client hello before rejecting multiple SGC restarts. Thanks to
8838 Ivan Nestlerode <inestlerode@us.ibm.com> for discovering this bug.
8842 ### Changes between 1.0.0f and 1.0.0g [18 Jan 2012]
8844 * Fix for DTLS DoS issue introduced by fix for CVE-2011-4109.
8845 Thanks to Antonio Martin, Enterprise Secure Access Research and
8846 Development, Cisco Systems, Inc. for discovering this bug and
8847 preparing a fix. ([CVE-2012-0050])
8851 ### Changes between 1.0.0e and 1.0.0f [4 Jan 2012]
8853 * Nadhem Alfardan and Kenny Paterson have discovered an extension
8854 of the Vaudenay padding oracle attack on CBC mode encryption
8855 which enables an efficient plaintext recovery attack against
8856 the OpenSSL implementation of DTLS. Their attack exploits timing
8857 differences arising during decryption processing. A research
8858 paper describing this attack can be found at:
8859 <http://www.isg.rhul.ac.uk/~kp/dtls.pdf>
8860 Thanks go to Nadhem Alfardan and Kenny Paterson of the Information
8861 Security Group at Royal Holloway, University of London
8862 (www.isg.rhul.ac.uk) for discovering this flaw and to Robin Seggelmann
8863 <seggelmann@fh-muenster.de> and Michael Tuexen <tuexen@fh-muenster.de>
8864 for preparing the fix. ([CVE-2011-4108])
8866 *Robin Seggelmann, Michael Tuexen*
8868 * Clear bytes used for block padding of SSL 3.0 records.
8871 *Adam Langley (Google)*
8873 * Only allow one SGC handshake restart for SSL/TLS. Thanks to George
8874 Kadianakis <desnacked@gmail.com> for discovering this issue and
8875 Adam Langley for preparing the fix. ([CVE-2011-4619])
8877 *Adam Langley (Google)*
8879 * Check parameters are not NULL in GOST ENGINE. ([CVE-2012-0027])
8881 *Andrey Kulikov <amdeich@gmail.com>*
8883 * Prevent malformed RFC3779 data triggering an assertion failure.
8884 Thanks to Andrew Chi, BBN Technologies, for discovering the flaw
8885 and Rob Austein <sra@hactrn.net> for fixing it. ([CVE-2011-4577])
8887 *Rob Austein <sra@hactrn.net>*
8889 * Improved PRNG seeding for VOS.
8891 *Paul Green <Paul.Green@stratus.com>*
8893 * Fix ssl_ciph.c set-up race.
8895 *Adam Langley (Google)*
8897 * Fix spurious failures in ecdsatest.c.
8899 *Emilia Käsper (Google)*
8901 * Fix the BIO_f_buffer() implementation (which was mixing different
8902 interpretations of the `..._len` fields).
8904 *Adam Langley (Google)*
8906 * Fix handling of BN_BLINDING: now BN_BLINDING_invert_ex (rather than
8907 BN_BLINDING_invert_ex) calls BN_BLINDING_update, ensuring that concurrent
8908 threads won't reuse the same blinding coefficients.
8910 This also avoids the need to obtain the CRYPTO_LOCK_RSA_BLINDING
8911 lock to call BN_BLINDING_invert_ex, and avoids one use of
8912 BN_BLINDING_update for each BN_BLINDING structure (previously,
8913 the last update always remained unused).
8915 *Emilia Käsper (Google)*
8917 * In ssl3_clear, preserve s3->init_extra along with s3->rbuf.
8919 *Bob Buckholz (Google)*
8921 ### Changes between 1.0.0d and 1.0.0e [6 Sep 2011]
8923 * Fix bug where CRLs with nextUpdate in the past are sometimes accepted
8924 by initialising X509_STORE_CTX properly. ([CVE-2011-3207])
8926 *Kaspar Brand <ossl@velox.ch>*
8928 * Fix SSL memory handling for (EC)DH ciphersuites, in particular
8929 for multi-threaded use of ECDH. ([CVE-2011-3210])
8931 *Adam Langley (Google)*
8933 * Fix x509_name_ex_d2i memory leak on bad inputs.
8937 * Remove hard coded ecdsaWithSHA1 signature tests in ssl code and check
8938 signature public key algorithm by using OID xref utilities instead.
8939 Before this you could only use some ECC ciphersuites with SHA1 only.
8943 * Add protection against ECDSA timing attacks as mentioned in the paper
8944 by Billy Bob Brumley and Nicola Tuveri, see:
8945 <http://eprint.iacr.org/2011/232.pdf>
8947 *Billy Bob Brumley and Nicola Tuveri*
8949 ### Changes between 1.0.0c and 1.0.0d [8 Feb 2011]
8951 * Fix parsing of OCSP stapling ClientHello extension. CVE-2011-0014
8953 *Neel Mehta, Adam Langley, Bodo Moeller (Google)*
8955 * Fix bug in string printing code: if *any* escaping is enabled we must
8956 escape the escape character (backslash) or the resulting string is
8961 ### Changes between 1.0.0b and 1.0.0c [2 Dec 2010]
8963 * Disable code workaround for ancient and obsolete Netscape browsers
8964 and servers: an attacker can use it in a ciphersuite downgrade attack.
8965 Thanks to Martin Rex for discovering this bug. CVE-2010-4180
8969 * Fixed J-PAKE implementation error, originally discovered by
8970 Sebastien Martini, further info and confirmation from Stefan
8971 Arentz and Feng Hao. Note that this fix is a security fix. CVE-2010-4252
8975 ### Changes between 1.0.0a and 1.0.0b [16 Nov 2010]
8977 * Fix extension code to avoid race conditions which can result in a buffer
8978 overrun vulnerability: resumed sessions must not be modified as they can
8979 be shared by multiple threads. CVE-2010-3864
8983 * Fix WIN32 build system to correctly link an ENGINE directory into
8988 ### Changes between 1.0.0 and 1.0.0a [01 Jun 2010]
8990 * Check return value of int_rsa_verify in pkey_rsa_verifyrecover
8993 *Steve Henson, Peter-Michael Hager <hager@dortmund.net>*
8995 ### Changes between 0.9.8n and 1.0.0 [29 Mar 2010]
8997 * Add "missing" function EVP_CIPHER_CTX_copy(). This copies a cipher
8998 context. The operation can be customised via the ctrl mechanism in
8999 case ENGINEs want to include additional functionality.
9003 * Tolerate yet another broken PKCS#8 key format: private key value negative.
9007 * Add new -subject_hash_old and -issuer_hash_old options to x509 utility to
9008 output hashes compatible with older versions of OpenSSL.
9010 *Willy Weisz <weisz@vcpc.univie.ac.at>*
9012 * Fix compression algorithm handling: if resuming a session use the
9013 compression algorithm of the resumed session instead of determining
9014 it from client hello again. Don't allow server to change algorithm.
9018 * Add load_crls() function to commands tidying load_certs() too. Add option
9019 to verify utility to allow additional CRLs to be included.
9023 * Update OCSP request code to permit adding custom headers to the request:
9024 some responders need this.
9028 * The function EVP_PKEY_sign() returns <=0 on error: check return code
9031 *Julia Lawall <julia@diku.dk>*
9033 * Update verify callback code in `apps/s_cb.c` and `apps/verify.c`, it
9034 needlessly dereferenced structures, used obsolete functions and
9035 didn't handle all updated verify codes correctly.
9039 * Disable MD2 in the default configuration.
9043 * In BIO_pop() and BIO_push() use the ctrl argument (which was NULL) to
9044 indicate the initial BIO being pushed or popped. This makes it possible
9045 to determine whether the BIO is the one explicitly called or as a result
9046 of the ctrl being passed down the chain. Fix BIO_pop() and SSL BIOs so
9047 it handles reference counts correctly and doesn't zero out the I/O bio
9048 when it is not being explicitly popped. WARNING: applications which
9049 included workarounds for the old buggy behaviour will need to be modified
9050 or they could free up already freed BIOs.
9054 * Extend the uni2asc/asc2uni => OPENSSL_uni2asc/OPENSSL_asc2uni
9055 renaming to all platforms (within the 0.9.8 branch, this was
9056 done conditionally on Netware platforms to avoid a name clash).
9058 *Guenter <lists@gknw.net>*
9060 * Add ECDHE and PSK support to DTLS.
9062 *Michael Tuexen <tuexen@fh-muenster.de>*
9064 * Add CHECKED_STACK_OF macro to safestack.h, otherwise safestack can't
9069 * Add "missing" function EVP_MD_flags() (without this the only way to
9070 retrieve a digest flags is by accessing the structure directly. Update
9071 `EVP_MD_do_all*()` and `EVP_CIPHER_do_all*()` to include the name a digest
9072 or cipher is registered as in the "from" argument. Print out all
9073 registered digests in the dgst usage message instead of manually
9074 attempting to work them out.
9078 * If no SSLv2 ciphers are used don't use an SSLv2 compatible client hello:
9079 this allows the use of compression and extensions. Change default cipher
9080 string to remove SSLv2 ciphersuites. This effectively avoids ancient SSLv2
9081 by default unless an application cipher string requests it.
9085 * Alter match criteria in PKCS12_parse(). It used to try to use local
9086 key ids to find matching certificates and keys but some PKCS#12 files
9087 don't follow the (somewhat unwritten) rules and this strategy fails.
9088 Now just gather all certificates together and the first private key
9089 then look for the first certificate that matches the key.
9093 * Support use of registered digest and cipher names for dgst and cipher
9094 commands instead of having to add each one as a special case. So now
9101 openssl dgst -sha256 foo
9103 and this works for ENGINE based algorithms too.
9107 * Update Gost ENGINE to support parameter files.
9109 *Victor B. Wagner <vitus@cryptocom.ru>*
9111 * Support GeneralizedTime in ca utility.
9113 *Oliver Martin <oliver@volatilevoid.net>, Steve Henson*
9115 * Enhance the hash format used for certificate directory links. The new
9116 form uses the canonical encoding (meaning equivalent names will work
9117 even if they aren't identical) and uses SHA1 instead of MD5. This form
9118 is incompatible with the older format and as a result c_rehash should
9119 be used to rebuild symbolic links.
9123 * Make PKCS#8 the default write format for private keys, replacing the
9124 traditional format. This form is standardised, more secure and doesn't
9125 include an implicit MD5 dependency.
9129 * Add a $gcc_devteam_warn option to Configure. The idea is that any code
9130 committed to OpenSSL should pass this lot as a minimum.
9134 * Add session ticket override functionality for use by EAP-FAST.
9136 *Jouni Malinen <j@w1.fi>*
9138 * Modify HMAC functions to return a value. Since these can be implemented
9139 in an ENGINE errors can occur.
9143 * Type-checked OBJ_bsearch_ex.
9147 * Type-checked OBJ_bsearch. Also some constification necessitated
9148 by type-checking. Still to come: TXT_DB, bsearch(?),
9149 OBJ_bsearch_ex, qsort, CRYPTO_EX_DATA, ASN1_VALUE, ASN1_STRING,
9154 * New function OPENSSL_gmtime_adj() to add a specific number of days and
9155 seconds to a tm structure directly, instead of going through OS
9156 specific date routines. This avoids any issues with OS routines such
9157 as the year 2038 bug. New `*_adj()` functions for ASN1 time structures
9158 and X509_time_adj_ex() to cover the extended range. The existing
9159 X509_time_adj() is still usable and will no longer have any date issues.
9163 * Delta CRL support. New use deltas option which will attempt to locate
9164 and search any appropriate delta CRLs available.
9166 This work was sponsored by Google.
9170 * Support for CRLs partitioned by reason code. Reorganise CRL processing
9171 code and add additional score elements. Validate alternate CRL paths
9172 as part of the CRL checking and indicate a new error "CRL path validation
9173 error" in this case. Applications wanting additional details can use
9174 the verify callback and check the new "parent" field. If this is not
9175 NULL CRL path validation is taking place. Existing applications won't
9176 see this because it requires extended CRL support which is off by
9179 This work was sponsored by Google.
9183 * Support for freshest CRL extension.
9185 This work was sponsored by Google.
9189 * Initial indirect CRL support. Currently only supported in the CRLs
9190 passed directly and not via lookup. Process certificate issuer
9191 CRL entry extension and lookup CRL entries by bother issuer name
9192 and serial number. Check and process CRL issuer entry in IDP extension.
9194 This work was sponsored by Google.
9198 * Add support for distinct certificate and CRL paths. The CRL issuer
9199 certificate is validated separately in this case. Only enabled if
9200 an extended CRL support flag is set: this flag will enable additional
9201 CRL functionality in future.
9203 This work was sponsored by Google.
9207 * Add support for policy mappings extension.
9209 This work was sponsored by Google.
9213 * Fixes to pathlength constraint, self issued certificate handling,
9214 policy processing to align with RFC3280 and PKITS tests.
9216 This work was sponsored by Google.
9220 * Support for name constraints certificate extension. DN, email, DNS
9221 and URI types are currently supported.
9223 This work was sponsored by Google.
9227 * To cater for systems that provide a pointer-based thread ID rather
9228 than numeric, deprecate the current numeric thread ID mechanism and
9229 replace it with a structure and associated callback type. This
9230 mechanism allows a numeric "hash" to be extracted from a thread ID in
9231 either case, and on platforms where pointers are larger than 'long',
9232 mixing is done to help ensure the numeric 'hash' is usable even if it
9233 can't be guaranteed unique. The default mechanism is to use "&errno"
9234 as a pointer-based thread ID to distinguish between threads.
9236 Applications that want to provide their own thread IDs should now use
9237 CRYPTO_THREADID_set_callback() to register a callback that will call
9238 either CRYPTO_THREADID_set_numeric() or CRYPTO_THREADID_set_pointer().
9240 Note that ERR_remove_state() is now deprecated, because it is tied
9241 to the assumption that thread IDs are numeric. ERR_remove_state(0)
9242 to free the current thread's error state should be replaced by
9243 ERR_remove_thread_state(NULL).
9245 (This new approach replaces the functions CRYPTO_set_idptr_callback(),
9246 CRYPTO_get_idptr_callback(), and CRYPTO_thread_idptr() that existed in
9247 OpenSSL 0.9.9-dev between June 2006 and August 2008. Also, if an
9248 application was previously providing a numeric thread callback that
9249 was inappropriate for distinguishing threads, then uniqueness might
9250 have been obtained with &errno that happened immediately in the
9251 intermediate development versions of OpenSSL; this is no longer the
9252 case, the numeric thread callback will now override the automatic use
9255 *Geoff Thorpe, with help from Bodo Moeller*
9257 * Initial support for different CRL issuing certificates. This covers a
9258 simple case where the self issued certificates in the chain exist and
9259 the real CRL issuer is higher in the existing chain.
9261 This work was sponsored by Google.
9265 * Removed effectively defunct crypto/store from the build.
9269 * Revamp of STACK to provide stronger type-checking. Still to come:
9270 TXT_DB, bsearch(?), OBJ_bsearch, qsort, CRYPTO_EX_DATA, ASN1_VALUE,
9271 ASN1_STRING, CONF_VALUE.
9275 * Add a new SSL_MODE_RELEASE_BUFFERS mode flag to release unused buffer
9276 RAM on SSL connections. This option can save about 34k per idle SSL.
9280 * Revamp of LHASH to provide stronger type-checking. Still to come:
9281 STACK, TXT_DB, bsearch, qsort.
9285 * Initial support for Cryptographic Message Syntax (aka CMS) based
9286 on RFC3850, RFC3851 and RFC3852. New cms directory and cms utility,
9287 support for data, signedData, compressedData, digestedData and
9288 encryptedData, envelopedData types included. Scripts to check against
9289 RFC4134 examples draft and interop and consistency checks of many
9290 content types and variants.
9294 * Add options to enc utility to support use of zlib compression BIO.
9298 * Extend mk1mf to support importing of options and assembly language
9299 files from Configure script, currently only included in VC-WIN32.
9300 The assembly language rules can now optionally generate the source
9301 files from the associated perl scripts.
9305 * Implement remaining functionality needed to support GOST ciphersuites.
9306 Interop testing has been performed using CryptoPro implementations.
9308 *Victor B. Wagner <vitus@cryptocom.ru>*
9310 * s390x assembler pack.
9314 * ARMv4 assembler pack. ARMv4 refers to v4 and later ISA, not CPU
9319 * Implement Opaque PRF Input TLS extension as specified in
9320 draft-rescorla-tls-opaque-prf-input-00.txt. Since this is not an
9321 official specification yet and no extension type assignment by
9322 IANA exists, this extension (for now) will have to be explicitly
9323 enabled when building OpenSSL by providing the extension number
9324 to use. For example, specify an option
9326 -DTLSEXT_TYPE_opaque_prf_input=0x9527
9328 to the "config" or "Configure" script to enable the extension,
9329 assuming extension number 0x9527 (which is a completely arbitrary
9330 and unofficial assignment based on the MD5 hash of the Internet
9331 Draft). Note that by doing so, you potentially lose
9332 interoperability with other TLS implementations since these might
9333 be using the same extension number for other purposes.
9335 SSL_set_tlsext_opaque_prf_input(ssl, src, len) is used to set the
9336 opaque PRF input value to use in the handshake. This will create
9337 an internal copy of the length-'len' string at 'src', and will
9338 return non-zero for success.
9340 To get more control and flexibility, provide a callback function
9343 SSL_CTX_set_tlsext_opaque_prf_input_callback(ctx, cb)
9344 SSL_CTX_set_tlsext_opaque_prf_input_callback_arg(ctx, arg)
9348 int (*cb)(SSL *, void *peerinput, size_t len, void *arg);
9351 Callback function 'cb' will be called in handshakes, and is
9352 expected to use SSL_set_tlsext_opaque_prf_input() as appropriate.
9353 Argument 'arg' is for application purposes (the value as given to
9354 SSL_CTX_set_tlsext_opaque_prf_input_callback_arg() will directly
9355 be provided to the callback function). The callback function
9356 has to return non-zero to report success: usually 1 to use opaque
9357 PRF input just if possible, or 2 to enforce use of the opaque PRF
9358 input. In the latter case, the library will abort the handshake
9359 if opaque PRF input is not successfully negotiated.
9361 Arguments 'peerinput' and 'len' given to the callback function
9362 will always be NULL and 0 in the case of a client. A server will
9363 see the client's opaque PRF input through these variables if
9364 available (NULL and 0 otherwise). Note that if the server
9365 provides an opaque PRF input, the length must be the same as the
9366 length of the client's opaque PRF input.
9368 Note that the callback function will only be called when creating
9369 a new session (session resumption can resume whatever was
9370 previously negotiated), and will not be called in SSL 2.0
9371 handshakes; thus, SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv2) or
9372 SSL_set_options(ssl, SSL_OP_NO_SSLv2) is especially recommended
9373 for applications that need to enforce opaque PRF input.
9377 * Update ssl code to support digests other than SHA1+MD5 for handshake
9380 *Victor B. Wagner <vitus@cryptocom.ru>*
9382 * Add RFC4507 support to OpenSSL. This includes the corrections in
9383 RFC4507bis. The encrypted ticket format is an encrypted encoded
9384 SSL_SESSION structure, that way new session features are automatically
9387 If a client application caches session in an SSL_SESSION structure
9388 support is transparent because tickets are now stored in the encoded
9391 The SSL_CTX structure automatically generates keys for ticket
9392 protection in servers so again support should be possible
9393 with no application modification.
9395 If a client or server wishes to disable RFC4507 support then the option
9396 SSL_OP_NO_TICKET can be set.
9398 Add a TLS extension debugging callback to allow the contents of any client
9399 or server extensions to be examined.
9401 This work was sponsored by Google.
9405 * Final changes to avoid use of pointer pointer casts in OpenSSL.
9406 OpenSSL should now compile cleanly on gcc 4.2
9408 *Peter Hartley <pdh@utter.chaos.org.uk>, Steve Henson*
9410 * Update SSL library to use new EVP_PKEY MAC API. Include generic MAC
9411 support including streaming MAC support: this is required for GOST
9412 ciphersuite support.
9414 *Victor B. Wagner <vitus@cryptocom.ru>, Steve Henson*
9416 * Add option -stream to use PKCS#7 streaming in smime utility. New
9417 function i2d_PKCS7_bio_stream() and PEM_write_PKCS7_bio_stream()
9418 to output in BER and PEM format.
9422 * Experimental support for use of HMAC via EVP_PKEY interface. This
9423 allows HMAC to be handled via the `EVP_DigestSign*()` interface. The
9424 EVP_PKEY "key" in this case is the HMAC key, potentially allowing
9425 ENGINE support for HMAC keys which are unextractable. New -mac and
9426 -macopt options to dgst utility.
9430 * New option -sigopt to dgst utility. Update dgst to use
9431 `EVP_Digest{Sign,Verify}*`. These two changes make it possible to use
9432 alternative signing parameters such as X9.31 or PSS in the dgst
9437 * Change ssl_cipher_apply_rule(), the internal function that does
9438 the work each time a ciphersuite string requests enabling
9439 ("foo+bar"), moving ("+foo+bar"), disabling ("-foo+bar", or
9440 removing ("!foo+bar") a class of ciphersuites: Now it maintains
9441 the order of disabled ciphersuites such that those ciphersuites
9442 that most recently went from enabled to disabled not only stay
9443 in order with respect to each other, but also have higher priority
9444 than other disabled ciphersuites the next time ciphersuites are
9447 This means that you can now say, e.g., "PSK:-PSK:HIGH" to enable
9448 the same ciphersuites as with "HIGH" alone, but in a specific
9449 order where the PSK ciphersuites come first (since they are the
9450 most recently disabled ciphersuites when "HIGH" is parsed).
9452 Also, change ssl_create_cipher_list() (using this new
9453 functionality) such that between otherwise identical
9454 ciphersuites, ephemeral ECDH is preferred over ephemeral DH in
9459 * Change ssl_create_cipher_list() so that it automatically
9460 arranges the ciphersuites in reasonable order before starting
9461 to process the rule string. Thus, the definition for "DEFAULT"
9462 (SSL_DEFAULT_CIPHER_LIST) now is just "ALL:!aNULL:!eNULL", but
9463 remains equivalent to `"AES:ALL:!aNULL:!eNULL:+aECDH:+kRSA:+RC4:@STRENGTH"`.
9464 This makes it much easier to arrive at a reasonable default order
9465 in applications for which anonymous ciphers are OK (meaning
9466 that you can't actually use DEFAULT).
9468 *Bodo Moeller; suggested by Victor Duchovni*
9470 * Split the SSL/TLS algorithm mask (as used for ciphersuite string
9471 processing) into multiple integers instead of setting
9472 "SSL_MKEY_MASK" bits, "SSL_AUTH_MASK" bits, "SSL_ENC_MASK",
9473 "SSL_MAC_MASK", and "SSL_SSL_MASK" bits all in a single integer.
9474 (These masks as well as the individual bit definitions are hidden
9475 away into the non-exported interface ssl/ssl_locl.h, so this
9476 change to the definition of the SSL_CIPHER structure shouldn't
9477 affect applications.) This give us more bits for each of these
9478 categories, so there is no longer a need to coagulate AES128 and
9479 AES256 into a single algorithm bit, and to coagulate Camellia128
9480 and Camellia256 into a single algorithm bit, which has led to all
9483 Thus, among other things, the kludge introduced in 0.9.7m and
9484 0.9.8e for masking out AES256 independently of AES128 or masking
9485 out Camellia256 independently of AES256 is not needed here in 0.9.9.
9487 With the change, we also introduce new ciphersuite aliases that
9488 so far were missing: "AES128", "AES256", "CAMELLIA128", and
9493 * Add support for dsa-with-SHA224 and dsa-with-SHA256.
9494 Use the leftmost N bytes of the signature input if the input is
9495 larger than the prime q (with N being the size in bytes of q).
9499 * Very *very* experimental PKCS#7 streaming encoder support. Nothing uses
9500 it yet and it is largely untested.
9504 * Add support for the ecdsa-with-SHA224/256/384/512 signature types.
9508 * Initial incomplete changes to avoid need for function casts in OpenSSL
9509 some compilers (gcc 4.2 and later) reject their use. Safestack is
9510 reimplemented. Update ASN1 to avoid use of legacy functions.
9514 * Win32/64 targets are linked with Winsock2.
9518 * Add an X509_CRL_METHOD structure to allow CRL processing to be redirected
9519 to external functions. This can be used to increase CRL handling
9520 efficiency especially when CRLs are very large by (for example) storing
9521 the CRL revoked certificates in a database.
9525 * Overhaul of by_dir code. Add support for dynamic loading of CRLs so
9526 new CRLs added to a directory can be used. New command line option
9527 -verify_return_error to s_client and s_server. This causes real errors
9528 to be returned by the verify callback instead of carrying on no matter
9529 what. This reflects the way a "real world" verify callback would behave.
9533 * GOST engine, supporting several GOST algorithms and public key formats.
9534 Kindly donated by Cryptocom.
9538 * Partial support for Issuing Distribution Point CRL extension. CRLs
9539 partitioned by DP are handled but no indirect CRL or reason partitioning
9540 (yet). Complete overhaul of CRL handling: now the most suitable CRL is
9541 selected via a scoring technique which handles IDP and AKID in CRLs.
9545 * New X509_STORE_CTX callbacks lookup_crls() and lookup_certs() which
9546 will ultimately be used for all verify operations: this will remove the
9547 X509_STORE dependency on certificate verification and allow alternative
9548 lookup methods. X509_STORE based implementations of these two callbacks.
9552 * Allow multiple CRLs to exist in an X509_STORE with matching issuer names.
9553 Modify get_crl() to find a valid (unexpired) CRL if possible.
9557 * New function X509_CRL_match() to check if two CRLs are identical. Normally
9558 this would be called X509_CRL_cmp() but that name is already used by
9559 a function that just compares CRL issuer names. Cache several CRL
9560 extensions in X509_CRL structure and cache CRLDP in X509.
9564 * Store a "canonical" representation of X509_NAME structure (ASN1 Name)
9565 this maps equivalent X509_NAME structures into a consistent structure.
9566 Name comparison can then be performed rapidly using memcmp().
9570 * Non-blocking OCSP request processing. Add -timeout option to ocsp
9575 * Allow digests to supply their own micalg string for S/MIME type using
9576 the ctrl EVP_MD_CTRL_MICALG.
9580 * During PKCS7 signing pass the PKCS7 SignerInfo structure to the
9581 EVP_PKEY_METHOD before and after signing via the EVP_PKEY_CTRL_PKCS7_SIGN
9582 ctrl. It can then customise the structure before and/or after signing
9587 * New function OBJ_add_sigid() to allow application defined signature OIDs
9588 to be added to OpenSSLs internal tables. New function OBJ_sigid_free()
9589 to free up any added signature OIDs.
9593 * New functions EVP_CIPHER_do_all(), EVP_CIPHER_do_all_sorted(),
9594 EVP_MD_do_all() and EVP_MD_do_all_sorted() to enumerate internal
9595 digest and cipher tables. New options added to openssl utility:
9596 list-message-digest-algorithms and list-cipher-algorithms.
9600 * Change the array representation of binary polynomials: the list
9601 of degrees of non-zero coefficients is now terminated with -1.
9602 Previously it was terminated with 0, which was also part of the
9603 value; thus, the array representation was not applicable to
9604 polynomials where t^0 has coefficient zero. This change makes
9605 the array representation useful in a more general context.
9609 * Various modifications and fixes to SSL/TLS cipher string
9610 handling. For ECC, the code now distinguishes between fixed ECDH
9611 with RSA certificates on the one hand and with ECDSA certificates
9612 on the other hand, since these are separate ciphersuites. The
9613 unused code for Fortezza ciphersuites has been removed.
9615 For consistency with EDH, ephemeral ECDH is now called "EECDH"
9616 (not "ECDHE"). For consistency with the code for DH
9617 certificates, use of ECDH certificates is now considered ECDH
9618 authentication, not RSA or ECDSA authentication (the latter is
9619 merely the CA's signing algorithm and not actively used in the
9622 The temporary ciphersuite alias "ECCdraft" is no longer
9623 available, and ECC ciphersuites are no longer excluded from "ALL"
9624 and "DEFAULT". The following aliases now exist for RFC 4492
9625 ciphersuites, most of these by analogy with the DH case:
9627 kECDHr - ECDH cert, signed with RSA
9628 kECDHe - ECDH cert, signed with ECDSA
9629 kECDH - ECDH cert (signed with either RSA or ECDSA)
9630 kEECDH - ephemeral ECDH
9631 ECDH - ECDH cert or ephemeral ECDH
9637 AECDH - anonymous ECDH
9638 EECDH - non-anonymous ephemeral ECDH (equivalent to "kEECDH:-AECDH")
9642 * Add additional S/MIME capabilities for AES and GOST ciphers if supported.
9643 Use correct micalg parameters depending on digest(s) in signed message.
9647 * Add engine support for EVP_PKEY_ASN1_METHOD. Add functions to process
9648 an ENGINE asn1 method. Support ENGINE lookups in the ASN1 code.
9652 * Initial engine support for EVP_PKEY_METHOD. New functions to permit
9653 an engine to register a method. Add ENGINE lookups for methods and
9654 functional reference processing.
9658 * New functions `EVP_Digest{Sign,Verify)*`. These are enhanced versions of
9659 `EVP_{Sign,Verify}*` which allow an application to customise the signature
9664 * New -resign option to smime utility. This adds one or more signers
9665 to an existing PKCS#7 signedData structure. Also -md option to use an
9666 alternative message digest algorithm for signing.
9670 * Tidy up PKCS#7 routines and add new functions to make it easier to
9671 create PKCS7 structures containing multiple signers. Update smime
9672 application to support multiple signers.
9676 * New -macalg option to pkcs12 utility to allow setting of an alternative
9681 * Initial support for PKCS#5 v2.0 PRFs other than default SHA1 HMAC.
9682 Reorganize PBE internals to lookup from a static table using NIDs,
9683 add support for HMAC PBE OID translation. Add a EVP_CIPHER ctrl:
9684 EVP_CTRL_PBE_PRF_NID this allows a cipher to specify an alternative
9685 PRF which will be automatically used with PBES2.
9689 * Replace the algorithm specific calls to generate keys in "req" with the
9694 * Update PKCS#7 enveloped data routines to use new API. This is now
9695 supported by any public key method supporting the encrypt operation. A
9696 ctrl is added to allow the public key algorithm to examine or modify
9697 the PKCS#7 RecipientInfo structure if it needs to: for RSA this is
9702 * Add a ctrl to asn1 method to allow a public key algorithm to express
9703 a default digest type to use. In most cases this will be SHA1 but some
9704 algorithms (such as GOST) need to specify an alternative digest. The
9705 return value indicates how strong the preference is 1 means optional and
9706 2 is mandatory (that is it is the only supported type). Modify
9707 ASN1_item_sign() to accept a NULL digest argument to indicate it should
9708 use the default md. Update openssl utilities to use the default digest
9709 type for signing if it is not explicitly indicated.
9713 * Use OID cross reference table in ASN1_sign() and ASN1_verify(). New
9714 EVP_MD flag EVP_MD_FLAG_PKEY_METHOD_SIGNATURE. This uses the relevant
9715 signing method from the key type. This effectively removes the link
9716 between digests and public key types.
9720 * Add an OID cross reference table and utility functions. Its purpose is to
9721 translate between signature OIDs such as SHA1WithrsaEncryption and SHA1,
9722 rsaEncryption. This will allow some of the algorithm specific hackery
9723 needed to use the correct OID to be removed.
9727 * Remove algorithm specific dependencies when setting PKCS7_SIGNER_INFO
9728 structures for PKCS7_sign(). They are now set up by the relevant public
9733 * Add provisional EC pkey method with support for ECDSA and ECDH.
9737 * Add support for key derivation (agreement) in the API, DH method and
9742 * Add DSA pkey method and DH pkey methods, extend DH ASN1 method to support
9743 public and private key formats. As a side effect these add additional
9744 command line functionality not previously available: DSA signatures can be
9745 generated and verified using pkeyutl and DH key support and generation in
9752 *Oliver Tappe <zooey@hirschkaefer.de>*
9754 * New make target "install_html_docs" installs HTML renditions of the
9757 *Oliver Tappe <zooey@hirschkaefer.de>*
9759 * New utility "genpkey" this is analogous to "genrsa" etc except it can
9760 generate keys for any algorithm. Extend and update EVP_PKEY_METHOD to
9761 support key and parameter generation and add initial key generation
9762 functionality for RSA.
9766 * Add functions for main EVP_PKEY_method operations. The undocumented
9767 functions `EVP_PKEY_{encrypt,decrypt}` have been renamed to
9768 `EVP_PKEY_{encrypt,decrypt}_old`.
9772 * Initial definitions for EVP_PKEY_METHOD. This will be a high level public
9773 key API, doesn't do much yet.
9777 * New function EVP_PKEY_asn1_get0_info() to retrieve information about
9778 public key algorithms. New option to openssl utility:
9779 "list-public-key-algorithms" to print out info.
9783 * Implement the Supported Elliptic Curves Extension for
9784 ECC ciphersuites from draft-ietf-tls-ecc-12.txt.
9788 * Don't free up OIDs in OBJ_cleanup() if they are in use by EVP_MD or
9789 EVP_CIPHER structures to avoid later problems in EVP_cleanup().
9793 * New utilities pkey and pkeyparam. These are similar to algorithm specific
9794 utilities such as rsa, dsa, dsaparam etc except they process any key
9799 * Transfer public key printing routines to EVP_PKEY_ASN1_METHOD. New
9800 functions EVP_PKEY_print_public(), EVP_PKEY_print_private(),
9801 EVP_PKEY_print_param() to print public key data from an EVP_PKEY
9806 * Initial support for pluggable public key ASN1.
9807 De-spaghettify the public key ASN1 handling. Move public and private
9808 key ASN1 handling to a new EVP_PKEY_ASN1_METHOD structure. Relocate
9809 algorithm specific handling to a single module within the relevant
9810 algorithm directory. Add functions to allow (near) opaque processing
9811 of public and private key structures.
9815 * Implement the Supported Point Formats Extension for
9816 ECC ciphersuites from draft-ietf-tls-ecc-12.txt.
9820 * Add initial support for RFC 4279 PSK TLS ciphersuites. Add members
9821 for the psk identity [hint] and the psk callback functions to the
9822 SSL_SESSION, SSL and SSL_CTX structure.
9825 PSK-RC4-SHA, PSK-3DES-EDE-CBC-SHA, PSK-AES128-CBC-SHA,
9829 SSL_CTX_use_psk_identity_hint
9830 SSL_get_psk_identity_hint
9831 SSL_get_psk_identity
9832 SSL_use_psk_identity_hint
9834 *Mika Kousa and Pasi Eronen of Nokia Corporation*
9836 * Add RFC 3161 compliant time stamp request creation, response generation
9837 and response verification functionality.
9839 *Zoltán Glózik <zglozik@opentsa.org>, The OpenTSA Project*
9841 * Add initial support for TLS extensions, specifically for the server_name
9842 extension so far. The SSL_SESSION, SSL_CTX, and SSL data structures now
9843 have new members for a hostname. The SSL data structure has an
9844 additional member `SSL_CTX *initial_ctx` so that new sessions can be
9845 stored in that context to allow for session resumption, even after the
9846 SSL has been switched to a new SSL_CTX in reaction to a client's
9847 server_name extension.
9849 New functions (subject to change):
9851 SSL_get_servername()
9852 SSL_get_servername_type()
9855 New CTRL codes and macros (subject to change):
9857 SSL_CTRL_SET_TLSEXT_SERVERNAME_CB
9858 - SSL_CTX_set_tlsext_servername_callback()
9859 SSL_CTRL_SET_TLSEXT_SERVERNAME_ARG
9860 - SSL_CTX_set_tlsext_servername_arg()
9861 SSL_CTRL_SET_TLSEXT_HOSTNAME - SSL_set_tlsext_host_name()
9863 openssl s_client has a new '-servername ...' option.
9865 openssl s_server has new options '-servername_host ...', '-cert2 ...',
9866 '-key2 ...', '-servername_fatal' (subject to change). This allows
9867 testing the HostName extension for a specific single hostname ('-cert'
9868 and '-key' remain fallbacks for handshakes without HostName
9869 negotiation). If the unrecognized_name alert has to be sent, this by
9870 default is a warning; it becomes fatal with the '-servername_fatal'
9873 *Peter Sylvester, Remy Allais, Christophe Renou*
9875 * Whirlpool hash implementation is added.
9879 * BIGNUM code on 64-bit SPARCv9 targets is switched from bn(64,64) to
9880 bn(64,32). Because of instruction set limitations it doesn't have
9881 any negative impact on performance. This was done mostly in order
9882 to make it possible to share assembler modules, such as bn_mul_mont
9883 implementations, between 32- and 64-bit builds without hassle.
9887 * Move code previously exiled into file crypto/ec/ec2_smpt.c
9888 to ec2_smpl.c, and no longer require the OPENSSL_EC_BIN_PT_COMP
9893 * New candidate for BIGNUM assembler implementation, bn_mul_mont,
9894 dedicated Montgomery multiplication procedure, is introduced.
9895 BN_MONT_CTX is modified to allow bn_mul_mont to reach for higher
9896 "64-bit" performance on certain 32-bit targets.
9900 * New option SSL_OP_NO_COMP to disable use of compression selectively
9901 in SSL structures. New SSL ctrl to set maximum send fragment size.
9902 Save memory by setting the I/O buffer sizes dynamically instead of
9903 using the maximum available value.
9907 * New option -V for 'openssl ciphers'. This prints the ciphersuite code
9908 in addition to the text details.
9912 * Very, very preliminary EXPERIMENTAL support for printing of general
9913 ASN1 structures. This currently produces rather ugly output and doesn't
9914 handle several customised structures at all.
9918 * Integrated support for PVK file format and some related formats such
9919 as MS PUBLICKEYBLOB and PRIVATEKEYBLOB. Command line switches to support
9920 these in the 'rsa' and 'dsa' utilities.
9924 * Support for PKCS#1 RSAPublicKey format on rsa utility command line.
9928 * Remove the ancient ASN1_METHOD code. This was only ever used in one
9929 place for the (very old) "NETSCAPE" format certificates which are now
9930 handled using new ASN1 code equivalents.
9934 * Let the TLSv1_method() etc. functions return a 'const' SSL_METHOD
9935 pointer and make the SSL_METHOD parameter in SSL_CTX_new,
9936 SSL_CTX_set_ssl_version and SSL_set_ssl_method 'const'.
9940 * Modify CRL distribution points extension code to print out previously
9941 unsupported fields. Enhance extension setting code to allow setting of
9946 * Add print and set support for Issuing Distribution Point CRL extension.
9950 * Change 'Configure' script to enable Camellia by default.
9957 ### Changes between 0.9.8m and 0.9.8n [24 Mar 2010]
9959 * When rejecting SSL/TLS records due to an incorrect version number, never
9960 update s->server with a new major version number. As of
9961 - OpenSSL 0.9.8m if 'short' is a 16-bit type,
9962 - OpenSSL 0.9.8f if 'short' is longer than 16 bits,
9963 the previous behavior could result in a read attempt at NULL when
9964 receiving specific incorrect SSL/TLS records once record payload
9965 protection is active. ([CVE-2010-0740])
9967 *Bodo Moeller, Adam Langley <agl@chromium.org>*
9969 * Fix for CVE-2010-0433 where some kerberos enabled versions of OpenSSL
9970 could be crashed if the relevant tables were not present (e.g. chrooted).
9972 *Tomas Hoger <thoger@redhat.com>*
9974 ### Changes between 0.9.8l and 0.9.8m [25 Feb 2010]
9976 * Always check bn_wexpand() return values for failure. ([CVE-2009-3245])
9978 *Martin Olsson, Neel Mehta*
9980 * Fix X509_STORE locking: Every 'objs' access requires a lock (to
9981 accommodate for stack sorting, always a write lock!).
9985 * On some versions of WIN32 Heap32Next is very slow. This can cause
9986 excessive delays in the RAND_poll(): over a minute. As a workaround
9987 include a time check in the inner Heap32Next loop too.
9991 * The code that handled flushing of data in SSL/TLS originally used the
9992 BIO_CTRL_INFO ctrl to see if any data was pending first. This caused
9993 the problem outlined in PR#1949. The fix suggested there however can
9994 trigger problems with buggy BIO_CTRL_WPENDING (e.g. some versions
9995 of Apache). So instead simplify the code to flush unconditionally.
9996 This should be fine since flushing with no data to flush is a no op.
10000 * Handle TLS versions 2.0 and later properly and correctly use the
10001 highest version of TLS/SSL supported. Although TLS >= 2.0 is some way
10002 off ancient servers have a habit of sticking around for a while...
10006 * Modify compression code so it frees up structures without using the
10007 ex_data callbacks. This works around a problem where some applications
10008 call CRYPTO_cleanup_all_ex_data() before application exit (e.g. when
10009 restarting) then use compression (e.g. SSL with compression) later.
10010 This results in significant per-connection memory leaks and
10011 has caused some security issues including CVE-2008-1678 and
10016 * Constify crypto/cast (i.e., <openssl/cast.h>): a CAST_KEY doesn't
10017 change when encrypting or decrypting.
10021 * Add option SSL_OP_LEGACY_SERVER_CONNECT which will allow clients to
10022 connect and renegotiate with servers which do not support RI.
10023 Until RI is more widely deployed this option is enabled by default.
10027 * Add "missing" ssl ctrls to clear options and mode.
10031 * If client attempts to renegotiate and doesn't support RI respond with
10032 a no_renegotiation alert as required by RFC5746. Some renegotiating
10033 TLS clients will continue a connection gracefully when they receive
10034 the alert. Unfortunately OpenSSL mishandled this alert and would hang
10035 waiting for a server hello which it will never receive. Now we treat a
10036 received no_renegotiation alert as a fatal error. This is because
10037 applications requesting a renegotiation might well expect it to succeed
10038 and would have no code in place to handle the server denying it so the
10039 only safe thing to do is to terminate the connection.
10043 * Add ctrl macro SSL_get_secure_renegotiation_support() which returns 1 if
10044 peer supports secure renegotiation and 0 otherwise. Print out peer
10045 renegotiation support in s_client/s_server.
10049 * Replace the highly broken and deprecated SPKAC certification method with
10050 the updated NID creation version. This should correctly handle UTF8.
10054 * Implement RFC5746. Re-enable renegotiation but require the extension
10055 as needed. Unfortunately, SSL3_FLAGS_ALLOW_UNSAFE_LEGACY_RENEGOTIATION
10056 turns out to be a bad idea. It has been replaced by
10057 SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION which can be set with
10058 SSL_CTX_set_options(). This is really not recommended unless you
10059 know what you are doing.
10061 *Eric Rescorla <ekr@networkresonance.com>, Ben Laurie, Steve Henson*
10063 * Fixes to stateless session resumption handling. Use initial_ctx when
10064 issuing and attempting to decrypt tickets in case it has changed during
10065 servername handling. Use a non-zero length session ID when attempting
10066 stateless session resumption: this makes it possible to determine if
10067 a resumption has occurred immediately after receiving server hello
10068 (several places in OpenSSL subtly assume this) instead of later in
10073 * The functions ENGINE_ctrl(), OPENSSL_isservice(),
10074 CMS_get1_RecipientRequest() and RAND_bytes() can return <=0 on error
10075 fixes for a few places where the return code is not checked
10078 *Julia Lawall <julia@diku.dk>*
10080 * Add --strict-warnings option to Configure script to include devteam
10081 warnings in other configurations.
10085 * Add support for --libdir option and LIBDIR variable in makefiles. This
10086 makes it possible to install openssl libraries in locations which
10087 have names other than "lib", for example "/usr/lib64" which some
10090 *Steve Henson, based on patch from Jeremy Utley*
10092 * Don't allow the use of leading 0x80 in OIDs. This is a violation of
10093 X690 8.9.12 and can produce some misleading textual output of OIDs.
10095 *Steve Henson, reported by Dan Kaminsky*
10097 * Delete MD2 from algorithm tables. This follows the recommendation in
10098 several standards that it is not used in new applications due to
10099 several cryptographic weaknesses. For binary compatibility reasons
10100 the MD2 API is still compiled in by default.
10104 * Add compression id to {d2i,i2d}_SSL_SESSION so it is correctly saved
10109 * Rename uni2asc and asc2uni functions to OPENSSL_uni2asc and
10110 OPENSSL_asc2uni conditionally on Netware platforms to avoid a name
10113 *Guenter <lists@gknw.net>*
10115 * Fix the server certificate chain building code to use X509_verify_cert(),
10116 it used to have an ad-hoc builder which was unable to cope with anything
10117 other than a simple chain.
10119 *David Woodhouse <dwmw2@infradead.org>, Steve Henson*
10121 * Don't check self signed certificate signatures in X509_verify_cert()
10122 by default (a flag can override this): it just wastes time without
10123 adding any security. As a useful side effect self signed root CAs
10124 with non-FIPS digests are now usable in FIPS mode.
10128 * In dtls1_process_out_of_seq_message() the check if the current message
10129 is already buffered was missing. For every new message was memory
10130 allocated, allowing an attacker to perform an denial of service attack
10131 with sending out of seq handshake messages until there is no memory
10132 left. Additionally every future message was buffered, even if the
10133 sequence number made no sense and would be part of another handshake.
10134 So only messages with sequence numbers less than 10 in advance will be
10135 buffered. ([CVE-2009-1378])
10137 *Robin Seggelmann, discovered by Daniel Mentz*
10139 * Records are buffered if they arrive with a future epoch to be
10140 processed after finishing the corresponding handshake. There is
10141 currently no limitation to this buffer allowing an attacker to perform
10142 a DOS attack with sending records with future epochs until there is no
10143 memory left. This patch adds the pqueue_size() function to determine
10144 the size of a buffer and limits the record buffer to 100 entries.
10147 *Robin Seggelmann, discovered by Daniel Mentz*
10149 * Keep a copy of frag->msg_header.frag_len so it can be used after the
10150 parent structure is freed. ([CVE-2009-1379])
10154 * Handle non-blocking I/O properly in SSL_shutdown() call.
10156 *Darryl Miles <darryl-mailinglists@netbauds.net>*
10158 * Add `2.5.4.*` OIDs
10160 *Ilya O. <vrghost@gmail.com>*
10162 ### Changes between 0.9.8k and 0.9.8l [5 Nov 2009]
10164 * Disable renegotiation completely - this fixes a severe security
10165 problem ([CVE-2009-3555]) at the cost of breaking all
10166 renegotiation. Renegotiation can be re-enabled by setting
10167 SSL3_FLAGS_ALLOW_UNSAFE_LEGACY_RENEGOTIATION in s3->flags at
10168 run-time. This is really not recommended unless you know what
10173 ### Changes between 0.9.8j and 0.9.8k [25 Mar 2009]
10175 * Don't set val to NULL when freeing up structures, it is freed up by
10176 underlying code. If `sizeof(void *) > sizeof(long)` this can result in
10177 zeroing past the valid field. ([CVE-2009-0789])
10179 *Paolo Ganci <Paolo.Ganci@AdNovum.CH>*
10181 * Fix bug where return value of CMS_SignerInfo_verify_content() was not
10182 checked correctly. This would allow some invalid signed attributes to
10183 appear to verify correctly. ([CVE-2009-0591])
10185 *Ivan Nestlerode <inestlerode@us.ibm.com>*
10187 * Reject UniversalString and BMPString types with invalid lengths. This
10188 prevents a crash in ASN1_STRING_print_ex() which assumes the strings have
10189 a legal length. ([CVE-2009-0590])
10193 * Set S/MIME signing as the default purpose rather than setting it
10194 unconditionally. This allows applications to override it at the store
10199 * Permit restricted recursion of ASN1 strings. This is needed in practice
10200 to handle some structures.
10204 * Improve efficiency of mem_gets: don't search whole buffer each time
10207 *Jeremy Shapiro <jnshapir@us.ibm.com>*
10209 * New -hex option for openssl rand.
10213 * Print out UTF8String and NumericString when parsing ASN1.
10217 * Support NumericString type for name components.
10221 * Allow CC in the environment to override the automatically chosen
10222 compiler. Note that nothing is done to ensure flags work with the
10227 ### Changes between 0.9.8i and 0.9.8j [07 Jan 2009]
10229 * Properly check EVP_VerifyFinal() and similar return values
10232 *Ben Laurie, Bodo Moeller, Google Security Team*
10234 * Enable TLS extensions by default.
10238 * Allow the CHIL engine to be loaded, whether the application is
10239 multithreaded or not. (This does not release the developer from the
10240 obligation to set up the dynamic locking callbacks.)
10242 *Sander Temme <sander@temme.net>*
10244 * Use correct exit code if there is an error in dgst command.
10246 *Steve Henson; problem pointed out by Roland Dirlewanger*
10248 * Tweak Configure so that you need to say "experimental-jpake" to enable
10249 JPAKE, and need to use -DOPENSSL_EXPERIMENTAL_JPAKE in applications.
10253 * Add experimental JPAKE support, including demo authentication in
10254 s_client and s_server.
10258 * Set the comparison function in v3_addr_canonize().
10260 *Rob Austein <sra@hactrn.net>*
10262 * Add support for XMPP STARTTLS in s_client.
10264 *Philip Paeps <philip@freebsd.org>*
10266 * Change the server-side SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG behavior
10267 to ensure that even with this option, only ciphersuites in the
10268 server's preference list will be accepted. (Note that the option
10269 applies only when resuming a session, so the earlier behavior was
10270 just about the algorithm choice for symmetric cryptography.)
10274 ### Changes between 0.9.8h and 0.9.8i [15 Sep 2008]
10276 * Fix NULL pointer dereference if a DTLS server received
10277 ChangeCipherSpec as first record ([CVE-2009-1386]).
10281 * Fix a state transition in s3_srvr.c and d1_srvr.c
10282 (was using SSL3_ST_CW_CLNT_HELLO_B, should be `..._ST_SW_SRVR_...`).
10284 *Nagendra Modadugu*
10286 * The fix in 0.9.8c that supposedly got rid of unsafe
10287 double-checked locking was incomplete for RSA blinding,
10288 addressing just one layer of what turns out to have been
10289 doubly unsafe triple-checked locking.
10291 So now fix this for real by retiring the MONT_HELPER macro
10292 in crypto/rsa/rsa_eay.c.
10294 *Bodo Moeller; problem pointed out by Marius Schilder*
10296 * Various precautionary measures:
10298 - Avoid size_t integer overflow in HASH_UPDATE (md32_common.h).
10300 - Avoid a buffer overflow in d2i_SSL_SESSION() (ssl_asn1.c).
10301 (NB: This would require knowledge of the secret session ticket key
10302 to exploit, in which case you'd be SOL either way.)
10304 - Change bn_nist.c so that it will properly handle input BIGNUMs
10305 outside the expected range.
10307 - Enforce the 'num' check in BN_div() (bn_div.c) for non-BN_DEBUG
10310 *Neel Mehta, Bodo Moeller*
10312 * Allow engines to be "soft loaded" - i.e. optionally don't die if
10313 the load fails. Useful for distros.
10315 *Ben Laurie and the FreeBSD team*
10317 * Add support for Local Machine Keyset attribute in PKCS#12 files.
10321 * Fix BN_GF2m_mod_arr() top-bit cleanup code.
10325 * Expand ENGINE to support engine supplied SSL client certificate functions.
10327 This work was sponsored by Logica.
10331 * Add CryptoAPI ENGINE to support use of RSA and DSA keys held in Windows
10332 keystores. Support for SSL/TLS client authentication too.
10333 Not compiled unless enable-capieng specified to Configure.
10335 This work was sponsored by Logica.
10339 * Fix bug in X509_ATTRIBUTE creation: don't set attribute using
10340 ASN1_TYPE_set1 if MBSTRING flag set. This bug would crash certain
10341 attribute creation routines such as certificate requests and PKCS#12
10346 ### Changes between 0.9.8g and 0.9.8h [28 May 2008]
10348 * Fix flaw if 'Server Key exchange message' is omitted from a TLS
10349 handshake which could lead to a client crash as found using the
10350 Codenomicon TLS test suite ([CVE-2008-1672])
10352 *Steve Henson, Mark Cox*
10354 * Fix double free in TLS server name extensions which could lead to
10355 a remote crash found by Codenomicon TLS test suite ([CVE-2008-0891])
10359 * Clear error queue in SSL_CTX_use_certificate_chain_file()
10361 Clear the error queue to ensure that error entries left from
10362 older function calls do not interfere with the correct operation.
10364 *Lutz Jaenicke, Erik de Castro Lopo*
10366 * Remove root CA certificates of commercial CAs:
10368 The OpenSSL project does not recommend any specific CA and does not
10369 have any policy with respect to including or excluding any CA.
10370 Therefore, it does not make any sense to ship an arbitrary selection
10371 of root CA certificates with the OpenSSL software.
10375 * RSA OAEP patches to fix two separate invalid memory reads.
10376 The first one involves inputs when 'lzero' is greater than
10377 'SHA_DIGEST_LENGTH' (it would read about SHA_DIGEST_LENGTH bytes
10378 before the beginning of from). The second one involves inputs where
10379 the 'db' section contains nothing but zeroes (there is a one-byte
10380 invalid read after the end of 'db').
10382 *Ivan Nestlerode <inestlerode@us.ibm.com>*
10384 * Partial backport from 0.9.9-dev:
10386 Introduce bn_mul_mont (dedicated Montgomery multiplication
10387 procedure) as a candidate for BIGNUM assembler implementation.
10388 While 0.9.9-dev uses assembler for various architectures, only
10389 x86_64 is available by default here in the 0.9.8 branch, and
10390 32-bit x86 is available through a compile-time setting.
10392 To try the 32-bit x86 assembler implementation, use Configure
10393 option "enable-montasm" (which exists only for this backport).
10395 As "enable-montasm" for 32-bit x86 disclaims code stability
10396 anyway, in this constellation we activate additional code
10397 backported from 0.9.9-dev for further performance improvements,
10398 namely BN_from_montgomery_word. (To enable this otherwise,
10399 e.g. x86_64, try `-DMONT_FROM_WORD___NON_DEFAULT_0_9_8_BUILD`.)
10401 *Andy Polyakov (backport partially by Bodo Moeller)*
10403 * Add TLS session ticket callback. This allows an application to set
10404 TLS ticket cipher and HMAC keys rather than relying on hardcoded fixed
10405 values. This is useful for key rollover for example where several key
10406 sets may exist with different names.
10410 * Reverse ENGINE-internal logic for caching default ENGINE handles.
10411 This was broken until now in 0.9.8 releases, such that the only way
10412 a registered ENGINE could be used (assuming it initialises
10413 successfully on the host) was to explicitly set it as the default
10414 for the relevant algorithms. This is in contradiction with 0.9.7
10415 behaviour and the documentation. With this fix, when an ENGINE is
10416 registered into a given algorithm's table of implementations, the
10417 'uptodate' flag is reset so that auto-discovery will be used next
10418 time a new context for that algorithm attempts to select an
10421 *Ian Lister (tweaked by Geoff Thorpe)*
10423 * Backport of CMS code to OpenSSL 0.9.8. This differs from the 0.9.9
10424 implementation in the following ways:
10426 Lack of EVP_PKEY_ASN1_METHOD means algorithm parameters have to be
10429 Lack of BER streaming support means one pass streaming processing is
10430 only supported if data is detached: setting the streaming flag is
10431 ignored for embedded content.
10433 CMS support is disabled by default and must be explicitly enabled
10434 with the enable-cms configuration option.
10438 * Update the GMP engine glue to do direct copies between BIGNUM and
10439 mpz_t when openssl and GMP use the same limb size. Otherwise the
10440 existing "conversion via a text string export" trick is still used.
10442 *Paul Sheer <paulsheer@gmail.com>*
10444 * Zlib compression BIO. This is a filter BIO which compressed and
10445 uncompresses any data passed through it.
10449 * Add AES_wrap_key() and AES_unwrap_key() functions to implement
10450 RFC3394 compatible AES key wrapping.
10454 * Add utility functions to handle ASN1 structures. ASN1_STRING_set0():
10455 sets string data without copying. X509_ALGOR_set0() and
10456 X509_ALGOR_get0(): set and retrieve X509_ALGOR (AlgorithmIdentifier)
10457 data. Attribute function X509at_get0_data_by_OBJ(): retrieves data
10458 from an X509_ATTRIBUTE structure optionally checking it occurs only
10459 once. ASN1_TYPE_set1(): set and ASN1_TYPE structure copying supplied
10464 * Fix BN flag handling in RSA_eay_mod_exp() and BN_MONT_CTX_set()
10465 to get the expected BN_FLG_CONSTTIME behavior.
10467 *Bodo Moeller (Google)*
10471 - fixed wrong usage of ioctlsocket() when build for LIBC BSD sockets
10472 - fixed do_tests.pl to run the test suite with CLIB builds too (CLIB_OPT)
10473 - added some more tests to do_tests.pl
10474 - fixed RunningProcess usage so that it works with newer LIBC NDKs too
10475 - removed usage of BN_LLONG for CLIB builds to avoid runtime dependency
10476 - added new Configure targets netware-clib-bsdsock, netware-clib-gcc,
10477 netware-clib-bsdsock-gcc, netware-libc-bsdsock-gcc
10478 - various changes to netware.pl to enable gcc-cross builds on Win32
10480 - changed crypto/bio/b_sock.c to work with macro functions (CLIB BSD)
10481 - various changes to fix missing prototype warnings
10482 - fixed x86nasm.pl to create correct asm files for NASM COFF output
10483 - added AES, WHIRLPOOL and CPUID assembler code to build files
10484 - added missing AES assembler make rules to mk1mf.pl
10485 - fixed order of includes in `apps/ocsp.c` so that `e_os.h` settings apply
10487 *Guenter Knauf <eflash@gmx.net>*
10489 * Implement certificate status request TLS extension defined in RFC3546.
10490 A client can set the appropriate parameters and receive the encoded
10491 OCSP response via a callback. A server can query the supplied parameters
10492 and set the encoded OCSP response in the callback. Add simplified examples
10493 to s_client and s_server.
10497 ### Changes between 0.9.8f and 0.9.8g [19 Oct 2007]
10499 * Fix various bugs:
10500 + Binary incompatibility of ssl_ctx_st structure
10501 + DTLS interoperation with non-compliant servers
10502 + Don't call get_session_cb() without proposed session
10503 + Fix ia64 assembler code
10505 *Andy Polyakov, Steve Henson*
10507 ### Changes between 0.9.8e and 0.9.8f [11 Oct 2007]
10509 * DTLS Handshake overhaul. There were longstanding issues with
10510 OpenSSL DTLS implementation, which were making it impossible for
10511 RFC 4347 compliant client to communicate with OpenSSL server.
10512 Unfortunately just fixing these incompatibilities would "cut off"
10513 pre-0.9.8f clients. To allow for hassle free upgrade post-0.9.8e
10514 server keeps tolerating non RFC compliant syntax. The opposite is
10515 not true, 0.9.8f client can not communicate with earlier server.
10516 This update even addresses CVE-2007-4995.
10520 * Changes to avoid need for function casts in OpenSSL: some compilers
10521 (gcc 4.2 and later) reject their use.
10522 *Kurt Roeckx <kurt@roeckx.be>, Peter Hartley <pdh@utter.chaos.org.uk>,
10525 * Add RFC4507 support to OpenSSL. This includes the corrections in
10526 RFC4507bis. The encrypted ticket format is an encrypted encoded
10527 SSL_SESSION structure, that way new session features are automatically
10530 If a client application caches session in an SSL_SESSION structure
10531 support is transparent because tickets are now stored in the encoded
10534 The SSL_CTX structure automatically generates keys for ticket
10535 protection in servers so again support should be possible
10536 with no application modification.
10538 If a client or server wishes to disable RFC4507 support then the option
10539 SSL_OP_NO_TICKET can be set.
10541 Add a TLS extension debugging callback to allow the contents of any client
10542 or server extensions to be examined.
10544 This work was sponsored by Google.
10548 * Add initial support for TLS extensions, specifically for the server_name
10549 extension so far. The SSL_SESSION, SSL_CTX, and SSL data structures now
10550 have new members for a hostname. The SSL data structure has an
10551 additional member `SSL_CTX *initial_ctx` so that new sessions can be
10552 stored in that context to allow for session resumption, even after the
10553 SSL has been switched to a new SSL_CTX in reaction to a client's
10554 server_name extension.
10556 New functions (subject to change):
10558 SSL_get_servername()
10559 SSL_get_servername_type()
10562 New CTRL codes and macros (subject to change):
10564 SSL_CTRL_SET_TLSEXT_SERVERNAME_CB
10565 - SSL_CTX_set_tlsext_servername_callback()
10566 SSL_CTRL_SET_TLSEXT_SERVERNAME_ARG
10567 - SSL_CTX_set_tlsext_servername_arg()
10568 SSL_CTRL_SET_TLSEXT_HOSTNAME - SSL_set_tlsext_host_name()
10570 openssl s_client has a new '-servername ...' option.
10572 openssl s_server has new options '-servername_host ...', '-cert2 ...',
10573 '-key2 ...', '-servername_fatal' (subject to change). This allows
10574 testing the HostName extension for a specific single hostname ('-cert'
10575 and '-key' remain fallbacks for handshakes without HostName
10576 negotiation). If the unrecognized_name alert has to be sent, this by
10577 default is a warning; it becomes fatal with the '-servername_fatal'
10580 *Peter Sylvester, Remy Allais, Christophe Renou, Steve Henson*
10582 * Add AES and SSE2 assembly language support to VC++ build.
10586 * Mitigate attack on final subtraction in Montgomery reduction.
10590 * Fix crypto/ec/ec_mult.c to work properly with scalars of value 0
10591 (which previously caused an internal error).
10595 * Squeeze another 10% out of IGE mode when in != out.
10599 * AES IGE mode speedup.
10601 *Dean Gaudet (Google)*
10603 * Add the Korean symmetric 128-bit cipher SEED (see
10604 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>) and
10605 add SEED ciphersuites from RFC 4162:
10607 TLS_RSA_WITH_SEED_CBC_SHA = "SEED-SHA"
10608 TLS_DHE_DSS_WITH_SEED_CBC_SHA = "DHE-DSS-SEED-SHA"
10609 TLS_DHE_RSA_WITH_SEED_CBC_SHA = "DHE-RSA-SEED-SHA"
10610 TLS_DH_anon_WITH_SEED_CBC_SHA = "ADH-SEED-SHA"
10612 To minimize changes between patchlevels in the OpenSSL 0.9.8
10613 series, SEED remains excluded from compilation unless OpenSSL
10614 is configured with 'enable-seed'.
10616 *KISA, Bodo Moeller*
10618 * Mitigate branch prediction attacks, which can be practical if a
10619 single processor is shared, allowing a spy process to extract
10620 information. For detailed background information, see
10621 <http://eprint.iacr.org/2007/039> (O. Aciicmez, S. Gueron,
10622 J.-P. Seifert, "New Branch Prediction Vulnerabilities in OpenSSL
10623 and Necessary Software Countermeasures"). The core of the change
10624 are new versions BN_div_no_branch() and
10625 BN_mod_inverse_no_branch() of BN_div() and BN_mod_inverse(),
10626 respectively, which are slower, but avoid the security-relevant
10627 conditional branches. These are automatically called by BN_div()
10628 and BN_mod_inverse() if the flag BN_FLG_CONSTTIME is set for one
10629 of the input BIGNUMs. Also, BN_is_bit_set() has been changed to
10630 remove a conditional branch.
10632 BN_FLG_CONSTTIME is the new name for the previous
10633 BN_FLG_EXP_CONSTTIME flag, since it now affects more than just
10634 modular exponentiation. (Since OpenSSL 0.9.7h, setting this flag
10635 in the exponent causes BN_mod_exp_mont() to use the alternative
10636 implementation in BN_mod_exp_mont_consttime().) The old name
10637 remains as a deprecated alias.
10639 Similarly, RSA_FLAG_NO_EXP_CONSTTIME is replaced by a more general
10640 RSA_FLAG_NO_CONSTTIME flag since the RSA implementation now uses
10641 constant-time implementations for more than just exponentiation.
10642 Here too the old name is kept as a deprecated alias.
10644 BN_BLINDING_new() will now use BN_dup() for the modulus so that
10645 the BN_BLINDING structure gets an independent copy of the
10646 modulus. This means that the previous `BIGNUM *m` argument to
10647 BN_BLINDING_new() and to BN_BLINDING_create_param() now
10648 essentially becomes `const BIGNUM *m`, although we can't actually
10649 change this in the header file before 0.9.9. It allows
10650 RSA_setup_blinding() to use BN_with_flags() on the modulus to
10651 enable BN_FLG_CONSTTIME.
10653 *Matthew D Wood (Intel Corp)*
10655 * In the SSL/TLS server implementation, be strict about session ID
10656 context matching (which matters if an application uses a single
10657 external cache for different purposes). Previously,
10658 out-of-context reuse was forbidden only if SSL_VERIFY_PEER was
10659 set. This did ensure strict client verification, but meant that,
10660 with applications using a single external cache for quite
10661 different requirements, clients could circumvent ciphersuite
10662 restrictions for a given session ID context by starting a session
10663 in a different context.
10667 * Include "!eNULL" in SSL_DEFAULT_CIPHER_LIST to make sure that
10668 a ciphersuite string such as "DEFAULT:RSA" cannot enable
10669 authentication-only ciphersuites.
10673 * Update the SSL_get_shared_ciphers() fix CVE-2006-3738 which was
10674 not complete and could lead to a possible single byte overflow
10675 ([CVE-2007-5135]) [Ben Laurie]
10677 ### Changes between 0.9.8d and 0.9.8e [23 Feb 2007]
10679 * Since AES128 and AES256 (and similarly Camellia128 and
10680 Camellia256) share a single mask bit in the logic of
10681 ssl/ssl_ciph.c, the code for masking out disabled ciphers needs a
10682 kludge to work properly if AES128 is available and AES256 isn't
10683 (or if Camellia128 is available and Camellia256 isn't).
10687 * Fix the BIT STRING encoding generated by crypto/ec/ec_asn1.c
10688 (within i2d_ECPrivateKey, i2d_ECPKParameters, i2d_ECParameters):
10689 When a point or a seed is encoded in a BIT STRING, we need to
10690 prevent the removal of trailing zero bits to get the proper DER
10691 encoding. (By default, crypto/asn1/a_bitstr.c assumes the case
10692 of a NamedBitList, for which trailing 0 bits need to be removed.)
10696 * Have SSL/TLS server implementation tolerate "mismatched" record
10697 protocol version while receiving ClientHello even if the
10698 ClientHello is fragmented. (The server can't insist on the
10699 particular protocol version it has chosen before the ServerHello
10700 message has informed the client about his choice.)
10704 * Add RFC 3779 support.
10706 *Rob Austein for ARIN, Ben Laurie*
10708 * Load error codes if they are not already present instead of using a
10709 static variable. This allows them to be cleanly unloaded and reloaded.
10710 Improve header file function name parsing.
10714 * extend SMTP and IMAP protocol emulation in s_client to use EHLO
10715 or CAPABILITY handshake as required by RFCs.
10717 *Goetz Babin-Ebell*
10719 ### Changes between 0.9.8c and 0.9.8d [28 Sep 2006]
10721 * Introduce limits to prevent malicious keys being able to
10722 cause a denial of service. ([CVE-2006-2940])
10724 *Steve Henson, Bodo Moeller*
10726 * Fix ASN.1 parsing of certain invalid structures that can result
10727 in a denial of service. ([CVE-2006-2937]) [Steve Henson]
10729 * Fix buffer overflow in SSL_get_shared_ciphers() function.
10730 ([CVE-2006-3738]) [Tavis Ormandy and Will Drewry, Google Security Team]
10732 * Fix SSL client code which could crash if connecting to a
10733 malicious SSLv2 server. ([CVE-2006-4343])
10735 *Tavis Ormandy and Will Drewry, Google Security Team*
10737 * Since 0.9.8b, ciphersuite strings naming explicit ciphersuites
10738 match only those. Before that, "AES256-SHA" would be interpreted
10739 as a pattern and match "AES128-SHA" too (since AES128-SHA got
10740 the same strength classification in 0.9.7h) as we currently only
10741 have a single AES bit in the ciphersuite description bitmap.
10742 That change, however, also applied to ciphersuite strings such as
10743 "RC4-MD5" that intentionally matched multiple ciphersuites --
10744 namely, SSL 2.0 ciphersuites in addition to the more common ones
10745 from SSL 3.0/TLS 1.0.
10747 So we change the selection algorithm again: Naming an explicit
10748 ciphersuite selects this one ciphersuite, and any other similar
10749 ciphersuite (same bitmap) from *other* protocol versions.
10750 Thus, "RC4-MD5" again will properly select both the SSL 2.0
10751 ciphersuite and the SSL 3.0/TLS 1.0 ciphersuite.
10753 Since SSL 2.0 does not have any ciphersuites for which the
10754 128/256 bit distinction would be relevant, this works for now.
10755 The proper fix will be to use different bits for AES128 and
10756 AES256, which would have avoided the problems from the beginning;
10757 however, bits are scarce, so we can only do this in a new release
10758 (not just a patchlevel) when we can change the SSL_CIPHER
10759 definition to split the single 'unsigned long mask' bitmap into
10760 multiple values to extend the available space.
10764 ### Changes between 0.9.8b and 0.9.8c [05 Sep 2006]
10766 * Avoid PKCS #1 v1.5 signature attack discovered by Daniel Bleichenbacher
10767 ([CVE-2006-4339]) [Ben Laurie and Google Security Team]
10769 * Add AES IGE and biIGE modes.
10773 * Change the Unix randomness entropy gathering to use poll() when
10774 possible instead of select(), since the latter has some
10775 undesirable limitations.
10777 *Darryl Miles via Richard Levitte and Bodo Moeller*
10779 * Disable "ECCdraft" ciphersuites more thoroughly. Now special
10780 treatment in ssl/ssl_ciph.s makes sure that these ciphersuites
10781 cannot be implicitly activated as part of, e.g., the "AES" alias.
10782 However, please upgrade to OpenSSL 0.9.9[-dev] for
10783 non-experimental use of the ECC ciphersuites to get TLS extension
10784 support, which is required for curve and point format negotiation
10785 to avoid potential handshake problems.
10789 * Disable rogue ciphersuites:
10791 - SSLv2 0x08 0x00 0x80 ("RC4-64-MD5")
10792 - SSLv3/TLSv1 0x00 0x61 ("EXP1024-RC2-CBC-MD5")
10793 - SSLv3/TLSv1 0x00 0x60 ("EXP1024-RC4-MD5")
10795 The latter two were purportedly from
10796 draft-ietf-tls-56-bit-ciphersuites-0[01].txt, but do not really
10799 Also deactivate the remaining ciphersuites from
10800 draft-ietf-tls-56-bit-ciphersuites-01.txt. These are just as
10801 unofficial, and the ID has long expired.
10805 * Fix RSA blinding Heisenbug (problems sometimes occurred on
10806 dual-core machines) and other potential thread-safety issues.
10810 * Add the symmetric cipher Camellia (128-bit, 192-bit, 256-bit key
10811 versions), which is now available for royalty-free use
10812 (see <http://info.isl.ntt.co.jp/crypt/eng/info/chiteki.html>).
10813 Also, add Camellia TLS ciphersuites from RFC 4132.
10815 To minimize changes between patchlevels in the OpenSSL 0.9.8
10816 series, Camellia remains excluded from compilation unless OpenSSL
10817 is configured with 'enable-camellia'.
10821 * Disable the padding bug check when compression is in use. The padding
10822 bug check assumes the first packet is of even length, this is not
10823 necessarily true if compression is enabled and can result in false
10824 positives causing handshake failure. The actual bug test is ancient
10825 code so it is hoped that implementations will either have fixed it by
10826 now or any which still have the bug do not support compression.
10830 ### Changes between 0.9.8a and 0.9.8b [04 May 2006]
10832 * When applying a cipher rule check to see if string match is an explicit
10833 cipher suite and only match that one cipher suite if it is.
10837 * Link in manifests for VC++ if needed.
10839 *Austin Ziegler <halostatue@gmail.com>*
10841 * Update support for ECC-based TLS ciphersuites according to
10842 draft-ietf-tls-ecc-12.txt with proposed changes (but without
10843 TLS extensions, which are supported starting with the 0.9.9
10844 branch, not in the OpenSSL 0.9.8 branch).
10848 * New functions EVP_CIPHER_CTX_new() and EVP_CIPHER_CTX_free() to support
10849 opaque EVP_CIPHER_CTX handling.
10853 * Fixes and enhancements to zlib compression code. We now only use
10854 "zlib1.dll" and use the default `__cdecl` calling convention on Win32
10855 to conform with the standards mentioned here:
10856 <http://www.zlib.net/DLL_FAQ.txt>
10857 Static zlib linking now works on Windows and the new --with-zlib-include
10858 --with-zlib-lib options to Configure can be used to supply the location
10859 of the headers and library. Gracefully handle case where zlib library
10864 * Several fixes and enhancements to the OID generation code. The old code
10865 sometimes allowed invalid OIDs (1.X for X >= 40 for example), couldn't
10866 handle numbers larger than ULONG_MAX, truncated printing and had a
10867 non standard OBJ_obj2txt() behaviour.
10871 * Add support for building of engines under engine/ as shared libraries
10872 under VC++ build system.
10876 * Corrected the numerous bugs in the Win32 path splitter in DSO.
10877 Hopefully, we will not see any false combination of paths any more.
10881 ### Changes between 0.9.8 and 0.9.8a [11 Oct 2005]
10883 * Remove the functionality of SSL_OP_MSIE_SSLV2_RSA_PADDING
10884 (part of SSL_OP_ALL). This option used to disable the
10885 countermeasure against man-in-the-middle protocol-version
10886 rollback in the SSL 2.0 server implementation, which is a bad
10887 idea. ([CVE-2005-2969])
10889 *Bodo Moeller; problem pointed out by Yutaka Oiwa (Research Center
10890 for Information Security, National Institute of Advanced Industrial
10891 Science and Technology [AIST], Japan)*
10893 * Add two function to clear and return the verify parameter flags.
10897 * Keep cipherlists sorted in the source instead of sorting them at
10898 runtime, thus removing the need for a lock.
10902 * Avoid some small subgroup attacks in Diffie-Hellman.
10904 *Nick Mathewson and Ben Laurie*
10906 * Add functions for well-known primes.
10910 * Extended Windows CE support.
10912 *Satoshi Nakamura and Andy Polyakov*
10914 * Initialize SSL_METHOD structures at compile time instead of during
10915 runtime, thus removing the need for a lock.
10919 * Make PKCS7_decrypt() work even if no certificate is supplied by
10920 attempting to decrypt each encrypted key in turn. Add support to
10925 ### Changes between 0.9.7h and 0.9.8 [05 Jul 2005]
10927 [NB: OpenSSL 0.9.7i and later 0.9.7 patch levels were released after
10930 * Add libcrypto.pc and libssl.pc for those who feel they need them.
10934 * Change CA.sh and CA.pl so they don't bundle the CSR and the private
10935 key into the same file any more.
10939 * Add initial support for Win64, both IA64 and AMD64/x64 flavors.
10943 * Add -utf8 command line and config file option to 'ca'.
10945 *Stefan <stf@udoma.org*
10947 * Removed the macro des_crypt(), as it seems to conflict with some
10948 libraries. Use DES_crypt().
10952 * Correct naming of the 'chil' and '4758cca' ENGINEs. This
10953 involves renaming the source and generated shared-libs for
10954 both. The engines will accept the corrected or legacy ids
10955 ('ncipher' and '4758_cca' respectively) when binding. NB,
10956 this only applies when building 'shared'.
10958 *Corinna Vinschen <vinschen@redhat.com> and Geoff Thorpe*
10960 * Add attribute functions to EVP_PKEY structure. Modify
10961 PKCS12_create() to recognize a CSP name attribute and
10962 use it. Make -CSP option work again in pkcs12 utility.
10966 * Add new functionality to the bn blinding code:
10967 - automatic re-creation of the BN_BLINDING parameters after
10968 a fixed number of uses (currently 32)
10969 - add new function for parameter creation
10970 - introduce flags to control the update behaviour of the
10971 BN_BLINDING parameters
10972 - hide BN_BLINDING structure
10973 Add a second BN_BLINDING slot to the RSA structure to improve
10974 performance when a single RSA object is shared among several
10979 * Add support for DTLS.
10981 *Nagendra Modadugu <nagendra@cs.stanford.edu> and Ben Laurie*
10983 * Add support for DER encoded private keys (SSL_FILETYPE_ASN1)
10984 to SSL_CTX_use_PrivateKey_file() and SSL_use_PrivateKey_file()
10988 * Remove buggy and incomplete DH cert support from
10989 ssl/ssl_rsa.c and ssl/s3_both.c
10993 * Use SHA-1 instead of MD5 as the default digest algorithm for
10994 the `apps/openssl` commands.
10998 * Compile clean with "-Wall -Wmissing-prototypes
10999 -Wstrict-prototypes -Wmissing-declarations -Werror". Currently
11000 DEBUG_SAFESTACK must also be set.
11004 * Change ./Configure so that certain algorithms can be disabled by default.
11005 The new counterpiece to "no-xxx" is "enable-xxx".
11007 The patented RC5 and MDC2 algorithms will now be disabled unless
11008 "enable-rc5" and "enable-mdc2", respectively, are specified.
11010 (IDEA remains enabled despite being patented. This is because IDEA
11011 is frequently required for interoperability, and there is no license
11012 fee for non-commercial use. As before, "no-idea" can be used to
11013 avoid this algorithm.)
11017 * Add processing of proxy certificates (see RFC 3820). This work was
11018 sponsored by KTH (The Royal Institute of Technology in Stockholm) and
11019 EGEE (Enabling Grids for E-science in Europe).
11023 * RC4 performance overhaul on modern architectures/implementations, such
11024 as Intel P4, IA-64 and AMD64.
11028 * New utility extract-section.pl. This can be used specify an alternative
11029 section number in a pod file instead of having to treat each file as
11030 a separate case in Makefile. This can be done by adding two lines to the
11033 =for comment openssl_section:XXX
11035 The blank line is mandatory.
11039 * New arguments -certform, -keyform and -pass for s_client and s_server
11040 to allow alternative format key and certificate files and passphrase
11045 * New structure X509_VERIFY_PARAM which combines current verify parameters,
11046 update associated structures and add various utility functions.
11048 Add new policy related verify parameters, include policy checking in
11049 standard verify code. Enhance 'smime' application with extra parameters
11050 to support policy checking and print out.
11054 * Add a new engine to support VIA PadLock ACE extensions in the VIA C3
11055 Nehemiah processors. These extensions support AES encryption in hardware
11056 as well as RNG (though RNG support is currently disabled).
11058 *Michal Ludvig <michal@logix.cz>, with help from Andy Polyakov*
11060 * Deprecate `BN_[get|set]_params()` functions (they were ignored internally).
11064 * New FIPS 180-2 algorithms, SHA-224/-256/-384/-512 are implemented.
11066 *Andy Polyakov and a number of other people*
11068 * Improved PowerPC platform support. Most notably BIGNUM assembler
11069 implementation contributed by IBM.
11071 *Suresh Chari, Peter Waltenberg, Andy Polyakov*
11073 * The new 'RSA_generate_key_ex' function now takes a BIGNUM for the public
11074 exponent rather than 'unsigned long'. There is a corresponding change to
11075 the new 'rsa_keygen' element of the RSA_METHOD structure.
11077 *Jelte Jansen, Geoff Thorpe*
11079 * Functionality for creating the initial serial number file is now
11080 moved from CA.pl to the 'ca' utility with a new option -create_serial.
11082 (Before OpenSSL 0.9.7e, CA.pl used to initialize the serial
11083 number file to 1, which is bound to cause problems. To avoid
11084 the problems while respecting compatibility between different 0.9.7
11085 patchlevels, 0.9.7e employed 'openssl x509 -next_serial' in
11086 CA.pl for serial number initialization. With the new release 0.9.8,
11087 we can fix the problem directly in the 'ca' utility.)
11091 * Reduced header interdependencies by declaring more opaque objects in
11092 ossl_typ.h. As a consequence, including some headers (eg. engine.h) will
11093 give fewer recursive includes, which could break lazy source code - so
11094 this change is covered by the OPENSSL_NO_DEPRECATED symbol. As always,
11095 developers should define this symbol when building and using openssl to
11096 ensure they track the recommended behaviour, interfaces, [etc], but
11097 backwards-compatible behaviour prevails when this isn't defined.
11101 * New function X509_POLICY_NODE_print() which prints out policy nodes.
11105 * Add new EVP function EVP_CIPHER_CTX_rand_key and associated functionality.
11106 This will generate a random key of the appropriate length based on the
11107 cipher context. The EVP_CIPHER can provide its own random key generation
11108 routine to support keys of a specific form. This is used in the des and
11109 3des routines to generate a key of the correct parity. Update S/MIME
11110 code to use new functions and hence generate correct parity DES keys.
11111 Add EVP_CHECK_DES_KEY #define to return an error if the key is not
11112 valid (weak or incorrect parity).
11116 * Add a local set of CRLs that can be used by X509_verify_cert() as well
11117 as looking them up. This is useful when the verified structure may contain
11118 CRLs, for example PKCS#7 signedData. Modify PKCS7_verify() to use any CRLs
11119 present unless the new PKCS7_NO_CRL flag is asserted.
11123 * Extend ASN1 oid configuration module. It now additionally accepts the
11126 shortName = some long name, 1.2.3.4
11130 * Reimplemented the BN_CTX implementation. There is now no more static
11131 limitation on the number of variables it can handle nor the depth of the
11132 "stack" handling for BN_CTX_start()/BN_CTX_end() pairs. The stack
11133 information can now expand as required, and rather than having a single
11134 static array of bignums, BN_CTX now uses a linked-list of such arrays
11135 allowing it to expand on demand whilst maintaining the usefulness of
11136 BN_CTX's "bundling".
11140 * Add a missing BN_CTX parameter to the 'rsa_mod_exp' callback in RSA_METHOD
11141 to allow all RSA operations to function using a single BN_CTX.
11145 * Preliminary support for certificate policy evaluation and checking. This
11146 is initially intended to pass the tests outlined in "Conformance Testing
11147 of Relying Party Client Certificate Path Processing Logic" v1.07.
11151 * bn_dup_expand() has been deprecated, it was introduced in 0.9.7 and
11152 remained unused and not that useful. A variety of other little bignum
11153 tweaks and fixes have also been made continuing on from the audit (see
11158 * Constify all or almost all d2i, c2i, s2i and r2i functions, along with
11159 associated ASN1, EVP and SSL functions and old ASN1 macros.
11163 * BN_zero() only needs to set 'top' and 'neg' to zero for correct results,
11164 and this should never fail. So the return value from the use of
11165 BN_set_word() (which can fail due to needless expansion) is now deprecated;
11166 if OPENSSL_NO_DEPRECATED is defined, BN_zero() is a void macro.
11170 * BN_CTX_get() should return zero-valued bignums, providing the same
11171 initialised value as BN_new().
11173 *Geoff Thorpe, suggested by Ulf Möller*
11175 * Support for inhibitAnyPolicy certificate extension.
11179 * An audit of the BIGNUM code is underway, for which debugging code is
11180 enabled when BN_DEBUG is defined. This makes stricter enforcements on what
11181 is considered valid when processing BIGNUMs, and causes execution to
11182 assert() when a problem is discovered. If BN_DEBUG_RAND is defined,
11183 further steps are taken to deliberately pollute unused data in BIGNUM
11184 structures to try and expose faulty code further on. For now, openssl will
11185 (in its default mode of operation) continue to tolerate the inconsistent
11186 forms that it has tolerated in the past, but authors and packagers should
11187 consider trying openssl and their own applications when compiled with
11188 these debugging symbols defined. It will help highlight potential bugs in
11189 their own code, and will improve the test coverage for OpenSSL itself. At
11190 some point, these tighter rules will become openssl's default to improve
11191 maintainability, though the assert()s and other overheads will remain only
11192 in debugging configurations. See bn.h for more details.
11194 *Geoff Thorpe, Nils Larsch, Ulf Möller*
11196 * BN_CTX_init() has been deprecated, as BN_CTX is an opaque structure
11197 that can only be obtained through BN_CTX_new() (which implicitly
11198 initialises it). The presence of this function only made it possible
11199 to overwrite an existing structure (and cause memory leaks).
11203 * Because of the callback-based approach for implementing LHASH as a
11204 template type, lh_insert() adds opaque objects to hash-tables and
11205 lh_doall() or lh_doall_arg() are typically used with a destructor callback
11206 to clean up those corresponding objects before destroying the hash table
11207 (and losing the object pointers). So some over-zealous constifications in
11208 LHASH have been relaxed so that lh_insert() does not take (nor store) the
11209 objects as "const" and the `lh_doall[_arg]` callback wrappers are not
11210 prototyped to have "const" restrictions on the object pointers they are
11211 given (and so aren't required to cast them away any more).
11215 * The tmdiff.h API was so ugly and minimal that our own timing utility
11216 (speed) prefers to use its own implementation. The two implementations
11217 haven't been consolidated as yet (volunteers?) but the tmdiff API has had
11218 its object type properly exposed (MS_TM) instead of casting to/from
11219 `char *`. This may still change yet if someone realises MS_TM and
11221 aren't necessarily the greatest nomenclatures - but this is what was used
11222 internally to the implementation so I've used that for now.
11226 * Ensure that deprecated functions do not get compiled when
11227 OPENSSL_NO_DEPRECATED is defined. Some "openssl" subcommands and a few of
11228 the self-tests were still using deprecated key-generation functions so
11229 these have been updated also.
11233 * Reorganise PKCS#7 code to separate the digest location functionality
11234 into PKCS7_find_digest(), digest addition into PKCS7_bio_add_digest().
11235 New function PKCS7_set_digest() to set the digest type for PKCS#7
11236 digestedData type. Add additional code to correctly generate the
11237 digestedData type and add support for this type in PKCS7 initialization
11242 * New function PKCS7_set0_type_other() this initializes a PKCS7
11243 structure of type "other".
11247 * Fix prime generation loop in crypto/bn/bn_prime.pl by making
11248 sure the loop does correctly stop and breaking ("division by zero")
11249 modulus operations are not performed. The (pre-generated) prime
11250 table crypto/bn/bn_prime.h was already correct, but it could not be
11251 re-generated on some platforms because of the "division by zero"
11252 situation in the script.
11254 *Ralf S. Engelschall*
11256 * Update support for ECC-based TLS ciphersuites according to
11257 draft-ietf-tls-ecc-03.txt: the KDF1 key derivation function with
11258 SHA-1 now is only used for "small" curves (where the
11259 representation of a field element takes up to 24 bytes); for
11260 larger curves, the field element resulting from ECDH is directly
11261 used as premaster secret.
11263 *Douglas Stebila (Sun Microsystems Laboratories)*
11265 * Add code for kP+lQ timings to crypto/ec/ectest.c, and add SEC2
11266 curve secp160r1 to the tests.
11268 *Douglas Stebila (Sun Microsystems Laboratories)*
11270 * Add the possibility to load symbols globally with DSO.
11272 *Götz Babin-Ebell <babin-ebell@trustcenter.de> via Richard Levitte*
11274 * Add the functions ERR_set_mark() and ERR_pop_to_mark() for better
11275 control of the error stack.
11279 * Add support for STORE in ENGINE.
11283 * Add the STORE type. The intention is to provide a common interface
11284 to certificate and key stores, be they simple file-based stores, or
11285 HSM-type store, or LDAP stores, or...
11286 NOTE: The code is currently UNTESTED and isn't really used anywhere.
11290 * Add a generic structure called OPENSSL_ITEM. This can be used to
11291 pass a list of arguments to any function as well as provide a way
11292 for a function to pass data back to the caller.
11296 * Add the functions BUF_strndup() and BUF_memdup(). BUF_strndup()
11297 works like BUF_strdup() but can be used to duplicate a portion of
11298 a string. The copy gets NUL-terminated. BUF_memdup() duplicates
11303 * Add the function sk_find_ex() which works like sk_find(), but will
11304 return an index to an element even if an exact match couldn't be
11305 found. The index is guaranteed to point at the element where the
11306 searched-for key would be inserted to preserve sorting order.
11310 * Add the function OBJ_bsearch_ex() which works like OBJ_bsearch() but
11311 takes an extra flags argument for optional functionality. Currently,
11312 the following flags are defined:
11314 OBJ_BSEARCH_VALUE_ON_NOMATCH
11315 This one gets OBJ_bsearch_ex() to return a pointer to the first
11316 element where the comparing function returns a negative or zero
11319 OBJ_BSEARCH_FIRST_VALUE_ON_MATCH
11320 This one gets OBJ_bsearch_ex() to return a pointer to the first
11321 element where the comparing function returns zero. This is useful
11322 if there are more than one element where the comparing function
11327 * Make it possible to create self-signed certificates with 'openssl ca'
11328 in such a way that the self-signed certificate becomes part of the
11329 CA database and uses the same mechanisms for serial number generation
11330 as all other certificate signing. The new flag '-selfsign' enables
11331 this functionality. Adapt CA.sh and CA.pl.in.
11335 * Add functionality to check the public key of a certificate request
11336 against a given private. This is useful to check that a certificate
11337 request can be signed by that key (self-signing).
11341 * Make it possible to have multiple active certificates with the same
11342 subject in the CA index file. This is done only if the keyword
11343 'unique_subject' is set to 'no' in the main CA section (default
11344 if 'CA_default') of the configuration file. The value is saved
11345 with the database itself in a separate index attribute file,
11346 named like the index file with '.attr' appended to the name.
11350 * Generate multi-valued AVAs using '+' notation in config files for
11355 * Support for nameConstraints certificate extension.
11359 * Support for policyConstraints certificate extension.
11363 * Support for policyMappings certificate extension.
11367 * Make sure the default DSA_METHOD implementation only uses its
11368 dsa_mod_exp() and/or bn_mod_exp() handlers if they are non-NULL,
11369 and change its own handlers to be NULL so as to remove unnecessary
11370 indirection. This lets alternative implementations fallback to the
11371 default implementation more easily.
11375 * Support for directoryName in GeneralName related extensions
11380 * Make it possible to link applications using Makefile.shared.
11381 Make that possible even when linking against static libraries!
11385 * Support for single pass processing for S/MIME signing. This now
11386 means that S/MIME signing can be done from a pipe, in addition
11387 cleartext signing (multipart/signed type) is effectively streaming
11388 and the signed data does not need to be all held in memory.
11390 This is done with a new flag PKCS7_STREAM. When this flag is set
11391 PKCS7_sign() only initializes the PKCS7 structure and the actual signing
11392 is done after the data is output (and digests calculated) in
11393 SMIME_write_PKCS7().
11397 * Add full support for -rpath/-R, both in shared libraries and
11398 applications, at least on the platforms where it's known how
11403 * In crypto/ec/ec_mult.c, implement fast point multiplication with
11404 precomputation, based on wNAF splitting: EC_GROUP_precompute_mult()
11405 will now compute a table of multiples of the generator that
11406 makes subsequent invocations of EC_POINTs_mul() or EC_POINT_mul()
11407 faster (notably in the case of a single point multiplication,
11408 scalar * generator).
11410 *Nils Larsch, Bodo Moeller*
11412 * IPv6 support for certificate extensions. The various extensions
11413 which use the IP:a.b.c.d can now take IPv6 addresses using the
11414 formats of RFC1884 2.2 . IPv6 addresses are now also displayed
11419 * Added an ENGINE that implements RSA by performing private key
11420 exponentiations with the GMP library. The conversions to and from
11421 GMP's mpz_t format aren't optimised nor are any montgomery forms
11422 cached, and on x86 it appears OpenSSL's own performance has caught up.
11423 However there are likely to be other architectures where GMP could
11424 provide a boost. This ENGINE is not built in by default, but it can be
11425 specified at Configure time and should be accompanied by the necessary
11426 linker additions, eg;
11427 ./config -DOPENSSL_USE_GMP -lgmp
11431 * "openssl engine" will not display ENGINE/DSO load failure errors when
11432 testing availability of engines with "-t" - the old behaviour is
11433 produced by increasing the feature's verbosity with "-tt".
11437 * ECDSA routines: under certain error conditions uninitialized BN objects
11438 could be freed. Solution: make sure initialization is performed early
11439 enough. (Reported and fix supplied by Nils Larsch <nla@trustcenter.de>
11444 * Key-generation can now be implemented in RSA_METHOD, DSA_METHOD
11445 and DH_METHOD (eg. by ENGINE implementations) to override the normal
11446 software implementations. For DSA and DH, parameter generation can
11447 also be overridden by providing the appropriate method callbacks.
11451 * Change the "progress" mechanism used in key-generation and
11452 primality testing to functions that take a new BN_GENCB pointer in
11453 place of callback/argument pairs. The new API functions have `_ex`
11454 postfixes and the older functions are reimplemented as wrappers for
11455 the new ones. The OPENSSL_NO_DEPRECATED symbol can be used to hide
11456 declarations of the old functions to help (graceful) attempts to
11457 migrate to the new functions. Also, the new key-generation API
11458 functions operate on a caller-supplied key-structure and return
11459 success/failure rather than returning a key or NULL - this is to
11460 help make "keygen" another member function of RSA_METHOD etc.
11462 Example for using the new callback interface:
11464 int (*my_callback)(int a, int b, BN_GENCB *cb) = ...;
11465 void *my_arg = ...;
11468 BN_GENCB_set(&my_cb, my_callback, my_arg);
11470 return BN_is_prime_ex(some_bignum, BN_prime_checks, NULL, &cb);
11471 /* For the meaning of a, b in calls to my_callback(), see the
11472 * documentation of the function that calls the callback.
11473 * cb will point to my_cb; my_arg can be retrieved as cb->arg.
11474 * my_callback should return 1 if it wants BN_is_prime_ex()
11475 * to continue, or 0 to stop.
11480 * Change the ZLIB compression method to be stateful, and make it
11481 available to TLS with the number defined in
11482 draft-ietf-tls-compression-04.txt.
11486 * Add the ASN.1 structures and functions for CertificatePair, which
11487 is defined as follows (according to X.509_4thEditionDraftV6.pdf):
11489 CertificatePair ::= SEQUENCE {
11490 forward [0] Certificate OPTIONAL,
11491 reverse [1] Certificate OPTIONAL,
11492 -- at least one of the pair shall be present -- }
11494 Also implement the PEM functions to read and write certificate
11495 pairs, and defined the PEM tag as "CERTIFICATE PAIR".
11497 This needed to be defined, mostly for the sake of the LDAP
11498 attribute crossCertificatePair, but may prove useful elsewhere as
11503 * Make it possible to inhibit symlinking of shared libraries in
11504 Makefile.shared, for Cygwin's sake.
11508 * Extend the BIGNUM API by creating a function
11509 void BN_set_negative(BIGNUM *a, int neg);
11510 and a macro that behave like
11511 int BN_is_negative(const BIGNUM *a);
11513 to avoid the need to access 'a->neg' directly in applications.
11517 * Implement fast modular reduction for pseudo-Mersenne primes
11518 used in NIST curves (crypto/bn/bn_nist.c, crypto/ec/ecp_nist.c).
11519 EC_GROUP_new_curve_GFp() will now automatically use this
11522 *Nils Larsch <nla@trustcenter.de>*
11524 * Add new lock type (CRYPTO_LOCK_BN).
11528 * Change the ENGINE framework to automatically load engines
11529 dynamically from specific directories unless they could be
11530 found to already be built in or loaded. Move all the
11531 current engines except for the cryptodev one to a new
11532 directory engines/.
11533 The engines in engines/ are built as shared libraries if
11534 the "shared" options was given to ./Configure or ./config.
11535 Otherwise, they are inserted in libcrypto.a.
11536 /usr/local/ssl/engines is the default directory for dynamic
11537 engines, but that can be overridden at configure time through
11538 the usual use of --prefix and/or --openssldir, and at run
11539 time with the environment variable OPENSSL_ENGINES.
11541 *Geoff Thorpe and Richard Levitte*
11543 * Add Makefile.shared, a helper makefile to build shared
11544 libraries. Adapt Makefile.org.
11548 * Add version info to Win32 DLLs.
11550 *Peter 'Luna' Runestig" <peter@runestig.com>*
11552 * Add new 'medium level' PKCS#12 API. Certificates and keys
11553 can be added using this API to created arbitrary PKCS#12
11554 files while avoiding the low-level API.
11556 New options to PKCS12_create(), key or cert can be NULL and
11557 will then be omitted from the output file. The encryption
11558 algorithm NIDs can be set to -1 for no encryption, the mac
11559 iteration count can be set to 0 to omit the mac.
11561 Enhance pkcs12 utility by making the -nokeys and -nocerts
11562 options work when creating a PKCS#12 file. New option -nomac
11563 to omit the mac, NONE can be set for an encryption algorithm.
11564 New code is modified to use the enhanced PKCS12_create()
11565 instead of the low-level API.
11569 * Extend ASN1 encoder to support indefinite length constructed
11570 encoding. This can output sequences tags and octet strings in
11571 this form. Modify pk7_asn1.c to support indefinite length
11572 encoding. This is experimental and needs additional code to
11573 be useful, such as an ASN1 bio and some enhanced streaming
11576 Extend template encode functionality so that tagging is passed
11577 down to the template encoder.
11581 * Let 'openssl req' fail if an argument to '-newkey' is not
11582 recognized instead of using RSA as a default.
11586 * Add support for ECC-based ciphersuites from draft-ietf-tls-ecc-01.txt.
11587 As these are not official, they are not included in "ALL";
11588 the "ECCdraft" ciphersuite group alias can be used to select them.
11590 *Vipul Gupta and Sumit Gupta (Sun Microsystems Laboratories)*
11592 * Add ECDH engine support.
11594 *Nils Gura and Douglas Stebila (Sun Microsystems Laboratories)*
11596 * Add ECDH in new directory crypto/ecdh/.
11598 *Douglas Stebila (Sun Microsystems Laboratories)*
11600 * Let BN_rand_range() abort with an error after 100 iterations
11601 without success (which indicates a broken PRNG).
11605 * Change BN_mod_sqrt() so that it verifies that the input value
11606 is really the square of the return value. (Previously,
11607 BN_mod_sqrt would show GIGO behaviour.)
11611 * Add named elliptic curves over binary fields from X9.62, SECG,
11612 and WAP/WTLS; add OIDs that were still missing.
11614 *Sheueling Chang Shantz and Douglas Stebila (Sun Microsystems Laboratories)*
11616 * Extend the EC library for elliptic curves over binary fields
11617 (new files ec2_smpl.c, ec2_smpt.c, ec2_mult.c in crypto/ec/).
11620 EC_GF2m_simple_method
11624 EC_GROUP_new_curve_GF2m
11625 EC_GROUP_set_curve_GF2m
11626 EC_GROUP_get_curve_GF2m
11627 EC_POINT_set_affine_coordinates_GF2m
11628 EC_POINT_get_affine_coordinates_GF2m
11629 EC_POINT_set_compressed_coordinates_GF2m
11631 Point compression for binary fields is disabled by default for
11632 patent reasons (compile with OPENSSL_EC_BIN_PT_COMP defined to
11635 As binary polynomials are represented as BIGNUMs, various members
11636 of the EC_GROUP and EC_POINT data structures can be shared
11637 between the implementations for prime fields and binary fields;
11638 the above `..._GF2m functions` (except for EX_GROUP_new_curve_GF2m)
11639 are essentially identical to their `..._GFp` counterparts.
11640 (For simplicity, the `..._GFp` prefix has been dropped from
11641 various internal method names.)
11643 An internal 'field_div' method (similar to 'field_mul' and
11644 'field_sqr') has been added; this is used only for binary fields.
11646 *Sheueling Chang Shantz and Douglas Stebila (Sun Microsystems Laboratories)*
11648 * Optionally dispatch EC_POINT_mul(), EC_POINT_precompute_mult()
11649 through methods ('mul', 'precompute_mult').
11651 The generic implementations (now internally called 'ec_wNAF_mul'
11652 and 'ec_wNAF_precomputed_mult') remain the default if these
11653 methods are undefined.
11655 *Sheueling Chang Shantz and Douglas Stebila (Sun Microsystems Laboratories)*
11657 * New function EC_GROUP_get_degree, which is defined through
11658 EC_METHOD. For curves over prime fields, this returns the bit
11659 length of the modulus.
11661 *Sheueling Chang Shantz and Douglas Stebila (Sun Microsystems Laboratories)*
11663 * New functions EC_GROUP_dup, EC_POINT_dup.
11664 (These simply call ..._new and ..._copy).
11666 *Sheueling Chang Shantz and Douglas Stebila (Sun Microsystems Laboratories)*
11668 * Add binary polynomial arithmetic software in crypto/bn/bn_gf2m.c.
11669 Polynomials are represented as BIGNUMs (where the sign bit is not
11670 used) in the following functions [macros]:
11673 BN_GF2m_sub [= BN_GF2m_add]
11674 BN_GF2m_mod [wrapper for BN_GF2m_mod_arr]
11675 BN_GF2m_mod_mul [wrapper for BN_GF2m_mod_mul_arr]
11676 BN_GF2m_mod_sqr [wrapper for BN_GF2m_mod_sqr_arr]
11678 BN_GF2m_mod_exp [wrapper for BN_GF2m_mod_exp_arr]
11679 BN_GF2m_mod_sqrt [wrapper for BN_GF2m_mod_sqrt_arr]
11680 BN_GF2m_mod_solve_quad [wrapper for BN_GF2m_mod_solve_quad_arr]
11681 BN_GF2m_cmp [= BN_ucmp]
11683 (Note that only the 'mod' functions are actually for fields GF(2^m).
11684 BN_GF2m_add() is misnomer, but this is for the sake of consistency.)
11686 For some functions, an the irreducible polynomial defining a
11687 field can be given as an 'unsigned int[]' with strictly
11688 decreasing elements giving the indices of those bits that are set;
11689 i.e., p[] represents the polynomial
11690 f(t) = t^p[0] + t^p[1] + ... + t^p[k]
11692 p[0] > p[1] > ... > p[k] = 0.
11693 This applies to the following functions:
11696 BN_GF2m_mod_mul_arr
11697 BN_GF2m_mod_sqr_arr
11698 BN_GF2m_mod_inv_arr [wrapper for BN_GF2m_mod_inv]
11699 BN_GF2m_mod_div_arr [wrapper for BN_GF2m_mod_div]
11700 BN_GF2m_mod_exp_arr
11701 BN_GF2m_mod_sqrt_arr
11702 BN_GF2m_mod_solve_quad_arr
11706 Conversion can be performed by the following functions:
11711 bntest.c has additional tests for binary polynomial arithmetic.
11713 Two implementations for BN_GF2m_mod_div() are available.
11714 The default algorithm simply uses BN_GF2m_mod_inv() and
11715 BN_GF2m_mod_mul(). The alternative algorithm is compiled in only
11716 if OPENSSL_SUN_GF2M_DIV is defined (patent pending; read the
11717 copyright notice in crypto/bn/bn_gf2m.c before enabling it).
11719 *Sheueling Chang Shantz and Douglas Stebila (Sun Microsystems Laboratories)*
11721 * Add new error code 'ERR_R_DISABLED' that can be used when some
11722 functionality is disabled at compile-time.
11724 *Douglas Stebila <douglas.stebila@sun.com>*
11726 * Change default behaviour of 'openssl asn1parse' so that more
11727 information is visible when viewing, e.g., a certificate:
11729 Modify asn1_parse2 (crypto/asn1/asn1_par.c) so that in non-'dump'
11730 mode the content of non-printable OCTET STRINGs is output in a
11731 style similar to INTEGERs, but with '[HEX DUMP]' prepended to
11732 avoid the appearance of a printable string.
11734 *Nils Larsch <nla@trustcenter.de>*
11736 * Add 'asn1_flag' and 'asn1_form' member to EC_GROUP with access
11738 EC_GROUP_set_asn1_flag()
11739 EC_GROUP_get_asn1_flag()
11740 EC_GROUP_set_point_conversion_form()
11741 EC_GROUP_get_point_conversion_form()
11742 These control ASN1 encoding details:
11743 - Curves (i.e., groups) are encoded explicitly unless asn1_flag
11744 has been set to OPENSSL_EC_NAMED_CURVE.
11745 - Points are encoded in uncompressed form by default; options for
11746 asn1_for are as for point2oct, namely
11747 POINT_CONVERSION_COMPRESSED
11748 POINT_CONVERSION_UNCOMPRESSED
11749 POINT_CONVERSION_HYBRID
11751 Also add 'seed' and 'seed_len' members to EC_GROUP with access
11753 EC_GROUP_set_seed()
11754 EC_GROUP_get0_seed()
11755 EC_GROUP_get_seed_len()
11756 This is used only for ASN1 purposes (so far).
11758 *Nils Larsch <nla@trustcenter.de>*
11760 * Add 'field_type' member to EC_METHOD, which holds the NID
11761 of the appropriate field type OID. The new function
11762 EC_METHOD_get_field_type() returns this value.
11764 *Nils Larsch <nla@trustcenter.de>*
11767 EC_POINT_point2bn()
11768 EC_POINT_bn2point()
11769 EC_POINT_point2hex()
11770 EC_POINT_hex2point()
11771 providing useful interfaces to EC_POINT_point2oct() and
11772 EC_POINT_oct2point().
11774 *Nils Larsch <nla@trustcenter.de>*
11776 * Change internals of the EC library so that the functions
11777 EC_GROUP_set_generator()
11778 EC_GROUP_get_generator()
11779 EC_GROUP_get_order()
11780 EC_GROUP_get_cofactor()
11781 are implemented directly in crypto/ec/ec_lib.c and not dispatched
11782 to methods, which would lead to unnecessary code duplication when
11783 adding different types of curves.
11785 *Nils Larsch <nla@trustcenter.de> with input by Bodo Moeller*
11787 * Implement compute_wNAF (crypto/ec/ec_mult.c) without BIGNUM
11788 arithmetic, and such that modified wNAFs are generated
11789 (which avoid length expansion in many cases).
11793 * Add a function EC_GROUP_check_discriminant() (defined via
11794 EC_METHOD) that verifies that the curve discriminant is non-zero.
11796 Add a function EC_GROUP_check() that makes some sanity tests
11797 on a EC_GROUP, its generator and order. This includes
11798 EC_GROUP_check_discriminant().
11800 *Nils Larsch <nla@trustcenter.de>*
11802 * Add ECDSA in new directory crypto/ecdsa/.
11804 Add applications 'openssl ecparam' and 'openssl ecdsa'
11805 (these are based on 'openssl dsaparam' and 'openssl dsa').
11807 ECDSA support is also included in various other files across the
11808 library. Most notably,
11809 - 'openssl req' now has a '-newkey ecdsa:file' option;
11810 - EVP_PKCS82PKEY (crypto/evp/evp_pkey.c) now can handle ECDSA;
11811 - X509_PUBKEY_get (crypto/asn1/x_pubkey.c) and
11812 d2i_PublicKey (crypto/asn1/d2i_pu.c) have been modified to make
11813 them suitable for ECDSA where domain parameters must be
11814 extracted before the specific public key;
11815 - ECDSA engine support has been added.
11817 *Nils Larsch <nla@trustcenter.de>*
11819 * Include some named elliptic curves, and add OIDs from X9.62,
11820 SECG, and WAP/WTLS. Each curve can be obtained from the new
11822 EC_GROUP_new_by_curve_name(),
11823 and the list of available named curves can be obtained with
11824 EC_get_builtin_curves().
11825 Also add a 'curve_name' member to EC_GROUP objects, which can be
11827 EC_GROUP_set_curve_name()
11828 EC_GROUP_get_curve_name()
11830 *Nils Larsch <larsch@trustcenter.de, Bodo Moeller*
11832 * Remove a few calls to bn_wexpand() in BN_sqr() (the one in there
11833 was actually never needed) and in BN_mul(). The removal in BN_mul()
11834 required a small change in bn_mul_part_recursive() and the addition
11835 of the functions bn_cmp_part_words(), bn_sub_part_words() and
11836 bn_add_part_words(), which do the same thing as bn_cmp_words(),
11837 bn_sub_words() and bn_add_words() except they take arrays with
11842 ### Changes between 0.9.7l and 0.9.7m [23 Feb 2007]
11844 * Cleanse PEM buffers before freeing them since they may contain
11847 *Benjamin Bennett <ben@psc.edu>*
11849 * Include "!eNULL" in SSL_DEFAULT_CIPHER_LIST to make sure that
11850 a ciphersuite string such as "DEFAULT:RSA" cannot enable
11851 authentication-only ciphersuites.
11855 * Since AES128 and AES256 share a single mask bit in the logic of
11856 ssl/ssl_ciph.c, the code for masking out disabled ciphers needs a
11857 kludge to work properly if AES128 is available and AES256 isn't.
11861 * Expand security boundary to match 1.1.1 module.
11865 * Remove redundant features: hash file source, editing of test vectors
11866 modify fipsld to use external fips_premain.c signature.
11870 * New perl script mkfipsscr.pl to create shell scripts or batch files to
11871 run algorithm test programs.
11875 * Make algorithm test programs more tolerant of whitespace.
11879 * Have SSL/TLS server implementation tolerate "mismatched" record
11880 protocol version while receiving ClientHello even if the
11881 ClientHello is fragmented. (The server can't insist on the
11882 particular protocol version it has chosen before the ServerHello
11883 message has informed the client about his choice.)
11887 * Load error codes if they are not already present instead of using a
11888 static variable. This allows them to be cleanly unloaded and reloaded.
11892 ### Changes between 0.9.7k and 0.9.7l [28 Sep 2006]
11894 * Introduce limits to prevent malicious keys being able to
11895 cause a denial of service. ([CVE-2006-2940])
11897 *Steve Henson, Bodo Moeller*
11899 * Fix ASN.1 parsing of certain invalid structures that can result
11900 in a denial of service. ([CVE-2006-2937]) [Steve Henson]
11902 * Fix buffer overflow in SSL_get_shared_ciphers() function.
11903 ([CVE-2006-3738]) [Tavis Ormandy and Will Drewry, Google Security Team]
11905 * Fix SSL client code which could crash if connecting to a
11906 malicious SSLv2 server. ([CVE-2006-4343])
11908 *Tavis Ormandy and Will Drewry, Google Security Team*
11910 * Change ciphersuite string processing so that an explicit
11911 ciphersuite selects this one ciphersuite (so that "AES256-SHA"
11912 will no longer include "AES128-SHA"), and any other similar
11913 ciphersuite (same bitmap) from *other* protocol versions (so that
11914 "RC4-MD5" will still include both the SSL 2.0 ciphersuite and the
11915 SSL 3.0/TLS 1.0 ciphersuite). This is a backport combining
11916 changes from 0.9.8b and 0.9.8d.
11920 ### Changes between 0.9.7j and 0.9.7k [05 Sep 2006]
11922 * Avoid PKCS #1 v1.5 signature attack discovered by Daniel Bleichenbacher
11923 ([CVE-2006-4339]) [Ben Laurie and Google Security Team]
11925 * Change the Unix randomness entropy gathering to use poll() when
11926 possible instead of select(), since the latter has some
11927 undesirable limitations.
11929 *Darryl Miles via Richard Levitte and Bodo Moeller*
11931 * Disable rogue ciphersuites:
11933 - SSLv2 0x08 0x00 0x80 ("RC4-64-MD5")
11934 - SSLv3/TLSv1 0x00 0x61 ("EXP1024-RC2-CBC-MD5")
11935 - SSLv3/TLSv1 0x00 0x60 ("EXP1024-RC4-MD5")
11937 The latter two were purportedly from
11938 draft-ietf-tls-56-bit-ciphersuites-0[01].txt, but do not really
11941 Also deactivate the remaining ciphersuites from
11942 draft-ietf-tls-56-bit-ciphersuites-01.txt. These are just as
11943 unofficial, and the ID has long expired.
11947 * Fix RSA blinding Heisenbug (problems sometimes occurred on
11948 dual-core machines) and other potential thread-safety issues.
11952 ### Changes between 0.9.7i and 0.9.7j [04 May 2006]
11954 * Adapt fipsld and the build system to link against the validated FIPS
11955 module in FIPS mode.
11959 * Fixes for VC++ 2005 build under Windows.
11963 * Add new Windows build target VC-32-GMAKE for VC++. This uses GNU make
11964 from a Windows bash shell such as MSYS. It is autodetected from the
11965 "config" script when run from a VC++ environment. Modify standard VC++
11966 build to use fipscanister.o from the GNU make build.
11970 ### Changes between 0.9.7h and 0.9.7i [14 Oct 2005]
11972 * Wrapped the definition of EVP_MAX_MD_SIZE in a #ifdef OPENSSL_FIPS.
11973 The value now differs depending on if you build for FIPS or not.
11974 BEWARE! A program linked with a shared FIPSed libcrypto can't be
11975 safely run with a non-FIPSed libcrypto, as it may crash because of
11976 the difference induced by this change.
11980 ### Changes between 0.9.7g and 0.9.7h [11 Oct 2005]
11982 * Remove the functionality of SSL_OP_MSIE_SSLV2_RSA_PADDING
11983 (part of SSL_OP_ALL). This option used to disable the
11984 countermeasure against man-in-the-middle protocol-version
11985 rollback in the SSL 2.0 server implementation, which is a bad
11986 idea. ([CVE-2005-2969])
11988 *Bodo Moeller; problem pointed out by Yutaka Oiwa (Research Center
11989 for Information Security, National Institute of Advanced Industrial
11990 Science and Technology [AIST, Japan)]*
11992 * Minimal support for X9.31 signatures and PSS padding modes. This is
11993 mainly for FIPS compliance and not fully integrated at this stage.
11997 * For DSA signing, unless DSA_FLAG_NO_EXP_CONSTTIME is set, perform
11998 the exponentiation using a fixed-length exponent. (Otherwise,
11999 the information leaked through timing could expose the secret key
12000 after many signatures; cf. Bleichenbacher's attack on DSA with
12005 * Make a new fixed-window mod_exp implementation the default for
12006 RSA, DSA, and DH private-key operations so that the sequence of
12007 squares and multiplies and the memory access pattern are
12008 independent of the particular secret key. This will mitigate
12009 cache-timing and potential related attacks.
12011 BN_mod_exp_mont_consttime() is the new exponentiation implementation,
12012 and this is automatically used by BN_mod_exp_mont() if the new flag
12013 BN_FLG_EXP_CONSTTIME is set for the exponent. RSA, DSA, and DH
12014 will use this BN flag for private exponents unless the flag
12015 RSA_FLAG_NO_EXP_CONSTTIME, DSA_FLAG_NO_EXP_CONSTTIME, or
12016 DH_FLAG_NO_EXP_CONSTTIME, respectively, is set.
12018 *Matthew D Wood (Intel Corp), with some changes by Bodo Moeller*
12020 * Change the client implementation for SSLv23_method() and
12021 SSLv23_client_method() so that is uses the SSL 3.0/TLS 1.0
12022 Client Hello message format if the SSL_OP_NO_SSLv2 option is set.
12023 (Previously, the SSL 2.0 backwards compatible Client Hello
12024 message format would be used even with SSL_OP_NO_SSLv2.)
12028 * Add support for smime-type MIME parameter in S/MIME messages which some
12033 * New function BN_MONT_CTX_set_locked() to set montgomery parameters in
12034 a threadsafe manner. Modify rsa code to use new function and add calls
12035 to dsa and dh code (which had race conditions before).
12039 * Include the fixed error library code in the C error file definitions
12040 instead of fixing them up at runtime. This keeps the error code
12041 structures constant.
12045 ### Changes between 0.9.7f and 0.9.7g [11 Apr 2005]
12047 [NB: OpenSSL 0.9.7h and later 0.9.7 patch levels were released after
12050 * Fixes for newer kerberos headers. NB: the casts are needed because
12051 the 'length' field is signed on one version and unsigned on another
12052 with no (?) obvious way to tell the difference, without these VC++
12053 complains. Also the "definition" of FAR (blank) is no longer included
12054 nor is the error ENOMEM. KRB5_PRIVATE has to be set to 1 to pick up
12055 some needed definitions.
12059 * Undo Cygwin change.
12063 * Added support for proxy certificates according to RFC 3820.
12064 Because they may be a security thread to unaware applications,
12065 they must be explicitly allowed in run-time. See
12066 docs/HOWTO/proxy_certificates.txt for further information.
12070 ### Changes between 0.9.7e and 0.9.7f [22 Mar 2005]
12072 * Use (SSL_RANDOM_VALUE - 4) bytes of pseudo random data when generating
12073 server and client random values. Previously
12074 (SSL_RANDOM_VALUE - sizeof(time_t)) would be used which would result in
12075 less random data when sizeof(time_t) > 4 (some 64 bit platforms).
12077 This change has negligible security impact because:
12079 1. Server and client random values still have 24 bytes of pseudo random
12082 2. Server and client random values are sent in the clear in the initial
12085 3. The master secret is derived using the premaster secret (48 bytes in
12086 size for static RSA ciphersuites) as well as client server and random
12089 The OpenSSL team would like to thank the UK NISCC for bringing this issue
12092 *Stephen Henson, reported by UK NISCC*
12094 * Use Windows randomness collection on Cygwin.
12098 * Fix hang in EGD/PRNGD query when communication socket is closed
12099 prematurely by EGD/PRNGD.
12101 *Darren Tucker <dtucker@zip.com.au> via Lutz Jänicke, resolves #1014*
12103 * Prompt for pass phrases when appropriate for PKCS12 input format.
12107 * Back-port of selected performance improvements from development
12108 branch, as well as improved support for PowerPC platforms.
12112 * Add lots of checks for memory allocation failure, error codes to indicate
12113 failure and freeing up memory if a failure occurs.
12115 *Nauticus Networks SSL Team <openssl@nauticusnet.com>, Steve Henson*
12117 * Add new -passin argument to dgst.
12121 * Perform some character comparisons of different types in X509_NAME_cmp:
12122 this is needed for some certificates that re-encode DNs into UTF8Strings
12123 (in violation of RFC3280) and can't or won't issue name rollover
12128 * Make an explicit check during certificate validation to see that
12129 the CA setting in each certificate on the chain is correct. As a
12130 side effect always do the following basic checks on extensions,
12131 not just when there's an associated purpose to the check:
12133 - if there is an unhandled critical extension (unless the user
12134 has chosen to ignore this fault)
12135 - if the path length has been exceeded (if one is set at all)
12136 - that certain extensions fit the associated purpose (if one has
12141 ### Changes between 0.9.7d and 0.9.7e [25 Oct 2004]
12143 * Avoid a race condition when CRLs are checked in a multi threaded
12144 environment. This would happen due to the reordering of the revoked
12145 entries during signature checking and serial number lookup. Now the
12146 encoding is cached and the serial number sort performed under a lock.
12147 Add new STACK function sk_is_sorted().
12151 * Add Delta CRL to the extension code.
12155 * Various fixes to s3_pkt.c so alerts are sent properly.
12157 *David Holmes <d.holmes@f5.com>*
12159 * Reduce the chances of duplicate issuer name and serial numbers (in
12160 violation of RFC3280) using the OpenSSL certificate creation utilities.
12161 This is done by creating a random 64 bit value for the initial serial
12162 number when a serial number file is created or when a self signed
12163 certificate is created using 'openssl req -x509'. The initial serial
12164 number file is created using 'openssl x509 -next_serial' in CA.pl
12165 rather than being initialized to 1.
12169 ### Changes between 0.9.7c and 0.9.7d [17 Mar 2004]
12171 * Fix null-pointer assignment in do_change_cipher_spec() revealed
12172 by using the Codenomicon TLS Test Tool ([CVE-2004-0079])
12174 *Joe Orton, Steve Henson*
12176 * Fix flaw in SSL/TLS handshaking when using Kerberos ciphersuites
12179 *Joe Orton, Steve Henson*
12181 * Make it possible to have multiple active certificates with the same
12182 subject in the CA index file. This is done only if the keyword
12183 'unique_subject' is set to 'no' in the main CA section (default
12184 if 'CA_default') of the configuration file. The value is saved
12185 with the database itself in a separate index attribute file,
12186 named like the index file with '.attr' appended to the name.
12190 * X509 verify fixes. Disable broken certificate workarounds when
12191 X509_V_FLAGS_X509_STRICT is set. Check CRL issuer has cRLSign set if
12192 keyUsage extension present. Don't accept CRLs with unhandled critical
12193 extensions: since verify currently doesn't process CRL extensions this
12194 rejects a CRL with *any* critical extensions. Add new verify error codes
12199 * When creating an OCSP nonce use an OCTET STRING inside the extnValue.
12200 A clarification of RFC2560 will require the use of OCTET STRINGs and
12201 some implementations cannot handle the current raw format. Since OpenSSL
12202 copies and compares OCSP nonces as opaque blobs without any attempt at
12203 parsing them this should not create any compatibility issues.
12207 * New md flag EVP_MD_CTX_FLAG_REUSE this allows md_data to be reused when
12208 calling EVP_MD_CTX_copy_ex() to avoid calling OPENSSL_malloc(). Without
12209 this HMAC (and other) operations are several times slower than OpenSSL
12214 * Print out GeneralizedTime and UTCTime in ASN1_STRING_print_ex().
12216 *Peter Sylvester <Peter.Sylvester@EdelWeb.fr>*
12218 * Use the correct content when signing type "other".
12222 ### Changes between 0.9.7b and 0.9.7c [30 Sep 2003]
12224 * Fix various bugs revealed by running the NISCC test suite:
12226 Stop out of bounds reads in the ASN1 code when presented with
12227 invalid tags (CVE-2003-0543 and CVE-2003-0544).
12229 Free up ASN1_TYPE correctly if ANY type is invalid ([CVE-2003-0545]).
12231 If verify callback ignores invalid public key errors don't try to check
12232 certificate signature with the NULL public key.
12236 * New -ignore_err option in ocsp application to stop the server
12237 exiting on the first error in a request.
12241 * In ssl3_accept() (ssl/s3_srvr.c) only accept a client certificate
12242 if the server requested one: as stated in TLS 1.0 and SSL 3.0
12247 * In ssl3_get_client_hello() (ssl/s3_srvr.c), tolerate additional
12248 extra data after the compression methods not only for TLS 1.0
12249 but also for SSL 3.0 (as required by the specification).
12251 *Bodo Moeller; problem pointed out by Matthias Loepfe*
12253 * Change X509_certificate_type() to mark the key as exported/exportable
12254 when it's 512 *bits* long, not 512 bytes.
12258 * Change AES_cbc_encrypt() so it outputs exact multiple of
12259 blocks during encryption.
12263 * Various fixes to base64 BIO and non blocking I/O. On write
12264 flushes were not handled properly if the BIO retried. On read
12265 data was not being buffered properly and had various logic bugs.
12266 This also affects blocking I/O when the data being decoded is a
12271 * Various S/MIME bugfixes and compatibility changes:
12272 output correct application/pkcs7 MIME type if
12273 PKCS7_NOOLDMIMETYPE is set. Tolerate some broken signatures.
12274 Output CR+LF for EOL if PKCS7_CRLFEOL is set (this makes opening
12275 of files as .eml work). Correctly handle very long lines in MIME
12280 ### Changes between 0.9.7a and 0.9.7b [10 Apr 2003]
12282 * Countermeasure against the Klima-Pokorny-Rosa extension of
12283 Bleichbacher's attack on PKCS #1 v1.5 padding: treat
12284 a protocol version number mismatch like a decryption error
12285 in ssl3_get_client_key_exchange (ssl/s3_srvr.c).
12289 * Turn on RSA blinding by default in the default implementation
12290 to avoid a timing attack. Applications that don't want it can call
12291 RSA_blinding_off() or use the new flag RSA_FLAG_NO_BLINDING.
12292 They would be ill-advised to do so in most cases.
12294 *Ben Laurie, Steve Henson, Geoff Thorpe, Bodo Moeller*
12296 * Change RSA blinding code so that it works when the PRNG is not
12297 seeded (in this case, the secret RSA exponent is abused as
12298 an unpredictable seed -- if it is not unpredictable, there
12299 is no point in blinding anyway). Make RSA blinding thread-safe
12300 by remembering the creator's thread ID in rsa->blinding and
12301 having all other threads use local one-time blinding factors
12302 (this requires more computation than sharing rsa->blinding, but
12303 avoids excessive locking; and if an RSA object is not shared
12304 between threads, blinding will still be very fast).
12308 * Fixed a typo bug that would cause ENGINE_set_default() to set an
12309 ENGINE as defaults for all supported algorithms irrespective of
12310 the 'flags' parameter. 'flags' is now honoured, so applications
12311 should make sure they are passing it correctly.
12315 * Target "mingw" now allows native Windows code to be generated in
12316 the Cygwin environment as well as with the MinGW compiler.
12320 ### Changes between 0.9.7 and 0.9.7a [19 Feb 2003]
12322 * In ssl3_get_record (ssl/s3_pkt.c), minimize information leaked
12323 via timing by performing a MAC computation even if incorrect
12324 block cipher padding has been found. This is a countermeasure
12325 against active attacks where the attacker has to distinguish
12326 between bad padding and a MAC verification error. ([CVE-2003-0078])
12328 *Bodo Moeller; problem pointed out by Brice Canvel (EPFL),
12329 Alain Hiltgen (UBS), Serge Vaudenay (EPFL), and
12330 Martin Vuagnoux (EPFL, Ilion)*
12332 * Make the no-err option work as intended. The intention with no-err
12333 is not to have the whole error stack handling routines removed from
12334 libcrypto, it's only intended to remove all the function name and
12335 reason texts, thereby removing some of the footprint that may not
12336 be interesting if those errors aren't displayed anyway.
12338 NOTE: it's still possible for any application or module to have its
12339 own set of error texts inserted. The routines are there, just not
12340 used by default when no-err is given.
12344 * Add support for FreeBSD on IA64.
12346 *dirk.meyer@dinoex.sub.org via Richard Levitte, resolves #454*
12348 * Adjust DES_cbc_cksum() so it returns the same value as the MIT
12349 Kerberos function mit_des_cbc_cksum(). Before this change,
12350 the value returned by DES_cbc_cksum() was like the one from
12351 mit_des_cbc_cksum(), except the bytes were swapped.
12353 *Kevin Greaney <Kevin.Greaney@hp.com> and Richard Levitte*
12355 * Allow an application to disable the automatic SSL chain building.
12356 Before this a rather primitive chain build was always performed in
12357 ssl3_output_cert_chain(): an application had no way to send the
12358 correct chain if the automatic operation produced an incorrect result.
12360 Now the chain builder is disabled if either:
12362 1. Extra certificates are added via SSL_CTX_add_extra_chain_cert().
12364 2. The mode flag SSL_MODE_NO_AUTO_CHAIN is set.
12366 The reasoning behind this is that an application would not want the
12367 auto chain building to take place if extra chain certificates are
12368 present and it might also want a means of sending no additional
12369 certificates (for example the chain has two certificates and the
12374 * Add the possibility to build without the ENGINE framework.
12376 *Steven Reddie <smr@essemer.com.au> via Richard Levitte*
12378 * Under Win32 gmtime() can return NULL: check return value in
12379 OPENSSL_gmtime(). Add error code for case where gmtime() fails.
12383 * DSA routines: under certain error conditions uninitialized BN objects
12384 could be freed. Solution: make sure initialization is performed early
12385 enough. (Reported and fix supplied by Ivan D Nestlerode <nestler@MIT.EDU>,
12386 Nils Larsch <nla@trustcenter.de> via PR#459)
12390 * Another fix for SSLv2 session ID handling: the session ID was incorrectly
12391 checked on reconnect on the client side, therefore session resumption
12392 could still fail with a "ssl session id is different" error. This
12393 behaviour is masked when SSL_OP_ALL is used due to
12394 SSL_OP_MICROSOFT_SESS_ID_BUG being set.
12395 Behaviour observed by Crispin Flowerday <crispin@flowerday.cx> as
12396 followup to PR #377.
12400 * IA-32 assembler support enhancements: unified ELF targets, support
12401 for SCO/Caldera platforms, fix for Cygwin shared build.
12405 * Add support for FreeBSD on sparc64. As a consequence, support for
12406 FreeBSD on non-x86 processors is separate from x86 processors on
12407 the config script, much like the NetBSD support.
12409 *Richard Levitte & Kris Kennaway <kris@obsecurity.org>*
12411 ### Changes between 0.9.6h and 0.9.7 [31 Dec 2002]
12413 [NB: OpenSSL 0.9.6i and later 0.9.6 patch levels were released after
12416 * Fix session ID handling in SSLv2 client code: the SERVER FINISHED
12417 code (06) was taken as the first octet of the session ID and the last
12418 octet was ignored consequently. As a result SSLv2 client side session
12419 caching could not have worked due to the session ID mismatch between
12421 Behaviour observed by Crispin Flowerday <crispin@flowerday.cx> as
12426 * Change the declaration of needed Kerberos libraries to use EX_LIBS
12427 instead of the special (and badly supported) LIBKRB5. LIBKRB5 is
12432 * The hw_ncipher.c engine requires dynamic locks. Unfortunately, it
12433 seems that in spite of existing for more than a year, many application
12434 author have done nothing to provide the necessary callbacks, which
12435 means that this particular engine will not work properly anywhere.
12436 This is a very unfortunate situation which forces us, in the name
12437 of usability, to give the hw_ncipher.c a static lock, which is part
12439 NOTE: This is for the 0.9.7 series ONLY. This hack will never
12440 appear in 0.9.8 or later. We EXPECT application authors to have
12441 dealt properly with this when 0.9.8 is released (unless we actually
12442 make such changes in the libcrypto locking code that changes will
12443 have to be made anyway).
12447 * In asn1_d2i_read_bio() repeatedly call BIO_read() until all content
12448 octets have been read, EOF or an error occurs. Without this change
12449 some truncated ASN1 structures will not produce an error.
12453 * Disable Heimdal support, since it hasn't been fully implemented.
12454 Still give the possibility to force the use of Heimdal, but with
12455 warnings and a request that patches get sent to openssl-dev.
12459 * Add the VC-CE target, introduce the WINCE sysname, and add
12460 INSTALL.WCE and appropriate conditionals to make it build.
12462 *Steven Reddie <smr@essemer.com.au> via Richard Levitte*
12464 * Change the DLL names for Cygwin to cygcrypto-x.y.z.dll and
12465 cygssl-x.y.z.dll, where x, y and z are the major, minor and
12466 edit numbers of the version.
12468 *Corinna Vinschen <vinschen@redhat.com> and Richard Levitte*
12470 * Introduce safe string copy and catenation functions
12471 (BUF_strlcpy() and BUF_strlcat()).
12473 *Ben Laurie (CHATS) and Richard Levitte*
12475 * Avoid using fixed-size buffers for one-line DNs.
12477 *Ben Laurie (CHATS)*
12479 * Add BUF_MEM_grow_clean() to avoid information leakage when
12480 resizing buffers containing secrets, and use where appropriate.
12482 *Ben Laurie (CHATS)*
12484 * Avoid using fixed size buffers for configuration file location.
12486 *Ben Laurie (CHATS)*
12488 * Avoid filename truncation for various CA files.
12490 *Ben Laurie (CHATS)*
12492 * Use sizeof in preference to magic numbers.
12494 *Ben Laurie (CHATS)*
12496 * Avoid filename truncation in cert requests.
12498 *Ben Laurie (CHATS)*
12500 * Add assertions to check for (supposedly impossible) buffer
12503 *Ben Laurie (CHATS)*
12505 * Don't cache truncated DNS entries in the local cache (this could
12506 potentially lead to a spoofing attack).
12508 *Ben Laurie (CHATS)*
12510 * Fix various buffers to be large enough for hex/decimal
12511 representations in a platform independent manner.
12513 *Ben Laurie (CHATS)*
12515 * Add CRYPTO_realloc_clean() to avoid information leakage when
12516 resizing buffers containing secrets, and use where appropriate.
12518 *Ben Laurie (CHATS)*
12520 * Add BIO_indent() to avoid much slightly worrying code to do
12523 *Ben Laurie (CHATS)*
12525 * Convert sprintf()/BIO_puts() to BIO_printf().
12527 *Ben Laurie (CHATS)*
12529 * buffer_gets() could terminate with the buffer only half
12532 *Ben Laurie (CHATS)*
12534 * Add assertions to prevent user-supplied crypto functions from
12535 overflowing internal buffers by having large block sizes, etc.
12537 *Ben Laurie (CHATS)*
12539 * New OPENSSL_assert() macro (similar to assert(), but enabled
12542 *Ben Laurie (CHATS)*
12544 * Eliminate unused copy of key in RC4.
12546 *Ben Laurie (CHATS)*
12548 * Eliminate unused and incorrectly sized buffers for IV in pem.h.
12550 *Ben Laurie (CHATS)*
12552 * Fix off-by-one error in EGD path.
12554 *Ben Laurie (CHATS)*
12556 * If RANDFILE path is too long, ignore instead of truncating.
12558 *Ben Laurie (CHATS)*
12560 * Eliminate unused and incorrectly sized X.509 structure
12563 *Ben Laurie (CHATS)*
12565 * Eliminate unused and dangerous function knumber().
12567 *Ben Laurie (CHATS)*
12569 * Eliminate unused and dangerous structure, KSSL_ERR.
12571 *Ben Laurie (CHATS)*
12573 * Protect against overlong session ID context length in an encoded
12574 session object. Since these are local, this does not appear to be
12577 *Ben Laurie (CHATS)*
12579 * Change from security patch (see 0.9.6e below) that did not affect
12580 the 0.9.6 release series:
12582 Remote buffer overflow in SSL3 protocol - an attacker could
12583 supply an oversized master key in Kerberos-enabled versions.
12586 *Ben Laurie (CHATS)*
12588 * Change the SSL kerb5 codes to match RFC 2712.
12592 * Make -nameopt work fully for req and add -reqopt switch.
12594 *Michael Bell <michael.bell@rz.hu-berlin.de>, Steve Henson*
12596 * The "block size" for block ciphers in CFB and OFB mode should be 1.
12598 *Steve Henson, reported by Yngve Nysaeter Pettersen <yngve@opera.com>*
12600 * Make sure tests can be performed even if the corresponding algorithms
12601 have been removed entirely. This was also the last step to make
12602 OpenSSL compilable with DJGPP under all reasonable conditions.
12604 *Richard Levitte, Doug Kaufman <dkaufman@rahul.net>*
12606 * Add cipher selection rules COMPLEMENTOFALL and COMPLEMENTOFDEFAULT
12607 to allow version independent disabling of normally unselected ciphers,
12608 which may be activated as a side-effect of selecting a single cipher.
12610 (E.g., cipher list string "RSA" enables ciphersuites that are left
12611 out of "ALL" because they do not provide symmetric encryption.
12612 "RSA:!COMPLEMEMENTOFALL" avoids these unsafe ciphersuites.)
12614 *Lutz Jaenicke, Bodo Moeller*
12616 * Add appropriate support for separate platform-dependent build
12617 directories. The recommended way to make a platform-dependent
12618 build directory is the following (tested on Linux), maybe with
12621 # Place yourself outside of the OpenSSL source tree. In
12622 # this example, the environment variable OPENSSL_SOURCE
12623 # is assumed to contain the absolute OpenSSL source directory.
12624 mkdir -p objtree/"`uname -s`-`uname -r`-`uname -m`"
12625 cd objtree/"`uname -s`-`uname -r`-`uname -m`"
12626 (cd $OPENSSL_SOURCE; find . -type f) | while read F; do
12627 mkdir -p `dirname $F`
12628 ln -s $OPENSSL_SOURCE/$F $F
12631 To be absolutely sure not to disturb the source tree, a "make clean"
12632 is a good thing. If it isn't successful, don't worry about it,
12633 it probably means the source directory is very clean.
12637 * Make sure any ENGINE control commands make local copies of string
12638 pointers passed to them whenever necessary. Otherwise it is possible
12639 the caller may have overwritten (or deallocated) the original string
12640 data when a later ENGINE operation tries to use the stored values.
12642 *Götz Babin-Ebell <babinebell@trustcenter.de>*
12644 * Improve diagnostics in file reading and command-line digests.
12646 *Ben Laurie aided and abetted by Solar Designer <solar@openwall.com>*
12648 * Add AES modes CFB and OFB to the object database. Correct an
12649 error in AES-CFB decryption.
12653 * Remove most calls to EVP_CIPHER_CTX_cleanup() in evp_enc.c, this
12654 allows existing EVP_CIPHER_CTX structures to be reused after
12655 calling `EVP_*Final()`. This behaviour is used by encryption
12656 BIOs and some applications. This has the side effect that
12657 applications must explicitly clean up cipher contexts with
12658 EVP_CIPHER_CTX_cleanup() or they will leak memory.
12662 * Check the values of dna and dnb in bn_mul_recursive before calling
12663 bn_mul_comba (a non zero value means the a or b arrays do not contain
12664 n2 elements) and fallback to bn_mul_normal if either is not zero.
12668 * Fix escaping of non-ASCII characters when using the -subj option
12669 of the "openssl req" command line tool. (Robert Joop <joop@fokus.gmd.de>)
12673 * Make object definitions compliant to LDAP (RFC2256): SN is the short
12674 form for "surname", serialNumber has no short form.
12675 Use "mail" as the short name for "rfc822Mailbox" according to RFC2798;
12676 therefore remove "mail" short name for "internet 7".
12677 The OID for unique identifiers in X509 certificates is
12678 x500UniqueIdentifier, not uniqueIdentifier.
12679 Some more OID additions. (Michael Bell <michael.bell@rz.hu-berlin.de>)
12683 * Add an "init" command to the ENGINE config module and auto initialize
12684 ENGINEs. Without any "init" command the ENGINE will be initialized
12685 after all ctrl commands have been executed on it. If init=1 the
12686 ENGINE is initialized at that point (ctrls before that point are run
12687 on the uninitialized ENGINE and after on the initialized one). If
12688 init=0 then the ENGINE will not be initialized at all.
12692 * Fix the 'app_verify_callback' interface so that the user-defined
12693 argument is actually passed to the callback: In the
12694 SSL_CTX_set_cert_verify_callback() prototype, the callback
12695 declaration has been changed from
12698 int (*cb)(X509_STORE_CTX *,void *);
12699 in ssl_verify_cert_chain (ssl/ssl_cert.c), the call
12700 i=s->ctx->app_verify_callback(&ctx)
12701 has been changed into
12702 i=s->ctx->app_verify_callback(&ctx, s->ctx->app_verify_arg).
12704 To update applications using SSL_CTX_set_cert_verify_callback(),
12705 a dummy argument can be added to their callback functions.
12707 *D. K. Smetters <smetters@parc.xerox.com>*
12709 * Added the '4758cca' ENGINE to support IBM 4758 cards.
12711 *Maurice Gittens <maurice@gittens.nl>, touchups by Geoff Thorpe*
12713 * Add and OPENSSL_LOAD_CONF define which will cause
12714 OpenSSL_add_all_algorithms() to load the openssl.cnf config file.
12715 This allows older applications to transparently support certain
12716 OpenSSL features: such as crypto acceleration and dynamic ENGINE loading.
12717 Two new functions OPENSSL_add_all_algorithms_noconf() which will never
12718 load the config file and OPENSSL_add_all_algorithms_conf() which will
12719 always load it have also been added.
12723 * Add the OFB, CFB and CTR (all with 128 bit feedback) to AES.
12724 Adjust NIDs and EVP layer.
12726 *Stephen Sprunk <stephen@sprunk.org> and Richard Levitte*
12728 * Config modules support in openssl utility.
12730 Most commands now load modules from the config file,
12731 though in a few (such as version) this isn't done
12732 because it couldn't be used for anything.
12734 In the case of ca and req the config file used is
12735 the same as the utility itself: that is the -config
12736 command line option can be used to specify an
12741 * Move default behaviour from OPENSSL_config(). If appname is NULL
12742 use "openssl_conf" if filename is NULL use default openssl config file.
12746 * Add an argument to OPENSSL_config() to allow the use of an alternative
12747 config section name. Add a new flag to tolerate a missing config file
12748 and move code to CONF_modules_load_file().
12752 * Support for crypto accelerator cards from Accelerated Encryption
12753 Processing, www.aep.ie. (Use engine 'aep')
12754 The support was copied from 0.9.6c [engine] and adapted/corrected
12755 to work with the new engine framework.
12757 *AEP Inc. and Richard Levitte*
12759 * Support for SureWare crypto accelerator cards from Baltimore
12760 Technologies. (Use engine 'sureware')
12761 The support was copied from 0.9.6c [engine] and adapted
12762 to work with the new engine framework.
12766 * Have the CHIL engine fork-safe (as defined by nCipher) and actually
12767 make the newer ENGINE framework commands for the CHIL engine work.
12769 *Toomas Kiisk <vix@cyber.ee> and Richard Levitte*
12771 * Make it possible to produce shared libraries on ReliantUNIX.
12773 *Robert Dahlem <Robert.Dahlem@ffm2.siemens.de> via Richard Levitte*
12775 * Add the configuration target debug-linux-ppro.
12776 Make 'openssl rsa' use the general key loading routines
12777 implemented in `apps.c`, and make those routines able to
12778 handle the key format FORMAT_NETSCAPE and the variant
12781 *Toomas Kiisk <vix@cyber.ee> via Richard Levitte*
12783 * Fix a crashbug and a logic bug in hwcrhk_load_pubkey().
12785 *Toomas Kiisk <vix@cyber.ee> via Richard Levitte*
12787 * Add -keyform to rsautl, and document -engine.
12789 *Richard Levitte, inspired by Toomas Kiisk <vix@cyber.ee>*
12791 * Change BIO_new_file (crypto/bio/bss_file.c) to use new
12792 BIO_R_NO_SUCH_FILE error code rather than the generic
12793 ERR_R_SYS_LIB error code if fopen() fails with ENOENT.
12797 * Add new functions
12798 ERR_peek_last_error
12799 ERR_peek_last_error_line
12800 ERR_peek_last_error_line_data.
12801 These are similar to
12803 ERR_peek_error_line
12804 ERR_peek_error_line_data,
12805 but report on the latest error recorded rather than the first one
12806 still in the error queue.
12808 *Ben Laurie, Bodo Moeller*
12810 * default_algorithms option in ENGINE config module. This allows things
12812 default_algorithms = ALL
12813 default_algorithms = RSA, DSA, RAND, CIPHERS, DIGESTS
12817 * Preliminary ENGINE config module.
12821 * New experimental application configuration code.
12825 * Change the AES code to follow the same name structure as all other
12826 symmetric ciphers, and behave the same way. Move everything to
12827 the directory crypto/aes, thereby obsoleting crypto/rijndael.
12829 *Stephen Sprunk <stephen@sprunk.org> and Richard Levitte*
12831 * SECURITY: remove unsafe setjmp/signal interaction from ui_openssl.c.
12833 *Ben Laurie and Theo de Raadt*
12835 * Add option to output public keys in req command.
12837 *Massimiliano Pala madwolf@openca.org*
12839 * Use wNAFs in EC_POINTs_mul() for improved efficiency
12840 (up to about 10% better than before for P-192 and P-224).
12844 * New functions/macros
12846 SSL_CTX_set_msg_callback(ctx, cb)
12847 SSL_CTX_set_msg_callback_arg(ctx, arg)
12848 SSL_set_msg_callback(ssl, cb)
12849 SSL_set_msg_callback_arg(ssl, arg)
12851 to request calling a callback function
12853 void cb(int write_p, int version, int content_type,
12854 const void *buf, size_t len, SSL *ssl, void *arg)
12856 whenever a protocol message has been completely received
12857 (write_p == 0) or sent (write_p == 1). Here 'version' is the
12858 protocol version according to which the SSL library interprets
12859 the current protocol message (SSL2_VERSION, SSL3_VERSION, or
12860 TLS1_VERSION). 'content_type' is 0 in the case of SSL 2.0, or
12861 the content type as defined in the SSL 3.0/TLS 1.0 protocol
12862 specification (change_cipher_spec(20), alert(21), handshake(22)).
12863 'buf' and 'len' point to the actual message, 'ssl' to the
12864 SSL object, and 'arg' is the application-defined value set by
12865 SSL[_CTX]_set_msg_callback_arg().
12867 'openssl s_client' and 'openssl s_server' have new '-msg' options
12868 to enable a callback that displays all protocol messages.
12872 * Change the shared library support so shared libraries are built as
12873 soon as the corresponding static library is finished, and thereby get
12874 openssl and the test programs linked against the shared library.
12875 This still only happens when the keyword "shard" has been given to
12876 the configuration scripts.
12878 NOTE: shared library support is still an experimental thing, and
12879 backward binary compatibility is still not guaranteed.
12881 *"Maciej W. Rozycki" <macro@ds2.pg.gda.pl> and Richard Levitte*
12883 * Add support for Subject Information Access extension.
12885 *Peter Sylvester <Peter.Sylvester@EdelWeb.fr>*
12887 * Make BUF_MEM_grow() behaviour more consistent: Initialise to zero
12888 additional bytes when new memory had to be allocated, not just
12889 when reusing an existing buffer.
12893 * New command line and configuration option 'utf8' for the req command.
12894 This allows field values to be specified as UTF8 strings.
12898 * Add -multi and -mr options to "openssl speed" - giving multiple parallel
12899 runs for the former and machine-readable output for the latter.
12903 * Add '-noemailDN' option to 'openssl ca'. This prevents inclusion
12904 of the e-mail address in the DN (i.e., it will go into a certificate
12905 extension only). The new configuration file option 'email_in_dn = no'
12906 has the same effect.
12908 *Massimiliano Pala madwolf@openca.org*
12910 * Change all functions with names starting with `des_` to be starting
12911 with `DES_` instead. Add wrappers that are compatible with libdes,
12912 but are named `_ossl_old_des_*`. Finally, add macros that map the
12913 `des_*` symbols to the corresponding `_ossl_old_des_*` if libdes
12914 compatibility is desired. If OpenSSL 0.9.6c compatibility is
12915 desired, the `des_*` symbols will be mapped to `DES_*`, with one
12918 Since we provide two compatibility mappings, the user needs to
12919 define the macro OPENSSL_DES_LIBDES_COMPATIBILITY if libdes
12920 compatibility is desired. The default (i.e., when that macro
12921 isn't defined) is OpenSSL 0.9.6c compatibility.
12923 There are also macros that enable and disable the support of old
12924 des functions altogether. Those are OPENSSL_ENABLE_OLD_DES_SUPPORT
12925 and OPENSSL_DISABLE_OLD_DES_SUPPORT. If none or both of those
12926 are defined, the default will apply: to support the old des routines.
12928 In either case, one must include openssl/des.h to get the correct
12929 definitions. Do not try to just include openssl/des_old.h, that
12932 NOTE: This is a major break of an old API into a new one. Software
12933 authors are encouraged to switch to the `DES_` style functions. Some
12934 time in the future, des_old.h and the libdes compatibility functions
12935 will be disable (i.e. OPENSSL_DISABLE_OLD_DES_SUPPORT will be the
12936 default), and then completely removed.
12940 * Test for certificates which contain unsupported critical extensions.
12941 If such a certificate is found during a verify operation it is
12942 rejected by default: this behaviour can be overridden by either
12943 handling the new error X509_V_ERR_UNHANDLED_CRITICAL_EXTENSION or
12944 by setting the verify flag X509_V_FLAG_IGNORE_CRITICAL. A new function
12945 X509_supported_extension() has also been added which returns 1 if a
12946 particular extension is supported.
12950 * Modify the behaviour of EVP cipher functions in similar way to digests
12951 to retain compatibility with existing code.
12955 * Modify the behaviour of EVP_DigestInit() and EVP_DigestFinal() to retain
12956 compatibility with existing code. In particular the 'ctx' parameter does
12957 not have to be to be initialized before the call to EVP_DigestInit() and
12958 it is tidied up after a call to EVP_DigestFinal(). New function
12959 EVP_DigestFinal_ex() which does not tidy up the ctx. Similarly function
12960 EVP_MD_CTX_copy() changed to not require the destination to be
12961 initialized valid and new function EVP_MD_CTX_copy_ex() added which
12962 requires the destination to be valid.
12964 Modify all the OpenSSL digest calls to use EVP_DigestInit_ex(),
12965 EVP_DigestFinal_ex() and EVP_MD_CTX_copy_ex().
12969 * Change ssl3_get_message (ssl/s3_both.c) and the functions using it
12970 so that complete 'Handshake' protocol structures are kept in memory
12971 instead of overwriting 'msg_type' and 'length' with 'body' data.
12975 * Add an implementation of SSL_add_dir_cert_subjects_to_stack for Win32.
12977 *Massimo Santin via Richard Levitte*
12979 * Major restructuring to the underlying ENGINE code. This includes
12980 reduction of linker bloat, separation of pure "ENGINE" manipulation
12981 (initialisation, etc) from functionality dealing with implementations
12982 of specific crypto interfaces. This change also introduces integrated
12983 support for symmetric ciphers and digest implementations - so ENGINEs
12984 can now accelerate these by providing EVP_CIPHER and EVP_MD
12985 implementations of their own. This is detailed in
12986 [crypto/engine/README.md](crypto/engine/README.md)
12987 as it couldn't be adequately described here. However, there are a few
12988 API changes worth noting - some RSA, DSA, DH, and RAND functions that
12989 were changed in the original introduction of ENGINE code have now
12990 reverted back - the hooking from this code to ENGINE is now a good
12991 deal more passive and at run-time, operations deal directly with
12992 RSA_METHODs, DSA_METHODs (etc) as they did before, rather than
12993 dereferencing through an ENGINE pointer any more. Also, the ENGINE
12994 functions dealing with `BN_MOD_EXP[_CRT]` handlers have been removed -
12995 they were not being used by the framework as there is no concept of a
12996 BIGNUM_METHOD and they could not be generalised to the new
12997 'ENGINE_TABLE' mechanism that underlies the new code. Similarly,
12998 ENGINE_cpy() has been removed as it cannot be consistently defined in
13003 * Change ASN1_GENERALIZEDTIME_check() to allow fractional seconds.
13007 * Change mkdef.pl to sort symbols that get the same entry number,
13008 and make sure the automatically generated functions `ERR_load_*`
13009 become part of libeay.num as well.
13013 * New function SSL_renegotiate_pending(). This returns true once
13014 renegotiation has been requested (either SSL_renegotiate() call
13015 or HelloRequest/ClientHello received from the peer) and becomes
13016 false once a handshake has been completed.
13017 (For servers, SSL_renegotiate() followed by SSL_do_handshake()
13018 sends a HelloRequest, but does not ensure that a handshake takes
13019 place. SSL_renegotiate_pending() is useful for checking if the
13020 client has followed the request.)
13024 * New SSL option SSL_OP_NO_SESSION_RESUMPTION_ON_RENEGOTIATION.
13025 By default, clients may request session resumption even during
13026 renegotiation (if session ID contexts permit); with this option,
13027 session resumption is possible only in the first handshake.
13029 SSL_OP_ALL is now 0x00000FFFL instead of 0x000FFFFFL. This makes
13030 more bits available for options that should not be part of
13031 SSL_OP_ALL (such as SSL_OP_NO_SESSION_RESUMPTION_ON_RENEGOTIATION).
13035 * Add some demos for certificate and certificate request creation.
13039 * Make maximum certificate chain size accepted from the peer application
13040 settable (`SSL*_get/set_max_cert_list()`), as proposed by
13041 "Douglas E. Engert" <deengert@anl.gov>.
13045 * Add support for shared libraries for Unixware-7
13046 (Boyd Lynn Gerber <gerberb@zenez.com>).
13050 * Add a "destroy" handler to ENGINEs that allows structural cleanup to
13051 be done prior to destruction. Use this to unload error strings from
13052 ENGINEs that load their own error strings. NB: This adds two new API
13053 functions to "get" and "set" this destroy handler in an ENGINE.
13057 * Alter all existing ENGINE implementations (except "openssl" and
13058 "openbsd") to dynamically instantiate their own error strings. This
13059 makes them more flexible to be built both as statically-linked ENGINEs
13060 and self-contained shared-libraries loadable via the "dynamic" ENGINE.
13061 Also, add stub code to each that makes building them as self-contained
13062 shared-libraries easier (see [README-Engine.md](README-Engine.md)).
13066 * Add a "dynamic" ENGINE that provides a mechanism for binding ENGINE
13067 implementations into applications that are completely implemented in
13068 self-contained shared-libraries. The "dynamic" ENGINE exposes control
13069 commands that can be used to configure what shared-library to load and
13070 to control aspects of the way it is handled. Also, made an update to
13071 the [README-Engine.md](README-Engine.md) file
13072 that brings its information up-to-date and
13073 provides some information and instructions on the "dynamic" ENGINE
13074 (ie. how to use it, how to build "dynamic"-loadable ENGINEs, etc).
13078 * Make it possible to unload ranges of ERR strings with a new
13079 "ERR_unload_strings" function.
13083 * Add a copy() function to EVP_MD.
13087 * Make EVP_MD routines take a context pointer instead of just the
13088 md_data void pointer.
13092 * Add flags to EVP_MD and EVP_MD_CTX. EVP_MD_FLAG_ONESHOT indicates
13093 that the digest can only process a single chunk of data
13094 (typically because it is provided by a piece of
13095 hardware). EVP_MD_CTX_FLAG_ONESHOT indicates that the application
13096 is only going to provide a single chunk of data, and hence the
13097 framework needn't accumulate the data for oneshot drivers.
13101 * As with "ERR", make it possible to replace the underlying "ex_data"
13102 functions. This change also alters the storage and management of global
13103 ex_data state - it's now all inside ex_data.c and all "class" code (eg.
13104 RSA, BIO, SSL_CTX, etc) no longer stores its own STACKS and per-class
13105 index counters. The API functions that use this state have been changed
13106 to take a "class_index" rather than pointers to the class's local STACK
13107 and counter, and there is now an API function to dynamically create new
13108 classes. This centralisation allows us to (a) plug a lot of the
13109 thread-safety problems that existed, and (b) makes it possible to clean
13110 up all allocated state using "CRYPTO_cleanup_all_ex_data()". W.r.t. (b)
13111 such data would previously have always leaked in application code and
13112 workarounds were in place to make the memory debugging turn a blind eye
13113 to it. Application code that doesn't use this new function will still
13114 leak as before, but their memory debugging output will announce it now
13115 rather than letting it slide.
13117 Besides the addition of CRYPTO_cleanup_all_ex_data(), another API change
13118 induced by the "ex_data" overhaul is that X509_STORE_CTX_init() now
13119 has a return value to indicate success or failure.
13123 * Make it possible to replace the underlying "ERR" functions such that the
13124 global state (2 LHASH tables and 2 locks) is only used by the "default"
13125 implementation. This change also adds two functions to "get" and "set"
13126 the implementation prior to it being automatically set the first time
13127 any other ERR function takes place. Ie. an application can call "get",
13128 pass the return value to a module it has just loaded, and that module
13129 can call its own "set" function using that value. This means the
13130 module's "ERR" operations will use (and modify) the error state in the
13131 application and not in its own statically linked copy of OpenSSL code.
13135 * Give DH, DSA, and RSA types their own `*_up_ref()` function to increment
13136 reference counts. This performs normal REF_PRINT/REF_CHECK macros on
13137 the operation, and provides a more encapsulated way for external code
13138 (crypto/evp/ and ssl/) to do this. Also changed the evp and ssl code
13139 to use these functions rather than manually incrementing the counts.
13141 Also rename "DSO_up()" function to more descriptive "DSO_up_ref()".
13145 * Add EVP test program.
13149 * Add symmetric cipher support to ENGINE. Expect the API to change!
13153 * New CRL functions: X509_CRL_set_version(), X509_CRL_set_issuer_name()
13154 X509_CRL_set_lastUpdate(), X509_CRL_set_nextUpdate(), X509_CRL_sort(),
13155 X509_REVOKED_set_serialNumber(), and X509_REVOKED_set_revocationDate().
13156 These allow a CRL to be built without having to access X509_CRL fields
13157 directly. Modify 'ca' application to use new functions.
13161 * Move SSL_OP_TLS_ROLLBACK_BUG out of the SSL_OP_ALL list of recommended
13162 bug workarounds. Rollback attack detection is a security feature.
13163 The problem will only arise on OpenSSL servers when TLSv1 is not
13164 available (sslv3_server_method() or SSL_OP_NO_TLSv1).
13165 Software authors not wanting to support TLSv1 will have special reasons
13166 for their choice and can explicitly enable this option.
13168 *Bodo Moeller, Lutz Jaenicke*
13170 * Rationalise EVP so it can be extended: don't include a union of
13171 cipher/digest structures, add init/cleanup functions for EVP_MD_CTX
13172 (similar to those existing for EVP_CIPHER_CTX).
13177 EVP_MD_CTX_init(&md); /* new function call */
13178 EVP_DigestInit(&md, EVP_sha1());
13179 EVP_DigestUpdate(&md, in, len);
13180 EVP_DigestFinal(&md, out, NULL);
13181 EVP_MD_CTX_cleanup(&md); /* new function call */
13185 * Make DES key schedule conform to the usual scheme, as well as
13186 correcting its structure. This means that calls to DES functions
13187 now have to pass a pointer to a des_key_schedule instead of a
13188 plain des_key_schedule (which was actually always a pointer
13191 des_key_schedule ks;
13193 des_set_key_checked(..., &ks);
13194 des_ncbc_encrypt(..., &ks, ...);
13196 (Note that a later change renames 'des_...' into 'DES_...'.)
13200 * Initial reduction of linker bloat: the use of some functions, such as
13201 PEM causes large amounts of unused functions to be linked in due to
13202 poor organisation. For example pem_all.c contains every PEM function
13203 which has a knock on effect of linking in large amounts of (unused)
13204 ASN1 code. Grouping together similar functions and splitting unrelated
13205 functions prevents this.
13209 * Cleanup of EVP macros.
13213 * Change historical references to `{NID,SN,LN}_des_ede` and ede3 to add the
13214 correct `_ecb suffix`.
13218 * Add initial OCSP responder support to ocsp application. The
13219 revocation information is handled using the text based index
13220 use by the ca application. The responder can either handle
13221 requests generated internally, supplied in files (for example
13222 via a CGI script) or using an internal minimal server.
13226 * Add configuration choices to get zlib compression for TLS.
13230 * Changes to Kerberos SSL for RFC 2712 compliance:
13231 1. Implemented real KerberosWrapper, instead of just using
13232 KRB5 AP_REQ message. [Thanks to Simon Wilkinson <sxw@sxw.org.uk>]
13233 2. Implemented optional authenticator field of KerberosWrapper.
13235 Added openssl-style ASN.1 macros for Kerberos ticket, ap_req,
13236 and authenticator structs; see crypto/krb5/.
13238 Generalized Kerberos calls to support multiple Kerberos libraries.
13239 *Vern Staats <staatsvr@asc.hpc.mil>, Jeffrey Altman <jaltman@columbia.edu>
13240 via Richard Levitte*
13242 * Cause 'openssl speed' to use fully hard-coded DSA keys as it
13243 already does with RSA. testdsa.h now has 'priv_key/pub_key'
13244 values for each of the key sizes rather than having just
13245 parameters (and 'speed' generating keys each time).
13249 * Speed up EVP routines.
13252 pe 8 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
13253 s-cbc 4408.85k 5560.51k 5778.46k 5862.20k 5825.16k
13254 s-cbc 4389.55k 5571.17k 5792.23k 5846.91k 5832.11k
13255 s-cbc 4394.32k 5575.92k 5807.44k 5848.37k 5841.30k
13257 s-cbc 3482.66k 5069.49k 5496.39k 5614.16k 5639.28k
13258 s-cbc 3480.74k 5068.76k 5510.34k 5609.87k 5635.52k
13259 s-cbc 3483.72k 5067.62k 5504.60k 5708.01k 5724.80k
13262 s-cbc 4660.16k 5650.19k 5807.19k 5827.13k 5783.32k
13264 s-cbc 3624.96k 5258.21k 5530.91k 5624.30k 5628.26k
13268 * Added the OS2-EMX target.
13270 *"Brian Havard" <brianh@kheldar.apana.org.au> and Richard Levitte*
13272 * Rewrite commands to use `NCONF` routines instead of the old `CONF`.
13273 New functions to support `NCONF` routines in extension code.
13274 New function `CONF_set_nconf()`
13275 to allow functions which take an `NCONF` to also handle the old `LHASH`
13276 structure: this means that the old `CONF` compatible routines can be
13277 retained (in particular w.rt. extensions) without having to duplicate the
13278 code. New function `X509V3_add_ext_nconf_sk()` to add extensions to a stack.
13282 * Enhance the general user interface with mechanisms for inner control
13283 and with possibilities to have yes/no kind of prompts.
13287 * Change all calls to low-level digest routines in the library and
13288 applications to use EVP. Add missing calls to HMAC_cleanup() and
13289 don't assume HMAC_CTX can be copied using memcpy().
13291 *Verdon Walker <VWalker@novell.com>, Steve Henson*
13293 * Add the possibility to control engines through control names but with
13294 arbitrary arguments instead of just a string.
13295 Change the key loaders to take a UI_METHOD instead of a callback
13296 function pointer. NOTE: this breaks binary compatibility with earlier
13297 versions of OpenSSL [engine].
13298 Adapt the nCipher code for these new conditions and add a card insertion
13303 * Enhance the general user interface with mechanisms to better support
13304 dialog box interfaces, application-defined prompts, the possibility
13305 to use defaults (for example default passwords from somewhere else)
13306 and interrupts/cancellations.
13310 * Tidy up PKCS#12 attribute handling. Add support for the CSP name
13311 attribute in PKCS#12 files, add new -CSP option to pkcs12 utility.
13315 * Fix a memory leak in 'sk_dup()' in the case reallocation fails. (Also
13316 tidy up some unnecessarily weird code in 'sk_new()').
13318 *Geoff, reported by Diego Tartara <dtartara@novamens.com>*
13320 * Change the key loading routines for ENGINEs to use the same kind
13321 callback (pem_password_cb) as all other routines that need this
13326 * Increase ENTROPY_NEEDED to 32 bytes, as Rijndael can operate with
13327 256 bit (=32 byte) keys. Of course seeding with more entropy bytes
13328 than this minimum value is recommended.
13332 * New random seeder for OpenVMS, using the system process statistics
13333 that are easily reachable.
13337 * Windows apparently can't transparently handle global
13338 variables defined in DLLs. Initialisations such as:
13340 const ASN1_ITEM *it = &ASN1_INTEGER_it;
13342 won't compile. This is used by the any applications that need to
13343 declare their own ASN1 modules. This was fixed by adding the option
13344 EXPORT_VAR_AS_FN to all Win32 platforms, although this isn't strictly
13345 needed for static libraries under Win32.
13349 * New functions X509_PURPOSE_set() and X509_TRUST_set() to handle
13350 setting of purpose and trust fields. New X509_STORE trust and
13351 purpose functions and tidy up setting in other SSL functions.
13355 * Add copies of X509_STORE_CTX fields and callbacks to X509_STORE
13356 structure. These are inherited by X509_STORE_CTX when it is
13357 initialised. This allows various defaults to be set in the
13358 X509_STORE structure (such as flags for CRL checking and custom
13359 purpose or trust settings) for functions which only use X509_STORE_CTX
13360 internally such as S/MIME.
13362 Modify X509_STORE_CTX_purpose_inherit() so it only sets purposes and
13363 trust settings if they are not set in X509_STORE. This allows X509_STORE
13364 purposes and trust (in S/MIME for example) to override any set by default.
13366 Add command line options for CRL checking to smime, s_client and s_server
13371 * Initial CRL based revocation checking. If the CRL checking flag(s)
13372 are set then the CRL is looked up in the X509_STORE structure and
13373 its validity and signature checked, then if the certificate is found
13374 in the CRL the verify fails with a revoked error.
13376 Various new CRL related callbacks added to X509_STORE_CTX structure.
13378 Command line options added to 'verify' application to support this.
13380 This needs some additional work, such as being able to handle multiple
13381 CRLs with different times, extension based lookup (rather than just
13382 by subject name) and ultimately more complete V2 CRL extension
13387 * Add a general user interface API (crypto/ui/). This is designed
13388 to replace things like des_read_password and friends (backward
13389 compatibility functions using this new API are provided).
13390 The purpose is to remove prompting functions from the DES code
13391 section as well as provide for prompting through dialog boxes in
13392 a window system and the like.
13396 * Add "ex_data" support to ENGINE so implementations can add state at a
13397 per-structure level rather than having to store it globally.
13401 * Make it possible for ENGINE structures to be copied when retrieved by
13402 ENGINE_by_id() if the ENGINE specifies a new flag: ENGINE_FLAGS_BY_ID_COPY.
13403 This causes the "original" ENGINE structure to act like a template,
13404 analogous to the RSA vs. RSA_METHOD type of separation. Because of this
13405 operational state can be localised to each ENGINE structure, despite the
13406 fact they all share the same "methods". New ENGINE structures returned in
13407 this case have no functional references and the return value is the single
13408 structural reference. This matches the single structural reference returned
13409 by ENGINE_by_id() normally, when it is incremented on the pre-existing
13414 * Fix ASN1 decoder when decoding type ANY and V_ASN1_OTHER: since this
13415 needs to match any other type at all we need to manually clear the
13420 * Changes to the "openssl engine" utility to include;
13421 - verbosity levels ('-v', '-vv', and '-vvv') that provide information
13422 about an ENGINE's available control commands.
13423 - executing control commands from command line arguments using the
13424 '-pre' and '-post' switches. '-post' is only used if '-t' is
13425 specified and the ENGINE is successfully initialised. The syntax for
13426 the individual commands are colon-separated, for example;
13427 openssl engine chil -pre FORK_CHECK:0 -pre SO_PATH:/lib/test.so
13431 * New dynamic control command support for ENGINEs. ENGINEs can now
13432 declare their own commands (numbers), names (strings), descriptions,
13433 and input types for run-time discovery by calling applications. A
13434 subset of these commands are implicitly classed as "executable"
13435 depending on their input type, and only these can be invoked through
13436 the new string-based API function ENGINE_ctrl_cmd_string(). (Eg. this
13437 can be based on user input, config files, etc). The distinction is
13438 that "executable" commands cannot return anything other than a boolean
13439 result and can only support numeric or string input, whereas some
13440 discoverable commands may only be for direct use through
13441 ENGINE_ctrl(), eg. supporting the exchange of binary data, function
13442 pointers, or other custom uses. The "executable" commands are to
13443 support parameterisations of ENGINE behaviour that can be
13444 unambiguously defined by ENGINEs and used consistently across any
13445 OpenSSL-based application. Commands have been added to all the
13446 existing hardware-supporting ENGINEs, noticeably "SO_PATH" to allow
13447 control over shared-library paths without source code alterations.
13451 * Changed all ENGINE implementations to dynamically allocate their
13452 ENGINEs rather than declaring them statically. Apart from this being
13453 necessary with the removal of the ENGINE_FLAGS_MALLOCED distinction,
13454 this also allows the implementations to compile without using the
13455 internal engine_int.h header.
13459 * Minor adjustment to "rand" code. RAND_get_rand_method() now returns a
13460 'const' value. Any code that should be able to modify a RAND_METHOD
13461 should already have non-const pointers to it (ie. they should only
13462 modify their own ones).
13466 * Made a variety of little tweaks to the ENGINE code.
13467 - "atalla" and "ubsec" string definitions were moved from header files
13468 to C code. "nuron" string definitions were placed in variables
13469 rather than hard-coded - allowing parameterisation of these values
13470 later on via ctrl() commands.
13471 - Removed unused "#if 0"'d code.
13472 - Fixed engine list iteration code so it uses ENGINE_free() to release
13473 structural references.
13474 - Constified the RAND_METHOD element of ENGINE structures.
13475 - Constified various get/set functions as appropriate and added
13476 missing functions (including a catch-all ENGINE_cpy that duplicates
13477 all ENGINE values onto a new ENGINE except reference counts/state).
13478 - Removed NULL parameter checks in get/set functions. Setting a method
13479 or function to NULL is a way of cancelling out a previously set
13480 value. Passing a NULL ENGINE parameter is just plain stupid anyway
13481 and doesn't justify the extra error symbols and code.
13482 - Deprecate the ENGINE_FLAGS_MALLOCED define and move the area for
13483 flags from engine_int.h to engine.h.
13484 - Changed prototypes for ENGINE handler functions (init(), finish(),
13485 ctrl(), key-load functions, etc) to take an (ENGINE*) parameter.
13489 * Implement binary inversion algorithm for BN_mod_inverse in addition
13490 to the algorithm using long division. The binary algorithm can be
13491 used only if the modulus is odd. On 32-bit systems, it is faster
13492 only for relatively small moduli (roughly 20-30% for 128-bit moduli,
13493 roughly 5-15% for 256-bit moduli), so we use it only for moduli
13494 up to 450 bits. In 64-bit environments, the binary algorithm
13495 appears to be advantageous for much longer moduli; here we use it
13496 for moduli up to 2048 bits.
13500 * Rewrite CHOICE field setting in ASN1_item_ex_d2i(). The old code
13501 could not support the combine flag in choice fields.
13505 * Add a 'copy_extensions' option to the 'ca' utility. This copies
13506 extensions from a certificate request to the certificate.
13510 * Allow multiple 'certopt' and 'nameopt' options to be separated
13511 by commas. Add 'namopt' and 'certopt' options to the 'ca' config
13512 file: this allows the display of the certificate about to be
13513 signed to be customised, to allow certain fields to be included
13514 or excluded and extension details. The old system didn't display
13515 multicharacter strings properly, omitted fields not in the policy
13516 and couldn't display additional details such as extensions.
13520 * Function EC_POINTs_mul for multiple scalar multiplication
13521 of an arbitrary number of elliptic curve points
13522 \sum scalars[i]*points[i],
13523 optionally including the generator defined for the EC_GROUP:
13524 scalar*generator + \sum scalars[i]*points[i].
13526 EC_POINT_mul is a simple wrapper function for the typical case
13527 that the point list has just one item (besides the optional
13532 * First EC_METHODs for curves over GF(p):
13534 EC_GFp_simple_method() uses the basic BN_mod_mul and BN_mod_sqr
13535 operations and provides various method functions that can also
13536 operate with faster implementations of modular arithmetic.
13538 EC_GFp_mont_method() reuses most functions that are part of
13539 EC_GFp_simple_method, but uses Montgomery arithmetic.
13541 *Bodo Moeller; point addition and point doubling
13542 implementation directly derived from source code provided by
13543 Lenka Fibikova <fibikova@exp-math.uni-essen.de>*
13545 * Framework for elliptic curves (crypto/ec/ec.h, crypto/ec/ec_lcl.h,
13546 crypto/ec/ec_lib.c):
13548 Curves are EC_GROUP objects (with an optional group generator)
13549 based on EC_METHODs that are built into the library.
13551 Points are EC_POINT objects based on EC_GROUP objects.
13553 Most of the framework would be able to handle curves over arbitrary
13554 finite fields, but as there are no obvious types for fields other
13555 than GF(p), some functions are limited to that for now.
13559 * Add the -HTTP option to s_server. It is similar to -WWW, but requires
13560 that the file contains a complete HTTP response.
13564 * Add the ec directory to mkdef.pl and mkfiles.pl. In mkdef.pl
13565 change the def and num file printf format specifier from "%-40sXXX"
13566 to "%-39s XXX". The latter will always guarantee a space after the
13567 field while the former will cause them to run together if the field
13568 is 40 of more characters long.
13572 * Constify the cipher and digest 'method' functions and structures
13573 and modify related functions to take constant EVP_MD and EVP_CIPHER
13578 * Hide BN_CTX structure details in bn_lcl.h instead of publishing them
13579 in <openssl/bn.h>. Also further increase BN_CTX_NUM to 32.
13583 * Modify `EVP_Digest*()` routines so they now return values. Although the
13584 internal software routines can never fail additional hardware versions
13589 * Clean up crypto/err/err.h and change some error codes to avoid conflicts:
13591 Previously ERR_R_FATAL was too small and coincided with ERR_LIB_PKCS7
13592 (= ERR_R_PKCS7_LIB); it is now 64 instead of 32.
13595 ERR_R_NESTED_ASN1_ERROR
13597 ERR_R_MISSING_ASN1_EOS
13598 were 4 .. 9, conflicting with
13599 ERR_LIB_RSA (= ERR_R_RSA_LIB)
13601 ERR_LIB_PEM (= ERR_R_PEM_LIB).
13602 They are now 58 .. 63 (i.e., just below ERR_R_FATAL).
13604 Add new error code 'ERR_R_INTERNAL_ERROR'.
13608 * Don't overuse locks in crypto/err/err.c: For data retrieval, CRYPTO_r_lock
13613 * New option '-subj arg' for 'openssl req' and 'openssl ca'. This
13614 sets the subject name for a new request or supersedes the
13615 subject name in a given request. Formats that can be parsed are
13616 'CN=Some Name, OU=myOU, C=IT'
13618 'CN=Some Name/OU=myOU/C=IT'.
13620 Add options '-batch' and '-verbose' to 'openssl req'.
13622 *Massimiliano Pala <madwolf@hackmasters.net>*
13624 * Introduce the possibility to access global variables through
13625 functions on platform were that's the best way to handle exporting
13626 global variables in shared libraries. To enable this functionality,
13627 one must configure with "EXPORT_VAR_AS_FN" or defined the C macro
13628 "OPENSSL_EXPORT_VAR_AS_FUNCTION" in crypto/opensslconf.h (the latter
13629 is normally done by Configure or something similar).
13631 To implement a global variable, use the macro OPENSSL_IMPLEMENT_GLOBAL
13632 in the source file (foo.c) like this:
13634 OPENSSL_IMPLEMENT_GLOBAL(int,foo)=1;
13635 OPENSSL_IMPLEMENT_GLOBAL(double,bar);
13637 To declare a global variable, use the macros OPENSSL_DECLARE_GLOBAL
13638 and OPENSSL_GLOBAL_REF in the header file (foo.h) like this:
13640 OPENSSL_DECLARE_GLOBAL(int,foo);
13641 #define foo OPENSSL_GLOBAL_REF(foo)
13642 OPENSSL_DECLARE_GLOBAL(double,bar);
13643 #define bar OPENSSL_GLOBAL_REF(bar)
13645 The #defines are very important, and therefore so is including the
13646 header file everywhere where the defined globals are used.
13648 The macro OPENSSL_EXPORT_VAR_AS_FUNCTION also affects the definition
13649 of ASN.1 items, but that structure is a bit different.
13651 The largest change is in util/mkdef.pl which has been enhanced with
13652 better and easier to understand logic to choose which symbols should
13653 go into the Windows .def files as well as a number of fixes and code
13654 cleanup (among others, algorithm keywords are now sorted
13655 lexicographically to avoid constant rewrites).
13659 * In BN_div() keep a copy of the sign of 'num' before writing the
13660 result to 'rm' because if rm==num the value will be overwritten
13661 and produce the wrong result if 'num' is negative: this caused
13662 problems with BN_mod() and BN_nnmod().
13666 * Function OCSP_request_verify(). This checks the signature on an
13667 OCSP request and verifies the signer certificate. The signer
13668 certificate is just checked for a generic purpose and OCSP request
13673 * Add OCSP_check_validity() function to check the validity of OCSP
13674 responses. OCSP responses are prepared in real time and may only
13675 be a few seconds old. Simply checking that the current time lies
13676 between thisUpdate and nextUpdate max reject otherwise valid responses
13677 caused by either OCSP responder or client clock inaccuracy. Instead
13678 we allow thisUpdate and nextUpdate to fall within a certain period of
13679 the current time. The age of the response can also optionally be
13680 checked. Two new options -validity_period and -status_age added to
13685 * If signature or public key algorithm is unrecognized print out its
13686 OID rather that just UNKNOWN.
13690 * Change OCSP_cert_to_id() to tolerate a NULL subject certificate and
13691 OCSP_cert_id_new() a NULL serialNumber. This allows a partial certificate
13692 ID to be generated from the issuer certificate alone which can then be
13693 passed to OCSP_id_issuer_cmp().
13697 * New compilation option ASN1_ITEM_FUNCTIONS. This causes the new
13698 ASN1 modules to export functions returning ASN1_ITEM pointers
13699 instead of the ASN1_ITEM structures themselves. This adds several
13700 new macros which allow the underlying ASN1 function/structure to
13701 be accessed transparently. As a result code should not use ASN1_ITEM
13702 references directly (such as &X509_it) but instead use the relevant
13703 macros (such as ASN1_ITEM_rptr(X509)). This option is to allow
13704 use of the new ASN1 code on platforms where exporting structures
13705 is problematical (for example in shared libraries) but exporting
13706 functions returning pointers to structures is not.
13710 * Add support for overriding the generation of SSL/TLS session IDs.
13711 These callbacks can be registered either in an SSL_CTX or per SSL.
13712 The purpose of this is to allow applications to control, if they wish,
13713 the arbitrary values chosen for use as session IDs, particularly as it
13714 can be useful for session caching in multiple-server environments. A
13715 command-line switch for testing this (and any client code that wishes
13716 to use such a feature) has been added to "s_server".
13718 *Geoff Thorpe, Lutz Jaenicke*
13720 * Modify mkdef.pl to recognise and parse preprocessor conditionals
13721 of the form `#if defined(...) || defined(...) || ...` and
13722 `#if !defined(...) && !defined(...) && ...`. This also avoids
13723 the growing number of special cases it was previously handling.
13727 * Make all configuration macros available for application by making
13728 sure they are available in opensslconf.h, by giving them names starting
13729 with `OPENSSL_` to avoid conflicts with other packages and by making
13730 sure e_os2.h will cover all platform-specific cases together with
13732 Additionally, it is now possible to define configuration/platform-
13733 specific names (called "system identities"). In the C code, these
13734 are prefixed with `OPENSSL_SYSNAME_`. e_os2.h will create another
13735 macro with the name beginning with `OPENSSL_SYS_`, which is determined
13736 from `OPENSSL_SYSNAME_*` or compiler-specific macros depending on
13741 * New option -set_serial to 'req' and 'x509' this allows the serial
13742 number to use to be specified on the command line. Previously self
13743 signed certificates were hard coded with serial number 0 and the
13744 CA options of 'x509' had to use a serial number in a file which was
13749 * New options to 'ca' utility to support V2 CRL entry extensions.
13750 Currently CRL reason, invalidity date and hold instruction are
13751 supported. Add new CRL extensions to V3 code and some new objects.
13755 * New function EVP_CIPHER_CTX_set_padding() this is used to
13756 disable standard block padding (aka PKCS#5 padding) in the EVP
13757 API, which was previously mandatory. This means that the data is
13758 not padded in any way and so the total length much be a multiple
13759 of the block size, otherwise an error occurs.
13763 * Initial (incomplete) OCSP SSL support.
13767 * New function OCSP_parse_url(). This splits up a URL into its host,
13768 port and path components: primarily to parse OCSP URLs. New -url
13769 option to ocsp utility.
13773 * New nonce behavior. The return value of OCSP_check_nonce() now
13774 reflects the various checks performed. Applications can decide
13775 whether to tolerate certain situations such as an absent nonce
13776 in a response when one was present in a request: the ocsp application
13777 just prints out a warning. New function OCSP_add1_basic_nonce()
13778 this is to allow responders to include a nonce in a response even if
13779 the request is nonce-less.
13783 * Disable stdin buffering in `load_cert()` (`apps/apps.c`) so that no certs are
13784 skipped when using openssl x509 multiple times on a single input file,
13785 e.g. `(openssl x509 -out cert1; openssl x509 -out cert2) <certs`.
13789 * Make ASN1_UTCTIME_set_string() and ASN1_GENERALIZEDTIME_set_string()
13790 set string type: to handle setting ASN1_TIME structures. Fix ca
13791 utility to correctly initialize revocation date of CRLs.
13795 * New option SSL_OP_CIPHER_SERVER_PREFERENCE allows the server to override
13796 the clients preferred ciphersuites and rather use its own preferences.
13797 Should help to work around M$ SGC (Server Gated Cryptography) bug in
13798 Internet Explorer by ensuring unchanged hash method during stepup.
13799 (Also replaces the broken/deactivated SSL_OP_NON_EXPORT_FIRST option.)
13803 * Make mkdef.pl recognise all DECLARE_ASN1 macros, change rijndael
13804 to aes and add a new 'exist' option to print out symbols that don't
13809 * Additional options to ocsp utility to allow flags to be set and
13810 additional certificates supplied.
13814 * Add the option -VAfile to 'openssl ocsp', so the user can give the
13815 OCSP client a number of certificate to only verify the response
13820 * Update Rijndael code to version 3.0 and change EVP AES ciphers to
13821 handle the new API. Currently only ECB, CBC modes supported. Add new
13824 Add TLS AES ciphersuites as described in RFC3268, "Advanced
13825 Encryption Standard (AES) Ciphersuites for Transport Layer
13826 Security (TLS)". (In beta versions of OpenSSL 0.9.7, these were
13827 not enabled by default and were not part of the "ALL" ciphersuite
13828 alias because they were not yet official; they could be
13829 explicitly requested by specifying the "AESdraft" ciphersuite
13830 group alias. In the final release of OpenSSL 0.9.7, the group
13831 alias is called "AES" and is part of "ALL".)
13833 *Ben Laurie, Steve Henson, Bodo Moeller*
13835 * New function OCSP_copy_nonce() to copy nonce value (if present) from
13836 request to response.
13840 * Functions for OCSP responders. OCSP_request_onereq_count(),
13841 OCSP_request_onereq_get0(), OCSP_onereq_get0_id() and OCSP_id_get0_info()
13842 extract information from a certificate request. OCSP_response_create()
13843 creates a response and optionally adds a basic response structure.
13844 OCSP_basic_add1_status() adds a complete single response to a basic
13845 response and returns the OCSP_SINGLERESP structure just added (to allow
13846 extensions to be included for example). OCSP_basic_add1_cert() adds a
13847 certificate to a basic response and OCSP_basic_sign() signs a basic
13848 response with various flags. New helper functions ASN1_TIME_check()
13849 (checks validity of ASN1_TIME structure) and ASN1_TIME_to_generalizedtime()
13850 (converts ASN1_TIME to GeneralizedTime).
13854 * Various new functions. EVP_Digest() combines EVP_Digest{Init,Update,Final}()
13855 in a single operation. X509_get0_pubkey_bitstr() extracts the public_key
13856 structure from a certificate. X509_pubkey_digest() digests the public_key
13857 contents: this is used in various key identifiers.
13861 * Make sk_sort() tolerate a NULL argument.
13863 *Steve Henson reported by Massimiliano Pala <madwolf@comune.modena.it>*
13865 * New OCSP verify flag OCSP_TRUSTOTHER. When set the "other" certificates
13866 passed by the function are trusted implicitly. If any of them signed the
13867 response then it is assumed to be valid and is not verified.
13871 * In PKCS7_set_type() initialise content_type in PKCS7_ENC_CONTENT
13872 to data. This was previously part of the PKCS7 ASN1 code. This
13873 was causing problems with OpenSSL created PKCS#12 and PKCS#7 structures.
13874 *Steve Henson, reported by Kenneth R. Robinette
13875 <support@securenetterm.com>*
13877 * Add CRYPTO_push_info() and CRYPTO_pop_info() calls to new ASN1
13878 routines: without these tracing memory leaks is very painful.
13879 Fix leaks in PKCS12 and PKCS7 routines.
13883 * Make X509_time_adj() cope with the new behaviour of ASN1_TIME_new().
13884 Previously it initialised the 'type' argument to V_ASN1_UTCTIME which
13885 effectively meant GeneralizedTime would never be used. Now it
13886 is initialised to -1 but X509_time_adj() now has to check the value
13887 and use ASN1_TIME_set() if the value is not V_ASN1_UTCTIME or
13888 V_ASN1_GENERALIZEDTIME, without this it always uses GeneralizedTime.
13889 *Steve Henson, reported by Kenneth R. Robinette
13890 <support@securenetterm.com>*
13892 * Fixes to BN_to_ASN1_INTEGER when bn is zero. This would previously
13893 result in a zero length in the ASN1_INTEGER structure which was
13894 not consistent with the structure when d2i_ASN1_INTEGER() was used
13895 and would cause ASN1_INTEGER_cmp() to fail. Enhance s2i_ASN1_INTEGER()
13896 to cope with hex and negative integers. Fix bug in i2a_ASN1_INTEGER()
13897 where it did not print out a minus for negative ASN1_INTEGER.
13901 * Add summary printout to ocsp utility. The various functions which
13902 convert status values to strings have been renamed to:
13903 OCSP_response_status_str(), OCSP_cert_status_str() and
13904 OCSP_crl_reason_str() and are no longer static. New options
13905 to verify nonce values and to disable verification. OCSP response
13906 printout format cleaned up.
13910 * Add additional OCSP certificate checks. These are those specified
13911 in RFC2560. This consists of two separate checks: the CA of the
13912 certificate being checked must either be the OCSP signer certificate
13913 or the issuer of the OCSP signer certificate. In the latter case the
13914 OCSP signer certificate must contain the OCSP signing extended key
13915 usage. This check is performed by attempting to match the OCSP
13916 signer or the OCSP signer CA to the issuerNameHash and issuerKeyHash
13917 in the OCSP_CERTID structures of the response.
13921 * Initial OCSP certificate verification added to OCSP_basic_verify()
13922 and related routines. This uses the standard OpenSSL certificate
13923 verify routines to perform initial checks (just CA validity) and
13924 to obtain the certificate chain. Then additional checks will be
13925 performed on the chain. Currently the root CA is checked to see
13926 if it is explicitly trusted for OCSP signing. This is used to set
13927 a root CA as a global signing root: that is any certificate that
13928 chains to that CA is an acceptable OCSP signing certificate.
13932 * New '-extfile ...' option to 'openssl ca' for reading X.509v3
13933 extensions from a separate configuration file.
13934 As when reading extensions from the main configuration file,
13935 the '-extensions ...' option may be used for specifying the
13938 *Massimiliano Pala <madwolf@comune.modena.it>*
13940 * New OCSP utility. Allows OCSP requests to be generated or
13941 read. The request can be sent to a responder and the output
13942 parsed, outputted or printed in text form. Not complete yet:
13943 still needs to check the OCSP response validity.
13947 * New subcommands for 'openssl ca':
13948 `openssl ca -status <serial>` prints the status of the cert with
13949 the given serial number (according to the index file).
13950 `openssl ca -updatedb` updates the expiry status of certificates
13953 *Massimiliano Pala <madwolf@comune.modena.it>*
13955 * New '-newreq-nodes' command option to CA.pl. This is like
13956 '-newreq', but calls 'openssl req' with the '-nodes' option
13957 so that the resulting key is not encrypted.
13959 *Damien Miller <djm@mindrot.org>*
13961 * New configuration for the GNU Hurd.
13963 *Jonathan Bartlett <johnnyb@wolfram.com> via Richard Levitte*
13965 * Initial code to implement OCSP basic response verify. This
13966 is currently incomplete. Currently just finds the signer's
13967 certificate and verifies the signature on the response.
13971 * New SSLeay_version code SSLEAY_DIR to determine the compiled-in
13972 value of OPENSSLDIR. This is available via the new '-d' option
13973 to 'openssl version', and is also included in 'openssl version -a'.
13977 * Allowing defining memory allocation callbacks that will be given
13978 file name and line number information in additional arguments
13979 (a `const char*` and an int). The basic functionality remains, as
13980 well as the original possibility to just replace malloc(),
13981 realloc() and free() by functions that do not know about these
13982 additional arguments. To register and find out the current
13983 settings for extended allocation functions, the following
13984 functions are provided:
13986 CRYPTO_set_mem_ex_functions
13987 CRYPTO_set_locked_mem_ex_functions
13988 CRYPTO_get_mem_ex_functions
13989 CRYPTO_get_locked_mem_ex_functions
13991 These work the same way as CRYPTO_set_mem_functions and friends.
13992 `CRYPTO_get_[locked_]mem_functions` now writes 0 where such an
13993 extended allocation function is enabled.
13994 Similarly, `CRYPTO_get_[locked_]mem_ex_functions` writes 0 where
13995 a conventional allocation function is enabled.
13997 *Richard Levitte, Bodo Moeller*
13999 * Finish off removing the remaining LHASH function pointer casts.
14000 There should no longer be any prototype-casting required when using
14001 the LHASH abstraction, and any casts that remain are "bugs". See
14002 the callback types and macros at the head of lhash.h for details
14003 (and "OBJ_cleanup" in crypto/objects/obj_dat.c as an example).
14007 * Add automatic query of EGD sockets in RAND_poll() for the unix variant.
14008 If /dev/[u]random devices are not available or do not return enough
14009 entropy, EGD style sockets (served by EGD or PRNGD) will automatically
14011 The locations /var/run/egd-pool, /dev/egd-pool, /etc/egd-pool, and
14012 /etc/entropy will be queried once each in this sequence, querying stops
14013 when enough entropy was collected without querying more sockets.
14017 * Change the Unix RAND_poll() variant to be able to poll several
14018 random devices, as specified by DEVRANDOM, until a sufficient amount
14019 of data has been collected. We spend at most 10 ms on each file
14020 (select timeout) and read in non-blocking mode. DEVRANDOM now
14021 defaults to the list "/dev/urandom", "/dev/random", "/dev/srandom"
14022 (previously it was just the string "/dev/urandom"), so on typical
14023 platforms the 10 ms delay will never occur.
14024 Also separate out the Unix variant to its own file, rand_unix.c.
14025 For VMS, there's a currently-empty rand_vms.c.
14029 * Move OCSP client related routines to ocsp_cl.c. These
14030 provide utility functions which an application needing
14031 to issue a request to an OCSP responder and analyse the
14032 response will typically need: as opposed to those which an
14033 OCSP responder itself would need which will be added later.
14035 OCSP_request_sign() signs an OCSP request with an API similar
14036 to PKCS7_sign(). OCSP_response_status() returns status of OCSP
14037 response. OCSP_response_get1_basic() extracts basic response
14038 from response. OCSP_resp_find_status(): finds and extracts status
14039 information from an OCSP_CERTID structure (which will be created
14040 when the request structure is built). These are built from lower
14041 level functions which work on OCSP_SINGLERESP structures but
14042 won't normally be used unless the application wishes to examine
14043 extensions in the OCSP response for example.
14045 Replace nonce routines with a pair of functions.
14046 OCSP_request_add1_nonce() adds a nonce value and optionally
14047 generates a random value. OCSP_check_nonce() checks the
14048 validity of the nonce in an OCSP response.
14052 * Change function OCSP_request_add() to OCSP_request_add0_id().
14053 This doesn't copy the supplied OCSP_CERTID and avoids the
14054 need to free up the newly created id. Change return type
14055 to OCSP_ONEREQ to return the internal OCSP_ONEREQ structure.
14056 This can then be used to add extensions to the request.
14057 Deleted OCSP_request_new(), since most of its functionality
14058 is now in OCSP_REQUEST_new() (and the case insensitive name
14059 clash) apart from the ability to set the request name which
14060 will be added elsewhere.
14064 * Update OCSP API. Remove obsolete extensions argument from
14065 various functions. Extensions are now handled using the new
14066 OCSP extension code. New simple OCSP HTTP function which
14067 can be used to send requests and parse the response.
14071 * Fix the PKCS#7 (S/MIME) code to work with new ASN1. Two new
14072 ASN1_ITEM structures help with sign and verify. PKCS7_ATTR_SIGN
14073 uses the special reorder version of SET OF to sort the attributes
14074 and reorder them to match the encoded order. This resolves a long
14075 standing problem: a verify on a PKCS7 structure just after signing
14076 it used to fail because the attribute order did not match the
14077 encoded order. PKCS7_ATTR_VERIFY does not reorder the attributes:
14078 it uses the received order. This is necessary to tolerate some broken
14079 software that does not order SET OF. This is handled by encoding
14080 as a SEQUENCE OF but using implicit tagging (with UNIVERSAL class)
14081 to produce the required SET OF.
14085 * Have mk1mf.pl generate the macros OPENSSL_BUILD_SHLIBCRYPTO and
14086 OPENSSL_BUILD_SHLIBSSL and use them appropriately in the header
14087 files to get correct declarations of the ASN.1 item variables.
14091 * Rewrite of PKCS#12 code to use new ASN1 functionality. Replace many
14092 PKCS#12 macros with real functions. Fix two unrelated ASN1 bugs:
14093 asn1_check_tlen() would sometimes attempt to use 'ctx' when it was
14094 NULL and ASN1_TYPE was not dereferenced properly in asn1_ex_c2i().
14095 New ASN1 macro: DECLARE_ASN1_ITEM() which just declares the relevant
14096 ASN1_ITEM and no wrapper functions.
14100 * New functions or ASN1_item_d2i_fp() and ASN1_item_d2i_bio(). These
14101 replace the old function pointer based I/O routines. Change most of
14102 the `*_d2i_bio()` and `*_d2i_fp()` functions to use these.
14106 * Enhance mkdef.pl to be more accepting about spacing in C preprocessor
14107 lines, recognize more "algorithms" that can be deselected, and make
14108 it complain about algorithm deselection that isn't recognised.
14112 * New ASN1 functions to handle dup, sign, verify, digest, pack and
14113 unpack operations in terms of ASN1_ITEM. Modify existing wrappers
14114 to use new functions. Add NO_ASN1_OLD which can be set to remove
14115 some old style ASN1 functions: this can be used to determine if old
14116 code will still work when these eventually go away.
14120 * New extension functions for OCSP structures, these follow the
14121 same conventions as certificates and CRLs.
14125 * New function X509V3_add1_i2d(). This automatically encodes and
14126 adds an extension. Its behaviour can be customised with various
14127 flags to append, replace or delete. Various wrappers added for
14128 certificates and CRLs.
14132 * Fix to avoid calling the underlying ASN1 print routine when
14133 an extension cannot be parsed. Correct a typo in the
14134 OCSP_SERVICELOC extension. Tidy up print OCSP format.
14138 * Make mkdef.pl parse some of the ASN1 macros and add appropriate
14139 entries for variables.
14143 * Add functionality to `apps/openssl.c` for detecting locking
14144 problems: As the program is single-threaded, all we have
14145 to do is register a locking callback using an array for
14146 storing which locks are currently held by the program.
14150 * Use a lock around the call to CRYPTO_get_ex_new_index() in
14151 SSL_get_ex_data_X509_STORE_idx(), which is used in
14152 ssl_verify_cert_chain() and thus can be called at any time
14153 during TLS/SSL handshakes so that thread-safety is essential.
14154 Unfortunately, the ex_data design is not at all suited
14155 for multi-threaded use, so it probably should be abolished.
14159 * Added Broadcom "ubsec" ENGINE to OpenSSL.
14161 *Broadcom, tweaked and integrated by Geoff Thorpe*
14163 * Move common extension printing code to new function
14164 X509V3_print_extensions(). Reorganise OCSP print routines and
14165 implement some needed OCSP ASN1 functions. Add OCSP extensions.
14169 * New function X509_signature_print() to remove duplication in some
14174 * Add a special meaning when SET OF and SEQUENCE OF flags are both
14175 set (this was treated exactly the same as SET OF previously). This
14176 is used to reorder the STACK representing the structure to match the
14177 encoding. This will be used to get round a problem where a PKCS7
14178 structure which was signed could not be verified because the STACK
14179 order did not reflect the encoded order.
14183 * Reimplement the OCSP ASN1 module using the new code.
14187 * Update the X509V3 code to permit the use of an ASN1_ITEM structure
14188 for its ASN1 operations. The old style function pointers still exist
14189 for now but they will eventually go away.
14193 * Merge in replacement ASN1 code from the ASN1 branch. This almost
14194 completely replaces the old ASN1 functionality with a table driven
14195 encoder and decoder which interprets an ASN1_ITEM structure describing
14196 the ASN1 module. Compatibility with the existing ASN1 API (i2d,d2i) is
14197 largely maintained. Almost all of the old asn1_mac.h macro based ASN1
14198 has also been converted to the new form.
14202 * Change BN_mod_exp_recp so that negative moduli are tolerated
14203 (the sign is ignored). Similarly, ignore the sign in BN_MONT_CTX_set
14204 so that BN_mod_exp_mont and BN_mod_exp_mont_word work
14205 for negative moduli.
14209 * Fix BN_uadd and BN_usub: Always return non-negative results instead
14210 of not touching the result's sign bit.
14214 * BN_div bugfix: If the result is 0, the sign (res->neg) must not be
14219 * Changed the LHASH code to use prototypes for callbacks, and created
14220 macros to declare and implement thin (optionally static) functions
14221 that provide type-safety and avoid function pointer casting for the
14222 type-specific callbacks.
14226 * Added Kerberos Cipher Suites to be used with TLS, as written in
14228 *Veers Staats <staatsvr@asc.hpc.mil>,
14229 Jeffrey Altman <jaltman@columbia.edu>, via Richard Levitte*
14231 * Reformat the FAQ so the different questions and answers can be divided
14232 in sections depending on the subject.
14236 * Have the zlib compression code load ZLIB.DLL dynamically under
14241 * New function BN_mod_sqrt for computing square roots modulo a prime
14242 (using the probabilistic Tonelli-Shanks algorithm unless
14243 p == 3 (mod 4) or p == 5 (mod 8), which are cases that can
14244 be handled deterministically).
14246 *Lenka Fibikova <fibikova@exp-math.uni-essen.de>, Bodo Moeller*
14248 * Make BN_mod_inverse faster by explicitly handling small quotients
14249 in the Euclid loop. (Speed gain about 20% for small moduli [256 or
14250 512 bits], about 30% for larger ones [1024 or 2048 bits].)
14254 * New function BN_kronecker.
14258 * Fix BN_gcd so that it works on negative inputs; the result is
14259 positive unless both parameters are zero.
14260 Previously something reasonably close to an infinite loop was
14261 possible because numbers could be growing instead of shrinking
14262 in the implementation of Euclid's algorithm.
14266 * Fix BN_is_word() and BN_is_one() macros to take into account the
14267 sign of the number in question.
14269 Fix BN_is_word(a,w) to work correctly for w == 0.
14271 The old BN_is_word(a,w) macro is now called BN_abs_is_word(a,w)
14272 because its test if the absolute value of 'a' equals 'w'.
14273 Note that BN_abs_is_word does *not* handle w == 0 reliably;
14274 it exists mostly for use in the implementations of BN_is_zero(),
14275 BN_is_one(), and BN_is_word().
14279 * New function BN_swap.
14283 * Use BN_nnmod instead of BN_mod in crypto/bn/bn_exp.c so that
14284 the exponentiation functions are more likely to produce reasonable
14285 results on negative inputs.
14289 * Change BN_mod_mul so that the result is always non-negative.
14290 Previously, it could be negative if one of the factors was negative;
14291 I don't think anyone really wanted that behaviour.
14295 * Move `BN_mod_...` functions into new file `crypto/bn/bn_mod.c`
14296 (except for exponentiation, which stays in `crypto/bn/bn_exp.c`,
14297 and `BN_mod_mul_reciprocal`, which stays in `crypto/bn/bn_recp.c`)
14298 and add new functions:
14307 BN_mod_lshift1_quick
14309 BN_mod_lshift_quick
14311 These functions always generate non-negative results.
14313 `BN_nnmod` otherwise is `like BN_mod` (if `BN_mod` computes a remainder `r`
14314 such that `|m| < r < 0`, `BN_nnmod` will output `rem + |m|` instead).
14316 `BN_mod_XXX_quick(r, a, [b,] m)` generates the same result as
14317 `BN_mod_XXX(r, a, [b,] m, ctx)`, but requires that `a` [and `b`]
14318 be reduced modulo `m`.
14320 *Lenka Fibikova <fibikova@exp-math.uni-essen.de>, Bodo Moeller*
14323 The following entry accidentally appeared in the CHANGES file
14324 distributed with OpenSSL 0.9.7. The modifications described in
14325 it do *not* apply to OpenSSL 0.9.7.
14327 * Remove a few calls to bn_wexpand() in BN_sqr() (the one in there
14328 was actually never needed) and in BN_mul(). The removal in BN_mul()
14329 required a small change in bn_mul_part_recursive() and the addition
14330 of the functions bn_cmp_part_words(), bn_sub_part_words() and
14331 bn_add_part_words(), which do the same thing as bn_cmp_words(),
14332 bn_sub_words() and bn_add_words() except they take arrays with
14338 * In 'openssl passwd', verify passwords read from the terminal
14339 unless the '-salt' option is used (which usually means that
14340 verification would just waste user's time since the resulting
14341 hash is going to be compared with some given password hash)
14342 or the new '-noverify' option is used.
14344 This is an incompatible change, but it does not affect
14345 non-interactive use of 'openssl passwd' (passwords on the command
14346 line, '-stdin' option, '-in ...' option) and thus should not
14347 cause any problems.
14351 * Remove all references to RSAref, since there's no more need for it.
14355 * Make DSO load along a path given through an environment variable
14356 (SHLIB_PATH) with shl_load().
14360 * Constify the ENGINE code as a result of BIGNUM constification.
14361 Also constify the RSA code and most things related to it. In a
14362 few places, most notable in the depth of the ASN.1 code, ugly
14363 casts back to non-const were required (to be solved at a later
14368 * Make it so the openssl application has all engines loaded by default.
14372 * Constify the BIGNUM routines a little more.
14376 * Add the following functions:
14378 ENGINE_load_cswift()
14380 ENGINE_load_atalla()
14381 ENGINE_load_nuron()
14382 ENGINE_load_builtin_engines()
14384 That way, an application can itself choose if external engines that
14385 are built-in in OpenSSL shall ever be used or not. The benefit is
14386 that applications won't have to be linked with libdl or other dso
14387 libraries unless it's really needed.
14389 Changed 'openssl engine' to load all engines on demand.
14390 Changed the engine header files to avoid the duplication of some
14391 declarations (they differed!).
14395 * 'openssl engine' can now list capabilities.
14399 * Better error reporting in 'openssl engine'.
14403 * Never call load_dh_param(NULL) in s_server.
14407 * Add engine application. It can currently list engines by name and
14408 identity, and test if they are actually available.
14412 * Improve RPM specification file by forcing symbolic linking and making
14413 sure the installed documentation is also owned by root.root.
14415 *Damien Miller <djm@mindrot.org>*
14417 * Give the OpenSSL applications more possibilities to make use of
14418 keys (public as well as private) handled by engines.
14422 * Add OCSP code that comes from CertCo.
14426 * Add VMS support for the Rijndael code.
14430 * Added untested support for Nuron crypto accelerator.
14434 * Add support for external cryptographic devices. This code was
14435 previously distributed separately as the "engine" branch.
14437 *Geoff Thorpe, Richard Levitte*
14439 * Rework the filename-translation in the DSO code. It is now possible to
14440 have far greater control over how a "name" is turned into a filename
14441 depending on the operating environment and any oddities about the
14442 different shared library filenames on each system.
14446 * Support threads on FreeBSD-elf in Configure.
14450 * Fix for SHA1 assembly problem with MASM: it produces
14451 warnings about corrupt line number information when assembling
14452 with debugging information. This is caused by the overlapping
14455 *Bernd Matthes <mainbug@celocom.de>, Steve Henson*
14458 NCONF_get_number() has no error checking at all. As a replacement,
14459 NCONF_get_number_e() is defined (`_e` for "error checking") and is
14460 promoted strongly. The old NCONF_get_number is kept around for
14461 binary backward compatibility.
14462 Make it possible for methods to load from something other than a BIO,
14463 by providing a function pointer that is given a name instead of a BIO.
14464 For example, this could be used to load configuration data from an
14469 * Fix for non blocking accept BIOs. Added new I/O special reason
14470 BIO_RR_ACCEPT to cover this case. Previously use of accept BIOs
14471 with non blocking I/O was not possible because no retry code was
14472 implemented. Also added new SSL code SSL_WANT_ACCEPT to cover
14477 * Added the beginnings of Rijndael support.
14481 * Fix for bug in DirectoryString mask setting. Add support for
14482 X509_NAME_print_ex() in 'req' and X509_print_ex() function
14483 to allow certificate printing to more controllable, additional
14484 'certopt' option to 'x509' to allow new printing options to be
14489 * Clean old EAY MD5 hack from e_os.h.
14493 ### Changes between 0.9.6l and 0.9.6m [17 Mar 2004]
14495 * Fix null-pointer assignment in do_change_cipher_spec() revealed
14496 by using the Codenomicon TLS Test Tool ([CVE-2004-0079])
14498 *Joe Orton, Steve Henson*
14500 ### Changes between 0.9.6k and 0.9.6l [04 Nov 2003]
14502 * Fix additional bug revealed by the NISCC test suite:
14504 Stop bug triggering large recursion when presented with
14505 certain ASN.1 tags ([CVE-2003-0851])
14509 ### Changes between 0.9.6j and 0.9.6k [30 Sep 2003]
14511 * Fix various bugs revealed by running the NISCC test suite:
14513 Stop out of bounds reads in the ASN1 code when presented with
14514 invalid tags (CVE-2003-0543 and CVE-2003-0544).
14516 If verify callback ignores invalid public key errors don't try to check
14517 certificate signature with the NULL public key.
14521 * In ssl3_accept() (ssl/s3_srvr.c) only accept a client certificate
14522 if the server requested one: as stated in TLS 1.0 and SSL 3.0
14527 * In ssl3_get_client_hello() (ssl/s3_srvr.c), tolerate additional
14528 extra data after the compression methods not only for TLS 1.0
14529 but also for SSL 3.0 (as required by the specification).
14531 *Bodo Moeller; problem pointed out by Matthias Loepfe*
14533 * Change X509_certificate_type() to mark the key as exported/exportable
14534 when it's 512 *bits* long, not 512 bytes.
14538 ### Changes between 0.9.6i and 0.9.6j [10 Apr 2003]
14540 * Countermeasure against the Klima-Pokorny-Rosa extension of
14541 Bleichbacher's attack on PKCS #1 v1.5 padding: treat
14542 a protocol version number mismatch like a decryption error
14543 in ssl3_get_client_key_exchange (ssl/s3_srvr.c).
14547 * Turn on RSA blinding by default in the default implementation
14548 to avoid a timing attack. Applications that don't want it can call
14549 RSA_blinding_off() or use the new flag RSA_FLAG_NO_BLINDING.
14550 They would be ill-advised to do so in most cases.
14552 *Ben Laurie, Steve Henson, Geoff Thorpe, Bodo Moeller*
14554 * Change RSA blinding code so that it works when the PRNG is not
14555 seeded (in this case, the secret RSA exponent is abused as
14556 an unpredictable seed -- if it is not unpredictable, there
14557 is no point in blinding anyway). Make RSA blinding thread-safe
14558 by remembering the creator's thread ID in rsa->blinding and
14559 having all other threads use local one-time blinding factors
14560 (this requires more computation than sharing rsa->blinding, but
14561 avoids excessive locking; and if an RSA object is not shared
14562 between threads, blinding will still be very fast).
14566 ### Changes between 0.9.6h and 0.9.6i [19 Feb 2003]
14568 * In ssl3_get_record (ssl/s3_pkt.c), minimize information leaked
14569 via timing by performing a MAC computation even if incorrect
14570 block cipher padding has been found. This is a countermeasure
14571 against active attacks where the attacker has to distinguish
14572 between bad padding and a MAC verification error. ([CVE-2003-0078])
14574 *Bodo Moeller; problem pointed out by Brice Canvel (EPFL),
14575 Alain Hiltgen (UBS), Serge Vaudenay (EPFL), and
14576 Martin Vuagnoux (EPFL, Ilion)*
14578 ### Changes between 0.9.6g and 0.9.6h [5 Dec 2002]
14580 * New function OPENSSL_cleanse(), which is used to cleanse a section of
14581 memory from its contents. This is done with a counter that will
14582 place alternating values in each byte. This can be used to solve
14583 two issues: 1) the removal of calls to memset() by highly optimizing
14584 compilers, and 2) cleansing with other values than 0, since those can
14585 be read through on certain media, for example a swap space on disk.
14589 * Bugfix: client side session caching did not work with external caching,
14590 because the session->cipher setting was not restored when reloading
14591 from the external cache. This problem was masked, when
14592 SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG (part of SSL_OP_ALL) was set.
14593 (Found by Steve Haslam <steve@araqnid.ddts.net>.)
14597 * Fix client_certificate (ssl/s2_clnt.c): The permissible total
14598 length of the REQUEST-CERTIFICATE message is 18 .. 34, not 17 .. 33.
14600 *Zeev Lieber <zeev-l@yahoo.com>*
14602 * Undo an undocumented change introduced in 0.9.6e which caused
14603 repeated calls to OpenSSL_add_all_ciphers() and
14604 OpenSSL_add_all_digests() to be ignored, even after calling
14609 * Change the default configuration reader to deal with last line not
14610 being properly terminated.
14614 * Change X509_NAME_cmp() so it applies the special rules on handling
14615 DN values that are of type PrintableString, as well as RDNs of type
14616 emailAddress where the value has the type ia5String.
14618 *stefank@valicert.com via Richard Levitte*
14620 * Add a SSL_SESS_CACHE_NO_INTERNAL_STORE flag to take over half
14621 the job SSL_SESS_CACHE_NO_INTERNAL_LOOKUP was inconsistently
14622 doing, define a new flag (SSL_SESS_CACHE_NO_INTERNAL) to be
14623 the bitwise-OR of the two for use by the majority of applications
14624 wanting this behaviour, and update the docs. The documented
14625 behaviour and actual behaviour were inconsistent and had been
14626 changing anyway, so this is more a bug-fix than a behavioural
14629 *Geoff Thorpe, diagnosed by Nadav Har'El*
14631 * Don't impose a 16-byte length minimum on session IDs in ssl/s3_clnt.c
14632 (the SSL 3.0 and TLS 1.0 specifications allow any length up to 32 bytes).
14636 * Fix initialization code race conditions in
14637 SSLv23_method(), SSLv23_client_method(), SSLv23_server_method(),
14638 SSLv2_method(), SSLv2_client_method(), SSLv2_server_method(),
14639 SSLv3_method(), SSLv3_client_method(), SSLv3_server_method(),
14640 TLSv1_method(), TLSv1_client_method(), TLSv1_server_method(),
14641 ssl2_get_cipher_by_char(),
14642 ssl3_get_cipher_by_char().
14644 *Patrick McCormick <patrick@tellme.com>, Bodo Moeller*
14646 * Reorder cleanup sequence in SSL_CTX_free(): only remove the ex_data after
14647 the cached sessions are flushed, as the remove_cb() might use ex_data
14648 contents. Bug found by Sam Varshavchik <mrsam@courier-mta.com>
14649 (see [openssl.org #212]).
14651 *Geoff Thorpe, Lutz Jaenicke*
14653 * Fix typo in OBJ_txt2obj which incorrectly passed the content
14654 length, instead of the encoding length to d2i_ASN1_OBJECT.
14658 ### Changes between 0.9.6f and 0.9.6g [9 Aug 2002]
14660 * [In 0.9.6g-engine release:]
14661 Fix crypto/engine/vendor_defns/cswift.h for WIN32 (use `_stdcall`).
14663 *Lynn Gazis <lgazis@rainbow.com>*
14665 ### Changes between 0.9.6e and 0.9.6f [8 Aug 2002]
14667 * Fix ASN1 checks. Check for overflow by comparing with LONG_MAX
14668 and get fix the header length calculation.
14669 *Florian Weimer <Weimer@CERT.Uni-Stuttgart.DE>,
14670 Alon Kantor <alonk@checkpoint.com> (and others), Steve Henson*
14672 * Use proper error handling instead of 'assertions' in buffer
14673 overflow checks added in 0.9.6e. This prevents DoS (the
14674 assertions could call abort()).
14676 *Arne Ansper <arne@ats.cyber.ee>, Bodo Moeller*
14678 ### Changes between 0.9.6d and 0.9.6e [30 Jul 2002]
14680 * Add various sanity checks to asn1_get_length() to reject
14681 the ASN1 length bytes if they exceed sizeof(long), will appear
14682 negative or the content length exceeds the length of the
14685 *Steve Henson, Adi Stav <stav@mercury.co.il>, James Yonan <jim@ntlp.com>*
14687 * Fix cipher selection routines: ciphers without encryption had no flags
14688 for the cipher strength set and where therefore not handled correctly
14689 by the selection routines (PR #130).
14693 * Fix EVP_dsa_sha macro.
14698 SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS
14699 for disabling the SSL 3.0/TLS 1.0 CBC vulnerability countermeasure
14700 that was added in OpenSSL 0.9.6d.
14702 As the countermeasure turned out to be incompatible with some
14703 broken SSL implementations, the new option is part of SSL_OP_ALL.
14704 SSL_OP_ALL is usually employed when compatibility with weird SSL
14705 implementations is desired (e.g. '-bugs' option to 's_client' and
14706 's_server'), so the new option is automatically set in many
14711 * Changes in security patch:
14713 Changes marked "(CHATS)" were sponsored by the Defense Advanced
14714 Research Projects Agency (DARPA) and Air Force Research Laboratory,
14715 Air Force Materiel Command, USAF, under agreement number
14718 * Add various sanity checks to asn1_get_length() to reject
14719 the ASN1 length bytes if they exceed sizeof(long), will appear
14720 negative or the content length exceeds the length of the
14721 supplied buffer. ([CVE-2002-0659])
14723 *Steve Henson, Adi Stav <stav@mercury.co.il>, James Yonan <jim@ntlp.com>*
14725 * Assertions for various potential buffer overflows, not known to
14726 happen in practice.
14728 *Ben Laurie (CHATS)*
14730 * Various temporary buffers to hold ASCII versions of integers were
14731 too small for 64 bit platforms. ([CVE-2002-0655])
14732 *Matthew Byng-Maddick <mbm@aldigital.co.uk> and Ben Laurie (CHATS)>*
14734 * Remote buffer overflow in SSL3 protocol - an attacker could
14735 supply an oversized session ID to a client. ([CVE-2002-0656])
14737 *Ben Laurie (CHATS)*
14739 * Remote buffer overflow in SSL2 protocol - an attacker could
14740 supply an oversized client master key. ([CVE-2002-0656])
14742 *Ben Laurie (CHATS)*
14744 ### Changes between 0.9.6c and 0.9.6d [9 May 2002]
14746 * Fix crypto/asn1/a_sign.c so that 'parameters' is omitted (not
14747 encoded as NULL) with id-dsa-with-sha1.
14749 *Nils Larsch <nla@trustcenter.de>; problem pointed out by Bodo Moeller*
14751 * Check various `X509_...()` return values in `apps/req.c`.
14753 *Nils Larsch <nla@trustcenter.de>*
14755 * Fix BASE64 decode (EVP_DecodeUpdate) for data with CR/LF ended lines:
14756 an end-of-file condition would erroneously be flagged, when the CRLF
14757 was just at the end of a processed block. The bug was discovered when
14758 processing data through a buffering memory BIO handing the data to a
14759 BASE64-decoding BIO. Bug fund and patch submitted by Pavel Tsekov
14760 <ptsekov@syntrex.com> and Nedelcho Stanev.
14764 * Implement a countermeasure against a vulnerability recently found
14765 in CBC ciphersuites in SSL 3.0/TLS 1.0: Send an empty fragment
14766 before application data chunks to avoid the use of known IVs
14767 with data potentially chosen by the attacker.
14771 * Fix length checks in ssl3_get_client_hello().
14775 * TLS/SSL library bugfix: use s->s3->in_read_app_data differently
14776 to prevent ssl3_read_internal() from incorrectly assuming that
14777 ssl3_read_bytes() found application data while handshake
14778 processing was enabled when in fact s->s3->in_read_app_data was
14779 merely automatically cleared during the initial handshake.
14781 *Bodo Moeller; problem pointed out by Arne Ansper <arne@ats.cyber.ee>*
14783 * Fix object definitions for Private and Enterprise: they were not
14784 recognized in their shortname (=lowercase) representation. Extend
14785 obj_dat.pl to issue an error when using undefined keywords instead
14786 of silently ignoring the problem (Svenning Sorensen
14787 <sss@sss.dnsalias.net>).
14791 * Fix DH_generate_parameters() so that it works for 'non-standard'
14792 generators, i.e. generators other than 2 and 5. (Previously, the
14793 code did not properly initialise the 'add' and 'rem' values to
14794 BN_generate_prime().)
14796 In the new general case, we do not insist that 'generator' is
14797 actually a primitive root: This requirement is rather pointless;
14798 a generator of the order-q subgroup is just as good, if not
14803 * Map new X509 verification errors to alerts. Discovered and submitted by
14804 Tom Wu <tom@arcot.com>.
14808 * Fix ssl3_pending() (ssl/s3_lib.c) to prevent SSL_pending() from
14809 returning non-zero before the data has been completely received
14810 when using non-blocking I/O.
14812 *Bodo Moeller; problem pointed out by John Hughes*
14814 * Some of the ciphers missed the strength entry (SSL_LOW etc).
14816 *Ben Laurie, Lutz Jaenicke*
14818 * Fix bug in SSL_clear(): bad sessions were not removed (found by
14819 Yoram Zahavi <YoramZ@gilian.com>).
14823 * Add information about CygWin 1.3 and on, and preserve proper
14824 configuration for the versions before that.
14826 *Corinna Vinschen <vinschen@redhat.com> and Richard Levitte*
14828 * Make removal from session cache (SSL_CTX_remove_session()) more robust:
14829 check whether we deal with a copy of a session and do not delete from
14830 the cache in this case. Problem reported by "Izhar Shoshani Levi"
14831 <izhar@checkpoint.com>.
14835 * Do not store session data into the internal session cache, if it
14836 is never intended to be looked up (SSL_SESS_CACHE_NO_INTERNAL_LOOKUP
14837 flag is set). Proposed by Aslam <aslam@funk.com>.
14841 * Have ASN1_BIT_STRING_set_bit() really clear a bit when the requested
14846 * [In 0.9.6d-engine release:]
14847 Fix a crashbug and a logic bug in hwcrhk_load_pubkey().
14849 *Toomas Kiisk <vix@cyber.ee> via Richard Levitte*
14851 * Add the configuration target linux-s390x.
14853 *Neale Ferguson <Neale.Ferguson@SoftwareAG-USA.com> via Richard Levitte*
14855 * The earlier bugfix for the SSL3_ST_SW_HELLO_REQ_C case of
14856 ssl3_accept (ssl/s3_srvr.c) incorrectly used a local flag
14857 variable as an indication that a ClientHello message has been
14858 received. As the flag value will be lost between multiple
14859 invocations of ssl3_accept when using non-blocking I/O, the
14860 function may not be aware that a handshake has actually taken
14861 place, thus preventing a new session from being added to the
14864 To avoid this problem, we now set s->new_session to 2 instead of
14865 using a local variable.
14867 *Lutz Jaenicke, Bodo Moeller*
14869 * Bugfix: Return -1 from ssl3_get_server_done (ssl3/s3_clnt.c)
14870 if the SSL_R_LENGTH_MISMATCH error is detected.
14872 *Geoff Thorpe, Bodo Moeller*
14874 * New 'shared_ldflag' column in Configure platform table.
14878 * Fix EVP_CIPHER_mode macro.
14880 *"Dan S. Camper" <dan@bti.net>*
14882 * Fix ssl3_read_bytes (ssl/s3_pkt.c): To ignore messages of unknown
14883 type, we must throw them away by setting rr->length to 0.
14885 *D P Chang <dpc@qualys.com>*
14887 ### Changes between 0.9.6b and 0.9.6c [21 dec 2001]
14889 * Fix BN_rand_range bug pointed out by Dominikus Scherkl
14890 <Dominikus.Scherkl@biodata.com>. (The previous implementation
14891 worked incorrectly for those cases where range = `10..._2` and
14892 `3*range` is two bits longer than range.)
14896 * Only add signing time to PKCS7 structures if it is not already
14901 * Fix crypto/objects/objects.h: "ld-ce" should be "id-ce",
14902 OBJ_ld_ce should be OBJ_id_ce.
14903 Also some ip-pda OIDs in crypto/objects/objects.txt were
14904 incorrect (cf. RFC 3039).
14906 *Matt Cooper, Frederic Giudicelli, Bodo Moeller*
14908 * Release CRYPTO_LOCK_DYNLOCK when CRYPTO_destroy_dynlockid()
14909 returns early because it has nothing to do.
14911 *Andy Schneider <andy.schneider@bjss.co.uk>*
14913 * [In 0.9.6c-engine release:]
14914 Fix mutex callback return values in crypto/engine/hw_ncipher.c.
14916 *Andy Schneider <andy.schneider@bjss.co.uk>*
14918 * [In 0.9.6c-engine release:]
14919 Add support for Cryptographic Appliance's keyserver technology.
14920 (Use engine 'keyclient')
14922 *Cryptographic Appliances and Geoff Thorpe*
14924 * Add a configuration entry for OS/390 Unix. The C compiler 'c89'
14925 is called via tools/c89.sh because arguments have to be
14926 rearranged (all '-L' options must appear before the first object
14929 *Richard Shapiro <rshapiro@abinitio.com>*
14931 * [In 0.9.6c-engine release:]
14932 Add support for Broadcom crypto accelerator cards, backported
14935 *Broadcom, Nalin Dahyabhai <nalin@redhat.com>, Mark Cox*
14937 * [In 0.9.6c-engine release:]
14938 Add support for SureWare crypto accelerator cards from
14939 Baltimore Technologies. (Use engine 'sureware')
14941 *Baltimore Technologies and Mark Cox*
14943 * [In 0.9.6c-engine release:]
14944 Add support for crypto accelerator cards from Accelerated
14945 Encryption Processing, www.aep.ie. (Use engine 'aep')
14947 *AEP Inc. and Mark Cox*
14949 * Add a configuration entry for gcc on UnixWare.
14951 *Gary Benson <gbenson@redhat.com>*
14953 * Change ssl/s2_clnt.c and ssl/s2_srvr.c so that received handshake
14954 messages are stored in a single piece (fixed-length part and
14955 variable-length part combined) and fix various bugs found on the way.
14959 * Disable caching in BIO_gethostbyname(), directly use gethostbyname()
14960 instead. BIO_gethostbyname() does not know what timeouts are
14961 appropriate, so entries would stay in cache even when they have
14963 *Bodo Moeller; problem pointed out by Rich Salz <rsalz@zolera.com>*
14965 * Change ssl23_get_client_hello (ssl/s23_srvr.c) behaviour when
14966 faced with a pathologically small ClientHello fragment that does
14967 not contain client_version: Instead of aborting with an error,
14968 simply choose the highest available protocol version (i.e.,
14969 TLS 1.0 unless it is disabled). In practice, ClientHello
14970 messages are never sent like this, but this change gives us
14971 strictly correct behaviour at least for TLS.
14975 * Fix SSL handshake functions and SSL_clear() such that SSL_clear()
14976 never resets s->method to s->ctx->method when called from within
14977 one of the SSL handshake functions.
14979 *Bodo Moeller; problem pointed out by Niko Baric*
14981 * In ssl3_get_client_hello (ssl/s3_srvr.c), generate a fatal alert
14982 (sent using the client's version number) if client_version is
14983 smaller than the protocol version in use. Also change
14984 ssl23_get_client_hello (ssl/s23_srvr.c) to select TLS 1.0 if
14985 the client demanded SSL 3.0 but only TLS 1.0 is enabled; then
14986 the client will at least see that alert.
14990 * Fix ssl3_get_message (ssl/s3_both.c) to handle message fragmentation
14995 * Avoid infinite loop in ssl3_get_message (ssl/s3_both.c) if a
14996 client receives HelloRequest while in a handshake.
14998 *Bodo Moeller; bug noticed by Andy Schneider <andy.schneider@bjss.co.uk>*
15000 * Bugfix in ssl3_accept (ssl/s3_srvr.c): Case SSL3_ST_SW_HELLO_REQ_C
15001 should end in 'break', not 'goto end' which circumvents various
15002 cleanups done in state SSL_ST_OK. But session related stuff
15003 must be disabled for SSL_ST_OK in the case that we just sent a
15006 Also avoid some overhead by not calling ssl_init_wbio_buffer()
15007 before just sending a HelloRequest.
15009 *Bodo Moeller, Eric Rescorla <ekr@rtfm.com>*
15011 * Fix ssl/s3_enc.c, ssl/t1_enc.c and ssl/s3_pkt.c so that we don't
15012 reveal whether illegal block cipher padding was found or a MAC
15013 verification error occurred. (Neither SSLerr() codes nor alerts
15014 are directly visible to potential attackers, but the information
15015 may leak via logfiles.)
15017 Similar changes are not required for the SSL 2.0 implementation
15018 because the number of padding bytes is sent in clear for SSL 2.0,
15019 and the extra bytes are just ignored. However ssl/s2_pkt.c
15020 failed to verify that the purported number of padding bytes is in
15025 * Add OpenUNIX-8 support including shared libraries
15026 (Boyd Lynn Gerber <gerberb@zenez.com>).
15030 * Improve RSA_padding_check_PKCS1_OAEP() check again to avoid
15031 'wristwatch attack' using huge encoding parameters (cf.
15032 James H. Manger's CRYPTO 2001 paper). Note that the
15033 RSA_PKCS1_OAEP_PADDING case of RSA_private_decrypt() does not use
15034 encoding parameters and hence was not vulnerable.
15038 * BN_sqr() bug fix.
15040 *Ulf Möller, reported by Jim Ellis <jim.ellis@cavium.com>*
15042 * Rabin-Miller test analyses assume uniformly distributed witnesses,
15043 so use BN_pseudo_rand_range() instead of using BN_pseudo_rand()
15044 followed by modular reduction.
15046 *Bodo Moeller; pointed out by Adam Young <AYoung1@NCSUS.JNJ.COM>*
15048 * Add BN_pseudo_rand_range() with obvious functionality: BN_rand_range()
15049 equivalent based on BN_pseudo_rand() instead of BN_rand().
15053 * s3_srvr.c: allow sending of large client certificate lists (> 16 kB).
15054 This function was broken, as the check for a new client hello message
15055 to handle SGC did not allow these large messages.
15056 (Tracked down by "Douglas E. Engert" <deengert@anl.gov>.)
15060 * Add alert descriptions for TLSv1 to `SSL_alert_desc_string[_long]()`.
15064 * Fix buggy behaviour of BIO_get_num_renegotiates() and BIO_ctrl()
15065 for BIO_C_GET_WRITE_BUF_SIZE ("Stephen Hinton" <shinton@netopia.com>).
15069 * Rework the configuration and shared library support for Tru64 Unix.
15070 The configuration part makes use of modern compiler features and
15071 still retains old compiler behavior for those that run older versions
15072 of the OS. The shared library support part includes a variant that
15073 uses the RPATH feature, and is available through the special
15074 configuration target "alpha-cc-rpath", which will never be selected
15077 *Tim Mooney <mooney@dogbert.cc.ndsu.NoDak.edu> via Richard Levitte*
15079 * In ssl3_get_key_exchange (ssl/s3_clnt.c), call ssl3_get_message()
15080 with the same message size as in ssl3_get_certificate_request().
15081 Otherwise, if no ServerKeyExchange message occurs, CertificateRequest
15082 messages might inadvertently be reject as too long.
15084 *Petr Lampa <lampa@fee.vutbr.cz>*
15086 * Enhanced support for IA-64 Unix platforms (well, Linux and HP-UX).
15090 * Modified SSL library such that the verify_callback that has been set
15091 specifically for an SSL object with SSL_set_verify() is actually being
15092 used. Before the change, a verify_callback set with this function was
15093 ignored and the verify_callback() set in the SSL_CTX at the time of
15094 the call was used. New function X509_STORE_CTX_set_verify_cb() introduced
15095 to allow the necessary settings.
15099 * Initialize static variable in crypto/dsa/dsa_lib.c and crypto/dh/dh_lib.c
15100 explicitly to NULL, as at least on Solaris 8 this seems not always to be
15101 done automatically (in contradiction to the requirements of the C
15102 standard). This made problems when used from OpenSSH.
15106 * In OpenSSL 0.9.6a and 0.9.6b, crypto/dh/dh_key.c ignored
15107 dh->length and always used
15109 BN_rand_range(priv_key, dh->p).
15111 BN_rand_range() is not necessary for Diffie-Hellman, and this
15112 specific range makes Diffie-Hellman unnecessarily inefficient if
15113 dh->length (recommended exponent length) is much smaller than the
15114 length of dh->p. We could use BN_rand_range() if the order of
15115 the subgroup was stored in the DH structure, but we only have
15120 BN_rand(priv_key, l, ...)
15122 where 'l' is dh->length if this is defined, or BN_num_bits(dh->p)-1
15129 RSA_eay_public_encrypt
15130 RSA_eay_private_decrypt
15131 RSA_eay_private_encrypt (signing)
15132 RSA_eay_public_decrypt (signature verification)
15134 (default implementations for RSA_public_encrypt,
15135 RSA_private_decrypt, RSA_private_encrypt, RSA_public_decrypt),
15136 always reject numbers >= n.
15140 * In crypto/rand/md_rand.c, use a new short-time lock CRYPTO_LOCK_RAND2
15141 to synchronize access to 'locking_thread'. This is necessary on
15142 systems where access to 'locking_thread' (an 'unsigned long'
15143 variable) is not atomic.
15147 * In crypto/rand/md_rand.c, set 'locking_thread' to current thread's ID
15148 *before* setting the 'crypto_lock_rand' flag. The previous code had
15149 a race condition if 0 is a valid thread ID.
15151 *Travis Vitek <vitek@roguewave.com>*
15153 * Add support for shared libraries under Irix.
15155 *Albert Chin-A-Young <china@thewrittenword.com>*
15157 * Add configuration option to build on Linux on both big-endian and
15158 little-endian MIPS.
15160 *Ralf Baechle <ralf@uni-koblenz.de>*
15162 * Add the possibility to create shared libraries on HP-UX.
15166 ### Changes between 0.9.6a and 0.9.6b [9 Jul 2001]
15168 * Change ssleay_rand_bytes (crypto/rand/md_rand.c)
15169 to avoid a SSLeay/OpenSSL PRNG weakness pointed out by
15170 Markku-Juhani O. Saarinen <markku-juhani.saarinen@nokia.com>:
15171 PRNG state recovery was possible based on the output of
15172 one PRNG request appropriately sized to gain knowledge on
15173 'md' followed by enough consecutive 1-byte PRNG requests
15174 to traverse all of 'state'.
15176 1. When updating 'md_local' (the current thread's copy of 'md')
15177 during PRNG output generation, hash all of the previous
15178 'md_local' value, not just the half used for PRNG output.
15180 2. Make the number of bytes from 'state' included into the hash
15181 independent from the number of PRNG bytes requested.
15183 The first measure alone would be sufficient to avoid
15184 Markku-Juhani's attack. (Actually it had never occurred
15185 to me that the half of 'md_local' used for chaining was the
15186 half from which PRNG output bytes were taken -- I had always
15187 assumed that the secret half would be used.) The second
15188 measure makes sure that additional data from 'state' is never
15189 mixed into 'md_local' in small portions; this heuristically
15190 further strengthens the PRNG.
15194 * Fix crypto/bn/asm/mips3.s.
15198 * When only the key is given to "enc", the IV is undefined. Print out
15199 an error message in this case.
15203 * Handle special case when X509_NAME is empty in X509 printing routines.
15207 * In dsa_do_verify (crypto/dsa/dsa_ossl.c), verify that r and s are
15208 positive and less than q.
15212 * Don't change `*pointer` in CRYPTO_add_lock() is add_lock_callback is
15213 used: it isn't thread safe and the add_lock_callback should handle
15216 *Paul Rose <Paul.Rose@bridge.com>*
15218 * Verify that incoming data obeys the block size in
15219 ssl3_enc (ssl/s3_enc.c) and tls1_enc (ssl/t1_enc.c).
15225 *Ulf Möller, Bodo Möller*
15227 * The countermeasure against Bleichbacher's attack on PKCS #1 v1.5
15228 RSA encryption was accidentally removed in s3_srvr.c in OpenSSL 0.9.5
15229 when fixing the server behaviour for backwards-compatible 'client
15230 hello' messages. (Note that the attack is impractical against
15231 SSL 3.0 and TLS 1.0 anyway because length and version checking
15232 means that the probability of guessing a valid ciphertext is
15233 around 2^-40; see section 5 in Bleichenbacher's CRYPTO '98
15236 Before 0.9.5, the countermeasure (hide the error by generating a
15237 random 'decryption result') did not work properly because
15238 ERR_clear_error() was missing, meaning that SSL_get_error() would
15239 detect the supposedly ignored error.
15241 Both problems are now fixed.
15245 * In crypto/bio/bf_buff.c, increase DEFAULT_BUFFER_SIZE to 4096
15246 (previously it was 1024).
15250 * Fix for compatibility mode trust settings: ignore trust settings
15251 unless some valid trust or reject settings are present.
15255 * Fix for blowfish EVP: its a variable length cipher.
15259 * Fix various bugs related to DSA S/MIME verification. Handle missing
15260 parameters in DSA public key structures and return an error in the
15261 DSA routines if parameters are absent.
15265 * In versions up to 0.9.6, RAND_file_name() resorted to file ".rnd"
15266 in the current directory if neither $RANDFILE nor $HOME was set.
15267 RAND_file_name() in 0.9.6a returned NULL in this case. This has
15268 caused some confusion to Windows users who haven't defined $HOME.
15269 Thus RAND_file_name() is changed again: e_os.h can define a
15270 DEFAULT_HOME, which will be used if $HOME is not set.
15271 For Windows, we use "C:"; on other platforms, we still require
15272 environment variables.
15274 * Move 'if (!initialized) RAND_poll()' into regions protected by
15275 CRYPTO_LOCK_RAND. This is not strictly necessary, but avoids
15276 having multiple threads call RAND_poll() concurrently.
15280 * In crypto/rand/md_rand.c, replace 'add_do_not_lock' flag by a
15281 combination of a flag and a thread ID variable.
15282 Otherwise while one thread is in ssleay_rand_bytes (which sets the
15283 flag), *other* threads can enter ssleay_add_bytes without obeying
15284 the CRYPTO_LOCK_RAND lock (and may even illegally release the lock
15285 that they do not hold after the first thread unsets add_do_not_lock).
15289 * Change bctest again: '-x' expressions are not available in all
15290 versions of 'test'.
15294 ### Changes between 0.9.6 and 0.9.6a [5 Apr 2001]
15296 * Fix a couple of memory leaks in PKCS7_dataDecode()
15298 *Steve Henson, reported by Heyun Zheng <hzheng@atdsprint.com>*
15300 * Change Configure and Makefiles to provide EXE_EXT, which will contain
15301 the default extension for executables, if any. Also, make the perl
15302 scripts that use symlink() to test if it really exists and use "cp"
15303 if it doesn't. All this made OpenSSL compilable and installable in
15308 * Fix for asn1_GetSequence() for indefinite length constructed data.
15309 If SEQUENCE is length is indefinite just set c->slen to the total
15310 amount of data available.
15312 *Steve Henson, reported by shige@FreeBSD.org*
15314 *This change does not apply to 0.9.7.*
15316 * Change bctest to avoid here-documents inside command substitution
15317 (workaround for FreeBSD /bin/sh bug).
15318 For compatibility with Ultrix, avoid shell functions (introduced
15319 in the bctest version that searches along $PATH).
15323 * Rename 'des_encrypt' to 'des_encrypt1'. This avoids the clashes
15324 with des_encrypt() defined on some operating systems, like Solaris
15329 * Check the result of RSA-CRT (see D. Boneh, R. DeMillo, R. Lipton:
15330 On the Importance of Eliminating Errors in Cryptographic
15331 Computations, J. Cryptology 14 (2001) 2, 101-119,
15332 <http://theory.stanford.edu/~dabo/papers/faults.ps.gz>).
15336 * MIPS assembler BIGNUM division bug fix.
15340 * Disabled incorrect Alpha assembler code.
15344 * Fix PKCS#7 decode routines so they correctly update the length
15345 after reading an EOC for the EXPLICIT tag.
15349 *This change does not apply to 0.9.7.*
15351 * Fix bug in PKCS#12 key generation routines. This was triggered
15352 if a 3DES key was generated with a 0 initial byte. Include
15353 PKCS12_BROKEN_KEYGEN compilation option to retain the old
15354 (but broken) behaviour.
15358 * Enhance bctest to search for a working bc along $PATH and print
15361 *Tim Rice <tim@multitalents.net> via Richard Levitte*
15363 * Fix memory leaks in err.c: free err_data string if necessary;
15364 don't write to the wrong index in ERR_set_error_data.
15368 * Implement ssl23_peek (analogous to ssl23_read), which previously
15373 * Replace rdtsc with `_emit` statements for VC++ version 5.
15375 *Jeremy Cooper <jeremy@baymoo.org>*
15377 * Make it possible to reuse SSLv2 sessions.
15381 * In copy_email() check for >= 0 as a return value for
15382 X509_NAME_get_index_by_NID() since 0 is a valid index.
15384 *Steve Henson reported by Massimiliano Pala <madwolf@opensca.org>*
15386 * Avoid coredump with unsupported or invalid public keys by checking if
15387 X509_get_pubkey() fails in PKCS7_verify(). Fix memory leak when
15388 PKCS7_verify() fails with non detached data.
15392 * Don't use getenv in library functions when run as setuid/setgid.
15393 New function OPENSSL_issetugid().
15397 * Avoid false positives in memory leak detection code (crypto/mem_dbg.c)
15398 due to incorrect handling of multi-threading:
15400 1. Fix timing glitch in the MemCheck_off() portion of CRYPTO_mem_ctrl().
15402 2. Fix logical glitch in is_MemCheck_on() aka CRYPTO_is_mem_check_on().
15404 3. Count how many times MemCheck_off() has been called so that
15405 nested use can be treated correctly. This also avoids
15406 inband-signalling in the previous code (which relied on the
15407 assumption that thread ID 0 is impossible).
15411 * Add "-rand" option also to s_client and s_server.
15415 * Fix CPU detection on Irix 6.x.
15416 *Kurt Hockenbury <khockenb@stevens-tech.edu> and
15417 "Bruce W. Forsberg" <bruce.forsberg@baesystems.com>*
15419 * Fix X509_NAME bug which produced incorrect encoding if X509_NAME
15424 *This change does not apply to 0.9.7.*
15426 * Use the cached encoding of an X509_NAME structure rather than
15427 copying it. This is apparently the reason for the libsafe "errors"
15428 but the code is actually correct.
15432 * Add new function BN_rand_range(), and fix DSA_sign_setup() to prevent
15433 Bleichenbacher's DSA attack.
15434 Extend BN_[pseudo_]rand: As before, top=1 forces the highest two bits
15435 to be set and top=0 forces the highest bit to be set; top=-1 is new
15436 and leaves the highest bit random.
15438 *Ulf Moeller, Bodo Moeller*
15440 * In the `NCONF_...`-based implementations for `CONF_...` queries
15441 (crypto/conf/conf_lib.c), if the input LHASH is NULL, avoid using
15442 a temporary CONF structure with the data component set to NULL
15443 (which gives segmentation faults in lh_retrieve).
15444 Instead, use NULL for the CONF pointer in CONF_get_string and
15445 CONF_get_number (which may use environment variables) and directly
15446 return NULL from CONF_get_section.
15450 * Fix potential buffer overrun for EBCDIC.
15454 * Tolerate nonRepudiation as being valid for S/MIME signing and certSign
15455 keyUsage if basicConstraints absent for a CA.
15459 * Make SMIME_write_PKCS7() write mail header values with a format that
15460 is more generally accepted (no spaces before the semicolon), since
15461 some programs can't parse those values properly otherwise. Also make
15462 sure BIO's that break lines after each write do not create invalid
15467 * Make the CRL encoding routines work with empty SEQUENCE OF. The
15468 macros previously used would not encode an empty SEQUENCE OF
15469 and break the signature.
15473 *This change does not apply to 0.9.7.*
15475 * Zero the premaster secret after deriving the master secret in
15480 * Add some EVP_add_digest_alias registrations (as found in
15481 OpenSSL_add_all_digests()) to SSL_library_init()
15482 aka OpenSSL_add_ssl_algorithms(). This provides improved
15483 compatibility with peers using X.509 certificates
15484 with unconventional AlgorithmIdentifier OIDs.
15488 * Fix for Irix with NO_ASM.
15490 *"Bruce W. Forsberg" <bruce.forsberg@baesystems.com>*
15492 * ./config script fixes.
15494 *Ulf Moeller, Richard Levitte*
15496 * Fix 'openssl passwd -1'.
15500 * Change PKCS12_key_gen_asc() so it can cope with non null
15501 terminated strings whose length is passed in the passlen
15502 parameter, for example from PEM callbacks. This was done
15503 by adding an extra length parameter to asc2uni().
15505 *Steve Henson, reported by <oddissey@samsung.co.kr>*
15507 * Fix C code generated by 'openssl dsaparam -C': If a BN_bin2bn
15508 call failed, free the DSA structure.
15512 * Fix to uni2asc() to cope with zero length Unicode strings.
15513 These are present in some PKCS#12 files.
15517 * Increase s2->wbuf allocation by one byte in ssl2_new (ssl/s2_lib.c).
15518 Otherwise do_ssl_write (ssl/s2_pkt.c) will write beyond buffer limits
15519 when writing a 32767 byte record.
15521 *Bodo Moeller; problem reported by Eric Day <eday@concentric.net>*
15523 * In `RSA_eay_public_{en,ed}crypt` and RSA_eay_mod_exp (rsa_eay.c),
15524 obtain lock CRYPTO_LOCK_RSA before setting `rsa->_method_mod_{n,p,q}`.
15526 (RSA objects have a reference count access to which is protected
15527 by CRYPTO_LOCK_RSA [see rsa_lib.c, s3_srvr.c, ssl_cert.c, ssl_rsa.c],
15528 so they are meant to be shared between threads.)
15529 *Bodo Moeller, Geoff Thorpe; original patch submitted by
15530 "Reddie, Steven" <Steven.Reddie@ca.com>*
15532 * Fix a deadlock in CRYPTO_mem_leaks().
15536 * Use better test patterns in bntest.
15540 * rand_win.c fix for Borland C.
15544 * BN_rshift bugfix for n == 0.
15548 * Add a 'bctest' script that checks for some known 'bc' bugs
15549 so that 'make test' does not abort just because 'bc' is broken.
15553 * Store verify_result within SSL_SESSION also for client side to
15554 avoid potential security hole. (Re-used sessions on the client side
15555 always resulted in verify_result==X509_V_OK, not using the original
15556 result of the server certificate verification.)
15560 * Fix ssl3_pending: If the record in s->s3->rrec is not of type
15561 SSL3_RT_APPLICATION_DATA, return 0.
15562 Similarly, change ssl2_pending to return 0 if SSL_in_init(s) is true.
15567 Both ssl2_peek and ssl3_peek, which were totally broken in earlier
15568 releases, have been re-implemented by renaming the previous
15569 implementations of ssl2_read and ssl3_read to ssl2_read_internal
15570 and ssl3_read_internal, respectively, and adding 'peek' parameters
15571 to them. The new ssl[23]_{read,peek} functions are calls to
15572 ssl[23]_read_internal with the 'peek' flag set appropriately.
15573 A 'peek' parameter has also been added to ssl3_read_bytes, which
15574 does the actual work for ssl3_read_internal.
15578 * Initialise "ex_data" member of RSA/DSA/DH structures prior to calling
15579 the method-specific "init()" handler. Also clean up ex_data after
15580 calling the method-specific "finish()" handler. Previously, this was
15581 happening the other way round.
15585 * Increase BN_CTX_NUM (the number of BIGNUMs in a BN_CTX) to 16.
15586 The previous value, 12, was not always sufficient for BN_mod_exp().
15590 * Make sure that shared libraries get the internal name engine with
15591 the full version number and not just 0. This should mark the
15592 shared libraries as not backward compatible. Of course, this should
15593 be changed again when we can guarantee backward binary compatibility.
15597 * Fix typo in get_cert_by_subject() in by_dir.c
15599 *Jean-Marc Desperrier <jean-marc.desperrier@certplus.com>*
15601 * Rework the system to generate shared libraries:
15603 - Make note of the expected extension for the shared libraries and
15604 if there is a need for symbolic links from for example libcrypto.so.0
15605 to libcrypto.so.0.9.7. There is extended info in Configure for
15608 - Make as few rebuilds of the shared libraries as possible.
15610 - Still avoid linking the OpenSSL programs with the shared libraries.
15612 - When installing, install the shared libraries separately from the
15617 * Fix SSL_CTX_set_read_ahead macro to actually use its argument.
15619 Copy SSL_CTX's read_ahead flag to SSL object directly in SSL_new
15620 and not in SSL_clear because the latter is also used by the
15621 accept/connect functions; previously, the settings made by
15622 SSL_set_read_ahead would be lost during the handshake.
15624 *Bodo Moeller; problems reported by Anders Gertz <gertz@epact.se>*
15626 * Correct util/mkdef.pl to be selective about disabled algorithms.
15627 Previously, it would create entries for disabled algorithms no
15632 * Added several new manual pages for SSL_* function.
15636 ### Changes between 0.9.5a and 0.9.6 [24 Sep 2000]
15638 * In ssl23_get_client_hello, generate an error message when faced
15639 with an initial SSL 3.0/TLS record that is too small to contain the
15640 first two bytes of the ClientHello message, i.e. client_version.
15641 (Note that this is a pathologic case that probably has never happened
15642 in real life.) The previous approach was to use the version number
15643 from the record header as a substitute; but our protocol choice
15644 should not depend on that one because it is not authenticated
15645 by the Finished messages.
15649 * More robust randomness gathering functions for Windows.
15651 *Jeffrey Altman <jaltman@columbia.edu>*
15653 * For compatibility reasons if the flag X509_V_FLAG_ISSUER_CHECK is
15654 not set then we don't setup the error code for issuer check errors
15655 to avoid possibly overwriting other errors which the callback does
15656 handle. If an application does set the flag then we assume it knows
15657 what it is doing and can handle the new informational codes
15662 * Fix for a nasty bug in ASN1_TYPE handling. ASN1_TYPE is used for
15663 a general "ANY" type, as such it should be able to decode anything
15664 including tagged types. However it didn't check the class so it would
15665 wrongly interpret tagged types in the same way as their universal
15666 counterpart and unknown types were just rejected. Changed so that the
15667 tagged and unknown types are handled in the same way as a SEQUENCE:
15668 that is the encoding is stored intact. There is also a new type
15669 "V_ASN1_OTHER" which is used when the class is not universal, in this
15670 case we have no idea what the actual type is so we just lump them all
15675 * On VMS, stdout may very well lead to a file that is written to
15676 in a record-oriented fashion. That means that every write() will
15677 write a separate record, which will be read separately by the
15678 programs trying to read from it. This can be very confusing.
15680 The solution is to put a BIO filter in the way that will buffer
15681 text until a linefeed is reached, and then write everything a
15682 line at a time, so every record written will be an actual line,
15683 not chunks of lines and not (usually doesn't happen, but I've
15684 seen it once) several lines in one record. BIO_f_linebuffer() is
15687 Currently, it's a VMS-only method, because that's where it has
15688 been tested well enough.
15692 * Remove 'optimized' squaring variant in BN_mod_mul_montgomery,
15693 it can return incorrect results.
15694 (Note: The buggy variant was not enabled in OpenSSL 0.9.5a,
15695 but it was in 0.9.6-beta[12].)
15699 * Disable the check for content being present when verifying detached
15700 signatures in pk7_smime.c. Some versions of Netscape (wrongly)
15701 include zero length content when signing messages.
15705 * New BIO_shutdown_wr macro, which invokes the BIO_C_SHUTDOWN_WR
15706 BIO_ctrl (for BIO pairs).
15710 * Add DSO method for VMS.
15714 * Bug fix: Montgomery multiplication could produce results with the
15719 * Add RPM specification openssl.spec and modify it to build three
15720 packages. The default package contains applications, application
15721 documentation and run-time libraries. The devel package contains
15722 include files, static libraries and function documentation. The
15723 doc package contains the contents of the doc directory. The original
15724 openssl.spec was provided by Damien Miller <djm@mindrot.org>.
15728 * Add a large number of documentation files for many SSL routines.
15730 *Lutz Jaenicke <Lutz.Jaenicke@aet.TU-Cottbus.DE>*
15732 * Add a configuration entry for Sony News 4.
15734 *NAKAJI Hiroyuki <nakaji@tutrp.tut.ac.jp>*
15736 * Don't set the two most significant bits to one when generating a
15737 random number < q in the DSA library.
15741 * New SSL API mode 'SSL_MODE_AUTO_RETRY'. This disables the default
15742 behaviour that SSL_read may result in SSL_ERROR_WANT_READ (even if
15743 the underlying transport is blocking) if a handshake took place.
15744 (The default behaviour is needed by applications such as s_client
15745 and s_server that use select() to determine when to use SSL_read;
15746 but for applications that know in advance when to expect data, it
15747 just makes things more complicated.)
15751 * Add RAND_egd_bytes(), which gives control over the number of bytes read
15756 * Add a few more EBCDIC conditionals that make `req` and `x509`
15757 work better on such systems.
15759 *Martin Kraemer <Martin.Kraemer@MchP.Siemens.De>*
15761 * Add two demo programs for PKCS12_parse() and PKCS12_create().
15762 Update PKCS12_parse() so it copies the friendlyName and the
15763 keyid to the certificates aux info.
15767 * Fix bug in PKCS7_verify() which caused an infinite loop
15768 if there was more than one signature.
15770 *Sven Uszpelkat <su@celocom.de>*
15772 * Major change in util/mkdef.pl to include extra information
15773 about each symbol, as well as presenting variables as well
15774 as functions. This change means that there's n more need
15775 to rebuild the .num files when some algorithms are excluded.
15779 * Allow the verify time to be set by an application,
15780 rather than always using the current time.
15784 * Phase 2 verify code reorganisation. The certificate
15785 verify code now looks up an issuer certificate by a
15786 number of criteria: subject name, authority key id
15787 and key usage. It also verifies self signed certificates
15788 by the same criteria. The main comparison function is
15789 X509_check_issued() which performs these checks.
15791 Lot of changes were necessary in order to support this
15792 without completely rewriting the lookup code.
15794 Authority and subject key identifier are now cached.
15796 The LHASH 'certs' is X509_STORE has now been replaced
15797 by a STACK_OF(X509_OBJECT). This is mainly because an
15798 LHASH can't store or retrieve multiple objects with
15799 the same hash value.
15801 As a result various functions (which were all internal
15802 use only) have changed to handle the new X509_STORE
15803 structure. This will break anything that messed round
15804 with X509_STORE internally.
15806 The functions X509_STORE_add_cert() now checks for an
15807 exact match, rather than just subject name.
15809 The X509_STORE API doesn't directly support the retrieval
15810 of multiple certificates matching a given criteria, however
15811 this can be worked round by performing a lookup first
15812 (which will fill the cache with candidate certificates)
15813 and then examining the cache for matches. This is probably
15814 the best we can do without throwing out X509_LOOKUP
15815 entirely (maybe later...).
15817 The X509_VERIFY_CTX structure has been enhanced considerably.
15819 All certificate lookup operations now go via a get_issuer()
15820 callback. Although this currently uses an X509_STORE it
15821 can be replaced by custom lookups. This is a simple way
15822 to bypass the X509_STORE hackery necessary to make this
15823 work and makes it possible to use more efficient techniques
15824 in future. A very simple version which uses a simple
15825 STACK for its trusted certificate store is also provided
15826 using X509_STORE_CTX_trusted_stack().
15828 The verify_cb() and verify() callbacks now have equivalents
15829 in the X509_STORE_CTX structure.
15831 X509_STORE_CTX also has a 'flags' field which can be used
15832 to customise the verify behaviour.
15836 * Add new PKCS#7 signing option PKCS7_NOSMIMECAP which
15837 excludes S/MIME capabilities.
15841 * When a certificate request is read in keep a copy of the
15842 original encoding of the signed data and use it when outputting
15843 again. Signatures then use the original encoding rather than
15844 a decoded, encoded version which may cause problems if the
15845 request is improperly encoded.
15849 * For consistency with other BIO_puts implementations, call
15850 buffer_write(b, ...) directly in buffer_puts instead of calling
15853 In BIO_puts, increment b->num_write as in BIO_write.
15855 *Peter.Sylvester@EdelWeb.fr*
15857 * Fix BN_mul_word for the case where the word is 0. (We have to use
15858 BN_zero, we may not return a BIGNUM with an array consisting of
15859 words set to zero.)
15863 * Avoid calling abort() from within the library when problems are
15864 detected, except if preprocessor symbols have been defined
15865 (such as REF_CHECK, BN_DEBUG etc.).
15869 * New openssl application 'rsautl'. This utility can be
15870 used for low-level RSA operations. DER public key
15871 BIO/fp routines also added.
15875 * New Configure entry and patches for compiling on QNX 4.
15877 *Andreas Schneider <andreas@ds3.etech.fh-hamburg.de>*
15879 * A demo state-machine implementation was sponsored by
15880 Nuron (<http://www.nuron.com/>) and is now available in
15881 demos/state_machine.
15885 * New options added to the 'dgst' utility for signature
15886 generation and verification.
15890 * Unrecognized PKCS#7 content types are now handled via a
15891 catch all ASN1_TYPE structure. This allows unsupported
15892 types to be stored as a "blob" and an application can
15893 encode and decode it manually.
15897 * Fix various signed/unsigned issues to make a_strex.c
15898 compile under VC++.
15900 *Oscar Jacobsson <oscar.jacobsson@celocom.com>*
15902 * ASN1 fixes. i2d_ASN1_OBJECT was not returning the correct
15903 length if passed a buffer. ASN1_INTEGER_to_BN failed
15904 if passed a NULL BN and its argument was negative.
15906 *Steve Henson, pointed out by Sven Heiberg <sven@tartu.cyber.ee>*
15908 * Modification to PKCS#7 encoding routines to output definite
15909 length encoding. Since currently the whole structures are in
15910 memory there's not real point in using indefinite length
15911 constructed encoding. However if OpenSSL is compiled with
15912 the flag PKCS7_INDEFINITE_ENCODING the old form is used.
15916 * Added BIO_vprintf() and BIO_vsnprintf().
15920 * Added more prefixes to parse for in the strings written
15921 through a logging bio, to cover all the levels that are available
15922 through syslog. The prefixes are now:
15924 PANIC, EMERG, EMR => LOG_EMERG
15925 ALERT, ALR => LOG_ALERT
15926 CRIT, CRI => LOG_CRIT
15927 ERROR, ERR => LOG_ERR
15928 WARNING, WARN, WAR => LOG_WARNING
15929 NOTICE, NOTE, NOT => LOG_NOTICE
15930 INFO, INF => LOG_INFO
15931 DEBUG, DBG => LOG_DEBUG
15933 and as before, if none of those prefixes are present at the
15934 beginning of the string, LOG_ERR is chosen.
15936 On Win32, the `LOG_*` levels are mapped according to this:
15938 LOG_EMERG, LOG_ALERT, LOG_CRIT, LOG_ERR => EVENTLOG_ERROR_TYPE
15939 LOG_WARNING => EVENTLOG_WARNING_TYPE
15940 LOG_NOTICE, LOG_INFO, LOG_DEBUG => EVENTLOG_INFORMATION_TYPE
15944 * Made it possible to reconfigure with just the configuration
15945 argument "reconf" or "reconfigure". The command line arguments
15946 are stored in Makefile.ssl in the variable CONFIGURE_ARGS,
15947 and are retrieved from there when reconfiguring.
15953 *Assar Westerlund <assar@sics.se>, Richard Levitte*
15955 * Add the arguments -CAfile and -CApath to the pkcs12 utility.
15959 * The obj_dat.pl script was messing up the sorting of object
15960 names. The reason was that it compared the quoted version
15961 of strings as a result "OCSP" > "OCSP Signing" because
15962 " > SPACE. Changed script to store unquoted versions of
15963 names and add quotes on output. It was also omitting some
15964 names from the lookup table if they were given a default
15965 value (that is if SN is missing it is given the same
15966 value as LN and vice versa), these are now added on the
15967 grounds that if an object has a name we should be able to
15968 look it up. Finally added warning output when duplicate
15969 short or long names are found.
15973 * Changes needed for Tandem NSK.
15975 *Scott Uroff <scott@xypro.com>*
15977 * Fix SSL 2.0 rollback checking: Due to an off-by-one error in
15978 RSA_padding_check_SSLv23(), special padding was never detected
15979 and thus the SSL 3.0/TLS 1.0 countermeasure against protocol
15980 version rollback attacks was not effective.
15982 In s23_clnt.c, don't use special rollback-attack detection padding
15983 (RSA_SSLV23_PADDING) if SSL 2.0 is the only protocol enabled in the
15984 client; similarly, in s23_srvr.c, don't do the rollback check if
15985 SSL 2.0 is the only protocol enabled in the server.
15989 * Make it possible to get hexdumps of unprintable data with 'openssl
15990 asn1parse'. By implication, the functions ASN1_parse_dump() and
15991 BIO_dump_indent() are added.
15995 * New functions ASN1_STRING_print_ex() and X509_NAME_print_ex()
15996 these print out strings and name structures based on various
15997 flags including RFC2253 support and proper handling of
15998 multibyte characters. Added options to the 'x509' utility
15999 to allow the various flags to be set.
16003 * Various fixes to use ASN1_TIME instead of ASN1_UTCTIME.
16004 Also change the functions X509_cmp_current_time() and
16005 X509_gmtime_adj() work with an ASN1_TIME structure,
16006 this will enable certificates using GeneralizedTime in validity
16007 dates to be checked.
16011 * Make the NEG_PUBKEY_BUG code (which tolerates invalid
16012 negative public key encodings) on by default,
16013 NO_NEG_PUBKEY_BUG can be set to disable it.
16017 * New function c2i_ASN1_OBJECT() which acts on ASN1_OBJECT
16018 content octets. An i2c_ASN1_OBJECT is unnecessary because
16019 the encoding can be trivially obtained from the structure.
16023 * crypto/err.c locking bugfix: Use write locks (`CRYPTO_w_[un]lock`),
16024 not read locks (`CRYPTO_r_[un]lock`).
16028 * A first attempt at creating official support for shared
16029 libraries through configuration. I've kept it so the
16030 default is static libraries only, and the OpenSSL programs
16031 are always statically linked for now, but there are
16032 preparations for dynamic linking in place.
16033 This has been tested on Linux and Tru64.
16037 * Randomness polling function for Win9x, as described in:
16038 Peter Gutmann, Software Generation of Practically Strong
16043 * Fix so PRNG is seeded in req if using an already existing
16048 * New options to smime application. -inform and -outform
16049 allow alternative formats for the S/MIME message including
16050 PEM and DER. The -content option allows the content to be
16051 specified separately. This should allow things like Netscape
16052 form signing output easier to verify.
16056 * Fix the ASN1 encoding of tags using the 'long form'.
16060 * New ASN1 functions, `i2c_*` and `c2i_*` for INTEGER and BIT
16061 STRING types. These convert content octets to and from the
16062 underlying type. The actual tag and length octets are
16063 already assumed to have been read in and checked. These
16064 are needed because all other string types have virtually
16065 identical handling apart from the tag. By having versions
16066 of the ASN1 functions that just operate on content octets
16067 IMPLICIT tagging can be handled properly. It also allows
16068 the ASN1_ENUMERATED code to be cut down because ASN1_ENUMERATED
16069 and ASN1_INTEGER are identical apart from the tag.
16073 * Change the handling of OID objects as follows:
16075 - New object identifiers are inserted in objects.txt, following
16076 the syntax given in [crypto/objects/README.md](crypto/objects/README.md).
16077 - objects.pl is used to process obj_mac.num and create a new
16079 - obj_dat.pl is used to create a new obj_dat.h, using the data in
16082 This is currently kind of a hack, and the perl code in objects.pl
16083 isn't very elegant, but it works as I intended. The simplest way
16084 to check that it worked correctly is to look in obj_dat.h and
16085 check the array nid_objs and make sure the objects haven't moved
16086 around (this is important!). Additions are OK, as well as
16087 consistent name changes.
16091 * Add BSD-style MD5-based passwords to 'openssl passwd' (option '-1').
16095 * Addition of the command line parameter '-rand file' to 'openssl req'.
16096 The given file adds to whatever has already been seeded into the
16097 random pool through the RANDFILE configuration file option or
16098 environment variable, or the default random state file.
16102 * mkstack.pl now sorts each macro group into lexical order.
16103 Previously the output order depended on the order the files
16104 appeared in the directory, resulting in needless rewriting
16109 * Patches to make OpenSSL compile under Win32 again. Mostly
16110 work arounds for the VC++ problem that it treats func() as
16111 func(void). Also stripped out the parts of mkdef.pl that
16112 added extra typesafe functions: these no longer exist.
16116 * Reorganisation of the stack code. The macros are now all
16117 collected in safestack.h . Each macro is defined in terms of
16118 a "stack macro" of the form `SKM_<name>(type, a, b)`. The
16119 DEBUG_SAFESTACK is now handled in terms of function casts,
16120 this has the advantage of retaining type safety without the
16121 use of additional functions. If DEBUG_SAFESTACK is not defined
16122 then the non typesafe macros are used instead. Also modified the
16123 mkstack.pl script to handle the new form. Needs testing to see
16124 if which (if any) compilers it chokes and maybe make DEBUG_SAFESTACK
16125 the default if no major problems. Similar behaviour for ASN1_SET_OF
16126 and PKCS12_STACK_OF.
16130 * When some versions of IIS use the 'NET' form of private key the
16131 key derivation algorithm is different. Normally MD5(password) is
16132 used as a 128 bit RC4 key. In the modified case
16133 MD5(MD5(password) + "SGCKEYSALT") is used instead. Added some
16134 new functions i2d_RSA_NET(), d2i_RSA_NET() etc which are the same
16135 as the old Netscape_RSA functions except they have an additional
16136 'sgckey' parameter which uses the modified algorithm. Also added
16137 an -sgckey command line option to the rsa utility. Thanks to
16138 Adrian Peck <bertie@ncipher.com> for posting details of the modified
16139 algorithm to openssl-dev.
16143 * The evp_local.h macros were using 'c.##kname' which resulted in
16144 invalid expansion on some systems (SCO 5.0.5 for example).
16145 Corrected to 'c.kname'.
16147 *Phillip Porch <root@theporch.com>*
16149 * New X509_get1_email() and X509_REQ_get1_email() functions that return
16150 a STACK of email addresses from a certificate or request, these look
16151 in the subject name and the subject alternative name extensions and
16152 omit any duplicate addresses.
16156 * Re-implement BN_mod_exp2_mont using independent (and larger) windows.
16157 This makes DSA verification about 2 % faster.
16161 * Increase maximum window size in `BN_mod_exp_...` to 6 bits instead of 5
16162 (meaning that now 2^5 values will be precomputed, which is only 4 KB
16163 plus overhead for 1024 bit moduli).
16164 This makes exponentiations about 0.5 % faster for 1024 bit
16165 exponents (as measured by "openssl speed rsa2048").
16169 * Rename memory handling macros to avoid conflicts with other
16171 Malloc => OPENSSL_malloc
16172 Malloc_locked => OPENSSL_malloc_locked
16173 Realloc => OPENSSL_realloc
16174 Free => OPENSSL_free
16178 * New function BN_mod_exp_mont_word for small bases (roughly 15%
16179 faster than BN_mod_exp_mont, i.e. 7% for a full DH exchange).
16183 * CygWin32 support.
16185 *John Jarvie <jjarvie@newsguy.com>*
16187 * The type-safe stack code has been rejigged. It is now only compiled
16188 in when OpenSSL is configured with the DEBUG_SAFESTACK option and
16189 by default all type-specific stack functions are "#define"d back to
16190 standard stack functions. This results in more streamlined output
16191 but retains the type-safety checking possibilities of the original
16196 * The STACK code has been cleaned up, and certain type declarations
16197 that didn't make a lot of sense have been brought in line. This has
16198 also involved a cleanup of sorts in safestack.h to more correctly
16199 map type-safe stack functions onto their plain stack counterparts.
16200 This work has also resulted in a variety of "const"ifications of
16201 lots of the code, especially `_cmp` operations which should normally
16202 be prototyped with "const" parameters anyway.
16206 * When generating bytes for the first time in md_rand.c, 'stir the pool'
16207 by seeding with STATE_SIZE dummy bytes (with zero entropy count).
16208 (The PRNG state consists of two parts, the large pool 'state' and 'md',
16209 where all of 'md' is used each time the PRNG is used, but 'state'
16210 is used only indexed by a cyclic counter. As entropy may not be
16211 well distributed from the beginning, 'md' is important as a
16212 chaining variable. However, the output function chains only half
16213 of 'md', i.e. 80 bits. ssleay_rand_add, on the other hand, chains
16214 all of 'md', and seeding with STATE_SIZE dummy bytes will result
16215 in all of 'state' being rewritten, with the new values depending
16216 on virtually all of 'md'. This overcomes the 80 bit limitation.)
16220 * In ssl/s2_clnt.c and ssl/s3_clnt.c, call ERR_clear_error() when
16221 the handshake is continued after ssl_verify_cert_chain();
16222 otherwise, if SSL_VERIFY_NONE is set, remaining error codes
16223 can lead to 'unexplainable' connection aborts later.
16225 *Bodo Moeller; problem tracked down by Lutz Jaenicke*
16227 * Major EVP API cipher revision.
16228 Add hooks for extra EVP features. This allows various cipher
16229 parameters to be set in the EVP interface. Support added for variable
16230 key length ciphers via the EVP_CIPHER_CTX_set_key_length() function and
16231 setting of RC2 and RC5 parameters.
16233 Modify EVP_OpenInit() and EVP_SealInit() to cope with variable key length
16236 Remove lots of duplicated code from the EVP library. For example *every*
16237 cipher init() function handles the 'iv' in the same way according to the
16238 cipher mode. They also all do nothing if the 'key' parameter is NULL and
16239 for CFB and OFB modes they zero ctx->num.
16241 New functionality allows removal of S/MIME code RC2 hack.
16243 Most of the routines have the same form and so can be declared in terms
16246 By shifting this to the top level EVP_CipherInit() it can be removed from
16247 all individual ciphers. If the cipher wants to handle IVs or keys
16248 differently it can set the EVP_CIPH_CUSTOM_IV or EVP_CIPH_ALWAYS_CALL_INIT
16251 Change lots of functions like EVP_EncryptUpdate() to now return a
16252 value: although software versions of the algorithms cannot fail
16253 any installed hardware versions can.
16257 * Implement SSL_OP_TLS_ROLLBACK_BUG: In ssl3_get_client_key_exchange, if
16258 this option is set, tolerate broken clients that send the negotiated
16259 protocol version number instead of the requested protocol version
16264 * Call dh_tmp_cb (set by `..._TMP_DH_CB`) with correct 'is_export' flag;
16265 i.e. non-zero for export ciphersuites, zero otherwise.
16266 Previous versions had this flag inverted, inconsistent with
16267 rsa_tmp_cb (..._TMP_RSA_CB).
16269 *Bodo Moeller; problem reported by Amit Chopra*
16271 * Add missing DSA library text string. Work around for some IIS
16272 key files with invalid SEQUENCE encoding.
16276 * Add a document (doc/standards.txt) that list all kinds of standards
16277 and so on that are implemented in OpenSSL.
16281 * Enhance c_rehash script. Old version would mishandle certificates
16282 with the same subject name hash and wouldn't handle CRLs at all.
16283 Added -fingerprint option to crl utility, to support new c_rehash
16288 * Eliminate non-ANSI declarations in crypto.h and stack.h.
16292 * Fix for SSL server purpose checking. Server checking was
16293 rejecting certificates which had extended key usage present
16294 but no ssl client purpose.
16296 *Steve Henson, reported by Rene Grosser <grosser@hisolutions.com>*
16298 * Make PKCS#12 code work with no password. The PKCS#12 spec
16299 is a little unclear about how a blank password is handled.
16300 Since the password in encoded as a BMPString with terminating
16301 double NULL a zero length password would end up as just the
16302 double NULL. However no password at all is different and is
16303 handled differently in the PKCS#12 key generation code. NS
16304 treats a blank password as zero length. MSIE treats it as no
16305 password on export: but it will try both on import. We now do
16306 the same: PKCS12_parse() tries zero length and no password if
16307 the password is set to "" or NULL (NULL is now a valid password:
16308 it wasn't before) as does the pkcs12 application.
16312 * Bugfixes in `apps/x509.c`: Avoid a memory leak; and don't use
16313 perror when PEM_read_bio_X509_REQ fails, the error message must
16314 be obtained from the error queue.
16318 * Avoid 'thread_hash' memory leak in crypto/err/err.c by freeing
16319 it in ERR_remove_state if appropriate, and change ERR_get_state
16320 accordingly to avoid race conditions (this is necessary because
16321 thread_hash is no longer constant once set).
16325 * Bugfix for linux-elf makefile.one.
16329 * RSA_get_default_method() will now cause a default
16330 RSA_METHOD to be chosen if one doesn't exist already.
16331 Previously this was only set during a call to RSA_new()
16332 or RSA_new_method(NULL) meaning it was possible for
16333 RSA_get_default_method() to return NULL.
16337 * Added native name translation to the existing DSO code
16338 that will convert (if the flag to do so is set) filenames
16339 that are sufficiently small and have no path information
16340 into a canonical native form. Eg. "blah" converted to
16341 "libblah.so" or "blah.dll" etc.
16345 * New function ERR_error_string_n(e, buf, len) which is like
16346 ERR_error_string(e, buf), but writes at most 'len' bytes
16347 including the 0 terminator. For ERR_error_string_n, 'buf'
16350 *Damien Miller <djm@mindrot.org>, Bodo Moeller*
16352 * CONF library reworked to become more general. A new CONF
16353 configuration file reader "class" is implemented as well as a
16354 new functions (`NCONF_*`, for "New CONF") to handle it. The now
16355 old `CONF_*` functions are still there, but are reimplemented to
16356 work in terms of the new functions. Also, a set of functions
16357 to handle the internal storage of the configuration data is
16358 provided to make it easier to write new configuration file
16359 reader "classes" (I can definitely see something reading a
16360 configuration file in XML format, for example), called `_CONF_*`,
16361 or "the configuration storage API"...
16363 The new configuration file reading functions are:
16365 NCONF_new, NCONF_free, NCONF_load, NCONF_load_fp, NCONF_load_bio,
16366 NCONF_get_section, NCONF_get_string, NCONF_get_numbre
16368 NCONF_default, NCONF_WIN32
16370 NCONF_dump_fp, NCONF_dump_bio
16372 NCONF_default and NCONF_WIN32 are method (or "class") choosers,
16373 NCONF_new creates a new CONF object. This works in the same way
16374 as other interfaces in OpenSSL, like the BIO interface.
16375 `NCONF_dump_*` dump the internal storage of the configuration file,
16376 which is useful for debugging. All other functions take the same
16377 arguments as the old `CONF_*` functions with the exception of the
16378 first that must be a `CONF *` instead of a `LHASH *`.
16380 To make it easier to use the new classes with the old `CONF_*` functions,
16381 the function CONF_set_default_method is provided.
16385 * Add '-tls1' option to 'openssl ciphers', which was already
16386 mentioned in the documentation but had not been implemented.
16387 (This option is not yet really useful because even the additional
16388 experimental TLS 1.0 ciphers are currently treated as SSL 3.0 ciphers.)
16392 * Initial DSO code added into libcrypto for letting OpenSSL (and
16393 OpenSSL-based applications) load shared libraries and bind to
16394 them in a portable way.
16396 *Geoff Thorpe, with contributions from Richard Levitte*
16398 ### Changes between 0.9.5 and 0.9.5a [1 Apr 2000]
16400 * Make sure _lrotl and _lrotr are only used with MSVC.
16402 * Use lock CRYPTO_LOCK_RAND correctly in ssleay_rand_status
16403 (the default implementation of RAND_status).
16405 * Rename openssl x509 option '-crlext', which was added in 0.9.5,
16406 to '-clrext' (= clear extensions), as intended and documented.
16407 *Bodo Moeller; inconsistency pointed out by Michael Attili
16408 <attili@amaxo.com>*
16410 * Fix for HMAC. It wasn't zeroing the rest of the block if the key length
16411 was larger than the MD block size.
16413 *Steve Henson, pointed out by Yost William <YostW@tce.com>*
16415 * Modernise PKCS12_parse() so it uses STACK_OF(X509) for its ca argument
16416 fix a leak when the ca argument was passed as NULL. Stop X509_PUBKEY_set()
16417 using the passed key: if the passed key was a private key the result
16418 of X509_print(), for example, would be to print out all the private key
16423 * des_quad_cksum() byte order bug fix.
16424 *Ulf Möller, using the problem description in krb4-0.9.7, where
16425 the solution is attributed to Derrick J Brashear <shadow@DEMENTIA.ORG>*
16427 * Fix so V_ASN1_APP_CHOOSE works again: however its use is strongly
16430 *Steve Henson, pointed out by Brian Korver <briank@cs.stanford.edu>*
16432 * For easily testing in shell scripts whether some command
16433 'openssl XXX' exists, the new pseudo-command 'openssl no-XXX'
16434 returns with exit code 0 iff no command of the given name is available.
16435 'no-XXX' is printed in this case, 'XXX' otherwise. In both cases,
16436 the output goes to stdout and nothing is printed to stderr.
16437 Additional arguments are always ignored.
16439 Since for each cipher there is a command of the same name,
16440 the 'no-cipher' compilation switches can be tested this way.
16442 ('openssl no-XXX' is not able to detect pseudo-commands such
16443 as 'quit', 'list-XXX-commands', or 'no-XXX' itself.)
16447 * Update test suite so that 'make test' succeeds in 'no-rsa' configuration.
16451 * For SSL_[CTX_]set_tmp_dh, don't create a DH key if SSL_OP_SINGLE_DH_USE
16452 is set; it will be thrown away anyway because each handshake creates
16454 ssl_cert_dup, which is used by SSL_new, now copies DH keys in addition
16455 to parameters -- in previous versions (since OpenSSL 0.9.3) the
16456 'default key' from SSL_CTX_set_tmp_dh would always be lost, meaning
16457 you effectively got SSL_OP_SINGLE_DH_USE when using this macro.
16461 * New s_client option -ign_eof: EOF at stdin is ignored, and
16462 'Q' and 'R' lose their special meanings (quit/renegotiate).
16463 This is part of what -quiet does; unlike -quiet, -ign_eof
16464 does not suppress any output.
16468 * Add compatibility options to the purpose and trust code. The
16469 purpose X509_PURPOSE_ANY is "any purpose" which automatically
16470 accepts a certificate or CA, this was the previous behaviour,
16471 with all the associated security issues.
16473 X509_TRUST_COMPAT is the old trust behaviour: only and
16474 automatically trust self signed roots in certificate store. A
16475 new trust setting X509_TRUST_DEFAULT is used to specify that
16476 a purpose has no associated trust setting and it should instead
16477 use the value in the default purpose.
16481 * Fix the PKCS#8 DSA private key code so it decodes keys again
16482 and fix a memory leak.
16486 * In util/mkerr.pl (which implements 'make errors'), preserve
16487 reason strings from the previous version of the .c file, as
16488 the default to have only downcase letters (and digits) in
16489 automatically generated reasons codes is not always appropriate.
16493 * In ERR_load_ERR_strings(), build an ERR_LIB_SYS error reason table
16494 using strerror. Previously, ERR_reason_error_string() returned
16495 library names as reason strings for SYSerr; but SYSerr is a special
16496 case where small numbers are errno values, not library numbers.
16500 * Add '-dsaparam' option to 'openssl dhparam' application. This
16501 converts DSA parameters into DH parameters. (When creating parameters,
16502 DSA_generate_parameters is used.)
16506 * Include 'length' (recommended exponent length) in C code generated
16507 by 'openssl dhparam -C'.
16511 * The second argument to set_label in perlasm was already being used
16512 so couldn't be used as a "file scope" flag. Moved to third argument
16517 * In PEM_ASN1_write_bio and some other functions, use RAND_pseudo_bytes
16518 instead of RAND_bytes for encryption IVs and salts.
16522 * Include RAND_status() into RAND_METHOD instead of implementing
16523 it only for md_rand.c Otherwise replacing the PRNG by calling
16524 RAND_set_rand_method would be impossible.
16528 * Don't let DSA_generate_key() enter an infinite loop if the random
16529 number generation fails.
16533 * New 'rand' application for creating pseudo-random output.
16537 * Added configuration support for Linux/IA64
16539 *Rolf Haberrecker <rolf@suse.de>*
16541 * Assembler module support for Mingw32.
16545 * Shared library support for HPUX (in shlib/).
16547 *Lutz Jaenicke <Lutz.Jaenicke@aet.TU-Cottbus.DE> and Anonymous*
16549 * Shared library support for Solaris gcc.
16551 *Lutz Behnke <behnke@trustcenter.de>*
16553 ### Changes between 0.9.4 and 0.9.5 [28 Feb 2000]
16555 * PKCS7_encrypt() was adding text MIME headers twice because they
16556 were added manually and by SMIME_crlf_copy().
16560 * In bntest.c don't call BN_rand with zero bits argument.
16562 *Steve Henson, pointed out by Andrew W. Gray <agray@iconsinc.com>*
16564 * BN_mul bugfix: In bn_mul_part_recursion() only the a>a[n] && b>b[n]
16565 case was implemented. This caused BN_div_recp() to fail occasionally.
16569 * Add an optional second argument to the set_label() in the perl
16570 assembly language builder. If this argument exists and is set
16571 to 1 it signals that the assembler should use a symbol whose
16572 scope is the entire file, not just the current function. This
16573 is needed with MASM which uses the format label:: for this scope.
16575 *Steve Henson, pointed out by Peter Runestig <peter@runestig.com>*
16577 * Change the ASN1 types so they are typedefs by default. Before
16578 almost all types were #define'd to ASN1_STRING which was causing
16579 STACK_OF() problems: you couldn't declare STACK_OF(ASN1_UTF8STRING)
16584 * Change names of new functions to the new get1/get0 naming
16585 convention: After 'get1', the caller owns a reference count
16586 and has to call `..._free`; 'get0' returns a pointer to some
16587 data structure without incrementing reference counters.
16588 (Some of the existing 'get' functions increment a reference
16589 counter, some don't.)
16590 Similarly, 'set1' and 'add1' functions increase reference
16591 counters or duplicate objects.
16595 * Allow for the possibility of temp RSA key generation failure:
16596 the code used to assume it always worked and crashed on failure.
16600 * Fix potential buffer overrun problem in BIO_printf().
16601 *Ulf Möller, using public domain code by Patrick Powell; problem
16602 pointed out by David Sacerdote <das33@cornell.edu>*
16604 * Support EGD <http://www.lothar.com/tech/crypto/>. New functions
16605 RAND_egd() and RAND_status(). In the command line application,
16606 the EGD socket can be specified like a seed file using RANDFILE
16611 * Allow the string CERTIFICATE to be tolerated in PKCS#7 structures.
16612 Some CAs (e.g. Verisign) distribute certificates in this form.
16616 * Remove the SSL_ALLOW_ADH compile option and set the default cipher
16617 list to exclude them. This means that no special compilation option
16618 is needed to use anonymous DH: it just needs to be included in the
16623 * Change the EVP_MD_CTX_type macro so its meaning consistent with
16624 EVP_MD_type. The old functionality is available in a new macro called
16625 EVP_MD_md(). Change code that uses it and update docs.
16629 * `..._ctrl` functions now have corresponding `..._callback_ctrl` functions
16630 where the `void *` argument is replaced by a function pointer argument.
16631 Previously `void *` was abused to point to functions, which works on
16632 many platforms, but is not correct. As these functions are usually
16633 called by macros defined in OpenSSL header files, most source code
16634 should work without changes.
16638 * `<openssl/opensslconf.h>` (which is created by Configure) now contains
16639 sections with information on -D... compiler switches used for
16640 compiling the library so that applications can see them. To enable
16641 one of these sections, a pre-processor symbol `OPENSSL_..._DEFINES`
16642 must be defined. E.g.,
16643 #define OPENSSL_ALGORITHM_DEFINES
16644 #include <openssl/opensslconf.h>
16645 defines all pertinent `NO_<algo>` symbols, such as NO_IDEA, NO_RSA, etc.
16647 *Richard Levitte, Ulf and Bodo Möller*
16649 * Bugfix: Tolerate fragmentation and interleaving in the SSL 3/TLS
16654 * Change the 'other' type in certificate aux info to a STACK_OF
16655 X509_ALGOR. Although not an AlgorithmIdentifier as such it has
16656 the required ASN1 format: arbitrary types determined by an OID.
16660 * Add some PEM_write_X509_REQ_NEW() functions and a command line
16661 argument to 'req'. This is not because the function is newer or
16662 better than others it just uses the work 'NEW' in the certificate
16663 request header lines. Some software needs this.
16667 * Reorganise password command line arguments: now passwords can be
16668 obtained from various sources. Delete the PEM_cb function and make
16669 it the default behaviour: i.e. if the callback is NULL and the
16670 usrdata argument is not NULL interpret it as a null terminated pass
16671 phrase. If usrdata and the callback are NULL then the pass phrase
16672 is prompted for as usual.
16676 * Add support for the Compaq Atalla crypto accelerator. If it is installed,
16677 the support is automatically enabled. The resulting binaries will
16678 autodetect the card and use it if present.
16680 *Ben Laurie and Compaq Inc.*
16682 * Work around for Netscape hang bug. This sends certificate request
16683 and server done in one record. Since this is perfectly legal in the
16684 SSL/TLS protocol it isn't a "bug" option and is on by default. See
16685 the bugs/SSLv3 entry for more info.
16689 * HP-UX tune-up: new unified configs, HP C compiler bug workaround.
16693 * Add -rand argument to smime and pkcs12 applications and read/write
16698 * New 'passwd' tool for crypt(3) and apr1 password hashes.
16702 * Add command line password options to the remaining applications.
16706 * Bug fix for BN_div_recp() for numerators with an even number of
16711 * More tests in bntest.c, and changed test_bn output.
16715 * ./config recognizes MacOS X now.
16719 * Bug fix for BN_div() when the first words of num and divisor are
16720 equal (it gave wrong results if `(rem=(n1-q*d0)&BN_MASK2) < d0)`.
16724 * Add support for various broken PKCS#8 formats, and command line
16725 options to produce them.
16729 * New functions BN_CTX_start(), BN_CTX_get() and BT_CTX_end() to
16730 get temporary BIGNUMs from a BN_CTX.
16734 * Correct return values in BN_mod_exp_mont() and BN_mod_exp2_mont()
16739 * Change the `SSLeay_add_all_*()` functions to `OpenSSL_add_all_*()` and
16740 include a #define from the old name to the new. The original intent
16741 was that statically linked binaries could for example just call
16742 SSLeay_add_all_ciphers() to just add ciphers to the table and not
16743 link with digests. This never worked because SSLeay_add_all_digests()
16744 and SSLeay_add_all_ciphers() were in the same source file so calling
16745 one would link with the other. They are now in separate source files.
16749 * Add a new -notext option to 'ca' and a -pubkey option to 'spkac'.
16753 * Use a less unusual form of the Miller-Rabin primality test (it used
16754 a binary algorithm for exponentiation integrated into the Miller-Rabin
16755 loop, our standard modexp algorithms are faster).
16759 * Support for the EBCDIC character set completed.
16761 *Martin Kraemer <Martin.Kraemer@Mch.SNI.De>*
16763 * Source code cleanups: use const where appropriate, eliminate casts,
16764 use `void *` instead of `char *` in lhash.
16768 * Bugfix: ssl3_send_server_key_exchange was not restartable
16769 (the state was not changed to SSL3_ST_SW_KEY_EXCH_B, and because of
16770 this the server could overwrite ephemeral keys that the client
16775 * Turn DSA_is_prime into a macro that calls BN_is_prime,
16776 using 50 iterations of the Rabin-Miller test.
16778 DSA_generate_parameters now uses BN_is_prime_fasttest (with 50
16779 iterations of the Rabin-Miller test as required by the appendix
16780 to FIPS PUB 186[-1]) instead of DSA_is_prime.
16781 As BN_is_prime_fasttest includes trial division, DSA parameter
16782 generation becomes much faster.
16784 This implies a change for the callback functions in DSA_is_prime
16785 and DSA_generate_parameters: The callback function is called once
16786 for each positive witness in the Rabin-Miller test, not just
16787 occasionally in the inner loop; and the parameters to the
16788 callback function now provide an iteration count for the outer
16789 loop rather than for the current invocation of the inner loop.
16790 DSA_generate_parameters additionally can call the callback
16791 function with an 'iteration count' of -1, meaning that a
16792 candidate has passed the trial division test (when q is generated
16793 from an application-provided seed, trial division is skipped).
16797 * New function BN_is_prime_fasttest that optionally does trial
16798 division before starting the Rabin-Miller test and has
16799 an additional BN_CTX * argument (whereas BN_is_prime always
16800 has to allocate at least one BN_CTX).
16801 'callback(1, -1, cb_arg)' is called when a number has passed the
16802 trial division stage.
16806 * Fix for bug in CRL encoding. The validity dates weren't being handled
16811 * New -pkcs12 option to CA.pl script to write out a PKCS#12 file.
16815 * New function BN_pseudo_rand().
16819 * Clean up BN_mod_mul_montgomery(): replace the broken (and unreadable)
16820 bignum version of BN_from_montgomery() with the working code from
16821 SSLeay 0.9.0 (the word based version is faster anyway), and clean up
16826 * Avoid a race condition in s2_clnt.c (function get_server_hello) that
16827 made it impossible to use the same SSL_SESSION data structure in
16828 SSL2 clients in multiple threads.
16832 * The return value of RAND_load_file() no longer counts bytes obtained
16833 by stat(). RAND_load_file(..., -1) is new and uses the complete file
16834 to seed the PRNG (previously an explicit byte count was required).
16836 *Ulf Möller, Bodo Möller*
16838 * Clean up CRYPTO_EX_DATA functions, some of these didn't have prototypes
16839 used `char *` instead of `void *` and had casts all over the place.
16843 * Make BN_generate_prime() return NULL on error if ret!=NULL.
16847 * Retain source code compatibility for BN_prime_checks macro:
16848 BN_is_prime(..., BN_prime_checks, ...) now uses
16849 BN_prime_checks_for_size to determine the appropriate number of
16850 Rabin-Miller iterations.
16854 * Diffie-Hellman uses "safe" primes: DH_check() return code renamed to
16855 DH_CHECK_P_NOT_SAFE_PRIME.
16856 (Check if this is true? OpenPGP calls them "strong".)
16860 * Merge the functionality of "dh" and "gendh" programs into a new program
16861 "dhparam". The old programs are retained for now but will handle DH keys
16862 (instead of parameters) in future.
16866 * Make the ciphers, s_server and s_client programs check the return values
16867 when a new cipher list is set.
16871 * Enhance the SSL/TLS cipher mechanism to correctly handle the TLS 56bit
16872 ciphers. Before when the 56bit ciphers were enabled the sorting was
16875 The syntax for the cipher sorting has been extended to support sorting by
16876 cipher-strength (using the strength_bits hard coded in the tables).
16877 The new command is `@STRENGTH` (see also `doc/apps/ciphers.pod`).
16879 Fix a bug in the cipher-command parser: when supplying a cipher command
16880 string with an "undefined" symbol (neither command nor alphanumeric
16881 *A-Za-z0-9*, ssl_set_cipher_list used to hang in an endless loop. Now
16882 an error is flagged.
16884 Due to the strength-sorting extension, the code of the
16885 ssl_create_cipher_list() function was completely rearranged. I hope that
16886 the readability was also increased :-)
16888 *Lutz Jaenicke <Lutz.Jaenicke@aet.TU-Cottbus.DE>*
16890 * Minor change to 'x509' utility. The -CAcreateserial option now uses 1
16891 for the first serial number and places 2 in the serial number file. This
16892 avoids problems when the root CA is created with serial number zero and
16893 the first user certificate has the same issuer name and serial number
16898 * Fixes to X509_ATTRIBUTE utilities, change the 'req' program so it uses
16899 the new code. Add documentation for this stuff.
16903 * Changes to X509_ATTRIBUTE utilities. These have been renamed from
16904 `X509_*()` to `X509at_*()` on the grounds that they don't handle X509
16905 structures and behave in an analogous way to the X509v3 functions:
16906 they shouldn't be called directly but wrapper functions should be used
16909 So we also now have some wrapper functions that call the X509at functions
16910 when passed certificate requests. (TO DO: similar things can be done with
16911 PKCS#7 signed and unsigned attributes, PKCS#12 attributes and a few other
16912 things. Some of these need some d2i or i2d and print functionality
16913 because they handle more complex structures.)
16917 * Add missing #ifndefs that caused missing symbols when building libssl
16918 as a shared library without RSA. Use #ifndef NO_SSL2 instead of
16919 NO_RSA in `ssl/s2*.c`.
16921 *Kris Kennaway <kris@hub.freebsd.org>, modified by Ulf Möller*
16923 * Precautions against using the PRNG uninitialized: RAND_bytes() now
16924 has a return value which indicates the quality of the random data
16925 (1 = ok, 0 = not seeded). Also an error is recorded on the thread's
16926 error queue. New function RAND_pseudo_bytes() generates output that is
16927 guaranteed to be unique but not unpredictable. RAND_add is like
16928 RAND_seed, but takes an extra argument for an entropy estimate
16929 (RAND_seed always assumes full entropy).
16933 * Do more iterations of Rabin-Miller probable prime test (specifically,
16934 3 for 1024-bit primes, 6 for 512-bit primes, 12 for 256-bit primes
16935 instead of only 2 for all lengths; see BN_prime_checks_for_size definition
16936 in crypto/bn/bn_prime.c for the complete table). This guarantees a
16937 false-positive rate of at most 2^-80 for random input.
16941 * Rewrite ssl3_read_n (ssl/s3_pkt.c) avoiding a couple of bugs.
16945 * New function X509_CTX_rget_chain() (renamed to X509_CTX_get1_chain
16946 in the 0.9.5 release), this returns the chain
16947 from an X509_CTX structure with a dup of the stack and all
16948 the X509 reference counts upped: so the stack will exist
16949 after X509_CTX_cleanup() has been called. Modify pkcs12.c
16952 Also make SSL_SESSION_print() print out the verify return
16957 * Add manpage for the pkcs12 command. Also change the default
16958 behaviour so MAC iteration counts are used unless the new
16959 -nomaciter option is used. This improves file security and
16960 only older versions of MSIE (4.0 for example) need it.
16964 * Honor the no-xxx Configure options when creating .DEF files.
16968 * Add PKCS#10 attributes to field table: challengePassword,
16969 unstructuredName and unstructuredAddress. These are taken from
16970 draft PKCS#9 v2.0 but are compatible with v1.2 provided no
16971 international characters are used.
16973 More changes to X509_ATTRIBUTE code: allow the setting of types
16974 based on strings. Remove the 'loc' parameter when adding
16975 attributes because these will be a SET OF encoding which is sorted
16980 * Initial changes to the 'req' utility to allow request generation
16981 automation. This will allow an application to just generate a template
16982 file containing all the field values and have req construct the
16985 Initial support for X509_ATTRIBUTE handling. Stacks of these are
16986 used all over the place including certificate requests and PKCS#7
16987 structures. They are currently handled manually where necessary with
16988 some primitive wrappers for PKCS#7. The new functions behave in a
16989 manner analogous to the X509 extension functions: they allow
16990 attributes to be looked up by NID and added.
16992 Later something similar to the X509V3 code would be desirable to
16993 automatically handle the encoding, decoding and printing of the
16994 more complex types. The string types like challengePassword can
16995 be handled by the string table functions.
16997 Also modified the multi byte string table handling. Now there is
16998 a 'global mask' which masks out certain types. The table itself
16999 can use the flag STABLE_NO_MASK to ignore the mask setting: this
17000 is useful when for example there is only one permissible type
17001 (as in countryName) and using the mask might result in no valid
17006 * Clean up 'Finished' handling, and add functions SSL_get_finished and
17007 SSL_get_peer_finished to allow applications to obtain the latest
17008 Finished messages sent to the peer or expected from the peer,
17009 respectively. (SSL_get_peer_finished is usually the Finished message
17010 actually received from the peer, otherwise the protocol will be aborted.)
17012 As the Finished message are message digests of the complete handshake
17013 (with a total of 192 bits for TLS 1.0 and more for SSL 3.0), they can
17014 be used for external authentication procedures when the authentication
17015 provided by SSL/TLS is not desired or is not enough.
17019 * Enhanced support for Alpha Linux is added. Now ./config checks if
17020 the host supports BWX extension and if Compaq C is present on the
17021 $PATH. Just exploiting of the BWX extension results in 20-30%
17022 performance kick for some algorithms, e.g. DES and RC4 to mention
17023 a couple. Compaq C in turn generates ~20% faster code for MD5 and
17028 * Add support for MS "fast SGC". This is arguably a violation of the
17029 SSL3/TLS protocol. Netscape SGC does two handshakes: the first with
17030 weak crypto and after checking the certificate is SGC a second one
17031 with strong crypto. MS SGC stops the first handshake after receiving
17032 the server certificate message and sends a second client hello. Since
17033 a server will typically do all the time consuming operations before
17034 expecting any further messages from the client (server key exchange
17035 is the most expensive) there is little difference between the two.
17037 To get OpenSSL to support MS SGC we have to permit a second client
17038 hello message after we have sent server done. In addition we have to
17039 reset the MAC if we do get this second client hello.
17043 * Add a function 'd2i_AutoPrivateKey()' this will automatically decide
17044 if a DER encoded private key is RSA or DSA traditional format. Changed
17045 d2i_PrivateKey_bio() to use it. This is only needed for the "traditional"
17046 format DER encoded private key. Newer code should use PKCS#8 format which
17047 has the key type encoded in the ASN1 structure. Added DER private key
17048 support to pkcs8 application.
17052 * SSL 3/TLS 1 servers now don't request certificates when an anonymous
17053 ciphersuites has been selected (as required by the SSL 3/TLS 1
17054 specifications). Exception: When SSL_VERIFY_FAIL_IF_NO_PEER_CERT
17055 is set, we interpret this as a request to violate the specification
17056 (the worst that can happen is a handshake failure, and 'correct'
17057 behaviour would result in a handshake failure anyway).
17061 * In SSL_CTX_add_session, take into account that there might be multiple
17062 SSL_SESSION structures with the same session ID (e.g. when two threads
17063 concurrently obtain them from an external cache).
17064 The internal cache can handle only one SSL_SESSION with a given ID,
17065 so if there's a conflict, we now throw out the old one to achieve
17070 * Add OIDs for idea and blowfish in CBC mode. This will allow both
17071 to be used in PKCS#5 v2.0 and S/MIME. Also add checking to
17072 some routines that use cipher OIDs: some ciphers do not have OIDs
17073 defined and so they cannot be used for S/MIME and PKCS#5 v2.0 for
17078 * Simplify the trust setting structure and code. Now we just have
17079 two sequences of OIDs for trusted and rejected settings. These will
17080 typically have values the same as the extended key usage extension
17081 and any application specific purposes.
17083 The trust checking code now has a default behaviour: it will just
17084 check for an object with the same NID as the passed id. Functions can
17085 be provided to override either the default behaviour or the behaviour
17086 for a given id. SSL client, server and email already have functions
17087 in place for compatibility: they check the NID and also return "trusted"
17088 if the certificate is self signed.
17092 * Add d2i,i2d bio/fp functions for PrivateKey: these convert the
17093 traditional format into an EVP_PKEY structure.
17097 * Add a password callback function PEM_cb() which either prompts for
17098 a password if usr_data is NULL or otherwise assumes it is a null
17099 terminated password. Allow passwords to be passed on command line
17100 environment or config files in a few more utilities.
17104 * Add a bunch of DER and PEM functions to handle PKCS#8 format private
17105 keys. Add some short names for PKCS#8 PBE algorithms and allow them
17106 to be specified on the command line for the pkcs8 and pkcs12 utilities.
17107 Update documentation.
17111 * Support for ASN1 "NULL" type. This could be handled before by using
17112 ASN1_TYPE but there wasn't any function that would try to read a NULL
17113 and produce an error if it couldn't. For compatibility we also have
17114 ASN1_NULL_new() and ASN1_NULL_free() functions but these are faked and
17115 don't allocate anything because they don't need to.
17119 * Initial support for MacOS is now provided. Examine INSTALL.MacOS
17122 *Andy Polyakov, Roy Woods <roy@centicsystems.ca>*
17124 * Rebuild of the memory allocation routines used by OpenSSL code and
17125 possibly others as well. The purpose is to make an interface that
17126 provide hooks so anyone can build a separate set of allocation and
17127 deallocation routines to be used by OpenSSL, for example memory
17128 pool implementations, or something else, which was previously hard
17129 since Malloc(), Realloc() and Free() were defined as macros having
17130 the values malloc, realloc and free, respectively (except for Win32
17131 compilations). The same is provided for memory debugging code.
17132 OpenSSL already comes with functionality to find memory leaks, but
17133 this gives people a chance to debug other memory problems.
17135 With these changes, a new set of functions and macros have appeared:
17137 CRYPTO_set_mem_debug_functions() [F]
17138 CRYPTO_get_mem_debug_functions() [F]
17139 CRYPTO_dbg_set_options() [F]
17140 CRYPTO_dbg_get_options() [F]
17141 CRYPTO_malloc_debug_init() [M]
17143 The memory debug functions are NULL by default, unless the library
17144 is compiled with CRYPTO_MDEBUG or friends is defined. If someone
17145 wants to debug memory anyway, CRYPTO_malloc_debug_init() (which
17146 gives the standard debugging functions that come with OpenSSL) or
17147 CRYPTO_set_mem_debug_functions() (tells OpenSSL to use functions
17148 provided by the library user) must be used. When the standard
17149 debugging functions are used, CRYPTO_dbg_set_options can be used to
17150 request additional information:
17151 CRYPTO_dbg_set_options(V_CYRPTO_MDEBUG_xxx) corresponds to setting
17152 the CRYPTO_MDEBUG_xxx macro when compiling the library.
17154 Also, things like CRYPTO_set_mem_functions will always give the
17155 expected result (the new set of functions is used for allocation
17156 and deallocation) at all times, regardless of platform and compiler
17159 To finish it up, some functions that were never use in any other
17160 way than through macros have a new API and new semantic:
17162 CRYPTO_dbg_malloc()
17163 CRYPTO_dbg_realloc()
17166 All macros of value have retained their old syntax.
17168 *Richard Levitte and Bodo Moeller*
17170 * Some S/MIME fixes. The OID for SMIMECapabilities was wrong, the
17171 ordering of SMIMECapabilities wasn't in "strength order" and there
17172 was a missing NULL in the AlgorithmIdentifier for the SHA1 signature
17177 * Some ASN1 types with illegal zero length encoding (INTEGER,
17178 ENUMERATED and OBJECT IDENTIFIER) choked the ASN1 routines.
17180 *Frans Heymans <fheymans@isaserver.be>, modified by Steve Henson*
17182 * Merge in my S/MIME library for OpenSSL. This provides a simple
17183 S/MIME API on top of the PKCS#7 code, a MIME parser (with enough
17184 functionality to handle multipart/signed properly) and a utility
17185 called 'smime' to call all this stuff. This is based on code I
17186 originally wrote for Celo who have kindly allowed it to be
17187 included in OpenSSL.
17191 * Add variants des_set_key_checked and des_set_key_unchecked of
17192 des_set_key (aka des_key_sched). Global variable des_check_key
17193 decides which of these is called by des_set_key; this way
17194 des_check_key behaves as it always did, but applications and
17195 the library itself, which was buggy for des_check_key == 1,
17196 have a cleaner way to pick the version they need.
17200 * New function PKCS12_newpass() which changes the password of a
17205 * Modify X509_TRUST and X509_PURPOSE so it also uses a static and
17206 dynamic mix. In both cases the ids can be used as an index into the
17207 table. Also modified the X509_TRUST_add() and X509_PURPOSE_add()
17208 functions so they accept a list of the field values and the
17209 application doesn't need to directly manipulate the X509_TRUST
17214 * Modify the ASN1_STRING_TABLE stuff so it also uses bsearch and doesn't
17219 * Modify the way the V3 extension code looks up extensions. This now
17220 works in a similar way to the object code: we have some "standard"
17221 extensions in a static table which is searched with OBJ_bsearch()
17222 and the application can add dynamic ones if needed. The file
17223 crypto/x509v3/ext_dat.h now has the info: this file needs to be
17224 updated whenever a new extension is added to the core code and kept
17225 in ext_nid order. There is a simple program 'tabtest.c' which checks
17226 this. New extensions are not added too often so this file can readily
17227 be maintained manually.
17229 There are two big advantages in doing things this way. The extensions
17230 can be looked up immediately and no longer need to be "added" using
17231 X509V3_add_standard_extensions(): this function now does nothing.
17232 Side note: I get *lots* of email saying the extension code doesn't
17233 work because people forget to call this function.
17234 Also no dynamic allocation is done unless new extensions are added:
17235 so if we don't add custom extensions there is no need to call
17236 X509V3_EXT_cleanup().
17240 * Modify enc utility's salting as follows: make salting the default. Add a
17241 magic header, so unsalted files fail gracefully instead of just decrypting
17242 to garbage. This is because not salting is a big security hole, so people
17243 should be discouraged from doing it.
17247 * Fixes and enhancements to the 'x509' utility. It allowed a message
17248 digest to be passed on the command line but it only used this
17249 parameter when signing a certificate. Modified so all relevant
17250 operations are affected by the digest parameter including the
17251 -fingerprint and -x509toreq options. Also -x509toreq choked if a
17252 DSA key was used because it didn't fix the digest.
17256 * Initial certificate chain verify code. Currently tests the untrusted
17257 certificates for consistency with the verify purpose (which is set
17258 when the X509_STORE_CTX structure is set up) and checks the pathlength.
17260 There is a NO_CHAIN_VERIFY compilation option to keep the old behaviour:
17261 this is because it will reject chains with invalid extensions whereas
17262 every previous version of OpenSSL and SSLeay made no checks at all.
17264 Trust code: checks the root CA for the relevant trust settings. Trust
17265 settings have an initial value consistent with the verify purpose: e.g.
17266 if the verify purpose is for SSL client use it expects the CA to be
17267 trusted for SSL client use. However the default value can be changed to
17268 permit custom trust settings: one example of this would be to only trust
17269 certificates from a specific "secure" set of CAs.
17271 Also added X509_STORE_CTX_new() and X509_STORE_CTX_free() functions
17272 which should be used for version portability: especially since the
17273 verify structure is likely to change more often now.
17275 SSL integration. Add purpose and trust to SSL_CTX and SSL and functions
17276 to set them. If not set then assume SSL clients will verify SSL servers
17279 Two new options to the verify program: -untrusted allows a set of
17280 untrusted certificates to be passed in and -purpose which sets the
17281 intended purpose of the certificate. If a purpose is set then the
17282 new chain verify code is used to check extension consistency.
17286 * Support for the authority information access extension.
17290 * Modify RSA and DSA PEM read routines to transparently handle
17291 PKCS#8 format private keys. New *_PUBKEY_* functions that handle
17292 public keys in a format compatible with certificate
17293 SubjectPublicKeyInfo structures. Unfortunately there were already
17294 functions called *_PublicKey_* which used various odd formats so
17295 these are retained for compatibility: however the DSA variants were
17296 never in a public release so they have been deleted. Changed dsa/rsa
17297 utilities to handle the new format: note no releases ever handled public
17298 keys so we should be OK.
17300 The primary motivation for this change is to avoid the same fiasco
17301 that dogs private keys: there are several incompatible private key
17302 formats some of which are standard and some OpenSSL specific and
17303 require various evil hacks to allow partial transparent handling and
17304 even then it doesn't work with DER formats. Given the option anything
17305 other than PKCS#8 should be dumped: but the other formats have to
17306 stay in the name of compatibility.
17308 With public keys and the benefit of hindsight one standard format
17309 is used which works with EVP_PKEY, RSA or DSA structures: though
17310 it clearly returns an error if you try to read the wrong kind of key.
17312 Added a -pubkey option to the 'x509' utility to output the public key.
17313 Also rename the `EVP_PKEY_get_*()` to `EVP_PKEY_rget_*()`
17314 (renamed to `EVP_PKEY_get1_*()` in the OpenSSL 0.9.5 release) and add
17315 `EVP_PKEY_rset_*()` functions (renamed to `EVP_PKEY_set1_*()`)
17316 that do the same as the `EVP_PKEY_assign_*()` except they up the
17317 reference count of the added key (they don't "swallow" the
17322 * Fixes to crypto/x509/by_file.c the code to read in certificates and
17323 CRLs would fail if the file contained no certificates or no CRLs:
17324 added a new function to read in both types and return the number
17325 read: this means that if none are read it will be an error. The
17326 DER versions of the certificate and CRL reader would always fail
17327 because it isn't possible to mix certificates and CRLs in DER format
17328 without choking one or the other routine. Changed this to just read
17329 a certificate: this is the best we can do. Also modified the code
17330 in `apps/verify.c` to take notice of return codes: it was previously
17331 attempting to read in certificates from NULL pointers and ignoring
17332 any errors: this is one reason why the cert and CRL reader seemed
17333 to work. It doesn't check return codes from the default certificate
17334 routines: these may well fail if the certificates aren't installed.
17338 * Code to support otherName option in GeneralName.
17342 * First update to verify code. Change the verify utility
17343 so it warns if it is passed a self signed certificate:
17344 for consistency with the normal behaviour. X509_verify
17345 has been modified to it will now verify a self signed
17346 certificate if *exactly* the same certificate appears
17347 in the store: it was previously impossible to trust a
17348 single self signed certificate. This means that:
17349 openssl verify ss.pem
17350 now gives a warning about a self signed certificate but
17351 openssl verify -CAfile ss.pem ss.pem
17356 * For servers, store verify_result in SSL_SESSION data structure
17357 (and add it to external session representation).
17358 This is needed when client certificate verifications fails,
17359 but an application-provided verification callback (set by
17360 SSL_CTX_set_cert_verify_callback) allows accepting the session
17361 anyway (i.e. leaves x509_store_ctx->error != X509_V_OK
17362 but returns 1): When the session is reused, we have to set
17363 ssl->verify_result to the appropriate error code to avoid
17366 *Bodo Moeller, problem pointed out by Lutz Jaenicke*
17368 * Fix a bug in the new PKCS#7 code: it didn't consider the
17369 case in PKCS7_dataInit() where the signed PKCS7 structure
17370 didn't contain any existing data because it was being created.
17372 *Po-Cheng Chen <pocheng@nst.com.tw>, slightly modified by Steve Henson*
17374 * Add a salt to the key derivation routines in enc.c. This
17375 forms the first 8 bytes of the encrypted file. Also add a
17376 -S option to allow a salt to be input on the command line.
17380 * New function X509_cmp(). Oddly enough there wasn't a function
17381 to compare two certificates. We do this by working out the SHA1
17382 hash and comparing that. X509_cmp() will be needed by the trust
17387 * SSL_get1_session() is like SSL_get_session(), but increments
17388 the reference count in the SSL_SESSION returned.
17390 *Geoff Thorpe <geoff@eu.c2.net>*
17392 * Fix for 'req': it was adding a null to request attributes.
17393 Also change the X509_LOOKUP and X509_INFO code to handle
17394 certificate auxiliary information.
17398 * Add support for 40 and 64 bit RC2 and RC4 algorithms: document
17403 * Add the possibility to add extra information to the memory leak
17404 detecting output, to form tracebacks, showing from where each
17405 allocation was originated: CRYPTO_push_info("constant string") adds
17406 the string plus current file name and line number to a per-thread
17407 stack, CRYPTO_pop_info() does the obvious, CRYPTO_remove_all_info()
17408 is like calling CYRPTO_pop_info() until the stack is empty.
17409 Also updated memory leak detection code to be multi-thread-safe.
17413 * Add options -text and -noout to pkcs7 utility and delete the
17414 encryption options which never did anything. Update docs.
17418 * Add options to some of the utilities to allow the pass phrase
17419 to be included on either the command line (not recommended on
17420 OSes like Unix) or read from the environment. Update the
17421 manpages and fix a few bugs.
17425 * Add a few manpages for some of the openssl commands.
17429 * Fix the -revoke option in ca. It was freeing up memory twice,
17430 leaking and not finding already revoked certificates.
17434 * Extensive changes to support certificate auxiliary information.
17435 This involves the use of X509_CERT_AUX structure and X509_AUX
17436 functions. An X509_AUX function such as PEM_read_X509_AUX()
17437 can still read in a certificate file in the usual way but it
17438 will also read in any additional "auxiliary information". By
17439 doing things this way a fair degree of compatibility can be
17440 retained: existing certificates can have this information added
17441 using the new 'x509' options.
17443 Current auxiliary information includes an "alias" and some trust
17444 settings. The trust settings will ultimately be used in enhanced
17445 certificate chain verification routines: currently a certificate
17446 can only be trusted if it is self signed and then it is trusted
17451 * Fix assembler for Alpha (tested only on DEC OSF not Linux or `*BSD`).
17452 The problem was that one of the replacement routines had not been working
17453 since SSLeay releases. For now the offending routine has been replaced
17454 with non-optimised assembler. Even so, this now gives around 95%
17455 performance improvement for 1024 bit RSA signs.
17459 * Hack to fix PKCS#7 decryption when used with some unorthodox RC2
17460 handling. Most clients have the effective key size in bits equal to
17461 the key length in bits: so a 40 bit RC2 key uses a 40 bit (5 byte) key.
17462 A few however don't do this and instead use the size of the decrypted key
17463 to determine the RC2 key length and the AlgorithmIdentifier to determine
17464 the effective key length. In this case the effective key length can still
17465 be 40 bits but the key length can be 168 bits for example. This is fixed
17466 by manually forcing an RC2 key into the EVP_PKEY structure because the
17467 EVP code can't currently handle unusual RC2 key sizes: it always assumes
17468 the key length and effective key length are equal.
17472 * Add a bunch of functions that should simplify the creation of
17473 X509_NAME structures. Now you should be able to do:
17474 X509_NAME_add_entry_by_txt(nm, "CN", MBSTRING_ASC, "Steve", -1, -1, 0);
17475 and have it automatically work out the correct field type and fill in
17476 the structures. The more adventurous can try:
17477 X509_NAME_add_entry_by_txt(nm, field, MBSTRING_UTF8, str, -1, -1, 0);
17478 and it will (hopefully) work out the correct multibyte encoding.
17482 * Change the 'req' utility to use the new field handling and multibyte
17483 copy routines. Before the DN field creation was handled in an ad hoc
17484 way in req, ca, and x509 which was rather broken and didn't support
17485 BMPStrings or UTF8Strings. Since some software doesn't implement
17486 BMPStrings or UTF8Strings yet, they can be enabled using the config file
17487 using the dirstring_type option. See the new comment in the default
17488 openssl.cnf for more info.
17492 * Make crypto/rand/md_rand.c more robust:
17493 - Assure unique random numbers after fork().
17494 - Make sure that concurrent threads access the global counter and
17495 md serializably so that we never lose entropy in them
17496 or use exactly the same state in multiple threads.
17497 Access to the large state is not always serializable because
17498 the additional locking could be a performance killer, and
17499 md should be large enough anyway.
17503 * New file `apps/app_rand.c` with commonly needed functionality
17504 for handling the random seed file.
17506 Use the random seed file in some applications that previously did not:
17508 dsaparam -genkey (which also ignored its '-rand' option),
17511 x509 (when signing).
17512 Except on systems with /dev/urandom, it is crucial to have a random
17513 seed file at least for key creation, DSA signing, and for DH exchanges;
17514 for RSA signatures we could do without one.
17516 gendh and gendsa (unlike genrsa) used to read only the first byte
17517 of each file listed in the '-rand' option. The function as previously
17518 found in genrsa is now in app_rand.c and is used by all programs
17519 that support '-rand'.
17523 * In RAND_write_file, use mode 0600 for creating files;
17524 don't just chmod when it may be too late.
17528 * Report an error from X509_STORE_load_locations
17529 when X509_LOOKUP_load_file or X509_LOOKUP_add_dir failed.
17533 * New function ASN1_mbstring_copy() this copies a string in either
17534 ASCII, Unicode, Universal (4 bytes per character) or UTF8 format
17535 into an ASN1_STRING type. A mask of permissible types is passed
17536 and it chooses the "minimal" type to use or an error if not type
17541 * Add function equivalents to the various macros in asn1.h. The old
17542 macros are retained with an `M_` prefix. Code inside the library can
17543 use the `M_` macros. External code (including the openssl utility)
17544 should *NOT* in order to be "shared library friendly".
17548 * Add various functions that can check a certificate's extensions
17549 to see if it usable for various purposes such as SSL client,
17550 server or S/MIME and CAs of these types. This is currently
17551 VERY EXPERIMENTAL but will ultimately be used for certificate chain
17552 verification. Also added a -purpose flag to x509 utility to
17553 print out all the purposes.
17557 * Add a CRYPTO_EX_DATA to X509 certificate structure and associated
17562 * New `X509V3_{X509,CRL,REVOKED}_get_d2i()` functions. These will search
17563 for, obtain and decode and extension and obtain its critical flag.
17564 This allows all the necessary extension code to be handled in a
17565 single function call.
17569 * RC4 tune-up featuring 30-40% performance improvement on most RISC
17570 platforms. See crypto/rc4/rc4_enc.c for further details.
17574 * New -noout option to asn1parse. This causes no output to be produced
17575 its main use is when combined with -strparse and -out to extract data
17576 from a file (which may not be in ASN.1 format).
17580 * Fix for pkcs12 program. It was hashing an invalid certificate pointer
17581 when producing the local key id.
17583 *Richard Levitte <levitte@stacken.kth.se>*
17585 * New option -dhparam in s_server. This allows a DH parameter file to be
17586 stated explicitly. If it is not stated then it tries the first server
17587 certificate file. The previous behaviour hard coded the filename
17592 * Add -pubin and -pubout options to the rsa and dsa commands. These allow
17593 a public key to be input or output. For example:
17594 openssl rsa -in key.pem -pubout -out pubkey.pem
17595 Also added necessary DSA public key functions to handle this.
17599 * Fix so PKCS7_dataVerify() doesn't crash if no certificates are contained
17600 in the message. This was handled by allowing
17601 X509_find_by_issuer_and_serial() to tolerate a NULL passed to it.
17603 *Steve Henson, reported by Sampo Kellomaki <sampo@mail.neuronio.pt>*
17605 * Fix for bug in d2i_ASN1_bytes(): other ASN1 functions add an extra null
17606 to the end of the strings whereas this didn't. This would cause problems
17607 if strings read with d2i_ASN1_bytes() were later modified.
17609 *Steve Henson, reported by Arne Ansper <arne@ats.cyber.ee>*
17611 * Fix for base64 decode bug. When a base64 bio reads only one line of
17612 data and it contains EOF it will end up returning an error. This is
17613 caused by input 46 bytes long. The cause is due to the way base64
17614 BIOs find the start of base64 encoded data. They do this by trying a
17615 trial decode on each line until they find one that works. When they
17616 do a flag is set and it starts again knowing it can pass all the
17617 data directly through the decoder. Unfortunately it doesn't reset
17618 the context it uses. This means that if EOF is reached an attempt
17619 is made to pass two EOFs through the context and this causes the
17620 resulting error. This can also cause other problems as well. As is
17621 usual with these problems it takes *ages* to find and the fix is
17622 trivial: move one line.
17624 *Steve Henson, reported by ian@uns.ns.ac.yu (Ivan Nejgebauer)*
17626 * Ugly workaround to get s_client and s_server working under Windows. The
17627 old code wouldn't work because it needed to select() on sockets and the
17628 tty (for keypresses and to see if data could be written). Win32 only
17629 supports select() on sockets so we select() with a 1s timeout on the
17630 sockets and then see if any characters are waiting to be read, if none
17631 are present then we retry, we also assume we can always write data to
17632 the tty. This isn't nice because the code then blocks until we've
17633 received a complete line of data and it is effectively polling the
17634 keyboard at 1s intervals: however it's quite a bit better than not
17635 working at all :-) A dedicated Windows application might handle this
17636 with an event loop for example.
17640 * Enhance RSA_METHOD structure. Now there are two extra methods, rsa_sign
17641 and rsa_verify. When the RSA_FLAGS_SIGN_VER option is set these functions
17642 will be called when RSA_sign() and RSA_verify() are used. This is useful
17643 if rsa_pub_dec() and rsa_priv_enc() equivalents are not available.
17644 For this to work properly RSA_public_decrypt() and RSA_private_encrypt()
17645 should *not* be used: RSA_sign() and RSA_verify() must be used instead.
17646 This necessitated the support of an extra signature type NID_md5_sha1
17647 for SSL signatures and modifications to the SSL library to use it instead
17648 of calling RSA_public_decrypt() and RSA_private_encrypt().
17652 * Add new -verify -CAfile and -CApath options to the crl program, these
17653 will lookup a CRL issuers certificate and verify the signature in a
17654 similar way to the verify program. Tidy up the crl program so it
17655 no longer accesses structures directly. Make the ASN1 CRL parsing a bit
17656 less strict. It will now permit CRL extensions even if it is not
17657 a V2 CRL: this will allow it to tolerate some broken CRLs.
17661 * Initialize all non-automatic variables each time one of the openssl
17662 sub-programs is started (this is necessary as they may be started
17663 multiple times from the "OpenSSL>" prompt).
17665 *Lennart Bang, Bodo Moeller*
17667 * Preliminary compilation option RSA_NULL which disables RSA crypto without
17668 removing all other RSA functionality (this is what NO_RSA does). This
17669 is so (for example) those in the US can disable those operations covered
17670 by the RSA patent while allowing storage and parsing of RSA keys and RSA
17675 * Non-copying interface to BIO pairs.
17676 (still largely untested)
17680 * New function ASN1_tag2str() to convert an ASN1 tag to a descriptive
17681 ASCII string. This was handled independently in various places before.
17685 * New functions UTF8_getc() and UTF8_putc() that parse and generate
17686 UTF8 strings a character at a time.
17690 * Use client_version from client hello to select the protocol
17691 (s23_srvr.c) and for RSA client key exchange verification
17692 (s3_srvr.c), as required by the SSL 3.0/TLS 1.0 specifications.
17696 * Add various utility functions to handle SPKACs, these were previously
17697 handled by poking round in the structure internals. Added new function
17698 NETSCAPE_SPKI_print() to print out SPKAC and a new utility 'spkac' to
17699 print, verify and generate SPKACs. Based on an original idea from
17700 Massimiliano Pala <madwolf@comune.modena.it> but extensively modified.
17704 * RIPEMD160 is operational on all platforms and is back in 'make test'.
17708 * Allow the config file extension section to be overwritten on the
17709 command line. Based on an original idea from Massimiliano Pala
17710 <madwolf@comune.modena.it>. The new option is called -extensions
17711 and can be applied to ca, req and x509. Also -reqexts to override
17712 the request extensions in req and -crlexts to override the crl extensions
17717 * Add new feature to the SPKAC handling in ca. Now you can include
17718 the same field multiple times by preceding it by "XXXX." for example:
17721 this is the same syntax as used in the req config file.
17725 * Allow certificate extensions to be added to certificate requests. These
17726 are specified in a 'req_extensions' option of the req section of the
17727 config file. They can be printed out with the -text option to req but
17728 are otherwise ignored at present.
17732 * Fix a horrible bug in enc_read() in crypto/evp/bio_enc.c: if the first
17733 data read consists of only the final block it would not decrypted because
17734 EVP_CipherUpdate() would correctly report zero bytes had been decrypted.
17735 A misplaced 'break' also meant the decrypted final block might not be
17736 copied until the next read.
17740 * Initial support for DH_METHOD. Again based on RSA_METHOD. Also added
17741 a few extra parameters to the DH structure: these will be useful if
17742 for example we want the value of 'q' or implement X9.42 DH.
17746 * Initial support for DSA_METHOD. This is based on the RSA_METHOD and
17747 provides hooks that allow the default DSA functions or functions on a
17748 "per key" basis to be replaced. This allows hardware acceleration and
17749 hardware key storage to be handled without major modification to the
17750 library. Also added low-level modexp hooks and CRYPTO_EX structure and
17751 associated functions.
17755 * Add a new flag to memory BIOs, BIO_FLAG_MEM_RDONLY. This marks the BIO
17756 as "read only": it can't be written to and the buffer it points to will
17757 not be freed. Reading from a read only BIO is much more efficient than
17758 a normal memory BIO. This was added because there are several times when
17759 an area of memory needs to be read from a BIO. The previous method was
17760 to create a memory BIO and write the data to it, this results in two
17761 copies of the data and an O(n^2) reading algorithm. There is a new
17762 function BIO_new_mem_buf() which creates a read only memory BIO from
17763 an area of memory. Also modified the PKCS#7 routines to use read only
17768 * Bugfix: ssl23_get_client_hello did not work properly when called in
17769 state SSL23_ST_SR_CLNT_HELLO_B, i.e. when the first 7 bytes of
17770 a SSLv2-compatible client hello for SSLv3 or TLSv1 could be read,
17771 but a retry condition occurred while trying to read the rest.
17775 * The PKCS7_ENC_CONTENT_new() function was setting the content type as
17776 NID_pkcs7_encrypted by default: this was wrong since this should almost
17777 always be NID_pkcs7_data. Also modified the PKCS7_set_type() to handle
17778 the encrypted data type: this is a more sensible place to put it and it
17779 allows the PKCS#12 code to be tidied up that duplicated this
17784 * Changed obj_dat.pl script so it takes its input and output files on
17785 the command line. This should avoid shell escape redirection problems
17790 * Initial support for certificate extension requests, these are included
17791 in things like Xenroll certificate requests. Included functions to allow
17792 extensions to be obtained and added.
17796 * -crlf option to s_client and s_server for sending newlines as
17797 CRLF (as required by many protocols).
17801 ### Changes between 0.9.3a and 0.9.4 [09 Aug 1999]
17803 * Install libRSAglue.a when OpenSSL is built with RSAref.
17805 *Ralf S. Engelschall*
17807 * A few more `#ifndef NO_FP_API / #endif` pairs for consistency.
17809 *Andrija Antonijevic <TheAntony2@bigfoot.com>*
17811 * Fix -startdate and -enddate (which was missing) arguments to 'ca'
17816 * New function DSA_dup_DH, which duplicates DSA parameters/keys as
17817 DH parameters/keys (q is lost during that conversion, but the resulting
17818 DH parameters contain its length).
17820 For 1024-bit p, DSA_generate_parameters followed by DSA_dup_DH is
17821 much faster than DH_generate_parameters (which creates parameters
17822 where `p = 2*q + 1`), and also the smaller q makes DH computations
17823 much more efficient (160-bit exponentiation instead of 1024-bit
17824 exponentiation); so this provides a convenient way to support DHE
17825 ciphersuites in SSL/TLS servers (see ssl/ssltest.c). It is of
17826 utter importance to use
17827 SSL_CTX_set_options(s_ctx, SSL_OP_SINGLE_DH_USE);
17829 SSL_set_options(s_ctx, SSL_OP_SINGLE_DH_USE);
17830 when such DH parameters are used, because otherwise small subgroup
17831 attacks may become possible!
17835 * Avoid memory leak in i2d_DHparams.
17839 * Allow the -k option to be used more than once in the enc program:
17840 this allows the same encrypted message to be read by multiple recipients.
17844 * New function OBJ_obj2txt(buf, buf_len, a, no_name), this converts
17845 an ASN1_OBJECT to a text string. If the "no_name" parameter is set then
17846 it will always use the numerical form of the OID, even if it has a short
17851 * Added an extra RSA flag: RSA_FLAG_EXT_PKEY. Previously the rsa_mod_exp
17852 method only got called if p,q,dmp1,dmq1,iqmp components were present,
17853 otherwise bn_mod_exp was called. In the case of hardware keys for example
17854 no private key components need be present and it might store extra data
17855 in the RSA structure, which cannot be accessed from bn_mod_exp.
17856 By setting RSA_FLAG_EXT_PKEY rsa_mod_exp will always be called for
17857 private key operations.
17861 * Added support for SPARC Linux.
17865 * pem_password_cb function type incompatibly changed from
17866 typedef int pem_password_cb(char *buf, int size, int rwflag);
17868 ....(char *buf, int size, int rwflag, void *userdata);
17869 so that applications can pass data to their callbacks:
17870 The `PEM[_ASN1]_{read,write}...` functions and macros now take an
17871 additional void * argument, which is just handed through whenever
17872 the password callback is called.
17874 *Damien Miller <dmiller@ilogic.com.au>; tiny changes by Bodo Moeller*
17876 New function SSL_CTX_set_default_passwd_cb_userdata.
17878 Compatibility note: As many C implementations push function arguments
17879 onto the stack in reverse order, the new library version is likely to
17880 interoperate with programs that have been compiled with the old
17881 pem_password_cb definition (PEM_whatever takes some data that
17882 happens to be on the stack as its last argument, and the callback
17883 just ignores this garbage); but there is no guarantee whatsoever that
17886 * The -DPLATFORM="\"$(PLATFORM)\"" definition and the similar -DCFLAGS=...
17887 (both in crypto/Makefile.ssl for use by crypto/cversion.c) caused
17888 problems not only on Windows, but also on some Unix platforms.
17889 To avoid problematic command lines, these definitions are now in an
17890 auto-generated file crypto/buildinf.h (created by crypto/Makefile.ssl
17891 for standard "make" builds, by util/mk1mf.pl for "mk1mf" builds).
17895 * MIPS III/IV assembler module is reimplemented.
17899 * More DES library cleanups: remove references to srand/rand and
17900 delete an unused file.
17904 * Add support for the free Netwide assembler (NASM) under Win32,
17905 since not many people have MASM (ml) and it can be hard to obtain.
17906 This is currently experimental but it seems to work OK and pass all
17907 the tests. Check out INSTALL.W32 for info.
17911 * Fix memory leaks in s3_clnt.c: All non-anonymous SSL3/TLS1 connections
17912 without temporary keys kept an extra copy of the server key,
17913 and connections with temporary keys did not free everything in case
17918 * New function RSA_check_key and new openssl rsa option -check
17919 for verifying the consistency of RSA keys.
17921 *Ulf Moeller, Bodo Moeller*
17923 * Various changes to make Win32 compile work:
17924 1. Casts to avoid "loss of data" warnings in p5_crpt2.c
17925 2. Change unsigned int to int in b_dump.c to avoid "signed/unsigned
17926 comparison" warnings.
17927 3. Add `sk_<TYPE>_sort` to DEF file generator and do make update.
17931 * Add a debugging option to PKCS#5 v2 key generation function: when
17932 you #define DEBUG_PKCS5V2 passwords, salts, iteration counts and
17933 derived keys are printed to stderr.
17937 * Copy the flags in ASN1_STRING_dup().
17939 *Roman E. Pavlov <pre@mo.msk.ru>*
17941 * The x509 application mishandled signing requests containing DSA
17942 keys when the signing key was also DSA and the parameters didn't match.
17944 It was supposed to omit the parameters when they matched the signing key:
17945 the verifying software was then supposed to automatically use the CA's
17946 parameters if they were absent from the end user certificate.
17948 Omitting parameters is no longer recommended. The test was also
17949 the wrong way round! This was probably due to unusual behaviour in
17950 EVP_cmp_parameters() which returns 1 if the parameters match.
17951 This meant that parameters were omitted when they *didn't* match and
17952 the certificate was useless. Certificates signed with 'ca' didn't have
17955 *Steve Henson, reported by Doug Erickson <Doug.Erickson@Part.NET>*
17957 * Memory leak checking (-DCRYPTO_MDEBUG) had some problems.
17958 The interface is as follows:
17959 Applications can use
17960 CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_ON) aka MemCheck_start(),
17961 CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_OFF) aka MemCheck_stop();
17962 "off" is now the default.
17963 The library internally uses
17964 CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_DISABLE) aka MemCheck_off(),
17965 CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_ENABLE) aka MemCheck_on()
17966 to disable memory-checking temporarily.
17968 Some inconsistent states that previously were possible (and were
17969 even the default) are now avoided.
17971 -DCRYPTO_MDEBUG_TIME is new and additionally stores the current time
17972 with each memory chunk allocated; this is occasionally more helpful
17973 than just having a counter.
17975 -DCRYPTO_MDEBUG_THREAD is also new and adds the thread ID.
17977 -DCRYPTO_MDEBUG_ALL enables all of the above, plus any future
17982 * Introduce "mode" for SSL structures (with defaults in SSL_CTX),
17983 which largely parallels "options", but is for changing API behaviour,
17984 whereas "options" are about protocol behaviour.
17985 Initial "mode" flags are:
17987 SSL_MODE_ENABLE_PARTIAL_WRITE Allow SSL_write to report success when
17988 a single record has been written.
17989 SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER Don't insist that SSL_write
17990 retries use the same buffer location.
17991 (But all of the contents must be
17996 * Bugfix: SSL_set_options ignored its parameter, only SSL_CTX_set_options
17999 * Fix problems with no-hmac etc.
18001 *Ulf Möller, pointed out by Brian Wellington <bwelling@tislabs.com>*
18003 * New functions RSA_get_default_method(), RSA_set_method() and
18004 RSA_get_method(). These allows replacement of RSA_METHODs without having
18005 to mess around with the internals of an RSA structure.
18009 * Fix memory leaks in DSA_do_sign and DSA_is_prime.
18010 Also really enable memory leak checks in openssl.c and in some
18013 *Chad C. Mulligan, Bodo Moeller*
18015 * Fix a bug in d2i_ASN1_INTEGER() and i2d_ASN1_INTEGER() which can mess
18016 up the length of negative integers. This has now been simplified to just
18017 store the length when it is first determined and use it later, rather
18018 than trying to keep track of where data is copied and updating it to
18020 *Steve Henson, reported by Brien Wheeler <bwheeler@authentica-security.com>*
18022 * Add a new function PKCS7_signatureVerify. This allows the verification
18023 of a PKCS#7 signature but with the signing certificate passed to the
18024 function itself. This contrasts with PKCS7_dataVerify which assumes the
18025 certificate is present in the PKCS#7 structure. This isn't always the
18026 case: certificates can be omitted from a PKCS#7 structure and be
18027 distributed by "out of band" means (such as a certificate database).
18031 * Complete the `PEM_*` macros with DECLARE_PEM versions to replace the
18032 function prototypes in pem.h, also change util/mkdef.pl to add the
18033 necessary function names.
18037 * mk1mf.pl (used by Windows builds) did not properly read the
18038 options set by Configure in the top level Makefile, and Configure
18039 was not even able to write more than one option correctly.
18040 Fixed, now "no-idea no-rc5 -DCRYPTO_MDEBUG" etc. works as intended.
18044 * New functions CONF_load_bio() and CONF_load_fp() to allow a config
18045 file to be loaded from a BIO or FILE pointer. The BIO version will
18046 for example allow memory BIOs to contain config info.
18050 * New function "CRYPTO_num_locks" that returns CRYPTO_NUM_LOCKS.
18051 Whoever hopes to achieve shared-library compatibility across versions
18052 must use this, not the compile-time macro.
18053 (Exercise 0.9.4: Which is the minimum library version required by
18055 Note: All this applies only to multi-threaded programs, others don't
18060 * Add missing case to s3_clnt.c state machine -- one of the new SSL tests
18061 through a BIO pair triggered the default case, i.e.
18062 SSLerr(...,SSL_R_UNKNOWN_STATE).
18066 * New "BIO pair" concept (crypto/bio/bss_bio.c) so that applications
18067 can use the SSL library even if none of the specific BIOs is
18072 * Fix a bug in i2d_DSAPublicKey() which meant it returned the wrong value
18073 for the encoded length.
18075 *Jeon KyoungHo <khjeon@sds.samsung.co.kr>*
18077 * Add initial documentation of the X509V3 functions.
18081 * Add a new pair of functions PEM_write_PKCS8PrivateKey() and
18082 PEM_write_bio_PKCS8PrivateKey() that are equivalent to
18083 PEM_write_PrivateKey() and PEM_write_bio_PrivateKey() but use the more
18084 secure PKCS#8 private key format with a high iteration count.
18088 * Fix determination of Perl interpreter: A perl or perl5
18089 *directory* in $PATH was also accepted as the interpreter.
18091 *Ralf S. Engelschall*
18093 * Fix demos/sign/sign.c: well there wasn't anything strictly speaking
18094 wrong with it but it was very old and did things like calling
18095 PEM_ASN1_read() directly and used MD5 for the hash not to mention some
18096 unusual formatting.
18100 * Fix demos/selfsign.c: it used obsolete and deleted functions, changed
18101 to use the new extension code.
18105 * Implement the PEM_read/PEM_write functions in crypto/pem/pem_all.c
18106 with macros. This should make it easier to change their form, add extra
18107 arguments etc. Fix a few PEM prototypes which didn't have cipher as a
18112 * Add to configuration table a new entry that can specify an alternative
18113 name for unistd.h (for pre-POSIX systems); we need this for NeXTstep,
18114 according to Mark Crispin <MRC@Panda.COM>.
18118 * DES CBC did not update the IV. Weird.
18122 des_cbc_encrypt does not update the IV, but des_ncbc_encrypt does.
18123 Changing the behaviour of the former might break existing programs --
18124 where IV updating is needed, des_ncbc_encrypt can be used.
18127 * When bntest is run from "make test" it drives bc to check its
18128 calculations, as well as internally checking them. If an internal check
18129 fails, it needs to cause bc to give a non-zero result or make test carries
18130 on without noticing the failure. Fixed.
18134 * DES library cleanups.
18138 * Add support for PKCS#5 v2.0 PBE algorithms. This will permit PKCS#8 to be
18139 used with any cipher unlike PKCS#5 v1.5 which can at most handle 64 bit
18140 ciphers. NOTE: although the key derivation function has been verified
18141 against some published test vectors it has not been extensively tested
18142 yet. Added a -v2 "cipher" option to pkcs8 application to allow the use
18147 * Instead of "mkdir -p", which is not fully portable, use new
18148 Perl script "util/mkdir-p.pl".
18152 * Rewrite the way password based encryption (PBE) is handled. It used to
18153 assume that the ASN1 AlgorithmIdentifier parameter was a PBEParameter
18154 structure. This was true for the PKCS#5 v1.5 and PKCS#12 PBE algorithms
18155 but doesn't apply to PKCS#5 v2.0 where it can be something else. Now
18156 the 'parameter' field of the AlgorithmIdentifier is passed to the
18157 underlying key generation function so it must do its own ASN1 parsing.
18158 This has also changed the EVP_PBE_CipherInit() function which now has a
18159 'parameter' argument instead of literal salt and iteration count values
18160 and the function EVP_PBE_ALGOR_CipherInit() has been deleted.
18164 * Support for PKCS#5 v1.5 compatible password based encryption algorithms
18165 and PKCS#8 functionality. New 'pkcs8' application linked to openssl.
18166 Needed to change the PEM_STRING_EVP_PKEY value which was just "PRIVATE
18167 KEY" because this clashed with PKCS#8 unencrypted string. Since this
18168 value was just used as a "magic string" and not used directly its
18169 value doesn't matter.
18173 * Introduce some semblance of const correctness to BN. Shame C doesn't
18178 * "linux-sparc64" configuration (ultrapenguin).
18180 *Ray Miller <ray.miller@oucs.ox.ac.uk>*
18181 "linux-sparc" configuration.
18183 *Christian Forster <fo@hawo.stw.uni-erlangen.de>*
18185 * config now generates no-xxx options for missing ciphers.
18189 * Support the EBCDIC character set (work in progress).
18190 File ebcdic.c not yet included because it has a different license.
18192 *Martin Kraemer <Martin.Kraemer@MchP.Siemens.De>*
18194 * Support BS2000/OSD-POSIX.
18196 *Martin Kraemer <Martin.Kraemer@MchP.Siemens.De>*
18198 * Make callbacks for key generation use `void *` instead of `char *`.
18202 * Make S/MIME samples compile (not yet tested).
18206 * Additional typesafe stacks.
18210 * New configuration variants "bsdi-elf-gcc" (BSD/OS 4.x).
18214 ### Changes between 0.9.3 and 0.9.3a [29 May 1999]
18216 * New configuration variant "sco5-gcc".
18218 * Updated some demos.
18220 *Sean O Riordain, Wade Scholine*
18222 * Add missing BIO_free at exit of pkcs12 application.
18226 * Fix memory leak in conf.c.
18230 * Updates for Win32 to assembler version of MD5.
18234 * Set #! path to perl in `apps/der_chop` to where we found it
18235 instead of using a fixed path.
18239 * SHA library changes for irix64-mips4-cc.
18243 * Improvements for VMS support.
18247 ### Changes between 0.9.2b and 0.9.3 [24 May 1999]
18249 * Bignum library bug fix. IRIX 6 passes "make test" now!
18250 This also avoids the problems with SC4.2 and unpatched SC5.
18252 *Andy Polyakov <appro@fy.chalmers.se>*
18254 * New functions sk_num, sk_value and sk_set to replace the previous macros.
18255 These are required because of the typesafe stack would otherwise break
18256 existing code. If old code used a structure member which used to be STACK
18257 and is now STACK_OF (for example cert in a PKCS7_SIGNED structure) with
18258 sk_num or sk_value it would produce an error because the num, data members
18259 are not present in STACK_OF. Now it just produces a warning. sk_set
18260 replaces the old method of assigning a value to sk_value
18261 (e.g. sk_value(x, i) = y) which the library used in a few cases. Any code
18262 that does this will no longer work (and should use sk_set instead) but
18263 this could be regarded as a "questionable" behaviour anyway.
18267 * Fix most of the other PKCS#7 bugs. The "experimental" code can now
18268 correctly handle encrypted S/MIME data.
18272 * Change type of various DES function arguments from des_cblock
18273 (which means, in function argument declarations, pointer to char)
18274 to des_cblock * (meaning pointer to array with 8 char elements),
18275 which allows the compiler to do more typechecking; it was like
18276 that back in SSLeay, but with lots of ugly casts.
18278 Introduce new type const_des_cblock.
18282 * Reorganise the PKCS#7 library and get rid of some of the more obvious
18283 problems: find RecipientInfo structure that matches recipient certificate
18284 and initialise the ASN1 structures properly based on passed cipher.
18288 * Belatedly make the BN tests actually check the results.
18292 * Fix the encoding and decoding of negative ASN1 INTEGERS and conversion
18293 to and from BNs: it was completely broken. New compilation option
18294 NEG_PUBKEY_BUG to allow for some broken certificates that encode public
18295 key elements as negative integers.
18299 * Reorganize and speed up MD5.
18301 *Andy Polyakov <appro@fy.chalmers.se>*
18305 *Richard Levitte <richard@levitte.org>*
18307 * New option -out to asn1parse to allow the parsed structure to be
18308 output to a file. This is most useful when combined with the -strparse
18309 option to examine the output of things like OCTET STRINGS.
18313 * Make SSL library a little more fool-proof by not requiring any longer
18314 that `SSL_set_{accept,connect}_state` be called before
18315 `SSL_{accept,connect}` may be used (`SSL_set_..._state` is omitted
18316 in many applications because usually everything *appeared* to work as
18317 intended anyway -- now it really works as intended).
18321 * Move openssl.cnf out of lib/.
18325 * Fix various things to let OpenSSL even pass "egcc -pipe -O2 -Wall
18326 -Wshadow -Wpointer-arith -Wcast-align -Wmissing-prototypes
18327 -Wmissing-declarations -Wnested-externs -Winline" with EGCS 1.1.2+
18329 *Ralf S. Engelschall*
18331 * Various fixes to the EVP and PKCS#7 code. It may now be able to
18332 handle PKCS#7 enveloped data properly.
18334 *Sebastian Akerman <sak@parallelconsulting.com>, modified by Steve*
18336 * Create a duplicate of the SSL_CTX's CERT in SSL_new instead of
18337 copying pointers. The cert_st handling is changed by this in
18338 various ways (and thus what used to be known as ctx->default_cert
18339 is now called ctx->cert, since we don't resort to `s->ctx->[default_]cert`
18340 any longer when s->cert does not give us what we need).
18341 ssl_cert_instantiate becomes obsolete by this change.
18342 As soon as we've got the new code right (possibly it already is?),
18343 we have solved a couple of bugs of the earlier code where s->cert
18344 was used as if it could not have been shared with other SSL structures.
18346 Note that using the SSL API in certain dirty ways now will result
18347 in different behaviour than observed with earlier library versions:
18348 Changing settings for an `SSL_CTX *ctx` after having done s = SSL_new(ctx)
18349 does not influence s as it used to.
18351 In order to clean up things more thoroughly, inside SSL_SESSION
18352 we don't use CERT any longer, but a new structure SESS_CERT
18353 that holds per-session data (if available); currently, this is
18354 the peer's certificate chain and, for clients, the server's certificate
18355 and temporary key. CERT holds only those values that can have
18356 meaningful defaults in an SSL_CTX.
18360 * New function X509V3_EXT_i2d() to create an X509_EXTENSION structure
18361 from the internal representation. Various PKCS#7 fixes: remove some
18362 evil casts and set the enc_dig_alg field properly based on the signing
18367 * Allow PKCS#12 password to be set from the command line or the
18368 environment. Let 'ca' get its config file name from the environment
18369 variables "OPENSSL_CONF" or "SSLEAY_CONF" (for consistency with 'req'
18374 * Allow certificate policies extension to use an IA5STRING for the
18375 organization field. This is contrary to the PKIX definition but
18376 VeriSign uses it and IE5 only recognises this form. Document 'x509'
18381 * Add PEDANTIC compiler flag to allow compilation with gcc -pedantic,
18382 without disallowing inline assembler and the like for non-pedantic builds.
18386 * Support Borland C++ builder.
18388 *Janez Jere <jj@void.si>, modified by Ulf Möller*
18394 * SHA-1 cleanups and performance enhancements.
18396 *Andy Polyakov <appro@fy.chalmers.se>*
18398 * Sparc v8plus assembler for the bignum library.
18400 *Andy Polyakov <appro@fy.chalmers.se>*
18402 * Accept any -xxx and +xxx compiler options in Configure.
18406 * Update HPUX configuration.
18410 * Add missing `sk_<type>_unshift()` function to safestack.h
18412 *Ralf S. Engelschall*
18414 * New function SSL_CTX_use_certificate_chain_file that sets the
18415 "extra_cert"s in addition to the certificate. (This makes sense
18416 only for "PEM" format files, as chains as a whole are not
18421 * Support verify_depth from the SSL API.
18422 x509_vfy.c had what can be considered an off-by-one-error:
18423 Its depth (which was not part of the external interface)
18424 was actually counting the number of certificates in a chain;
18425 now it really counts the depth.
18429 * Bugfix in crypto/x509/x509_cmp.c: The SSLerr macro was used
18430 instead of X509err, which often resulted in confusing error
18431 messages since the error codes are not globally unique
18432 (e.g. an alleged error in ssl3_accept when a certificate
18433 didn't match the private key).
18435 * New function SSL_CTX_set_session_id_context that allows to set a default
18436 value (so that you don't need SSL_set_session_id_context for each
18437 connection using the SSL_CTX).
18441 * OAEP decoding bug fix.
18445 * Support INSTALL_PREFIX for package builders, as proposed by
18450 * New Configure options "threads" and "no-threads". For systems
18451 where the proper compiler options are known (currently Solaris
18452 and Linux), "threads" is the default.
18456 * New script util/mklink.pl as a faster substitute for util/mklink.sh.
18460 * Install various scripts to $(OPENSSLDIR)/misc, not to
18461 $(INSTALLTOP)/bin -- they shouldn't clutter directories
18462 such as /usr/local/bin.
18466 * "make linux-shared" to build shared libraries.
18468 *Niels Poppe <niels@netbox.org>*
18470 * New Configure option `no-<cipher>` (rsa, idea, rc5, ...).
18474 * Add the PKCS#12 API documentation to openssl.txt. Preliminary support for
18475 extension adding in x509 utility.
18479 * Remove NOPROTO sections and error code comments.
18483 * Partial rewrite of the DEF file generator to now parse the ANSI
18488 * New Configure options --prefix=DIR and --openssldir=DIR.
18492 * Complete rewrite of the error code script(s). It is all now handled
18493 by one script at the top level which handles error code gathering,
18494 header rewriting and C source file generation. It should be much better
18495 than the old method: it now uses a modified version of Ulf's parser to
18496 read the ANSI prototypes in all header files (thus the old K&R definitions
18497 aren't needed for error creation any more) and do a better job of
18498 translating function codes into names. The old 'ASN1 error code embedded
18499 in a comment' is no longer necessary and it doesn't use .err files which
18500 have now been deleted. Also the error code call doesn't have to appear all
18501 on one line (which resulted in some large lines...).
18505 * Change #include filenames from `<foo.h>` to `<openssl/foo.h>`.
18509 * Change behaviour of ssl2_read when facing length-0 packets: Don't return
18510 0 (which usually indicates a closed connection), but continue reading.
18514 * Fix some race conditions.
18518 * Add support for CRL distribution points extension. Add Certificate
18519 Policies and CRL distribution points documentation.
18523 * Move the autogenerated header file parts to crypto/opensslconf.h.
18527 * Fix new 56-bit DES export ciphersuites: they were using 7 bytes instead of
18528 8 of keying material. Merlin has also confirmed interop with this fix
18529 between OpenSSL and Baltimore C/SSL 2.0 and J/SSL 2.0.
18531 *Merlin Hughes <merlin@baltimore.ie>*
18533 * Fix lots of warnings.
18535 *Richard Levitte <levitte@stacken.kth.se>*
18537 * In add_cert_dir() in crypto/x509/by_dir.c, break out of the loop if
18538 the directory spec didn't end with a LIST_SEPARATOR_CHAR.
18540 *Richard Levitte <levitte@stacken.kth.se>*
18542 * Fix problems with sizeof(long) == 8.
18544 *Andy Polyakov <appro@fy.chalmers.se>*
18546 * Change functions to ANSI C.
18550 * Fix typos in error codes.
18552 *Martin Kraemer <Martin.Kraemer@MchP.Siemens.De>, Ulf Möller*
18554 * Remove defunct assembler files from Configure.
18558 * SPARC v8 assembler BIGNUM implementation.
18560 *Andy Polyakov <appro@fy.chalmers.se>*
18562 * Support for Certificate Policies extension: both print and set.
18563 Various additions to support the r2i method this uses.
18567 * A lot of constification, and fix a bug in X509_NAME_oneline() that could
18568 return a const string when you are expecting an allocated buffer.
18572 * Add support for ASN1 types UTF8String and VISIBLESTRING, also the CHOICE
18573 types DirectoryString and DisplayText.
18577 * Add code to allow r2i extensions to access the configuration database,
18578 add an LHASH database driver and add several ctx helper functions.
18582 * Fix an evil bug in bn_expand2() which caused various BN functions to
18583 fail when they extended the size of a BIGNUM.
18587 * Various utility functions to handle SXNet extension. Modify mkdef.pl to
18588 support typesafe stack.
18592 * Fix typo in SSL_[gs]et_options().
18594 *Nils Frostberg <nils@medcom.se>*
18596 * Delete various functions and files that belonged to the (now obsolete)
18597 old X509V3 handling code.
18601 * New Configure option "rsaref".
18605 * Don't auto-generate pem.h.
18609 * Introduce type-safe ASN.1 SETs.
18613 * Convert various additional casted stacks to type-safe STACK_OF() variants.
18615 *Ben Laurie, Ralf S. Engelschall, Steve Henson*
18617 * Introduce type-safe STACKs. This will almost certainly break lots of code
18618 that links with OpenSSL (well at least cause lots of warnings), but fear
18619 not: the conversion is trivial, and it eliminates loads of evil casts. A
18620 few STACKed things have been converted already. Feel free to convert more.
18621 In the fullness of time, I'll do away with the STACK type altogether.
18625 * Add `openssl ca -revoke <certfile>` facility which revokes a certificate
18626 specified in `<certfile>` by updating the entry in the index.txt file.
18627 This way one no longer has to edit the index.txt file manually for
18628 revoking a certificate. The -revoke option does the gory details now.
18630 *Massimiliano Pala <madwolf@openca.org>, Ralf S. Engelschall*
18632 * Fix `openssl crl -noout -text` combination where `-noout` killed the
18633 `-text` option at all and this way the `-noout -text` combination was
18634 inconsistent in `openssl crl` with the friends in `openssl x509|rsa|dsa`.
18636 *Ralf S. Engelschall*
18638 * Make sure a corresponding plain text error message exists for the
18639 X509_V_ERR_CERT_REVOKED/23 error number which can occur when a
18640 verify callback function determined that a certificate was revoked.
18642 *Ralf S. Engelschall*
18644 * Bugfix: In test/testenc, don't test `openssl <cipher>` for
18645 ciphers that were excluded, e.g. by -DNO_IDEA. Also, test
18646 all available ciphers including rc5, which was forgotten until now.
18647 In order to let the testing shell script know which algorithms
18648 are available, a new (up to now undocumented) command
18649 `openssl list-cipher-commands` is used.
18653 * Bugfix: s_client occasionally would sleep in select() when
18654 it should have checked SSL_pending() first.
18658 * New functions DSA_do_sign and DSA_do_verify to provide access to
18659 the raw DSA values prior to ASN.1 encoding.
18663 * Tweaks to Configure
18665 *Niels Poppe <niels@netbox.org>*
18667 * Add support for PKCS#5 v2.0 ASN1 PBES2 structures. No other support,
18672 * New variables $(RANLIB) and $(PERL) in the Makefiles.
18676 * New config option to avoid instructions that are illegal on the 80386.
18677 The default code is faster, but requires at least a 486.
18681 * Got rid of old SSL2_CLIENT_VERSION (inconsistently used) and
18682 SSL2_SERVER_VERSION (not used at all) macros, which are now the
18683 same as SSL2_VERSION anyway.
18687 * New "-showcerts" option for s_client.
18691 * Still more PKCS#12 integration. Add pkcs12 application to openssl
18692 application. Various cleanups and fixes.
18696 * More PKCS#12 integration. Add new pkcs12 directory with Makefile.ssl and
18697 modify error routines to work internally. Add error codes and PBE init
18698 to library startup routines.
18702 * Further PKCS#12 integration. Added password based encryption, PKCS#8 and
18703 packing functions to asn1 and evp. Changed function names and error
18704 codes along the way.
18708 * PKCS12 integration: and so it begins... First of several patches to
18709 slowly integrate PKCS#12 functionality into OpenSSL. Add PKCS#12
18710 objects to objects.h
18714 * Add a new 'indent' option to some X509V3 extension code. Initial ASN1
18715 and display support for Thawte strong extranet extension.
18719 * Add LinuxPPC support.
18721 *Jeff Dubrule <igor@pobox.org>*
18723 * Get rid of redundant BN file bn_mulw.c, and rename bn_div64 to
18724 bn_div_words in alpha.s.
18726 *Hannes Reinecke <H.Reinecke@hw.ac.uk> and Ben Laurie*
18728 * Make sure the RSA OAEP test is skipped under -DRSAref because
18729 OAEP isn't supported when OpenSSL is built with RSAref.
18731 *Ulf Moeller <ulf@fitug.de>*
18733 * Move definitions of IS_SET/IS_SEQUENCE inside crypto/asn1/asn1.h
18734 so they no longer are missing under -DNOPROTO.
18736 *Soren S. Jorvang <soren@t.dk>*
18738 ### Changes between 0.9.1c and 0.9.2b [22 Mar 1999]
18740 * Make SSL_get_peer_cert_chain() work in servers. Unfortunately, it still
18741 doesn't work when the session is reused. Coming soon!
18745 * Fix a security hole, that allows sessions to be reused in the wrong
18746 context thus bypassing client cert protection! All software that uses
18747 client certs and session caches in multiple contexts NEEDS PATCHING to
18748 allow session reuse! A fuller solution is in the works.
18750 *Ben Laurie, problem pointed out by Holger Reif, Bodo Moeller (and ???)*
18752 * Some more source tree cleanups (removed obsolete files
18753 crypto/bf/asm/bf586.pl, test/test.txt and crypto/sha/asm/f.s; changed
18754 permission on "config" script to be executable) and a fix for the INSTALL
18757 *Ulf Moeller <ulf@fitug.de>*
18759 * Remove some legacy and erroneous uses of malloc, free instead of
18762 *Lennart Bang <lob@netstream.se>, with minor changes by Steve*
18764 * Make rsa_oaep_test return non-zero on error.
18766 *Ulf Moeller <ulf@fitug.de>*
18768 * Add support for native Solaris shared libraries. Configure
18769 solaris-sparc-sc4-pic, make, then run shlib/solaris-sc4.sh. It'd be nice
18770 if someone would make that last step automatic.
18772 *Matthias Loepfe <Matthias.Loepfe@AdNovum.CH>*
18774 * ctx_size was not built with the right compiler during "make links". Fixed.
18778 * Change the meaning of 'ALL' in the cipher list. It now means "everything
18779 except NULL ciphers". This means the default cipher list will no longer
18780 enable NULL ciphers. They need to be specifically enabled e.g. with
18781 the string "DEFAULT:eNULL".
18785 * Fix to RSA private encryption routines: if p < q then it would
18786 occasionally produce an invalid result. This will only happen with
18787 externally generated keys because OpenSSL (and SSLeay) ensure p > q.
18791 * Be less restrictive and allow also `perl util/perlpath.pl
18792 /path/to/bin/perl` in addition to `perl util/perlpath.pl /path/to/bin`,
18793 because this way one can also use an interpreter named `perl5` (which is
18794 usually the name of Perl 5.xxx on platforms where an Perl 4.x is still
18795 installed as `perl`).
18797 *Matthias Loepfe <Matthias.Loepfe@adnovum.ch>*
18799 * Let util/clean-depend.pl work also with older Perl 5.00x versions.
18801 *Matthias Loepfe <Matthias.Loepfe@adnovum.ch>*
18803 * Fix Makefile.org so CC,CFLAG etc are passed to 'make links' add
18804 advapi32.lib to Win32 build and change the pem test comparison
18805 to fc.exe (thanks to Ulrich Kroener <kroneru@yahoo.com> for the
18806 suggestion). Fix misplaced ASNI prototypes and declarations in evp.h
18807 and crypto/des/ede_cbcm_enc.c.
18811 * DES quad checksum was broken on big-endian architectures. Fixed.
18815 * Comment out two functions in bio.h that aren't implemented. Fix up the
18816 Win32 test batch file so it (might) work again. The Win32 test batch file
18817 is horrible: I feel ill....
18821 * Move various #ifdefs around so NO_SYSLOG, NO_DIRENT etc are now selected
18822 in e_os.h. Audit of header files to check ANSI and non ANSI
18823 sections: 10 functions were absent from non ANSI section and not exported
18824 from Windows DLLs. Fixed up libeay.num for new functions.
18828 * Make `openssl version` output lines consistent.
18830 *Ralf S. Engelschall*
18832 * Fix Win32 symbol export lists for BIO functions: Added
18833 BIO_get_ex_new_index, BIO_get_ex_num, BIO_get_ex_data and BIO_set_ex_data
18834 to ms/libeay{16,32}.def.
18836 *Ralf S. Engelschall*
18838 * Second round of fixing the OpenSSL perl/ stuff. It now at least compiled
18839 fine under Unix and passes some trivial tests I've now added. But the
18840 whole stuff is horribly incomplete, so a README.1ST with a disclaimer was
18841 added to make sure no one expects that this stuff really works in the
18842 OpenSSL 0.9.2 release. Additionally I've started to clean the XS sources
18843 up and fixed a few little bugs and inconsistencies in OpenSSL.{pm,xs} and
18846 *Ralf S. Engelschall*
18848 * Fix the generation of two part addresses in perl.
18850 *Kenji Miyake <kenji@miyake.org>, integrated by Ben Laurie*
18852 * Add config entry for Linux on MIPS.
18854 *John Tobey <jtobey@channel1.com>*
18856 * Make links whenever Configure is run, unless we are on Windoze.
18860 * Permit extensions to be added to CRLs using crl_section in openssl.cnf.
18861 Currently only issuerAltName and AuthorityKeyIdentifier make any sense
18866 * Add a useful kludge to allow package maintainers to specify compiler and
18867 other platforms details on the command line without having to patch the
18868 Configure script every time: One now can use
18869 `perl Configure <id>:<details>`,
18870 i.e. platform ids are allowed to have details appended
18871 to them (separated by colons). This is treated as there would be a static
18872 pre-configured entry in Configure's %table under key `<id>` with value
18873 `<details>` and `perl Configure <id>` is called. So, when you want to
18874 perform a quick test-compile under FreeBSD 3.1 with pgcc and without
18875 assembler stuff you can use `perl Configure "FreeBSD-elf:pgcc:-O6:::"`
18876 now, which overrides the FreeBSD-elf entry on-the-fly.
18878 *Ralf S. Engelschall*
18880 * Disable new TLS1 ciphersuites by default: they aren't official yet.
18884 * Allow DSO flags like -fpic, -fPIC, -KPIC etc. to be specified
18885 on the `perl Configure ...` command line. This way one can compile
18886 OpenSSL libraries with Position Independent Code (PIC) which is needed
18887 for linking it into DSOs.
18889 *Ralf S. Engelschall*
18891 * Remarkably, export ciphers were totally broken and no-one had noticed!
18896 * Cleaned up the LICENSE document: The official contact for any license
18897 questions now is the OpenSSL core team under openssl-core@openssl.org.
18898 And add a paragraph about the dual-license situation to make sure people
18899 recognize that _BOTH_ the OpenSSL license _AND_ the SSLeay license apply
18900 to the OpenSSL toolkit.
18902 *Ralf S. Engelschall*
18904 * General source tree makefile cleanups: Made `making xxx in yyy...`
18905 display consistent in the source tree and replaced `/bin/rm` by `rm`.
18906 Additionally cleaned up the `make links` target: Remove unnecessary
18907 semicolons, subsequent redundant removes, inline point.sh into mklink.sh
18908 to speed processing and no longer clutter the display with confusing
18909 stuff. Instead only the actually done links are displayed.
18911 *Ralf S. Engelschall*
18913 * Permit null encryption ciphersuites, used for authentication only. It used
18914 to be necessary to set the preprocessor define SSL_ALLOW_ENULL to do this.
18915 It is now necessary to set SSL_FORBID_ENULL to prevent the use of null
18920 * Add a bunch of fixes to the PKCS#7 stuff. It used to sometimes reorder
18921 signed attributes when verifying signatures (this would break them),
18922 the detached data encoding was wrong and public keys obtained using
18923 X509_get_pubkey() weren't freed.
18927 * Add text documentation for the BUFFER functions. Also added a work around
18928 to a Win95 console bug. This was triggered by the password read stuff: the
18929 last character typed gets carried over to the next fread(). If you were
18930 generating a new cert request using 'req' for example then the last
18931 character of the passphrase would be CR which would then enter the first
18936 * Added the new 'Includes OpenSSL Cryptography Software' button as
18937 doc/openssl_button.{gif,html} which is similar in style to the old SSLeay
18938 button and can be used by applications based on OpenSSL to show the
18939 relationship to the OpenSSL project.
18941 *Ralf S. Engelschall*
18943 * Remove confusing variables in function signatures in files
18944 ssl/ssl_lib.c and ssl/ssl.h.
18946 *Lennart Bong <lob@kulthea.stacken.kth.se>*
18948 * Don't install bss_file.c under PREFIX/include/
18950 *Lennart Bong <lob@kulthea.stacken.kth.se>*
18952 * Get the Win32 compile working again. Modify mkdef.pl so it can handle
18953 functions that return function pointers and has support for NT specific
18954 stuff. Fix mk1mf.pl and VC-32.pl to support NT differences also. Various
18955 #ifdef WIN32 and WINNTs sprinkled about the place and some changes from
18956 unsigned to signed types: this was killing the Win32 compile.
18960 * Add new certificate file to stack functions,
18961 SSL_add_dir_cert_subjects_to_stack() and
18962 SSL_add_file_cert_subjects_to_stack(). These largely supplant
18963 SSL_load_client_CA_file(), and can be used to add multiple certs easily
18964 to a stack (usually this is then handed to SSL_CTX_set_client_CA_list()).
18965 This means that Apache-SSL and similar packages don't have to mess around
18966 to add as many CAs as they want to the preferred list.
18970 * Experiment with doxygen documentation. Currently only partially applied to
18972 See <http://www.stack.nl/~dimitri/doxygen/index.html>, and run doxygen with
18973 openssl.doxy as the configuration file.
18977 * Get rid of remaining C++-style comments which strict C compilers hate.
18979 *Ralf S. Engelschall, pointed out by Carlos Amengual*
18981 * Changed BN_RECURSION in bn_mont.c to BN_RECURSION_MONT so it is not
18982 compiled in by default: it has problems with large keys.
18986 * Add a bunch of SSL_xxx() functions for configuring the temporary RSA and
18987 DH private keys and/or callback functions which directly correspond to
18988 their SSL_CTX_xxx() counterparts but work on a per-connection basis. This
18989 is needed for applications which have to configure certificates on a
18990 per-connection basis (e.g. Apache+mod_ssl) instead of a per-context basis
18992 For the RSA certificate situation is makes no difference, but
18993 for the DSA certificate situation this fixes the "no shared cipher"
18994 problem where the OpenSSL cipher selection procedure failed because the
18995 temporary keys were not overtaken from the context and the API provided
18996 no way to reconfigure them.
18997 The new functions now let applications reconfigure the stuff and they
18998 are in detail: SSL_need_tmp_RSA, SSL_set_tmp_rsa, SSL_set_tmp_dh,
18999 SSL_set_tmp_rsa_callback and SSL_set_tmp_dh_callback. Additionally a new
19000 non-public-API function ssl_cert_instantiate() is used as a helper
19001 function and also to reduce code redundancy inside ssl_rsa.c.
19003 *Ralf S. Engelschall*
19005 * Move s_server -dcert and -dkey options out of the undocumented feature
19006 area because they are useful for the DSA situation and should be
19007 recognized by the users.
19009 *Ralf S. Engelschall*
19011 * Fix the cipher decision scheme for export ciphers: the export bits are
19012 *not* within SSL_MKEY_MASK or SSL_AUTH_MASK, they are within
19013 SSL_EXP_MASK. So, the original variable has to be used instead of the
19014 already masked variable.
19016 *Richard Levitte <levitte@stacken.kth.se>*
19018 * Fix `port` variable from `int` to `unsigned int` in crypto/bio/b_sock.c
19020 *Richard Levitte <levitte@stacken.kth.se>*
19022 * Change type of another md_len variable in pk7_doit.c:PKCS7_dataFinal()
19023 from `int` to `unsigned int` because it is a length and initialized by
19024 EVP_DigestFinal() which expects an `unsigned int *`.
19026 *Richard Levitte <levitte@stacken.kth.se>*
19028 * Don't hard-code path to Perl interpreter on shebang line of Configure
19029 script. Instead use the usual Shell->Perl transition trick.
19031 *Ralf S. Engelschall*
19033 * Make `openssl x509 -noout -modulus`' functional also for DSA certificates
19034 (in addition to RSA certificates) to match the behaviour of `openssl dsa
19035 -noout -modulus` as it's already the case for `openssl rsa -noout
19036 -modulus`. For RSA the -modulus is the real "modulus" while for DSA
19037 currently the public key is printed (a decision which was already done by
19038 `openssl dsa -modulus` in the past) which serves a similar purpose.
19039 Additionally the NO_RSA no longer completely removes the whole -modulus
19040 option; it now only avoids using the RSA stuff. Same applies to NO_DSA
19043 *Ralf S. Engelschall*
19045 * Add Arne Ansper's reliable BIO - this is an encrypted, block-digested
19046 BIO. See the source (crypto/evp/bio_ok.c) for more info.
19048 *Arne Ansper <arne@ats.cyber.ee>*
19050 * Dump the old yucky req code that tried (and failed) to allow raw OIDs
19051 to be added. Now both 'req' and 'ca' can use new objects defined in the
19056 * Add cool BIO that does syslog (or event log on NT).
19058 *Arne Ansper <arne@ats.cyber.ee>, integrated by Ben Laurie*
19060 * Add support for new TLS ciphersuites, TLS_RSA_EXPORT56_WITH_RC4_56_MD5,
19061 TLS_RSA_EXPORT56_WITH_RC2_CBC_56_MD5 and
19062 TLS_RSA_EXPORT56_WITH_DES_CBC_SHA, as specified in "56-bit Export Cipher
19063 Suites For TLS", draft-ietf-tls-56-bit-ciphersuites-00.txt.
19067 * Add preliminary config info for new extension code.
19071 * Make RSA_NO_PADDING really use no padding.
19073 *Ulf Moeller <ulf@fitug.de>*
19075 * Generate errors when private/public key check is done.
19079 * Overhaul for 'crl' utility. New function X509_CRL_print. Partial support
19080 for some CRL extensions and new objects added.
19084 * Really fix the ASN1 IMPLICIT bug this time... Partial support for private
19085 key usage extension and fuller support for authority key id.
19089 * Add OAEP encryption for the OpenSSL crypto library. OAEP is the improved
19090 padding method for RSA, which is recommended for new applications in PKCS
19091 #1 v2.0 (RFC 2437, October 1998).
19092 OAEP (Optimal Asymmetric Encryption Padding) has better theoretical
19093 foundations than the ad-hoc padding used in PKCS #1 v1.5. It is secure
19094 against Bleichbacher's attack on RSA.
19095 *Ulf Moeller <ulf@fitug.de>, reformatted, corrected and integrated by
19098 * Updates to the new SSL compression code
19100 *Eric A. Young, (from changes to C2Net SSLeay, integrated by Mark Cox)*
19102 * Fix so that the version number in the master secret, when passed
19103 via RSA, checks that if TLS was proposed, but we roll back to SSLv3
19104 (because the server will not accept higher), that the version number
19105 is 0x03,0x01, not 0x03,0x00
19107 *Eric A. Young, (from changes to C2Net SSLeay, integrated by Mark Cox)*
19109 * Run extensive memory leak checks on SSL commands. Fixed *lots* of memory
19110 leaks in `ssl/` relating to new `X509_get_pubkey()` behaviour. Also fixes
19111 in `apps/` and an unrelated leak in `crypto/dsa/dsa_vrf.c`.
19115 * Support for RAW extensions where an arbitrary extension can be
19116 created by including its DER encoding. See `apps/openssl.cnf` for
19121 * Make sure latest Perl versions don't interpret some generated C array
19122 code as Perl array code in the crypto/err/err_genc.pl script.
19124 *Lars Weber <3weber@informatik.uni-hamburg.de>*
19126 * Modify ms/do_ms.bat to not generate assembly language makefiles since
19127 not many people have the assembler. Various Win32 compilation fixes and
19128 update to the INSTALL.W32 file with (hopefully) more accurate Win32
19129 build instructions.
19133 * Modify configure script 'Configure' to automatically create crypto/date.h
19134 file under Win32 and also build pem.h from pem.org. New script
19135 util/mkfiles.pl to create the MINFO file on environments that can't do a
19136 'make files': perl util/mkfiles.pl >MINFO should work.
19140 * Major rework of DES function declarations, in the pursuit of correctness
19141 and purity. As a result, many evil casts evaporated, and some weirdness,
19142 too. You may find this causes warnings in your code. Zapping your evil
19143 casts will probably fix them. Mostly.
19147 * Fix for a typo in asn1.h. Bug fix to object creation script
19148 obj_dat.pl. It considered a zero in an object definition to mean
19149 "end of object": none of the objects in objects.h have any zeros
19150 so it wasn't spotted.
19152 *Steve Henson, reported by Erwann ABALEA <eabalea@certplus.com>*
19154 * Add support for Triple DES Cipher Block Chaining with Output Feedback
19155 Masking (CBCM). In the absence of test vectors, the best I have been able
19156 to do is check that the decrypt undoes the encrypt, so far. Send me test
19157 vectors if you have them.
19161 * Correct calculation of key length for export ciphers (too much space was
19162 allocated for null ciphers). This has not been tested!
19166 * Modifications to the mkdef.pl for Win32 DEF file creation. The usage
19167 message is now correct (it understands "crypto" and "ssl" on its
19168 command line). There is also now an "update" option. This will update
19169 the util/ssleay.num and util/libeay.num files with any new functions.
19171 perl util/mkdef.pl crypto ssl update
19172 it will update them.
19176 * Overhauled the Perl interface:
19177 - ported BN stuff to OpenSSL's different BN library
19178 - made the perl/ source tree CVS-aware
19179 - renamed the package from SSLeay to OpenSSL (the files still contain
19180 their history because I've copied them in the repository)
19181 - removed obsolete files (the test scripts will be replaced
19182 by better Test::Harness variants in the future)
19184 *Ralf S. Engelschall*
19186 * First cut for a very conservative source tree cleanup:
19187 1. merge various obsolete readme texts into doc/ssleay.txt
19188 where we collect the old documents and readme texts.
19189 2. remove the first part of files where I'm already sure that we no
19190 longer need them because of three reasons: either they are just temporary
19191 files which were left by Eric or they are preserved original files where
19192 I've verified that the diff is also available in the CVS via "cvs diff
19193 -rSSLeay_0_8_1b" or they were renamed (as it was definitely the case for
19194 the crypto/md/ stuff).
19196 *Ralf S. Engelschall*
19198 * More extension code. Incomplete support for subject and issuer alt
19199 name, issuer and authority key id. Change the i2v function parameters
19200 and add an extra 'crl' parameter in the X509V3_CTX structure: guess
19201 what that's for :-) Fix to ASN1 macro which messed up
19202 IMPLICIT tag and add f_enum.c which adds a2i, i2a for ENUMERATED.
19206 * Preliminary support for ENUMERATED type. This is largely copied from the
19211 * Add new function, EVP_MD_CTX_copy() to replace frequent use of memcpy.
19213 *Eric A. Young, (from changes to C2Net SSLeay, integrated by Mark Cox)*
19215 * Make sure `make rehash` target really finds the `openssl` program.
19217 *Ralf S. Engelschall, Matthias Loepfe <Matthias.Loepfe@adnovum.ch>*
19219 * Squeeze another 7% of speed out of MD5 assembler, at least on a P2. I'd
19220 like to hear about it if this slows down other processors.
19224 * Add CygWin32 platform information to Configure script.
19226 *Alan Batie <batie@aahz.jf.intel.com>*
19228 * Fixed ms/32all.bat script: `no_asm` -> `no-asm`
19230 *Rainer W. Gerling <gerling@mpg-gv.mpg.de>*
19232 * New program nseq to manipulate netscape certificate sequences
19236 * Modify crl2pkcs7 so it supports multiple -certfile arguments. Fix a
19241 * Fixes to BN code. Previously the default was to define BN_RECURSION
19242 but the BN code had some problems that would cause failures when
19243 doing certificate verification and some other functions.
19245 *Eric A. Young, (from changes to C2Net SSLeay, integrated by Mark Cox)*
19247 * Add ASN1 and PEM code to support netscape certificate sequences.
19251 * Add ASN1 and PEM code to support netscape certificate sequences.
19255 * Add several PKIX and private extended key usage OIDs.
19259 * Modify the 'ca' program to handle the new extension code. Modify
19260 openssl.cnf for new extension format, add comments.
19264 * More X509 V3 changes. Fix typo in v3_bitstr.c. Add support to 'req'
19265 and add a sample to openssl.cnf so req -x509 now adds appropriate
19270 * Continued X509 V3 changes. Add to other makefiles, integrate with the
19271 error code, add initial support to X509_print() and x509 application.
19275 * Takes a deep breath and start adding X509 V3 extension support code. Add
19276 files in crypto/x509v3. Move original stuff to crypto/x509v3/old. All this
19277 stuff is currently isolated and isn't even compiled yet.
19281 * Continuing patches for GeneralizedTime. Fix up certificate and CRL
19282 ASN1 to use ASN1_TIME and modify print routines to use ASN1_TIME_print.
19283 Removed the versions check from X509 routines when loading extensions:
19284 this allows certain broken certificates that don't set the version
19285 properly to be processed.
19289 * Deal with irritating shit to do with dependencies, in YAAHW (Yet Another
19290 Ad Hoc Way) - Makefile.ssls now all contain local dependencies, which
19291 can still be regenerated with "make depend".
19295 * Spelling mistake in C version of CAST-128.
19297 *Ben Laurie, reported by Jeremy Hylton <jeremy@cnri.reston.va.us>*
19299 * Changes to the error generation code. The perl script err-code.pl
19300 now reads in the old error codes and retains the old numbers, only
19301 adding new ones if necessary. It also only changes the .err files if new
19302 codes are added. The makefiles have been modified to only insert errors
19303 when needed (to avoid needlessly modifying header files). This is done
19304 by only inserting errors if the .err file is newer than the auto generated
19305 C file. To rebuild all the error codes from scratch (the old behaviour)
19306 either modify crypto/Makefile.ssl to pass the -regen flag to err_code.pl
19307 or delete all the .err files.
19311 * CAST-128 was incorrectly implemented for short keys. The C version has
19312 been fixed, but is untested. The assembler versions are also fixed, but
19313 new assembler HAS NOT BEEN GENERATED FOR WIN32 - the Makefile needs fixing
19314 to regenerate it if needed.
19315 *Ben Laurie, reported (with fix for C version) by Jun-ichiro itojun
19316 Hagino <itojun@kame.net>*
19318 * File was opened incorrectly in randfile.c.
19320 *Ulf Möller <ulf@fitug.de>*
19322 * Beginning of support for GeneralizedTime. d2i, i2d, check and print
19323 functions. Also ASN1_TIME suite which is a CHOICE of UTCTime or
19324 GeneralizedTime. ASN1_TIME is the proper type used in certificates et
19325 al: it's just almost always a UTCTime. Note this patch adds new error
19326 codes so do a "make errors" if there are problems.
19330 * Correct Linux 1 recognition in config.
19332 *Ulf Möller <ulf@fitug.de>*
19334 * Remove pointless MD5 hash when using DSA keys in ca.
19336 *Anonymous <nobody@replay.com>*
19338 * Generate an error if given an empty string as a cert directory. Also
19339 generate an error if handed NULL (previously returned 0 to indicate an
19340 error, but didn't set one).
19342 *Ben Laurie, reported by Anonymous <nobody@replay.com>*
19344 * Add prototypes to SSL methods. Make SSL_write's buffer const, at last.
19348 * Fix the dummy function BN_ref_mod_exp() in rsaref.c to have the correct
19349 parameters. This was causing a warning which killed off the Win32 compile.
19353 * Remove C++ style comments from crypto/bn/bn_local.h.
19355 *Neil Costigan <neil.costigan@celocom.com>*
19357 * The function OBJ_txt2nid was broken. It was supposed to return a nid
19358 based on a text string, looking up short and long names and finally
19359 "dot" format. The "dot" format stuff didn't work. Added new function
19360 OBJ_txt2obj to do the same but return an ASN1_OBJECT and rewrote
19361 OBJ_txt2nid to use it. OBJ_txt2obj can also return objects even if the
19362 OID is not part of the table.
19366 * Add prototypes to X509 lookup/verify methods, fixing a bug in
19367 X509_LOOKUP_by_alias().
19371 * Sort openssl functions by name.
19375 * Get the `gendsa` command working and add it to the `list` command. Remove
19376 encryption from sample DSA keys (in case anyone is interested the password
19381 * Make *all* `*_free` functions accept a NULL pointer.
19383 *Frans Heymans <fheymans@isaserver.be>*
19385 * If a DH key is generated in s3_srvr.c, don't blow it by trying to use
19388 *Anonymous <nobody@replay.com>*
19390 * s_server should send the CAfile as acceptable CAs, not its own cert.
19392 *Bodo Moeller <3moeller@informatik.uni-hamburg.de>*
19394 * Don't blow it for numeric `-newkey` arguments to `apps/req`.
19396 *Bodo Moeller <3moeller@informatik.uni-hamburg.de>*
19398 * Temp key "for export" tests were wrong in s3_srvr.c.
19400 *Anonymous <nobody@replay.com>*
19402 * Add prototype for temp key callback functions
19403 SSL_CTX_set_tmp_{rsa,dh}_callback().
19407 * Make DH_free() tolerate being passed a NULL pointer (like RSA_free() and
19408 DSA_free()). Make X509_PUBKEY_set() check for errors in d2i_PublicKey().
19412 * X509_name_add_entry() freed the wrong thing after an error.
19414 *Arne Ansper <arne@ats.cyber.ee>*
19416 * rsa_eay.c would attempt to free a NULL context.
19418 *Arne Ansper <arne@ats.cyber.ee>*
19420 * BIO_s_socket() had a broken should_retry() on Windoze.
19422 *Arne Ansper <arne@ats.cyber.ee>*
19424 * BIO_f_buffer() didn't pass on BIO_CTRL_FLUSH.
19426 *Arne Ansper <arne@ats.cyber.ee>*
19428 * Make sure the already existing X509_STORE->depth variable is initialized
19429 in X509_STORE_new(), but document the fact that this variable is still
19430 unused in the certificate verification process.
19432 *Ralf S. Engelschall*
19434 * Fix the various library and `apps/` files to free up pkeys obtained from
19435 X509_PUBKEY_get() et al. Also allow x509.c to handle netscape extensions.
19439 * Fix reference counting in X509_PUBKEY_get(). This makes
19440 demos/maurice/example2.c work, amongst others, probably.
19442 *Steve Henson and Ben Laurie*
19444 * First cut of a cleanup for `apps/`. First the `ssleay` program is now named
19445 `openssl` and second, the shortcut symlinks for the `openssl <command>`
19446 are no longer created. This way we have a single and consistent command
19447 line interface `openssl <command>`, similar to `cvs <command>`.
19449 *Ralf S. Engelschall, Paul Sutton and Ben Laurie*
19451 * ca.c: move test for DSA keys inside #ifndef NO_DSA. Make pubkey
19452 BIT STRING wrapper always have zero unused bits.
19456 * Add CA.pl, perl version of CA.sh, add extended key usage OID.
19460 * Make the top-level INSTALL documentation easier to understand.
19464 * Makefiles updated to exit if an error occurs in a sub-directory
19465 make (including if user presses ^C) [Paul Sutton]
19467 * Make Montgomery context stuff explicit in RSA data structure.
19471 * Fix build order of pem and err to allow for generated pem.h.
19475 * Fix renumbering bug in X509_NAME_delete_entry().
19479 * Enhanced the err-ins.pl script so it makes the error library number
19480 global and can add a library name. This is needed for external ASN1 and
19481 other error libraries.
19485 * Fixed sk_insert which never worked properly.
19489 * Fix ASN1 macros so they can handle indefinite length constructed
19490 EXPLICIT tags. Some non standard certificates use these: they can now
19495 * Merged the various old/obsolete SSLeay documentation files (doc/xxx.doc)
19496 into a single doc/ssleay.txt bundle. This way the information is still
19497 preserved but no longer messes up this directory. Now it's new room for
19498 the new set of documentation files.
19500 *Ralf S. Engelschall*
19502 * SETs were incorrectly DER encoded. This was a major pain, because they
19503 shared code with SEQUENCEs, which aren't coded the same. This means that
19504 almost everything to do with SETs or SEQUENCEs has either changed name or
19505 number of arguments.
19507 *Ben Laurie, based on a partial fix by GP Jayan <gp@nsj.co.jp>*
19509 * Fix test data to work with the above.
19513 * Fix the RSA header declarations that hid a bug I fixed in 0.9.0b but
19514 was already fixed by Eric for 0.9.1 it seems.
19516 *Ben Laurie - pointed out by Ulf Möller <ulf@fitug.de>*
19518 * Autodetect FreeBSD3.
19522 * Fix various bugs in Configure. This affects the following platforms:
19526 unixware-2.0-pentium
19531 * Eliminate generated files from CVS. Reorder tests to regenerate files
19532 before they are needed.
19536 * Generate Makefile.ssl from Makefile.org (to keep CVS happy).
19540 ### Changes between 0.9.1b and 0.9.1c [23-Dec-1998]
19542 * Added OPENSSL_VERSION_NUMBER to crypto/crypto.h and
19543 changed SSLeay to OpenSSL in version strings.
19545 *Ralf S. Engelschall*
19547 * Some fixups to the top-level documents.
19551 * Fixed the nasty bug where rsaref.h was not found under compile-time
19552 because the symlink to include/ was missing.
19554 *Ralf S. Engelschall*
19556 * Incorporated the popular no-RSA/DSA-only patches
19557 which allow to compile an RSA-free SSLeay.
19559 *Andrew Cooke / Interrader Ldt., Ralf S. Engelschall*
19561 * Fixed nasty rehash problem under `make -f Makefile.ssl links`
19562 when "ssleay" is still not found.
19564 *Ralf S. Engelschall*
19566 * Added more platforms to Configure: Cray T3E, HPUX 11,
19568 *Ralf S. Engelschall, Beckmann <beckman@acl.lanl.gov>*
19570 * Updated the README file.
19572 *Ralf S. Engelschall*
19574 * Added various .cvsignore files in the CVS repository subdirs
19575 to make a "cvs update" really silent.
19577 *Ralf S. Engelschall*
19579 * Recompiled the error-definition header files and added
19580 missing symbols to the Win32 linker tables.
19582 *Ralf S. Engelschall*
19584 * Cleaned up the top-level documents;
19585 o new files: CHANGES and LICENSE
19586 o merged VERSION, HISTORY* and README* files a CHANGES.SSLeay
19587 o merged COPYRIGHT into LICENSE
19588 o removed obsolete TODO file
19589 o renamed MICROSOFT to INSTALL.W32
19591 *Ralf S. Engelschall*
19593 * Removed dummy files from the 0.9.1b source tree:
19594 crypto/asn1/x crypto/bio/cd crypto/bio/fg crypto/bio/grep crypto/bio/vi
19595 crypto/bn/asm/......add.c crypto/bn/asm/a.out crypto/dsa/f crypto/md5/f
19596 crypto/pem/gmon.out crypto/perlasm/f crypto/pkcs7/build crypto/rsa/f
19597 crypto/sha/asm/f crypto/threads/f ms/zzz ssl/f ssl/f.mak test/f
19598 util/f.mak util/pl/f util/pl/f.mak crypto/bf/bf_locl.old apps/f
19600 *Ralf S. Engelschall*
19602 * Added various platform portability fixes.
19606 * The Genesis of the OpenSSL rpject:
19607 We start with the latest (unreleased) SSLeay version 0.9.1b which Eric A.
19608 Young and Tim J. Hudson created while they were working for C2Net until
19611 *The OpenSSL Project*
19613 ### Changes between 0.9.0b and 0.9.1b [not released]
19615 * Updated a few CA certificates under certs/
19619 * Changed some BIGNUM api stuff.
19623 * Various platform ports: OpenBSD, Ultrix, IRIX 64bit, NetBSD,
19624 DGUX x86, Linux Alpha, etc.
19628 * New COMP library [crypto/comp/] for SSL Record Layer Compression:
19629 RLE (dummy implemented) and ZLIB (really implemented when ZLIB is
19634 * Add -strparse option to asn1pars program which parses nested
19637 *Dr Stephen Henson <shenson@bigfoot.com>*
19639 * Added "oid_file" to ssleay.cnf for "ca" and "req" programs.
19643 * DSA fix for "ca" program.
19647 * Added "-genkey" option to "dsaparam" program.
19651 * Added RIPE MD160 (rmd160) message digest.
19655 * Added -a (all) option to "ssleay version" command.
19659 * Added PLATFORM define which is the id given to Configure.
19663 * Added MemCheck_XXXX functions to crypto/mem.c for memory checking.
19667 * Extended the ASN.1 parser routines.
19671 * Extended BIO routines to support REUSEADDR, seek, tell, etc.
19675 * Added a BN_CTX to the BN library.
19679 * Fixed the weak key values in DES library
19683 * Changed API in EVP library for cipher aliases.
19687 * Added support for RC2/64bit cipher.
19691 * Converted the lhash library to the crypto/mem.c functions.
19695 * Added more recognized ASN.1 object ids.
19699 * Added more RSA padding checks for SSL/TLS.
19703 * Added BIO proxy/filter functionality.
19707 * Added extra_certs to SSL_CTX which can be used
19708 send extra CA certificates to the client in the CA cert chain sending
19709 process. It can be configured with SSL_CTX_add_extra_chain_cert().
19713 * Now Fortezza is denied in the authentication phase because
19714 this is key exchange mechanism is not supported by SSLeay at all.
19718 * Additional PKCS1 checks.
19722 * Support the string "TLSv1" for all TLS v1 ciphers.
19726 * Added function SSL_get_ex_data_X509_STORE_CTX_idx() which gives the
19727 ex_data index of the SSL context in the X509_STORE_CTX ex_data.
19731 * Fixed a few memory leaks.
19735 * Fixed various code and comment typos.
19739 * A minor bug in ssl/s3_clnt.c where there would always be 4 0
19740 bytes sent in the client random.
19742 *Edward Bishop <ebishop@spyglass.com>*
19746 [CVE-2023-1255]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-1255
19747 [CVE-2023-0466]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-0466
19748 [CVE-2023-0465]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-0465
19749 [CVE-2023-0464]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-0464
19750 [CVE-2023-0401]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-0401
19751 [CVE-2023-0286]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-0286
19752 [CVE-2023-0217]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-0217
19753 [CVE-2023-0216]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-0216
19754 [CVE-2023-0215]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-0215
19755 [CVE-2022-4450]: https://www.openssl.org/news/vulnerabilities.html#CVE-2022-4450
19756 [CVE-2022-4304]: https://www.openssl.org/news/vulnerabilities.html#CVE-2022-4304
19757 [CVE-2022-4203]: https://www.openssl.org/news/vulnerabilities.html#CVE-2022-4203
19758 [CVE-2022-3996]: https://www.openssl.org/news/vulnerabilities.html#CVE-2022-3996
19759 [CVE-2022-2274]: https://www.openssl.org/news/vulnerabilities.html#CVE-2022-2274
19760 [CVE-2022-2097]: https://www.openssl.org/news/vulnerabilities.html#CVE-2022-2097
19761 [CVE-2020-1971]: https://www.openssl.org/news/vulnerabilities.html#CVE-2020-1971
19762 [CVE-2020-1967]: https://www.openssl.org/news/vulnerabilities.html#CVE-2020-1967
19763 [CVE-2019-1563]: https://www.openssl.org/news/vulnerabilities.html#CVE-2019-1563
19764 [CVE-2019-1559]: https://www.openssl.org/news/vulnerabilities.html#CVE-2019-1559
19765 [CVE-2019-1552]: https://www.openssl.org/news/vulnerabilities.html#CVE-2019-1552
19766 [CVE-2019-1551]: https://www.openssl.org/news/vulnerabilities.html#CVE-2019-1551
19767 [CVE-2019-1549]: https://www.openssl.org/news/vulnerabilities.html#CVE-2019-1549
19768 [CVE-2019-1547]: https://www.openssl.org/news/vulnerabilities.html#CVE-2019-1547
19769 [CVE-2019-1543]: https://www.openssl.org/news/vulnerabilities.html#CVE-2019-1543
19770 [CVE-2018-5407]: https://www.openssl.org/news/vulnerabilities.html#CVE-2018-5407
19771 [CVE-2018-0739]: https://www.openssl.org/news/vulnerabilities.html#CVE-2018-0739
19772 [CVE-2018-0737]: https://www.openssl.org/news/vulnerabilities.html#CVE-2018-0737
19773 [CVE-2018-0735]: https://www.openssl.org/news/vulnerabilities.html#CVE-2018-0735
19774 [CVE-2018-0734]: https://www.openssl.org/news/vulnerabilities.html#CVE-2018-0734
19775 [CVE-2018-0733]: https://www.openssl.org/news/vulnerabilities.html#CVE-2018-0733
19776 [CVE-2018-0732]: https://www.openssl.org/news/vulnerabilities.html#CVE-2018-0732
19777 [CVE-2017-3738]: https://www.openssl.org/news/vulnerabilities.html#CVE-2017-3738
19778 [CVE-2017-3737]: https://www.openssl.org/news/vulnerabilities.html#CVE-2017-3737
19779 [CVE-2017-3736]: https://www.openssl.org/news/vulnerabilities.html#CVE-2017-3736
19780 [CVE-2017-3735]: https://www.openssl.org/news/vulnerabilities.html#CVE-2017-3735
19781 [CVE-2017-3733]: https://www.openssl.org/news/vulnerabilities.html#CVE-2017-3733
19782 [CVE-2017-3732]: https://www.openssl.org/news/vulnerabilities.html#CVE-2017-3732
19783 [CVE-2017-3731]: https://www.openssl.org/news/vulnerabilities.html#CVE-2017-3731
19784 [CVE-2017-3730]: https://www.openssl.org/news/vulnerabilities.html#CVE-2017-3730
19785 [CVE-2016-7055]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-7055
19786 [CVE-2016-7054]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-7054
19787 [CVE-2016-7053]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-7053
19788 [CVE-2016-7052]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-7052
19789 [CVE-2016-6309]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-6309
19790 [CVE-2016-6308]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-6308
19791 [CVE-2016-6307]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-6307
19792 [CVE-2016-6306]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-6306
19793 [CVE-2016-6305]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-6305
19794 [CVE-2016-6304]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-6304
19795 [CVE-2016-6303]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-6303
19796 [CVE-2016-6302]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-6302
19797 [CVE-2016-2183]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2183
19798 [CVE-2016-2182]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2182
19799 [CVE-2016-2181]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2181
19800 [CVE-2016-2180]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2180
19801 [CVE-2016-2179]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2179
19802 [CVE-2016-2178]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2178
19803 [CVE-2016-2177]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2177
19804 [CVE-2016-2176]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2176
19805 [CVE-2016-2109]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2109
19806 [CVE-2016-2107]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2107
19807 [CVE-2016-2106]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2106
19808 [CVE-2016-2105]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-2105
19809 [CVE-2016-0800]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-0800
19810 [CVE-2016-0799]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-0799
19811 [CVE-2016-0798]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-0798
19812 [CVE-2016-0797]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-0797
19813 [CVE-2016-0705]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-0705
19814 [CVE-2016-0702]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-0702
19815 [CVE-2016-0701]: https://www.openssl.org/news/vulnerabilities.html#CVE-2016-0701
19816 [CVE-2015-3197]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-3197
19817 [CVE-2015-3196]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-3196
19818 [CVE-2015-3195]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-3195
19819 [CVE-2015-3194]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-3194
19820 [CVE-2015-3193]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-3193
19821 [CVE-2015-1793]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-1793
19822 [CVE-2015-1792]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-1792
19823 [CVE-2015-1791]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-1791
19824 [CVE-2015-1790]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-1790
19825 [CVE-2015-1789]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-1789
19826 [CVE-2015-1788]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-1788
19827 [CVE-2015-1787]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-1787
19828 [CVE-2015-0293]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0293
19829 [CVE-2015-0291]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0291
19830 [CVE-2015-0290]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0290
19831 [CVE-2015-0289]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0289
19832 [CVE-2015-0288]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0288
19833 [CVE-2015-0287]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0287
19834 [CVE-2015-0286]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0286
19835 [CVE-2015-0285]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0285
19836 [CVE-2015-0209]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0209
19837 [CVE-2015-0208]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0208
19838 [CVE-2015-0207]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0207
19839 [CVE-2015-0206]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0206
19840 [CVE-2015-0205]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0205
19841 [CVE-2015-0204]: https://www.openssl.org/news/vulnerabilities.html#CVE-2015-0204
19842 [CVE-2014-8275]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-8275
19843 [CVE-2014-5139]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-5139
19844 [CVE-2014-3572]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3572
19845 [CVE-2014-3571]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3571
19846 [CVE-2014-3570]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3570
19847 [CVE-2014-3569]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3569
19848 [CVE-2014-3568]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3568
19849 [CVE-2014-3567]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3567
19850 [CVE-2014-3566]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3566
19851 [CVE-2014-3513]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3513
19852 [CVE-2014-3512]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3512
19853 [CVE-2014-3511]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3511
19854 [CVE-2014-3510]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3510
19855 [CVE-2014-3509]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3509
19856 [CVE-2014-3508]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3508
19857 [CVE-2014-3507]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3507
19858 [CVE-2014-3506]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3506
19859 [CVE-2014-3505]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3505
19860 [CVE-2014-3470]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-3470
19861 [CVE-2014-0224]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-0224
19862 [CVE-2014-0221]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-0221
19863 [CVE-2014-0195]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-0195
19864 [CVE-2014-0160]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-0160
19865 [CVE-2014-0076]: https://www.openssl.org/news/vulnerabilities.html#CVE-2014-0076
19866 [CVE-2013-6450]: https://www.openssl.org/news/vulnerabilities.html#CVE-2013-6450
19867 [CVE-2013-4353]: https://www.openssl.org/news/vulnerabilities.html#CVE-2013-4353
19868 [CVE-2013-0169]: https://www.openssl.org/news/vulnerabilities.html#CVE-2013-0169
19869 [CVE-2013-0166]: https://www.openssl.org/news/vulnerabilities.html#CVE-2013-0166
19870 [CVE-2012-2686]: https://www.openssl.org/news/vulnerabilities.html#CVE-2012-2686
19871 [CVE-2012-2333]: https://www.openssl.org/news/vulnerabilities.html#CVE-2012-2333
19872 [CVE-2012-2110]: https://www.openssl.org/news/vulnerabilities.html#CVE-2012-2110
19873 [CVE-2012-0884]: https://www.openssl.org/news/vulnerabilities.html#CVE-2012-0884
19874 [CVE-2012-0050]: https://www.openssl.org/news/vulnerabilities.html#CVE-2012-0050
19875 [CVE-2012-0027]: https://www.openssl.org/news/vulnerabilities.html#CVE-2012-0027
19876 [CVE-2011-4619]: https://www.openssl.org/news/vulnerabilities.html#CVE-2011-4619
19877 [CVE-2011-4577]: https://www.openssl.org/news/vulnerabilities.html#CVE-2011-4577
19878 [CVE-2011-4576]: https://www.openssl.org/news/vulnerabilities.html#CVE-2011-4576
19879 [CVE-2011-4109]: https://www.openssl.org/news/vulnerabilities.html#CVE-2011-4109
19880 [CVE-2011-4108]: https://www.openssl.org/news/vulnerabilities.html#CVE-2011-4108
19881 [CVE-2011-3210]: https://www.openssl.org/news/vulnerabilities.html#CVE-2011-3210
19882 [CVE-2011-3207]: https://www.openssl.org/news/vulnerabilities.html#CVE-2011-3207
19883 [CVE-2011-0014]: https://www.openssl.org/news/vulnerabilities.html#CVE-2011-0014
19884 [CVE-2010-4252]: https://www.openssl.org/news/vulnerabilities.html#CVE-2010-4252
19885 [CVE-2010-4180]: https://www.openssl.org/news/vulnerabilities.html#CVE-2010-4180
19886 [CVE-2010-3864]: https://www.openssl.org/news/vulnerabilities.html#CVE-2010-3864
19887 [CVE-2010-1633]: https://www.openssl.org/news/vulnerabilities.html#CVE-2010-1633
19888 [CVE-2010-0740]: https://www.openssl.org/news/vulnerabilities.html#CVE-2010-0740
19889 [CVE-2010-0433]: https://www.openssl.org/news/vulnerabilities.html#CVE-2010-0433
19890 [CVE-2009-4355]: https://www.openssl.org/news/vulnerabilities.html#CVE-2009-4355
19891 [CVE-2009-3555]: https://www.openssl.org/news/vulnerabilities.html#CVE-2009-3555
19892 [CVE-2009-3245]: https://www.openssl.org/news/vulnerabilities.html#CVE-2009-3245
19893 [CVE-2009-1386]: https://www.openssl.org/news/vulnerabilities.html#CVE-2009-1386
19894 [CVE-2009-1379]: https://www.openssl.org/news/vulnerabilities.html#CVE-2009-1379
19895 [CVE-2009-1378]: https://www.openssl.org/news/vulnerabilities.html#CVE-2009-1378
19896 [CVE-2009-1377]: https://www.openssl.org/news/vulnerabilities.html#CVE-2009-1377
19897 [CVE-2009-0789]: https://www.openssl.org/news/vulnerabilities.html#CVE-2009-0789
19898 [CVE-2009-0591]: https://www.openssl.org/news/vulnerabilities.html#CVE-2009-0591
19899 [CVE-2009-0590]: https://www.openssl.org/news/vulnerabilities.html#CVE-2009-0590
19900 [CVE-2008-5077]: https://www.openssl.org/news/vulnerabilities.html#CVE-2008-5077
19901 [CVE-2008-1678]: https://www.openssl.org/news/vulnerabilities.html#CVE-2008-1678
19902 [CVE-2008-1672]: https://www.openssl.org/news/vulnerabilities.html#CVE-2008-1672
19903 [CVE-2008-0891]: https://www.openssl.org/news/vulnerabilities.html#CVE-2008-0891
19904 [CVE-2007-5135]: https://www.openssl.org/news/vulnerabilities.html#CVE-2007-5135
19905 [CVE-2007-4995]: https://www.openssl.org/news/vulnerabilities.html#CVE-2007-4995
19906 [CVE-2006-4343]: https://www.openssl.org/news/vulnerabilities.html#CVE-2006-4343
19907 [CVE-2006-4339]: https://www.openssl.org/news/vulnerabilities.html#CVE-2006-4339
19908 [CVE-2006-3738]: https://www.openssl.org/news/vulnerabilities.html#CVE-2006-3738
19909 [CVE-2006-2940]: https://www.openssl.org/news/vulnerabilities.html#CVE-2006-2940
19910 [CVE-2006-2937]: https://www.openssl.org/news/vulnerabilities.html#CVE-2006-2937
19911 [CVE-2005-2969]: https://www.openssl.org/news/vulnerabilities.html#CVE-2005-2969
19912 [CVE-2004-0112]: https://www.openssl.org/news/vulnerabilities.html#CVE-2004-0112
19913 [CVE-2004-0079]: https://www.openssl.org/news/vulnerabilities.html#CVE-2004-0079
19914 [CVE-2003-0851]: https://www.openssl.org/news/vulnerabilities.html#CVE-2003-0851
19915 [CVE-2003-0545]: https://www.openssl.org/news/vulnerabilities.html#CVE-2003-0545
19916 [CVE-2003-0544]: https://www.openssl.org/news/vulnerabilities.html#CVE-2003-0544
19917 [CVE-2003-0543]: https://www.openssl.org/news/vulnerabilities.html#CVE-2003-0543
19918 [CVE-2003-0078]: https://www.openssl.org/news/vulnerabilities.html#CVE-2003-0078
19919 [CVE-2002-0659]: https://www.openssl.org/news/vulnerabilities.html#CVE-2002-0659
19920 [CVE-2002-0657]: https://www.openssl.org/news/vulnerabilities.html#CVE-2002-0657
19921 [CVE-2002-0656]: https://www.openssl.org/news/vulnerabilities.html#CVE-2002-0656
19922 [CVE-2002-0655]: https://www.openssl.org/news/vulnerabilities.html#CVE-2002-0655