| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
handled properly.
Part of PR 75
|
|
|
|
|
|
| |
with existing code.
Modify library to use digest *_ex() functions.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
applications to use EVP. Add missing calls to HMAC_cleanup() and
don't assume HMAC_CTX can be copied using memcpy().
Note: this is almost identical to the patch submitted to openssl-dev
by Verdon Walker <VWalker@novell.com> except some redundant
EVP_add_digest_()/EVP_cleanup() calls were removed and some changes
made to avoid compiler warnings.
|
|
|
|
|
|
| |
errors can be tolerated, hide the error from 'make'.
This gives shorter output both if ranlib fails and if
it works.
|
|
|
|
|
| |
TODO: update docs, and make soe other routines
which use EVP_Digest*() check return codes.
|
|
|
|
|
|
|
|
| |
and make all files the depend on it include it without prefixing it
with openssl/.
This means that all Makefiles will have $(TOP) as one of the include
directories.
|
|
|
|
|
|
|
|
|
|
|
|
| |
sure they are available in opensslconf.h, by giving them names starting
with "OPENSSL_" to avoid conflicts with other packages and by making
sure e_os2.h will cover all platform-specific cases together with
opensslconf.h.
I've checked fairly well that nothing breaks with this (apart from
external software that will adapt if they have used something like
NO_KRB5), but I can't guarantee it completely, so a review of this
change would be a good thing.
|
|
|
|
|
| |
acceptable, since all that happens if it fails is a library with
an index, which makes linking slower, but still working correctly.
|
| |
|
|
|
|
|
|
| |
Also, "make update" has added some missing functions to libeay.num,
updated the TABLE for the alpha changes, and updated thousands of
dependancies that have changed from recent commits.
|
|
|
|
|
|
| |
"Jan Mikkelsen" <janm@transactionsite.com> correctly states that the
OpenSSL header files have #include's and extern "C"'s in an incorrect
order. Thusly fixed.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: Martin Kraemer <Martin.Kraemer@MchP.Siemens.De>
|
|
|
|
|
|
|
|
|
|
| |
in cryptlib.h (which is often included as "../cryptlib.h"), then the
question remains relative to which directory this is to be interpreted.
gcc went one further directory up, as intended; but makedepend thinks
differently, and so probably do some C compilers. So the ../ must go away;
thus e_os.h goes back into include/openssl (but I now use
#include "openssl/e_os.h" instead of <openssl/e_os.h> to make the point) --
and we have another huge bunch of dependency changes. Argh.
|
|
|
|
|
|
|
| |
There were problems with putting e_os.h just into the top directory,
because the test programs are compiled within test/ in the "standard"
case in in their original directories in the makefile.one case;
and in the latter symlinks may not be available.
|
|
|
|
| |
include file.
|
| |
|
|
|
|
|
|
| |
Submitted by:
Reviewed by:
PR:
|
|
|
|
| |
Submitted by: Anonymous
|
|
|
|
|
|
| |
Submitted by:
Reviewed by:
PR:
|
|
|
|
|
|
| |
Submitted by:
Reviewed by:
PR:
|
| |
|
| |
|
|
|
|
|
|
|
| |
script, translates function codes better and doesn't need the K&R function
prototypes to work (NB. the K&R prototypes can't be wiped just yet: they are
still needed by the DEF generator...). I also ran the script with the -rewrite
option to update all the header and source files.
|
|
|
|
|
|
| |
Submitted by:
Reviewed by:
PR:
|
| |
|
|
|
|
|
|
| |
Submitted by:
Reviewed by:
PR:
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
consistent in the source tree and replaced `/bin/rm' by `rm'. Additonally
cleaned up the `make links' target: Remove unnecessary semicolons, subsequent
redundant removes, inline point.sh into mklink.sh to speed processing and no
longer clutter the display with confusing stuff. Instead only the actually
done links are displayed.
|
| |
|
| |
|
|
|
|
|
| |
of 'make errors' without causing huge re-organisations of files when a new
code is added.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
1. The already released version was 0.9.1c and not 0.9.1b
2. The next release should be 0.9.2 and not 0.9.1d, because
first the changes are already too large, second we should avoid any more
0.9.1x confusions and third, the Apache version semantics of
VERSION.REVISION.PATCHLEVEL for the version string is reasonable (and here
.2 is already just a patchlevel and not major change).
tVS: ----------------------------------------------------------------------
|
| |
|
| |
|
| |
|
| |
|