On 02/06/2009 01:27 AM, Alon Bar-Lev:
On Friday 06 February 2009 01:08:29 Eddy Nigg (StartCom Ltd.) wrote:
A clear voice of reason. If we can get a unified project out of this it
would be terrific. I'll look into how we can support such a project, if
and when I can see the attempts to align
On Friday 06 February 2009 01:08:29 Eddy Nigg (StartCom Ltd.) wrote:
> A clear voice of reason. If we can get a unified project out of this it
> would be terrific. I'll look into how we can support such a project, if
> and when I can see the attempts to align toward one well supported
> project.
On Friday 06 February 2009 00:57:18 Peter Stuge wrote:
> > The problem is that I do not have an unlimited amount of time. I
> > prefer to slowly improve pcsc-lite step-by-step rather than start a
> > new project from scratch.
>
> Please clarify this. I don't think you are saying that you will
> ne
On 02/06/2009 12:57 AM, Peter Stuge:
Ludovic, I completely understand that you feel unable to contribute
much to a new project while still maintaining pcsc-lite as you do
now. But would you refuse to cooperate with the project (share
knowledge and code) if it was there, and do you refuse to find
On Friday 06 February 2009 00:00:21 Ludovic Rousseau wrote:
> > pcsc-lite has some infrastructural limitations, that cannot be
> > easily fixed. it has no driver support environment, so
> > writing new drivers is difficult.
>
> Do you need a new driver for pcsc-lite? For which reader?
> Do you kno
Ludovic Rousseau wrote:
> > Ludovic made it clear that he does not want to cooperate. So I
> > guess the initiative is rejected and dropped.
Hold on a moment.
> The problem is that I do not have an unlimited amount of time. I
> prefer to slowly improve pcsc-lite step-by-step rather than start a
Hi!
The german eGK specification does NOT specify a complete
card operating system but only a few commands. Every
card operating system that implements those commands
(among others) is eGK-compliant.
In order to support a card OpenSC must implement a
couple of basic commands and only some of them
2009/2/5 Alon Bar-Lev :
> Hello all,
Hello Alon,
> pcsc-lite has some infrastructural limitations, that cannot be
> easily fixed. it has no driver support environment, so
> writing new drivers is difficult.
Do you need a new driver for pcsc-lite? For which reader?
Do you know a smart card reader
Hello all,
About every two years the same subject pops-up.
pcsc-lite has some infrastructural limitations, that cannot be
easily fixed. it has no driver support environment, so
writing new drivers is difficult.
One round ended up with the development of competing
project: OpenCT.
I believe Ope
On Thursday 05 February 2009 14:15:33 Andreas Jellinghaus wrote:
> Am Mittwoch 04 Februar 2009 19:55:33 schrieb Alon Bar-Lev:
> > I hope so... The dependency of libusb forces you to compromise. See how
> > clean the implementation of OpenCT is.
>
> take a look at the way usb is accessed on mac os
Am Mittwoch 04 Februar 2009 19:55:33 schrieb Alon Bar-Lev:
> We discussed this too many times, Andreas also discussed this with you.
> OpenCT provide supportive environment for drivers, common code for logging,
> common code for protocols, common code for device access etc...
> If you write a drive
Am Mittwoch 04 Februar 2009 19:55:33 schrieb Alon Bar-Lev:
> I hope so... The dependency of libusb forces you to compromise. See how
> clean the implementation of OpenCT is.
take a look at the way usb is accessed on mac os X.
that is very hard to do without libusb.
with openct we never got any ma
2009/2/5 Peter Stuge :
> Alon Bar-Lev wrote:
>> > Because of problems with libusb I have to timeout every 2 seconds
>> > so a PC_to_RDR_GetSlotStatus command is sent to the reader every
>> > 2 seconds.
>> > This short timeout should be removed in a later version of the
>> > CCID driver.
>>
>> I hop
13 matches
Mail list logo
