KOBIL mIDentity

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

KOBIL mIDentity

Marcel Koopmans-2
Hello Everybody,

I am doing some tests with the mIDentity token itself.

The device is an 128Mb drive and a smartcard reader.
I know that under windows a service changes the device from a drive to both.

Now how do I do that under Linux?
The multiple SCSI LUNs sollution seems to work for multiple compact
flash cards readers not on this.

During testing the unsupported tcos card is placed.

-- debug data --

zeus:~# opensc-tool -vvvvvv -f
sc.c:120:sc_detect_card_presence: called
reader-openct.c:193:openct_reader_detect_card_presence: called
sc.c:125:sc_detect_card_presence: returning with: 0
Card not present.
ctx.c:618:sc_release_context: called
reader-openct.c:171:openct_reader_release: called
reader-openct.c:171:openct_reader_release: called
reader-openct.c:171:openct_reader_release: called
reader-openct.c:171:openct_reader_release: called
reader-openct.c:171:openct_reader_release: called
reader-openct.c:157:openct_reader_finish: called


already thanks for the help,
  Marcel

Marcel Koopmans
Elysium Open Systems

_______________________________________________
opensc-user mailing list
[hidden email]
http://www.opensc.org/cgi-bin/mailman/listinfo/opensc-user
Reply | Threaded
Open this post in threaded view
|

Re: KOBIL mIDentity

Andreas Jellinghaus-2
On Tuesday 13 September 2005 20:32, Marcel Koopmans wrote:
> Now how do I do that under Linux?

so it is a smart card reader, and you need a driver.
did you install a driver? does anyone know if the
device is ccid compatible or not?

openct-tool list?
opensc-tool -l?
opensc-tool -n?
lsusb -vvv?

if none of those work, you could use a usb sniffer and generate
a log file where you use the smart card reader. many usb crypto
tokens are simple enough to write a driver using a log file.
so maybe you are lucky. see openct web page for a link to a
usb sniffing software.

Regards, Andreas
_______________________________________________
opensc-user mailing list
[hidden email]
http://www.opensc.org/cgi-bin/mailman/listinfo/opensc-user
Reply | Threaded
Open this post in threaded view
|

Re: KOBIL mIDentity

Ludovic Rousseau
In reply to this post by Marcel Koopmans-2
On 13/09/05, Marcel Koopmans <[hidden email]> wrote:
> Hello Everybody,

Hi,

> I am doing some tests with the mIDentity token itself.
>
> The device is an 128Mb drive and a smartcard reader.
> I know that under windows a service changes the device from a drive to both.
>
> Now how do I do that under Linux?

Have you contacted Kobil?

I have such a mIDentity token and it works with my CCID driver [1].
But the device has been preconfigured _before_ I received it.

Bye,

[1] http://pcsclite.alioth.debian.org/ccid.html
--
 Dr. Ludovic Rousseau
 For private mail use [hidden email] and not "big brother" Google
_______________________________________________
opensc-user mailing list
[hidden email]
http://www.opensc.org/cgi-bin/mailman/listinfo/opensc-user
Reply | Threaded
Open this post in threaded view
|

Re: KOBIL mIDentity

Marcel Koopmans-2
In reply to this post by Andreas Jellinghaus-2
Hello Andreas,

Thanks for the hints, I just got of the phone with Kobil.
I should just switch the functionality of the reader under Windows (
once ) and that should solve the issue.

Kobil will release version 1.5 of there software soon, it will have a
utility for linux i386 to do the switching.

with kind regards,
  Marcel

Marcel Koopmans
Elysium Open Systems

Andreas Jellinghaus wrote:

>On Tuesday 13 September 2005 20:32, Marcel Koopmans wrote:
>  
>
>>Now how do I do that under Linux?
>>    
>>
>
>so it is a smart card reader, and you need a driver.
>did you install a driver? does anyone know if the
>device is ccid compatible or not?
>
>openct-tool list?
>opensc-tool -l?
>opensc-tool -n?
>lsusb -vvv?
>
>if none of those work, you could use a usb sniffer and generate
>a log file where you use the smart card reader. many usb crypto
>tokens are simple enough to write a driver using a log file.
>so maybe you are lucky. see openct web page for a link to a
>usb sniffing software.
>
>Regards, Andreas
>
>.
>
>  
>

_______________________________________________
opensc-user mailing list
[hidden email]
http://www.opensc.org/cgi-bin/mailman/listinfo/opensc-user
Reply | Threaded
Open this post in threaded view
|

Re: KOBIL mIDentity

Marcel Koopmans-2
In reply to this post by Ludovic Rousseau
Good news, it works!

I installed the mIDentity software on Windows.
Within the software I was required to set PIN, PUK and create a
self-signed certificate.
After that was done I was able to change a setting of the token. Now by
default the device has the smartcard reader enabled.

But now my smartcard was no longer empty.
Well I got a windows tool from Kobil to erase the smartcard.
The tool is for internal use only and they do not want me to make it
public, so I will respect that!

