Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sztp: how to get access to TPM vendor-specific-agnostic #2

Open
glimchb opened this issue Oct 5, 2022 · 3 comments
Open

sztp: how to get access to TPM vendor-specific-agnostic #2

glimchb opened this issue Oct 5, 2022 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@glimchb
Copy link
Member

glimchb commented Oct 5, 2022

per https://github.com/opiproject/opi-prov-life/blob/main/ZTP.md

we need IDEVID access, public/private keys, certificate, serial number to start SZTP process ...

see IEEE 802.1AR - Secure Device Identity

also see https://github.com/usnistgov/iDevIDCerts

@shachartal @mestery @prasunkapoor @rsb-oss @jainvipin @alknopfler @achilikin @gupta-alok ?

let's start the discussion here, on slack and on our next meeting

@glimchb glimchb added the help wanted Extra attention is needed label Oct 5, 2022
@glimchb glimchb transferred this issue from opiproject/opi-prov-life Oct 6, 2022
@alknopfler
Copy link
Contributor

Doubt I'm having on my table:

@glimchb
Copy link
Member Author

glimchb commented Oct 10, 2022

@alknopfler

  1. Customer places an order to DPU vendor to buy DPUs
  2. without Security (classic ZTP) - Vendor will send only Serial Numbers of the devices back to the Customer
  3. with sZTP - Vendor creates certificates with serial numbers and sends them back to the Customer
  4. Vendor places iDEVID (priv key, pub key, certif,..) to the Device's TPM-like storage
  5. Customer loads this information to the Bootstrap server using NB APIs or configuration file
  6. Devices arrive to the site and powered up
  7. Device get URL of the Bootstrap server (via mDNS or SLAAC or DHCP)
  8. Device offers iDEVID to the Bootstrap server
  9. Bootstrap server verifies iDEVID of the device
  10. Bootstrap server optionally sends ownership voucher to the device
  11. Bootstrap server sends signed artifacts (OS image, config) to the device
  12. Device verifies signed artifacts and starts installation

@glimchb
Copy link
Member Author

glimchb commented Oct 11, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants