Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fs/iso9660: md5 checksum boot dir files
Date: Fri, 11 Nov 2016 22:00:46 +0100	[thread overview]
Message-ID: <20161111220046.72d2547e@free-electrons.com> (raw)
In-Reply-To: <CANQCQpaZZ708bi1N3m2EqoT8+apV7wgLqE6CXNJ8q5Go3OGbLQ@mail.gmail.com>

Hello,

On Fri, 11 Nov 2016 14:54:06 -0600, Matthew Weber wrote:

> We thought for a iso9600 formatted iso, this was a way to add a quick
> integrity check capability to the images used for kernel/rootfs. Since the
> bzimage and initrd are both present in this boot folder.  This allows a
> product's install process to check the integrity of a disk after flashing
> the iso to a bare drive (mount the new boot partition and run md5sum -c).
> It also opens up the option for runtime verifying the images you booted
> from if you add scripting in your rootfs.

This all seems interesting, but if we want to solve this problem, we
want to solve it globally for all filesystems, and the entire contents
of the filesystem, not just the specific /boot directory of the
specific iso9660 filesystem.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2016-11-11 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 17:13 [Buildroot] [PATCH] fs/iso9660: md5 checksum boot dir files Matt Weber
2016-11-11 20:24 ` Thomas Petazzoni
2016-11-11 20:54   ` Matthew Weber
2016-11-11 21:00     ` Thomas Petazzoni [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=20161111220046.72d2547e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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