From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-qk0-x22f.google.com ([2607:f8b0:400d:c09::22f]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1aGP2s-0005zj-JO for barebox@lists.infradead.org; Tue, 05 Jan 2016 10:40:55 +0000 Received: by mail-qk0-x22f.google.com with SMTP id n135so139043340qka.2 for ; Tue, 05 Jan 2016 02:40:34 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <568B9BCD.9070509@pengutronix.de> References: <1451981463-23604-1-git-send-email-mkl@pengutronix.de> <1451981463-23604-4-git-send-email-mkl@pengutronix.de> <568B9BCD.9070509@pengutronix.de> From: Yegor Yefremov Date: Tue, 5 Jan 2016 11:40:13 +0100 Message-ID: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH 3/3] bootm: add initial FIT support To: Marc Kleine-Budde Cc: barebox , kernel@pengutronix.de On Tue, Jan 5, 2016 at 11:32 AM, Marc Kleine-Budde wrote: > On 01/05/2016 11:28 AM, Yegor Yefremov wrote: >> Hi Marc, >> >> thanks for reposting the patches. >> >> On Tue, Jan 5, 2016 at 9:11 AM, Marc Kleine-Budde wrote: >>> From: Jan Luebbe >>> >>> This implementation is inspired by U-Boot's FIT support. Instead of >>> using libfdt (which does not exist in barebox), configuration signatures >>> are verified by using a simplified DT parser based on barebox's own >>> code. >>> >>> Currently, only signed configurations with hashed images are supported, >>> as the other variants are less useful for verified boot. Compatible FIT >>> images can be created using U-Boot's mkimage tool. >> >> What about unsigned images? > > That's not our use case. We use plain zImages instead. The solution would be to introduce an option like in U-Boot? CONFIG_FIT_SIGNATURE: This option enables signature verification of FIT uImages, using a hash signed and verified using RSA. If CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive hashing is available using hardware, RSA library will use it. See doc/uImage.FIT/signature.txt for more details. >> I also get: unsupported algo crc32 >> Is it intended to be supported? > > Not for our usecase - feel free to add crc32 support. OK. But what about FIT configuration selection syntax? Yegor _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox