Billy Cole wrote:
>
> We are planning on an embedded SSL project and we're using OpenSSL
> as our "reference implementation". I have done the required to compile and
> run the 0.9.6 distribution on our target processor and all works well. While
> moving on to bigger and better thoughts, a number of "practicality" issues
> have surfaced. One thing I'm wondering is: What are peoples' thoughts
> (possibly with some experiences) on what it takes to deploy a product that
> uses OpenSSL from a code management/maintenance point of view? Are
> people working on a private branch (so to speak) and merging OpenSSL
> changes/fixes into that branch? Obviously everyone's going to have something
> different about "their version" of OpenSSL and I'm wondering how to do
> that while at the same time take advantage of the OpenSSL developers'
> updates.
Why is that obvious? The right thing to do is to contribute back your
modifications.
Cheers,
Ben.
--
http://www.apache-ssl.org/ben.html
"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]