Hi Mohan,
On 23.10.23 18:55, 'Mohan Mistry' via swupdate wrote:
> Hello,
> In order to get “encrypted” files/images feature to work, I had to fix
> a couple of things
>
You should explain here what is not working, as this was not raised as
issue before.
> * Setting up of SWUPDATE_IMAGES_ENCRYPTED dictionary based on if
> “encrypted = true” is present for a file.
Current support in meta-swupdate does not set
SWUPDATE_IMAGES_ENCRYPTED[artifact] from sw-description, and it is duty
of the integrator to maintain consistency.
> * Use the same AES key-file format as used by swupdate client on target
>
> Attached is how I fixed it in my own layer.
>
No, it does not work. Please read how to contribute.
You shouldsend a *patch* to this mailing list that can be reviewed, with
your Signed-off-by to track you worked for the project, and with an
exhaustive commit message. Patch should be sent via "git send-email" to
avoid corruption by m,ail clients. Such as patch, if correct, will
automatically stored by patchworks, whre I get patched to be applied.
Patches / Files that do not follow these simple rules won't be taken
into consideration.
Best regards,
Stefano Babic
> Feedback appreciated and should this be upstreamed
>
> Mohan Mistry
>
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
swupdate+u...@googlegroups.com
> <mailto:
swupdate+u...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/swupdate/SA1PR17MB5106EEEDDC28D612156DFC6791D8A%40SA1PR17MB5106.namprd17.prod.outlook.com <
https://groups.google.com/d/msgid/swupdate/SA1PR17MB5106EEEDDC28D612156DFC6791D8A%40SA1PR17MB5106.namprd17.prod.outlook.com?utm_medium=email&utm_source=footer>.