From: Rouven Czerwinski <r.czerwinski@pengutronix.de>
To: Maik Otto <m.otto@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/4] Makefile-imx: replace static variant to dynamic for signing images
Date: Tue, 28 May 2019 08:36:43 +0200 [thread overview]
Message-ID: <6e4fd1a87381c4a95a2597729e7f1e0858f63c0b.camel@pengutronix.de> (raw)
In-Reply-To: <3d3cf5bb-b119-ee89-a5ed-7a210f7f285b@phytec.de>
On Mon, 2019-05-27 at 15:08 +0200, Maik Otto wrote:
> Hi Mr. Czerwinski,
>
> i will change the patches and make checkboxes for the different
> images.
> my idea is to use different file extensions for the images
> for example
> .img for normal
> .simg for signed
> .esimg for encrypted signed
> .usimg for usb signed
>
> the other idea is to use different filenames for the images.
> for example
> -s.img
> -es.img
> -us.img
>
> my favorite is to use different file extensions for the images, but
> im
> not shure is this ok or can this have other negative effects.
> so the standard extension is .img
> What do you think about the file name or file extension?
Hm, I'm split on this. Normal images and signed images can be used in
the same way, however booting a signed image using imx-usb-loader is
only possible with the usb-signed image. Therefore the different file
extensions are sensible.
On the other hand all images contain the same data, keeping that in
mind it does not make sense to provide different file extensions.
I like a verbose filename version best, i.e:
-signed.img
-encrypted-signed.img
-signed-usb.img
Best Regards,
Rouven Czerwinski
--
Pengutronix e.K. | |
Industrial Linux Solutions | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-05-28 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 11:32 Maik Otto
2019-05-24 11:32 ` [PATCH 2/4] imx6, imx7, imx8: changing hardcoded suffix to variable Maik Otto
2019-05-24 11:32 ` [PATCH 3/4] i.mx6: signed boot: add habv4-imx6-gencsf.h to the flash header of the PHYTEC boards Maik Otto
2019-06-04 15:11 ` Bastian Krause
2019-05-24 11:32 ` [PATCH 4/4] imx6: added fit image signature to the devicetree for " Maik Otto
2019-05-24 12:55 ` [PATCH 1/4] Makefile-imx: replace static variant to dynamic for signing images Rouven Czerwinski
2019-05-27 13:08 ` Maik Otto
2019-05-28 6:36 ` Rouven Czerwinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6e4fd1a87381c4a95a2597729e7f1e0858f63c0b.camel@pengutronix.de \
--to=r.czerwinski@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.otto@phytec.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox