You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Marko Kiiskila (JIRA)" <ji...@apache.org> on 2016/02/13 00:56:18 UTC

[jira] [Updated] (MYNEWT-26) Revise Image Management Scheme

     [ https://issues.apache.org/jira/browse/MYNEWT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marko Kiiskila updated MYNEWT-26:
---------------------------------
    Due Date: 16/Feb/16

> Revise Image Management Scheme
> ------------------------------
>
>                 Key: MYNEWT-26
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-26
>             Project: Mynewt
>          Issue Type: New Feature
>          Components: Image Mgmt
>            Reporter: Sterling Hughes
>            Assignee: Marko Kiiskila
>             Fix For: v0_8_0_beta2
>
>
> We need the following in our image management and bootloader scheme: 
> - Image header should have a SHA-256 in it that uniquely identifies the image
> - That SHA-256 must be signed by a device private key in order to boot.  By default newt shall use the Apache Mynewt Development public/private key.  This is in no way secure, but will keep the process uniform across devices, so when people add security, they don't have to change bootloader or image formats.
> - Bootloader should support verifying the SHA-256 and the signature of the image.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)