Bug 790008 - Integrity Measurement Architecture (IMA) disabled
Summary: Integrity Measurement Architecture (IMA) disabled
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 816135
TreeView+ depends on / blocked
 
Reported: 2012-02-13 13:33 UTC by Roberto Sassu
Modified: 2018-02-19 18:56 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-19 18:56:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Roberto Sassu 2012-02-13 13:33:14 UTC
Description of problem:

The Linux kernel was compiled without the support for IMA.


Version-Release number of selected component (if applicable):

3.2.5-3.fc16.x86_64


How reproducible:

See the kernel config in /boot.


Steps to Reproduce:
1. cat /boot/config-3.2.5-3.fc16.x86_64 |grep CONFIG_IMA
2.
3.
  
Actual results:

# CONFIG_IMA is not set


Expected results:

CONFIG_IMA=y
CONFIG_IMA_MEASURE_PCR_IDX=10
CONFIG_IMA_AUDIT=y
CONFIG_IMA_LSM_RULES=y


Additional info:

Comment 1 Josh Boyer 2012-02-13 15:04:10 UTC
(In reply to comment #0)
> Description of problem:
> 
> The Linux kernel was compiled without the support for IMA.

This forces the TPM modules to be built in, which seem to cause a number of problems on various machines with crappy TPM hardware.

Also, there really isn't a great usecase for IMA in a Fedora kernel.

Comment 2 Rajiv Andrade 2012-02-13 17:04:35 UTC
Hi Josh,

Can you confirm what are the open issues with some TPMs out there? We've upstreamed a number of fixes to 3.3 to address the ones we were aware of.

Commit 7f326ed specially assesses if a TPM is working correctly, and if not,
blocks it from being used and therefore to cause suspend/resume issues.

Thanks,
Rajiv

Comment 3 Josh Boyer 2012-02-13 18:21:27 UTC
(In reply to comment #2)
> Hi Josh,
> 
> Can you confirm what are the open issues with some TPMs out there? We've
> upstreamed a number of fixes to 3.3 to address the ones we were aware of.

They caused 2-15min boot times for some machines, which I believe got a fix.

For others, they prevent suspend/resume from working correctly.  Still others have issues with iTPM (which I believe might also have since been fixed).

> Commit 7f326ed specially assesses if a TPM is working correctly, and if not,
> blocks it from being used and therefore to cause suspend/resume issues.

Yep, that's helpful for 3.3 based kernels.  Your upstream work is very much appreciated.  However, F16 is on 3.2 at the moment.

Comment 4 Rajiv Andrade 2012-02-13 19:08:54 UTC
And you're probably picking the code from stable-3.2.y, so I assume having such patches there would be a valid course of action to have this one solved?

Thanks,
Rajiv

Comment 5 Josh Boyer 2012-02-13 19:16:57 UTC
(In reply to comment #4)
> And you're probably picking the code from stable-3.2.y, so I assume having such
> patches there would be a valid course of action to have this one solved?

For any TPM issues, sure.

Comment 6 Dave Jones 2012-03-22 16:48:26 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 7 Dave Jones 2012-03-22 16:52:51 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 8 Dave Jones 2012-03-22 17:03:30 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 9 Roberto Sassu 2012-03-22 17:25:33 UTC
(In reply to comment #8)
> [mass update]
> kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
> Please retest with this update.

IMA support is still disabled in kernel-3.3.0-4.fc16.

Regards

Roberto Sassu

Comment 10 Josh Boyer 2012-03-26 15:23:18 UTC
Thanks for reminding us.  We still aren't going to turn it back on at this time.

Comment 11 Patrick Uiterwijk 2017-08-20 20:44:46 UTC
Given that it's now been over 5 years, is there any chance enabling IMA could be reconsidered?

Comment 12 Josh Boyer 2017-08-21 11:53:43 UTC
(In reply to Patrick Uiterwijk from comment #11)
> Given that it's now been over 5 years, is there any chance enabling IMA
> could be reconsidered?

Likely not without a good requirements that need IMA.

Comment 13 Laura Abbott 2017-08-24 21:26:01 UTC
There is a growing interest in IMA so I think this is worth turning on, or at least discussing. The configuration dependency chain is quite long though so I'll send out a patch for review to see if anyone has objections.

Comment 14 Laura Abbott 2018-02-19 18:56:37 UTC
Patrick reminded me a few weeks ago that this never got turned on. I went ahead and turned it on in rawhide with a note that it should probably be turned off on
rebase (F28+ feature). If there are problems we can revert on rawhide.


Note You need to log in before you can comment on or make changes to this bug.