Bug#456459: Cannot find card with Rainbow iKey 3000

2007-12-16 Thread Ludovic Rousseau

Hello Martin,

Martin Michlmayr a écrit :

Package: libccid
Version: 1.3.1-1

I'm trying to use a Rainbow iKey 3000 (a USB device) but opensc says
Card not present.  This is with etch, but I also upgraded to libccid
1.3.1-1 and pcscd 1.4.4-3 from unstable (compiled manually on etch)
and I get the same.  It knows about the reader but claims it cannot
see the card:

3203:[EMAIL PROTECTED]: ~] sudo opensc-tool -l
Readers known about:
Nr.Driver Name
0  openct OpenCT reader (detached)
1  openct Rainbow iKey 3000
2  openct OpenCT reader (detached)
3  openct OpenCT reader (detached)
4  openct OpenCT reader (detached)


libccid is only used by pcsc-lite. OpenCT has its own CCID driver (with 
less features :-)



Bus 003 Device 004: ID 04b9:1300 Rainbow Technologies, Inc. iKey 3000 Token


This device is not yet support by libccid. Only 0x04B9:0x1400:SafeNet 
IKey4000


I am also the upstream author of libccid. Please follow the procedure on 
[1].



I know that other people are using the iKey 3000 successfully, but I
can only ask for details on Monday.  Maybe you have an idea what might
be wrong in the meantime (maybe simply a missing package?  I didn't
have libccid installed originally, but even now that I do it doesn't
work).


You can also try to use pcsc-lite instead of openct. But follow [1] for now.

Thanks,

[1] http://pcsclite.alioth.debian.org/ccid.html#CCID_compliant

--
 Dr. Ludovic Rousseau




Bug#456459: Cannot find card with Rainbow iKey 3000

2007-12-16 Thread Martin Michlmayr
Hi Ludovic,

* Ludovic Rousseau [EMAIL PROTECTED] [2007-12-16 09:38]:
 libccid is only used by pcsc-lite. OpenCT has its own CCID driver (with
 less features :-)

I don't really know anything about the difference between libccid,
pcsc and openct.  All of this is pretty new to me.  However, I just
tried pkcs15-tool --list-certifications (i.e. openct) and it works.
Actually, now opensc-tool -a also works.  Neither of these two worked
yesterday.  And ealier today it didn't work either... but after I
restarted all daemons it suddenly worked.  It seemed that openct
wasn't running.  But when I stop openct now, I do get an error message
that I didn't get before.  So I cannot quite explain what I saw
yesterday and ealier today.  But it seems to work now.

 You can also try to use pcsc-lite instead of openct. But follow [1]
 for now.

You want the output of src/parse, right?  It's attached.
-- 
Martin Michlmayr
http://www.cyrius.com/
 idVendor: 0x08FF
  iManufacturer: ?
 idProduct: 0x2580
  iProduct: Fingerprint Sensor
 bcdDevice: 6.23 (firmware release?)
 bLength: 9
 bDescriptorType: 4
 bInterfaceNumber: 0
 bAlternateSetting: 0
 bNumEndpoints: 2
  bulk-IN and bulk-OUT
 bInterfaceClass: 0xFF
  NOT A CCID DEVICE
  Class is 0xFF (proprietary)
 bInterfaceSubClass: 255
  UNSUPPORTED SubClass
 bInterfaceProtocol: 255
  UNSUPPORTED InterfaceProtocol
 iInterface: 0
USB extra length is too short: 0

  NOT A CCID DEVICE
 idVendor: 0x03F0
  iManufacturer: Broadcom Corp
 idProduct: 0x171D
  iProduct: HP Integrated Module
 bcdDevice: 1.00 (firmware release?)
 bLength: 9
 bDescriptorType: 4
 bInterfaceNumber: 2
 bAlternateSetting: 0
 bNumEndpoints: 2
  bulk-IN and bulk-OUT
 bInterfaceClass: 0xFF
  NOT A CCID DEVICE
  Class is 0xFF (proprietary)
 bInterfaceSubClass: 255
  UNSUPPORTED SubClass
 bInterfaceProtocol: 255
  UNSUPPORTED InterfaceProtocol
 iInterface: 0
USB extra length is too short: 0

  NOT A CCID DEVICE
 idVendor: 0x04B9
  iManufacturer: ?
 idProduct: 0x1300
  iProduct: iKey 3000 Series Token
 bcdDevice: 1.00 (firmware release?)
 bLength: 9
 bDescriptorType: 4
 bInterfaceNumber: 0
 bAlternateSetting: 0
 bNumEndpoints: 0
  Control only
 bInterfaceClass: 0xFF
  NOT A CCID DEVICE
  Class is 0xFF (proprietary)
 bInterfaceSubClass: 0
 bInterfaceProtocol: 0
  bulk transfer, optional interrupt-IN
 iInterface: 0
USB extra length is too short: 2

  NOT A CCID DEVICE


Bug#456459: Cannot find card with Rainbow iKey 3000

2007-12-15 Thread Martin Michlmayr
Package: libccid
Version: 1.3.1-1

I'm trying to use a Rainbow iKey 3000 (a USB device) but opensc says
Card not present.  This is with etch, but I also upgraded to libccid
1.3.1-1 and pcscd 1.4.4-3 from unstable (compiled manually on etch)
and I get the same.  It knows about the reader but claims it cannot
see the card:

3203:[EMAIL PROTECTED]: ~] sudo opensc-tool -l
Readers known about:
Nr.Driver Name
0  openct OpenCT reader (detached)
1  openct Rainbow iKey 3000
2  openct OpenCT reader (detached)
3  openct OpenCT reader (detached)
4  openct OpenCT reader (detached)
3204:[EMAIL PROTECTED]: ~] sudo  opensc-tool -a
Card not present.
zsh: exit 3 sudo opensc-tool -a
3206:[EMAIL PROTECTED]: ~] sudo opensc-tool -v -a
Card not present.
zsh: exit 3 sudo opensc-tool -v -a
3207:[EMAIL PROTECTED]: ~] sudo opensc-tool -v -a
sc.c:168:sc_detect_card_presence: called
reader-openct.c:207:openct_reader_detect_card_presence: called
sc.c:173:sc_detect_card_presence: returning with: 0
Card not present.
ctx.c:728:sc_release_context: called
reader-openct.c:180:openct_reader_release: called
reader-openct.c:180:openct_reader_release: called
reader-openct.c:180:openct_reader_release: called
reader-openct.c:180:openct_reader_release: called
reader-openct.c:180:openct_reader_release: called
reader-openct.c:165:openct_reader_finish: called
zsh: exit 3 sudo opensc-tool -v -a
3208:[EMAIL PROTECTED]: ~] lsusb
Bus 005 Device 001: ID :
Bus 004 Device 001: ID :
Bus 002 Device 010: ID 08ff:2580 AuthenTec, Inc.
Bus 002 Device 001: ID :
Bus 001 Device 012: ID 03f0:171d Hewlett-Packard
Bus 001 Device 001: ID :
Bus 003 Device 004: ID 04b9:1300 Rainbow Technologies, Inc. iKey 3000 Token
Bus 003 Device 001: ID :
3209:[EMAIL PROTECTED]: ~]

I know that other people are using the iKey 3000 successfully, but I
can only ask for details on Monday.  Maybe you have an idea what might
be wrong in the meantime (maybe simply a missing package?  I didn't
have libccid installed originally, but even now that I do it doesn't
work).

-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]