Difference between revisions of "Secure OTA Update"

From eLinux.org
Jump to: navigation, search
(Reference implementations: fix some syntax issues)
m
Line 44: Line 44:
 
* [https://goo.gl/1EGWkr 2017 ELC-E Europe BoF: How to collaborate on secure update for Linux]
 
* [https://goo.gl/1EGWkr 2017 ELC-E Europe BoF: How to collaborate on secure update for Linux]
  
= Press releases =  
+
= Relevant information =  
 
* [https://www.cncf.io/announcement/2017/10/24/cncf-host-two-security-projects-notary-tuf-specification/ Cloud Native Compute Foundation announces Notary and TUF specification adoption]
 
* [https://www.cncf.io/announcement/2017/10/24/cncf-host-two-security-projects-notary-tuf-specification/ Cloud Native Compute Foundation announces Notary and TUF specification adoption]
 
* [http://markets.businessinsider.com/news/stocks/Cybersecurity-Protocol-that-Fends-off-Automobile-Hacks-Named-to-Popular-Science-Magazine-s-List-of-Top-100-Technologies-of-the-Year-1004763332 Uptane: One of Popular Science's top 100 technologies of the year]
 
* [http://markets.businessinsider.com/news/stocks/Cybersecurity-Protocol-that-Fends-off-Automobile-Hacks-Named-to-Popular-Science-Magazine-s-List-of-Top-100-Technologies-of-the-Year-1004763332 Uptane: One of Popular Science's top 100 technologies of the year]
 
+
* [https://ostree.readthedocs.io/en/latest/manual/related-projects ostree's documentation of related projects]
 
= Reference implementations =  
 
= Reference implementations =  
 
* AGL has a meta-sota layer that is an implementation - [https://wiki.automotivelinux.org/subsystem/agl-sota/ostree agl-sota]
 
* AGL has a meta-sota layer that is an implementation - [https://wiki.automotivelinux.org/subsystem/agl-sota/ostree agl-sota]
  
 
= Actions =
 
= Actions =
Actions:
 
 
* Setup mailing list?
 
* Setup mailing list?
* initial interest
+
** Please add your email if you are interested at being involved with the collaboration efforts.
* Please add your email if you are interested at being involved at the collaboration efforts.
+
*** alan (at) opensourcefoundries.com
** alan (at) opensourcefoundries.com
+
*** peter (at) korsgaard.com
** peter (at) korsgaard.com
+
*** ricardo (at) opensourcefoundries.com
** ricardo (at) opensourcefoundries.com
+
*** anton (at) advancedtelematic.com
** anton (at) advancedtelematic.com
 

Revision as of 23:26, 24 October 2017

Overview

A valid software update system on Linux should provide the following elements

  • Atomic updates
    • Stateless system
  • Capable of updating all software
    • bootloader
    • kernel
    • user data / configuration
    • rootfs / root file system
  • fail-safe, rollback to a previous software state
    • boot/update monitoring (watchdog) with boot confirmation
  • Secure download and verification of the image
  • Easy to use without vendor lock-in
  • Trusted
    • Compliant with and leverages HW elements (TPM/TEE)

Storage and delivery methods

  • Layered Tarball-based (i.e. docker)
  • File-based (i.e.libostree)
  • Chunk-based (i.e. casync)
  • Block-based (i.e. others)

Todo

  • Develop guidelines / reference implementations for key stories
    • Secure boot
    • Trusted execution environment (bootloader update, integrity checks)
    • Bootloader-driven rootfs image update process (image swap, boot count)
    • Boot firmware update process
    • Integration with different Open Source management servers
    • Secure software distribution (TUF) implementation
    • Watchdog best practices / boot image validation
  • Investigate cross-compatibility extensions in existing solutions
    • i.e. Mender support in SWUpdate?
    • casync (chunk-based image support in AGL

Relevant conference presentations

Relevant information

Reference implementations

  • AGL has a meta-sota layer that is an implementation - agl-sota

Actions

  • Setup mailing list?
    • Please add your email if you are interested at being involved with the collaboration efforts.
      • alan (at) opensourcefoundries.com
      • peter (at) korsgaard.com
      • ricardo (at) opensourcefoundries.com
      • anton (at) advancedtelematic.com