Pauley, John wrote:
All,
First, sorry for the long post.
My problem is that I have to authenticate the terminal with a GemPlus
MPCOS-EMV smart card using the following algorithm (this is in the G+
MPCOS-EMV manual):
[description deleted]
I'm not sure what your problem is but I have
Patrick Valsecchi wrote:
I don't have to store each signature of each bin into the smartcard. I won't
have enough RAM for that! I'll store inside each executable and library the
signed crypto hash. The kernel will check if the crypto hash is still the same
and the smartcard will just
Carlos Prados wrote:
Again, I would pay more athention to local security.
Why is the file /tmp/.pcscrx world writtable? isn't
this a security hole?
On the subject of security...
As may be apparent I've only just got my setup working and I've not
examined things in any detail. I did
Jean-Luc GIRAUD wrote:
Dr S N Henson wrote:
I suspect the answer is 'none of the above' :-)
Yes and no :-) (see below).
I'm compiling MUSCLE 0.9.1 and the GemPC430 driver from source. There
are a few problems with 'make install' in MUSCLE, at least on my setup:
for example
David Corcoran wrote:
Hi,
Try removing bundleparser.c and doing the ./configure --enable-usb
and everything over again.
That did the trick. I still get a few kernel warning messages when I
plug the device in but I can now access the reader, thanks.
Steve.
--
Dr Stephen N. Henson.
I've been testing out MUSCLE and some related software with some gemplus
readers, all with RHL 6.1 2.2.12 kernel and RHL7.0 2.2.16 with
backported USB and 2.4.5.
The serial reader (GemPC 410) seems to work fine.
I haven't got the USB reader GemPC430 to work though. All I get when I
plug the
