On Wed, 15 Mar 2000, Russell King wrote:
> James A Simmons writes:
> > > But anyway, i don't agree with you, there is no reason that a lots of people
> > > can open /dev/fb in read only mode, sure if some guys want to write to it at
> > > the same time, it could cause problems, ...
> >
> > Security :) One of the goals is to allow anyone to run a app on /dev/fb.
> > No more root.
>
> Erm, this is probably a silly question, especially as I haven't been following
> this thread in depth.
>
> If you're concerned about security, then you don't really want anyone to be
> able to open /dev/fb and read what you've got on your console. Think about
> it - allowing anyone to open /dev/fb means that you might as well broadcast
> the picture that is on your monitor to everyone who has access to your
> machine.
>
> I think think what you really want is to allow the user logged into the
> console to be able to read/write the framebuffer, in much the same way that
> /dev/console, /dev/dsp and friends are handled in a RedHat system - the
> ownership of these "console" based devices is changed when a user logs in
> at the console.
And changing the ownership of /dev/fb* is a userspace thingy, cfr. /dev/audio
and friends.
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.orgIn personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:17 EST