public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Hynek Hanke <hanke@brailcom.org>
To: Speakup <speakup@braille.uwo.ca>
Cc: Kirk Reiser <kirk@braille.uwo.ca>
Subject: Permissions for /dev/softsynth
Date: Thu, 28 Dec 2006 19:25:51 +0100	[thread overview]
Message-ID: <1167330352.3337.23.camel@chopin> (raw)


Hello,

I'm preparing a Debian package for SpeechD-Up and I'm puzzled with the
permissions to the /dev/softsynth device and the /proc/speakup/
controlls. The device is sometimes created by the user and sometimes
automatically, the proc tree is allways created when loading Speakup.
Is there some convention about who should be the owner and group
of /dev/softsynth and /proc/speakup?

I've been using the device as root so far, but this doesn't allow
me to run SpeechD-Up under a different user (e.g. speechd-up).
Making /dev/softsynth world readable is not an option too as it will
typically contain a complete log of users activity on the system
consoles, so it must be protected.

One more thing to consider is that there might be other interfaces
than SpeechD-Up wanting to access /dev/softsynth and /proc/speakup/ .

So it seems to me that it would be most sensible to create a group
with the name ''speakup'' and make /dev/softsynth and /proc/speakup
readable/writable by this group. Include user speechd-up in group
speakup and run SpeechD-Up with this user.

Should this be the correct approach, who will set the group ownership
for /dev/softsynth and /proc/speakup ? Should Speakup do it? Should it
be some user-space script? Which one?

The ownership change cannot be made in time of installation of
SpeechD-Up as there is not any guarantee that Speakup will already
be installed and that the device won't be deleted/re-created later (in
case of dynamically created device, it will).

I'd like to know your opinion.

Thank you,
Hynek Hanke



             reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Hynek Hanke [this message]
 ` Kirk Reiser
   ` Hynek Hanke
     ` Luke Yelavich
       ` Kirk Reiser
       ` Chris Norman
         ` Luke Yelavich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1167330352.3337.23.camel@chopin \
    --to=hanke@brailcom.org \
    --cc=kirk@braille.uwo.ca \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).