Which Binaries and Scripts Are Included in dom0 by Default?

User Support General
1

Context

I have recently discovered that my dom0 contains the following binaries:

  • /usr/bin/input-proxy-sender
  • /usr/bin/input-proxy-receiver

According to the guide at GitHub - QubesOS/qubes-app-linux-input-proxy, it appears that input-proxy-receiver is expected to be available in dom0. This is implied by the usage of the --localcmd flag in the following command: qvm-run -u root --pass-io --localcmd="input-proxy-receiver --mouse" usbvm "input-proxy-sender /dev/input/event2".

Question

Is there a canonical way to determine which Qubes-specific binaries and scripts are expected to be present in dom0, and how they vary across versions?

1 Like
2

Not that I know of. As a starting point, you could write a dom0 script to list the files installed by RPM packages signed by a Qubes OS signing key.

2 Likes
3

I’ve decided to re-read the README of the qubes-app-linux-input-proxy repository, and I must have missed the part that says:

There are two packages available:
1. `qubes-input-proxy-sender` - to be installed in VM with actual input device
2. `qubes-input-proxy` - to be installed in dom0

Maybe these specific packages are not included in dom0 by default.

1 Like
4

They are:

2 Likes