For myself, I probably be using group security. I will create a speakup group and limit all access to these files to root and to those who are in the speakup group. Terry -----Original Message----- From: Holmes, Steve [mailto:SAHolmes@xxxxxxxxxxxxxxxxxx] Sent: Thursday, February 15, 2001 3:10 PM To: 'speakup at braille.uwo.ca' Subject: RE: /proc/speakup I could certainly see why. It was just an idea. If I were to cast a vote on this, I would go for root-only access to the /proc/speakup files. I think most of the time, speakup would be running on a single blind person's machine and he/she is probably the only one using it so that person would most likely have root privileges. -----Original Message----- From: Kerry Hoath [mailto:kerry@xxxxxxxxxxxx] Sent: Thursday, February 15, 2001 9:05 AM To: speakup at braille.uwo.ca Subject: Re: /proc/speakup Setuid shellscripts are disabled by default because of the problems they introduce. You _can_ enable them somehow but it is highly discouraged. On Thu, Feb 15, 2001 at 07:15:48AM -0700, Holmes, Steve wrote: > Well, here's an idea; How about making the /proc/speak system root writeable > only and provide a user script that could be used by the user and have it > setuid to update the system. As I think about this, I suppose that really > wouldn't be any different than opening up the /proc files. > > -----Original Message----- > From: Geoff Shang [mailto:gshang at uq.net.au] > Sent: Thursday, February 15, 2001 6:01 AM > To: speakup at braille.uwo.ca > Subject: Re: /proc/speakup > > > On Thu, 15 Feb 2001, Steve Holmes wrote: > > > I thought I heard a while back that only root could update these files. > > Is that so? > > That is not so. The files in /proc/speakup apart from the exceptions > discussed earlier today can be updated by any user on the system. There > are some files in /proc/speakup/<synth> (where <synth> is the currently > used synth) which contain data that, if modified, might cause serious > damage to the system. These files therefore can only be modified by root. > > Since the proc file system is only a vertual file system, commands like > chmod and chown do not actually work, even though they return without > errors. The permissions have to be set as part of the speakup code. Jim > and I discussed alternative access methods for these files, but the choices > seem to be access for all or access for no-one except root, without making > it a configurable option in either the kernel command line or perhaps the > kernel config. Personally, I'd be quite happy to see all this be root > access only, but I can understand why people might want to be able to > change synth settings in user-space. > > Geoff. > > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- -- Kerry Hoath: kerry at gotss.eu.org Alternates: kerry at emusys.com.au kerry at gotss.spice.net.au or khoath at lis.net.au ICQ UIN: 8226547 _______________________________________________ Speakup mailing list Speakup at braille.uwo.ca http://speech.braille.uwo.ca/mailman/listinfo/speakup _______________________________________________ Speakup mailing list Speakup at braille.uwo.ca http://speech.braille.uwo.ca/mailman/listinfo/speakup
