...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
my<origname>A...eg "myCryptAcquireContextA".
see engines/e_capi.c for more details.
At the time I implemented those functions, it was just for the usage of
openssl e_capi ITSELF, not to be called from the exterior of e_capi.c.
This can be improved in the future.
But your problem is not there...
So, using directly and ecplicitely the W function should work corrrectly
for you (instead of using the "standard" short name without A neither W).
Best regards,
Pierre
Le 07/01/2011 05:25, Harshvir Sidhu a écrit :
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
these functions.
Thanks.
On Thu, Jan 6, 2011 at 4:58 PM, Pierre DELAAGE <delaage.pie...@free.fr
<mailto:delaage.pie...@free.fr>> wrote:
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 ending with W instead of A to
explicitely use unicode versions of the functions and include
Wincrypt.h in your c file, and link with Cryptapi.lib,
or more appropriately use the name ending with nothing:
"CryptSignHash", and adjust your compile flags to activate unicode
for evc compiler.
Of course you have to use the MS evc compiler 420 to do all this
stuff.
Yours sincerely,
Pierre
Le 06/01/2011 13:43, Harshvir Sidhu a écrit :
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 problem. So was just
making sure that it works on WinCE. Thanks.
On Thu, Jan 6, 2011 at 12:56 AM, Pierre DELAAGE
<delaage.pie...@free.fr <mailto:delaage.pie...@free.fr>> wrote:
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 (some flags and a few instructions in the sources,
some options in the makefiles, all very close and consistant
with the win32 code).
Harshvir : please find useful information and pre-compiled
openssl for WCE here :
http://delaage.pierre.free.fr <http://delaage.pierre.free.fr/>
Yours sincerely,
Pierre Delaage
Le 05/01/2011 23:44, Jeffrey Walton a écrit :
On Wed, Jan 5, 2011 at 12:45 PM, Harshvir
Sidhu<hvssi...@gmail.com <mailto: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
http://rt.openssl.org/Ticket/Display.html?id=2350.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
<http://www.openssl.org/>
User Support Mailing List openssl-users@openssl.org
<mailto:openssl-users@openssl.org>
Automated List Manager majord...@openssl.org
<mailto:majord...@openssl.org>
