On 2010/12/20 15:23, Andreas Jellinghaus wrote:
> 2.) a PKCS-CSP such as the ID-Ally CSP, CSP#11 or PKCSCP - all these
> packages implement a CSP, but they don't talk to the smart card
> directly. Instead they load a pkcs#11 plugin to do that, such as
> opensc-pkcs11.so
Forgot all ab
On 2010/12/20 5:30, Jean-Michel Pouré - GOOZE wrote:
> Some users are contacting me with questions about Windows support for
> PKCS#11 smartcards. As far as I understand, Windows support for PKCS#11
> is poor.
>
AFAIK, Windows uses CSPs, and does not support PKCS#11 at all. This may have
changed
On 2010/12/09 20:22, Kalev Lember wrote:
> Victor, that's a very good idea to use standard MSI generated with WiX!
>
> Instead of adding 'Program Files\OpenSC' directory to PATH, it might be
> better to put all the deps (libopensc.dll, zlib.dll, iconv.dll, etc)
> into WinSxS [1] and only put the
On 2010/12/07 16:03, Martin Paljak wrote:
>
> On Dec 7, 2010, at 4:41 AM, Nikolay Elenkov wrote:
>
>> On 2010/12/07 2:36, Viktor TARASOV wrote:
>>
>>>
>>>> [1]
>>>> http://www.opensc-project.org/opensc/wiki/WindowsInstaller#Possibleinstall
On 2010/12/07 2:36, Viktor TARASOV wrote:
>
>> [1]
>> http://www.opensc-project.org/opensc/wiki/WindowsInstaller#PossibleinstallerstepsWindowsenvironmentdescription
>>
> Here the OpenSC dlls are installed into 'system32'.
> Can an alternative method, like changing of the 'PATH' variable, be a
On 2010/08/14 20:57, Martin Paljak wrote:
Hi,
Thanks for your reply. See my comments inline.
> Hello,
> On Aug 12, 2010, at 5:23 AM, Nikolay Elenkov wrote:
>> I am developing a (proprietary) dynamic card driver (Windows). I have the
>> basics
>> setup working, I can l
Hi,
I am developing a (proprietary) dynamic card driver (Windows). I have the basics
setup working, I can load and login. However I am having some troubles with
locking (transactions). Any advice is much appreciated.
It appears that the framework calls pcsc_lock before calling my
card_select_file
