From: Tom Rini Date: Tue, 13 Oct 2020 10:06:54 -0400 Subject: [PATCH 1/2] fit: cipher: aes: allow to store the IV in the FIT image In-Reply-To: <1600347707-19080-1-git-send-email-philippe.reynes@softathome.com> References: <1600347707-19080-1-git-send-email-philippe.reynes@softathome.com> Message-ID: <20201013140654.GK14816@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thu, Sep 17, 2020 at 03:01:46PM +0200, Philippe Reynes wrote: > Binaries may be encrypted in a FIT image with AES. This > algo needs a key and an IV (Initialization Vector). The > IV is provided in a file (pointer by iv-name-hint in the > ITS file) when building the ITB file. > > This commits adds provide an alternative way to manage > the IV. If the property iv-name-hint is not provided in > the ITS file, the tool mkimage will generate an random > IV and store it in the FIT image. > > Signed-off-by: Philippe Reynes Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: