Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
R repo_manifest
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cobalt
  • repo_manifest
  • Wiki
  • secure provisioning

secure provisioning · Changes

Page history
mstevens created page: secure provisioning authored Nov 18, 2017 by Mark Stevens's avatar Mark Stevens
Hide whitespace changes
Inline Side-by-side
Showing with 36 additions and 0 deletions
+36 -0
  • secure-provisioning.md secure-provisioning.md +36 -0
  • No files found.
secure-provisioning.md 0 → 100644
View page @ ce65735c
Secure Provisioning is the first contact from qbert to figure out how the unit should be provisioned.
Device uses mDNS to discover one or more services that publish product-provisioner endpoints. The same device exposes an http server responding to the /bzt232hub02-provisioner endpoint.
Display list of services on device. or select if only one comes up.
> GET /bzt232hub02-provisioner?deviceId=10101010
Response:
```json
{
"product": "bzt232hub02",
"software": "rsync://ntn-mstevens-01.ntn.com:59144/site/BTUpdates",
"content": "rsync://ntn-mstevens-01.ntn.com:59144/site/BTContent",
"software-cache": "rsync://ntn-mstevens-01.ntn.com:59144/tablet/software",
"content-cache": "rsync://ntn-mstevens-01.ntn.com:59144/tablet/content",
"certificates": "rsync://ntn-mstevens-01.ntn.com:59144/site/CACerts",
"user": "git",
"password": "git",
"secrets": [
{"key": "jwt", "secret": "secret_value" },
{"key": "platform", "secret": "{....}" },
]
}
```
Upon receiving the above data:
Data | Disposition
--- | ---
certificates | certificates here are installed into the User CA Certs and registered by sha256
secrets | secrets are stored securely in the LockboxProvider until they can be transferred into BTSettings
software | all files in the folder are copied, to be installed according to the software manifest
content | all files are copied. When the content manifest is retrieved, the content is integrated into the MediaContentProvider
software-cache | files are copied into http software folder and organized for tablet software downloads
content-cache | files are copied into http content folder and organized for tablet content downloads
\ No newline at end of file
Clone repository
  • build stories
  • dev stories
  • fitness testing
  • handshake
  • Home
  • logging
  • provisioning
  • rockchip parameter file format v1.3 (en)
  • secure boot application note
  • secure provisioning
  • sitehub hardening
  • tee readme
  • tee