PCSCD Not reading Smart Card

[Wesley Nugent]

I've got PCSCD loaded and running, it sees my smart card reader, sees me
insert a card, but when I use a utility (the only one I have currently)
to try to read the card, I cannot read the card.

Let me explain a little. I work for a company that sells Point of Sale
Thin Client Stations. These Thin Client Stations have always run
busybox and have had an older version of pcscd running with some binary
utilities to read and write the card. I'm not sure where these
utilities came from, just they are called scard-read and scard-write.
They worked with this setup.

I'm doing development on a new thin client using Debian instead of
busybox. I unfortunately do not have the source code from the previous
binaries. The old terminals had a 2.4 kernel, the new one has 2.6.

I have done apt-get install pcscd and apt-get install libasedrive-usb.
/var/log/syslog shows the card. I run the scard-read, it shows:

Established context

Check the connected readers
reader=AseIIIeUSB 00 00
Please select reader from the list:


Then there is a blinking cursor. If I hit enter, I get segfault. If I
hit 0, 1, A, or type in AseIIIeUSB 00 00 it says The Specified reader
name is not recognized.

I'm willing to use any utility. I just need something to write 8
characters (1 - 8) and read those 8 characters back. It also needs to
be able to be run from a command line without Xwindows running.

Any suggestions on how I can resolve this issue, or another utility
would be greatly appreciated.


Wesley Nugent
--

[Ludovic Rousseau]

Post by Wesley Nugent
I've got PCSCD loaded and running, it sees my smart card reader, sees me
insert a card, but when I use a utility (the only one I have currently) to
try to read the card, I cannot read the card.
Let me explain a little. I work for a company that sells Point of Sale Thin
Client Stations. These Thin Client Stations have always run busybox and
have had an older version of pcscd running with some binary utilities to
read and write the card. I'm not sure where these utilities came from, just
they are called scard-read and scard-write. They worked with this setup.
I'm doing development on a new thin client using Debian instead of busybox.
I unfortunately do not have the source code from the previous binaries. The
old terminals had a 2.4 kernel, the new one has 2.6.

What is the version of pcscs-lite on the old terminals?
Use "pcscd -v"

Post by Wesley Nugent
I have done apt-get install pcscd and apt-get install libasedrive-usb.
Established context
Check the connected readers
reader=AseIIIeUSB 00 00
Then there is a blinking cursor. If I hit enter, I get segfault.

Can you use gdb to get a backtrace of the segfault?

Bye

[Wesley Nugent]

Post by Ludovic Rousseau

Post by Wesley Nugent
I've got PCSCD loaded and running, it sees my smart card reader, sees me
insert a card, but when I use a utility (the only one I have currently) to
try to read the card, I cannot read the card.
Let me explain a little. I work for a company that sells Point of Sale Thin
Client Stations. These Thin Client Stations have always run busybox and
have had an older version of pcscd running with some binary utilities to
read and write the card. I'm not sure where these utilities came from, just
they are called scard-read and scard-write. They worked with this setup.
I'm doing development on a new thin client using Debian instead of busybox.
I unfortunately do not have the source code from the previous binaries. The
old terminals had a 2.4 kernel, the new one has 2.6.

What is the version of pcscs-lite on the old terminals?
Use "pcscd -v"

old terminals: pcsc-lite version 1.1.1.

New terminal: pcsc-lite version 1.3.2

FYI, I tried using the old one on there but it said that it wasn't
running when I ran my read/write programs.

Post by Ludovic Rousseau

Post by Wesley Nugent
I have done apt-get install pcscd and apt-get install libasedrive-usb.
Established context
Check the connected readers
reader=AseIIIeUSB 00 00
Then there is a blinking cursor. If I hit enter, I get segfault.

Can you use gdb to get a backtrace of the segfault?
Bye

Ok, this is what I get:

(gdb) run /usr/local/bin/scard-read
Starting the program: /usr/local/bin/scard-read
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1209727296 (LWP 10210)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Established context

Check the connected readers
reader=AseIIIeUSB 00 00
Please select reader from the list:



