- Mar 19, 2016
-
-
Richard Levitte authored
Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Make Configure write @disablables to configdata.pm and have apps/progs.pl use that data. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
The check was erroneously inversed Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
In crypto, buildinf.h depends on ../configdata.pm, not ./configdata.pm Reviewed-by: Rich Salz <rsalz@openssl.org>
-
- Mar 18, 2016
-
-
Richard Levitte authored
Instead of relying on the '-nt' test operator, which doesn't exist everywhere, use find's '-newer' to find out if any of the known .d files is newer than Makefile. Closes RT#4444 Reviewed-by: Andy Polyakov <appro@openssl.org>
-
Richard Levitte authored
Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Matt Caswell authored
Numerous fixes for no-des. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Matt Caswell authored
A few places in s_client needed some OPENSSL_NO_DTLS guards which fixes no-dgram. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Matt Caswell authored
The no-deprecated build was failing because afalg was relying on a transitive include that does not exist in a no-deprecated build. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Matt Caswell authored
There were a couple of CMAC references without OPENSSL_NO_CMAC guards. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Reviewed-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Emilia Käsper <emilia@openssl.org>
-
Richard Levitte authored
$? in perl gets the status value from wait(2), which is a word with the exit code in the upper half and the number of a raised signal in the lower half. OpenSSL::Test::run() ignored the signal half up until now. With this change, we recalculate an exit code the same way the Unix shells do, using this formula: ($? & 0x7f) ? ($? & 0x7f)|0x80 : ($? >> 8); Reviewed-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Emilia Käsper <emilia@openssl.org>
-
Rich Salz authored
Moved doc/standards.txt to the web. Reviewed-by: Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
Compiling on Windows with no-hw was resulting in unresolved symbols in the padlock engine. Reviewed-by: Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
mkdef.pl was not detecting no-comp functions. This updates the header file so that mkdef.pl detects that no-comp applies, and the functions are marked accordingly. Reviewed-by: Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
The CMS test uses some RC2 keys which should be skipped if the RC2 is disabled. Reviewed-by: Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
OCB is AEAD capable but was not marked as such with the EVP_CIPH_FLAG_AEAD_CIPHER flag. Reviewed-by: Andy Polyakov <appro@openssl.org>
-
Matt Caswell authored
If a call to EVP_DecryptUpdate fails then a memory leak could occur. Ensure that the memory is freed appropriately. Issue reported by Guido Vranken. Reviewed-by: Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
There is a potential double free in EVP_DigestInit_ex. This is believed to be reached only as a result of programmer error - but we should fix it anyway. Issue reported by Guido Vranken. Reviewed-by: Richard Levitte <levitte@openssl.org>
-
Rich Salz authored
Reviewed-by: Dr. Stephen Henson <steve@openssl.org>
-
Conrado Porto Lopes Gouvêa authored
Add note about when EVP_CIPHER_CTX_set_padding should be called. Reviewed-by: Dr. Stephen Henson <steve@openssl.org>
-
- Mar 17, 2016
-
-
Richard Levitte authored
Don't refer to INSTALL files that don't exist any more. Make it clear that the libssl and libcrypto libraries may be named differently on different platforms. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Document them as well Reviewed-by: Andy Polyakov <appro@openssl.org>
-
Rich Salz authored
Reviewed-by: Richard Levitte <levitte@openssl.org>
-
Richard Levitte authored
With all the config changes, mk1mf is broken on Windows. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Reviewed-by: Andy Polyakov <appro@openssl.org>
-
Richard Levitte authored
On Windows, we set INSTALLTOP to default as follows: VC-WIN32: PREFIX: %ProgramFiles(x86)%\OpenSSL OPENSSLDIR: %CommonProgramFiles(x86)%\SSL VC-WIN64*: PREFIX: %ProgramW6432%\OpenSSL OPENSSLDIR: %CommonProgramW6432%\SSL Should those environment variables be missing, the following is used as fallback: PREFIX: %ProgramFiles%\OpenSSL OPENSSLDIR: %CommonProgramFiles%\SSL Reviewed-by: Andy Polyakov <appro@openssl.org>
-
Viktor Dukhovni authored
The TLSv1.0 form is retained for reporting the first protocol version that supports a given cupher. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Rich Salz authored
Reviewed-by: Richard Levitte <levitte@openssl.org>
-
Richard Levitte authored
Borland C++ 4.5 is very old and our "support" for it is already non-existent, we might as well remove it. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Dr. Stephen Henson authored
Reviewed-by: Richard Levitte <levitte@openssl.org>
-
Richard Levitte authored
This is a living document, everyone is encouraged to add to it. Implementation details as well as broader implementation philosophy has a place here. I'm starting with documentation of the how conditions in build.info files are treated. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
This is only enabled when the environment variable CONFIGURE_DEBUG_BUILDINFO is defined. This will cause every line in every build.info file to be displayed, along with the content of the skip stack before and after parsing. This can be a very powerful tool to see that all conditions are working as expected. Reviewed-by: Rich Salz <rsalz@openssl.org>
-
Dr. Stephen Henson authored
Reviewed-by: Tim Hudson <tjh@openssl.org>
-
Richard Levitte authored
In most builds, we can assume that engines live in the build tree subdirectory "engines". This was hard coded into the tests that use the engine ossltest. However, that hard coding is tedious, it would need to be done in every test recipe, and it's an incorrect assumption in some cases. This change has us play it safe and let the build files tell the testing framework where the engines are. Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
-
Richard Levitte authored
Reviewed-by: Rich Salz <rsalz@openssl.org>
-