W3C home > Mailing lists > Public > public-webauthn@w3.org > February 2019

RE: WebAuthn and dealing with authenticator firmware updates

From: Akshay Kumar <Akshay.Kumar@microsoft.com>
Date: Thu, 21 Feb 2019 00:07:53 +0000
To: Shane B Weeden <sweeden@au1.ibm.com>, "public-webauthn@w3.org" <public-webauthn@w3.org>
Message-ID: <MW2PR2101MB08895E138ED1E48259888249867E0@MW2PR2101MB0889.namprd21.prod.outlook.com>
My assumption right now is external authenticators don't upgrade. Upgrading the firmware needs to be thought through in terms of how securely one can upgrade. Also due to different form factors, mechanisms will be different. RP keeping a list of firmwares, which one is good and which one is not, is messy. And that list needs to be updated regularly by all the RPs. Which is another nightmare.

From: Shane B Weeden <sweeden@au1.ibm.com>
Sent: Wednesday, February 20, 2019 10:43 AM
To: public-webauthn@w3.org
Subject: WebAuthn and dealing with authenticator firmware updates

Per posting at:

I'm considering opening a WebAuthn issue for this topic to see if there is a POV amongst webauthn authors on dealing with authenticator firmware version updates. This note is simply to solicit any comments on the list before I do that.

Received on Thursday, 21 February 2019 00:08:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:59:02 UTC