> Yes, in 4.2 you can configure it with "qubes global config", including enabling/disabling it per-qube - it will setup appropriate qrexec policy.
Starting from no configured access to u2-proxy, editing with the Gobal config tool only created policies for u2f.Register and u2f.Authenticate. Nothing for ctap.ClientPin not ctap.getInfo.
Starting from no configured access to u2-proxy, editing with the Gobal config tool only created policies for u2f.Register and u2f.Authenticate. Nothing for ctap.ClientPin not ctap.getInfo.
Originally posted by @euidzero in https://github.com/QubesOS/qubes-issues/issues/8586#issuecomment-1761194807