Re: [Fwd: Re: EVM: Permission denied with overlayfs]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2018-12-20 at 14:04 +0200, Amir Goldstein wrote:

> > > 2. What does the call stack look like when failing to verify the hash
> > > on oo.text?
> >
> > *** Cat of same file on merged dir fails (ino != 258)
> > cat: overlay/merged/abc.text: Permission denied
> >
> > [  476.770869] evm: ino: 38593 258 38593 abc.text
> > [  476.770876] evm: ino: 38593
> > [  476.770883] CPU: 3 PID: 3928 Comm: cat Not tainted 4.20.0-rc2+ #1287
> > [  476.770887] Hardware name: LENOVO 20BTS1NJ00/20BTS1NJ00, BIOS N14ET48W (1.26 ) 06/11/2018
> > [  476.770890] Call Trace:
> > [  476.770906]  dump_stack+0x46/0x5b
> > [  476.770913]  hmac_add_misc+0x171/0x180
> > [  476.770920]  evm_calc_hmac_or_hash+0x1c9/0x280
> > [  476.770927]  evm_verify_hmac+0x11f/0x2b0
> > [  476.770933]  ? evm_protected_xattr+0x6c/0x90
> > [  476.770940]  ima_appraise_measurement+0x83/0x510
> > [  476.770948]  process_measurement+0x646/0x6f0
> > [  476.770955]  ? selinux_file_open+0xa8/0xc0
> > [  476.770961]  ? do_dentry_open+0x25c/0x340
> > [  476.770966]  ? open_with_fake_path+0x48/0x70
> > [  476.770974]  ? ovl_open_realfile+0x56/0xe0
> > [  476.770981]  ima_file_check+0x4a/0x60
> 
> If you let this check return success even though appraisal failed,
> you will see that ovl_open_realfile() will end up calling ima_file_check()
> again with the "real" file and this check should not fail.
> Hence, my suggestion to mark the overlayfs sb with SB_NOIMA.

There's all sorts of caching of results involved in both EVM and IMA. 
Not so easy to modify.  Assuming that I properly removed the caching,
 I'm not seeing another call to ima_file_check.

Mimi




[Index of Archives]     [Linux Filesystems Devel]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux