- 12 Feb, 2016 15 commits
-
-
Andy Polyakov authored
Not all git versions understand **/Makefile, but all recognize that filename without any path applies to all directories. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Andy Polyakov authored
Contemporary Xcode gcc is a front-end to clang, so that explicit gcc build is actually redundant on MacOS X. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Rich Salz authored
Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Andy Polyakov authored
RT#4237 Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Richard Levitte authored
It's nearly impossible to determine what goes wrong in the tests running there without this. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
If the environment variable HARNESS_ACTIVE isn't defined or HARNESS_VERBOSE is defined, it's probable that lots of output is desired. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
The logging that was performed in OpenSSL::Test was initially set up as a means not to let messages that test programs write to STDERR get displayed when a test isn't running in verbose mode. However, the way it was implemented, it meant that those messages were never displayed, and you had to look in a test log. This also meant that output to STDERR and output to STDOUT got broken apart, which isn't optimal. So, we remove the whole test log file implementation, and instead, we're sending STDERR to the null device unless one of these conditions apply: - the test recipe already redirects stderr. Just let it. - the environment variable HARNESS_ACTIVE is undefined, meaning the recipe is run directly as a perl script instead of being harnessed by Test::Harness - the environment variable HARNESS_VERBOSE is set. Getting a full log of the tests now becomes as simple as this: HARNESS_VERBOSE=yes make test 2>&1 | tee tests.log Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
The actual bug with current getnameinfo() on VMS is not that it puts gibberish in the service buffer, but that it doesn't touch it at all. The gibberish we dealt with before was simply stuff that happened to be on the stack. It's better to initialise the service buffer properly (with the empty string) and check if it's still an empty string after the getnameinfo() call, and fill it with the direct numerical translation of the raw port if that's the case. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
On VMS, periods in directory names weren't allowed. To counter that, unpackers such as VMSTAR convert periods in directory names to underscores. We need to count that in and add an alternative library path for Text::Template. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Emilia Kasper authored
Change the default keysize to 2048 bits, and the minimum to 512 bits. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
In the previous commit to change all chomp to a more flexible regexp, Configure was forgotten. This completes the change. Reviewed-by:
Andy Polyakov <appro@openssl.org>
-
Matt Caswell authored
The recent removal of static ECDH broke the enable-ssl-trace compilation. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Richard Levitte authored
Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
apps/progs.pl counted on the caller to provide the exact command files. The unified build doesn't have that knowledge, and the easier and more flexible thing to do is to feed it all the apps/*.c files and let it figure out the command names by looking inside (looking for /int ([a-z0-9][a-z0-9_]*)_main\(int argc,/). Also, add it to the generate command, since it's a versioned file. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
- 11 Feb, 2016 25 commits
-
-
Dr. Stephen Henson authored
Reviewed-by:
Viktor Dukhovni <viktor@openssl.org>
-
Richard Levitte authored
Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
Once upon a time, there was chop, which somply chopped off the last character of $_ or a given variable, and it was used to take off the EOL character (\n) of strings. ... but then, you had to check for the presence of such character. So came chomp, the better chop which checks for \n before chopping it off. And this worked well, as long as Perl made internally sure that all EOLs were converted to \n. These days, though, there seems to be a mixture of perls, so lines from files in the "wrong" environment might have \r\n as EOL, or just \r (Mac OS, unless I'm misinformed). So it's time we went for the more generic variant and use s|\R$||, the better chomp which recognises all kinds of known EOLs and chops them off. A few chops were left alone, as they are use as surgical tools to remove one last slash or one last comma. NOTE: \R came with perl 5.10.0. It means that from now on, our scripts will fail with any older version. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Dr. Stephen Henson authored
Reviewed-by:
Viktor Dukhovni <viktor@openssl.org>
-
Dr. Stephen Henson authored
Remove support for static ECDH ciphersuites. They require ECDH keys in certificates and don't support forward secrecy. Reviewed-by:
Viktor Dukhovni <viktor@openssl.org>
-
Andy Polyakov authored
RT#3885 Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Andy Polyakov authored
Trouble is that LINK variable assignment in make-file interferes with LINK environment variable, which can be used to modify Microsoft's LINK.EXE behaviour. RT#4289 Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Andy Polyakov authored
Reviewed-by:
Viktor Dukhovni <viktor@openssl.org>
-
Andy Polyakov authored
Reviewed-by:
Tim Hudson <tjh@openssl.org>
-
Richard Levitte authored
Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Dr. Stephen Henson authored
Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Viktor Dukhovni authored
Commit 7823d792 added DEFINE_LHASH_OF to a C source file. DEFINE_LHASH_OF() and DEFINE_STACK_OF() must be used only in header files to avoid clang warnings for unused static-inline functions. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Rich Salz authored
Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Rich Salz authored
To enable heartbeats for DTLS, configure with enable-heartbeats. Heartbeats for TLS have been completely removed. This addresses RT 3647 Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Rich Salz authored
Add utility macros REF_ASSERT_NOT and REF_PRINT_COUNT This is also RT 4181 Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Toshikuni Fukaya authored
Updated for 1.1 by Rich Salz Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Rich Salz authored
Valgrind complains about using unitialized memory. So call OPENSSL_zalloc, not malloc. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Richard Levitte authored
With this, Cygwin and Mingw builds stand a much better chance to be able to build outside of the source tree with the unified build. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
On Windows POSIX layers, two files are produced for a shared library, there's {shlibname}.dll and there's the import library {libname}.dll.a On some/most Unix platforms, a {shlibname}.{sover}.so and a symlink {shlibname}.so are produced. For each of them, unix-Makefile.tmpl was entirely consistent on which to have as a target when building a shared library or which to use as dependency. This change clears this up and makes it consistent, we use the simplest form possible, {lib}.dll.a on Windows POSIX layers and {shlibname}.so on Unix platforms. No exception. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Dr. Stephen Henson authored
PR#4246 and PR#4266 Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Dr Stephen Henson authored
Some keys are attached to the full RSA CSP which doesn't support SHA2 algorithms: uses the AES CSP if present. Reviewed-by:
Tim Hudson <tjh@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
If someone runs a mixed unixmake / unified environment (the unified build tree would obviously be out of the source tree), the unified build will pick up on the unixmake crypto/buildinf.h because of assumptions made around this sort of declaration (found in crypto/build.info): DEPENDS[cversion.o]=buildinf.h The assumption was that if such a header could be found in the source tree, that was the one to depend on, otherwise it would assume it should be in the build tree. This change makes sure that sort of mix-up won't happen again. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
It's not necessary for a pristine source, and a developer that makes changes usually knows what to do. Also, there was this mechanism that would do a "make depend" automatically which hasn't been used for so many years. Removed as well. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-