On Wed, Oct 11, 2006 at 02:56:37PM -0500, Eric Norman wrote:
> While all these are very valid concerns, I sure don't see why
> they would be relevant to the OpenSC group and this list.
Because a user (me too) would expect OpenSC to abstract the smart
card in a way that does not expose her to any r
On Oct 10, 2006, at 6:46 PM, Antti S. Lankila wrote:
Okay, these two tasks are the last ones, before the signer component
would be ready for wider consumption. Before it's anywhere near sane
to allow user to sign documents that legally binds her, it would be
good idea to:
1) visualize the
Hi all,
I have a Java 1.5 application, which use the opensc PKCS11 library
(opensc-pkcs11.so). It is impossible to access to the card by more
threads than one (and by more java processes) with lock_login set to
false.
Due this, I decide, that the 'static CK_RV pkcs15_bind(struct
sc_pkcs11_
On 10/11/06, Ludovic Rousseau <[EMAIL PROTECTED]> wrote:
I discovered that I cannot use an ISO Latin1 character in the tokenUid
name returned by OpenSCToken::probe(SecTokendProbeFlags flags, char
tokenUid[TOKEND_MAX_UID]). The token is not displayed in the KeyChain
application.
Comments?
As
Hello,
I discovered that I cannot use an ISO Latin1 character in the tokenUid
name returned by OpenSCToken::probe(SecTokendProbeFlags flags, char
tokenUid[TOKEND_MAX_UID]). The token is not displayed in the KeyChain
application.
Since this tokenUid value is not displayed I just replaced the
offe
