From: Mikhail Kurinnoi <viewizard@viewizard.com>
To: Dmitry Kasatkin <dmitry.kasatkin@huawei.com>
Cc: Matthew Garrett <mjg59@google.com>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"zohar@linux.vnet.ibm.com" <zohar@linux.vnet.ibm.com>
Subject: Re: [PATCH] EVM: Add support for portable signature format
Date: Thu, 19 Oct 2017 14:55:52 +0300 [thread overview]
Message-ID: <20171019145552.36f309e6@totoro> (raw)
In-Reply-To: <C2D7A727C393B644B70DF4B4DCFB60B921C43F0A@FRAEML521-MBX.china.huawei.com>
? Thu, 19 Oct 2017 11:02:51 +0000
Dmitry Kasatkin <dmitry.kasatkin@huawei.com> ?????:
> BTW.
>
> Just to refresh my mind. What would be the correct order for setting
> this signature from package? On any attr/xattr change, EVM will set
> HMAC.
from tar's code:
- uid/git/mode/data/etc...
- all xattrs
- caps
- selinux
- EVM xattr
EVM xattr should be restored the last one, when all xattrs/metadata
already restored, but... as soon, as first protected xattr will be
restored from package, EVM HMAC will be generated.
> What is the value of setting signature after that unless there is a
> policy to require signature (immutable)? In my original patchset
> portable was also immutable and also included policy support to
> require EVM signatures.
--
Best regards,
Mikhail Kurinnoi
next prev parent reply other threads:[~2017-10-19 11:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 18:01 [PATCH] EVM: Add support for portable signature format Matthew Garrett
2017-10-19 11:02 ` Dmitry Kasatkin
2017-10-19 11:55 ` Mikhail Kurinnoi [this message]
2017-10-19 12:00 ` Mimi Zohar
2017-10-19 15:11 ` Dmitry Kasatkin
2017-10-19 17:11 ` Matthew Garrett
2017-10-19 18:02 ` Dmitry Kasatkin
2017-10-19 18:13 ` Dmitry Kasatkin
2017-10-19 18:15 ` Matthew Garrett
2017-10-19 18:50 ` Dmitry Kasatkin
2017-10-19 12:52 ` Mimi Zohar
2017-10-19 17:09 ` Matthew Garrett
2017-10-19 17:44 ` Mimi Zohar
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=20171019145552.36f309e6@totoro \
--to=viewizard@viewizard.com \
--cc=dmitry.kasatkin@huawei.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.com \
--cc=zohar@linux.vnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.