Re: [opensc-devel] PKCS#11 for CryptoAPI

2007-05-09 Thread Nate Nielsen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Relyea wrote: > nss/lib/ckfw itself is meant to be a framework to quickly bring up new > PKCS #11 adapters. It's meant to be separable from NSS, (and in fact has > no nspr dependencies). Interesting. I guess it compiles the parts of NSS and NSP

Re: [opensc-devel] PKCS#11 for CryptoAPI

2007-05-08 Thread Robert Relyea
Nate Nielsen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Relyea wrote: nss/lib/ckfw itself is meant to be a framework to quickly bring up new PKCS #11 adapters. It's meant to be separable from NSS, (and in fact has no nspr dependencies). Interesting. I guess it compile

Re: [opensc-devel] PKCS#11 for CryptoAPI

2007-05-07 Thread Robert Relyea
Nate Nielsen wrote: Andreas Jellinghaus wrote: sure, it is very welcome. well, it is the third project next to pkcscsp and csp11, but both of that are dead and no longer under development. Well CSP#11, as I understand it, does the exact opposite. It presents a Windows Cryptographic Ser

Re: [opensc-devel] PKCS#11 for CryptoAPI

2007-05-06 Thread Nate Nielsen
Andreas Jellinghaus wrote: > sure, it is very welcome. well, it is the third project next to pkcscsp and > csp11, but both of that are dead and no longer under development. Well CSP#11, as I understand it, does the exact opposite. It presents a Windows Cryptographic Service Provider interface whi

Re: [opensc-devel] PKCS#11 for CryptoAPI

2007-05-06 Thread Nate Nielsen
Alon Bar-Lev wrote: > I will review this in week-end, but just a general comment... The RSA > Security include files come with L/GPL incompatible license. > There is a free alternative that we use, please test it out, so we > don't have licensing issues. > > The file is maintained at: > http://cvs

Re: [opensc-devel] PKCS#11 for CryptoAPI

2007-05-06 Thread Andreas Jellinghaus
On Sunday 06 May 2007 21:01:55 Alon Bar-Lev wrote: > > >>> BTW, I'm working on building a complete PKCS#11 provider for CAPI. So > > >>> by supporting PKCS#11 you'd be able to have things like CAPI support. > > >> > > >> This is great to hear! > > >> It has been long since I developed for Microsoft

[opensc-devel] PKCS#11 for CryptoAPI

2007-05-06 Thread Alon Bar-Lev
On 5/6/07, Nate Nielsen <[EMAIL PROTECTED]> wrote: > > Alon Bar-Lev wrote: > >> On 4/24/07, Nate Nielsen <[EMAIL PROTECTED]> wrote: > >>> BTW, I'm working on building a complete PKCS#11 provider for CAPI. So by > >>> supporting PKCS#11 you'd be able to have things like CAPI support. > >> This is gr