On 14.01.22 00:28, Dhananjay Phadke wrote:
On 1/13/2022 4:38 AM, Jan Kiszka wrote:
On 25.11.21 20:03, Jan Kiszka wrote:
Another step to decouple the FIT image specification from the actual
signing: With these changes, the signature nodes can leave out an algo
property, mkimage will initialize
[resent as requested by Simon]
Another step to decouple the FIT image specification from the actual
signing: With these changes, the signature nodes can leave out an algo
property, mkimage will initialize that as well while signing. This way,
in-tree FIT source files can be prepared for gaining
On 1/13/2022 4:38 AM, Jan Kiszka wrote:
On 25.11.21 20:03, Jan Kiszka wrote:
Another step to decouple the FIT image specification from the actual
signing: With these changes, the signature nodes can leave out an algo
property, mkimage will initialize that as well while signing. This way,
Hi Jan,
On Thu, 13 Jan 2022 at 05:38, Jan Kiszka wrote:
>
> On 25.11.21 20:03, Jan Kiszka wrote:
> > Another step to decouple the FIT image specification from the actual
> > signing: With these changes, the signature nodes can leave out an algo
> > property, mkimage will initialize that as well
On 25.11.21 20:03, Jan Kiszka wrote:
Another step to decouple the FIT image specification from the actual
signing: With these changes, the signature nodes can leave out an algo
property, mkimage will initialize that as well while signing. This way,
in-tree FIT source files can be prepared for
Another step to decouple the FIT image specification from the actual
signing: With these changes, the signature nodes can leave out an algo
property, mkimage will initialize that as well while signing. This way,
in-tree FIT source files can be prepared for gaining signatures without
defining the
6 matches
Mail list logo