- Dec 15, 2002
-
-
Geoff Thorpe authored
warnings. Reported by: Bernhard Simon.
-
Andy Polyakov authored
-
Andy Polyakov authored
uses WorkShop C. It's gcc driver that brings copy of libgcc.a into .so otherwise. In case you wonder what it's -Wl,-z... and not just -z. Problem is that gcc driver apparently omits all -z options but -z text. Don't ask me why. I'm not committing corresponding workaround into the HEAD as Makefile.shared reportedly needs even more work...
-
Andy Polyakov authored
is not expanded if prepended with a $-sign.
-
Richard Levitte authored
insensitive file names, as well as those that do not have symlinks. Incidently, both these cases apply on DOS/Windows...
-
Richard Levitte authored
- define a HERE variable to indicate where the source tree is (not used right now) - make more use of copying and making attribute changes to {file}.new, and then move it to {file} - use 'mv -f' to avoid all those questions to the user when the file in question doesn't have write attributes for that user.
-
Richard Levitte authored
-
Andy Polyakov authored
-
- Dec 14, 2002
-
-
Andy Polyakov authored
the one to be used to denote local labels in single function scope. Problem is that SHA uses same label set across functions, therefore I have to switch back to $ prefix.
-
Andy Polyakov authored
-
Andy Polyakov authored
-
cvs2svn authored
'OpenSSL_0_9_7-stable'.
-
Andy Polyakov authored
-
Andy Polyakov authored
-
Andy Polyakov authored
-
- Dec 13, 2002
-
-
Geoff Thorpe authored
warnings. Reported by: Bernhard Simon.
-
Andy Polyakov authored
shared libraries shared.
-
Andy Polyakov authored
shared libraries shared.
-
Richard Levitte authored
callbacks
-
Richard Levitte authored
callbacks
-
- Dec 12, 2002
-
-
Richard Levitte authored
BIO_s_bio.pod. The most logical is to move everything needed from BIO_new_bio_pair.pod to BIO_s_bio.pod (including the nice example) and toss BIO_new_bio_pair.pod. I hope I got all the info over properly. PR: 370
-
Richard Levitte authored
BIO_s_bio.pod. The most logical is to move everything needed from BIO_new_bio_pair.pod to BIO_s_bio.pod (including the nice example) and toss BIO_new_bio_pair.pod. I hope I got all the info over properly. PR: 370
-
Richard Levitte authored
since it's both enumerated and explained in BIO_s_connect.pod. PR: 370
-
Richard Levitte authored
since it's both enumerated and explained in BIO_s_connect.pod. PR: 370
-
Richard Levitte authored
-
Richard Levitte authored
PR: 353
-
Richard Levitte authored
PR: 353
-
Richard Levitte authored
that wants to use the hw_ncipher engine without having given any callbacks for the dynamic type of locks.
-
Richard Levitte authored
engine work properly even in bad situations.
-
- Dec 11, 2002
-
-
Geoff Thorpe authored
configured with zlib support).
-
Richard Levitte authored
callbacks) before attempting to lock.
-
Richard Levitte authored
callbacks) before attempting to lock.
-
Richard Levitte authored
pushed item. The index is the number of items - 1. And if a NULL item was found, actually use it. Finally, provide a little bit of safety in CRYPTO_lock() by asserting the a requested dynamic lock really must exist, instead of just being silent about it
-
Richard Levitte authored
pushed item. The index is the number of items - 1. And if a NULL item was found, actually use it. Finally, provide a little bit of safety in CRYPTO_lock() by asserting the a requested dynamic lock really must exist, instead of just being silent about it
-
Richard Levitte authored
were defined.
-
Richard Levitte authored
were defined.
-
Richard Levitte authored
were defined.
-
Richard Levitte authored
were defined.
-
Richard Levitte authored
(before SSLeay, maybe?), it's better to have that macro protect the compatibility header des_old.h. In the new des.h, let's use a slightly different protecting macro. The rationale is that there are application that might include (via other header files, perhaps) both an old libdes des.h and OpenSSL's des.h. Whichever comes first would overshadow the other because of the clash in protecting macro. This fix solves that problem.
-
Richard Levitte authored
(before SSLeay, maybe?), it's better to have that macro protect the compatibility header des_old.h. In the new des.h, let's use a slightly different protecting macro. The rationale is that there are application that might include (via other header files, perhaps) both an old libdes des.h and OpenSSL's des.h. Whichever comes first would overshadow the other because of the clash in protecting macro. This fix solves that problem.
-