I had just finished porting SSLeay 0.9.0 to MacOS 8.x when I learned (quite
by accident) that it had become OpenSSL. I was at once elated that the
library would continue to evolve, and consternated that a 0.9.1 had been
available for some time! (Do I upgrade now even though I'm under strenuous
deadline pressures, or just keep the code that's already working? Choices,
choices.)
I have some questions:
1) Should I use the SSLeay copyright/licensing, or the OpenSSL copyright?
It sounds like I should just use the OpenSSL version, but I'd like to make
sure.
2) How many changes are there between 0.9.0 and 0.9.1? Reading the
history, it appears most of the fixes are build/compile issues, not
features or serious bug fixes. Is there any compelling reason to upgrade
right away?
3) Is there any interest in the idea of a MacOS port, or does anyone care?
MacOS X is going to have a POSIX API, BSD sockets, etc., so there might be
no point in trying to maintain a port for MacOS 8.x. I only ported the
library, not any of the applications. It works, and only requires new code
in one file (threads). I did have to comment out lots of "#include
<sys/whatever.h>" throughout the library, so they would need to be properly
#ifdef'd.
4) Are there any plans to support chained certificates? This is an area
that I'm willing to contribute some time to, if there is interest (an
nobody has already done it).
cjh
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
