- Sep 22, 2001
-
-
Bodo Möller authored
-
- Sep 21, 2001
-
-
Bodo Möller authored
-
Bodo Möller authored
just sent a HelloRequest.
-
Bodo Möller authored
-
- Sep 20, 2001
-
-
Bodo Möller authored
-
Bodo Möller authored
reveal whether illegal block cipher padding was found or a MAC verification error occured. In ssl/s2_pkt.c, verify that the purported number of padding bytes is in the legal range.
-
- Sep 14, 2001
-
-
Bodo Möller authored
-
Bodo Möller authored
branch (revision 1.50, 2000-11-17)
-
- Sep 13, 2001
-
-
Lutz Jänicke authored
-
Lutz Jänicke authored
-
cvs2svn authored
'OpenSSL_0_9_6-stable'.
-
Lutz Jänicke authored
-
Lutz Jänicke authored
Bodo Moeller).
-
Bodo Möller authored
-
- Sep 12, 2001
-
-
Geoff Thorpe authored
-
Geoff Thorpe authored
-
Geoff Thorpe authored
in "types.h" so that very few headers will need to include engine.h, generally only C files using API functions will need it (reducing the header dependencies quite a lot).
-
Geoff Thorpe authored
-
Dr. Stephen Henson authored
Fix X509V3 macro so they compile.
-
- Sep 11, 2001
-
-
Lutz Jänicke authored
settable (proposed by "Douglas E. Engert" <deengert@anl.gov>).
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
-
- Sep 10, 2001
-
-
Geoff Thorpe authored
-
Geoff Thorpe authored
macros in apps.h.
-
Geoff Thorpe authored
-
Ulf Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
(Working file: progs.h revision 1.24 date: 2001/02/19 16:06:03; author: levitte; state: Exp; lines: +59 -59 Make all configuration macros available for application by making 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. [...])
-
Bodo Möller authored
-
Bodo Möller authored
-
Bodo Möller authored
distinction (which does not work well because if CRYPTO_MDEBUG is defined at library compile time, it is not necessarily defined at application compile time; and memory debugging now can be reconfigured at run-time anyway). To get the intended semantics, we could just use the EVP_DigestInit_dbg unconditionally (which uses the caller's __FILE__ and __LINE__ for memory leak debugging), but this would make memory debugging inconsistent. Instead, callers can use CRYPTO_push_info() to track down memory leaks.
-