How to configure openct to make etoken work properly while doing rdesktop

DarkKnight BrightWarrior <[email protected]>
Newsgroups gmane.network.rdesktop.user
Message-ID <[email protected]>
hai!

I am using customized linux distro with following packages.
pcsc-lite-1.4.0
openct 0.6.15
opensc- 0.11.6
I am using etoken 64K smartcard.

By refering openct quickstart I made some configurations. ( I am attaching
my /etc/openct.conf and /etc/reader.conf files. )

After Configuration When I open etoken properties window I can see two
entries, one is openCT 00 00 (which is symbol of reader without card) and
other is etoken (etoken symbol). I am attaching screenshot of etoken
properties window.

When I attach etoken and run pkcs11-tool --module /usr/lib/libeTPkcs11.so -L
, I can see Slot 0 is etoken and remaining slots are empty.

Now comes the problem,
When I do the rdesktop -r scard server-address with smart card attached, 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".
When I do rdesktop -r scard:"eToken PRO 00 00"="AKS ifdh 0" server-address,
It is asking for PIN and working fine. But by this command also it is
working only when connecting to a windows 2003 server and not working when
connecting to windows xp machine.

I think the empty openct reader showing in etoken properties window is
causing these problems. Is there a way so that I can show only etoken entry
and hide/doesn't show openct entry.
I also seen somewhere on net, etoken properties window showing two entries
one is openct reader with smartcard (etoken) and the other is actual etoken.
Is that what it should look like?

Please check my configuration files and tell me necessary changes for proper
functioning.

Thanks a lot.

------------------------------------------------------------------------------
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
reader.conf (application/octet-stream, 795 B)
# 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/reader.conf
# Configuration file for pcsc-lite
#
# This file has to be configured for serial and PCMCIA readers only.
# normal USB readers shall _not_ be configured here!
#
# David Corcoran <[email protected]>

FRIENDLYNAME     "OpenCT"
DEVICENAME       /dev/null
LIBPATH          /lib/openct-ifd.so
CHANNELID        0

# End of file

# End of file
openct.conf (application/octet-stream, 2.7 KB)
# Set debug level
debug	= 0;
#
# 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,
	};
};
driver	etoken64 {
	ids = {
		usb:0529/0600,
		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,
	};
};
etoken-properties-window-screenshot1.JPG (image/jpeg, 17.9 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.