[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rdesktop-users
Subject:    [rdesktop-users] problem with etoken 32K
From:       DarkKnight BrightWarrior <bindasbeast () gmail ! com>
Date:       2009-02-28 11:34:48
Message-ID: 68cead810902280322k13e83d4ci214dffe1bc0a346d () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hai!

I am using eToken PRO 32K ( 0529/0600 - vendor/product).

I am using combination of openct-0.6.15 and opensc-0.11.6 (no pcsc, no
aladdin middleware). I am using kernel 2.6.25 and udev 135. I am using udev
to detect usb events. I think hotplugging is working fine as I can see "
ifhandler -H etoken usb /proc/bus/usb/002/005" command running in "ps"
appearing/disappearing when I plug/unplug etoken.

I am using etoken 32k but its vendor/product  0529/0600 are matched with
etoken64 driver according to default /etc/openct.conf. So I moved that entry
from etoken64 to etoken driver in openct.conf.

I can see info of etoken using commands,

#openct-tool list
0 Aladdin etoken PRO

#openct-tool atr
Detected Aladdin eToken PRO
Card present, status changed
ATR: 3b f2 18 00 02 c1 0a 31 fe 58 c8 09 75

#cardos-info
 3b:f2:18:00:02:c1:0a:31:fe:58:c8:09:75

Info : CardOS V4.2B (C) Siemens AG 1994-2005
Chip type: 123
Serial number: 27 92 77 05 23 27
Full prom dump:
33 66 00 45 CB CB CB CB 7B FF 27 92 77 05 23 27 3f.E....{.'.w.#'
00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 ................
OS Version: 200.9 (that's CardOS M4.2b)
Current life cycle: 32 (administration)
Security Status of current DF:
Free memory : 1024
ATR Status: 0x0 ROM-ATR
Packages installed:
Ram size: 4, Eeprom size: 32, cpu type: 66, chip config: 63
Free eeprom memory: 27686
System keys: PackageLoadKey (version 0xfe, retries 10)
System keys: StartKey (version 0xff, retries 10)
Path to current DF:

Now comes the problem:


I am observing /var/log/messages. I can see message intialization failed (
driver etoken).
Here is the log of messages when I connect etoken.

Feb 27 17:00:38 (none) user.err kernel: hub 1-0:1.0: unable to enumerate USB
device on port 4
Feb 27 17:00:39 (none) user.info kernel: usb 2-4: new full speed USB device
using ohci_hcd and address 4
Feb 27 17:00:39 (none) user.info kernel: usb 2-4: configuration #1 chosen
from 1 choice
Feb 27 17:00:39 (none) daemon.debug ifdhandler[1093]: ifd_open: trying to
open etoken@usb:/proc/bus/usb/002/004
Feb 27 17:00:39 (none) daemon.debug ifdhandler[1093]: usb_set_params:
called. config xffffffff ifc x00 eps xffffffff/xffffffff
Feb 27 17:00:39 (none) daemon.debug ifdhandler[1093]:
ifdhandler_poll_presence: card status change: 0 -> 1
Feb 27 17:00:39 (none) daemon.debug ifdhandler[1101]: ifd_open: trying to
open etoken@usb:/proc/bus/usb/002/004
Feb 27 17:00:39 (none) daemon.debug ifdhandler[1101]: usb_set_params:
called. config xffffffff ifc x00 eps xffffffff/xffffffff
Feb 27 17:00:39 (none) daemon.warn ifdhandler[1101]: usb_claiminterface
failed: Device or resource busy
Feb 27 17:00:39 (none) daemon.warn ifdhandler[1101]: etoken: setting
parameters failed
Feb 27 17:00:39 (none) daemon.warn ifdhandler[1101]:
usb:/proc/bus/usb/002/004: initialization failed (driver etoken)
Feb 27 17:00:39 (none) daemon.warn ifdhandler[1101]: unable to open reader
etoken usb /proc/bus/usb/002/004

Then I installed pcsc-lite and configured /etc/reader.conf to load openct
reader.

I run pcscd -afd and observing the messages. If I connect token for the
first time everything seems fine but when I unplug and plug the token I can
see error message "eventhandler.c:443:EHStatusHandlerThread() Error powering
up card." This error is coming every time I plug the token except first time
plugging after pcscd start.

When I do the rdesktop -r scard server-address with smart card attached, It
is asking for PIN, when I unplug token it is showing login screen and when I
replug the token it is not asking for PIN rather it is showing error message
" The card supplied was not recognized. Please check that card is inserted
correctly and fits rightly".
Means the PIN asked only for the first time and whenever I unplug ad plug
the token it is giving a error rather than asking PIN.

please help

I am attaching my /etc/reader.conf, /etc/openct.conf.

Thank you.

[Attachment #5 (text/html)]

<p>Hai!<br> <br>I am using eToken PRO 32K ( 0529/0600 - vendor/product). </p>
<p>I am using combination of openct-0.6.15 and opensc-0.11.6 (no pcsc, no aladdin \
middleware). I am using kernel 2.6.25 and udev 135. I am using udev to detect usb \
events. I think hotplugging is working fine as I can see &quot; ifhandler -H etoken \
usb /proc/bus/usb/002/005&quot; command running in &quot;ps&quot; \
appearing/disappearing when I plug/unplug etoken.</p>

<p>I am using etoken 32k but its vendor/product  0529/0600 are matched with etoken64 \
driver according to default /etc/openct.conf. So I moved that entry from etoken64 to \
etoken driver in openct.conf.<br> <br>I can see info of etoken using commands,</p>

<p>#openct-tool list<br>0 Aladdin etoken PRO<br> <br>#openct-tool atr<br>Detected \
Aladdin eToken PRO<br>Card present, status changed <br>ATR: 3b f2 18 00 02 c1 0a 31 \
fe 58 c8 09 75<br> <br>#cardos-info<br> 3b:f2:18:00:02:c1:0a:31:fe:58:c8:09:75</p>

<p>Info : CardOS V4.2B (C) Siemens AG 1994-2005<br>Chip type: 123<br>Serial number: \
27 92 77 05 23 27<br>Full prom dump:<br>33 66 00 45 CB CB CB CB 7B FF 27 92 77 05 23 \
27 3f.E....{.&#39;.w.#&#39;<br>00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 \
................<br> OS Version: 200.9 (that&#39;s CardOS M4.2b)<br>Current life \
cycle: 32 (administration)<br>Security Status of current DF:<br>Free memory : \
1024<br>ATR Status: 0x0 ROM-ATR<br>Packages installed:<br>Ram size: 4, Eeprom size: \
32, cpu type: 66, chip config: 63<br> Free eeprom memory: 27686<br>System keys: \
PackageLoadKey (version 0xfe, retries 10)<br>System keys: StartKey (version 0xff, \
retries 10)<br>Path to current DF:</p> <p>Now comes the problem:<br> <br> <br>I am \
observing /var/log/messages. I can see message intialization failed ( driver etoken). \
<br>Here is the log of messages when I connect etoken.<br> <br>Feb 27 17:00:38 (none) \
user.err kernel: hub 1-0:1.0: unable to enumerate USB device on port 4<br> Feb 27 \
17:00:39 (none) <a href="http://user.info">user.info</a> kernel: usb 2-4: new full \
speed USB device using ohci_hcd and address 4<br>Feb 27 17:00:39 (none) <a \
href="http://user.info">user.info</a> kernel: usb 2-4: configuration #1 chosen from 1 \
choice<br> Feb 27 17:00:39 (none) daemon.debug ifdhandler[1093]: ifd_open: trying to \
open <a href="mailto:etoken@usb:/proc/bus/usb/002/004">etoken@usb:/proc/bus/usb/002/004</a><br>Feb \
27 17:00:39 (none) daemon.debug ifdhandler[1093]: usb_set_params: called. config \
xffffffff ifc x00 eps xffffffff/xffffffff<br> Feb 27 17:00:39 (none) daemon.debug \
ifdhandler[1093]: ifdhandler_poll_presence: card status change: 0 -&gt; 1<br>Feb 27 \
17:00:39 (none) daemon.debug ifdhandler[1101]: ifd_open: trying to open <a \
href="mailto:etoken@usb:/proc/bus/usb/002/004">etoken@usb:/proc/bus/usb/002/004</a><br>
 Feb 27 17:00:39 (none) daemon.debug ifdhandler[1101]: usb_set_params: called. config \
xffffffff ifc x00 eps xffffffff/xffffffff<br>Feb 27 17:00:39 (none) daemon.warn \
ifdhandler[1101]: usb_claiminterface failed: Device or resource busy<br> Feb 27 \
17:00:39 (none) daemon.warn ifdhandler[1101]: etoken: setting parameters \
failed<br>Feb 27 17:00:39 (none) daemon.warn ifdhandler[1101]: \
usb:/proc/bus/usb/002/004: initialization failed (driver etoken)<br>Feb 27 17:00:39 \
(none) daemon.warn ifdhandler[1101]: unable to open reader etoken usb \
/proc/bus/usb/002/004</p>

<p>Then I installed pcsc-lite and configured /etc/reader.conf to load openct \
reader.</p> <p>I run pcscd -afd and observing the messages. If I connect token for \
the first time everything seems fine but when I unplug and plug the token I can see \
error message &quot;eventhandler.c:443:EHStatusHandlerThread() Error powering up \
card.&quot; This error is coming every time I plug the token except first time \
plugging after pcscd start.</p>

<div> </div>
<div>When I do the rdesktop -r scard server-address with smart card attached, It is \
asking for PIN, when I unplug token it is showing login screen and when I replug the \
token it is not asking for PIN rather it is showing error message &quot; The card \
supplied was not recognized. Please check that card is inserted correctly and fits \
rightly&quot;.  </div>

<div>Means the PIN asked only for the first time and whenever I unplug ad plug the \
token it is giving a error rather than asking PIN.</div> <div> </div>
<div>please help</div>
<div><br>I am attaching my /etc/reader.conf, /etc/openct.conf.</div>
<p>Thank you.<br> </p>

--001636e0a774259f630463f8ce63--


["reader.conf" (application/octet-stream)]
["openct.conf" (application/octet-stream)]

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H

_______________________________________________
rdesktop-users mailing list
rdesktop-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rdesktop-users


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic