From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from uq.net.au(fox.uq.net.au[203.101.255.1]) (1401 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Wed, 14 Feb 2001 19:58:30 -0500 (EST) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from data.home (mail@dyn-25-89.dialin.uq.net.au [203.100.25.89]) by uq.net.au (8.9.3/8.9.3) with ESMTP id KAA27773 for ; Thu, 15 Feb 2001 10:58:30 +1000 (GMT+1000) Received: from geoff by data.home with local-esmtp (Exim 3.12 #1 (Debian)) id 14TCkf-000390-00; Thu, 15 Feb 2001 10:58:29 +1000 Date: Thu, 15 Feb 2001 10:58:29 +1000 (EST) From: Geoff Shang To: Subject: Re: /proc/speakup In-Reply-To: <200102150030.QAA10156@viper.wapvi.bc.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: Hi: Well of course, you can still be behind a firewall if you run one on the linux box itself, but your point is a good one. As much as I don't fear hackers, I am bothered that another user could arbitrarily set my speech params to something else, like the volume to minimum or something. Jim and I are debating this currently on the reflector. My current thinking is to make it all root writeable only and get users to implement sudo for non-root access, but unless you want to force this situation onto people you need to make the proc/speakup permissions settable, which they aren't at present. Geoff.