Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][RFC] sstate: implement basic signing/validation
Date: Tue, 25 Aug 2015 21:52:05 +0100	[thread overview]
Message-ID: <1440535925.12105.445.camel@linuxfoundation.org> (raw)
In-Reply-To: <1440521261-5444-1-git-send-email-ross.burton@intel.com>

On Tue, 2015-08-25 at 17:47 +0100, Ross Burton wrote:
> To provide some element of integrity to sstate archives, allow sstate archives
> to be GPG signed with a specified key (detached signature to a sidecar .sig
> file), and verify the signatures when sstate archives are unpacked.

Some random thoughts. We could add the signature into the tarball using
something like the --use-compress-program option  (see
https://www.gnu.org/software/tar/manual/html_chapter/tar_8.html and the
gpg references). That would mean we have one less separate file to worry
about.

Not sure which approach I prefer, just putting the idea out there...

> TODO: fetch .sig from remote sstate mirrors

We do something similar for siginfo already FWIW.

> Signed-off-by: Ross Burton <ross.burton@intel.com>

I'd also probably make these callable functions, then others can
override them and use them as hooks if they want to.

Cheers,

Richard




  reply	other threads:[~2015-08-25 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 16:47 [PATCH][RFC] sstate: implement basic signing/validation Ross Burton
2015-08-25 20:52 ` Richard Purdie [this message]
2015-08-25 20:55   ` Burton, Ross

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=1440535925.12105.445.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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