Am Freitag 21 Oktober 2011, 17:47:32 schrieb Ludovic Rousseau:
2011/10/21 Andreas Jellinghaus a...@dungeon.inka.de:
Am Freitag 21 Oktober 2011, 13:50:54 schrieb Ludovic Rousseau:
The specifications are MS WORD documents. We are in a corporate world
here. The documents have a Revision
Am Freitag 21 Oktober 2011, 13:50:54 schrieb Ludovic Rousseau:
The specifications are MS WORD documents. We are in a corporate world
here. The documents have a Revision History section at the beginning
listing the major changes.
I agree, a diff-able format would be cool. But I do not expect
Am Freitag 25 März 2011, um 03:40:21 schrieb Karsten Ohme:
Hi,
I have created a Wiki for the GlobalPlatform Library and GPShell. Also a
nice intro to the GlobalPlatform card specification is given:
http://globalplatform.sourceforge.net/
nice, thanks!
There are two issues that I find
Am Freitag 25 März 2011, um 11:00:01 schrieb Sébastien Lorquet:
You're talking about not initialized cards. First, it's near impossible to
find cards in this state, so the doc would be useless, and second, the
commands available in these modes are generally secret and not even
available with
I'd be very interested in feedback on using contactless cards
on android too!
So far I saw some documents or blog postings etc. telling me:
* google has only published an API for accessing nfc tags :(
* the nfc capable phones are supposed to be used with special
usim cards.
but I haven't found
Am Donnerstag 23 Dezember 2010, um 12:57:10 schrieb Adrian Mustelier:
Hi:
Can I read a synchronous card like (SLE5544) with a CCID Smart Card Reader
like (GemPC USB-SL) and the PCSC API?.
No. On windows every vendor ships their own library for using memory cards,
and you need to use that
Google for a PCSC tutorial, I think it will be easy to
find some exaple code. And it will show you the real
question: it is not hard to connect to a reader and
send a command to the card - but what is the right command?
In theory there is ISO 7816-4 ... -15 standards, but in
practice every card
Am Mittwoch 28 Juli 2010, um 08:22:24 schrieb Ludovic Rousseau:
Mac OS X uses uint32_t and normal C types like in:
PCSC_API int32_t SCardConnect(SCARDCONTEXT hContext,
const char *szReader,
uint32_t dwShareMode,
uint32_t dwPreferredProtocols,
Am Samstag 29 Mai 2010, um 15:13:12 schrieb Ludovic Rousseau:
The reader can't powering up the card.
The Windows driver may do something special to use this card.
Can you try this card with a reader from another manufacturer?
old german KVK are memory cards. not sure if/how pcsc-lite and
Am Sonntag 30 Mai 2010, um 13:13:35 schrieb Claudia Neumann:
I have implemented a lib for card readers that I can directly access
through a device. Don't understand yet how I could do something like that
with pcsc-lite. Is there a profund documentation? Or could I use the
Windows header files
Hi,
if I have a memory card with i2c interface, and pcsc-lite:
can I somehow write too it?
maybe there is some reader that supports i2c cards, with
a driver that does (or at least documentation enough to
implement such a driver)?
sure, ccid would be prefered, but I guess the ccid standard
Hi,
can you give me some advice:
which card readers for pcsc-lite have serial numbers?
with lsusb -v I find this:
Bus 004 Device 012: ID 04e6:5115 SCM Microsystems, Inc. SCR335 SmartCard
Reader
...
idVendor 0x04e6 SCM Microsystems, Inc.
idProduct 0x5115 SCR335 SmartCard
simply uninstall openct. only experts can use both at
the same time. normal users are best of using either
pcsc-lite with libccid reader, or openct (if there is no
pcsc driver for your reader), but not both.
so uninstall openct and the openct-ifd driver for pcsc-lite
(which is pretty much
Ludovic,
is there a current template for writing a driver
for an usb based device?
it would be nice to have all the normal goodies
(coldplug and hotplug detection for usb devices,
interface with pcscd, T=1 protocol engine), so
you only need to fill in the proprietory bits
between USB layer and
Am Montag 23 November 2009 14:21:20 schrieb Ludovic Rousseau:
libusb-1.1 will [1] support hotplug through libudev. So pcscd should
just use libusb 1.1 instead of 0.1 and have hotplug for free.
libusb-1.1 should be available before the end of 2009. So I think I
will skip the DeviceKit/udev
hmm. does anyone know details about ubuntus move away from hal?
on my (updated) 9.10 laptop hal is still installed, but no idea
if that is the case for new installations too.
also what is the replacement for hal? somewhere I read udev,
which would be strange, as the udev developers suggested I
Am Sonntag 25 Oktober 2009 21:05:05 schrieb Alex:
Your serial reader is most probably NOT a CCID compatible
device, so
no point in installing it. CCID is a USB standard.
Ok, thanks for explanation. Now I know what is CCID standard :-)
BTW, I understand correctly ?
There is no way to use
Am Samstag 17 Oktober 2009 13:14:30 schrieb Johannes Kapune:
Hello,
maybe I make something wrong, but I can't get my CardReader working.
If You miss some more informations please tell me.
try uninstalling openct or remove the openct.bundle file.
both ccid and openct contain ccid drivers, but
Am Mittwoch 23 September 2009 10:52:52 schrieb Linux User:
When a contactless smart card transmits data stored on a smart card to a
contactless smart card reader, is the wireless communication between the
card and the reader encrypted?
yes and no - if you setup encryption first and send
Am Mittwoch 23 September 2009 11:19:26 schrieb Linux User:
Thank you for that reply.
As an end user and not a developer, how can I determine if the wireless
communication between the card and reader are encrypted?
enable debugging, so you see each packet going forth and back,and sit down
with
Am Mittwoch 23 September 2009 12:09:49 schrieb Linux User:
I should have mentioned that my question was from the perspective of an end
user, not a developer. I'm sorry for that omission; I did not realize this
list was so developer-centric.
thats perfectly fine, user questions are very
Am Montag 21 September 2009 01:26:10 schrieb Linux User:
Hello,
Does the SCM Microsystems SCL3711 contactless smart card reader work
correctly on Linux (i586 and X86_64)?
it's not a CCID device (ccid not mentioned in the data sheet),
so it won't work with the generic ccid driver. I don't
Am Mittwoch 26 August 2009 23:03:13 schrieb Ludovic Rousseau:
My question is: what mechanism to use to convey the information?
I was thinking of using D-Bus and also provide other information like
reader insertion/removal, card insertion/removal. And then card
communication status.
Is D-Bus
Am Freitag 17 Juli 2009 13:57:18 schrieb Joao Pedro:
The idea is the following:
If a user wishes to verify its PIN, instead of just using sending a
INS_VERIFY_PIN APDU with the PIN clear text, the following would happen:
Pre-condition: The card has the PIN stored in clear text.
1.
if you want web connections authenticated with a smart card,
the best way is usualy
1.) use an ssl server
2.) use the option to authenticate to that ssl server using a
client certificate (with the private key)
3.) find a way so that the private key is stored on a smart
card and is not read
Hi Tim,
you can either use pcsc-lite + driver or openct,
opensc supports both middlewares.
openct can be a driver for pcsc-lite, but that is not recommended
and maybe not working well.
contactless card readers are either
a) supported by librfid + openct. have a look at the librfid project.
b)
you need for types of software:
* your application
* a plugin for your smart card
* a middleware
* a driver for your smart card reader
typical choices are:
* firefox
* a pkcs11 library such as opensc (does support some cards but not all)
* pcsc-lite as middleware
* some driver for the
creating a smart card reader as PCI device is total overkill :)
today there are some laptops with build in smart card readers
that are connected via usb. those should work.
also at least omnikey cardman 4040 should work - pcmcia smart
card reader. also cardman 4000 should work. but beware: I
gemsafe is proprietory stuff, as far as I know it can only be used with the
gemplus software.
I believe it also
has a GemSafe applet pre-installed.
I think so too, and I guess you can't remove it. but I'm no expert on this.
maybe ask on the global plattform shell ml?
Regards, Andreas
On Wednesday 02 May 2007 00:27:42 Michael Bender wrote:
How does this access control mechanism work?
openct uses a status file and sockets, both placed in /var/run/openct/
only those with 0700 - only root can access it. 0750 - those in the
group can use openct too, 0755 - everyone can use it.
On Wednesday 02 May 2007 06:17:29 Martin Preuss wrote:
On Wednesday 02 May 2007 00:27, Michael Bender wrote:
Andreas Jellinghaus wrote:
On Tuesday 01 May 2007 21:14:26 Martin Preuss wrote:
For CTAPI drivers there is also another problem that should be
addressed in the next step: I
On Tuesday 01 May 2007 23:24:00 Ville Skyttä wrote:
Fedora uses /usr/lib(64)/pcsc/drivers and /usr/lib(64)/ctapi. FWIW,
readers smells to me like a tad too generic name to use directly below
/usr/lib(64).
looks good to me, I think the reader term is too generic. even card reader
is used by
On Tuesday 01 May 2007 21:14:26 Martin Preuss wrote:
For CTAPI drivers there is also another problem that should be addressed in
the next step: I think it would be best to have a system
group/user chipcard (or whatever name is feasible) analogous to the
groups disk, audio etc.
FYI: debian and
I found the programming manual online:
http://www.chipcatalog.com/Doc/6834A5F027FFA5FAF9D73BB6A1D84348.pdf
http://www.chipcatalog.com/TI/PCI6515.htm
not sure if this is enough info to create a driver.
(never wrote a pci driver...)
Andreas
___
Muscle
Are you sure it is a PCI device? maybe it is a PCI/USB bridge with a usb
smart card reader attached?
in that case run lsusb. If you can see it, try the ccid driver
(either libccid with pcsc-lite or openct ccid driver).
Good luck!
Andreas
___
Muscle
I'm interested in creating a custom (k)ubuntu install cd/dvd
that can setup encrypted root and swap partition, comes with
all smart card software (including openssh with smart card
support) and can maybe even protect the encrypted root and swap
with smart cards.
but I also guess - as usual - I
with openct I'm using udev to detect new devices.
works fine so far. but the scripts in openct get
called twice, for /dev/bus/usb and /proc/bus/usb
so two ifdhandler processes are started. but that
is ok, only on of them can claim the interface to
the smart card reader, and the other one fails.
Hi Thomas,
thanks a lot, commited.
will try to run the full regression test suite, with your extensive
testing we should get a pass now.
once question: we still have that unidentified pin #1? (which
we set to and enter that when asked.)
what are the settings for this pin, will the
Thomas Harning Jr. wrote:
The unidentified pin is the user pin initialized when you initialize the
card. The card can lock up if it's entered wrong a few times, but since
its a normal user PIN, you could reset the card or use unblock and it'd
be ok.
ok, in any case we need to document how
Hi Iain,
Except that there is also an admin PIN for the MCardApplet, and that's
actually sometimes referred to as a transport key. The default value for
that is 0x4D7573636C653030, but it gets changed when the applet is
personalised. Both PINs also get assigned numbers of attempts before
they
Karsten Ohme wrote:
You can always delete and install applets on a GlobalPlatform card, if
you have the GlobalPlatform keys, this has nothing to do with the
MuscleCard applet.
what are these globalplatform keys? where do I use them, how
do I change them and all that?
or is that the one
Is there a tool to debug cards?
The code in opensc seems to have a bug:
first a file is created ok, then it is selected,
and that returns with an error / file does not exist.
So any tool that can list the files that do exist would
be a big help.
1.1.6: 25 November 2006, Ludovic Rousseau
-
Iain MacDonnell wrote:
The muscletest tool that is built with libmusclecard (but not
installed anywhere by default - find it in src/.libs) will
list objects,
thanks, will have a look.
but I'm not sure how the PKCS#15 files for OpenSC
get implemented as MuscleCard objects... is there a 1:1
Ludovic Rousseau wrote:
I also proposed to change the permissions on the /var/run/pcscd.*
files. Your idea of dynamically add a user in a particular group is
very good. I would prefer smartcard as the group name to be more
explicit.
debian, ubuntu and gentoo use scard already, so guess it will
Andy Kirby wrote:
Details a method for using the kernel 26 cm4040_cs driver and card for
reading smart cards.
works fine over here with openct 0.6.9 and opensc 0.11.1 (but opensc
version shouldn't matter), and kernel 2.6.18.
The card appears in /sys/bus/pcmcia but no device appears in /dev
John H. wrote:
I have activcard usb v2.0 but I understand it has problems with ccid.
as you can see on
http://pcsclite.alioth.debian.org/ccid.html
only active card reader v3.0 is supported by the CCID driver.
version 3.0 readers work exactly like scr3xx readers or any
other ccid reader
I looked at the code, and I am very confused. can you help me?
1.) why four bytes? all msc_* funcions only use the first two bytes
anyway, so passing more looks wrong to me. also I'm not sure which
if any functions in card-muscle or the muscle filesystem use more
than this. so why
Andreas Jellinghaus wrote:
I looked at the code, and I am very confused. can you help me?
1.) why four bytes? all msc_* funcions only use the first two bytes
no, misread the code. but still confused...
Andreas
___
Muscle mailing list
Muscle
I'm not sure if I have the same problem Dejan ran into, but
pkcs15-init is still failing for me. Now the problem is
...
card.c:531:sc_select_file: called; type=2, path=3f0050154946
apdu.c:504:sc_transmit_apdu: called
card.c:311:sc_unlock: called
apdu.c:504:sc_transmit_apdu: called
Thanks Karsten, got it to work.
The Applet is now (or should be) on my token, next I need to investigate
how to use the opensc support.
Regards, Andreas
___
Muscle mailing list
Muscle@lists.musclecard.com
the egate driver in openct is working fine for me,
at least with opensc. both are available from
www.opensc.org/files/snapshots
openct needs CONFIG_HOTPLUG, usb support and the
usb device filesystem (compiled in and mounted
to /proc/bus/usb).
Andreas
Hi,
David Mattes wrote:
This is a request for information. Does anyone have any experience
using OpenSSL with smartcards in Linux? Are you using the Trustway
PKCS11 OpenSSL patch? I'm investigating the use of a smartcard to
negotiate an stunnel. Stunnel uses the OpenSSL libraries, and
On Wed, 2003-04-02 at 02:48, MRovari - TecHelp wrote:
Hi
Did you say that with the solution a and b I would need formatar the eToken
under linux, correct?
Like me format the eToken under linux, that command I use?
From the README (I had it attached to the last message):
4.) initialize the
On Wed, 2003-04-02 at 12:27, MRovari - TecHelp AT wrote:
Hi
I am using Mozilla version 1.0.1-26
The opensc is truly the 0.7.0.
update to the latest cvs version
(or download a snapshot - see
http://etoken.sf.net).
You also might want to try the usbtoken driver instead
of the etoken driver
Have just installed RedHat8.0 Full, what I need to install so that my
Browser Mozilla or Netscape recognize my eToken Alladin?
see the certificates you have installed on it using windows: never.
At least not with open source software. Ask Aladdin for drivers,
maybe they have finished their
Hi.
To use an Aladdin eToken with Mozilla you need:
a) Mozilla + OpenSC + PC/SC-Lite + Etoken
b) Mozilla + OpenSC + USB Token
c) Mozilla + Aladdins PKCS#11 + PC/SC-Lite + Aladdins Ifdhandler
With solution a) and b) you need to format the key under linux
and put stuff on it.
On Wed, 2003-03-26 at 18:08, David Mattes wrote:
This is a request for information. Does anyone have any experience
using OpenSSL with smartcards in Linux?
My experience is build on the mix of openssl, openssh and opensc.
This works fine, but it is old code of the
Hi,
I bought an iKey 2032. Anyone interested in a driver?
I don't have an APDU documentation so far, but looking
at the usb layer, it should be easy to support the iKey.
(mostly T=1 with some crude hacks / i understand about 850
of 868 usb transactions i sniffed).
If you know the iKey in detail
i wonder why pcscd doesn't use /var/run/pcsc ?
many other daemons have their own /var/run directories
for similiar purposes, and that works fine.
Andreas
___
Muscle mailing list
[EMAIL PROTECTED]
http://lists.musclecard.com/mailman/listinfo/muscle
59 matches
Mail list logo
