problem with etoken 32K

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.

------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/rdesktop-users

# Configuration file for pcsc-lite
#
# Don't modify this file. Instead put a file or modify the files in
# /etc/reader.conf.d/ and run /usr/sbin/update-reader.conf
# afterwards.  Note that when starting pcscd with the init script,
# update-reader.conf will be run automatically.
#
# Note also that this file should include configuration for serial and PCMCIA
# readers only; USB readers should _not_ be configured here.

# /etc/reader.conf.d/openct.conf
FRIENDLYNAME     "OpenCT"
DEVICENAME       /dev/null
LIBPATH          /lib/openct-ifd.so
CHANNELID        0


# End of file

# Set debug level
debug	= 8;
#
# Enable hot plugging
hotplug	= yes;

#
# Path to ifdhandler
ifdhandler {
	program		= //sbin/ifdhandler;
#	user		= openctd;
#	groups = {
#		usb,
#	};
};

#
# Configuration for ifdproxy (if you use it)
ifdproxy {
#	server-port     = //var/run/openct/.ifdproxy,
#	device-port     = :6666;
};

# Configure static, non-hotplug aware readers here
#
# For a list of drivers try command 'ifdhandler -i', please
# notice that not all drivers have serial device capability.

#reader towitoko {
#	driver = towitoko;
#	device = serial:/dev/ttyS0;
#};

#reader gempc {
#	driver = gempc;
#	device = serial:/dev/ttyS0;
#};

reader cm4000 {
	driver = cm4000;
	device = pcmcia:/dev/cmm0;
};

#reader cm4040 {
#	driver = ccid;
#	device = pcmcia_block:/dev/cmx0;
#};

#reader pertosmart1030 {
#	driver = pertosmart1030;
#	device = serial:/dev/ttyS0;
#};

#
# Hotplug IDs
driver	egate {
	ids = {
		usb:0973/0001,
	};
};
driver	etoken {
	ids = {
		usb:0529/050c,
		usb:0529/0514,
		usb:0529/0600,
	};
};
driver	etoken64 {
	ids = {
		usb:0529/0700,
	};
};
driver	eutron {
	ids = {
		usb:073d/0005,
	};
};
driver	ikey2k {
	ids = {
		usb:04b9/1202,
	};
};
driver	ikey3k {
	ids = {
		usb:04b9/1300,
	};
};
driver	starkey {
	ids = {
		usb:096e/0005,
	};
};
driver	cardman {
	ids = {
#		usb:076b/0596, # OMNIKEY CardMan 2020
#		usb:076b/1784, # OMNIKEY CardMan 6020
#		usb:08d4/0009, # Fujitsu Siemens SCR USB Reader
	};
};
driver	ccid {
	ids = {
		usb:03f0/1024,	# HP Keyboard with CCID reader
		usb:046a/0010,	# Cherry smartboard G83-6744
		usb:04e6/5115,
		usb:04e6/5116,
		usb:04e6/5117,	# SCM Micro token size reader
		usb:04e6/511d,	# SCM Micro SCR3311
		usb:04e6/E001,
		usb:04e6/E003,
		usb:073d/0c00,	# Eutron SimPocket (doesn't work yet)
		usb:076b/1021,  # OmniKey CardMan 1021
		usb:076b/3021,
		usb:076b/5121,
		usb:076b/5321,	# OmniKey CardMan 5321
		usb:076b/6622,	# OmniKey CardMan 6121
		usb:0783/0003,
		usb:08e6/3437,	# Gemplus
		usb:08e6/3438,	# Gemplus GemPC Key SmartCard Reader
		usb:08e6/4433,	# Gemplus
		usb:0b97/7762,	# O2 Micro, Inc. Oz776 SmartCard Reader 
		usb:0b97/7772,	# O2 Micro, Inc. Oz776 SmartCard Reader 
		usb:0bf8/1006,	# fujitsu siemens 3.5" drive size reader
		usb:0dc3/1004,	# Athena Smartcard Solutions, Inc. ASEKey
	};
};
driver pertosmart1030 {
	ids = {
		usb:072f/0001,
		usb:072f/8009,
	};
};
driver pertosmart1038 {
	ids = {
		usb:072f/9000,
		usb:072f/9006, # ACS CryptoMate Token
		usb:072f/9007, # ACS ACR 100 SIMFlash
		usb:072f/90d0,
	};
};
#driver wbeiuu {	#	driver not working yet
#	ids = {
#		usb:104f/0004,
#	};
#};

# Tested with USBID 0c4b:0100. These are red readers: one with LCD, 
# another one without. 
driver cyberjack {
	ids = {
		usb:0c4b/0100,
	};
};
driver rutoken {
	ids = {
		usb:0a89/0020,
	};
};