Thanks Pierre, I checked your patched code and in that its done the way you
are explaining and its not giving error. I was talking about the Original
OpenSSL 1.0.0a the one which i downloaded from OpenSSL.org
I will try using the one you patched. Do you know by when your patch will be
added to
Hi Harshvir,
I am patching now openssl for WCE for almost a couple of year, with very
limited modifications and high compatibility with win32 code,
but unfortunately till now I had no feedback from the devteam.
It is a pity, as openssl mainstream code already contains many WCE flags
and so on,
On Fri, Jan 07, 2011, Pierre DELAAGE wrote:
Only the devteam can answer to your question about my patch inclusion.
Hope they will hear you...
http://rt.openssl.org/Ticket/Display.html?id=2350.
I have actually commented on that patch already about the problems of C++
style comments and how
ok, understood.
I will update the comments as required and re-submit with the same rt id.
Pierre
Le 07/01/2011 15:30, Dr. Stephen Henson a écrit :
On Fri, Jan 07, 2011, Pierre DELAAGE wrote:
Only the devteam can answer to your question about my patch inclusion.
Hope they will hear you...
Thanks, I was able to compile OpenSSL 1.0.0a for WinCE, but when i was
trying to use it with Application, then it was giving error for function
CryptSignHashA, and 2 more functions. OpenSSL is using ANSI version of
functions, and my application was using Unicode libraries thats why there
was a
Hi Harshvir,
if you are using the UNICODE version of the three functions, then you DO
NOT need the openssl implementation,
BECAUSE the standard MS SDK already provides them (and does NOT provide
ANSI implementations...!!! so I reimplemented them in e_capi.c).
just use the function names
Hi Pierre,
No I will need OpenSSL, as i am using OpenSSL for doing all the work I need.
OpenSSL code 1.0.0a is calling the functions with A, but as WinCE is
UNICODE, so Wincrypt.lib is having W function functions and not A functions,
and hence it was giving linking errors for OpenSSL libs for
Harshvir,
there is no problem for you to link BOTH with openssl AND wincrypt.lib !
particularly because openssl USES wincrypt.lib ! (I mean my patched
openssl v100a).
Linking with both libs should WORK. You have just to modify the makefile
of your application.
That way you will have access
...And call EXPLICITELY the W function, as my A function is NOT named
exactly as expected, to avoid conflict with the A function provided in
win32 5I can improve this later..).
for your information, my A function embedded in openssl is called
myorignameA...eg myCryptAcquireContextA.
see
Hi,
Is the CAPI engine from OpenSSL supported on WinCE?
// Harshvir
On Wed, Jan 5, 2011 at 12:45 PM, Harshvir Sidhu hvssi...@gmail.com wrote:
Hi,
Is the CAPI engine from OpenSSL supported on WinCE?
I don't believe OpenSSL will compile on Windows Mobile. I also
believe a patch by Pierre
Delaage is available at
Thanks Jeffrey,
I patched openssl 1.0.0a to compile perfectly for WCE.
including e_capi support.
This build works also perfectly for Windows Mobile 5 and 6 and above.
I am still waiting for the fine day where my limited modifications of
the code will be included in the openssl mainstream
12 matches
Mail list logo
