W3C home > Mailing lists > Public > public-webauthn@w3.org > November 2017

[w3c/webauthn] ba242b: Don't always require UV for first factor authentic...

From: GitHub <noreply@github.com>
Date: Tue, 14 Nov 2017 06:24:40 -0800
To: public-webauthn@w3.org
Message-ID: <5a0afca8737d9_75f63f9e6b313c3093026@hookshot-fe2-cp1-prd.iad.github.net.mail>
  Branch: refs/heads/issue-644
  Home:   https://github.com/w3c/webauthn
  Commit: ba242b9d5f7ea2b3534618d4d31890d5f993ae56
      https://github.com/w3c/webauthn/commit/ba242b9d5f7ea2b3534618d4d31890d5f993ae56
  Author: Emil Lundberg <emil@yubico.com>
  Date:   2017-11-14 (Tue, 14 Nov 2017)

  Changed paths:
    M index.bs

  Log Message:
  -----------
  Don't always require UV for first factor authenticatorGetAssertion

This requirement isn't compatible with the current CTAP2 draft.


  Commit: 7f831e3c7ebf669041c6413acc8005c3efa0eb8b
      https://github.com/w3c/webauthn/commit/7f831e3c7ebf669041c6413acc8005c3efa0eb8b
  Author: Emil Lundberg <emil@yubico.com>
  Date:   2017-11-14 (Tue, 14 Nov 2017)

  Changed paths:
    M index.bs

  Log Message:
  -----------
  Align authenticator operations' UP/UV behaviour with CTAP2


Compare: https://github.com/w3c/webauthn/compare/2969b37b04e8...7f831e3c7ebf
Received on Tuesday, 14 November 2017 14:25:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:58:44 UTC