Weekly github digest (WebAuthn)

Issues
------
* w3c/webauthn (+1/-2/💬11)
  1 issues created:
  - Is it possible to fail the registration ceremony if a certain extension is not present? (by arianvp)
    https://github.com/w3c/webauthn/issues/1487 

  5 issues received 11 new comments:
  - #1487 Is it possible to fail the registration ceremony if a certain extension is not present? (4 by arianvp, ve7jtb)
    https://github.com/w3c/webauthn/issues/1487 
  - #1485 Handling unwanted or unsupported attestation formats (1 by nicksteele)
    https://github.com/w3c/webauthn/issues/1485 [type:editorial] 
  - #1484 Regarding the issue of Credential ID exposure(13.5.6), from what perspective should RP compare RK and NRK and which should be adopted? (1 by keikoit)
    https://github.com/w3c/webauthn/issues/1484 [type:editorial] 
  - #1363 Provide the public key in `AuthenticatorAttestationResponse` (3 by CrazyChris75, agl)
    https://github.com/w3c/webauthn/issues/1363 [priority:low] [stat:pr-open] [type:technical] 
  - #1258 Clearly define the way how RP handles the extensions (2 by Kieun, madwizard-thomas)
    https://github.com/w3c/webauthn/issues/1258 [subtype:extensions] [subtype:rp-ops] [subtype:underspecifiedBehaviors] 

  2 issues closed:
  - Is it possible to fail the registration ceremony if a certain extension is not present? https://github.com/w3c/webauthn/issues/1487 
  - Handling unwanted or unsupported attestation formats https://github.com/w3c/webauthn/issues/1485 [type:editorial] 




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