LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* SAK and screen readers
@ 2006-12-05 23:50 Samuel Thibault
2006-12-06 0:26 ` Thomas Tuttle
0 siblings, 1 reply; 2+ messages in thread
From: Samuel Thibault @ 2006-12-05 23:50 UTC (permalink / raw)
To: linux-kernel; +Cc: mrkiko.rs, dave, sebastien.hinderer
Hi,
BrlTTY is a screen reader: it is a deamon run as root on machines used
by blind users for getting the content of the screen via braille or
speech.
BrlTTY, like other screen readers (susebl, yasr, ...) needs to open
/dev/tty0 for performing various actions, namely:
- VT_ACTIVATE
- GIO_UNISCRNMAP
- GIO_UNIMAP
- KDFONTOP
- VT_GETHIFONTMASK
- VT_GETSTATE
- KDGETMODE
- TIOCSTI
- KDGKBMETA
- KDGKBMODE
The problem comes when using SAK: brltty gets killed because it owns an
fd on /dev/tty0. This is a problem since the blind user then just can't
use her computer any more...
Some of the actions above are not directly related to the current VT, so
these could use a generic VT handle ; but at least KD* and TIOCSTI need
to be directed to the current VT, so brltty really needs to have an fd
on the current VT tty.
Could there be a solution for brltty yet not being killed by SAK? (like
letting brltty just nicely close his fd for the current VT, and then
re-open it later)
Samuel
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: SAK and screen readers
2006-12-05 23:50 SAK and screen readers Samuel Thibault
@ 2006-12-06 0:26 ` Thomas Tuttle
0 siblings, 0 replies; 2+ messages in thread
From: Thomas Tuttle @ 2006-12-06 0:26 UTC (permalink / raw)
To: linux-kernel; +Cc: Samuel Thibault, mrkiko.rs, dave, sebastien.hinderer
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
On December 05 at 18:50 EST, Samuel Thibault hastily scribbled:
> The problem comes when using SAK: brltty gets killed because it owns an
> fd on /dev/tty0. This is a problem since the blind user then just can't
> use her computer any more...
> <snip>
> Could there be a solution for brltty yet not being killed by SAK? (like
> letting brltty just nicely close his fd for the current VT, and then
> re-open it later)
How about this?
brltty launches a child process that opens the VT and pipes data back
and forth to the parent process via pipes or fifos.
When the SAK is pressed, the child process will die, and the parent
process will simply relaunch it.
It seems like any solution that involves the kernel not killing brltty
will compromise the (admittedly rudimentary) security that the SAK
offers.
Hope this helps,
Thomas Tuttle
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-12-06 0:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-12-05 23:50 SAK and screen readers Samuel Thibault
2006-12-06 0:26 ` Thomas Tuttle
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 NNTP newsgroup(s).