| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
casts) used in the lhash code are about as horrible and evil as they can
be. For starters, the callback prototypes contain empty parameter lists.
Yuck.
This first change defines clearer prototypes - including "typedef"'d
function pointer types to use as "hash" and "compare" callbacks, as well as
the callbacks passed to the lh_doall and lh_doall_arg iteration functions.
Now at least more explicit (and clear) casting is required in all of the
dependant code - and that should be included in this commit.
The next step will be to hunt down and obliterate some of the function
pointer casting being used when it's not necessary - a particularly evil
variant exists in the implementation of lh_doall.
|
| |
|
|
| |
For the server side this was already done one year ago :-(
|
| |
|
|
|
|
|
|
|
| |
like Malloc, Realloc and especially Free conflict with already existing names
on some operating systems or other packages. That is reason enough to change
the names of the OpenSSL memory allocation macros to something that has a
better chance of being unique, like prepending them with OPENSSL_.
This change includes all the name changes needed throughout all C files.
|
| |
|
|
| |
eliminate some of the -Wcast-qual warnings (debug-ben-strict target)
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
they can sometimes be different memory structures.
|
| |
|
|
| |
don't leak tons of memory.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Previously, the returned SSL_SESSION didn't have its reference count
incremented so the SSL_SESSION could be freed at any time causing
seg-faults if the pointer was subsequently used. Code that uses
SSL_get_session must now make a corresponding SSL_SESSION_free() call when
it is done to avoid memory leaks (or blocked up session caches).
Submitted By: Geoff Thorpe <geoff@eu.c2.net>
|
| |
|
|
| |
a pain to read when using 4-space tabs.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
because of missing session ID context (so that application programmers
are directly pointed to what they should do differently).
|
| |
|
|
|
|
|
| |
While modifying the sources, I found some inconsistencies on the use of
s->cert vs. s->session->sess_cert; I don't know if those could
really have caused problems, but possibly this is a proper bug-fix
and not just a clean-up.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
called sess_cert instead of just cert. This is in preparation of further
changes: Probably often when s->session->sess_cert is used, we should
use s->cert instead; s->session->sess_cert should be a new structure
containing only the stuff that is for just one connection (e.g.
the peer's certificate, which the SSL client implementations currently
store in s->session->[sess_]cert, which is a very confusing thing to do).
Submitted by:
Reviewed by:
PR:
|
| |
|
|
|
|
|
|
|
|
| |
Submitted by: Anonymous
Reviewed by:
PR:
Submitted by:
Reviewed by:
PR:
|
| |
|
|
| |
mutex.
|
| | |
|
| |
|
|
|
|
| |
Submitted by:
Reviewed by:
PR:
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Slight cleanup in ssl/
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
[Eric A. Young, (from changes to C2Net SSLeay, integrated by Mark Cox)]
Fix so that the version number in the master secret, when passed
via RSA, checks that if TLS was proposed, but we roll back to SSLv3
(because the server will not accept higher), that the version number
is 0x03,0x01, not 0x03,0x00
[Eric A. Young, (from changes to C2Net SSLeay, integrated by Mark Cox)]
Submitted by:
Reviewed by:
PR:
|
| | |
|
| | |
|
| | |
|
| |
|
