>> I have the following differences in s3_clnt.c. The problems are >> that the cryptlib.h header is in the crypto directory. Should I >> put this on the include path when building the SSL library or >> would it make more sense to use the "openssl" copy. Ie, change, >> >> #include "cryptlib.h" >> >> #include <openssl/cryptlib.h>
Richard> I'm sorry, I don't understand what the problem is. the Richard> first above variant of the #include is the correct one, Richard> since cryptolib.h is a OpenSSL-internal header file (if you Richard> look in include/openssl, you'll see that it doesn't exist Richard> there). Thank-you. The status of `cryptolib.h' as an OpenSSL-internal header was what I needed to know. Since I have to make my own build files, I had never put the crypto directory as an include path to the libssl Makefile. I am building OpenSSL for vxWorks with my own makefiles. I did not mean for there to be a bug submitted to the openSsl RT. I was just asking for information. Is the address "[EMAIL PROTECTED]" the wrong place to ask? The other part of my request did have some merit. The comparison of a 'sizeof struct' to an int could fail if the int overflows in to a negative value. However, I am not certain that this is a possible condition...but it is locally incorrect. The compiler just gives me a warning about this, so I have changed the code locally to cast the "int" to "unsigned int". This works fine for me and you may certainly close the RT ticket if you don't think this is a problem. If this is a problem, there are a few places in openSSL where this occurs (comparison of a signed variable to a `sizeof' operator). Most of the time a very large buffer would have to be sent. The condition might be more problematic for a 16 bit version of OpenSSL. Thanks again for your time. The openSsl developers seem to be under heat for all of the wrong reason. Regards, Bill Pringlemeir. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
