Andreas Jellinghaus <aj <at> dungeon.inka.de> writes: > > you got it to work? great! I once got the binary on the web page to work, > but everytime I compiled it myself (and got it signed by microsoft), it didn't > work. did you compile it yourself? can you share the code? >
Sorry, it is pkcscsp2. First I used csp11, but unsuccessful. Now I use pkcscsp2. > > sorry, I don't understand. what exactly are you trying to do? > if you want to encrypt, the csp can do it with normal cryptoapi or openssl. > if you want to decrypt or sign with asymetric: ask opensc/the card to do it. > can be done using the normal PKCS#11 operations, no big deal. > > opensc doesn't implement using public keys - there is not much use askign the > card to do that. so if you want to do operations with the public key, yes I > think the CSP should do that itself - either with windows crypto api > functions or with openssl. > I show, why I decide what I need generation of key pair from OpenSc on encryption. First I wrote order of CryptoApi commands, which needed for calling in Windows for encrypt, as written in MSDN. On CryptoApi command CryptGenKey, pkcscsp2 call C_GenerateKeyPair and fails. So I supposed, that problem in pkcscsp2. But why they try call C_GenerateKeyPair, if it not needed, I don't understand. Then I supposed what have I do to correct it, because I don't have enough experience in working with encryption. I need asymmetric encrypt throw standard Windows CSP, and decrypt throw OpenSc, it is possible? I just want hear, what I'm moving in right direction. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
