Re: Supporting multiple keyboard

[James S. <jsi...@ac...>]

> Locking machine is not security hole... It is bad bug in software...

X windows also does this :( The security hole is the ablilty to write
software that can mmap the framebuffer and then vt switch via VT_ACTIVATE.
While the application is busy away on the text console the fbdev program
can be recording the info. 

> If they are graphics programs, they must either explicitly disable switching
> or they must be able to handle switches correctly.

For programs that hit the graphics hardware directly yes. Thats what the
KDSETMODE ioctl call will do. Set graphics mode and disable VT switching.
If the app wants to VT then it sets the mode back to KDSETMODE.
  
> I was talking only about security... That if you mmap /dev/fb and switch
> to syslog screen, you can get these data. It is not possible through 
> /dev/vcsa, as this can be controlled per-VT.

Thats right. I always use syslogd to recorded Oops. 

> I'd like to see some backward compatibility in picture. Until last month
> platan.vc.cvut.cz was still running '95s Slackware 3.0 (with couple of
> new things, such as glibc and kernel 2.3.33, but X was still old, non-matrox
> aware version).

Yeah. Backwards compatabilty should stay in until the end of the
developement cycle of 2.5.X. Just have the kernel print to the screen
Obsolete: Use /dev/input/eventX.