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
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.
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
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"
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
