Microchip ATECC608C-TNGTLS Handleiding

Microchip Niet gecategoriseerd ATECC608C-TNGTLS

Lees hieronder de 📖 handleiding in het Nederlandse voor Microchip ATECC608C-TNGTLS (19 pagina's) in de categorie Niet gecategoriseerd. Deze handleiding was nuttig voor 3 personen en werd door 2 gebruikers gemiddeld met 4.5 sterren beoordeeld

Pagina 1/19
Trust Platform Manifest File Format
Overview
The manifest file format is designed to convey the unique information about a group of secure subsystems, including
unique ID (e.g., serial number), public keys and certificates. This was primarily developed for CryptoAuthentication
â„¢
(currently ATECC508A, ATECC608A and ATECC608B) secure elements. However, it is structured to work for other
secure subsystems as well.
Manifest files provide a way to link an actual Microchip Trust security device to the infrastructure environment that
it needs to connect to. These files are a critical aspect of the Microchip Trust&GO, TrustFLEX and, optionally,
TrustCUSTOM development environments. Whether you connect to an IoT cloud, a LoRaWAN
® network or,
potentially, any other infrastructure or environment, the manifest file uniquely ties a given device to that environment.
When working with Microchip Trust&GO, TrustFLEX or TrustCUSTOM products, a manifest file will be generated for
a group of devices that are provisioned through the Microchip Just-In-Time provisioning services. Each object entry
in the manifest file is known as a signed secure element and is signed by a Microchip Elliptic Curve Cryptography
(ECC) private key to validate its authenticity. The overall manifest is made of multiple signed secure elements.
Specific information associated with the manufacturer, the secure product device and specific individual device
information are all part of the information associated with a given signed secure element.
The manifest file is available in a secure fashion only to the customer that orders the group of devices. Accessing
these manifest files is part of the development and provisioning flow provided through Microchip. Once provisioning is
completed for a group of products, the manifest file is available for download.
© 2022 Microchip Technology Inc.
and its subsidiaries
Family Reference Manual DS60001759A-page 1
Table of Contents
Overview........................................................................................................................................................ 1
1. Manifest Generation................................................................................................................................3
1.1. Microchip vs. Self-Generated Files.............................................................................................. 3
1.2. Trust&GO vs. TrustFLEX vs. TrustCUSTOM Files.......................................................................4
1.3. Prototype vs. Production Device Files..........................................................................................4
2. Structure and Format of a Manifest File..................................................................................................5
2.1. Introduction...................................................................................................................................5
2.2. Binary Encoding........................................................................................................................... 5
2.3. SecureElementManifest Object....................................................................................................5
2.4. SignedSecureElement Object...................................................................................................... 5
2.4.1. SignedSecureElementProtectedHeader Object............................................................ 6
2.5. SecureElement Object................................................................................................................. 6
2.6. EntityName Object....................................................................................................................... 7
2.7. PublicJWK Object.........................................................................................................................8
2.8. EncryptedSecretJWK Object........................................................................................................8
2.9. ModelInfo Object.......................................................................................................................... 8
2.9.1. CryptoAuthentication ModelInfo Object......................................................................... 8
2.9.1.1. CryptoAuthPublicDataElement Object........................................................ 9
3. Manifest File Example and Decoding....................................................................................................10
3.1. Manifest Example.......................................................................................................................10
3.2. Decode Python Example............................................................................................................12
4. Revision History.................................................................................................................................... 15
The Microchip Website.................................................................................................................................16
Product Change Notification Service............................................................................................................16
Customer Support........................................................................................................................................ 16
Microchip Devices Code Protection Feature................................................................................................ 16
Legal Notice................................................................................................................................................. 16
Trademarks.................................................................................................................................................. 17
Quality Management System....................................................................................................................... 18
Worldwide Sales and Service.......................................................................................................................19
© 2022 Microchip Technology Inc.
and its subsidiaries
Family Reference Manual DS60001759A-page 2
1. Manifest Generation
The manifest of the TrustFLEX and Trust&GO devices can be generated in two scenarios. One is through the
Microchip Just-In-Time provisioning services (Microchip-generated) and the second one is a custom generation using
the scripts provided (self-generated).
In both cases, the Trust&GO, TrustFLEX and TrustCUSTOM devices will have different information due to differences
in their configuration.
The following sections provide manifest file differences between:
1. Microchip and self-generated files
– Manifest signature
2. Trust&GO and TrustFLEX files
3. Prototype and production device files
1.1 Microchip vs. Self-Generated Files
The manifest file format and generation procedures are public information; hence, they can be generated by users.
Due to this nature and when the procedures are followed, there will still be minor differences between Microchip and
self-generated files.
Manifest Signature
In the manifest file, each element is signed to ensure the integrity of the content. For a Microchip-generated manifest
file, the signing operation is performed by Microchip using its Certificate Authority (CA). The corresponding CA
certificate can be downloaded from the Microchip website. This certificate can be used to validate the authenticity of
the Microchip-generated files.
Tip: 
• (under tab)
MCHP Manifest Signer Certificates Documentation
•Direct link to Download
For a self-generated manifest file, it is not possible to get each element signed by Microchip CA, as users do not
have access to a CA private key. It is required to generate/use a local CA to perform the signature operations. In
this case, the users must share the validation certificate along with the manifest file to others. This enables them to
validate the content before using it further.
The other differences include:
1. Trust&GO – Content remains the same, as the device data are immutable, but signature and verification
certificates are different, as self-generated scripts use their own CA.
2. TrustFLEX
a. Device and signer certificates can be different if custom PKI is selected during resource generation.
b. Slots 1-4, 13-15 vary based on additional key generations as part of resource generation at the user’s
location.
c. Signature and verification certificates are different, as self-generated scripts use their own CA.
The Trust Platform Design Suite provides the required scripts/tools to self-generate the manifest files.
Tip: 
•Trust&GO manifest generation scripts
•TrustFLEX manifest generation scripts (with dev key generation)
Manifest Generation
© 2022 Microchip Technology Inc.
and its subsidiaries
Family Reference Manual DS60001759A-page 3


Product specificaties

Merk: Microchip
Categorie: Niet gecategoriseerd
Model: ATECC608C-TNGTLS

Heb je hulp nodig?

Als je hulp nodig hebt met Microchip ATECC608C-TNGTLS stel dan hieronder een vraag en andere gebruikers zullen je antwoorden




Handleiding Niet gecategoriseerd Microchip

Handleiding Niet gecategoriseerd

Nieuwste handleidingen voor Niet gecategoriseerd