3 ms·
it's not focused on TLS certificates, but the Autonomic Network and Integrated Model and Approach (ANIMA) work group[1] has a sizable % of their Documents and D
by rektide 6y ago
it's not focused on TLS certificates, but the Autonomic Network and Integrated Model and Approach (ANIMA) work group[1] has a sizable % of their Documents and Drafts dedicated to shipping or setting up devices with pre-set certificates. Most of this related to their Bootstrapping Remote Secure Keys Infrastructure (BRSKI) work[2]. I'll let BRSKI descibe itself in it's own words, with the start of their abstract:
> This document specifies automated bootstrapping of an Autonomic Control Plane. To do this a Secure Key Infrastructure is bootstrapped. This is done using manufacturer-installed X.509 certificates, in combination with a manufacturer's authorizing service, both online and offline. We call this process the Bootstrapping Remote Secure Key Infrastructure (BRSKI) protocol. Bootstrapping a new device can occur using a routable address and a cloud service, or using only link-local connectivity, or on limited/ disconnected networks.
The BRSKI document does quite an robust imo job outlaying the environments & challenges & constraints folks like OpenWRT face in trying to set up devices.
BRSKI presents a specific approach, which no, does not immediately seem super useful/simple enough for openwrt. A devices (Pledge) contact a Manufacturer Authorized Signing Authority (MASA) Service. The MASA returns a Voucher that points it to a Join Registrar (& Coordinator), which the device uses for Enrollmemt to the domain & Imprinting of the Domain's material & exchange of Local Identity. The standard also includes ways for the MASA to collect Domain information (so you can register your registrar) and to provide optional Ownership Tracking of devices.
Openwrt could become a MASA, users could host Join Registrar's for their Domains, & nodes could securely go get the root trust key they ought to from that Join Registrar. Since the Domain generated that key, if the device were to present it's https interface with that key or one derived from it, HTTPS ought work.
[1] https://datatracker.ietf.org/group/anima/documents/ https://datatracker.ietf.org/group/anima/documents/
[2] https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/ https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapp...