Make CTAP proxy installation documentation more precise #9708
Labels
C: doc
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
How to file a helpful issue
The problem you're addressing (if any)
I'm working on a separate vm-sys template, usable for sys-net-dvm, sys-firewall-dvm and sys-usb-dvm. I want to give the documentation of this to the Qubes User Docs, why I want to write it as exact as possible.
sys-usb-dvm shall be able to work as the backend part of the CTAP proxy
https://www.qubes-os.org/doc/ctap-proxy/
The doc gives a good explanation of the topic, but in the Installation-part it's inexact at a few places, why I can't decide, what steps have to be done on my vm-sys template and what on the work templates.
As it's not completely clear, what parts of the qubes-ctap package are used in sys-usb and what in the work qubes, the following parts need clarification:
In which templates do we need to intall the qubes-ctap package?
"Non-default USB qube name"
What are the "appropriate" templates for the systemctl commands in that part?
The solution you'd like
The value to a user, and who that user might be
Completion criteria checklist
(This section is for developer use only. Please do not modify it.)
The text was updated successfully, but these errors were encountered: