W3C home > Mailing lists > Public > public-webauthn@w3.org > September 2016

[webauthn] new commits pushed by equalsJeffH

From: =JeffH via GitHub <sysbot+gh@w3.org>
Date: Mon, 12 Sep 2016 23:50:27 +0000
To: public-webauthn@w3.org
Message-ID: <push-4fbfa4c315e679e2d29e9cee661049b165938898-1473724222-sysbot+gh@w3.org>

The following commits were just pushed by equalsJeffH to 

* Represent binary data as ArrayBuffers instead of base64-encoded 

Fixes #61.

I switched the main API completely from base64-encoded DOMStrings to
Buffersource (for input parameters) and ArrayBuffer (for output
parameters). The actual signatures are still computed over the same 
as before, so signatures computed after this change will be compatible
with those computed before, except for being represented differently.

I moved the ClientData section into the Authenticator model section
since it is not directly used by script authors. This structure still
does base64 encoding of the challenge, for two reasons. First, this
maintains backward compatibility. Second, it is more natural to
represent a binary challenge in JSON as base64 rather than the clunky
array notation.

I would like to advocate for also changing the rawData in the TPM and
packed attestation formats to ArrayBuffers so we can sign directly 
the data without base64 encoding. That would seem to simplify
processing. However this would break compatibility so I would like to
gather opinions from the group before making that change. On the 
side, I do not know of any implementations producing WebAuthn
attestation statements in these formats yet.
  by Vijay Bharadwaj

* Remove base64 from packed and TPM attestation formats

Remove base64 encoding from the rawData fields and return them 
as ArrayBuffers.
  by Vijay Bharadwaj

* Clarify Android attestation procedure
  by Vijay Bharadwaj
Received on Monday, 12 September 2016 23:50:41 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:22 UTC