On 19-07-2010 12:35, Jakob Bohm wrote:
On 16-07-2010 22:50, Mark Bishop wrote:
Thank you very much so far with all the input you have given me. I have
few more questions. I am going to have to give up on interfacing with
the Windows Crypto library and put openssl on my client as well.
However, my client will be running Windows CE 6.0 with an ARM processor.
Are the installation instructions in INSTALL.WCE still valid? Has anyone
compiled openssl for CE 6.0 (Visual C 2005), ARM processor? I've been
asked to give a quote on how long it is going to take me and by the
looks of the instructions, it doesn't look difficult at all. Can anyone
more experienced say otherwise?
I know someone who has recently compiled a 0.9.8 version for this target
and I am going to port his work to 1.0.0 and 1.0.0a very soon.
I will post back with more information when I get it.
Just to let you all know that I am still working on this. I have
something good enough for our own use, but it is not prepped public
consumption yet.
During my porting work, I ran into a number of practical issues that
each required some heavy coding (my current patch is more than 350K).
For anyone else working along similar lines, the issues I have dealt
with are:
1. The current README.WCE and code assumes that you link with one of
two less free libraries (one is LGPL, the other requires reconfiguration
of the target device/phone). I wrote my own more minimal library
under the OpenSSL license to avoid them both. This obviously implied
patching OpenSSL to use the new library rather than one of the two
old ones.
2. To simplify installation of my program, I prefer static linking of
OpenSSL. This turned up a number of general (not WinCE specific) design
issues in EVP and ASN code, resulting in massive bloat of programs that
don't use all of OpenSSL. Basically, lots of .o files are pulled in
by just-in-case calls (mostly XXX_free() functions), table-driven
selection of which code to execute and other such bad practices.
Using a number of ad-hoc patches I managed to cut down some of the
overhead, but its not very clean or efficient yet.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
