On Saturday 15 April 2006 11:34, Chaskiel M Grundman wrote:
> ITSEC-P and FIPS use the same card operating system (STARCOS). They're not
> identical though. The ITSEC-P is STARCOS SPK 2.3, and FIPS is 2.4. The
> other models do not use STARCOS (ITSEC-I is cardOS and 5 & 2048 are based
> on ARX Priv
On Sun, 16 Apr 2006, Justin Karneges wrote:
But what about drivers? Does the same SafeSign driver installation work for
all 5 devices? This might mean that even though there are varying firmwares,
they probably operate very similarly if one driver can manage all of them.
There are 2 "driver" c
On Sunday 16 April 2006 10:15, Chaskiel Grundman wrote:
> On Sun, 16 Apr 2006, Justin Karneges wrote:
> > Well, this is silly and stupid, yet unsurprising. I guess what we really
> > want is OpenSC support for the devices and then we can wipe our cards and
> > throw SafeSign out the window.
>
> ex
I am unfortunately encountering frequent usb errors with the itsec-p and
5/2048. ifd_usb_control is failing with EOVERFLOW, which apparently
means that a usb condition known as 'babble' has been detected. I don't
really know what this means or if it's the fault of openct, linux, or
the hardware
The attached patch implements the eutron changes from my last message,
including the T=1 fix. It also adds an ifsd negotiation function to
proto-t1.c (taken from the copy of proto-t1.c in the pcsc-lite ccid
driver), and makes use of it in the eutron driver.
The patch also attempts to flush the
