Brian Duggan bcduggan

Automatically activate user session with loginctl in Qubes debian-12-minimal template (#7689 workaround)

debian-12-minimal templates in Qubes don't recognize USB devices by default. They require the qubes-usb-proxy package. But a longstanding issue ((#7689) prevents users from interacting with connected USB devices. Qubes documentation for Debian miminal templates describes manually using loginctl to activate the current user session to resolve this. But it doesn't describe a way to automatically activate the user session.

Until the team resolves #7689, I'm using this method to automatically activate the user session on debian-12-minimal templates. It relies on the rc.local script to execute commands on qube

DEPRECATED

See https://github.com/bcduggan/qrexec-connect

Instantiate Qubes RPCs and clients for systemd services with symlinks

Specifically, (Unix) socket-activated systemd services

I frequently want to allow client qubes to connect to existing (Unix) socket-activated systemd services on service qubes, like GnuPG's SSH and extra sockets, or a socket created by rclone serve. But I don't want to write a new RPC and corresponding

Qubes RPC for git remotes over qrexec

This gist describes a set of configurations to implement a new set of Qubes RPCs, qubes.GitUploadPack and qubes.GitReceivePack. These RPCs allow a client qube to clone, fetch, push, etc from local repositories to repositories on service qubes over qrexec. Qubes policy can control ro (clone, fetch, etc) and rw (push, etc) access per-repository.

The RPCs only allow access to git repositories on the service qube filesystem. They do not connect the client qube to internet git servers or forges.

However, the service qube can mount directories of git repositories to its filesystem from any remote storage service.

Purpose

Target Qubes VMs with tags in Salt Pillar data

Qubes allows users to target VMs in top files using pillar data:

base:
  qubes:type:app:
    - match: pillar
    - a_state

Keybase proof

I hereby claim:

I am bcduggan on github.
I am bcduggan (https://keybase.io/bcduggan) on keybase.
I have a public key whose fingerprint is CB26 03A6 423F AB00 1D12 ABCC 99CB D800 8AE8 179B

To claim this, I am signing this object:

	-----BEGIN PGP SIGNED MESSAGE-----
	Hash: SHA512

	OpenPGP Key Transition Statement for Brian C. Duggan

	I have created a new OpenPGP key and will transition away from my old
	key. I have no reason to belive that my old key has been
	compromised. However, I have revoked it because the new key supersedes
	it. Starting now, I will make all signatures with the new
	key. Starting now, please encrypt data that you intend to send to me