Skip to content

Allow setting qubes-split-gpg environment variables via QubesDB/vm-config #10640

@legoktm

Description

@legoktm

The problem you're addressing (if any)

To set config options for split-gpg, e.g. QUBES_GPG_AUTOACCEPT, you need to put it in the environment, usually by editing ~/.profile.

This means that any automated provisioning/configuration must edit a file in the VM to set it. It also adds state, which limits the effectiveness of dispVMs/partial dispVMs via custom-persist (c.f. freedomofpress/securedrop-workstation#1555 (comment))

The solution you'd like

It would be nice if we could set these via a vm-config pref, e.g. vm-config.QUBES_GPG_AUTOACCEPT so that way it can be provisioned directly from dom0 without needing to change things inside a VM. Presumably the code could be adjusted to first check the environment variable, and if it's not set, look at QubesDB, and then fall back to the default.

The value to a user and who that user might be

This would simplify provisioning via salt/ansible since the configuration can be set directly in dom0 and doesn't require changing things inside a VM. Plus it helps with moving state out of executable files into more disposable-friendly places.

Completion criteria checklist

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    C: coreThis issue pertains to a Qubes core component.C: split-gpg1This issue pertains to Split GPG version 1.C: split-gpg2This issue pertains to Split GPG version 2.P: defaultPriority: default. Default priority for new issues, to be replaced given sufficient information.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions