IMA-templates.txt 4.3 KB

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