Re: [PATCH 2/3] binfmt_elf: Verify signature of signed elf binary

[Vivek Goyal <vgoyal@redhat.com>]

On Wed, Jan 16, 2013 at 10:33:11AM -0500, Mimi Zohar wrote:

[..]
> > - Also I really could not figure out where does the private signing key
> >   lives. I got the impression that we need to trust installer and
> >   signing somehow happens at installation time. And we wanted signing
> >   to happen at build server and could not trust installer for that.
> 
> Dmitry's ima-evm-utils package signs files.  Depending on the options,
> both the EVM and IMA extended attributes are created.

I was going through following presentation.

http://selinuxproject.org/~jmorris/lss2011_slides/IMA_EVM_Digital_Signature_Support.pdf

On slide 8, it mentons signing.

	evmctl sign --imahash /path/to/file
	evmctl sign --imasig /path/to/file

Can't figure out where does the key for signing come from? Is it already
loaded in any of kernel keyrings.

If yes, I think this is non-starter. One can not distribute the private
key.

Also I am assuming that this is done at installation time? If yes, then
again it does not work as installer does not have private key.

On slide 11, it talks about importing public keys in kernel keyring from
initramfs. As we discussed this will need modification as these keys
need to be signed and signing public key should already be part of 
kernel keyring.

So looking at the signing process, it really does not look like that
I can sign the executable at build server. It looks it needs to be
signed by installer at install time and private key needs to be available
to installer?
 
> 
> >   My understanding of IMA could be wrong. So it would help if you
> >   could list the exact steps about how to achieve the same goal using
> >   IMA.
> 
> http://linux-ima.sourceforge.net/  needs to be updated, but it describes
> the integrity subsystem and includes a link to Dave Safford's original
> whitepaper "An Overview of the Linux Integrity subsystem".

I have gone through the paper in the past and still the quetions remain
unanswered. So it will really help, if you could take a very simple
example of hello-world executable and list the steps needed to be
performed to sign and verify executable.

Thanks
Vivek