migration to fido2: proxy setup clarification to avoid confusing errors

solves QubesOS/qubes-issues/issues/9064
This commit is contained in:
Piotr Bartman-Szwarc 2024-11-12 13:05:49 +01:00
parent 78b0742362
commit eea342bdb0
No known key found for this signature in database
GPG Key ID: E386DC76B775C5C9

View File

@ -85,7 +85,7 @@ $ sudo qubes-dom0-update qubes-ctap-dom0
$ qvm-service --enable work qubes-ctap-proxy $ qvm-service --enable work qubes-ctap-proxy
``` ```
The above assumes a `work` qube in which you would like to enable ctap. Repeat the `qvm-service` command for all qubes that should have the proxy enabled. Alternatively, you can add `qubes-ctap-proxy` in VM settings -> Services in the Qube Manager of each qube you would like to enable the service. The above assumes a `work` qube in which you would like to enable ctap. Repeat the `qvm-service` command for all qubes that should have the client proxy enabled. Alternatively, you can add `qubes-ctap-proxy` in VM settings -> Services in the Qube Manager of each qube you would like to enable the service. Attempting to start the `qubes-ctap-proxy` service in the device-hosting qube (`sys-usb`) will fail.
In Fedora templates: In Fedora templates: