Skip to content
Snippets Groups Projects
  1. Oct 13, 2021
  2. Oct 12, 2021
  3. Oct 11, 2021
  4. Oct 08, 2021
  5. Oct 07, 2021
  6. Oct 06, 2021
  7. Oct 05, 2021
  8. Oct 04, 2021
  9. Oct 01, 2021
    • Zygmunt Krynicki's avatar
      rauc: use known insecure keys by default · fc53cea0
      Zygmunt Krynicki authored
      
      Unless overridden in another layer or in local.conf, rauc will bundle
      and use a know public key for verifying updates. This allows us to
      to have some set of defaults that work out of the box and allow testing
      the OTA stack and producing signed update bundles coming out of the CI
      system.
      
      The key is insecure and will expire in a year. This is intentional. Over
      time we may switch to a reference key that is managed and secured or
      re-generate another key for another year.
      
      The insecure key has a fixed name and that name is used to trigger a
      bitbake warning. OTA stack will learn to detect that key and similarly
      warn users, or perform equally appropriate operations, in order to
      reduce the risk of someone accidentally using this key in production.
      
      Signed-off-by: default avatarZygmunt Krynicki <zygmunt.krynicki@huawei.com>
      fc53cea0
  10. Sep 30, 2021
Loading