Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

at v3.16-rc2 89 lines 4.4 kB view raw
1 IMA Template Management Mechanism 2 3 4==== INTRODUCTION ==== 5 6The original 'ima' template is fixed length, containing the filedata hash 7and pathname. The filedata hash is limited to 20 bytes (md5/sha1). 8The pathname is a null terminated string, limited to 255 characters. 9To overcome these limitations and to add additional file metadata, it is 10necessary to extend the current version of IMA by defining additional 11templates. For example, information that could be possibly reported are 12the inode UID/GID or the LSM labels either of the inode and of the process 13that is accessing it. 14 15However, the main problem to introduce this feature is that, each time 16a new template is defined, the functions that generate and display 17the measurements list would include the code for handling a new format 18and, thus, would significantly grow over the time. 19 20The proposed solution solves this problem by separating the template 21management from the remaining IMA code. The core of this solution is the 22definition of two new data structures: a template descriptor, to determine 23which information should be included in the measurement list; a template 24field, to generate and display data of a given type. 25 26Managing templates with these structures is very simple. To support 27a new data type, developers define the field identifier and implement 28two functions, init() and show(), respectively to generate and display 29measurement entries. Defining a new template descriptor requires 30specifying the template format, a string of field identifiers separated 31by the '|' character. While in the current implementation it is possible 32to define new template descriptors only by adding their definition in the 33template specific code (ima_template.c), in a future version it will be 34possible to register a new template on a running kernel by supplying to IMA 35the desired format string. In this version, IMA initializes at boot time 36all defined template descriptors by translating the format into an array 37of template fields structures taken from the set of the supported ones. 38 39After the initialization step, IMA will call ima_alloc_init_template() 40(new function defined within the patches for the new template management 41mechanism) to generate a new measurement entry by using the template 42descriptor chosen through the kernel configuration or through the newly 43introduced 'ima_template=' kernel command line parameter. It is during this 44phase that the advantages of the new architecture are clearly shown: 45the latter function will not contain specific code to handle a given template 46but, instead, it simply calls the init() method of the template fields 47associated to the chosen template descriptor and store the result (pointer 48to allocated data and data length) in the measurement entry structure. 49 50The same mechanism is employed to display measurements entries. 51The functions ima[_ascii]_measurements_show() retrieve, for each entry, 52the template descriptor used to produce that entry and call the show() 53method for each item of the array of template fields structures. 54 55 56 57==== SUPPORTED TEMPLATE FIELDS AND DESCRIPTORS ==== 58 59In the following, there is the list of supported template fields 60('<identifier>': description), that can be used to define new template 61descriptors by adding their identifier to the format string 62(support for more data types will be added later): 63 64 - 'd': the digest of the event (i.e. the digest of a measured file), 65 calculated with the SHA1 or MD5 hash algorithm; 66 - 'n': the name of the event (i.e. the file name), with size up to 255 bytes; 67 - 'd-ng': the digest of the event, calculated with an arbitrary hash 68 algorithm (field format: [<hash algo>:]digest, where the digest 69 prefix is shown only if the hash algorithm is not SHA1 or MD5); 70 - 'n-ng': the name of the event, without size limitations; 71 - 'sig': the file signature. 72 73 74Below, there is the list of defined template descriptors: 75 - "ima": its format is 'd|n'; 76 - "ima-ng" (default): its format is 'd-ng|n-ng'; 77 - "ima-sig": its format is 'd-ng|n-ng|sig'. 78 79 80 81==== USE ==== 82 83To specify the template descriptor to be used to generate measurement entries, 84currently the following methods are supported: 85 86 - select a template descriptor among those supported in the kernel 87 configuration ('ima-ng' is the default choice); 88 - specify a template descriptor name from the kernel command line through 89 the 'ima_template=' parameter.