Re: [Muscle] Re: [opensc-devel] Defining default paths for chipcard drivers

2007-05-01 Thread Andreas Jellinghaus
On Wednesday 02 May 2007 06:17:29 Martin Preuss wrote: > On Wednesday 02 May 2007 00:27, Michael Bender wrote: > > Andreas Jellinghaus wrote: > > > On Tuesday 01 May 2007 21:14:26 Martin Preuss wrote: > > >> For CTAPI drivers there is also another problem that should be > > >> addressed in the next

Re: [Muscle] Re: [opensc-devel] Defining default paths for chipcard drivers

2007-05-01 Thread Andreas Jellinghaus
On Wednesday 02 May 2007 00:27:42 Michael Bender wrote: > How does this access control mechanism work? openct uses a status file and sockets, both placed in /var/run/openct/ only those with 0700 -> only root can access it. 0750 -> those in the group can use openct too, 0755 -> everyone can use it.

Re: [Muscle] Re: [opensc-devel] Defining default paths for chipcard drivers

2007-05-01 Thread Martin Preuss
On Wednesday 02 May 2007 00:27, Michael Bender wrote: > Andreas Jellinghaus wrote: > > On Tuesday 01 May 2007 21:14:26 Martin Preuss wrote: > >> For CTAPI drivers there is also another problem that should be addressed > >> in the next step: I think it would be best to have a system > >> group/user

Re: [Muscle] Re: [opensc-devel] Defining default paths for chipcard drivers

2007-05-01 Thread Michael Bender
Andreas Jellinghaus wrote: On Tuesday 01 May 2007 21:14:26 Martin Preuss wrote: For CTAPI drivers there is also another problem that should be addressed in the next step: I think it would be best to have a system group/user "chipcard" (or whatever name is feasible) analogous to the groups "disk"

Re: [Libchipcard-devel] [opensc-devel] [Muscle] Re: Defining default paths for chipcard drivers

2007-05-01 Thread Martin Preuss
Hi, On Tuesday 01 May 2007 23:00, Peter Stuge wrote: > On Tue, May 01, 2007 at 10:19:56PM +0200, Andreas Jellinghaus wrote: > > On Tuesday 01 May 2007 21:14:26 Martin Preuss wrote: > > > For CTAPI drivers there is also another problem that should be > > > addressed in the next step: I think it wou

Re: [Muscle] Re: [opensc-devel] Defining default paths for chipcard drivers

2007-05-01 Thread Andreas Jellinghaus
On Tuesday 01 May 2007 21:14:26 Martin Preuss wrote: > For CTAPI drivers there is also another problem that should be addressed in > the next step: I think it would be best to have a system > group/user "chipcard" (or whatever name is feasible) analogous to the > groups "disk", "audio" etc. FYI: d

[Muscle] Re: [opensc-devel] Defining default paths for chipcard drivers

2007-05-01 Thread Martin Preuss
Hi, On Tuesday 01 May 2007 18:29, Hanno Böck wrote: [...] > Now, already some technical thoughts: > - We have, as far as I know, two kinds of chipcard-related driver types: > pcsc drivers and ctapi. > - At the moment, I can't see a reason why we shouldn't make it so simple to > just say "put all c

[Muscle] Defining default paths for chipcard drivers

2007-05-01 Thread Hanno Böck
Hi, I recently had a discussion with martin preuss on the libchipcard-devel-list about the paths where drivers of chipcard-readers resist on a linux-system. Currently, libchipcard has for every driver a whole bunch of possible locations and is looking on all of them. Not a very nice solution, t