Debug information...

zeus:~# lsusb
Bus 002 Device 006: ID 0d46:4000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 004: ID 05ac:0301 Apple Computer, Inc. iMac Mouse
[Mitsumi/Logitech]
Bus 001 Device 003: ID 05ac:0202 Apple Computer, Inc. Apple Keyboard [ALPS]
Bus 001 Device 002: ID 05ac:1001 Apple Computer, Inc. Apple Keyboard Hub
[ALPS]
Bus 001 Device 001: ID 0000:0000

The mIDentity is still seen as one device ( 0d46:4000 )
I have already told Kobil how to submit all there USD ID's so that Linux
knows what device it is.


zeus:~# opensc-tool -vvvvvv -f
sc.c:120:sc_detect_card_presence: called
sc.c:125:sc_detect_card_presence: returning with: 1
Connecting to card in reader KANN mIDentity 00 00...
card.c:346:sc_connect_card: called
reader-pcsc.c:406:pcsc_connect: Looking for a card_atr
3b:ba:96:00:81:31:86:5d:00:64:05:60:02:03:31:80:90:00:66
card.c:401:sc_connect_card: trying driver: Siemens CardOS
card.c:401:sc_connect_card: trying driver: Schlumberger Multiflex/Cryptoflex
card.c:401:sc_connect_card: trying driver: Schlumberger Cyberflex
card.c:401:sc_connect_card: trying driver: Gemplus GPK driver
card.c:401:sc_connect_card: trying driver: MioCOS 1.1 cards
card.c:401:sc_connect_card: trying driver: MICARDO 2.1
card.c:401:sc_connect_card: trying driver: Setec smartcards
card.c:401:sc_connect_card: trying driver: driver for STARCOS SPK 2.3 cards
card.c:401:sc_connect_card: trying driver: TCOS 2.0 cards
card.c:407:sc_connect_card: matched: TCOS 2.0 cards
card.c:431:sc_connect_card: returning with: 0
Using card driver TCOS 2.0 cards.
card.c:468:sc_lock: called
card.c:691:sc_select_file: called; type=2, path=3f00
card.c:229:sc_transmit_apdu: called
card.c:196:sc_transceive: Sending 8 bytes (resp. 260 bytes):
00 A4 00 00 02 3F 00 FF .....?..
card.c:249:sc_transmit_apdu: Received 33 bytes (SW1=90 SW2=00)
6F 1F 83 02 3F 00 82 01 38 85 01 01 84 05 D2 76 o...?...8......v
00 00 03 86 0C 60 00 00 00 FF FF A4 00 00 00 FF .....`..........
FF                                              .
card-tcos.c:337:tcos_process_fci: processing FCI bytes
card-tcos.c:343:tcos_process_fci:   file identifier: 0x3F00
card-tcos.c:370:tcos_process_fci:   shareable: no
card-tcos.c:390:tcos_process_fci:   type: DF
card-tcos.c:392:tcos_process_fci:   EF structure: 0
card-tcos.c:413:tcos_process_fci: File name: ?v???
card.c:713:sc_select_file: returning with: 0
3F00 [\xD2v\x00\x00\x03] type:  DF, size: 0
select[NONE] lock[NONE] delete[NONE] create[NONE] rehab[NONE]
inval[NONE] list[NONE] sec: 60:00:00:00:FF:FF:A4:00:00:00:FF:FF
prop: 01

card.c:514:sc_list_files: called
card.c:229:sc_transmit_apdu: called
card.c:196:sc_transceive: Sending 5 bytes (resp. 260 bytes):
80 AA 01 00 00 .....
card.c:249:sc_transmit_apdu: Received 0 bytes (SW1=6A SW2=82)
iso7816.c:98:iso7816_check_sw: File not found
card.c:229:sc_transmit_apdu: called
card.c:196:sc_transceive: Sending 5 bytes (resp. 260 bytes):
80 AA 02 00 00 .....
card.c:249:sc_transmit_apdu: Received 4 bytes (SW1=90 SW2=00)
44 00 2F 02 D./.
card.c:518:sc_list_files: returning with: 4
card.c:691:sc_select_file: called; type=2, path=3f004400
card.c:229:sc_transmit_apdu: called
card.c:196:sc_transceive: Sending 8 bytes (resp. 260 bytes):
00 A4 08 00 02 44 00 FF .....D..
card.c:249:sc_transmit_apdu: Received 43 bytes (SW1=90 SW2=00)
6F 29 83 02 44 00 81 02 00 1A 82 03 03 41 1A 85 o)..D........A..
06 01 C3 00 0C 05 05 86 12 DC 00 01 00 FF FF 82 ................
00 00 00 FF FF EE 00 00 00 FF FF                ...........
card-tcos.c:337:tcos_process_fci: processing FCI bytes
card-tcos.c:343:tcos_process_fci:   file identifier: 0x4400
card-tcos.c:349:tcos_process_fci:   bytes in file: 26
card-tcos.c:370:tcos_process_fci:   shareable: no
card-tcos.c:390:tcos_process_fci:   type: working EF
card-tcos.c:392:tcos_process_fci:   EF structure: 3
card.c:713:sc_select_file: returning with: 0
  3F00 4400 type: wEF, ef structure: linrfix(TLV), size: 26
  read[NONE] update[NONE] write[TERM] erase[NONE] rehab[N/A] inval[N/A]
sec: DC:00:01:00:FF:FF:82:00:00:00:FF:FF:EE:00:00:00:FF:FF
  prop: 01:C3:00:0C:05:05

card.c:691:sc_select_file: called; type=2, path=3f002f02
card.c:229:sc_transmit_apdu: called
card.c:196:sc_transceive: Sending 8 bytes (resp. 260 bytes):
00 A4 08 00 02 2F 02 FF ...../..
card.c:249:sc_transmit_apdu: Received 31 bytes (SW1=90 SW2=00)
6F 1D 83 02 2F 02 81 02 00 0C 82 01 01 85 02 01 o.../...........
02 86 0C B0 00 00 00 FF FF EE 00 00 00 FF FF    ...............
card-tcos.c:337:tcos_process_fci: processing FCI bytes
card-tcos.c:343:tcos_process_fci:   file identifier: 0x2F02
card-tcos.c:349:tcos_process_fci:   bytes in file: 12
card-tcos.c:370:tcos_process_fci:   shareable: no
card-tcos.c:390:tcos_process_fci:   type: working EF
card-tcos.c:392:tcos_process_fci:   EF structure: 1
card.c:713:sc_select_file: returning with: 0
  3F00 2F02 type: wEF, ef structure: transpnt, size: 12
  read[NONE] update[NONE] write[N/A] erase[NONE] rehab[N/A] inval[N/A]
sec: B0:00:00:00:FF:FF:EE:00:00:00:FF:FF
  prop: 01:02

card.c:563:sc_read_binary: called; 12 bytes at index 0
card.c:229:sc_transmit_apdu: called
card.c:196:sc_transceive: Sending 5 bytes (resp. 14 bytes):
00 B0 00 00 0C .....
card.c:249:sc_transmit_apdu: Received 12 bytes (SW1=90 SW2=00)
5A 0A 89 49 01 72 00 00 26 43 02 80 Z..I.r..&C..
iso7816.c:126:iso7816_read_binary: returning with: 12
card.c:594:sc_read_binary: returning with: 12
00000000: 5A 0A 89 49 01 72 00 00 26 43 02 80 Z..I.r..&C..
card.c:488:sc_unlock: called
card.c:493:sc_unlock: Calling card logout function
card.c:691:sc_select_file: called; type=2, path=3f00
card.c:229:sc_transmit_apdu: called
card.c:196:sc_transceive: Sending 8 bytes (resp. 260 bytes):
00 A4 00 00 02 3F 00 FF .....?..
card.c:249:sc_transmit_apdu: Received 33 bytes (SW1=90 SW2=00)
6F 1F 83 02 3F 00 82 01 38 85 01 01 84 05 D2 76 o...?...8......v
00 00 03 86 0C 60 00 00 00 FF FF A4 00 00 00 FF .....`..........
FF                                              .
card-tcos.c:501:hacked_iso7816_select_file: returning with: 0
card.c:713:sc_select_file: returning with: 0
card.c:443:sc_disconnect_card: called
card.c:458:sc_disconnect_card: returning with: 0
ctx.c:618:sc_release_context: called
reader-openct.c:171:openct_reader_release: called
reader-openct.c:171:openct_reader_release: called
reader-openct.c:171:openct_reader_release: called
reader-openct.c:171:openct_reader_release: called
reader-openct.c:171:openct_reader_release: called
reader-openct.c:157:openct_reader_finish: called


What I did also notice is that the device is seen as a "KANN mIDentity".
This should be "Kobil mIDentity" I had already posted this as a Debian
3.1 bug.

with kind regards,
  Marcel

Marcel Koopmans
Elysium Open Systems



Ludovic Rousseau wrote:

>On 13/09/05, Marcel Koopmans <[hidden email]> wrote:
>  
>
>>Hello Everybody,
>>    
>>
>
>Hi,
>
>  
>
>>I am doing some tests with the mIDentity token itself.
>>
>>The device is an 128Mb drive and a smartcard reader.
>>I know that under windows a service changes the device from a drive to both.
>>
>>Now how do I do that under Linux?
>>    
>>
>
>Have you contacted Kobil?
>
>I have such a mIDentity token and it works with my CCID driver [1].
>But the device has been preconfigured _before_ I received it.
>
>Bye,
>
>[1] http://pcsclite.alioth.debian.org/ccid.html
>  
>

_______________________________________________
opensc-user mailing list
[hidden email]
http://www.opensc.org/cgi-bin/mailman/listinfo/opensc-user