- 07 Jul, 2016 3 commits
-
-
Richard Levitte authored
OpenSSL engines are tied to the OpenSSL shared library versions, starting with OpenSSL 1.1. We therefore need to install them in directories which have the shared library version in it's name, to easily allow multiple OpenSSL versions to be installed at the same time. For VMS, the change is a bit more involved, primarly because the top installation directory was already versioned, *as well as* some of the files inside. That's a bit too much. Version numbering in files is also a bit different on VMS. The engines for shared library version 1.1 will therefore end up in OSSL$INSTROOT:[ENGINES0101.'arch'] ('arch' is the architecture we build for) Reviewed-by:Rich Salz <rsalz@openssl.org>
-
Richard Levitte authored
OpenSSL engines are tied to the OpenSSL shared library versions, starting with OpenSSL 1.1. We therefore need to install them in directories which have the shared library version in it's name, to easily allow multiple OpenSSL versions to be installed at the same time. For Unix, the default installation directory is changed from $PREFIX/lib/engines to $PREFIX/lib/engines-${major}_${minor} (mingw) or $PREFIX/lib/engines-${major}.${minor} (all but mingw) ($PREFIX is the directory given for the configuration option --prefix, and ${major} and ${minor} are the major and minor shared library version numbers) Reviewed-by: -
Richard Levitte authored
OpenSSL engines are tied to the OpenSSL shared library versions, starting with OpenSSL 1.1. We therefore need to install them in directories which have the shared library version in it's name, to easily allow multiple OpenSSL versions to be installed at the same time. For windows, the default installation directory is changed from $PREFIX/lib/engines to $PREFIX/lib/engines-${major}_${minor} ($PREFIX is the directory given for the configuration option --prefix, and ${major} and ${minor} are the major and minor shared library version numbers) Reviewed-by:
-
- 06 Jul, 2016 4 commits
-
-
Rich Salz authored
Reviewed-by:Matt Caswell <matt@openssl.org>
-
Richard Levitte authored
Reviewed-by: -
Dr. Stephen Henson authored
Reviewed-by:Tim Hudson <tjh@openssl.org>
-
Richard Levitte authored
When creating the library $lib.olb, make sure the extension is there. Otherwise, a logical name with the same name as the file in question will redirect the creation elsewhere. Reviewed-by:
-
- 05 Jul, 2016 8 commits
-
-
Richard Levitte authored
Reviewed-by: -
Richard Levitte authored
Reviewed-by: -
Richard Levitte authored
The calls we made to it were redundant, as the same initialization is done later in OPENSSL_init_crypto() anyway. Reviewed-by: -
FdaSilvaYY authored
Reviewed-by:
-
FdaSilvaYY authored
Separate invalid input case from any internal (malloc) failure Reviewed-by:
-
FdaSilvaYY authored
Reviewed-by:
-
FdaSilvaYY authored
Reviewed-by:
-
Dr. Stephen Henson authored
Reviewed-by:
-
- 04 Jul, 2016 2 commits
-
-
Rich Salz authored
Reviewed-by:
Kurt Roeckx <kurt@openssl.org> Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Richard Levitte authored
Make it possible to have a separate and different perl command string for installable scripts than we use when building, with the environment variable HASHBANGPERL. Its value default to the same as the environment PERL if it's defined, otherwise '/usr/bin/env perl'. Note: this is only relevant for Unix-like environments. Reviewed-by:
Andy Polyakov <appro@openssl.org> Reviewed-by:
-
- 02 Jul, 2016 8 commits
-
-
Andreas Karlsson authored
The SSL_load_client_CA_file() failed to load any CAs due to an inccorrect assumption about the return value of lh_*_insert(). The return value when inserting into a hash is the old value of the key. The bug was introduced in 3c82e437 . Reviewed-by:
-
Richard Levitte authored
On VMS, it's customary to have a procedure to check that the software was installed correctly and can run as advertised. The procedure added here is fairly simple, it checks that all libraries are in place, that the header crypto.h is in place, and that the command 'openssl version -a' runs without trouble. Reviewed-by: -
Richard Levitte authored
- The install top is versioned by default. However, only the major version should be used. - the default areas for certs, private keys an config files have changed, now all prefixed with 'OSSL$'. This gets reflected in cryptlib.h. - [.VMS]openssl_startup.com.in had some faults regarding creating rooted concealed logical names. Reviewed-by: -
Richard Levitte authored
This makes it possible for script writers to lock on to a specific version if they need to. Note that only the major version number is used. Reviewed-by: -
Richard Levitte authored
Also, have the static library file names contain the pointer size when applicable. Reviewed-by: -
Richard Levitte authored
Reviewed-by: -
Richard Levitte authored
Reviewed-by: -
Ben Laurie authored
Also, make sure that per-file deps are included in the build, even if previous builds have failed. Reviewed-by:
-
- 01 Jul, 2016 15 commits
-
-
Matt Caswell authored
Don't use hardcoded SSL_METHODs! Reviewed-by: -
Matt Caswell authored
We calculate the size required for the ServerKeyExchange message and then call BUF_MEM_grow_clean() on the buffer. However we fail to take account of 2 bytes required for the signature algorithm and 2 bytes for the signature length, i.e. we could overflow by 4 bytes. In reality this won't happen because the buffer is pre-allocated to a large size that means it should be big enough anyway. Addresses an OCAP Audit issue. Reviewed-by: -
Rich Salz authored
The recent merge of https://github.com/openssl/openssl/pull/1264 removed some trailing whitespace from the generated file obj_dat.h. Unfortunately obj_dat.pl kept re-adding it. Clean up the script and the output it generates. Add 'use strict / use warnings' Reviewed-by:
-
Richard Levitte authored
Reviewed-by: -
Richard Levitte authored
Now that INCLUDE considers both the source and build trees, no need for the rel2abs perl fragment hacks any more. Reviewed-by: -
Richard Levitte authored
INCLUDE statements in build.info files were source tree centric. That meant that to get include directory specs in the build tree, we had to resort to perl fragments that specified the build tree include paths as absolute ones. This change has the INCLUDE statement consider both the source and build tree for any include directory. It means that there may be some extra unnecessary include paths, but it also makes life simpler for anyone who makes changes in the build.info files. Reviewed-by: -
Dr. Stephen Henson authored
Reviewed-by: -
Kurt Roeckx authored
Reviewed-by: -
Kurt Roeckx authored
Fixes #1260 Reviewed-by: -
Kurt Roeckx authored
malloc(0) might return NULL and code for the old callbacks might fail, instead just say they should allocate 1 entry. Reviewed-by: -
mrpre authored
Reviewed-by:
-
mrpre authored
Reviewed-by:
-
Alessandro Ghedini authored
Reviewed-by:
Stephen Henson <steve@openssl.org> Reviewed-by:
-
Viktor Szakats authored
Reviewed-by:
-
Ben Laurie authored
Reviewed-by:
-
