- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 04 Jul 2023 17:00:41 +0000
- To: public-webauthn@w3.org
- Message-Id: <E1qGjOL-001fu7-Na@uranus.w3.org>
Issues
------
* w3c/webauthn (+4/-1/💬17)
4 issues created:
- username and display name should not be mandatory (rp, challange either) and OS UX should be simplified if not present (by r-jo)
https://github.com/w3c/webauthn/issues/1915 [stat:Discuss] [subtype:FeatureProposal]
- Misaligned steps in Section 7.2 (by ndpar)
https://github.com/w3c/webauthn/issues/1913 [type:editorial]
- Update Authenticator Taxonomy examples section (by timcappalli)
https://github.com/w3c/webauthn/issues/1912 [type:editorial]
- Ambiguous reference to [=Window=] (by emlun)
https://github.com/w3c/webauthn/issues/1910 [type:editorial]
8 issues received 17 new comments:
- #1915 username and display name should not be mandatory (rp, challange either) and OS UX should be simplified if not present (3 by Firstyear, emlun)
https://github.com/w3c/webauthn/issues/1915 [stat:Discuss] [subtype:FeatureProposal]
- #1913 Misaligned steps in Section 7.2 (1 by emlun)
https://github.com/w3c/webauthn/issues/1913 [type:editorial]
- #1909 Revisit description of userHandle (2 by arianvp, emlun)
https://github.com/w3c/webauthn/issues/1909 [type:editorial]
- #1892 Require non-null userHandle when allowCredentials is empty? (1 by emlun)
https://github.com/w3c/webauthn/issues/1892 [type:technical] [@Risk]
- #1888 Clarify browser behavior when an authenticators return equivalent of "InvalidStateError" (1 by MasterKale)
https://github.com/w3c/webauthn/issues/1888 [type:editorial] [@Risk]
- #1856 Clarify the need for truly randomly generated challenges (aka challenge callback issue) (4 by dolda2000, sbweeden)
https://github.com/w3c/webauthn/issues/1856 [type:editorial] [@Risk]
- #1640 Syncing Platform Keys, Recoverability and Security levels (1 by mfisk)
https://github.com/w3c/webauthn/issues/1640 [type:technical] [@Risk]
- #1372 Consider allowing cross-domain credential use (4 by Mikescops, nadalin, sbweeden)
https://github.com/w3c/webauthn/issues/1372 [stat:Discuss] [@Risk]
1 issues closed:
- Add topOrigin to clientData for cross-origin GET in iframe https://github.com/w3c/webauthn/issues/1842 [type:technical]
Pull requests
-------------
* w3c/webauthn (+2/-2/💬4)
2 pull requests submitted:
- Address description of uses, and requirements for supplying userHandle (by sbweeden)
https://github.com/w3c/webauthn/pull/1914
- Disambiguate [=Window=] links as {{Window}} (by emlun)
https://github.com/w3c/webauthn/pull/1911 [type:editorial]
2 pull requests received 4 new comments:
- #1914 Address description of uses, and requirements for supplying userHandle (1 by sbweeden)
https://github.com/w3c/webauthn/pull/1914
- #1855 Recommend duration of challenge validity (3 by Kieun, emlun)
https://github.com/w3c/webauthn/pull/1855 [type:editorial]
2 pull requests merged:
- add client processing for topOrigin
https://github.com/w3c/webauthn/pull/1891
- Merge #1887 into main
https://github.com/w3c/webauthn/pull/1906
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/webauthn
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 July 2023 17:00:43 UTC