Hi,

[din...@mini]-[/Library/OpenSC/bin]$ ./cardos-info
Running cardos-tool --info
Using reader with a card: OmniKey CardMan 6121 00 00
3b:f2:18:00:02:c1:0a:31:fe:58:c8:08:74
Info : CardOS V4.3B (C) Siemens AG 1994-2004
Chip type: 124
Serial number: 26 67 9b 08 15 1a
Full prom dump:
33 66 00 1B 5B 5B 5B 5B 7C FF 26 67 9B 08 15 1A 3f..[[[[|.&g....
00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 ................
OS Version: 200.8 (that's CardOS M4.3B)
Current life cycle: 16 (operational)
Security Status of current DF:
Free memory : 15
ATR Status: 0x0 ROM-ATR
Packages installed:
E1 09 01 04 13 02 C8 08 8F 01 01 ...........
Ram size: 4, Eeprom size: 64, cpu type: 66, chip config: 63
Free eeprom memory: 38740
System keys: PackageLoadKey (version 0x00, retries 10)
System keys: StartKey (version 0xff, retries 10)
Path to current DF:
50 15 P.

The output from opensc-tool -f is too long what specifics should i  
look for ?
The card is provided by the certificated issuer, this is officially e- 
sing in our country, so i suppose that i do not need to initialize it ?

On Jun 5, 2009, at 3:20 PM, JP Szikora wrote:

> Hi,
>
> Your card (a CardOS from Siemens) is (probably) not initialized with  
> OpenSC tools (pkcs15-init). Maybe you need to use a PKCS11 module  
> specifically designed for your card!
>
> What is the output of the cardos-info command?  and of the opensc- 
> tool -f command?
>
> Jean-Pierre
>
> Sevdalin Todorov Todorov a écrit :
>> Hi Jean-Pierre thanks for the reply,
>>
>> the output of previews commands is from SCA 0.2.4.1 - installed  
>> because of recommendation of my certificate issuer.
>> But, before 0.2.4.1 i also tried the SCA 0.2.6, with no success.
>> Now i've installed SCA 0.2.6 back to try again but the result is  
>> same:
>>
>> [din...@mini]-[/Library/OpenSC/bin]$ ./opensc-tool -i
>> opensc 0.11.8 [gcc  4.0.1 (Apple Computer, Inc. build 5367)]
>> Enabled features: zlib readline iconv openssl pcsc(/System/Library/ 
>> Frameworks/PCSC.framework/PCSC)
>>
>> [din...@mini]-[/Library/OpenSC/bin]$ ./pkcs11-tool -I
>> Cryptoki version 2.20
>> Manufacturer     OpenSC (www.opensc-project.org)
>> Library          smart card PKCS#11 API (ver 0.0)
>>
>> [din...@mini]-[/Library/OpenSC/bin]$ ./pkcs11-tool -O
>> Bus error
>>
>> Below is the output of recommended command by you:
>>
>> [din...@mini]-[/Library/OpenSC/bin]$ /Library/OpenSC/bin/pkcs11- 
>> tool -t -l --module /Library/OpenSC/lib/opensc-pkcs11.so
>> Please enter User PIN:
>> C_SeedRandom() and C_GenerateRandom():
>>  seeding (C_SeedRandom) not supported
>>  seems to be OK
>> Digests:
>>  all 4 digest functions seem to work
>>  MD5: OK
>>  SHA-1: OK
>>  RIPEMD160: OK
>> Signatures (currently only RSA signatures)
>>  testing key 0 (******************************)
>> Bus error
>>
>> Regarding the smartcard:
>> [din...@mini]-[/Library/OpenSC/bin]$ ./opensc-tool -n
>> Using reader with a card: OmniKey CardMan 6121 00 00
>> CardOS M4
>>
>> The strange thing for me is that some other commands works e.g.:
>> [din...@mini]-[/Library/OpenSC/bin]$ ./pkcs11-tool -T
>> Available slots:
>> Slot 0           OmniKey CardMan 6121 00 00
>>  token label:   InfoNotary (PIN)
>>  token manuf:   Siemens AG (C)
>>  token model:   PKCS#15
>>  token flags:   login required, PIN initialized, token initialized
>>  serial num  :
>>
>>
>> If you point me how can i go deep to debug this "bus error" will be  
>> great.
>>
>> Greets,
>> Dincho
>>
>>
>>
>> On Jun 5, 2009, at 1:39 PM, JP Szikora wrote:
>>
>>> Hi Dincho,
>>>
>>> Which SCA did you use? opensc 0.11.5 is pretty old now.
>>> Which smartcard? Is it supported by OpenSC?
>>> Have you tried with the module specification:
>>> /Library/OpenSC/bin/pkcs11-tool -t -l --module /Library/OpenSC/lib/ 
>>> opensc-pkcs11.so
>>>
>>> Cheers,
>>>
>>> Jean-Pierre
>>>
>>> Sevdalin Todorov Todorov a écrit :
>>>>
>>>> The error occurred when I try to show objects on token.
>>>>
>>>> [din...@mini]-[/Library/OpenSC/bin]$ ./pkcs11-tool -vvvvvv -O
>>>> Bus error
>>>>
>>>> The same happens if i try: /pkcs11-tool -t -l but with some more  
>>>> stack information ( i'm not sure that it's secure to post my key  
>>>> signature here ).
>>>>
>>
>>
>

_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to