waiting on status change!

Card Connect

Program received signal SIGSEGV. Segmentation Fault.
[Switching to Thread -1209727296 (LWP 10210)]
9xb7ec0463 in strlen () from /lib/tls/i686/cmov/libc.so.6
(gdb)


If I type in AseIIIeUSB taht I see, it shows:
Card Connect
The specified reader name is not recognized

Program exited normally
(gdb)


Thank you for the assistance.


--

[Wesley Nugent]

I finally got scriptor to work on the card (had to add lines to enable
RAW protocol) and it will connect to the card, but I cannot seem to find
what I need to type (It says reading commands from STDIN) to get it to
read / write to the card.

My end goal is to be able to write 12345678 and read it back from the card.

Post by Wesley Nugent

Post by Ludovic Rousseau

Post by Wesley Nugent
I've got PCSCD loaded and running, it sees my smart card reader, sees me
insert a card, but when I use a utility (the only one I have currently) to
try to read the card, I cannot read the card.
Let me explain a little. I work for a company that sells Point of Sale Thin
Client Stations. These Thin Client Stations have always run busybox and
have had an older version of pcscd running with some binary utilities to
read and write the card. I'm not sure where these utilities came from, just
they are called scard-read and scard-write. They worked with this setup.
I'm doing development on a new thin client using Debian instead of busybox.
I unfortunately do not have the source code from the previous binaries. The
old terminals had a 2.4 kernel, the new one has 2.6.

What is the version of pcscs-lite on the old terminals?
Use "pcscd -v"

old terminals: pcsc-lite version 1.1.1.
New terminal: pcsc-lite version 1.3.2
FYI, I tried using the old one on there but it said that it wasn't
running when I ran my read/write programs.

Post by Ludovic Rousseau

Post by Wesley Nugent
I have done apt-get install pcscd and apt-get install libasedrive-usb.
Established context
Check the connected readers
reader=AseIIIeUSB 00 00
Then there is a blinking cursor. If I hit enter, I get segfault.

Can you use gdb to get a backtrace of the segfault?
Bye

(gdb) run /usr/local/bin/scard-read
Starting the program: /usr/local/bin/scard-read
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1209727296 (LWP 10210)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Established context
Check the connected readers
reader=AseIIIeUSB 00 00
waiting on status change!
Card Connect
Program received signal SIGSEGV. Segmentation Fault.
[Switching to Thread -1209727296 (LWP 10210)]
9xb7ec0463 in strlen () from /lib/tls/i686/cmov/libc.so.6
(gdb)
Card Connect
The specified reader name is not recognized
Program exited normally
(gdb)
Thank you for the assistance.
--
------------------------------------------------------------------------
_______________________________________________
Muscle mailing list
http://lists.drizzle.com/mailman/listinfo/muscle

--

[Ludovic Rousseau]

Post by Wesley Nugent
(gdb) run /usr/local/bin/scard-read
Starting the program: /usr/local/bin/scard-read
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1209727296 (LWP 10210)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Established context
Check the connected readers
reader=AseIIIeUSB 00 00
waiting on status change!
Card Connect
Program received signal SIGSEGV. Segmentation Fault.
[Switching to Thread -1209727296 (LWP 10210)]
9xb7ec0463 in strlen () from /lib/tls/i686/cmov/libc.so.6
(gdb)

At this stage you need to enter "bt" or "backtrace" at the (gdb)
prompt to get a backtrace of the calls.

[Wesley Nugent]

Post by Ludovic Rousseau

Post by Wesley Nugent
(gdb) run /usr/local/bin/scard-read
Starting the program: /usr/local/bin/scard-read
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1209727296 (LWP 10210)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Established context
Check the connected readers
reader=AseIIIeUSB 00 00
waiting on status change!
Card Connect
Program received signal SIGSEGV. Segmentation Fault.
[Switching to Thread -1209727296 (LWP 10210)]
9xb7ec0463 in strlen () from /lib/tls/i686/cmov/libc.so.6
(gdb)

