I made a significant change to UpdateManager and ArchiveManager where they don't store the public verification keys when they are started, but are instead passed them by the socket when an archive or update is ready to be downloaded.
This is because if the keys were updated, but then the process died, they would not have the most up to date keys.
This simplifies the setup of public keys for archive verification purposes.
If there are no public keys setup for archive verification defined...
fwup_public_keys
, if they existNervesHub
to send over the latest public keysAlso support the ability in the config to request the latest public keys from
NervesHub
even iffwup_public_keys
are defined in the config.Related: https://github.com/nerves-hub/nerves_hub_web/pull/1291
Please Note:
I made a significant change to
UpdateManager
andArchiveManager
where they don't store the public verification keys when they are started, but are instead passed them by the socket when an archive or update is ready to be downloaded.This is because if the keys were updated, but then the process died, they would not have the most up to date keys.