Angus Lee wrote:
> 
> Hi,
> 
> There're three sk_pop_free() calls in the dump_certs_keys_p12() function in
> the pkcs12.c program. I copied the code from dump_certs_keys_p12() function
> into my program and compiled in VC6 /w SP4 on Win98SE. VC6 reported that:
> C:\Work\EudSMIME\SetngDlg.cpp(378) : error C2664: 'sk_pop_free' : cannot
> convert parameter 2 from 'void (PKCS12_SAFEBAG *)' to 'void (__cdecl *)(void)'
>         None of the functions with this name in scope match the target type
> C:\Work\EudSMIME\SetngDlg.cpp(381) : error C2664: 'sk_pop_free' : cannot
> convert parameter 2 from 'void (PKCS12_SAFEBAG *)' to 'void (__cdecl *)(void)'
>         None of the functions with this name in scope match the target type
> C:\Work\EudSMIME\SetngDlg.cpp(383) : error C2664: 'sk_pop_free' : cannot
> convert parameter 2 from 'void (struct pkcs7_st *)' to 'void (__cdecl
> *)(void)'
>         None of the functions with this name in scope match the target type
> 
> Has anyone got any idea? I've come accross similar problem with the
> M_PKCS12_unpack_authsafes() function. Someone told me to cast the parameter in
> the macros definitions. However sk_pop_free is indeed a function inside
> OpenSSL. I don't think simply doing a cast will work. Please help me. Thank
> you.
> 

>From those errors it looks like you are trying to call these macros in
C++. Why do you need to do that? You can parse PKCS#12 files much more
easily with PKCS12_parse() which should have no problems.

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
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to