At this stage you need to enter "bt" or "backtrace" at the (gdb)
prompt to get a backtrace of the calls.

Sorry. Here is the rest of the info:

(gdb) backtrace
#0 0xb7e6e463 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7f4bbf7 in SCardConnect () from /usr/lib/libpcsclite.so.0
#2 0x08048c50 in ?? ()
(gdb)

--

[Ludovic Rousseau]

Post by Wesley Nugent
(gdb) backtrace
#0 0xb7e6e463 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7f4bbf7 in SCardConnect () from /usr/lib/libpcsclite.so.0
#2 0x08048c50 in ?? ()
(gdb)

Please recompile pcsc-lite with debug info (it should be the default).
And do not strip the installed library.

Also please use the latest pcsc-lite version. You are using 1.3.2 and
the latest version is 1.4.102

[Wesley Nugent]

Post by Ludovic Rousseau

Post by Wesley Nugent
(gdb) backtrace
#0 0xb7e6e463 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7f4bbf7 in SCardConnect () from /usr/lib/libpcsclite.so.0
#2 0x08048c50 in ?? ()
(gdb)

Please recompile pcsc-lite with debug info (it should be the default).
And do not strip the installed library.
Also please use the latest pcsc-lite version. You are using 1.3.2 and
the latest version is 1.4.102

