Is there likely to be much more of this? Coz the longer its left the
harder it gets to incorporate...
Yes, there is some more of this; but it is intermingled with C2Net
proprietary stuff that I need to extract it from. I tried to break down
the changes into a number of distinct self-contained changes that I can
apply over time after going through each one. As we know the SSLeay team
didn't use CVS so finding out reasons for changes to the code base can
only be done by reading every line. The major bits were the BN and SSL
bits. There are also some CAST fixes.
I presume the diff was made by diffing your internal tree, patching
the current one, then diffing again? I'm just worried about
accidentally undoing existing changes...
This stuff isn't all in our internal tree. But yes, I diffed it against
the original SSLeay-0.9.1b we supplied to start out OpenSSL. Then went
through those diffs manually to remove anything that shouldn't be there
and to tidy them up (removing extra blank lines and stuff, fixing
indentation). Then I applied that patch to my copy of the latest CVS tree
and used a CVS diff output to again go through the changes. By doing it
this way I think it will catch any recent patches and conflicts. Where
I've found conflicts (in the BN code) I've gone through the CVS logs to
see what people have changed since SSLeay-0.9.1b to make sure they are
folded in. I'm not able to test the resultant code thoroughly however, so
it may break for people. I was concerned about the ssl changes as they
are a fairly major change and have not been part of C2Net products so
they've not seen any public testing yet.
Mark
Mark J Cox, . www.awe.com/~mark
Latest news on the Apache Web Server ... www.apacheweek.com
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
