- From: John Schanck via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Dec 2023 19:53:00 +0000
- To: public-webauthn@w3.org
I'm happy with that level of detail. I would more explicitly call out the fingerprinting risk, and I would also note that lack of support can be a fingerprinting risk. So I would phrase your second paragraph as: > The client's support or lack of support of a WebAuthn capability may pose a fingerprinting risk. Client implementations MAY wish to limit capability disclosures based on client policy and/or user consent. -- GitHub Notification of comment by jschanck Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1923#issuecomment-1850782317 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 December 2023 19:53:02 UTC