Hi Bastian,
On Thu, Sep 24, 2020 at 01:05:31PM +0200, Bastian Krause wrote:
[doc quote deleted]
> After reading the quoted documentation snippets above (and assuming the
> error message triggers correctly now), do you still think this needs
> documentation improvement? If yes, you're very welcome to add an
> explanation to the signing doc section (maybe an info box?) to help
> others migrate their development key material into a code signing
> provider for the sake of backwards compatibility.
I needed to handle this situation (I guess many people find it familiar):
Board is using rauc for updates, keys was generated using previously
provided script and boards were supposed to stay near developers until
software stack is finalized. As always that was not the case and now
we need to update then. Templated provider does not add ca.cert.pem,
so generating rauc will end with error (Failed to create bundle:
failed signing bundle: signature verification failed: Verify error:
unable to get local issuer certificate).
This way you can at least prepare firmware using recent ptxdist
with properly generated keys. If there is any other option,
please let me know.
ladis
_______________________________________________
ptxdist mailing list
[email protected]
To unsubscribe, send a mail with subject "unsubscribe" to
[email protected]
