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. We would also like to shrink code size, memory requirements, etc.
> and making these types of drastic changes seem like it would make it even
> more difficult to work off the same tree. Anyway, I'd be very interested in
> hearing about any pros/cons and project experiences.
>
As has been mentioned the easiest thing is to contribute you changes to
the development team. Any patches to shrink memory and code size would
be welcomed.
If you are going to try adding your own modifications to each OpenSSL
release then this could prove very painful. In particular the changes
from OpenSSL 0.9.6->0.9.7 will be considerable: whole sections of the
code have been completely rewritten.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
