On 08.01.2011 16:11, Jean-Michel Pouré - GOOZE wrote:
>> But OpenSC implements the emulation of pkcs15 and pkcs15init and thus
>> this card can be initialized and used by OpenSC and can stay
>> compatible with the native middleware.
> I want to make sure, so that everyone understands: the Feitian P
> Windows OS
To be more precise, only Windows Vista / 7 seem to need these flags.
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mai
> But OpenSC implements the emulation of pkcs15 and pkcs15init and thus
> this card can be initialized and used by OpenSC and can stay
> compatible with the native middleware.
I want to make sure, so that everyone understands: the Feitian PKI can
be initialized and used under GNU/Linux, Windows a
Hello,
On 08.01.2011 13:55, Martin Paljak wrote:
> On Jan 2, 2011, at 6:24 PM, Viktor TARASOV wrote:
>> Martin Paljak wrote:
>>> This will hold plaintext RSA private key parameters. Why? When importing a
>>> private key, the key object should already come from pkcs15-init (or
>>> equivalent)?
>>
Hello,
On 07.01.2011 22:21, Jean-Michel Pouré - GOOZE wrote:
Because users have smartcards in the wallet and need to connect from any
computer, including Mac OS X, Windows and GNU/Linux, and they don't know
in advance which framework is installed, it seems important that card
initialization is co
Am Donnerstag 06 Januar 2011, um 14:57:35 schrieb Peter Stuge:
> Cool. I'm not sure exactly how to implement that $handling, it also
> depends a bit on what tools and processes are used on the server.
see one of my last emails in the thread. postfix has everything we need
build in.
> I also think
Hello,
On Jan 2, 2011, at 6:24 PM, Viktor TARASOV wrote:
> Martin Paljak wrote:
>>>
>>>
>> This will hold plaintext RSA private key parameters. Why? When importing a
>> private key, the key object should already come from pkcs15-init (or
>> equivalent)?
>>
> 'data.prvkey' is used to pass the
Hello,
A generic question about authentic_pin* (like authentic_chv_verify_pinpad)
functions and related logic.
Generic review of it suggests that it mostly duplicates iso7816_pin_cmd and
sc_pin_cmd. Why the duplication? What is missing from ISO functions?
PIN handling and decisions to what hap
Dear all,
> We can't vouch for what a proprietary driver or CSP can or should do with
> cards initialized with OpenSC. If the proprietary software does not claim
> PKCS#15 conformance, there's nothing to do.
What do you mean by claim PKCS#15? Does it require a flag?
I am sure that Feitian PKI c
Hello,
On Jan 8, 2011, at 12:13 AM, Douglas E. Engert wrote:
> On 1/7/2011 3:21 PM, Jean-Michel Pouré - GOOZE wrote:
>> It seems that initializing a Feitian PKI on Windows 7 64bits (CSP), you
>> are able to use the card on GNU/Linux (OpenSC). But the converse is not
>> always true. Windows may not
Le vendredi 07 janvier 2011 à 16:13 -0600, Douglas E. Engert a écrit :
> I would think it should be possible. The trick is to know what the
> vendor's
> driver is expecting in the flags, and other fields.
Thanks a lot Douglas, I will contact Feitian about that. Also I would
like to play with Open
11 matches
Mail list logo
