2009/2/6 Alon Bar-Lev :
> On Friday 06 February 2009 15:06:25 Andreas Jellinghaus wrote:
>> Am Freitag 06 Februar 2009 13:36:58 schrieb Ludovic Rousseau:
>> > > also 3 seconds seems quite long to me.
>> >
>> > Only if you also have pcscd running.
>> >
>> > The patch will impact only people with the
On Friday 06 February 2009 15:06:25 Andreas Jellinghaus wrote:
> Am Freitag 06 Februar 2009 13:36:58 schrieb Ludovic Rousseau:
> > > also 3 seconds seems quite long to me.
> >
> > Only if you also have pcscd running.
> >
> > The patch will impact only people with the following configuration:
> > -
2009/2/6 Andreas Jellinghaus :
> Am Freitag 06 Februar 2009 13:36:58 schrieb Ludovic Rousseau:
>> > also 3 seconds seems quite long to me.
>>
>> Only if you also have pcscd running.
>>
>> The patch will impact only people with the following configuration:
>> - use OpenCT
>> - use pcsc-lite (file "/
Am Freitag 06 Februar 2009 13:36:58 schrieb Ludovic Rousseau:
> > also 3 seconds seems quite long to me.
>
> Only if you also have pcscd running.
>
> The patch will impact only people with the following configuration:
> - use OpenCT
> - use pcsc-lite (file "/var/run/pcscd/pcscd.comm" is present)
>
2009/2/6 Andreas Jellinghaus :
> Am Freitag 06 Februar 2009 09:27:11 schrieb Ludovic Rousseau:
>> I propose the attached patch. The idea is to sleep for 3 seconds if a
>> CCID device is detected and pcsc-lite is also running.
>> If the device is not claimed by a pcsc-lite driver then openct will
>>
Am Freitag 06 Februar 2009 09:27:11 schrieb Ludovic Rousseau:
> I propose the attached patch. The idea is to sleep for 3 seconds if a
> CCID device is detected and pcsc-lite is also running.
> If the device is not claimed by a pcsc-lite driver then openct will
> use it as before.
please resend, th
On 2/6/09, Ludovic Rousseau wrote:
> I propose the attached patch. The idea is to sleep for 3 seconds if a
> CCID device is detected and pcsc-lite is also running.
> If the device is not claimed by a pcsc-lite driver then openct will
> use it as before.
>
> I could not test the patch. I can't
2009/2/2 Ludovic Rousseau :
> Maybe we could also define a priority rule : if both openct and
> pcsc-lite are installed then pcsc-lite has priority, or something like
> that.
> It can be easy to implement: in the ccid driver just wait for 1 or 2
> seconds before claiming the device. pcsc-lite will
--On Monday, February 02, 2009 07:38:23 PM +0100 Andreas Jellinghaus
wrote:
> but keeping openct around with or without ccid
> driver, or having some other drivers around
> to implement non-ccid drivers all ends up with
> the same result: lots of common functionality in
> several places.
The so
On Monday 02 February 2009 21:58:17 Andreas Jellinghaus wrote:
> of limitations. also openct has a lot less to offer than pcsc-lite plus ccid,
> for example no working pinpad support.
This is driver issue not framework issue.
> I believe if all things pcsc-lite plus ccid can do would be added to
Am Montag 02 Februar 2009 19:27:42 schrieb Douglas E. Engert:
> > The way to do this is to have a single service which provides a
> > rendesvous point for clients and readers, keeps track of what readers
> > exist and of their state, informs clients of changes they are interested
> > in, and mediat
Jeffrey Hutzelman wrote:
> --On Monday, February 02, 2009 07:52:30 PM +0200 Alon Bar-Lev
> wrote:
>
>> On Mon, Feb 2, 2009 at 7:41 PM, Jeffrey Hutzelman wrote:
>>> --On Monday, February 02, 2009 04:28:22 PM +0200 Alon Bar-Lev
>>> wrote:
>>>
The client library monitors /var/run/libscread
Hi Ludovic,
how tied is the ccid reader to supporting ccid only?
or could you implement other protocols in it as well?
in theory I'm all for using the best software available,
and at least once pinpad support is required that is
pcscd with your ccid driver and not openct.
but keeping openct arou
On Mon, Feb 2, 2009 at 8:02 PM, Jeffrey Hutzelman wrote:
> The way to do this is to have a single service which provides a rendesvous
> point for clients and readers, keeps track of what readers exist and of
> their state, informs clients of changes they are interested in, and mediates
> when more
--On Monday, February 02, 2009 07:52:30 PM +0200 Alon Bar-Lev
wrote:
> On Mon, Feb 2, 2009 at 7:41 PM, Jeffrey Hutzelman wrote:
>> --On Monday, February 02, 2009 04:28:22 PM +0200 Alon Bar-Lev
>> wrote:
>>
>>> The client library monitors /var/run/libscreader for changes
>>
>> That sounds reall
On Mon, Feb 2, 2009 at 7:41 PM, Jeffrey Hutzelman wrote:
> --On Monday, February 02, 2009 04:28:22 PM +0200 Alon Bar-Lev
> wrote:
>
>> The client library monitors /var/run/libscreader for changes
>
> That sounds really nonportable.
>
I have it working for Linux (inotify) and BSD (kevent).
Solari
--On Monday, February 02, 2009 04:28:22 PM +0200 Alon Bar-Lev
wrote:
> The client library monitors /var/run/libscreader for changes
That sounds really nonportable.
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-p
On 02/02/2009 04:28 PM, Alon Bar-Lev:
On Monday 02 February 2009 16:17:12 Peter Stuge wrote:
Alon Bar-Lev wrote:
work together to achieve single common framework
I really liked that proposal. Sorry I didn't say so sooner.
This is my proposal, I will be happy to get s
Alon Bar-Lev wrote:
> work together to achieve single common framework
I really liked that proposal. Sorry I didn't say so sooner.
//Peter
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinf
On Monday 02 February 2009 14:09:12 Ludovic Rousseau wrote:
> Maybe it is time to let OpenCT die and use pcsc-lite only?
Ludovic, we discussed this off-list.
pcsc-lite has many disadvantages, I offered you my help and time in order to
work together to achieve single common framework for smartcar
Dear OpenCT developpers and users,
The problem reported by Johannes was a resource conflict between
OpenCT and pcsc-lite.
Maybe it is time to let OpenCT die and use pcsc-lite only? Another
option is to remove the support of CCID readers from OpenCT and
activate it _only_ after the user changed a
2009/1/30 Johannes Becker :
> Hello,
Hello,
> using Debian lenny at the moment the card reader has to be
> plugged in to the USB port while the PC boots.
> If you plug it in later or if you unplug and plug again, the reader doesn't
> work. I noticed this only recently. It was ok before.
>
> # un
Hello,
using Debian lenny at the moment the card reader has to be
plugged in to the USB port while the PC boots.
If you plug it in later or if you unplug and plug again, the reader doesn't
work. I noticed this only recently. It was ok before.
# uname -a
Linux be 2.6.26-1-686 #1 SMP Sat Jan 10 1
23 matches
Mail list logo
