linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rishi gupta <gupt21@gmail.com>
To: Matthew Garrett <mjg59@google.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
	linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: OTA does not work with IMA due to xattr not supported by zip
Date: Sun, 13 Jan 2019 16:28:01 +0530	[thread overview]
Message-ID: <CALUj-gvn5MDLcY-pwh=PBSZwSK41Jv6C6Ay5qx5bRTj5btfNMw@mail.gmail.com> (raw)
In-Reply-To: <CACdnJusByW8ybecgaMRHooi_vhJkuUzmf3MeEsQmNP38TiZkdA@mail.gmail.com>

Thanks Mimi, I am asking if integrity team is working with zip
community like the RPM. I will have a look at zip code to see if it is
in my capacity to add xattr support or not. A possible solution looks
like replacing zip with tar in OTA solution.

Thanks Matthew, I am at lower version of kernel therefore portable evm
may not be taken in as of now. I will backport it possibly.


On Thu, Jan 10, 2019 at 11:50 PM Matthew Garrett <mjg59@google.com> wrote:
>
> On Wed, Jan 9, 2019 at 10:47 PM rishi gupta <gupt21@gmail.com> wrote:
> >
> > Thanks Mimi. Any plan for zip archive format support.
> > Also when using EVM, the files has to be signed on target. So after
> > new files has been flashed on device during OTA, does private key also
> > needs to be present on system.
>
> This is what the portable EVM format is for - it allows EVM signatures
> to be generated remotely and shipped as part of a package.

      reply	other threads:[~2019-01-13 10:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08  1:26 OTA does not work with IMA due to xattr not supported by zip rishi gupta
2019-01-08 20:58 ` Mimi Zohar
2019-01-10  6:46   ` rishi gupta
2019-01-10 16:18     ` Mimi Zohar
2019-01-10 18:20     ` Matthew Garrett
2019-01-13 10:58       ` rishi gupta [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='CALUj-gvn5MDLcY-pwh=PBSZwSK41Jv6C6Ay5qx5bRTj5btfNMw@mail.gmail.com' \
    --to=gupt21@gmail.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=mjg59@google.com \
    --cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).