- Jun 29, 2017
-
-
Richard Levitte authored
Containers are objects that are containers for a bunch of other objects with types we recognise but aren't readable in a stream. Such containers are read and parsed, and their content is cached, to be served one object at a time. This extends the FILE_HANDLER type to include a function to destroy the cache and a function to simulate the EOF check. Reviewed-by:
Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/3542)
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
This command can be used to view the contents of any supported type of information fetched from a URI, and output them in PEM format. Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
This is needed for the upcoming "file" scheme STORE loader. Reviewed-by:
-
Richard Levitte authored
This is needed for the upcoming "file" scheme STORE loader. Reviewed-by:
-
Richard Levitte authored
This STORE module adds the following functionality: - A function OSSL_STORE_open(), OSSL_STORE_load() and OSSL_STORE_close() that accesses a URI and helps loading the supported objects (PKEYs, CERTs and CRLs for the moment) from it. - An opaque type OSSL_STORE_INFO that holds information on each loaded object. - A few functions to retrieve desired data from a OSSL_STORE_INFO reference. - Functions to register and unregister loaders for different URI schemes. This enables dynamic addition of loaders from applications or from engines. Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Matt Caswell authored
Reviewed-by:
Rich Salz <rsalz@openssl.org> (Merged from https://github.com/openssl/openssl/pull/3782)
-
Matt Caswell authored
Reviewed-by:
-
Matt Caswell authored
There aren't any test vectors for this, so all we do is test that both sides of the communication create the same result for different protocol versions. Reviewed-by:
-
Matt Caswell authored
Fixes #3680 Reviewed-by:
-
- Jun 28, 2017
-
-
Greg Zaverucha authored
Fix memory leak in sample encryption code and check return value of fopen. CLA: trivial Signed-off-by:
Greg Zaverucha <gregz@microsoft.com> Reviewed-by:
Paul Dale <paul.dale@oracle.com> Reviewed-by:
Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/3790)
-
Richard Levitte authored
Windows doesn't provide random(). In this particular case, our requirements on the quality of randomness isn't high, so we don't need to care how good randomness rand() does or doesn't provide. Fixes #3778 Reviewed-by:
-
Todd Short authored
Properly copy ext.alpn_session in ssl_session_dup() Use OPENSSL_strndup() as that's used in ssl_asn1.c Reviewed-by:
Ben Kaduk <kaduk@mit.edu> (Merged from https://github.com/openssl/openssl/pull/3770)
-
Richard Levitte authored
uitest.o depends on apps.h which depends on progs.h, which is dynamically generated, so we need to explicitely add a dependency between uitest.o and progs.h for the latter to be generated in time. Fixed #3793 Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
The callback we're wrapping around may or may not return a NUL-terminated string. Let's ensure it is. Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
The BSD cryptodev.h doesn't have things like COP_FLAG_WRITE_IV and COP_FLAG_UPDATE. In that case, we need to implement that functionality ourselves. Reviewed-by:
-
Richard Levitte authored
Based on cryptodev-linux Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
- Jun 27, 2017
-
-
Rich Salz authored
Reviewed-by:
-
Benjamin Kaduk authored
Commit db17e43d added the function but would improperly report success if the underlying dup operation failed. Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
To make sure that our symbols don't clash with other libraries, we claim the namespaces OSSL and OPENSSL. Because C doesn't provide namespaces, the only solution is to have them as prefixes on symbols, thus we allow OSSL_ and OPENSSL_ as prefixes. These namespace prefixes are optional for the foreseeable future, and will only be used for new modules as needed on a case by case basis, until further notice. For extra safety, there's an added requirement that module names - apart from the namespace prefix - be at least 2 characters long. Reviewed-by:
-
- Jun 26, 2017
-
-
Rich Salz authored
Breaks djgpp, masks a common kernel function name. Thanks to Gisle Vanem for pointing this out. Reviewed-by:
-
Paul Yang authored
To make it consistent in the code base Reviewed-by:
Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from https://github.com/openssl/openssl/pull/3749)
-
Paul Yang authored
BIO_sock_init returns '-1' on error, not '0', so it's needed to check explicitly istead of using '!'. Reviewed-by:
Tim Hudson <tjh@openssl.org> Reviewed-by:
-
Paul Yang authored
As well as a coding style nit is fixed. Reviewed-by:
-
- Jun 25, 2017
-
-
Richard Levitte authored
This function is undocumented, but similarly named functions (such as 'curl_global_cleanup') are documented as internals that should not be called by scripts. Fixes #3765 Reviewed-by:
-
Benjamin Kaduk authored
Reviewed-by:
-
Benjamin Kaduk authored
Test for each of DSA, SHA1, and SHA224. Use the symbolic names for SignatureScheme comparisons just added. Reviewed-by:
-
Benjamin Kaduk authored
Reviewed-by:
-
Benjamin Kaduk authored
Put them into the TLSProxy::Message namespace along with the extension type constants. Reviewed-by:
-
Benjamin Kaduk authored
In draft-ietf-tls-tls13-20 Appendix B we find that: This section describes protocol types and constants. Values listed as _RESERVED were used in previous versions of TLS and are listed here for completeness. TLS 1.3 implementations MUST NOT send them but might receive them from older TLS implementations. Similarly, in section 4.2.3 we see: Legacy algorithms Indicates algorithms which are being deprecated because they use algorithms with known weaknesses, specifically SHA-1 which is used in this context with either with RSA using RSASSA-PKCS1-v1_5 or ECDSA. These values refer solely to signatures which appear in certificates (see Section 4.4.2.2) and are not defined for use in signed TLS handshake messages. Endpoints SHOULD NOT negotiate these algorithms but are permitted to do so solely for backward compatibility. Clients offering these values MUST list them as the lowest priority (listed after all other algorithms in SignatureSchemeList). TLS 1.3 servers MUST NOT offer a SHA-1 signed certificate unless no valid certificate chain can be produced without it (see Section 4.4.2.2). However, we are currently sending the SHA2-based DSA signature schemes and many SHA1-based schemes, which is in contradiction with the specification. Because TLS 1.3 support will appear in OpenSSL 1.1, we are bound by stability requirements to continue to offer the DSA signature schemes and the deprecated hash algorithms. at least until OpenSSL 1.2. However, for pure TLS 1.3 clients that do not offer lower TLS versions, we can be compliant. Do so, and leave a note to revisit the issue when we are permitted to break with sacred historical tradition. Reviewed-by:
-
- Jun 24, 2017
-
-
Andy Polyakov authored
Curiously enough out-of-order Silvermont benefited most from optimization, 33%. [Originally mentioned "anomaly" turned to be misreported frequency scaling problem. Correct results were collected under older kernel.] Reviewed-by:
-
Andy Polyakov authored
Reviewed-by:
-
- Jun 23, 2017
-
-
Matt Caswell authored
[extended tests] Reviewed-by:
-
