Nicolas Pitre writes:
> On Sun, 25 Jun 2023, Dave Mielke wrote:
>
>> [quoted lines by Crystal Kolipe on 2023/06/25 at 21:17 -0300]
>>
>> >It's certainly possible to patch OpenBSD to implement a screen
>> readout device that would potentially allow brltty to access the
>> console independently
Nicolas Pitre writes:
> On Sun, 25 Jun 2023, Dave Mielke wrote:
>
>> [quoted lines by Christian Schoepplein on 2023/06/25 at 20:59 +0200]
>>
>> >For me it is OK to set
>> >
>> >dev.tty.legacy_tiocsti=1
>> >
>> >in /etc/sysctlconf as a workaround like Rob suggested, thanks Rob for this
>>
Dave Mielke, le lun. 26 juin 2023 12:49:05 -0400, a ecrit:
> TIOCSTI injects input. Of course one could argue that that poses a security
> risk, but how is that different from creating a uinput device and injecting
> key events? What am I missing?
Basically, TIOCSTI is not privileged and
TIOCSTI injects input. Of course one could argue that that poses a security
risk, but how is that different from creating a uinput device and injecting key
events? What am I missing?
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke| 2213 Fox
Hi,
On 2023-06-25 at 16:10 -0400, Dave Mielke wrote:
> [quoted lines by Christian Schoepplein on 2023/06/25 at 20:59 +0200]
> >For me it is OK to set
> >
> >dev.tty.legacy_tiocsti=1
> >
> >in /etc/sysctlconf as a workaround like Rob suggested, thanks Rob for this
> >hint!
> I'm
On Sun, 25 Jun 2023, Dave Mielke wrote:
> [quoted lines by Crystal Kolipe on 2023/06/25 at 21:17 -0300]
>
> >It's certainly possible to patch OpenBSD to implement a screen readout
> >device that would potentially allow brltty to access the console
> >independently of any particular login
On Sun, 25 Jun 2023, Dave Mielke wrote:
> [quoted lines by Christian Schoepplein on 2023/06/25 at 20:59 +0200]
>
> >For me it is OK to set
> >
> >dev.tty.legacy_tiocsti=1
> >
> >in /etc/sysctlconf as a workaround like Rob suggested, thanks Rob for this
> >hint!
>
> I'm wondering if brltty
