[w3c/webauthn] 71f92c: Propose second-factor use case as mitigation for u...

• From: Emil Lundberg <noreply@github.com>
• Date: Mon, 01 Jul 2019 07:42:26 -0700
• To: public-webauthn@w3.org
• Message-ID: <w3c/webauthn/push/refs/heads/issue-1246-credentialid-privacy-leak/000000-62df7c>

  Branch: refs/heads/issue-1246-credentialid-privacy-leak
  Home:   https://github.com/w3c/webauthn
  Commit: 71f92c5dd3915ef37d47c1016d7bc35079e51125
      https://github.com/w3c/webauthn/commit/71f92c5dd3915ef37d47c1016d7bc35079e51125
  Author: Emil Lundberg <emil@yubico.com>
  Date:   2019-07-01 (Mon, 01 Jul 2019)

  Changed paths:
    M index.bs

  Log Message:
  -----------
  Propose second-factor use case as mitigation for username enumeration


  Commit: 62df7c16e1bf89dc04b2cc0a83e198b27ed93818
      https://github.com/w3c/webauthn/commit/62df7c16e1bf89dc04b2cc0a83e198b27ed93818
  Author: Emil Lundberg <emil@yubico.com>
  Date:   2019-07-01 (Mon, 01 Jul 2019)

  Changed paths:
    M index.bs

  Log Message:
  -----------
  Add privacy consideration about PII leak via credential IDs


Compare: https://github.com/w3c/webauthn/compare/71f92c5dd391%5E...62df7c16e1bf

Received on Monday, 1 July 2019 14:42:50 UTC