(Windows is the only platform they currently support :-( ).
I'm available to make a Java (native) interface to a Linux C library or
try to migrate the whole towitoko software to Java, so it would run over every
platform supporting Java.
Carlos Prados.
Java developer
will be a difficulty to install the driver. Any ideas
are welcomed.
The modified source code is in
ftp://apolonio.atos-ods.es/pub/musclecard/mini.tar.gz
Thanks,
Carlos Prados.
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement
the status (card insterted / no card inserted).
Now I'm working on I2C memory card read/write commands. Help is welcomed
Last version of modified source code is in
ftp://apolonio.atos-ods.es/pub/musclecard/mini.tar.gz
Thanks,
Carlos Prados
and only P1
and P2 bytes.
The card I'm using for testing is an "Euro 6000" Spanish purse card. It
complies with ISO 7816. What standard does musclecard generated APDU's
complies with?
Thanks,
Carlos Prados.
***
Linux Smart Card
are using Kartenzwerg please make sure you have
a modern one. There are some old Kartenzewrg readers that works with
a distinct comunication protocol, that Towitoko doest want to make
public and won't be supported in the future.
Thanks,
Carlos Prados.
Gregor,
Would it be against OSI model if we put the IO parameters in a config
file? I think this is better from a practical point of view than having
two diferent shared libraries for two identical (except the IO
initialization parameters) readers.
This config file could be the same we use to
David Timothy Corcoran wrote:
There is a version of xcard for the CT-API which Carlos Prados has done.
This should probably work with the CT-API for your reader. I need to get
some links on the web site to this. Please send me your links and I'll
put them on the site.
Thanks
Dave
All
David Timothy Corcoran wrote:
There is a version of xcard for the CT-API which Carlos Prados has done.
This should probably work with the CT-API for your reader. I need to get
some links on the web site to this. Please send me your links and I'll
put them on the site.
Thanks
Dave
You should contact the support of the company that owns the reader for
wich you are writting the driver. Commonly they use to be very friendly to
give you support, (new platform supported implies more readers/cards
sales for them :-)
You can also take some code from the already written drivers.
Hi, Gergor,
I wan't a copy of your driver when you think it is ready.
Thanks,
Carlos
"Gregor A. Panstruga" wrote:
hi folx,
the response to my announcement about a driver for GCR410 was
overhelming.
the driver will be available after the weekend (i hope).
i send everybody who is
Hi everyone!
On Mon, 22 Feb 1999, Per Undheim wrote:
1)
Excuse me if this has been published before on the mailinglist, but as
I lost some of my archive I didnt find it. Is there any fix for the fact
that /dev/ttyS* is used instead of /dev/cua* in linux 2.2.* ? I
downloaded the latest
Hi,
I have some sugestions about installation procedure of pcsc-0.98:
The following errors are displayed while compiling:
make[2]: Entering directory `/home/cprados/muscle/pcsc-src-0.98/src/iccsp'
cd
slb_crypto4k; make make[3]: Entering directory
Hi,
I have Debian 2.0 also and pcsc compiles fine in my machine. Nevertheless
I think configure.in should include a call to AM_PROG_LIBTOOL since some
of the libraries are compiled with libtool.
I have being trying to reconvert pcsc package to work with
automake, autoconf and libtool, in order
Hello,
Current version only handles one reader at a time.
Next release will support 4 readers simultaneously.
Also a single multithreaded process will be able to
use one reader from diferent threads.
Thanks,
Carlos.
--- Nilesh Correia [EMAIL PROTECTED] wrote:
Hi All,
I ahve got two
Hello all,
I've finished the first pre-release of the new
Towitoko driver. It changes a lot from the previous
versions although it can be yet a bit unstable so it's
number is
2.0.0-pre1.
I'll be uploading it to
http://pcsc.virtualdave.com/~cprados this weekend (I
also want to change the web
Hello,
Almost all the code has changed. There is new
functionality:
- It handles any number of readers concurrently. Also
it is prepared to handle more than one slot / reader.
It's thread safe.
- All CT-BCS commands are fully implemented.
- It handles I2C, 2 wire and 3 wire memory smartcards.
Hello,
The newer release of the Towitoko driver is now
available at http://pcsc.virtualdave.com/~cprados.
Feel free to e-mail me with any question about it.
Carlos.
__
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com
please
send me the output for the same process configuring
the driver with --enable-debug=1 ?
Greetings to the Linux community and
gracias a David Corcoran y Carlos Prados
who are doing a great job for us all.
¡No hay de qué!
Carlos Prados.
__
Do
Hello,
I was wondering about the interpretation of the ATR
parameters "F" and "D".
ISO 7816-3 says
work etu = 1/D * 1/9600 s
does this means that bitrate shold be set to D* 9600
when the parameter "D" is sent in the ATR ? (for
instance in Cyberflex TA1 = 0x94, and this means that
the
Bad news:
It seems that besides doing the PTS protocol with the
card and increasing the speed of the serial port,
Chipdrive controler needs to be informed of the new
serial por speed.
The problem is that the commands for changing the
serial speed are not going to be published by the
With old IFD handler definition the length of the ATR
cannot be returned.
In IFD handler 2.0 IFD_Get_Capabilities has been
replaced with IFDHGetCapabilities, wich return the
value and length of the item requested. Also the
function IFDHPowerICC returns both ATR and ATR Length
when resseting the
Hello,
I recently updated the Towitoko driver. New release is
2.0.0, and is available under:
http://www.geocities.com/cprados
Here is the last ChangeLog for this release. There is
more detailed information about the changes in the
file NEWS within the package.
Best regards,
Carlos Prados
Hello,
Version 2.0.1 of the Towitoko driver is out. Changes in this release are
important if you want to create a multi-threaded application over
CT-API.
There are some corrections in T=1, CT-BCS, and memory cards also.
This is the lastest enty in the ChangeLog:
2000-12-29 Carlos Prados
Yes, the driver must set the "best" communication
settings from the ATR. But sometimes the card can do
more than it specifies on its ATR.
For instance Cryptoflex has D=1, F=372 on its ATR (the
default 9600 bps), but can do more baudrate if the
proper PTS is issued.
The driver can set the
Hello,
This is what I think I'm going to do with the PTS
issue:
* The driver will auto-set "best" comunication
protocol and speed, infered from the ATR, as explained
in previous e-mail.
* The CT-BCS command "Reset CT" will optionaly convey
the PTS request in it's data field. Note that this
Hello,
You can see the sample code in the tester app that
comes with the towitoko driver at
http://www.geocities.com/cprados.
Also some time ago I found two interesanting apps that
uses CT-API to access memory smartcards, that I would
like to introduce in this mailing list:
smartcard:
Hello,
I would put my hand in the fire, and guess that the
following happens with memory cards and protocol RAW:
* The pcsc daemon calls the ifdhandler function
IFDHControl().
* The driver maps the command to a CT command, instead
of a ICC command.
* 6E 00 is returned because this is the CT-BCS
Hello,
--- Andreas Schwier [EMAIL PROTECTED]
escribi: Hi Dave
I never really understood the reason for handling
the transmission
protocols at application level. For the application
it should not matter, if
the card uses T=0, T=1 or a memory card interface,
What happens if card supports
--- Andreas Schwier [EMAIL PROTECTED]
escribi: Hello
On Sam, 20 Jan 2001, you wrote:
I never really understood the reason for
handling
the transmission
protocols at application level. For the
application
it should not matter, if
the card uses T=0, T=1 or a memory card
Hello,
In theory it is possible to use extended commands like
this (case 4 extended):
CLASS INS P0 P1 0x00 LC1 LC2 DATA LE1 LE2
^^^ ^^^
Length of cmd. Length of resp.
That is, you split the length of the command and the
length of
Hello,
So if anyone could give me some
recommendations that would be great.
I'm looking for a good reader/writer that works
under linux and a card
that will run Java.
If you realy want to progarm in Java, the opencard is
your framework (this list is mainly about PC/SC) and
Gemplus
Hello,
i can read onto the memory card, however the file
that i have selected
to read in is the MF.
I would like to create EF with transaparent
structure.
I wonder how to do that ?
You cannot do this with a memory card. The command set
for memory cards allows you to do select file, read
I didn't tested German telephone cards when I wrote
the memory cards functionality. I haven't got one. If
they use either I2C, 2 wire or 3 wire protocol, they
should be supported, but maybe they are not recognized
on initialization. Try setting the smartcard protocol
at compile time and see if
sorry, but I can't give you more
informaton.
Carlos Prados wrote:
I didn't tested German telephone cards when I
wrote
the memory cards functionality. I haven't got one.
If
they use either I2C, 2 wire or 3 wire protocol,
they
should be supported, but maybe they are not
recognized
Hi,
I have already created the Debian Packages. They are
under http://www.geocities.com/cprados/debian
I'm currently in the NM queue and intend to include
pcsc + drivers + ssp's in the next unstable release.
(I have already passed all the checks, and I'm just
waiting for the Debian Account
Hi,
Try to compile the driver as a static library with
"ar" and link your program against this library with
-ldriver.
You can compile the Towitoko driver as static libary
doing:
$ ./configure --enable-static
$ make
--- "Ph. Marek" [EMAIL PROTECTED] escribi: Hi
everyone!
Has anybody tried
Hi,
By now you can:
# apt-get install libtowitoko2 libtowitoko-dev
pcscd, libpcsclite0 and libpcsclite-dev are being
processed.
Regards,
Carlos.
--- Martin Ellis [EMAIL PROTECTED] wrote:
Perhaps my sources.list is wrong, but I didn't find
any packages when I looked
at the weekend.
Hi,
Latests version of this package is ssp-lite-0.1.0 and it compiles against
pcsc-lite 0.4.9. Also I noticed it uses internal functions for dynamic
loading from libpcsclite.so, besides Winscard api.
I think it's interesanting to have a smartcard abstraction layer (I was
thinking on doing
Hi,
it will make the return ATR length zero
This will cause EHSpawnEventHandler: power up fail
The only issue is that the debug message Power Up Fail
is printed. The card should work the same if you send
the appropiate commands.
However I also don't understand why the ATR is parsed
by the
Hi,
On Tue, 17 Apr 2001, David Corcoran wrote:
Hi,
The ATR is parsed because the Resource Manager has to determine which
protocols can be used on the card and is in charge of sending a PTS when
the application has the choice of T=0 or T=1 and chooses the one that is
not default. The
On Tue, 17 Apr 2001, David Corcoran wrote:
Hello,
The error is normal since the card really isn't being powered up. Memory
cards do not all have ATR's and some of them that do don't always follow a
particular pattern.
In this case the debug message could be more descriptive, like:
Hi,
I see the package finally includes autoconf/automake
stuff. I congratulate for it :-)
Just a suggestion: for distributting clean tar.gz
source packages with only system-independent files
(f.i. without generated makefiles, dependencies and
configurations that are created on you machine),
Hi,
I got 67 00 (wrong length) while running `makecard',
when the program tried to do an Update Binary of the
EF 0x (CHV1).
The message returned by the program was error writing
PIN
I edited the file cat/makecard.c, line 250, activated
the line:
check = createFile(0x, 0x0027,
Hi,
I need some advice to interpretate the ISO 7816-3
normative: ISO 7816-3 states that the Work Waiting
Time for T=0 is calculated as follows:
wwt = 960 * D * WI * work etu.
I use this value as timeout for receiving chars from
the card.
I'm not sure how to calculate this value when etu =
Hi,
The package looks fine for me. It fails for me with
Cyberflex, but it's due to the timeout issue I have
asked in the other thread in this mailing list.
Just one question: do you intend to hanlde the case
where the user logs in from a remote computer via,
let's say `telnet` ?
Because
Hi,
I think the PCSC is good enough if it enables access
to the local smartcard to local proceses, and
verifies that the user has UNIX permission to use the
smartcard reader (for instance if /tmp/.pcsctx anc
/tmp/.pcscrx are accessibe to the user).
For remote authentication, a client/server
Hi,
--- David Corcoran [EMAIL PROTECTED] wrote:
Definitely. The interface exported must be a subset
of the
available functionality or else someone could write
a worm which does a
Verify Key function incorrectly and blocks cards
where services are
available.
Even worst. If you leave
Hi,
Thanks Peter for your great explanation.
7816-3:1997 section 8.2 on work waiting time:
wwt = 960 * WI * (Fi / f)
This is exactly what I get doning variable
substitution and symplification in the formula that
comes in ISO 7816-3: 1992.
[snip]
It seems, therefore, that changing the
Hi,
which includes 2 memory cards. Those two cards seems
to be of a different type:
- 2Kbit I2C EEPROM Card (256 Byte, R/W)
seems to be a 2-wire card
(icc-type = 2)
If it's I2C, then it isn't 2-wire. If the Towitoko
driver assigns '2' to the ICC type then it migth be an
2-wire card.
Hi,
I completly agree with Andreas. Get Response is
dependant on T=0 transport protocol and must not be
handled at application level. This is at least what
ISO 7816 says.
Towitoko driver 2.0.X handles authomatically the Get
Response when the command is Case 3 or Case 4. Also
the issues
Hi,
--- Axel Heider [EMAIL PROTECTED] wrote:
Hi,
some time ago I got this response from Eric Perlin
from
Microsoft about their PC/SC implementation:
This is no work for the driver. This needs to be
handled
by the app. I recommend a little layer on top of
SCardTransmit to hide
Hi,
I recently became Debian developer with the intention of packaging the
MUSCLE environment (Drivers/PCSC lite/Applications).
Towitoko driver (written by myself) and PCSC daemon/lib/devel (by David)
are already packaged and uploaded to debian unstable branch (sid).
If some developer wants
52 matches
Mail list logo
