public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: <bardiazakeri@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: World writable speakup files in Linux next
Date: Mon, 13 Dec 2010 17:52:03 +0100	[thread overview]
Message-ID: <93564A09B17C45BE9B870D49EC802549@BardiaDator> (raw)
In-Reply-To: <20101213145306.GA8824@rivensight.dyndns.org>

how i install speakup in ubuntu

--------------------------------------------------
From: "Frost" <znvyyvfgf@gmail.com>
Sent: Monday, December 13, 2010 3:53 PM
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: World writable speakup files in Linux next

> On Mon, Dec 13, 2010 at 02:06:12PM +0100, Samuel Thibault wrote:
>> > >But, the world writable bit can be seen as a big security issue right
>> > >now, right?  It would be good to get that fixed, or at the very least,
>> > >narrowed down a lot right now.
>
> Can't you just monitor for keyboard activity alone, as when
> you're in a terminal console, operating the system remotely, you don't
> need to issue commands to SpeakUP?  Only at the local keyboard?
>
> Maybe it's too complicated because of the kernel or what-not.  I
> don't know.  I just figure that if it's not coming from /dev/Stty#, then
> the command should be allowed, or only allowed if the commands are being
> issued by a logged in user at the console, unless it's a major security
> risk to have the cat accidently pressing a SpeakUp key combo.  If you
> trust a person on your system enough to give them a user account, then
> it stands reasonable that you alsod trust them enough not to F with /sys
> and speakupconf without knowing what they're doing
>
> Michael
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

      parent reply	other threads:[~ UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101210190047.GA19219@kroah.com>
 ` William Hubbs
   ` Frost
 ` Christopher Brannon
   ` William Hubbs
     ` Samuel Thibault
     [not found]       ` <20101212182940.GB16883@kroah.com>
         ` Kirk Reiser
           ` Samuel Thibault
             ` Kirk Reiser
               ` Samuel Thibault
               ` acollins
                 ` Samuel Thibault
             ` Frost
               ` Samuel Thibault
                 ` Kitty Litter
                   ` Samuel Thibault
                 ` Frost
                   ` bardiazakeri
                     ` Frost
                       ` bardiazakeri
                         ` Littlefield, Tyler
                           ` bardiazakeri
                             ` Kerry Hoath
                               ` Littlefield, Tyler
                                 ` Arch Linux was: " Øyvind Lode
                           ` bardiazakeri
                           ` speakup and ubuntu, was: " Gregory Nowak
                             ` Littlefield, Tyler
                   ` Samuel Thibault
                   ` Michael Whapples
                     ` Samuel Thibault
                       ` Frost
               ` bardiazakeri [this message]

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=93564A09B17C45BE9B870D49EC802549@BardiaDator \
    --to=bardiazakeri@gmail.com \
    --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).