linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rishi gupta <gupt21@gmail.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org
Subject: Re: OTA does not work with IMA due to xattr not supported by zip
Date: Thu, 10 Jan 2019 12:16:46 +0530	[thread overview]
Message-ID: <CALUj-gvmo8pTGeHB=L+sZaP9a1QPTE2AXNc=vzzfZ+4GtVac3A@mail.gmail.com> (raw)
In-Reply-To: <1546981121.19931.130.camel@linux.ibm.com>

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.


On Wed, Jan 9, 2019 at 2:28 AM Mimi Zohar <zohar@linux.ibm.com> wrote:
>
> On Tue, 2019-01-08 at 06:56 +0530, rishi gupta wrote:
> > Hi Team,
> >
> > Android and android recovery based implementation for Linux, generates
> > ota package which is a zipped archive.
> >
> > I observed that xattr gets dropped when creating zip archive and
> > therefore after OTA system will not boot if IMA_APPRAISE_SIGNED_INIT
> > is used.
> >
> > This essentially means that IMA may not be used in commercial products
> > requiring OTA or I missed something or there is a workaround to such
> > problem.
> >
> > https://source.android.com/devices/tech/ota/tools
>
> Ok.  Some applications support xattrs (eg. RPM, tar); others don't
> (eg. Debian packages, CPIO/initramfs).  We worked with the RPM
> community to add xattr support.  Multiple attempts have been made to
> add xattr support to Debian packages.
>
> Mimi
>

  reply	other threads:[~2019-01-10  6:47 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 [this message]
2019-01-10 16:18     ` Mimi Zohar
2019-01-10 18:20     ` Matthew Garrett
2019-01-13 10:58       ` rishi gupta

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-gvmo8pTGeHB=L+sZaP9a1QPTE2AXNc=vzzfZ+4GtVac3A@mail.gmail.com' \
    --to=gupt21@gmail.com \
    --cc=linux-integrity@vger.kernel.org \
    --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).