On 11/30/2016 04:18 AM, pixel fairy wrote:
> has anyone here experimented with bluetooth locks? it seems like a lot of
> extra scary code to run in dom0, but i like the idea of auto shutdown if
> device loses range. or maybe after a timeout period of some trigger?thats
> another discussion.
On your Bluetooth VM (usually a USBVM), run Blueproximity, and have
Blueproximity invoke a custom /etc/qubes-rpc/pixelfairy.Lock service on
dom0 which you will need to write yourself. It's a one-liner service:
loginctl lock-sessions
To invoke it from the Bluetooth VM, you need to ask Blueproximity to run
the command:
/usr/lib/qubes/qrexec-client-vm "$bluetoothvm" pixelfairy.Lock
Once you have given the Bluetooth VM permission ("yes to all") to invoke
the locker, it should work automatically every time you walk away.
The reverse is also possible — you could have a similar service that
unlocks the screen by running loginctl unlock-sessions.
--
Rudd-O
http://rudd-o.com/
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/cd707267-d4c1-2a3c-a155-1d2cb89e850e%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.
