Oh, it just occurred to me that those lines aren't necessarily mutually
exclusive. Is that correct? So one allows local connections, another
restricts authentication to a given group. I assumed that they both
controlled access to a single connection mechanism of some sort.
In any case, thanks for the help getting this going. Works nicely now.
My only remaining question is whether it is possible to use the Braille
keyboard on the Orbit under Orca? It works fine on the console, but is
unresponsive under Orca/X. I'd thought to use the Orbit as a small
keyboard on a screenless Intel NUC as a laptop replacement, but looks
like I may need to spring for a separate keyboard there as well.
On 6/12/19 12:27 AM, Dave Mielke wrote:
[quoted lines by Nolan Darilek on 2019/06/11 at 22:16 -0500]
If by "kernel" you mean the Linux kernel, I did nothing at all with the
kernel. I simply replaced this line:
#api-parameters Auth=group:brlapi # Allow some local group
with this one:
api-parameters Host=:0 # Accept only local Unix connections
okay. That's what you meant by:
I enabled local-only auth via a Unix socket.
And then it worked. But my user is in the brlapi group, so I'm not clear on
why I received logs implying that it wasn't.
It's been a long time since I've looked at the capability, but I don't think
that it's possible to determine which user and/or groups the client is in when
an IP socket is being used.
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://brltty.app/mailman/listinfo/brltty
