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.
One last thing: I'm looking for a Sr level Software Engineer to be our SSL
"guru" so if you're interested in moving to San Diego and working for a
really hot new startup, send me an e-mail and we'll go from there.
Thanks again,
--
Billy Cole
Astute Networks, Inc.
760-736-3663 x207
[EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
