On Tuesday 10 February 2009 20:38:30 Douglas E. Engert wrote:
> I have some more basic questions of the people in this discussion.
>
> Have any of you met face to face?
Did not met anyone.
>
> What are your motives in getting involved in OpenSC?
>
I began with this mission:
>From my public p
Thanks Douglas for helping us in this discussion.
Am Dienstag 10 Februar 2009 19:38:30 schrieb Douglas E. Engert:
> Have any of you met face to face?
nope. I know Peter Koch and Peter Stuge (well, met him once many
years ago), and once or twice phones Nils, but don't know anyone else.
> What are
Andreas Jellinghaus wrote:
> For the record, I completely agree with ludovics posting.
I also agree.
I have some more basic questions of the people in this discussion.
Have any of you met face to face?
What are your motives in getting involved in OpenSC?
Are you working for companies that n
On 02/06/2009 11:26 AM, Andreas Jellinghaus:
questions for me after hours of exchanging emails with him, and
all that without writing code first.
For me open source doesn't work that way.
Oh yeah, I almost forgot, this is OSS ...open source projects first
write some code, then figure out
On 2/6/09, Andreas Jellinghaus wrote:
> For the record, I completely agree with ludovics posting.
>
> Alon wants other people to fix the problem he found, but not
> even help in reproducing or debugging it. Alon wants to commitment
> to a new design he came up with, one that leaves many, many o
For the record, I completely agree with ludovics posting.
Alon wants other people to fix the problem he found, but not
even help in reproducing or debugging it. Alon wants to commitment
to a new design he came up with, one that leaves many, many open
questions for me after hours of exchanging emai
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
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
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 hope so... The dependency of libus
On 04.02.2009, at 20:36, Alon Bar-Lev wrote:
> On Wednesday 04 February 2009 12:29:01 Martin Preuss wrote:
>> Hi,
>>
>> On Dienstag, 3. Februar 2009, Alon Bar-Lev wrote:
>>> On Wednesday 04 February 2009 00:00:44 Martin Preuss wrote:
>> [...]
>>> True. This is why I suggest separating the reader
On Wednesday 04 February 2009 11:11:26 Ludovic Rousseau wrote:
> 2009/2/3 Alon Bar-Lev :
> > In time I believe commonly used drivers may be migrated into new framework,
> > to be more efficient, maintainable and share the common code base available
> > in the reader library. Example: Logging, Proto
On Wednesday 04 February 2009 12:29:01 Martin Preuss wrote:
> Hi,
>
> On Dienstag, 3. Februar 2009, Alon Bar-Lev wrote:
> > On Wednesday 04 February 2009 00:00:44 Martin Preuss wrote:
> [...]
> > True. This is why I suggest separating the reader framework from the
> > application API.
> [...]
>
>
2009/2/4 Martin Preuss :
> Hi,
>
> On Mittwoch, 4. Februar 2009, Ludovic Rousseau wrote:
>> 2009/2/3 Martin Preuss :
>> > 1) with pcscd all readers are always *on*. As soon as a reader is
>> > connected it is started and polled for card insertion and removal even
>> > when there is no client. I wou
Hi,
On Dienstag, 3. Februar 2009, Alon Bar-Lev wrote:
> On Wednesday 04 February 2009 00:00:44 Martin Preuss wrote:
[...]
> True. This is why I suggest separating the reader framework from the
> application API.
[...]
Ah, now I understand: so what you propose is to make the PC/SC just a client
o
Hi,
On Mittwoch, 4. Februar 2009, Ludovic Rousseau wrote:
> 2009/2/3 Martin Preuss :
> > 1) with pcscd all readers are always *on*. As soon as a reader is
> > connected it is started and polled for card insertion and removal even
> > when there is no client. I would very much like the pcscd to onl
2009/2/3 Alon Bar-Lev :
> In time I believe commonly used drivers may be migrated into new framework,
> to be more efficient, maintainable and share the common code base available
> in the reader library. Example: Logging, Protocols, Device Access etc.
I think you are too optimistic here. Many dri
Hello,
2009/2/3 Martin Preuss :
> 1) with pcscd all readers are always *on*. As soon as a reader is connected it
> is started and polled for card insertion and removal even when there is no
> client. I would very much like the pcscd to only power up a reader if there
> is at least one client. This
On Wednesday 04 February 2009 01:18:40 Martin Paljak wrote:
> If we talk about restructuring or "smoothing" the scene, we should
> really figure out some bits and pieces in the big picture and how they
> fit/should fit together to find the most rewarding locations to
> improve. Even if we r
On 03.02.2009, at 22:45, Alon Bar-Lev wrote:
> OpenSC is a great effort trying to join efforts and support as much
> devices
> as possible. The vision is great. So I fixed OpenSC PKCS#11
> implementation
> to actually work (fork(), plug&play etc...).
We should look at the broad picture of card
On Wednesday 04 February 2009 00:00:44 Martin Preuss wrote:
> As I see it the situation is this: There are applications which mandatory use
> the SCard interface provided by libpcsclite. There are other
> applications/libraries that can optionally use the SCard interface (as is the
> case with O
Hi list,
just a few thoughts from an outsider to OpenSC:
On Dienstag, 3. Februar 2009, Alon Bar-Lev wrote:
[...]
> I think a lot has changed since year 2000. Design practices were changed
> from blocking, threaded, single process model to none blocking, single
> threaded model. The number of popu
Hello Ludovic,
Thank you for replying.
On Tuesday 03 February 2009 12:42:40 Ludovic Rousseau wrote:
> I see _many_ advantages to your ideas. I even think of reusing some of them.
> What I don't want:
> - drop the IFDHandler API and drop support of existing drivers
> - engage in a multi-months de
Am Dienstag 03 Februar 2009 11:30:17 schrieb Ludovic Rousseau:
> I looked at the code of ifd-ikey2k.c and ifd-etoken.c and they are far
> from CCID.
well, openct is a very thin layer for those: get bytes from opensc,
put those into t=1, and put the t=1 result back to opensc.
t=1 calls the reader o
On 2/3/09, Ludovic Rousseau wrote:
> Hello,
>
> 2009/2/2 Alon Bar-Lev :
>> On Monday 02 February 2009 21:58:17 Andreas Jellinghaus wrote:
>>> but today pcsc-lite is active maintained by ludovic, has a huge amount of
>>> features, and works well. I wonder why anyone would want to spend a huge
>>> a
Hello,
2009/2/2 Alon Bar-Lev :
> On Monday 02 February 2009 21:58:17 Andreas Jellinghaus wrote:
>> but today pcsc-lite is active maintained by ludovic, has a huge amount of
>> features, and works well. I wonder why anyone would want to spend a huge
>> amount of time to get similar features ported
Hello,
Note that I have no idea how OpenCT works internally and externally. I
can't say if it is complex or not to maintain since I have never tried
:-)
2009/2/2 Andreas Jellinghaus :
> Hi Ludovic,
>
> how tied is the ccid reader to supporting ccid only?
> or could you implement other protocols i
31 matches
Mail list logo
