About Metadata Statement

127 views
Skip to first unread message

Skybird Le

unread,
Dec 30, 2016, 2:23:58 AM12/30/16
to FIDO Dev (fido-dev)
I heard Metadata Service is now available for U2F in Beta launching, but I'm confused with Metadata Statement specs. I have some questions as below.
1. Is each Metadata Statement only for a single authenticator model? What about different housing with different appearance (have different icon) but using same circuit design?
2. If the same authenticator model have individual attestation certificate for each piece of hardware, there should be infinite attestationCertificateKeyIdentifiers in the Metadata Statement. How to compose this type of Metadata Statement.
3. If we change the Attestation Certificate later for this type of authenticator, can I update the Metadata Statement in https://mymds.fidoalliance.org/ ?
4. If we change the Root certificate, can I use multiple  attestationRootCertificates and add multiple attestationCertificateKeyIdentifiers from different issuer for  this single authenticator?

Best Regards,
Skybird Le

Skybird Le

unread,
Jan 3, 2017, 12:57:08 AM1/3/17
to FIDO Dev (fido-dev)
Can anyone help me to answer these questions?

Rolf Lindemann

unread,
Jan 3, 2017, 3:50:47 AM1/3/17
to Skybird Le, FIDO Dev (fido-dev)
Hi,

here are some answers:
>1. Is each Metadata Statement only for a single authenticator model? What about different housing with different appearance (have different icon) but using same circuit design?

Yes, each Metadata Statement is for one single Authenticator Model.  The next question is how do we define Authenticator Model.  In general, each authenticator sharing the characteristics defined in the Metadata Statement belongs to that model.
Since housing color and form factor are not part of the Metadata Statement itself, you could have red, green and yellow authenticators all having being the same model.

> 2. If the same authenticator model have individual attestation certificate for each piece of hardware, there should be infinite attestationCertificateKeyIdentifiers in the Metadata Statement. How to compose this type of Metadata Statement.

For privacy reasons (see Unlinkability security goal, https://fidoalliance.org/specs/fido-uaf-v1.1-rd-20161005/fido-security-ref-v1.1-rd-20161005.html), FIDO requires Authenticators to share attestation keys/certificates across a large number of authenticators (e.g. see https://fidoalliance.org/specs/fido-uaf-v1.1-rd-20161005/fido-uaf-protocol-v1.1-rd-20161005.html#full-basic-attestation).  This applies to U2F as well.

> 3.  If we change the Attestation Certificate later for this type of authenticator, can I update the Metadata Statement in https://mymds.fidoalliance.org/ 
Yes.

4. If we change the Root certificate, can I use multiple  attestationRootCertificates and add multiple attestationCertificateKeyIdentifiers from different issuer for  this single authenticator?

Yes, if you mean single authenticator model by "... single authenticator".

Kind regards,
   Rolf


On Fri, Dec 30, 2016 at 8:21 AM, Skybird Le <skybi...@gmail.com> wrote:
I heard Metadata Service is now available for U2F in Beta launching, but I'm confused with Metadata Statement specs. I have some questions as below.
1. Is each Metadata Statement only for a single authenticator model? What about different housing with different appearance (have different icon) but using same circuit design?
2. 2. If the same authenticator model have individual attestation certificate for each piece of hardware, there should be infinite attestationCertificateKeyIdentifiers in the Metadata Statement. How to compose this type of Metadata Statement.
    3. If we change the Attestation Certificate later for this type of authenticator, can I update the Metadata Statement in https://mymds.fidoalliance.org/ ?
4. If we change the Root certificate, can I use multiple  attestationRootCertificates and add multiple attestationCertificateKeyIdentifiers from different issuer for  this single authenticator?

Best Regards,
Skybird Le




3
3

--
You received this message because you are subscribed to the Google Groups "FIDO Dev (fido-dev)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fido-dev+unsubscribe@fidoalliance.org.
To post to this group, send email to fido...@fidoalliance.org.
Visit this group at https://groups.google.com/a/fidoalliance.org/group/fido-dev/.
To view this discussion on the web visit https://groups.google.com/a/fidoalliance.org/d/msgid/fido-dev/189ad800-8121-4e7d-981f-159af4b282ec%40fidoalliance.org.



--

Rolf Lindemann
Senior Director, Products and Technology
 rlind...@noknok.com

Nok Nok Labs Inc.
2100 Geng Road, Suite 105
Palo Alto, CA 94303
T +1 650 433 1300
in...@noknok.com

www.noknok.com

 

 


Skybird Le

unread,
Jan 3, 2017, 4:54:06 AM1/3/17
to FIDO Dev (fido-dev), skybi...@gmail.com
Hi Rolf,
Thank you very much for you help and answers.
Our authenticators have same electric schematic but different housing and appearance, even the shape. For example, one type is circle, the other type is square, they have same functions, same firmware, same electronic elements, but different PCBs. So I want to know whether they belong to model.

Best Regards,
Geoffrey
To unsubscribe from this group and stop receiving emails from it, send an email to fido-dev+u...@fidoalliance.org.

Rolf Lindemann

unread,
Jan 3, 2017, 8:43:20 AM1/3/17
to Skybird Le, FIDO Dev (fido-dev)

Hi Geoffrey,

 

I am not sure I understand what differences the PCBs could have if *all* electronic elements (all CPUs, FPGAs, other ICs, etc.) are the same.

Let me give two examples:

a)      Authenticator A using a traditional microcontroller and Authenticator B using a smart CPU with substantial physical protection measures and Common Criteria evaluation – both supporting same instruction set and having the same software (i.e. firmware) running on it.

b)      Authenticator A using a microcontroller manufactured by company “a” and Authenticator B using a microcontroller manufactured by company “b” – both supporting same instruction set and having the same software (i.e. firmware) running on it.

 

In case b), I would think Authenticator A and B would be treated as being of the same model.

In case a), you might want to treat them as two different authenticator models as the security characteristics differ substantially and you might want to advertise one model with the enhanced security.  So you might want to use different Metadata Statements.

 

Note: in addition there is also the notion of derivative certification.  This allows simplified certification of a new authenticator model being similar (but not identical) to another already certified authenticator model.

 

Please see https://fidoalliance.org/certification/conformance-self%e2%80%90validation-testing/ for more details.

 

Kind regards,

  Rolf

Skybird Le

unread,
Jan 3, 2017, 9:04:05 PM1/3/17
to FIDO Dev (fido-dev), skybi...@gmail.com
Hi Rolf,
Your comments are very helpful to me, thank you very much.
Different PCBs are just made for different housing and appearance, both firmware and  circuit principle diagram are same. From that point of view they are same model.

Best Regards,
Geoffrey
Reply all
Reply to author
Forward
0 new messages