Qubes and split-gpg2: which operation authorizes the prompt?
A prompt displayed by a trusted environment still needs to match an expected operation. QSB-124 provides a reason to review authorized clients and execution after an update.
Ler em portuguêsBy Pentesty
Window origin is one part of the evidence
The SempreUpdate report published November 17 covers QSB-124, dated November 13 and announced November 14. A malicious split-gpg2 client can trigger a prompt with arbitrary text and receive the response while the window carries the backend's borders. Under the supported configuration, the bulletin maintains the restriction against extracting or manipulating secret keys.
The project architecture separates client processing from private material held by the server. Businesses therefore need two records: where the key remains and who can request an operation. Familiar presentation helps identify the domain, while approval also needs the context of the task being performed.
Tie approval to a specific task
Consider a workstation used by a legal team to sign documents. Before accepting a request, the operator should recognize the document they opened, the identity expected to sign it and the application that initiated the workflow. This proposed procedure reduces decisions based solely on window color. It is an operational check, with no claim of an additional product capability.
Define a verification route for unexpected requests. Someone can pause the task and contact support through an established channel, providing the time, client qube and activity they started. Avoid asking for screenshots containing secrets. A useful report lets the owner reconstruct the sequence without collecting the password the organization wants to protect.
Map the clients that reach the backend
Build a short inventory for each business workflow: client, template, backend, purpose, expected key or subkey and authorization owner. Compare effective policy with that inventory. Record maintenance exceptions separately so that temporary permission does not silently become part of routine contract, release or team-message signing. Include the person who can explain why an exception remains necessary.
The project classifies allow_keygen as unsupported for security; the QSB describes greater impact in that configuration. Locate any exceptions and refer the decision to the key owner. Assessment should reflect the configuration actually deployed. The criteria for approving signing software changes provide a useful way to organize that review.
Finish the update at execution
For Qubes 4.3, the QSB lists split-gpg2 1.1.16 and requires shutting down relevant templates and restarting backends. Follow the official update procedure and check availability in your organization's chosen channel. A version being present in testing does not establish its distribution through the environment's stable channel.
Keep the installed version, corresponding template, shutdown time and restart of each affected backend in the change record. Then perform a harmless signature from an authorized client and verify the result. Separately check access policy for a client without permission. The approach of checking the running process after a patch helps structure this operational evidence.
Decide who can close the change
The service owner should accept functional results; security should review permissions and evidence; workstation administrators should record restarts. If one element is missing, keep the open item visible with an owner and deadline. A package installed in one template does not describe the state of every workstation it serves. Make that scope clear to whoever approves closure.
Pentesty proposes this record as an acceptance criterion for environments relying on isolation and signing. Use synthetic data and an authorized window, with agreed stop conditions. The expected result is a verifiable connection between task, client, backend and produced signature, accompanied by any limitations that still require follow-up. Preserve enough evidence for a different reviewer to understand the decision.
Frequently asked questions
Is a familiar window enough to approve a request?
Connect the request to the task you started, the expected identity and the authorized client. When a request is unexpected, pause the workflow and confirm its context with the service owner.
Does every workstation need the same response?
Start with the actual inventory of components, policies and keys in use. Record configuration differences and review exceptions with the owner, rather than assuming every workstation follows an identical design.
What evidence supports closing the change?
Keep the version, affected environments, restart records and result of a harmless operation. Identify who checked functionality and who accepted the permissions after the change.
Must the test collect passwords or keys?
Plan validation with synthetic data and avoid recording secrets. A workflow and authorization demonstration should produce enough evidence for the agreed decision, with its limitations documented.
Sources and references
- SempreUpdate: QSB-124 news reference
- Qubes OS: QSB-124 scope, impact and patching
- QubesOS: split-gpg2 architecture and configuration
- Qubes OS: official update procedure
Original Pentesty analysis, published November 17, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.