Ok, I have no idea what I'm doing wrong. I uninstalled the old pcscd
and libasedrive-usb (that I had obtained through apt-get. I downloaded
the source, ./configure, make, make install on pcscd-lite,
libasedrive-usb, and ccid. I run /usr/local/sbin/pcscd (this is where
it installed on make install) and now it won't load my card. Says files
are missing and not looking in the directory where the drivers are
installed for libasedrive-usb. I tried apt-get install libasedrive-usb
since I nkow those work. Made sure I'm using the proper pcscd. I run
pcscd -f -d and see it detect my card.

I run scriptor or my scard-read or scard-write programs, none of them
work. Says:

winscard_msg.c:94:SHMClientSetupSessino() Error: connect to client
socket: Connection Refused

on scriptor I also get: Could not create Chipcard::PCSC object: Service
not available

On my program, I get: The smart card resource manager is not running.

Did I miss something while compiling pcsc-lite v 1.4.102?

--

[Wesley Nugent]

Post by Wesley Nugent

Post by Ludovic Rousseau

Post by Wesley Nugent
(gdb) backtrace
#0 0xb7e6e463 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7f4bbf7 in SCardConnect () from /usr/lib/libpcsclite.so.0
#2 0x08048c50 in ?? ()
(gdb)

Please recompile pcsc-lite with debug info (it should be the default).
And do not strip the installed library.
Also please use the latest pcsc-lite version. You are using 1.3.2 and
the latest version is 1.4.102

Ok, I have no idea what I'm doing wrong. I uninstalled the old pcscd
and libasedrive-usb (that I had obtained through apt-get. I
downloaded the source, ./configure, make, make install on pcscd-lite,
libasedrive-usb, and ccid. I run /usr/local/sbin/pcscd (this is where
it installed on make install) and now it won't load my card. Says
files are missing and not looking in the directory where the drivers
are installed for libasedrive-usb. I tried apt-get install
libasedrive-usb since I nkow those work. Made sure I'm using the
proper pcscd. I run pcscd -f -d and see it detect my card.
I run scriptor or my scard-read or scard-write programs, none of them
winscard_msg.c:94:SHMClientSetupSessino() Error: connect to client
socket: Connection Refused
Service not available
On my program, I get: The smart card resource manager is not running.
Did I miss something while compiling pcsc-lite v 1.4.102?

Ok, I went back to a copy of the image I'm using for development to
before I started working on the smart card (I had installed and
uninstalled via apt many packages and couldn't ensure all were gone). I
downloaded the source code and recompiled.

Now I get winscard_clnt.c:3232:SCardCheckDaemonAvailablity() PCSC Not
Running, and yet I can clearly see /usr/local/sbin/pcscd running in ps
-ef and showing the debug info in the foreground on my console.

Please advise what flag I may have missed or startup option to get it to
run in daemon mode.

[Ludovic Rousseau]

Ok, I went back to a copy of the image I'm using for development to before I
started working on the smart card (I had installed and uninstalled via apt
many packages and couldn't ensure all were gone). I downloaded the source
code and recompiled.
Now I get winscard_clnt.c:3232:SCardCheckDaemonAvailablity() PCSC Not
Running, and yet I can clearly see /usr/local/sbin/pcscd running in ps -ef
and showing the debug info in the foreground on my console.
Please advise what flag I may have missed or startup option to get it to run
in daemon mode.

Your application is using /usr/lib/libpcsclite.so but the newly
compiled pcsc-lite installed the lib in /usr/local/lib/libpcsclite.so

If you use .deb packages you should backport the Debian/testing
package of pcsclite 1.4.102 and then only use .deb packages on your
system.

If you really want to configure by hand the Debian package is configured as:
./configure \
--sysconfdir=/etc \
--prefix=/usr \
--enable-usbdropdir=/usr/lib/pcsc/drivers

Bye

[Wesley Nugent]

Ok, this got it running and I'm able to connect now. I still get a seg
fault when I try to run my read or write programs. What happens, it
says please select reader from the list. If I hit enter, I get
segfault, if I type anything in, it doesn't recognize the reader. I did
a gdb with backtrace and get:

#0 0xb7e2e463 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7f0c457 in SCardConnect (hContext=16996003,
szReader=0x1000 <Address 0x1000 out of bounds>, dwShareMode=2,
dwPreferredProtocols=4, phCard=0xbf9e1758, pdwActiveProtocol=0xbf9e12f8
at winscard_clnt.c:745
#2 0x08048c50 in ?? ()

On a side note, I do have scriptor installed and can connect to the
smart card reader using scriptor. It uses RAW protocol and comes up
says reading commands from STDIN.

Unfortunately, I don't know what commands to give it. If you could
point me to the commands to read and write in raw mode, or where I can
find these commands, I would appreciate it. Either help with the
segfault or the commands to read/write with scriptor in RAW mode would
be of great benefit to me.


Thank you for all of your help.

Wesley

Post by Ludovic Rousseau

Ok, I went back to a copy of the image I'm using for development to before I
started working on the smart card (I had installed and uninstalled via apt
many packages and couldn't ensure all were gone). I downloaded the source
code and recompiled.
Now I get winscard_clnt.c:3232:SCardCheckDaemonAvailablity() PCSC Not
Running, and yet I can clearly see /usr/local/sbin/pcscd running in ps -ef
and showing the debug info in the foreground on my console.
Please advise what flag I may have missed or startup option to get it to run
in daemon mode.

Your application is using /usr/lib/libpcsclite.so but the newly
compiled pcsc-lite installed the lib in /usr/local/lib/libpcsclite.so
If you use .deb packages you should backport the Debian/testing
package of pcsclite 1.4.102 and then only use .deb packages on your
system.
./configure \
--sysconfdir=/etc \
--prefix=/usr \
--enable-usbdropdir=/usr/lib/pcsc/drivers
Bye

--

[Wesley Nugent]

Well, through trial and error, I found out that my program was looking
for the letter e to select the proper smart card. I have no idea why,
but I updated my scripts and it is now reading and writing. Thank you
for all of your help.

I'm still interested in references to scriptor as I don't want to rely
solely on the program that I don't have any source for from a previous
developer.

Thanks again.

Wesley

Post by Wesley Nugent
Ok, this got it running and I'm able to connect now. I still get a seg
fault when I try to run my read or write programs. What happens, it
says please select reader from the list. If I hit enter, I get
segfault, if I type anything in, it doesn't recognize the reader. I did
#0 0xb7e2e463 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7f0c457 in SCardConnect (hContext=16996003,
szReader=0x1000 <Address 0x1000 out of bounds>, dwShareMode=2,
dwPreferredProtocols=4, phCard=0xbf9e1758,
pdwActiveProtocol=0xbf9e12f8
at winscard_clnt.c:745
#2 0x08048c50 in ?? ()
On a side note, I do have scriptor installed and can connect to the
smart card reader using scriptor. It uses RAW protocol and comes up
says reading commands from STDIN.
Unfortunately, I don't know what commands to give it. If you could
point me to the commands to read and write in raw mode, or where I can
find these commands, I would appreciate it. Either help with the
segfault or the commands to read/write with scriptor in RAW mode would
be of great benefit to me.
Thank you for all of your help.
Wesley

Post by Ludovic Rousseau

Ok, I went back to a copy of the image I'm using for development to before I
started working on the smart card (I had installed and uninstalled via apt
many packages and couldn't ensure all were gone). I downloaded the source
code and recompiled.
Now I get winscard_clnt.c:3232:SCardCheckDaemonAvailablity() PCSC Not
Running, and yet I can clearly see /usr/local/sbin/pcscd running in ps -ef
and showing the debug info in the foreground on my console.
Please advise what flag I may have missed or startup option to get it to run
in daemon mode.

Your application is using /usr/lib/libpcsclite.so but the newly
compiled pcsc-lite installed the lib in /usr/local/lib/libpcsclite.so
If you use .deb packages you should backport the Debian/testing
package of pcsclite 1.4.102 and then only use .deb packages on your
system.
If you really want to configure by hand the Debian package is
./configure \
--sysconfdir=/etc \
--prefix=/usr \
--enable-usbdropdir=/usr/lib/pcsc/drivers
Bye

--

[Ludovic Rousseau]

Well, through trial and error, I found out that my program was looking for
the letter e to select the proper smart card. I have no idea why, but I
updated my scripts and it is now reading and writing. Thank you for all of
your help.

Start pcscd as "pcscd --apdu --forground" to list the APDU used by
your closed source programs.
Once you have the list of APDU used and you anderstand the format of
the parameters you can start writing an equivalent in the language of
your choice.

I'm still interested in references to scriptor as I don't want to rely
solely on the program that I don't have any source for from a previous
developer.

scriptor does not provide a programming language. It can just send a
static list of APDU and can't even use the answers from the card.

The winscard (or PC/SC API) can be used from a large variety of
languages on Unix. Just choose one.

Bye

[Ludovic Rousseau]

Post by Wesley Nugent
Ok, this got it running and I'm able to connect now. I still get a seg
fault when I try to run my read or write programs. What happens, it
says please select reader from the list. If I hit enter, I get
segfault, if I type anything in, it doesn't recognize the reader. I did
#0 0xb7e2e463 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7f0c457 in SCardConnect (hContext=16996003,
szReader=0x1000 <Address 0x1000 out of bounds>, dwShareMode=2,
dwPreferredProtocols=4, phCard=0xbf9e1758, pdwActiveProtocol=0xbf9e12f8
at winscard_clnt.c:745
#2 0x08048c50 in ?? ()

SCardConnect() is called with szReader=0x1000. szReader is supposed to
be a pointer to a C string containing the reader name to use.
It is clear that your application is using a wrong value here and can
only crash.

I am surprised your application ever worked.

Post by Wesley Nugent
On a side note, I do have scriptor installed and can connect to the
smart card reader using scriptor. It uses RAW protocol and comes up
says reading commands from STDIN.
Unfortunately, I don't know what commands to give it. If you could
point me to the commands to read and write in raw mode, or where I can
find these commands, I would appreciate it. Either help with the
segfault or the commands to read/write with scriptor in RAW mode would
be of great benefit to me.

I think you will have to reverse engineer the scard-read and
scard-write program (since you do not have the source code) and
rewrite them.

The --apdu pcscd option to log the apdu exchanged was introduced in
pcsc-lite 1.1.2beta1 and your "working" configuration is using
pcsc-lite 1.1.1. So it will not be easy to get the exchanged APDU.

Good luck,

[Wesley Nugent]

Any suggestions on getting scriptor to read and write to the card?

I am somewhat new to reverse engineering, and honestly don't know where
to begin. I do know a little about bash scripting and have hacked some
perl programs before and minor C. I've only had programming training
with 1 class in Java. Nowhere near the level of ability as people such
as yourself.

I have gotten it to read but would like to use scriptor if I can find
out what commands to give to read and write the card.

Thanks for all your help.

Wesley

Post by Ludovic Rousseau

Post by Wesley Nugent
Ok, this got it running and I'm able to connect now. I still get a seg
fault when I try to run my read or write programs. What happens, it
says please select reader from the list. If I hit enter, I get
segfault, if I type anything in, it doesn't recognize the reader. I did
#0 0xb7e2e463 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7f0c457 in SCardConnect (hContext=16996003,
szReader=0x1000 <Address 0x1000 out of bounds>, dwShareMode=2,
dwPreferredProtocols=4, phCard=0xbf9e1758, pdwActiveProtocol=0xbf9e12f8
at winscard_clnt.c:745
#2 0x08048c50 in ?? ()

SCardConnect() is called with szReader=0x1000. szReader is supposed to
be a pointer to a C string containing the reader name to use.
It is clear that your application is using a wrong value here and can
only crash.
I am surprised your application ever worked.

Post by Wesley Nugent
On a side note, I do have scriptor installed and can connect to the
smart card reader using scriptor. It uses RAW protocol and comes up
says reading commands from STDIN.
Unfortunately, I don't know what commands to give it. If you could
point me to the commands to read and write in raw mode, or where I can
find these commands, I would appreciate it. Either help with the
segfault or the commands to read/write with scriptor in RAW mode would
be of great benefit to me.

I think you will have to reverse engineer the scard-read and
scard-write program (since you do not have the source code) and
rewrite them.
The --apdu pcscd option to log the apdu exchanged was introduced in
pcsc-lite 1.1.2beta1 and your "working" configuration is using
pcsc-lite 1.1.1. So it will not be easy to get the exchanged APDU.
Good luck,

--

[Wesley Nugent]

Ok, this got it running and I'm able to connect now. I still get a seg
fault when I try to run my read or write programs. What happens, it
says please select reader from the list. If I hit enter, I get
segfault, if I type anything in, it doesn't recognize the reader. I did
a gdb with backtrace and get:

#0 0xb7e2e463 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7f0c457 in SCardConnect (hContext=16996003,
szReader=0x1000 <Address 0x1000 out of bounds>, dwShareMode=2,
dwPreferredProtocols=4, phCard=0xbf9e1758, pdwActiveProtocol=0xbf9e12f8
at winscard_clnt.c:745
#2 0x08048c50 in ?? ()

On a side note, I do have scriptor installed and can connect to the
smart card reader using scriptor. It uses RAW protocol and comes up
says reading commands from STDIN.

Unfortunately, I don't know what commands to give it. If you could
point me to the commands to read and write in raw mode, or where I can
find these commands, I would appreciate it. Either help with the
segfault or the commands to read/write with scriptor in RAW mode would
be of great benefit to me.


Thank you for all of your help.

Wesley

Post by Ludovic Rousseau

Ok, I went back to a copy of the image I'm using for development to before I
started working on the smart card (I had installed and uninstalled via apt
many packages and couldn't ensure all were gone). I downloaded the source
code and recompiled.
Now I get winscard_clnt.c:3232:SCardCheckDaemonAvailablity() PCSC Not
Running, and yet I can clearly see /usr/local/sbin/pcscd running in ps -ef
and showing the debug info in the foreground on my console.
Please advise what flag I may have missed or startup option to get it to run
in daemon mode.

Your application is using /usr/lib/libpcsclite.so but the newly
compiled pcsc-lite installed the lib in /usr/local/lib/libpcsclite.so
If you use .deb packages you should backport the Debian/testing
package of pcsclite 1.4.102 and then only use .deb packages on your
system.
./configure \
--sysconfdir=/etc \
--prefix=/usr \
--enable-usbdropdir=/usr/lib/pcsc/drivers
Bye

--