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

Add Onboarding/Key Distribution Section #27

Closed
mmccool opened this issue Nov 8, 2021 · 0 comments · Fixed by #28
Closed

Add Onboarding/Key Distribution Section #27

mmccool opened this issue Nov 8, 2021 · 0 comments · Fixed by #28

Comments

@mmccool
Copy link
Contributor

mmccool commented Nov 8, 2021

  • keys are needed for TLS
  • in a global network, existing CA-based mechanisms can and should be used
  • in local and offline networks, a separate key distribution mechanism is needed in order to use TLS. This is currently a gap, but we should define the requirements here (and mention the section in architecture, and also the recent IETF RFC survey paper on onboarding) (TODO: find actual references)
  • discovery may also be needed, explain how this relates to WoT Discovery (which currently focuses on authenticated discovery, but there may be some overlap)
  • the scripting API needs an isolated API (for use by the administrator) for managing secure information like keys. See Requirements for Managment APIs wot-scripting-api#298
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant