So I have one of these smart cards and started just fooling around with
it.
It looks to be a Oberthur CS PIV End Point v1.08 FIPS201 Certified
smartcard. Looking at their webpage they do indeed make the registered
traveler card.
Fly Clear card: ATR: 3b db 96 00 81 b1 fe 45 1f 03 80 f9 a0 00 00 03
On 1/29/09, Andrey Jivsov wrote:
> I am attaching the tested patch to the file ifd-ccid.c to add support for
> the reader. The reader's USB IDs that I tested with are 0b97:7762 and
> 0b97:7772. Without this patch the ifd-ccid.c code will not work with these
> readers.
>
> The patch is based on th
I am attaching the tested patch to the file ifd-ccid.c to add support
for the reader. The reader's USB IDs that I tested with are 0b97:7762
and 0b97:7772. Without this patch the ifd-ccid.c code will not work with
these readers.
The patch is based on the work done in the pcsc-lite project. The
Should be.
The autoconf substitute this in the Makefile, and the sysconfdir is
resolved by make.
When you run make, do you see invalid value for CPPFLAGS_OPENCT_CONF_PATH?
Alon.
On 1/29/09, Aktiv Co. Aleksey Samsonov wrote:
> Hello.
> The openct trunk revision 1127: configure.ac: Line 400:
> C
On 1/29/09, Aktiv Co. Aleksey Samsonov wrote:
> Alon Bar-Lev:
>
> > Can you please update the openct trunk so that Rutoken use the new
> > event interface?
> >
>
> OK, the updated patch is attached.
Thanks!
Alon.
___
opensc-devel mailing list
opensc-d
Hello.
The openct trunk revision 1127: configure.ac: Line 400:
CPPFLAGS_OPENCT_CONF_PATH='-DOPENCT_CONF_PATH="\"$(sysconfdir)/ifdhandler\""'
- is it correct?
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.o
Alon Bar-Lev:
Can you please update the openct trunk so that Rutoken use the new
event interface?
OK, the updated patch is attached.
On 1/28/09, Alon Bar-Lev wrote:
Thanks.
Applied.
Thanks!
diff -u -r openct-0.6.15.trunk-r1127/src/ifd/ifd-rutoken.c
openct-0.6.15.trunk-r1127_new/src/ifd
On 1/29/09, Andreas Jellinghaus wrote:
> Am Mittwoch 28 Januar 2009 19:02:39 schrieb Stanislav Brabec:
>
> > In case of Smart Cards, it might be GID writability for "scard" group,
> > allowing to run smart card daemon without root privileges.
>
>
> if pcscd or openct should run as non-root, then
Am Mittwoch 28 Januar 2009 19:05:08 schrieb Alon Bar-Lev:
> Running software as root is the worst solution. Especially security
> centric software.
not a good solution, but not the worst. remember old linux/unix systems
with a bin user and group, and all binaries owned by them? that was
worse. cre
Am Mittwoch 28 Januar 2009 19:02:39 schrieb Stanislav Brabec:
> In case of Smart Cards, it might be GID writability for "scard" group,
> allowing to run smart card daemon without root privileges.
if pcscd or openct should run as non-root, then there should be:
* one way how openct/pcscd can access
Am Mittwoch 28 Januar 2009 19:30:52 schrieb Stanislav Brabec:
> How to name the main category "smart_card_reader or crypto_token"?
I think it is easer to explain, that a usb crypto token is a device consisting
of a reduced smart card reader and a fixed build in smart card. I guess
this is quite cl
11 matches
Mail list logo
