- Sep 20, 2018
-
-
Richard Levitte authored
It turns out to be detrimental on some file systems that may or may not be case sensitive (such as NTFS, which has a case sensitive mode). Fixes #7172 Reviewed-by:
Tim Hudson <tjh@openssl.org> (Merged from https://github.com/openssl/openssl/pull/7172)
-
Richard Levitte authored
These both indicate that the file descriptor we're trying to use as a terminal isn't, in fact, a terminal. Fixes #7271 Reviewed-by:
Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com> (Merged from https://github.com/openssl/openssl/pull/7272)
-
- Sep 19, 2018
-
-
Benjamin Kaduk authored
Historically SSL_CTX_set_ssl_version() has reset the cipher list to the default. Splitting TLS 1.3 ciphers to be tracked separately caused a behavior change, in that TLS 1.3 cipher configuration was preserved across calls to SSL_CTX_set_ssl_version(). To restore commensurate behavior with the historical behavior, set the ciphersuites to the default as well as setting the cipher list to the default. Closes: #7226 Reviewed-by:
Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/7270)
-
Pauli authored
Reviewed-by:
Nicola Tuveri <nic.tuv@gmail.com> (Merged from https://github.com/openssl/openssl/pull/7249)
-
- Sep 18, 2018
-
-
Dr. Matthias St. Pierre authored
Fixes #7252 Reviewed-by:
Paul Dale <paul.dale@oracle.com> (Merged from https://github.com/openssl/openssl/pull/7253)
-
Tobias Nießen authored
This commit reuses a variable instead of reevaluating the expression and updates an outdated comment in the EVP test. Reviewed-by:
Richard Levitte <levitte@openssl.org> Reviewed-by:
-
- Sep 17, 2018
-
-
David Makepeace authored
Reviewed-by:
-
Pauli authored
Specifically, include e_os.h to pick up alloca definition for WIN32. Reviewed-by:
-
- Sep 16, 2018
-
-
Pauli authored
coexist. Reviewed-by:
-
Pauli authored
The latter causes problems when complex.h is #included. Reviewed-by:
-
Matt Eaton authored
Fixed a minor typo while reading the documentation. I agree that this contribution is trivial can be freely used. CLA: trivial Reviewed-by:
Kurt Roeckx <kurt@roeckx.be> (Merged from https://github.com/openssl/openssl/pull/7221)
-
Kurt Roeckx authored
Reviewed-by:Ben Kaduk <kaduk@mit.edu> GH: #7188
-
- Sep 15, 2018
-
-
Richard Levitte authored
It simply isn't available on older versions. Issue submitted by Mark Daniels Fixes #7229 Reviewed-by:
-
- Sep 14, 2018
-
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
With the change to have separate object files by intent, VMS name mangling gets done differently. While we previously had that for libraries only, we must now turn that on generally for our programs, because some of them depend in internal libraries where mangled names are all that there is. Dynamic modules are still built with non-mangled names, which is good enough to show that it's possible to build with our public libraries using our public headers. Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
- Sep 13, 2018
-
-
Paul Yang authored
Reviewed-by:
Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from https://github.com/openssl/openssl/pull/7209)
-
Matt Caswell authored
-early_data is not compatible with -www, -WWW, -HTTP or -rev. Fixes #7200 Reviewed-by:
-
Matt Caswell authored
Caused a compilation failure in some environments Fixes #7204 Reviewed-by:
Viktor Dukhovni <viktor@openssl.org> (Merged from https://github.com/openssl/openssl/pull/7205)
-
- Sep 12, 2018
-
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
The possibility to do this was killed when we started producing object file names with encoded intention (and possibly different builds), and leads to build errors. With that, 'libobj2shlib' is renamed to 'obj2shlib' to reflect this design change. The old name is still used if the new one isn't available, for the sake of backward compatibility. Reviewed-by:
-
Dr. Matthias St. Pierre authored
The new DRBG API added the aforementioned #define. However, it is used internally only and having it defined publicly does not serve any purpose except causing potential version compatibility problems. Fixes #7182 Reviewed-by:
-
Bernd Edlinger authored
Fixes: #7161 (hopefully) Reviewed-by:
-
Brian 'geeknik' Carpenter authored
Fixes a minor typo that would cause the linker to complain about not finding -lFuzzer CLA: trivial Reviewed-by:
-
Viktor Szakats authored
- fix to use secure URL in generated Windows resources - fix a potentially uninitialized variable - fix an unused variable warning CLA: trivial Reviewed-by:
-
Richard Levitte authored
Fixes #7186 Reviewed-by:
-
- Sep 11, 2018
-
-
Richard Levitte authored
This is in preparation for having separate CFLAGS variables for static and for shared library builds. Reviewed-by:
-
Richard Levitte authored
This will allow to have different object files for different products, even if they share the same source code, and possibly different builds for those different object files. For example, one can have something like this: SOURCES[libfoo]=cookie.c INCLUDES[libfoo]=include/foo SOURCES[libbar]=cookie.c INCLUDES[libbar]=include/bar This would mean that the object files and libraries would be build somewhat like this: $(CC) -Iinclude/foo -o libfoo-lib-cookie.o cookie.c $(AR) $(ARFLAGS) libfoo.a libfoo-lib-cookie.o $(CC) -Iinclude/bar -o libbar-lib-cookie.o cookie.c $(AR) $(ARFLAGS) libbar.a libbar-lib-cookie.o Reviewed-by: -
Richard Levitte authored
Instead, use the include settings from the products later in the process, making it possible to have different includes for two different libraries that share the same source code. Reviewed-by:
-
Pauli authored
limit is ever reached. This is a FIPS 140-2 requirement from IG A.5 "Key/IV Pair Uniqueness Requirements from SP 800-38D". Reviewed-by:
-
Pauli authored
Add support for HMAC over any evp supported digest. Reviewed-by:
-
Pauli authored
keys. Reviewed-by:
-
Pauli authored
Add a check that the two keys used for AES-XTS are different. One test case uses the same key for both of the AES-XTS keys. This causes a failure under FIP 140-2 IG A.9. Mark the test as returning a failure. Reviewed-by:
-
Richard Levitte authored
The OMC hasn't yet decided what the next release version will be, but it's at least going to 1.1.2, so we set that value for the moment. Reviewed-by:
-
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
Reviewed-by:
-
Richard Levitte authored
Since the SSL code started using RSA_NO_PADDING, the CAPI engine became unusable. This change fixes that. Fixes #7131 Reviewed-by:
-
- Sep 10, 2018
-
-
Matt Caswell authored
Found by Coverity Reviewed-by:
-
Matt Caswell authored
Fixes a Coverity complaint. Reviewed-by:
-
