1 What: /sys/kernel/security/evm !! 1 What: security/evm
2 What: /sys/kernel/security/*/evm <<
3 Date: March 2011 2 Date: March 2011
4 Contact: Mimi Zohar <zohar@us.ibm.com> 3 Contact: Mimi Zohar <zohar@us.ibm.com>
5 Description: 4 Description:
6 EVM protects a file's security 5 EVM protects a file's security extended attributes(xattrs)
7 against integrity attacks. The 6 against integrity attacks. The initial method maintains an
8 HMAC-sha1 value across the ext 7 HMAC-sha1 value across the extended attributes, storing the
9 value as the extended attribut 8 value as the extended attribute 'security.evm'.
10 9
11 EVM supports two classes of se 10 EVM supports two classes of security.evm. The first is
12 an HMAC-sha1 generated locally 11 an HMAC-sha1 generated locally with a
13 trusted/encrypted key stored i 12 trusted/encrypted key stored in the Kernel Key
14 Retention System. The second i 13 Retention System. The second is a digital signature
15 generated either locally or re 14 generated either locally or remotely using an
16 asymmetric key. These keys are 15 asymmetric key. These keys are loaded onto root's
17 keyring using keyctl, and EVM 16 keyring using keyctl, and EVM is then enabled by
18 echoing a value to <securityfs 17 echoing a value to <securityfs>/evm made up of the
19 following bits: 18 following bits:
20 19
21 === ==================== <<
22 Bit Effect 20 Bit Effect
23 === ==================== <<
24 0 Enable HMAC validati 21 0 Enable HMAC validation and creation
25 1 Enable digital signa 22 1 Enable digital signature validation
26 2 Permit modification 23 2 Permit modification of EVM-protected metadata at
27 runtime. Not support 24 runtime. Not supported if HMAC validation and
28 creation is enabled !! 25 creation is enabled.
29 31 Disable further runt 26 31 Disable further runtime modification of EVM policy
30 === ==================== <<
31 27
32 For example:: !! 28 For example:
33 29
34 echo 1 ><securityfs>/evm !! 30 echo 1 ><securityfs>/evm
35 31
36 will enable HMAC validation an 32 will enable HMAC validation and creation
37 33
38 :: !! 34 echo 0x80000003 ><securityfs>/evm
39 <<
40 echo 0x80000003 ><securityfs <<
41 35
42 will enable HMAC and digital s 36 will enable HMAC and digital signature validation and
43 HMAC creation and disable all 37 HMAC creation and disable all further modification of policy.
44 38
45 :: !! 39 echo 0x80000006 ><securityfs>/evm
46 <<
47 echo 0x80000006 ><securityfs <<
48 40
49 will enable digital signature 41 will enable digital signature validation, permit
50 modification of EVM-protected 42 modification of EVM-protected metadata and
51 disable all further modificati !! 43 disable all further modification of policy
52 deprecated in favor of:: <<
53 <<
54 echo 0x80000002 ><securityfs <<
55 <<
56 as the outstanding issues that <<
57 signatures have been solved. <<
58 <<
59 Echoing a value is additive, t <<
60 existing initialization flags. <<
61 <<
62 For example, after:: <<
63 <<
64 echo 2 ><securityfs>/evm <<
65 <<
66 another echo can be performed: <<
67 <<
68 echo 1 ><securityfs>/evm <<
69 <<
70 and the resulting value will b <<
71 <<
72 Note that once an HMAC key has <<
73 be possible to enable metadata <<
74 HMAC key has been loaded will <<
75 For example, if the current va <<
76 <<
77 echo 1 ><securityfs>/evm <<
78 <<
79 will set the new value to 3 (4 <<
80 44
81 Loading an HMAC key is the onl !! 45 Note that once a key has been loaded, it will no longer be
82 modification. !! 46 possible to enable metadata modification.
83 47
84 Until key loading has been sig 48 Until key loading has been signaled EVM can not create
85 or validate the 'security.evm' 49 or validate the 'security.evm' xattr, but returns
86 INTEGRITY_UNKNOWN. Loading ke 50 INTEGRITY_UNKNOWN. Loading keys and signaling EVM
87 should be done as early as pos 51 should be done as early as possible. Normally this is
88 done in the initramfs, which h 52 done in the initramfs, which has already been measured
89 as part of the trusted boot. 53 as part of the trusted boot. For more information on
90 creating and loading existing 54 creating and loading existing trusted/encrypted keys,
91 refer to: 55 refer to:
92 Documentation/security/keys/tr 56 Documentation/security/keys/trusted-encrypted.rst. Both
93 dracut (via 97masterkey and 98 57 dracut (via 97masterkey and 98integrity) and systemd (via
94 core/ima-setup) have support f 58 core/ima-setup) have support for loading keys at boot
95 time. 59 time.
96 60
97 What: /sys/kernel/security/*/evm/evm !! 61 What: security/integrity/evm/evm_xattrs
98 Date: April 2018 62 Date: April 2018
99 Contact: Matthew Garrett <mjg59@google.c 63 Contact: Matthew Garrett <mjg59@google.com>
100 Description: 64 Description:
101 Shows the set of extended attr 65 Shows the set of extended attributes used to calculate or
102 validate the EVM signature, an 66 validate the EVM signature, and allows additional attributes
103 to be added at runtime. Any si 67 to be added at runtime. Any signatures generated after
104 additional attributes are adde !! 68 additional attributes are added (and on files posessing those
105 additional attributes) will on 69 additional attributes) will only be valid if the same
106 additional attributes are conf 70 additional attributes are configured on system boot. Writing
107 a single period (.) will lock 71 a single period (.) will lock the xattr list from any further
108 modification. 72 modification.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.