integrity
Subsystems (10)
cover integrity
Reposting the integrity patchset based on James's security-testing-2.6/#next tree as per his request.
Mimi Zohar (3):
integrity: TPM internel kernel interface
integrity: Linux Integrity Module(LIM)
integrity: IMA as an integrity service provider
PATCH 1/3 integrity: TPM internel kernel interface
The internal TPM kernel interface did not protect itself from the removal of the TPM driver, while being used. We continue to protect the tpm_chip_list using the driver_lock as before, and are using an rcu lock to protect readers. The internal TPM kernel interface now protects itself from the driver being removed by incrementing the module reference count.
Resubmitting integrity-tpm-internal-kernel-interface.patch, which was previously Signed-off-by Kylene Hall.
Updated per feedback:
Adds the following support:
- make internal kernel interface to transmit TPM commands global
- adds reading a pcr value
- adds extending a pcr value
- adds lookup the tpm_chip for given chip number and type
---
drivers/char/tpm/tpm.c +137 -3
@@ -1,11 +1,12 @@/* -* Copyright (C) 2004 IBM Corporation +* Copyright (C) 2004,2007,2008 IBM Corporation * * Authors: * Leendert van Doorn <[email protected]> * Dave Safford <[email protected]> * Reiner Sailer <[email protected]> * Kylene Hall <[email protected]> +* Debora Velarde <[email protected]> * * Maintained by: <[email protected]> *
@@ -28,6 +29,14 @@#include <linux/spinlock.h> #include <linux/smp_lock.h> +#include <linux/mm.h> +#include <linux/slab.h> +#include <linux/string.h> +#include <linux/crypto.h> +#include <linux/fs.h> +#include <linux/scatterlist.h> +#include <linux/rcupdate.h> +#include <asm/unaligned.h> #include "tpm.h" enum tpm_const {
@@ -50,6 +59,8 @@ enum tpm_duration {static LIST_HEAD (tpm_chip_list);static DEFINE_SPINLOCK (driver_lock); static DECLARE_BITMAP(dev_mask, TPM_NUM_DEVICES); +#define TPM_CHIP_NUM_MASK 0x0000ffff +#define TPM_CHIP_TYPE_SHIFT 16/* * Array with one entry per ordinal defining the maximum amount
@@ -366,8 +377,7 @@ EXPORT_SYMBOL_GPL(tpm_calc_ordinal_duration);/* * Internal kernel interface to transmit TPM commands */ -static ssize_t tpm_transmit (struct tpm_chip *chip,const char *buf, -size_t bufsiz) +ssize_t tpm_transmit (struct tpm_chip *chip,char *buf,size_t bufsiz) {ssize_t rc;u32 count, ordinal;
@@ -425,6 +435,7 @@ out:mutex_unlock (&chip->tpm_mutex);return rc; } +EXPORT_SYMBOL_GPL (tpm_transmit);#define TPM_DIGEST_SIZE 20#define TPM_ERROR_SIZE 10
@@ -710,6 +721,7 @@ ssize_t tpm_show_temp_deactivated(struct device * dev, }EXPORT_SYMBOL_GPL (tpm_show_temp_deactivated); +#define READ_PCR_RESULT_SIZE 30static const u8 pcrread[] = {0 ,193 ,/* TPM_TAG_RQU_COMMAND */ 0 ,0 ,0 ,14 ,/* length */
@@ -765,6 +777,128 @@ out: }EXPORT_SYMBOL_GPL (tpm_show_pcrs); +/* +* tpm_chip_lookup - return tpm_chip for given chip number and type +* +* Must be called with rcu_read_lock. +*/ +static struct tpm_chip *tpm_chip_lookup (int chip_num,int chip_typ) +{ +struct tpm_chip *pos; +int rc; + +list_for_each_entry_rcu (pos, &tpm_chip_list, list) { + rc = (chip_num ==TPM_ANY_NUM || pos->dev_num == chip_num) + && (chip_typ ==TPM_ANY_TYPE ); +if (rc) +return pos; + } +return NULL ; +} + +/** +* tpm_pcr_read - read a pcr value +* @chip_id: tpm chip identifier +* Upper 2 bytes: ANY, HW_ONLY or SW_ONLY +* Lower 2 bytes: tpm idx # or AN& +* @pcr_idx: pcr idx to retrieve +* @res_buf: TPM_PCR value +* size of res_buf is 20 bytes (or NULL if you don't care) +* +* The TPM driver should be built-in, but for whatever reason it +* isn't, protect against the chip disappearing, by incrementing +* the module usage count. +*/ +int tpm_pcr_read (u32 chip_id,int pcr_idx,u8 *res_buf) +{ +u8 data[READ_PCR_RESULT_SIZE ]; +int rc; +__be32 index; +int chip_num = chip_id &TPM_CHIP_NUM_MASK ; +struct tpm_chip *chip; + +rcu_read_lock (); + chip =tpm_chip_lookup (chip_num, chip_id >>TPM_CHIP_TYPE_SHIFT ); +if (chip ==NULL ) { +rcu_read_unlock (); +return -ENODEV ; + } +if (!try_module_get (chip->dev->driver->owner)) { +rcu_read_unlock (); +return -ENODEV ; + } +rcu_read_unlock (); + +BUILD_BUG_ON (sizeof (pcrread) >READ_PCR_RESULT_SIZE ); +memcpy (data, pcrread,sizeof (pcrread)); + index =cpu_to_be32 (pcr_idx); +memcpy (data +10 , &index,4 ); + rc =tpm_transmit (chip, data,sizeof (data)); +if (rc >0 ) + rc =get_unaligned_be32 ((__be32 *) (data +6 )); + +if (rc ==0 && res_buf) +memcpy (res_buf, data +10 ,TPM_DIGEST_SIZE ); + +module_put (chip->dev->driver->owner); +return rc; +} +EXPORT_SYMBOL_GPL (tpm_pcr_read); + +#define EXTEND_PCR_SIZE 34 +static const u8 pcrextend[] = { +0 ,193 ,/* TPM_TAG_RQU_COMMAND */ +0 ,0 ,0 ,34 ,/* length */ +0 ,0 ,0 ,20 ,/* TPM_ORD_Extend */ +0 ,0 ,0 ,0 /* PCR index */ +}; + +/** +* tpm_pcr_extend - extend pcr value with hash +* @chip_id: tpm chip identifier +* Upper 2 bytes: ANY, HW_ONLY or SW_ONLY +* Lower 2 bytes: tpm idx # or AN& +* @pcr_idx: pcr idx to extend +* @hash: hash value used to extend pcr value +* +* The TPM driver should be built-in, but for whatever reason it +* isn't, protect against the chip disappearing, by incrementing +* the module usage count. +*/ +int tpm_pcr_extend (u32 chip_id,int pcr_idx,const u8 *hash) +{ +u8 data[EXTEND_PCR_SIZE ]; +int rc; +__be32 index; +int chip_num = chip_id &TPM_CHIP_NUM_MASK ; +struct tpm_chip *chip; + +rcu_read_lock (); + chip =tpm_chip_lookup (chip_num, chip_id >>TPM_CHIP_TYPE_SHIFT ); +if (chip ==NULL ) { +rcu_read_unlock (); +return -ENODEV ; + } +if (!try_module_get (chip->dev->driver->owner)) { +rcu_read_unlock (); +return -ENODEV ; + } +rcu_read_unlock (); + +BUILD_BUG_ON (sizeof (pcrextend) >EXTEND_PCR_SIZE ); +memcpy (data, pcrextend,sizeof (pcrextend)); + index =cpu_to_be32 (pcr_idx); +memcpy (data +10 , &index,4 ); +memcpy (data +14 , hash,TPM_DIGEST_SIZE ); + rc =tpm_transmit (chip, data,sizeof (data)); +if (rc >0 ) + rc =get_unaligned_be32 ((__be32 *) (data +6 )); + +module_put (chip->dev->driver->owner); +return rc; +} +EXPORT_SYMBOL_GPL (tpm_pcr_extend); +#define READ_PUBEK_RESULT_SIZE 314static const u8 readpubek[] = {0 ,193 ,/* TPM_TAG_RQU_COMMAND */
drivers/char/tpm/tpm.h +3 -1
@@ -1,5 +1,5 @@/* -* Copyright (C) 2004 IBM Corporation +* Copyright (C) 2004, 2007, 2008 IBM Corporation * * Authors: * Leendert van Doorn <[email protected]>
@@ -26,6 +26,7 @@#include <linux/miscdevice.h> #include <linux/platform_device.h> #include <linux/io.h> +#include <linux/tpm.h> enum tpm_timeout {TPM_TIMEOUT =5 ,/* msecs */
@@ -128,6 +129,7 @@ extern void tpm_get_timeouts(struct tpm_chip *);extern void tpm_gen_interrupt (struct tpm_chip *);extern void tpm_continue_selftest (struct tpm_chip *);extern unsigned long tpm_calc_ordinal_duration (struct tpm_chip *,u32 ); +ssize_t tpm_transmit (struct tpm_chip *chip,char *buf,size_t bufsiz);extern struct tpm_chip *tpm_register_hardware (struct device *,const struct tpm_vendor_specific *);extern int tpm_open (struct inode *,struct file *);
drivers/char/tpm/tpm_tis.c +3 -0
@@ -642,6 +642,9 @@ static __devexit void tpm_tis_pnp_remove(struct pnp_dev *dev)static struct pnp_driver tis_pnp_driver = { .name ="tpm_tis" , + .driver = { + .owner =THIS_MODULE , + }, .id_table = tpm_pnp_tbl, .probe = tpm_tis_pnp_init, .suspend = tpm_tis_pnp_suspend,
include/linux/tpm.h new file +49 -0
49 lines not on this page · raw message
Signature · 1 line
1.5.5.1
Serge E. Hallyn
maintainerRe: [PATCH 1/3] integrity: TPM internel kernel interface
Quoted 4 lines · Mimi Zohar
The internal TPM kernel interface did not protect itself from the removal of the TPM driver, while being used. We continue to protect the
tpm_chip_listusing thedriver_lockas before, and are using an rcu lock to protect readers. The internal TPM
I still would like to see this spelled out somewhere - correct me if I'm wrong but none of the patches sent so far have this spelled out in in-line comments, do they?
It does look sane:
1. writes to tpm_chip_list are protected by driver_lock
2. readers of the list are protected by rcu
3. chips which are read from the tpm_chip_list, if they are used outside of the rcu_read_lock(), are pinned using get_device(chip->dev) before releasing the rcu_read_lock.
Like I say it looks sane, but something like the above summary could stand to be in a comment on top of tpm.c or something.
Quoted 7 lines
kernel interface now protects itself from the driver being removed by incrementing the module reference count.
Resubmitting integrity-tpm-internal-kernel-interface.patch, which was previously Signed-off-by Kylene Hall.
Updated per feedback:
Quoted 8 lines
Adds the following support:
- make internal kernel interface to transmit TPM commands global
- adds reading a pcr value
- adds extending a pcr value
- adds lookup thetpm_chipfor given chip number and typeSigned-off-by Mimi Zohar <[email protected]>Signed-off-by Rajiv Andrade <[email protected]>
Now there are other, existing callers of tpm_transmit. Are they all protected by sysfs pinning the kobject and thereby the device, for the duration of the call?
thanks,
-serge
Quoted 302 lines
---
drivers/char/tpm/tpm.c +137
-3@@ -1,11 +1,12 @@/* -* Copyright (C) 2004 IBM Corporation +* Copyright (C) 2004,2007,2008 IBM Corporation * * Authors: * Leendert van Doorn <[email protected]> * Dave Safford <[email protected]> * Reiner Sailer <[email protected]> * Kylene Hall <[email protected]> +* Debora Velarde <[email protected]> * * Maintained by: <[email protected]> * @@ -28,6 +29,14 @@#include <linux/spinlock.h> #include <linux/smp_lock.h> +#include <linux/mm.h> +#include <linux/slab.h> +#include <linux/string.h> +#include <linux/crypto.h> +#include <linux/fs.h> +#include <linux/scatterlist.h> +#include <linux/rcupdate.h> +#include <asm/unaligned.h> #include "tpm.h" enum tpm_const {@@ -50,6 +59,8 @@ enum tpm_duration {static LIST_HEAD (tpm_chip_list);static DEFINE_SPINLOCK (driver_lock); static DECLARE_BITMAP(dev_mask, TPM_NUM_DEVICES); +#define TPM_CHIP_NUM_MASK 0x0000ffff +#define TPM_CHIP_TYPE_SHIFT 16/* * Array with one entry per ordinal defining the maximum amount @@ -366,8 +377,7 @@ EXPORT_SYMBOL_GPL(tpm_calc_ordinal_duration);/* * Internal kernel interface to transmit TPM commands */ -static ssize_t tpm_transmit (struct tpm_chip *chip,const char *buf, -size_t bufsiz) +ssize_t tpm_transmit (struct tpm_chip *chip,char *buf,size_t bufsiz) {ssize_t rc;u32 count, ordinal;@@ -425,6 +435,7 @@ out:mutex_unlock (&chip->tpm_mutex);return rc; } +EXPORT_SYMBOL_GPL (tpm_transmit);#define TPM_DIGEST_SIZE 20#define TPM_ERROR_SIZE 10@@ -710,6 +721,7 @@ ssize_t tpm_show_temp_deactivated(struct device * dev, }EXPORT_SYMBOL_GPL (tpm_show_temp_deactivated); +#define READ_PCR_RESULT_SIZE 30static const u8 pcrread[] = {0 ,193 ,/* TPM_TAG_RQU_COMMAND */ 0 ,0 ,0 ,14 ,/* length */ @@ -765,6 +777,128 @@ out: }EXPORT_SYMBOL_GPL (tpm_show_pcrs); +/* +* tpm_chip_lookup - return tpm_chip for given chip number and type +* +* Must be called with rcu_read_lock. +*/ +static struct tpm_chip *tpm_chip_lookup (int chip_num,int chip_typ) +{ +struct tpm_chip *pos; +int rc; + +list_for_each_entry_rcu (pos, &tpm_chip_list, list) { + rc = (chip_num ==TPM_ANY_NUM || pos->dev_num == chip_num) + && (chip_typ ==TPM_ANY_TYPE ); +if (rc) +return pos; + } +return NULL ; +} + +/** +* tpm_pcr_read - read a pcr value +* @chip_id: tpm chip identifier +* Upper 2 bytes: ANY, HW_ONLY or SW_ONLY +* Lower 2 bytes: tpm idx # or AN& +* @pcr_idx: pcr idx to retrieve +* @res_buf: TPM_PCR value +* size of res_buf is 20 bytes (or NULL if you don't care) +* +* The TPM driver should be built-in, but for whatever reason it +* isn't, protect against the chip disappearing, by incrementing +* the module usage count. +*/ +int tpm_pcr_read (u32 chip_id,int pcr_idx,u8 *res_buf) +{ +u8 data[READ_PCR_RESULT_SIZE ]; +int rc; +__be32 index; +int chip_num = chip_id &TPM_CHIP_NUM_MASK ; +struct tpm_chip *chip; + +rcu_read_lock (); + chip =tpm_chip_lookup (chip_num, chip_id >>TPM_CHIP_TYPE_SHIFT ); +if (chip ==NULL ) { +rcu_read_unlock (); +return -ENODEV ; + } +if (!try_module_get (chip->dev->driver->owner)) { +rcu_read_unlock (); +return -ENODEV ; + } +rcu_read_unlock (); + +BUILD_BUG_ON (sizeof (pcrread) >READ_PCR_RESULT_SIZE ); +memcpy (data, pcrread,sizeof (pcrread)); + index =cpu_to_be32 (pcr_idx); +memcpy (data +10 , &index,4 ); + rc =tpm_transmit (chip, data,sizeof (data)); +if (rc >0 ) + rc =get_unaligned_be32 ((__be32 *) (data +6 )); + +if (rc ==0 && res_buf) +memcpy (res_buf, data +10 ,TPM_DIGEST_SIZE ); + +module_put (chip->dev->driver->owner); +return rc; +} +EXPORT_SYMBOL_GPL (tpm_pcr_read); + +#define EXTEND_PCR_SIZE 34 +static const u8 pcrextend[] = { +0 ,193 ,/* TPM_TAG_RQU_COMMAND */ +0 ,0 ,0 ,34 ,/* length */ +0 ,0 ,0 ,20 ,/* TPM_ORD_Extend */ +0 ,0 ,0 ,0 /* PCR index */ +}; + +/** +* tpm_pcr_extend - extend pcr value with hash +* @chip_id: tpm chip identifier +* Upper 2 bytes: ANY, HW_ONLY or SW_ONLY +* Lower 2 bytes: tpm idx # or AN& +* @pcr_idx: pcr idx to extend +* @hash: hash value used to extend pcr value +* +* The TPM driver should be built-in, but for whatever reason it +* isn't, protect against the chip disappearing, by incrementing +* the module usage count. +*/ +int tpm_pcr_extend (u32 chip_id,int pcr_idx,const u8 *hash) +{ +u8 data[EXTEND_PCR_SIZE ]; +int rc; +__be32 index; +int chip_num = chip_id &TPM_CHIP_NUM_MASK ; +struct tpm_chip *chip; + +rcu_read_lock (); + chip =tpm_chip_lookup (chip_num, chip_id >>TPM_CHIP_TYPE_SHIFT ); +if (chip ==NULL ) { +rcu_read_unlock (); +return -ENODEV ; + } +if (!try_module_get (chip->dev->driver->owner)) { +rcu_read_unlock (); +return -ENODEV ; + } +rcu_read_unlock (); + +BUILD_BUG_ON (sizeof (pcrextend) >EXTEND_PCR_SIZE ); +memcpy (data, pcrextend,sizeof (pcrextend)); + index =cpu_to_be32 (pcr_idx); +memcpy (data +10 , &index,4 ); +memcpy (data +14 , hash,TPM_DIGEST_SIZE ); + rc =tpm_transmit (chip, data,sizeof (data)); +if (rc >0 ) + rc =get_unaligned_be32 ((__be32 *) (data +6 )); + +module_put (chip->dev->driver->owner); +return rc; +} +EXPORT_SYMBOL_GPL (tpm_pcr_extend); +#define READ_PUBEK_RESULT_SIZE 314static const u8 readpubek[] = {0 ,193 ,/* TPM_TAG_RQU_COMMAND */ drivers/char/tpm/tpm.h +3
-1@@ -1,5 +1,5 @@/* -* Copyright (C) 2004 IBM Corporation +* Copyright (C) 2004, 2007, 2008 IBM Corporation * * Authors: * Leendert van Doorn <[email protected]> @@ -26,6 +26,7 @@#include <linux/miscdevice.h> #include <linux/platform_device.h> #include <linux/io.h> +#include <linux/tpm.h> enum tpm_timeout {TPM_TIMEOUT =5 ,/* msecs */ @@ -128,6 +129,7 @@ extern void tpm_get_timeouts(struct tpm_chip *);extern void tpm_gen_interrupt (struct tpm_chip *);extern void tpm_continue_selftest (struct tpm_chip *);extern unsigned long tpm_calc_ordinal_duration (struct tpm_chip *,u32 ); +ssize_t tpm_transmit (struct tpm_chip *chip,char *buf,size_t bufsiz);extern struct tpm_chip *tpm_register_hardware (struct device *,const struct tpm_vendor_specific *);extern int tpm_open (struct inode *,struct file *);drivers/char/tpm/tpm_tis.c +3
-0@@ -642,6 +642,9 @@ static __devexit void tpm_tis_pnp_remove(struct pnp_dev *dev)static struct pnp_driver tis_pnp_driver = { .name ="tpm_tis" , + .driver = { + .owner =THIS_MODULE , + }, .id_table = tpm_pnp_tbl, .probe = tpm_tis_pnp_init, .suspend = tpm_tis_pnp_suspend,include/linux/tpm.h new file +49
-0@@ -0,0 +1,49 @@ +/* +* Copyright (C) 2004,2007,2008 IBM Corporation +* +* Authors: +* Leendert van Doorn <[email protected]> +* Dave Safford <[email protected]> +* Reiner Sailer <[email protected]> +* Kylene Hall <[email protected]> +* Debora Velarde <[email protected]> +* +* Maintained by: <[email protected]> +* +* Device driver for TCG/TCPA TPM (trusted platform module). +* Specifications at www.trustedcomputinggroup.org +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License as +* published by the Free Software Foundation, version 2 of the +* License. +* +*/ +#ifndef __LINUX_TPM_H__ +#define __LINUX_TPM_H__ + +#define PCI_DEVICE_ID_AMD_8111_LPC 0x7468 + +/* +* Chip type is one of these values in the upper two bytes of chip_id +*/ +enum tpm_chip_type { +TPM_HW_TYPE =0x0 , +TPM_SW_TYPE =0x1 , +TPM_ANY_TYPE =0xFFFF , +}; + +/* +* Chip num is this value or a valid tpm idx in lower two bytes of chip_id +*/ +enum tpm_chip_num { +TPM_ANY_NUM =0xFFFF , +}; + + +#if defined(CONFIG_TCG_TPM ) || defined(CONFIG_TCG_TPM_MODULE ) + +extern int tpm_pcr_read (u32 chip_id,int pcr_idx,u8 *res_buf); +extern int tpm_pcr_extend (u32 chip_id,int pcr_idx,const u8 *hash); +#endif +#endif Signature · 7 lines
1.5.5.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 1/3] integrity: TPM internel kernel interface
Quoted 19 lines · Serge E. Hallyn
Quoted 4 lines · Mimi Zohar
The internal TPM kernel interface did not protect itself from the removal of the TPM driver, while being used. We continue to protect the
tpm_chip_listusing thedriver_lockas before, and are using an rcu lock to protect readers. The internal TPMI still would like to see this spelled out somewhere - correct me if I'm wrong but none of the patches sent so far have this spelled out in in-line comments, do they?
It does look sane:
1. writes to
tpm_chip_listare protected bydriver_lock
2. readers of the list are protected by rcu
3. chips which are read from thetpm_chip_list, if they are used outside of thercu_read_lock(), are pinned usingget_device(chip->dev)before releasing thercu_read_lock.
Quoted 3 lines
Like I say it looks sane, but something like the above summary could stand to be in a comment on top of
tpm.cor something.
No problem, I'll submit a patch containing a proper comment section to be applied on top of these, maybe after they get accepted.
Quoted 13 lines
Quoted 13 lines
kernel interface now protects itself from the driver being removed by incrementing the module reference count.
Resubmitting integrity-tpm-internal-kernel-interface.patch, which was previously Signed-off-by Kylene Hall.
Updated per feedback:Adds the following support:
- make internal kernel interface to transmit TPM commands global
- adds reading a pcr value
- adds extending a pcr value
- adds lookup thetpm_chipfor given chip number and type
Quoted 7 lines
Quoted 2 lines
Signed-off-by Mimi Zohar <[email protected]>Signed-off-by Rajiv Andrade <[email protected]>Now there are other, existing callers of
tpm_transmit. Are they all protected by sysfs pinning the kobject and thereby the device, for the duration of the call?
They aren't called through sysfs, but are still protected. These new functions get chip data consistently by using rcu_read. Then, after computing what's intended to be written back to the chip, tpm_transmit sends the new data while using tpm_mutex, so both operations are performed without the risk of a race condition.
Quoted 310 lines
thanks,
-sergeQuoted 302 lines
---
drivers/char/tpm/tpm.c +137
-3@@ -1,11 +1,12 @@/* -* Copyright (C) 2004 IBM Corporation +* Copyright (C) 2004,2007,2008 IBM Corporation * * Authors: * Leendert van Doorn <[email protected]> * Dave Safford <[email protected]> * Reiner Sailer <[email protected]> * Kylene Hall <[email protected]> +* Debora Velarde <[email protected]> * * Maintained by: <[email protected]> * @@ -28,6 +29,14 @@#include <linux/spinlock.h> #include <linux/smp_lock.h> +#include <linux/mm.h> +#include <linux/slab.h> +#include <linux/string.h> +#include <linux/crypto.h> +#include <linux/fs.h> +#include <linux/scatterlist.h> +#include <linux/rcupdate.h> +#include <asm/unaligned.h> #include "tpm.h" enum tpm_const {@@ -50,6 +59,8 @@ enum tpm_duration {static LIST_HEAD (tpm_chip_list);static DEFINE_SPINLOCK (driver_lock); static DECLARE_BITMAP(dev_mask, TPM_NUM_DEVICES); +#define TPM_CHIP_NUM_MASK 0x0000ffff +#define TPM_CHIP_TYPE_SHIFT 16/* * Array with one entry per ordinal defining the maximum amount @@ -366,8 +377,7 @@ EXPORT_SYMBOL_GPL(tpm_calc_ordinal_duration);/* * Internal kernel interface to transmit TPM commands */ -static ssize_t tpm_transmit (struct tpm_chip *chip,const char *buf, -size_t bufsiz) +ssize_t tpm_transmit (struct tpm_chip *chip,char *buf,size_t bufsiz) {ssize_t rc;u32 count, ordinal;@@ -425,6 +435,7 @@ out:mutex_unlock (&chip->tpm_mutex);return rc; } +EXPORT_SYMBOL_GPL (tpm_transmit);#define TPM_DIGEST_SIZE 20#define TPM_ERROR_SIZE 10@@ -710,6 +721,7 @@ ssize_t tpm_show_temp_deactivated(struct device * dev, }EXPORT_SYMBOL_GPL (tpm_show_temp_deactivated); +#define READ_PCR_RESULT_SIZE 30static const u8 pcrread[] = {0 ,193 ,/* TPM_TAG_RQU_COMMAND */ 0 ,0 ,0 ,14 ,/* length */ @@ -765,6 +777,128 @@ out: }EXPORT_SYMBOL_GPL (tpm_show_pcrs); +/* +* tpm_chip_lookup - return tpm_chip for given chip number and type +* +* Must be called with rcu_read_lock. +*/ +static struct tpm_chip *tpm_chip_lookup (int chip_num,int chip_typ) +{ +struct tpm_chip *pos; +int rc; + +list_for_each_entry_rcu (pos, &tpm_chip_list, list) { + rc = (chip_num ==TPM_ANY_NUM || pos->dev_num == chip_num) + && (chip_typ ==TPM_ANY_TYPE ); +if (rc) +return pos; + } +return NULL ; +} + +/** +* tpm_pcr_read - read a pcr value +* @chip_id: tpm chip identifier +* Upper 2 bytes: ANY, HW_ONLY or SW_ONLY +* Lower 2 bytes: tpm idx # or AN& +* @pcr_idx: pcr idx to retrieve +* @res_buf: TPM_PCR value +* size of res_buf is 20 bytes (or NULL if you don't care) +* +* The TPM driver should be built-in, but for whatever reason it +* isn't, protect against the chip disappearing, by incrementing +* the module usage count. +*/ +int tpm_pcr_read (u32 chip_id,int pcr_idx,u8 *res_buf) +{ +u8 data[READ_PCR_RESULT_SIZE ]; +int rc; +__be32 index; +int chip_num = chip_id &TPM_CHIP_NUM_MASK ; +struct tpm_chip *chip; + +rcu_read_lock (); + chip =tpm_chip_lookup (chip_num, chip_id >>TPM_CHIP_TYPE_SHIFT ); +if (chip ==NULL ) { +rcu_read_unlock (); +return -ENODEV ; + } +if (!try_module_get (chip->dev->driver->owner)) { +rcu_read_unlock (); +return -ENODEV ; + } +rcu_read_unlock (); + +BUILD_BUG_ON (sizeof (pcrread) >READ_PCR_RESULT_SIZE ); +memcpy (data, pcrread,sizeof (pcrread)); + index =cpu_to_be32 (pcr_idx); +memcpy (data +10 , &index,4 ); + rc =tpm_transmit (chip, data,sizeof (data)); +if (rc >0 ) + rc =get_unaligned_be32 ((__be32 *) (data +6 )); + +if (rc ==0 && res_buf) +memcpy (res_buf, data +10 ,TPM_DIGEST_SIZE ); + +module_put (chip->dev->driver->owner); +return rc; +} +EXPORT_SYMBOL_GPL (tpm_pcr_read); + +#define EXTEND_PCR_SIZE 34 +static const u8 pcrextend[] = { +0 ,193 ,/* TPM_TAG_RQU_COMMAND */ +0 ,0 ,0 ,34 ,/* length */ +0 ,0 ,0 ,20 ,/* TPM_ORD_Extend */ +0 ,0 ,0 ,0 /* PCR index */ +}; + +/** +* tpm_pcr_extend - extend pcr value with hash +* @chip_id: tpm chip identifier +* Upper 2 bytes: ANY, HW_ONLY or SW_ONLY +* Lower 2 bytes: tpm idx # or AN& +* @pcr_idx: pcr idx to extend +* @hash: hash value used to extend pcr value +* +* The TPM driver should be built-in, but for whatever reason it +* isn't, protect against the chip disappearing, by incrementing +* the module usage count. +*/ +int tpm_pcr_extend (u32 chip_id,int pcr_idx,const u8 *hash) +{ +u8 data[EXTEND_PCR_SIZE ]; +int rc; +__be32 index; +int chip_num = chip_id &TPM_CHIP_NUM_MASK ; +struct tpm_chip *chip; + +rcu_read_lock (); + chip =tpm_chip_lookup (chip_num, chip_id >>TPM_CHIP_TYPE_SHIFT ); +if (chip ==NULL ) { +rcu_read_unlock (); +return -ENODEV ; + } +if (!try_module_get (chip->dev->driver->owner)) { +rcu_read_unlock (); +return -ENODEV ; + } +rcu_read_unlock (); + +BUILD_BUG_ON (sizeof (pcrextend) >EXTEND_PCR_SIZE ); +memcpy (data, pcrextend,sizeof (pcrextend)); + index =cpu_to_be32 (pcr_idx); +memcpy (data +10 , &index,4 ); +memcpy (data +14 , hash,TPM_DIGEST_SIZE ); + rc =tpm_transmit (chip, data,sizeof (data)); +if (rc >0 ) + rc =get_unaligned_be32 ((__be32 *) (data +6 )); + +module_put (chip->dev->driver->owner); +return rc; +} +EXPORT_SYMBOL_GPL (tpm_pcr_extend); +#define READ_PUBEK_RESULT_SIZE 314static const u8 readpubek[] = {0 ,193 ,/* TPM_TAG_RQU_COMMAND */ drivers/char/tpm/tpm.h +3
-1@@ -1,5 +1,5 @@/* -* Copyright (C) 2004 IBM Corporation +* Copyright (C) 2004, 2007, 2008 IBM Corporation * * Authors: * Leendert van Doorn <[email protected]> @@ -26,6 +26,7 @@#include <linux/miscdevice.h> #include <linux/platform_device.h> #include <linux/io.h> +#include <linux/tpm.h> enum tpm_timeout {TPM_TIMEOUT =5 ,/* msecs */ @@ -128,6 +129,7 @@ extern void tpm_get_timeouts(struct tpm_chip *);extern void tpm_gen_interrupt (struct tpm_chip *);extern void tpm_continue_selftest (struct tpm_chip *);extern unsigned long tpm_calc_ordinal_duration (struct tpm_chip *,u32 ); +ssize_t tpm_transmit (struct tpm_chip *chip,char *buf,size_t bufsiz);extern struct tpm_chip *tpm_register_hardware (struct device *,const struct tpm_vendor_specific *);extern int tpm_open (struct inode *,struct file *);drivers/char/tpm/tpm_tis.c +3
-0@@ -642,6 +642,9 @@ static __devexit void tpm_tis_pnp_remove(struct pnp_dev *dev)static struct pnp_driver tis_pnp_driver = { .name ="tpm_tis" , + .driver = { + .owner =THIS_MODULE , + }, .id_table = tpm_pnp_tbl, .probe = tpm_tis_pnp_init, .suspend = tpm_tis_pnp_suspend,include/linux/tpm.h new file +49
-0@@ -0,0 +1,49 @@ +/* +* Copyright (C) 2004,2007,2008 IBM Corporation +* +* Authors: +* Leendert van Doorn <[email protected]> +* Dave Safford <[email protected]> +* Reiner Sailer <[email protected]> +* Kylene Hall <[email protected]> +* Debora Velarde <[email protected]> +* +* Maintained by: <[email protected]> +* +* Device driver for TCG/TCPA TPM (trusted platform module). +* Specifications at www.trustedcomputinggroup.org +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License as +* published by the Free Software Foundation, version 2 of the +* License. +* +*/ +#ifndef __LINUX_TPM_H__ +#define __LINUX_TPM_H__ + +#define PCI_DEVICE_ID_AMD_8111_LPC 0x7468 + +/* +* Chip type is one of these values in the upper two bytes of chip_id +*/ +enum tpm_chip_type { +TPM_HW_TYPE =0x0 , +TPM_SW_TYPE =0x1 , +TPM_ANY_TYPE =0xFFFF , +}; + +/* +* Chip num is this value or a valid tpm idx in lower two bytes of chip_id +*/ +enum tpm_chip_num { +TPM_ANY_NUM =0xFFFF , +}; + + +#if defined(CONFIG_TCG_TPM ) || defined(CONFIG_TCG_TPM_MODULE ) + +extern int tpm_pcr_read (u32 chip_id,int pcr_idx,u8 *res_buf); +extern int tpm_pcr_extend (u32 chip_id,int pcr_idx,const u8 *hash); +#endif +#endif Signature · 7 lines
1.5.5.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 3 lines
Rajiv Andrade <[email protected]> Security Development IBM Linux Technology Center
Re: [PATCH 1/3] integrity: TPM internel kernel interface
Quoted 20 lines · Rajiv Andrade
Quoted 19 lines · Serge E. Hallyn
Quoted 4 lines · Mimi Zohar
The internal TPM kernel interface did not protect itself from the removal of the TPM driver, while being used. We continue to protect the
tpm_chip_listusing thedriver_lockas before, and are using an rcu lock to protect readers. The internal TPMI still would like to see this spelled out somewhere - correct me if I'm wrong but none of the patches sent so far have this spelled out in in-line comments, do they?
It does look sane:
1. writes to
tpm_chip_listare protected bydriver_lock
2. readers of the list are protected by rcu
3. chips which are read from thetpm_chip_list, if they are used outside of thercu_read_lock(), are pinned usingget_device(chip->dev)before releasing thercu_read_lock.
Quoted 5 lines
Quoted 3 lines
Like I say it looks sane, but something like the above summary could stand to be in a comment on top of
tpm.cor something.No problem, I'll submit a patch containing a proper comment section to be applied on top of these, maybe after they get accepted.
Great, thanks.
Quoted 21 lines
Quoted 13 lines
Quoted 13 lines
kernel interface now protects itself from the driver being removed by incrementing the module reference count.
Resubmitting integrity-tpm-internal-kernel-interface.patch, which was previously Signed-off-by Kylene Hall.
Updated per feedback:Adds the following support:
- make internal kernel interface to transmit TPM commands global
- adds reading a pcr value
- adds extending a pcr value
- adds lookup thetpm_chipfor given chip number and typeQuoted 7 lines
Quoted 2 lines
Signed-off-by Mimi Zohar <[email protected]>Signed-off-by Rajiv Andrade <[email protected]>Now there are other, existing callers of
tpm_transmit. Are they all protected by sysfs pinning the kobject and thereby the device, for the duration of the call?
Quoted 5 lines
They aren't called through sysfs, but are still protected. These new functions get chip data consistently by using
rcu_read. Then, after computing what's intended to be written back to the chip,tpm_transmitsends the new data while usingtpm_mutex, so both operations are performed without the risk of a race condition.
Can you show me where the refcount for dev is incremented (under the rcu_read_lock), either in sysfs code or tpm code? I'm not finding it, but it may just be done in some subtle way that I'm glossing over.
thanks,
-serge
Re: [PATCH 1/3] integrity: TPM internel kernel interface
Serge,
Quoted 56 lines · Serge E. Hallyn
Quoted 20 lines · Rajiv Andrade
Quoted 19 lines · Serge E. Hallyn
Quoted 4 lines · Mimi Zohar
The internal TPM kernel interface did not protect itself from the removal of the TPM driver, while being used. We continue to protect the
tpm_chip_listusing thedriver_lockas before, and are using an rcu lock to protect readers. The internal TPMI still would like to see this spelled out somewhere - correct me if I'm wrong but none of the patches sent so far have this spelled out in in-line comments, do they?
It does look sane:
1. writes to
tpm_chip_listare protected bydriver_lock
2. readers of the list are protected by rcu
3. chips which are read from thetpm_chip_list, if they are used outside of thercu_read_lock(), are pinned usingget_device(chip->dev)before releasing thercu_read_lock.Quoted 5 lines
Quoted 3 lines
Like I say it looks sane, but something like the above summary could stand to be in a comment on top of
tpm.cor something.No problem, I'll submit a patch containing a proper comment section to be applied on top of these, maybe after they get accepted.
Great, thanks.
Quoted 21 lines
Quoted 13 lines
Quoted 13 lines
kernel interface now protects itself from the driver being removed by incrementing the module reference count.
Resubmitting integrity-tpm-internal-kernel-interface.patch, which was previously Signed-off-by Kylene Hall.
Updated per feedback:Adds the following support:
- make internal kernel interface to transmit TPM commands global
- adds reading a pcr value
- adds extending a pcr value
- adds lookup thetpm_chipfor given chip number and typeQuoted 7 lines
Quoted 2 lines
Signed-off-by Mimi Zohar <[email protected]>Signed-off-by Rajiv Andrade <[email protected]>Now there are other, existing callers of
tpm_transmit. Are they all protected by sysfs pinning the kobject and thereby the device, for the duration of the call?Quoted 5 lines
They aren't called through sysfs, but are still protected. These new functions get chip data consistently by using
rcu_read. Then, after computing what's intended to be written back to the chip,tpm_transmitsends the new data while usingtpm_mutex, so both operations are performed without the risk of a race condition.
Quoted 4 lines
Can you show me where the refcount for dev is incremented (under the
rcu_read_lock), either in sysfs code or tpm code? I'm not finding it, but it may just be done in some subtle way that I'm glossing over.
The refcount is incremented/decremented in tpm_register_hardware() and tpm_remove_hardware() for tpm module, and tpm_open() and tpm_release() for tpm_tis module, all inside tpm.c. The last two are referenced in tpm_tis.c:
tpm_tis.c
static const struct file_operations tis_ops = {
.owner = THIS_MODULE,
.llseek = no_llseek,
.open = tpm_open,
.read = tpm_read,
.write = tpm_write,
.release = tpm_release,
};
thanks,
Quoted 7 lines
thanks,
-serge
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 3 lines
Rajiv Andrade <[email protected]> Security Development IBM Linux Technology Center
Serge E. Hallyn
Acked-byRe: [PATCH 1/3] integrity: TPM internel kernel interface
Quoted 80 lines · Rajiv Andrade
Serge,
Quoted 56 lines · Serge E. Hallyn
Quoted 20 lines · Rajiv Andrade
Quoted 19 lines · Serge E. Hallyn
Quoted 4 lines · Mimi Zohar
The internal TPM kernel interface did not protect itself from the removal of the TPM driver, while being used. We continue to protect the
tpm_chip_listusing thedriver_lockas before, and are using an rcu lock to protect readers. The internal TPMI still would like to see this spelled out somewhere - correct me if I'm wrong but none of the patches sent so far have this spelled out in in-line comments, do they?
It does look sane:
1. writes to
tpm_chip_listare protected bydriver_lock
2. readers of the list are protected by rcu
3. chips which are read from thetpm_chip_list, if they are used outside of thercu_read_lock(), are pinned usingget_device(chip->dev)before releasing thercu_read_lock.Quoted 5 lines
Quoted 3 lines
Like I say it looks sane, but something like the above summary could stand to be in a comment on top of
tpm.cor something.No problem, I'll submit a patch containing a proper comment section to be applied on top of these, maybe after they get accepted.
Great, thanks.
Quoted 21 lines
Quoted 13 lines
Quoted 13 lines
kernel interface now protects itself from the driver being removed by incrementing the module reference count.
Resubmitting integrity-tpm-internal-kernel-interface.patch, which was previously Signed-off-by Kylene Hall.
Updated per feedback:Adds the following support:
- make internal kernel interface to transmit TPM commands global
- adds reading a pcr value
- adds extending a pcr value
- adds lookup thetpm_chipfor given chip number and typeQuoted 7 lines
Quoted 2 lines
Signed-off-by Mimi Zohar <[email protected]>Signed-off-by Rajiv Andrade <[email protected]>Now there are other, existing callers of
tpm_transmit. Are they all protected by sysfs pinning the kobject and thereby the device, for the duration of the call?Quoted 5 lines
They aren't called through sysfs, but are still protected. These new functions get chip data consistently by using
rcu_read. Then, after computing what's intended to be written back to the chip,tpm_transmitsends the new data while usingtpm_mutex, so both operations are performed without the risk of a race condition.Quoted 4 lines
Can you show me where the refcount for dev is incremented (under the
rcu_read_lock), either in sysfs code or tpm code? I'm not finding it, but it may just be done in some subtle way that I'm glossing over.The refcount is incremented/decremented in
tpm_register_hardware()andtpm_remove_hardware()for tpm module, andtpm_open()andtpm_release()fortpm_tismodule, all insidetpm.c. The last two are referenced intpm_tis.c:
tpm_tis.cstatic const struct
file_operationstis_ops= {
.owner =THIS_MODULE,
.llseek =no_llseek,
.open =tpm_open,
.read =tpm_read,
.write =tpm_write,
.release =tpm_release,
};
Quoted 1 line
thanks,
Yup, perfect. Don't know how I was missing that.
to the set.
thanks,
-serge
PATCH 2/3 integrity: Linux Integrity Module(LIM)
In reply to Mimi ZoharConcern was raised on the lkml mailing list, about adding i_integrity to the inode structure. This patch adds a comment clarifying that i_integrity is only included in the inode if INTEGRITY is configured.
This version resolves the merge issues resulting from the removal of the nameidata parameter to inode_permission().
- Moved the integrity_inode_permission() call from inode_permission() to vfs_inode_permission() and file_inode_permission().
- Replaced the inode and nameidata parameters with file and path parameters to integrity_inode_permission().
This patch is a redesign of the integrity framework, which address a number of issues, including
- generalizing the measurement API beyond just inode measurements.
- separation of the measurement into distinct collection, appraisal, and commitment phases, for greater flexibility.
Extended Verification Module(EVM) and the Integrity Measurement Architecture(IMA) were originally implemented as an LSM module. Based on discussions on the LSM mailing list, a decision was made that the LSM hooks should only be used to enforce mandatory access control decisions and a new set of hooks should be defined specifically for integrity.
EVM/IMA was limited to verifying and measuring a file's (i.e. an inode) integrity and the metadata associated with it. Current research is looking into other types of integrity measurements. (i.e. "Linux kernel integrity measurement using contextual inspection", by Peter A. Loscocco, Perry W. Wilson, J. Aaron Pendergrass, C. Durward McDonell,
http://doi.acm.org/10.1145/1314354.1314362). As a result, a requirement of the new integrity framework is support for different types of integrity measurements.
This patch provides an integrity framework(api and hooks) and placement of the integrity hooks in the appropriate places in the fs directory. Collecting, appraising, and storing of file and other types of integrity data is supported. Multiple integrity templates, which implement the integrity API, may register themselves. For now, only a single integrity provider can register itself for the integrity hooks. (Support for multiple providers registering themselves for the integrity hooks would require some form of stacking.)
The six integrity hooks are:
inode_permission, inode_alloc_integrity, inode_free_integrity, bprm_check_integrity, file_free_integrity, file_mmap
The five integrity API calls provided are:
integrity_must_measure, integrity_collect_measurement, integrity_appraise_measurement, integrity_store_measurement, and integrity_display_template.
The type of integrity data being collected, appraised, stored, or displayed is template dependent.
(Details on the calls and their exact arguments are in linux/integrity.h, included in the patch.)
---
Documentation/kernel-parameters.txt +6 -0
@@ -44,6 +44,7 @@ parameter is applicable: FB The frame buffer device is enabled. HW Appropriate hardware is enabled. IA-64 IA-64 architecture is enabled. + INTEGRITY Integrity support is enabled. IOSCHED More than one I/O scheduler is enabled. IP_PNP IP DHCP, BOOTP, or RARP is enabled. ISAPNP ISA PnP code is enabled.
@@ -874,6 +875,11 @@ and is between 256 and 4096 characters. It is defined in the file inport.irq= [HW] Inport (ATI XL and Microsoft) busmouse driver Format: <irq> + integrity_audit= [INTEGRITY] + Format: { "0" | "1" } + 0 -- disable integrity auditing messages. + 1 -- enable integrity auditing messages. (Default) + inttest= [IA64] iommu= [x86]
fs/exec.c +4 -0
@@ -45,6 +45,7 @@#include <linux/proc_fs.h> #include <linux/mount.h> #include <linux/security.h> +#include <linux/integrity.h> #include <linux/syscalls.h> #include <linux/tsacct_kern.h> #include <linux/cn_proc.h>
@@ -1204,6 +1205,9 @@ int search_binary_handler(struct linux_binprm *bprm,struct pt_regs *regs) retval =security_bprm_check (bprm);if (retval)return retval; + retval =integrity_bprm_check (bprm); +if (retval) +return retval;/* kernel module loader fixup */ /* so we don't try to load run modprobe in kernel space. */
fs/file_table.c +3 -0
@@ -13,6 +13,7 @@#include <linux/module.h> #include <linux/fs.h> #include <linux/security.h> +#include <linux/integrity.h> #include <linux/eventpoll.h> #include <linux/rcupdate.h> #include <linux/mount.h>
@@ -272,6 +273,7 @@ void __fput(struct file *file)if (file->f_op && file->f_op->release) file->f_op->release (inode, file);security_file_free (file); +integrity_file_free (file);if (unlikely (S_ISCHR (inode->i_mode) && inode->i_cdev !=NULL ))cdev_put (inode->i_cdev);fops_put (file->f_op);
@@ -343,6 +345,7 @@ void put_filp(struct file *file) {if (atomic_long_dec_and_test (&file->f_count)) {security_file_free (file); +integrity_file_free (file);file_kill (file);file_free (file); }
fs/inode.c +15 -7
@@ -17,6 +17,7 @@#include <linux/hash.h> #include <linux/swap.h> #include <linux/security.h> +#include <linux/integrity.h> #include <linux/pagemap.h> #include <linux/cdev.h> #include <linux/bootmem.h>
@@ -143,13 +144,12 @@ static struct inode *alloc_inode(struct super_block *sb) inode->i_cdev =NULL ; inode->i_rdev =0 ; inode->dirtied_when =0 ; -if (security_inode_alloc (inode)) { -if (inode->i_sb->s_op->destroy_inode) - inode->i_sb->s_op->destroy_inode (inode); -else -kmem_cache_free (inode_cachep, (inode)); -return NULL ; - } +if (security_inode_alloc (inode)) + goto out_free_inode; + +/* allocate, attach and initialize an i_integrity */ +if (integrity_inode_alloc (inode)) + goto out_free_inode;spin_lock_init (&inode->i_lock);lockdep_set_class (&inode->i_lock, &sb->s_type->i_lock_key);
@@ -185,12 +185,20 @@ static struct inode *alloc_inode(struct super_block *sb) inode->i_mapping = mapping; }return inode; + +out_free_inode: +if (inode->i_sb->s_op->destroy_inode) + inode->i_sb->s_op->destroy_inode (inode); +else +kmem_cache_free (inode_cachep, (inode)); +return NULL ; }void destroy_inode (struct inode *inode) {BUG_ON (inode_has_buffers (inode));security_inode_free (inode); +integrity_inode_free (inode);if (inode->i_sb->s_op->destroy_inode) inode->i_sb->s_op->destroy_inode (inode);else
fs/namei.c +17 -2
@@ -24,6 +24,7 @@#include <linux/fsnotify.h> #include <linux/personality.h> #include <linux/security.h> +#include <linux/integrity.h> #include <linux/syscalls.h> #include <linux/mount.h> #include <linux/audit.h>
@@ -289,7 +290,14 @@ int inode_permission(struct inode *inode, int mask)*/ int vfs_permission (struct nameidata *nd,int mask) { -return inode_permission (nd->path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (nd->path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (NULL , &nd->path, + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC )); }/**
@@ -306,7 +314,14 @@ int vfs_permission(struct nameidata *nd, int mask)*/ int file_permission (struct file *file,int mask) { -return inode_permission (file->f_path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (file->f_path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (file,NULL , + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC )); }/*
include/linux/audit.h +8 -0
@@ -123,6 +123,11 @@#define AUDIT_LAST_KERN_ANOM_MSG 1799#define AUDIT_ANOM_PROMISCUOUS 1700/* Device changed promiscuous mode */ #define AUDIT_ANOM_ABEND 1701/* Process ended abnormally */ +#define AUDIT_INTEGRITY_DATA 1800/* Data integrity verification */ +#define AUDIT_INTEGRITY_METADATA 1801/* Metadata integrity verification */ +#define AUDIT_INTEGRITY_STATUS 1802/* Integrity enable status */ +#define AUDIT_INTEGRITY_HASH 1803/* Integrity HASH type */ +#define AUDIT_INTEGRITY_PCR 1804/* PCR invalidation msgs */ #define AUDIT_KERNEL 2000/* Asynchronous audit record. NOT A REQUEST. */
@@ -440,6 +445,8 @@ extern int audit_set_loginuid(struct task_struct *task, uid_t loginuid);#define audit_get_loginuid (t) ((t)->loginuid)#define audit_get_sessionid (t) ((t)->sessionid)extern void audit_log_task_context (struct audit_buffer *ab); +extern void audit_log_inode_context (struct audit_buffer *ab, +struct inode *inode);extern int __audit_ipc_obj (struct kern_ipc_perm *ipcp);extern int __audit_ipc_set_perm (unsigned long qbytes,uid_t uid,gid_t gid,mode_t mode);extern int audit_bprm (struct linux_binprm *bprm);
@@ -520,6 +527,7 @@ extern int audit_signals;#define audit_get_loginuid (t) (-1)#define audit_get_sessionid (t) (-1)#define audit_log_task_context (b) do { ; } while (0) +#define audit_log_inode_context (b, a) do { } while (0)#define audit_ipc_obj (i) ({ 0; })#define audit_ipc_set_perm (q,u,g,m) ({ 0; })#define audit_bprm (p) ({ 0; })
include/linux/fs.h +3 -0
@@ -683,6 +683,9 @@ struct inode {#ifdef CONFIG_SECURITY void *i_security;#endif +#ifdef CONFIG_INTEGRITY +void *i_integrity; +#endif void *i_private;/* fs or device private pointer */ };
include/linux/integrity.h new file +182 -0
182 lines not on this page · raw message
mm/mmap.c +4 -0
@@ -20,6 +20,7 @@#include <linux/fs.h> #include <linux/personality.h> #include <linux/security.h> +#include <linux/integrity.h> #include <linux/hugetlb.h> #include <linux/profile.h> #include <linux/module.h>
@@ -1050,6 +1051,9 @@ unsigned long do_mmap_pgoff(struct file * file, unsigned long addr, error =security_file_mmap (file, reqprot, prot, flags, addr,0 );if (error)return error; + error =integrity_file_mmap (file, prot); +if (error) +return error;return mmap_region (file, addr, len, flags, vm_flags, pgoff, accountable);
security/Kconfig +2 -0
@@ -4,6 +4,8 @@ menu "Security options" +source security/integrity/Kconfig + config KEYS bool "Enable access key retention support" help
security/Makefile +4 -0
@@ -17,3 +17,7 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += smack/built-in.o obj-$(CONFIG_SECURITY_ROOTPLUG) += root_plug.o obj-$(CONFIG_CGROUP_DEVICE) += device_cgroup.o + +# Object integrity file lists +subdir-$(CONFIG_INTEGRITY) += integrity +obj-$(CONFIG_INTEGRITY) += integrity/built-in.o
security/integrity/Kconfig new file +24 -0
@@ -0,0 +1,24 @@ +# +# Integrity configuration +# + +menu "Integrity options" + +config INTEGRITY + bool "Enable different integrity models" + help + This allows you to choose different integrity modules to be + configured into your kernel. + + If you are unsure how to answer this question, answer N. + +config INTEGRITY_AUDIT + bool "Integrity audit boot parameter" + depends on INTEGRITY + default y + help + This option adds a kernel parameter 'integrity_audit', which + allows integrity auditing to be disabled at boot. If this + option is selected, integrity auditing can be disabled with + 'integrity_audit=0' on the kernel command line. +endmenu
security/integrity/Makefile new file +6 -0
@@ -0,0 +1,6 @@ +# +# Makefile for the kernel integrity code +# + +# Object file lists +obj-$(CONFIG_INTEGRITY) += integrity.o integrity_audit.o
security/integrity/integrity.c new file +308 -0
308 lines not on this page · raw message
security/integrity/integrity_audit.c new file +79 -0
79 lines not on this page · raw message
Signature · 1 line
1.5.5.1
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
Quoted 17 lines
int
vfs_permission(struct nameidata *nd, int mask){fs/namei.c +8
-1-return inode_permission (nd->path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (nd->path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (NULL , &nd->path, + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC )); }/** @@ -306,7 +314,14 @@ int vfs_permission(struct nameidata *nd, int mask)*/ int file_permission (struct file *file,int mask)
fs/namei.c int vfs_permission(struct nameidata *nd, int mask) · line 324
Quoted 10 lines
fs/namei.c +8
-1{ -return inode_permission (file->f_path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (file->f_path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (file,NULL , + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC ));
Please don't add anything here as these two wrappers will go away. Please only make decisions based on what you get in inode_permission().
Quoted 8 lines
(quoted diff) +0
-0} /*include/linux/fs.h +0
-0
include/linux/fs.h struct inode { · line 688
Quoted 6 lines
include/linux/fs.h +3
-0@@ -683,6 +683,9 @@ struct inode {#ifdef CONFIG_SECURITY void *i_security;#endif +#ifdef CONFIG_INTEGRITY +void *i_integrity; +#endif
Sorry, but as said before bloating the inode for this is not an option. Please use something like the MRU approach I suggested in the last review round.
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
Quoted 22 lines · Christoph Hellwig
Quoted 22 lines
int
vfs_permission(struct nameidata *nd, int mask){fs/namei.c +11
-2-return inode_permission (nd->path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (nd->path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (NULL , &nd->path, + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC )); }/** @@ -306,7 +314,14 @@ int vfs_permission(struct nameidata *nd, int mask)*/ int file_permission (struct file *file,int mask) { -return inode_permission (file->f_path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (file->f_path.dentry->d_inode, mask);
Quoted 8 lines
fs/namei.c int vfs_permission(struct nameidata *nd, int mask) · line 324
Quoted 5 lines
fs/namei.c +5
-0+if (retval) +return retval; +return integrity_inode_permission (file,NULL , + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC ));Please don't add anything here as these two wrappers will go away. Please only make decisions based on what you get in
inode_permission().
Hmm... As Mimi mentioned in the last review, we really need access to a path, which is not available in inode_permission. (Note the path is not used to make any integrity decision, but is recorded along with the measurement to help with the integrity analysis by a third party verifier.) Yes, there are other callers without path information, but getting a path here covers the bulk of the measurements.
Is there some other alternative, other than this, or passing the dentry into inode_permission, which was also rejected?
Quoted 18 lines
Quoted 8 lines
(quoted diff) +0
-0} /*include/linux/fs.h +0
-0include/linux/fs.h struct inode { · line 688
Quoted 6 lines
include/linux/fs.h +3
-0@@ -683,6 +683,9 @@ struct inode {#ifdef CONFIG_SECURITY void *i_security;#endif +#ifdef CONFIG_INTEGRITY +void *i_integrity; +#endif Sorry, but as said before bloating the inode for this is not an option. Please use something like the MRU approach I suggested in the last review round.
Sorry, in that thread I thought we were ok, as Serge made the points that the bloat would only affect Integrity compiled kernels, that no one would press for making Integrity default (not only because of the bloat, but even more so because of the performance impact of hashing all the files), and that having LIM do MRU would be a big hit, as LIM allocates i_integrity for all inodes, and references it on all inode_permission, bprm and mmap calls.
If we have to, we have to, but we certainly would prefer not to.
thanks
dave
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
Quoted 39 lines · david safford
Quoted 22 lines · Christoph Hellwig
Quoted 22 lines
int
vfs_permission(struct nameidata *nd, int mask){fs/namei.c +11
-2-return inode_permission (nd->path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (nd->path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (NULL , &nd->path, + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC )); }/** @@ -306,7 +314,14 @@ int vfs_permission(struct nameidata *nd, int mask)*/ int file_permission (struct file *file,int mask) { -return inode_permission (file->f_path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (file->f_path.dentry->d_inode, mask);Quoted 8 lines
fs/namei.c int vfs_permission(struct nameidata *nd, int mask) · line 324
Quoted 5 lines
fs/namei.c +5
-0+if (retval) +return retval; +return integrity_inode_permission (file,NULL , + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC ));Please don't add anything here as these two wrappers will go away. Please only make decisions based on what you get in
inode_permission().Hmm... As Mimi mentioned in the last review, we really need access to a path, which is not available in
inode_permission. (Note the path is not used to make any integrity decision, but is recorded along with the measurement to help with the integrity analysis by a third party verifier.) Yes, there are other callers without path information, but getting a path here covers the bulk of the measurements.
Quoted 2 lines
Is there some other alternative, other than this, or passing the dentry into
inode_permission, which was also rejected?
Whatever happened to the patch Mimi had floated to use the audit subsystem to output a pathname? I thought that was pretty neat, and it made particularly clear the the pathname was purely informational.
-serge
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
Quoted 43 lines · Serge E. Hallyn
Quoted 39 lines · david safford
Quoted 22 lines · Christoph Hellwig
Quoted 22 lines
int
vfs_permission(struct nameidata *nd, int mask){fs/namei.c +11
-2-return inode_permission (nd->path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (nd->path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (NULL , &nd->path, + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC )); }/** @@ -306,7 +314,14 @@ int vfs_permission(struct nameidata *nd, int mask)*/ int file_permission (struct file *file,int mask) { -return inode_permission (file->f_path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (file->f_path.dentry->d_inode, mask);Quoted 8 lines
fs/namei.c int vfs_permission(struct nameidata *nd, int mask) · line 324
Quoted 5 lines
fs/namei.c +5
-0+if (retval) +return retval; +return integrity_inode_permission (file,NULL , + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC ));Please don't add anything here as these two wrappers will go away. Please only make decisions based on what you get in
inode_permission().Hmm... As Mimi mentioned in the last review, we really need access to a path, which is not available in
inode_permission. (Note the path is not used to make any integrity decision, but is recorded along with the measurement to help with the integrity analysis by a third party verifier.) Yes, there are other callers without path information, but getting a path here covers the bulk of the measurements.Quoted 2 lines
Is there some other alternative, other than this, or passing the dentry into
inode_permission, which was also rejected?
Quoted 6 lines
Whatever happened to the patch Mimi had floated to use the audit subsystem to output a pathname? I thought that was pretty neat, and it made particularly clear the the pathname was purely informational.
-serge
I'll double check with Mimi, but my recollection is that using the audit pathnames was nice, in that it returned a full path as a hint, not just a dentry filename, but that the audit system often did not have a path yet, so both the dentry name and the audit path were desirable.
dave
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
In reply to david saffordQuoted 20 lines · david safford
Quoted 18 lines · Christoph Hellwig
Quoted 8 lines
}
/*
include/linux/fs.h +0
-0include/linux/fs.h struct inode { · line 688
Quoted 6 lines
include/linux/fs.h +3
-0@@ -683,6 +683,9 @@ struct inode {#ifdef CONFIG_SECURITY void *i_security;#endif +#ifdef CONFIG_INTEGRITY +void *i_integrity; +#endif Sorry, but as said before bloating the inode for this is not an option. Please use something like the MRU approach I suggested in the last review round.
Quoted 7 lines
Sorry, in that thread I thought we were ok, as Serge made the points that the bloat would only affect Integrity compiled kernels, that no one would press for making Integrity default (not only because of the bloat, but even more so because of the performance impact of hashing all the files), and that having LIM do MRU would be a big hit, as LIM allocates
i_integrityfor all inodes, and references it on allinode_permission, bprm and mmap calls.
Yes I have to say that in this case, where every inode will have the field in use, using MRU doesn't seem to make sense. It's the ideal case for putting it straight in the inode.
But I hear Mimi is trying it out, so she can report about any resulting implementation and performance problems.
Quoted 4 lines
If we have to, we have to, but we certainly would prefer not to.
thanks
dave
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
In reply to Christoph HellwigQuoted 13 lines · Christoph Hellwig
Quoted 13 lines
int
vfs_permission(struct nameidata *nd, int mask){fs/namei.c +8
-1-return inode_permission (nd->path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (nd->path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (NULL , &nd->path, + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC )); }
Quoted 16 lines
Quoted 4 lines
/**
fs/namei.c +0
-0@@ -306,7 +314,14 @@ int vfs_permission(struct nameidata *nd, int mask)*/ int file_permission (struct file *file,int mask)fs/namei.c int vfs_permission(struct nameidata *nd, int mask) · line 324
Quoted 10 lines
fs/namei.c +8
-1{ -return inode_permission (file->f_path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (file->f_path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (file,NULL , + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC ));Please don't add anything here as these two wrappers will go away.
Ok.
Quoted 1 line
Please only make decisions based on what you get in
inode_permission().
Is there any way to read a file, in order to calculate a hash, based just on an inode and a mask? As far as I'm aware, either a file, or a dentry and vfsmount structures, are needed. Previously, only the dentry, not the vfsmount, was required, which is accessible from the inode.
Without access to the vfsmount in inode_permission(), as vfs_permission() is going away, the only option I see is to move the integrity_inode_permission() call up a level to may_open(), after the call to vfs_permission(). Would this be acceptable? (And change the hook name to integrity_may_open.)
Mimi
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
In reply to Christoph HellwigQuoted 8 lines · Christoph Hellwig
Quoted 8 lines
/*
include/linux/fs.h +0
-0@@ -683,6 +683,9 @@ struct inode {#ifdef CONFIG_SECURITY void *i_security;
Quoted 8 lines
include/linux/fs.h struct inode { · line 688
Quoted 4 lines
include/linux/fs.h +3
-0#endif +#ifdef CONFIG_INTEGRITY +void *i_integrity; +#endif Sorry, but as said before bloating the inode for this is not an option. Please use something like the MRU approach I suggested in the last review round.
Hi Christoph, Mimi is looking into uinsg a tree but is still trying to get the locking right. So in the meantime I just have to ask again - for something which will always be either compiled out, or filled in for every inode, why have the overhead of having an external cache? Either the i_integrity won't be compiled in, or you'll have to go through the external cache for every inode operation anyway. It doesn't make sense to me... Is there a case I'm missing that risks getting hard-hit here (performance-wise), or is this mainly a style thing?
thanks,
-serge
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
In reply to Christoph HellwigQuoted 5 lines · Christoph Hellwig
Quoted 5 lines
include/linux/fs.h +0
-0@@ -683,6 +683,9 @@ struct inode {#ifdef CONFIG_SECURITY void *i_security;
Quoted 8 lines
include/linux/fs.h struct inode { · line 688
Quoted 4 lines
include/linux/fs.h +3
-0#endif +#ifdef CONFIG_INTEGRITY +void *i_integrity; +#endif Sorry, but as said before bloating the inode for this is not an option. Please use something like the MRU approach I suggested in the last review round.
Why don't we just have a 'void *i_lots_of_bloat field', and let the security folks stick whatever they want in it? They can trade their i_security space for a new one. I know we want to conceptually separate security from integrity, so let's separate it:
struct i_bloat_inodes {
#ifdef CONFIG_SECURITY void *i_security; #endif #ifdef CONFIG_INTEGRITY void *i_integrity;
#endif
};
By the way, if there's no TPM hardware, why would I want i_integrity anyway?
-- Dave
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
Quoted 14 lines · Dave Hansen
Quoted 5 lines · Christoph Hellwig
Quoted 5 lines
include/linux/fs.h +0
-0@@ -683,6 +683,9 @@ struct inode {#ifdef CONFIG_SECURITY void *i_security;Quoted 8 lines
include/linux/fs.h struct inode { · line 688
Quoted 4 lines
include/linux/fs.h +3
-0#endif +#ifdef CONFIG_INTEGRITY +void *i_integrity; +#endif Sorry, but as said before bloating the inode for this is not an option. Please use something like the MRU approach I suggested in the last review round.
I am working on using a radix tree to store the i_integrity information, as Christoph suggested. Initially the measurements were awful, but after fixing the locking and removing an unnecessary sychronize_rcu, I'm not seeing a major performance hit.
Quoted 5 lines
Why don't we just have a 'void
*i_lots_of_bloatfield', and let the security folks stick whatever they want in it? They can trade theiri_securityspace for a new one. I know we want to conceptually separate security from integrity, so let's separate it:
Quoted 8 lines
struct
i_bloat_inodes{#ifdef CONFIG_SECURITY void *i_security; #endif #ifdef CONFIG_INTEGRITY void *i_integrity;#endif
};
I'm not sure that the LSM people would be too happy. If using the radix tree does not pan out, then we will have to look into this option.
Quoted 4 lines
By the way, if there's no TPM hardware, why would I want
i_integrityanyway?-- Dave
The integrity framework is for collecting, appraising, and storing integrity information. Integrity measurements today are mainly file measurements, but the framework allows for other types of integrity measurements. Some types of integrity measurements, might only require collecting and appraising, but not storing, so a TPM would not be required.
Mimi
Serge E. Hallyn
maintainerRe: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
In reply to Mimi ZoharQuoted 151 lines · Mimi Zohar
Concern was raised on the lkml mailing list, about adding
i_integrityto the inode structure. This patch adds a comment clarifying thati_integrityis only included in the inode if INTEGRITY is configured.This version resolves the merge issues resulting from the removal of the nameidata parameter to
inode_permission().
- Moved theintegrity_inode_permission()call frominode_permission()tovfs_inode_permission()andfile_inode_permission().
- Replaced the inode and nameidata parameters with file and path parameters tointegrity_inode_permission().This patch is a redesign of the integrity framework, which address a number of issues, including
- generalizing the measurement API beyond just inode measurements.
- separation of the measurement into distinct collection, appraisal, and commitment phases, for greater flexibility.Extended Verification Module(EVM) and the Integrity Measurement Architecture(IMA) were originally implemented as an LSM module. Based on discussions on the LSM mailing list, a decision was made that the LSM hooks should only be used to enforce mandatory access control decisions and a new set of hooks should be defined specifically for integrity.
EVM/IMA was limited to verifying and measuring a file's (i.e. an inode) integrity and the metadata associated with it. Current research is looking into other types of integrity measurements. (i.e. "Linux kernel integrity measurement using contextual inspection", by Peter A. Loscocco, Perry W. Wilson, J. Aaron Pendergrass, C. Durward McDonell,
http://doi.acm.org/10.1145/1314354.1314362). As a result, a requirement of the new integrity framework is support for different types of integrity measurements.This patch provides an integrity framework(api and hooks) and placement of the integrity hooks in the appropriate places in the fs directory. Collecting, appraising, and storing of file and other types of integrity data is supported. Multiple integrity templates, which implement the integrity API, may register themselves. For now, only a single integrity provider can register itself for the integrity hooks. (Support for multiple providers registering themselves for the integrity hooks would require some form of stacking.)
The six integrity hooks are:
inode_permission,inode_alloc_integrity,inode_free_integrity,bprm_check_integrity,file_free_integrity,file_mmapThe five integrity API calls provided are:
integrity_must_measure,integrity_collect_measurement,integrity_appraise_measurement,integrity_store_measurement, andintegrity_display_template.The type of integrity data being collected, appraised, stored, or displayed is template dependent.
(Details on the calls and their exact arguments are in
linux/integrity.h, included in the patch.)Signed-off-by Mimi Zohar <[email protected]>---
Documentation/kernel-parameters.txt +6
-0@@ -44,6 +44,7 @@ parameter is applicable: FB The frame buffer device is enabled. HW Appropriate hardware is enabled. IA-64 IA-64 architecture is enabled. + INTEGRITY Integrity support is enabled. IOSCHED More than one I/O scheduler is enabled. IP_PNP IP DHCP, BOOTP, or RARP is enabled. ISAPNP ISA PnP code is enabled.@@ -874,6 +875,11 @@ and is between 256 and 4096 characters. It is defined in the file inport.irq= [HW] Inport (ATI XL and Microsoft) busmouse driver Format: <irq> + integrity_audit= [INTEGRITY] + Format: { "0" | "1" } + 0 -- disable integrity auditing messages. + 1 -- enable integrity auditing messages. (Default) + inttest= [IA64] iommu= [x86]fs/exec.c +4
-0@@ -45,6 +45,7 @@#include <linux/proc_fs.h> #include <linux/mount.h> #include <linux/security.h> +#include <linux/integrity.h> #include <linux/syscalls.h> #include <linux/tsacct_kern.h> #include <linux/cn_proc.h> @@ -1204,6 +1205,9 @@ int search_binary_handler(struct linux_binprm *bprm,struct pt_regs *regs) retval =security_bprm_check (bprm);if (retval)return retval; + retval =integrity_bprm_check (bprm); +if (retval) +return retval;/* kernel module loader fixup */ /* so we don't try to load run modprobe in kernel space. */ fs/file_table.c +3
-0@@ -13,6 +13,7 @@#include <linux/module.h> #include <linux/fs.h> #include <linux/security.h> +#include <linux/integrity.h> #include <linux/eventpoll.h> #include <linux/rcupdate.h> #include <linux/mount.h> @@ -272,6 +273,7 @@ void __fput(struct file *file)if (file->f_op && file->f_op->release) file->f_op->release (inode, file);security_file_free (file); +integrity_file_free (file);if (unlikely (S_ISCHR (inode->i_mode) && inode->i_cdev !=NULL ))cdev_put (inode->i_cdev);fops_put (file->f_op);@@ -343,6 +345,7 @@ void put_filp(struct file *file) {if (atomic_long_dec_and_test (&file->f_count)) {security_file_free (file); +integrity_file_free (file);file_kill (file);file_free (file); }fs/inode.c +1
-2@@ -17,6 +17,7 @@#include <linux/hash.h> #include <linux/swap.h> #include <linux/security.h> +#include <linux/integrity.h> #include <linux/pagemap.h> #include <linux/cdev.h> #include <linux/bootmem.h> @@ -143,13 +144,12 @@ static struct inode *alloc_inode(struct super_block *sb) inode->i_cdev =NULL ; inode->i_rdev =0 ; inode->dirtied_when =0 ; -if (security_inode_alloc (inode)) { -if (inode->i_sb->s_op->destroy_inode)
fs/inode.c static struct inode *alloc_inode(struct super_block *sb) · line 151
Quoted 10 lines
fs/inode.c +5
-5- inode->i_sb->s_op->destroy_inode (inode); - else - kmem_cache_free(inode_cachep, (inode)); -return NULL ; - } +if (security_inode_alloc (inode)) + goto out_free_inode; + +/* allocate, attach and initialize an i_integrity */ +if (integrity_inode_alloc (inode))
Don't you need to do a security_inode_free(inode) if the integrity_inode_alloc() fails?
Quoted 139 lines
fs/inode.c +9
-0+ goto out_free_inode;spin_lock_init (&inode->i_lock);lockdep_set_class (&inode->i_lock, &sb->s_type->i_lock_key);@@ -185,12 +185,20 @@ static struct inode *alloc_inode(struct super_block *sb) inode->i_mapping = mapping; }return inode; + +out_free_inode: +if (inode->i_sb->s_op->destroy_inode) + inode->i_sb->s_op->destroy_inode (inode); +else +kmem_cache_free (inode_cachep, (inode)); +return NULL ; }void destroy_inode (struct inode *inode) {BUG_ON (inode_has_buffers (inode));security_inode_free (inode); +integrity_inode_free (inode);if (inode->i_sb->s_op->destroy_inode) inode->i_sb->s_op->destroy_inode (inode);else fs/namei.c +17
-2@@ -24,6 +24,7 @@#include <linux/fsnotify.h> #include <linux/personality.h> #include <linux/security.h> +#include <linux/integrity.h> #include <linux/syscalls.h> #include <linux/mount.h> #include <linux/audit.h> @@ -289,7 +290,14 @@ int inode_permission(struct inode *inode, int mask)*/ int vfs_permission (struct nameidata *nd,int mask) { -return inode_permission (nd->path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (nd->path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (NULL , &nd->path, + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC )); }/** @@ -306,7 +314,14 @@ int vfs_permission(struct nameidata *nd, int mask)*/ int file_permission (struct file *file,int mask) { -return inode_permission (file->f_path.dentry->d_inode, mask); +int retval; + + retval =inode_permission (file->f_path.dentry->d_inode, mask); +if (retval) +return retval; +return integrity_inode_permission (file,NULL , + mask & (MAY_READ |MAY_WRITE | +MAY_EXEC )); }/* include/linux/audit.h +8
-0@@ -123,6 +123,11 @@#define AUDIT_LAST_KERN_ANOM_MSG 1799#define AUDIT_ANOM_PROMISCUOUS 1700/* Device changed promiscuous mode */ #define AUDIT_ANOM_ABEND 1701/* Process ended abnormally */ +#define AUDIT_INTEGRITY_DATA 1800/* Data integrity verification */ +#define AUDIT_INTEGRITY_METADATA 1801/* Metadata integrity verification */ +#define AUDIT_INTEGRITY_STATUS 1802/* Integrity enable status */ +#define AUDIT_INTEGRITY_HASH 1803/* Integrity HASH type */ +#define AUDIT_INTEGRITY_PCR 1804/* PCR invalidation msgs */ #define AUDIT_KERNEL 2000/* Asynchronous audit record. NOT A REQUEST. */ @@ -440,6 +445,8 @@ extern int audit_set_loginuid(struct task_struct *task, uid_t loginuid);#define audit_get_loginuid (t) ((t)->loginuid)#define audit_get_sessionid (t) ((t)->sessionid)extern void audit_log_task_context (struct audit_buffer *ab); +extern void audit_log_inode_context (struct audit_buffer *ab, +struct inode *inode);extern int __audit_ipc_obj (struct kern_ipc_perm *ipcp);extern int __audit_ipc_set_perm (unsigned long qbytes,uid_t uid,gid_t gid,mode_t mode);extern int audit_bprm (struct linux_binprm *bprm);@@ -520,6 +527,7 @@ extern int audit_signals;#define audit_get_loginuid (t) (-1)#define audit_get_sessionid (t) (-1)#define audit_log_task_context (b) do { ; } while (0) +#define audit_log_inode_context (b, a) do { } while (0)#define audit_ipc_obj (i) ({ 0; })#define audit_ipc_set_perm (q,u,g,m) ({ 0; })#define audit_bprm (p) ({ 0; })include/linux/fs.h +3
-0@@ -683,6 +683,9 @@ struct inode {#ifdef CONFIG_SECURITY void *i_security;#endif +#ifdef CONFIG_INTEGRITY +void *i_integrity; +#endif void *i_private;/* fs or device private pointer */ };include/linux/integrity.h new file +17
-0@@ -0,0 +1,182 @@ +/* +* Copyright (C) 2005,2006,2007,2008 IBM Corporation +* Author: Mimi Zohar <[email protected]> +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License as published by +* the Free Software Foundation, version 2 of the License. +*/ + +#ifndef _LINUX_INTEGRITY_H +#define _LINUX_INTEGRITY_H + +#include <linux/fs.h> +#include <linux/audit.h> + +#ifdef CONFIG_INTEGRITY +void integrity_audit_msg(int audit_msgno, struct inode *inode,
include/linux/integrity.h line 27
Quoted 10 lines
include/linux/integrity.h new file +10
-0+ const unsigned char *fname, char *op, + char *cause, int result); + +/* +* Integrity API calls: +* +* @collect_measurement: +* Collect template specific measurement data. +* @data contains template specific data used for collecting the +* measurement.
Apparently it must be safe to call this (and all these hooks) under rcu_read_lock. That needs to be mentioned in these descriptions.
Quoted 209 lines
include/linux/integrity.h new file +155
-0+* Return 0 if operation was successful. +* +* @appraise_measurement: +* Appraise the integrity of the template specific measurement data. +* @data contains template specific data used for appraising the +* measurement. +* Return 0 if operation was successful. +* +* @store_measurement: +* Store the template specific data. +* @data contains template specific data used for storing the +* measurement. +* +* @must_measure: +* Measurement decision based on an integrity policy. +* @data contains template specific data used for making policy +* decision. +* Return 0 if operation was successful. +* +* @display_template: +* Display template specific data. +* +*/ + +enum integrity_show_type {INTEGRITY_SHOW_BINARY ,INTEGRITY_SHOW_ASCII }; + +struct template_operations { +int (*collect_measurement)(void *); +int (*appraise_measurement)(void *); +void (*store_measurement)(void *); +int (*must_measure)(void *); +void (*display_template)(struct seq_file *m,void *, +enum integrity_show_type ); +}; +extern int integrity_register_template (const char *template_name, +const struct template_operations *ops); +extern int integrity_unregister_template (const char *template_name); +extern int integrity_find_template (const char *, +const struct template_operations **ops); + +/* +* Integrity hooks: +* +* @bprm_check_integrity: +* This hook mediates the point when a search for a binary handler will +* begin. At this point, the OS protects against an executable file, +* already open for write, from being executed; and an executable file +* already open for execute, from being modified. So we can be certain +* that any measurements(collect, appraise, store) done here are of +* the file being executed. +* @bprm contains the linux_binprm structure. +* Return 0 if the hook is successful and permission is granted. +* +* @inode_alloc_integrity: +* Allocate and attach an integrity structure to @inode->i_integrity. The +* i_integrity field is initialized to NULL when the inode structure is +* allocated. +* @inode contains the inode structure. +* Return 0 if operation was successful. +* +* @inode_free_integrity: +* @inode contains the inode structure. +* Deallocate the inode integrity structure and set @inode->i_integrity to +* NULL. +* +* @inode_permission: +* This hook is called by the existing Linux vfs_permission and +* file_permission functions, as a file is opened. At this point, +* measurements(collect, appraise, store) of files open for read +* can be made. +* @file contains the file structure of the file being opened(may be NULL). +* @path contains the path structure (may be NULL). +* @mask contains the permission mask. +* Return 0 if the hook is successful and permission is granted. +* +* @file_free_integrity: +* Update the integrity xattr value as necessary. +* @file contains the file structure being closed. +* +* @file_mmap : +* Measurements(collect, appraise, store) of files mmaped for EXEC +* can be made. +* @file contains the file structure of the file to map (may be NULL). +* @prot contains the protection that will be applied by the kernel. +* Return 0 if the hook is successful and permission is granted. +*/ + +enum lim_hooks {INODE_PERMISSION =1 ,FILE_MMAP ,BPRM_CHECK }; + +struct integrity_operations { +int (*bprm_check_integrity) (struct linux_binprm *bprm); +int (*inode_alloc_integrity) (struct inode *inode); +void (*inode_free_integrity) (struct inode *inode); +int (*inode_permission) (struct file *file,struct path *path, +int mask); +void (*file_free_integrity) (struct file *file); +int (*file_mmap) (struct file *file,unsigned long prot); +}; +extern int register_integrity (const struct integrity_operations *ops); +extern int unregister_integrity (const struct integrity_operations *ops); + +/* global variables */ +extern const struct integrity_operations *integrity_ops; + + +int integrity_collect_measurement (const char *template_name,void *data); +int integrity_appraise_measurement (const char *template_name,void *data); +int integrity_must_measure (const char *template_name,void *data); +int integrity_store_measurement (const char *template_name,void *data); + +int integrity_bprm_check (struct linux_binprm *bprm); +int integrity_inode_alloc (struct inode *inode); +void integrity_inode_free (struct inode *inode); +int integrity_inode_permission (struct file *file,struct path *path,int mask); +void integrity_file_free (struct file *file); +int integrity_file_mmap (struct file *file,unsigned long prot); +#else + +static inline int integrity_bprm_check (struct linux_binprm *bprm) +{ +return 0 ; +} + +static inline int integrity_inode_alloc (struct inode *inode) +{ +return 0 ; +} + +static inline void integrity_inode_free (struct inode *inode) +{ +return ; +} + +static inline int integrity_inode_permission (struct file *file, +struct path *path,int mask); +{ +return 0 ; +} + +static inline int integrity_file_permission (struct file *file,int mask) +{ +return 0 ; +} + +static inline void integrity_file_free (struct file *file) +{ +return ; +} + +static inline int integrity_file_mmap (struct file *file,unsigned long prot) +{ +return 0 ; +} +#endif +#endif mm/mmap.c +4
-0@@ -20,6 +20,7 @@#include <linux/fs.h> #include <linux/personality.h> #include <linux/security.h> +#include <linux/integrity.h> #include <linux/hugetlb.h> #include <linux/profile.h> #include <linux/module.h> @@ -1050,6 +1051,9 @@ unsigned long do_mmap_pgoff(struct file * file, unsigned long addr, error =security_file_mmap (file, reqprot, prot, flags, addr,0 );if (error)return error; + error =integrity_file_mmap (file, prot); +if (error) +return error;return mmap_region (file, addr, len, flags, vm_flags, pgoff, accountable);security/Kconfig +2
-0@@ -4,6 +4,8 @@ menu "Security options" +source security/integrity/Kconfig + config KEYS bool "Enable access key retention support" helpsecurity/Makefile +4
-0@@ -17,3 +17,7 @@ obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o obj-$(CONFIG_SECURITY_SMACK) += smack/built-in.o obj-$(CONFIG_SECURITY_ROOTPLUG) += root_plug.o obj-$(CONFIG_CGROUP_DEVICE) += device_cgroup.o + +# Object integrity file lists +subdir-$(CONFIG_INTEGRITY) += integrity +obj-$(CONFIG_INTEGRITY) += integrity/built-in.osecurity/integrity/Kconfig new file +1
-0@@ -0,0 +1,24 @@ +#
security/integrity/Kconfig line 11
Quoted 10 lines
security/integrity/Kconfig new file +10
-0+# Integrity configuration +# + +menu "Integrity options" + +config INTEGRITY + bool "Enable different integrity models" + help + This allows you to choose different integrity modules to be + configured into your kernel.
Another sentence here to give a random person an idea of whether they
want this or nog?
security/integrity/Kconfig line 23
Quoted 12 lines
security/integrity/Kconfig new file +12
-0+ + If you are unsure how to answer this question, answer N. + +config INTEGRITY_AUDIT + bool "Integrity audit boot parameter" + depends on INTEGRITY + default y + help + This option adds a kernel parameter 'integrity_audit', which + allows integrity auditing to be disabled at boot. If this + option is selected, integrity auditing can be disabled with + 'integrity_audit=0' on the kernel command line.
Ok but what is 'integrity auditing?' And does disabling it mean that hooks are enforced but there's just no audit, or are integrity modules which can do more (i.e. refuse access or whatever) also stopped?
I guess the word 'audit' is confusing to me in this context.
Quoted 102 lines
security/integrity/Kconfig new file +1
-0+endmenusecurity/integrity/Makefile new file +6
-0@@ -0,0 +1,6 @@ +# +# Makefile for the kernel integrity code +# + +# Object file lists +obj-$(CONFIG_INTEGRITY) += integrity.o integrity_audit.osecurity/integrity/integrity.c new file +83
-0@@ -0,0 +1,308 @@ +/* +* Copyright (C) 2006,2007,2008 IBM Corporation +* Author: Mimi Zohar <[email protected]> +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License as published by +* the Free Software Foundation, version 2 of the License. +* +* File: integrity.c +* register integrity subsystem +* register integrity template +*/ + +#include <linux/module.h> +#include <linux/init.h> +#include <linux/kernel.h> +#include <linux/sched.h> +#include <linux/integrity.h> + +const struct integrity_operations *integrity_ops; +EXPORT_SYMBOL (integrity_ops); + +#define TEMPLATE_NAME_LEN_MAX 12 +struct template_list_entry { +struct list_head template; +char template_name[TEMPLATE_NAME_LEN_MAX +1 ]; +const struct template_operations *template_ops; +}; +static LIST_HEAD (integrity_templates); +static DEFINE_MUTEX (integrity_templates_mutex); + +/** +* register_integrity - registers an integrity framework with the kernel +* @ops: a pointer to the struct security_options that is to be registered +* +* Perhaps in the future integrity module stacking will be necessary, but +* for the time being, this function permits only one integrity module to +* register itself with the kernel integrity subsystem. +* +* If another integrity module is already registered, an error code is +* returned. On success 0 is returned. +*/ +int register_integrity (const struct integrity_operations *ops) +{ +if (integrity_ops !=NULL ) +return -EAGAIN ; + integrity_ops = ops; +return 0 ; +} + +EXPORT_SYMBOL_GPL (register_integrity); + +/** +* unregister_integrity - unregisters an integrity framework from the kernel +* @ops: a pointer to the struct security_options that is to be registered +* +* Returns 0 on success, -EINVAL on failure. +*/ +int unregister_integrity (const struct integrity_operations *ops) +{ +if (ops != integrity_ops) +return -EINVAL ; + + integrity_ops =NULL ; +return 0 ; +} + +EXPORT_SYMBOL_GPL (unregister_integrity); + +/** +* integrity_register_template - registers an integrity template with the kernel +* @template_name: a pointer to a string containing the template name. +* @template_ops: a pointer to the template functions +* +* Register a set of functions to collect, appraise, store, and display +* a template measurement, and a means to decide whether to do them. +* Unlike integrity modules, any number of templates may be registered. +* +* Returns 0 on success, an error code on failure. +*/ +int integrity_register_template (const char *template_name, +const struct template_operations *template_ops) +{
security/integrity/integrity.c line 93
Quoted 10 lines
security/integrity/integrity.c new file +10
-0+int template_len; +struct template_list_entry *entry; + + entry =kzalloc (sizeof (*entry),GFP_KERNEL ); +if (!entry) +return -ENOMEM ; +INIT_LIST_HEAD (&entry->template); + + template_len =strlen (template_name); +if (template_len >TEMPLATE_NAME_LEN_MAX )
leak?
Quoted 37 lines
security/integrity/integrity.c new file +37
-0+return -EINVAL ; +strcpy (entry->template_name, template_name); + entry->template_ops = template_ops; + +mutex_lock (&integrity_templates_mutex); +list_add_rcu (&entry->template, &integrity_templates); +mutex_unlock (&integrity_templates_mutex); +synchronize_rcu (); + +return 0 ; +} + +EXPORT_SYMBOL_GPL (integrity_register_template); + +/** +* integrity_unregister_template: unregister a template +* @template_name: a pointer to a string containing the template name. +* +* Returns 0 on success, -EINVAL on failure. +*/ +int integrity_unregister_template (const char *template_name) +{ +struct template_list_entry *entry; + +mutex_lock (&integrity_templates_mutex); +list_for_each_entry (entry, &integrity_templates, template) { +if (strncmp (entry->template_name, template_name, +strlen (entry->template_name)) ==0 ) { +list_del_rcu (&entry->template); +mutex_unlock (&integrity_templates_mutex); +synchronize_rcu (); +kfree (entry); +return 0 ; + } + } +mutex_unlock (&integrity_templates_mutex); +return -EINVAL ;
security/integrity/integrity.c line 140
Quoted 10 lines
security/integrity/integrity.c new file +10
-0+} + +EXPORT_SYMBOL_GPL (integrity_unregister_template); + +/** +* integrity_find_template - search the integrity_templates list +* @template_name: a pointer to a string containing the template name. +* @template_ops: a pointer to the template functions +* +* Called with an rcu_read_lock
"and the contents must be used or copied before the rcu_read_lock is dropped."
Quoted 261 lines
security/integrity/integrity.c new file +168
-0+* Returns 0 on success, -EINVAL on failure. +*/ +int integrity_find_template (const char *template_name, +const struct template_operations **template_ops) +{ +struct template_list_entry *entry; + +list_for_each_entry_rcu (entry, &integrity_templates, template) { +if (strncmp (entry->template_name, template_name, +strlen (entry->template_name)) ==0 ) { + *template_ops = entry->template_ops; +return 0 ; + } + } +return -EINVAL ; +} + +EXPORT_SYMBOL_GPL (integrity_find_template); + +/* Start of the integrity API calls */ + +/** +* integrity_collect_measurement - collect template specific measurement +* @template_name: a pointer to a string containing the template name. +* @data: pointer to template specific data +* +* Returns 0 on success, an error code on failure. +*/ +int integrity_collect_measurement (const char *template_name,void *data) +{ +const struct template_operations *template_ops; +int rc; + +rcu_read_lock (); + rc =integrity_find_template (template_name, &template_ops); +if (rc ==0 ) + rc = template_ops->collect_measurement (data); +rcu_read_unlock (); +return rc; +} + +EXPORT_SYMBOL_GPL (integrity_collect_measurement); + +/** +* integrity_appraise_measurement - appraise template specific measurement +* @template_name: a pointer to a string containing the template name. +* @data: pointer to template specific data +* +* Returns 0 on success, an error code on failure +*/ +int integrity_appraise_measurement (const char *template_name,void *data) +{ +const struct template_operations *template_ops; +int rc; + +rcu_read_lock (); + rc =integrity_find_template (template_name, &template_ops); +if (rc ==0 ) + rc = template_ops->appraise_measurement (data); +rcu_read_unlock (); +return rc; +} + +EXPORT_SYMBOL_GPL (integrity_appraise_measurement); + +/** +* integrity_store_measurement - store template specific measurement +* @template_name: a pointer to a string containing the template name. +* @data: pointer to template specific data +* +* Store template specific integrity measurement. +*/ +int integrity_store_measurement (const char *template_name,void *data) +{ +const struct template_operations *template_ops; +int rc; + +rcu_read_lock (); + rc =integrity_find_template (template_name, &template_ops); +if (rc ==0 ) + template_ops->store_measurement (data); +rcu_read_unlock (); +return rc; +} + +EXPORT_SYMBOL_GPL (integrity_store_measurement); + +/** +* integrity_must_measure - measure decision based on template policy +* @template_name: a pointer to a string containing the template name. +* @data: pointer to template specific data +* +* Returns 0 on success, an error code on failure. +*/ +int integrity_must_measure (const char *template_name,void *data) +{ +const struct template_operations *template_ops; +int rc; + +rcu_read_lock (); + rc =integrity_find_template (template_name, &template_ops); +if (rc ==0 ) + rc = template_ops->must_measure (data); +rcu_read_unlock (); +return rc; +} + +EXPORT_SYMBOL_GPL (integrity_must_measure); + +/* Start of the integrity Hooks */ + +/* Hook used to measure executable file integrity. */ +int integrity_bprm_check (struct linux_binprm *bprm) +{ +int rc =0 ; + +if (integrity_ops && integrity_ops->bprm_check_integrity) + rc = integrity_ops->bprm_check_integrity (bprm); +return rc; +} + +/* Allocate, attach and initialize an inode's i_integrity, +* if INTEGRITY is configured. +*/ +int integrity_inode_alloc (struct inode *inode) +{ +int rc =0 ; + +if (integrity_ops && integrity_ops->inode_alloc_integrity) + rc = integrity_ops->inode_alloc_integrity (inode); +return rc; +} + +/* Hook used to free an inode's i_integrity structure. */ +void integrity_inode_free (struct inode *inode) +{ +if (integrity_ops && integrity_ops->inode_free_integrity) + integrity_ops->inode_free_integrity (inode); +} + +/* Hook used to measure a file's integrity. */ +int integrity_inode_permission (struct file *file,struct path *path,int mask) +{ +int rc =0 ; + +if (integrity_ops && integrity_ops->inode_permission) + rc = integrity_ops->inode_permission (file, path, mask); +return rc; +} + +/* Hook used to update i_integrity data and integrity xattr values +* as necessary. +*/ +void integrity_file_free (struct file *file) +{ +if (integrity_ops && integrity_ops->file_free_integrity) + integrity_ops->file_free_integrity (file); +} + +/* Hook used to measure integrity of an mmapped file */ +int integrity_file_mmap (struct file *file,unsigned long prot) +{ +int rc =0 ; + +if (integrity_ops && integrity_ops->file_mmap) + rc = integrity_ops->file_mmap (file, prot); +return rc; +}security/integrity/integrity_audit.c new file +79
-0@@ -0,0 +1,79 @@ +/* +* Copyright (C) 2008 IBM Corporation +* Author: Mimi Zohar <[email protected]> +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License as published by +* the Free Software Foundation, version 2 of the License. +* +* File: integrity_audit.c +* Audit calls for the integrity subsystem +*/ + +#include <linux/audit.h> +#include <linux/fs.h> +#include <linux/integrity.h> + +static int integrity_audit =1 ; + +#ifdef CONFIG_INTEGRITY_AUDIT +static int __init integrity_audit_setup (char *str) +{ +ulong audit; +int rc; +char *op; + + rc =strict_strtoul (str,10 , &audit); +if (rc <0 || audit >1 ) +printk (KERN_INFO "integrity: invalid integrity_audit value\n" ); +else + integrity_audit = audit; + + op = integrity_audit ?"integrity_audit_enabled" : +"integrity_audit_not_enabled" ; +integrity_audit_msg (AUDIT_INTEGRITY_STATUS ,NULL ,NULL ,NULL , op,0 ); +return 1 ; +} + +__setup ("integrity_audit=" , integrity_audit_setup); +#endif + +void integrity_audit_msg (int audit_msgno,struct inode *inode, +const unsigned char *fname,char *op, +char *cause,int result) +{ +struct audit_buffer *ab; + +if (!integrity_audit && result ==1 ) +return ; + + ab =audit_log_start (current->audit_context,GFP_KERNEL , audit_msgno); +audit_log_format (ab,"integrity: pid=%d uid=%u auid=%u" , + current->pid, current->uid, +audit_get_loginuid (current)); +audit_log_task_context (ab); +switch (audit_msgno) { +case AUDIT_INTEGRITY_DATA : +case AUDIT_INTEGRITY_METADATA : +case AUDIT_INTEGRITY_PCR : +audit_log_format (ab," op=%s cause=%s" , op, cause); +break ; +case AUDIT_INTEGRITY_HASH : +audit_log_format (ab," op=%s hash=%s" , op, cause); +break ; +case AUDIT_INTEGRITY_STATUS : +default : +audit_log_format (ab," op=%s" , op); + } +audit_log_format (ab," comm=" ); +audit_log_untrustedstring (ab, current->comm); +if (fname) { +audit_log_format (ab," name=" ); +audit_log_untrustedstring (ab, fname); + } +if (inode) +audit_log_format (ab," dev=%s ino=%lu" , + inode->i_sb->s_id, inode->i_ino); +audit_log_format (ab," res=%d" , result); +audit_log_end (ab); +}Signature · 7 lines
1.5.5.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
In reply to Mimi ZoharQuoted 3 lines · Mimi Zohar
Concern was raised on the lkml mailing list, about adding
i_integrityto the inode structure. This patch adds a comment clarifying thati_integrityis only included in the inode if INTEGRITY is configured.
Mimi, it is nice that you made this a config option. That definitely helps the embedded folks and those compiling their own kernels. But, it doesn't really help those who run distros.
The distributions basically ship one kernel for everybody, and it has to have CONFIG_KITCHEN_SINK=y in order to support everyone's individual users. Although you provided a config option, in practice, this always bloats distro kernels which are the vast majority of users.
Is this even useful for filesystems like proc or sysfs? Should we bloat those inodes for a feature which might not possibly apply there?
-- Dave
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
Quoted 5 lines · Dave Hansen
Quoted 3 lines · Mimi Zohar
Concern was raised on the lkml mailing list, about adding
i_integrityto the inode structure. This patch adds a comment clarifying thati_integrityis only included in the inode if INTEGRITY is configured.
Quoted 8 lines
Mimi, it is nice that you made this a config option. That definitely helps the embedded folks and those compiling their own kernels. But, it doesn't really help those who run distros.
The distributions basically ship one kernel for everybody, and it has to have
CONFIG_KITCHEN_SINK=yin order to support everyone's individual users. Although you provided a config option, in practice, this always bloats distro kernels which are the vast majority of users.
Thank you for giving a more fuller explanation as to why extending the inode is such an issue.
Quoted 2 lines
Is this even useful for filesystems like proc or sysfs? Should we bloat those inodes for a feature which might not possibly apply there?
Currently, we're not measuring proc or sysfs files.
Mimi
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
Quoted 4 lines · Mimi Zohar
Quoted 2 lines
Is this even useful for filesystems like proc or sysfs? Should we bloat those inodes for a feature which might not possibly apply there?
Currently, we're not measuring proc or sysfs files.
So, one of the points is that this "bloats" 'struct inode' for at least these two filesystems. It has no use there, so it does not help much to stick it in a common structure that those use.
-- Dave
Re: [PATCH 2/3] integrity: Linux Integrity Module(LIM)
In reply to Dave HansenQuoted 8 lines · Dave Hansen
Quoted 3 lines · Mimi Zohar
Concern was raised on the lkml mailing list, about adding
i_integrityto the inode structure. This patch adds a comment clarifying thati_integrityis only included in the inode if INTEGRITY is configured.Mimi, it is nice that you made this a config option. That definitely helps the embedded folks and those compiling their own kernels. But, it doesn't really help those who run distros.
Ah, of course, that makes sense - thanks for the reminder. That answers my earlier stupid question.
-serge
PATCH 3/3 integrity: IMA as an integrity service provider
In reply to Mimi ZoharThis is a re-release of Integrity Measurement Architecture(IMA) as an independent Linunx Integrity Module(LIM) service provider.
This version addresses the merge issues resulting from the removal of the nameidata parameter to inode_permission().
- The parameter changes to integrity_inode_permission() are reflected here in this patch.
As a LIM integrity provider, IMA implements the new LIM must_measure(), collect_measurement(), store_measurement(), and display_template() API calls. The store_measurement() call supports two types of data, IMA (i.e. file data) and generic template data.
IMA provides hardware (TPM) based measurement and attestation for both files and other types of template measurements. As the Trusted Computing (TPM) model requires, IMA measures all files before they are accessed in any way (on the bprm_check_integrity, file_mmap and inode_permission hooks), and commits the measurements to the TPM. In addition, IMA maintains a list of these hash values, which can be used to validate the aggregate PCR value. The TPM can sign these measurements, and thus the system can prove to itself and to a third party these measurements in a way that cannot be circumvented by malicious or compromised software.
When store_measurement() is called for the IMA type of data, the file measurement and the file name hint are used to form an IMA template. IMA then calculates the IMA template measurement(hash) and submits it to the TPM chip for inclusion in one of the chip's Platform Configuration Registers (PCR).
When store_measurement() is called for generic template data, IMA calculates the measurement(hash) of the template data, and submits the template measurement to the TPM chip for inclusion in one of the chip's Platform Configuration Registers(PCR).
In order to view the contents of template data through securityfs, the template_display() function must be defined in the registered template_operations. In the case of the IMA template, the list of file names and files hashes submitted can be viewed through securityfs.
As mentioned above, IMA maintains a list of hash values of executables and other sensitive system files loaded into the run-time of the system. Our work has shown that requests for integrity appraisal and measurement need to be based on knowledge of the filesystem, requiring the system to either be labeled with integrity data or depend on the existent LSM security labels. The previous set of integrity patches modified the LSM modules to be integrity context aware, meaning that the LSM modules made integrity data/metadata appraisal and measurement API calls based on an understanding of the LSM security labels. Both of the LSM maintainers felt that the changes were too intrusive and that integrity enforcement should be made by the integrity provider, not the LSM module.
To address these concerns, Stephen Smalley suggested using the security_audit_rule_match(), renamed to security_filter_rule_match(), to define LSM specific integrity measurement policy rules, in lieu of modifying the LSM modules. In the current set of patches, the integrity API calls can be made either by IMA, based on an LSM specific integrity policy, or by an integrity context aware LSM.
--- Documentation/ABI/testing/ima_policy | 60 +++++ Documentation/kernel-parameters.txt | 5 + include/linux/ima.h | 46 ++++ security/integrity/Kconfig | 5 +- security/integrity/Makefile | 2 + security/integrity/ima/Kconfig | 48 ++++ security/integrity/ima/Makefile | 9 + security/integrity/ima/ima.h | 170 ++++++++++++ security/integrity/ima/ima_api.c | 348 +++++++++++++++++++++++++ security/integrity/ima/ima_crypto.c | 153 +++++++++++ security/integrity/ima/ima_fs.c | 473 ++++++++++++++++++++++++++++++++++ security/integrity/ima/ima_init.c | 105 ++++++++ security/integrity/ima/ima_main.c | 354 +++++++++++++++++++++++++ security/integrity/ima/ima_policy.c | 334 ++++++++++++++++++++++++ security/integrity/ima/ima_queue.c | 124 +++++++++ 15 files changed, 2233 insertions(+), 3 deletions(-) create mode 100644 Documentation/ABI/testing/ima_policy create mode 100644 include/linux/ima.h create mode 100644 security/integrity/ima/Kconfig create mode 100644 security/integrity/ima/Makefile create mode 100644 security/integrity/ima/ima.h create mode 100644 security/integrity/ima/ima_api.c create mode 100644 security/integrity/ima/ima_crypto.c create mode 100644 security/integrity/ima/ima_fs.c create mode 100644 security/integrity/ima/ima_init.c create mode 100644 security/integrity/ima/ima_main.c create mode 100644 security/integrity/ima/ima_policy.c create mode 100644 security/integrity/ima/ima_queue.c
Documentation/ABI/testing/ima_policy new file +60 -0
@@ -0,0 +1,60 @@ +What: security/ima/policy +Date: May 2008 +Contact: Mimi Zohar <[email protected]> +Description: + The Trusted Computing Group(TCG) runtime Integrity + Measurement Architecture(IMA) maintains a list of hash + values of executables and other sensitive system files + loaded into the run-time of this system. At runtime, + the policy can be constrained based on LSM specific data. + Policies are loaded into security/ima/policy by opening + the file, writing the rules one at a time and then + closing the file. The new policy takes effect after + the security/ima/policy is closed. + + rule format: action [condition ...] + + action: measure | dont_measure + condition:= base | lsm + base: [[func=] [mask=] [fsmagic=] [uid=]] + lsm: [[subj_user=] [subj_role=] [subj_type=] + [obj_user=] [obj_role=] [obj_type=]] + + base: func:= [BPRM_CHECK][FILE_MMAP][INODE_PERMISSION] + mask:= [MAY_READ] [MAY_WRITE] [MAY_APPEND] [MAY_EXEC] + fsmagic:= hex value + uid:= decimal value + lsm: are LSM specific + + default policy: + # PROC_SUPER_MAGIC + dont_measure fsmagic=0x9fa0 + # SYSFS_MAGIC + dont_measure fsmagic=0x62656572 + # DEBUGFS_MAGIC + dont_measure fsmagic=0x64626720 + # TMPFS_MAGIC + dont_measure fsmagic=0x01021994 + # SECURITYFS_MAGIC + dont_measure fsmagic=0x73636673 + # SELINUX_MAGIC + dont_measure fsmagic=0xF97CFF8C + + measure func=BPRM_CHECK + measure func=FILE_MMAP mask=MAY_EXEC + measure func=INODE_PERM mask=MAY_READ uid=0 + + The default policy measures all executables in bprm_check, + all files mmapped executable in file_mmap, and all files + open for read by root in inode_permission. + + Examples of LSM specific definitions: + + SELinux: + dont_measure obj_type=var_log_t + dont_measure obj_type=auditd_log_t + measure subj_user=system_u func=INODE_PERM mask=MAY_READ + measure subj_role=system_r func=INODE_PERM mask=MAY_READ + + Smack: + measure subj_user=_ func=INODE_PERM mask=MAY_READ
Documentation/kernel-parameters.txt +5 -0
@@ -44,6 +44,7 @@ parameter is applicable: FB The frame buffer device is enabled. HW Appropriate hardware is enabled. IA-64 IA-64 architecture is enabled. + IMA Integrity measurement architecture is enabled. INTEGRITY Integrity support is enabled. IOSCHED More than one I/O scheduler is enabled. IP_PNP IP DHCP, BOOTP, or RARP is enabled.
@@ -858,6 +859,10 @@ and is between 256 and 4096 characters. It is defined in the file ihash_entries= [KNL] Set number of hash buckets for inode cache. + ima_hash= [IMA] runtime ability to define hash crypto algorithm. + Format: { "MD5" | "SHA1" } + Default is "SHA1". + in2000= [HW,SCSI] See header of drivers/scsi/in2000.c.
include/linux/ima.h new file +46 -0
46 lines not on this page · raw message
security/integrity/Kconfig +2 -3
@@ -2,8 +2,6 @@ # Integrity configuration # -menu "Integrity options" - config INTEGRITY bool "Enable different integrity models" help
@@ -21,4 +19,5 @@ config INTEGRITY_AUDIT allows integrity auditing to be disabled at boot. If this option is selected, integrity auditing can be disabled with 'integrity_audit=0' on the kernel command line. -endmenu + +source security/integrity/ima/Kconfig
security/integrity/Makefile +2 -0
@@ -4,3 +4,5 @@ # Object file lists obj-$(CONFIG_INTEGRITY) += integrity.o integrity_audit.o + +obj-$(CONFIG_IMA) += ima/
security/integrity/ima/Kconfig new file +48 -0
48 lines not on this page · raw message
security/integrity/ima/Makefile new file +9 -0
@@ -0,0 +1,9 @@ +# +# Makefile for building Trusted Computing Group's(TCG) runtime Integrity +# Measurement Architecture(IMA). +# + +obj-$(CONFIG_IMA) += ima.o + +ima-y := ima_fs.o ima_queue.o ima_init.o ima_main.o ima_crypto.o ima_api.o \ + ima_policy.o
security/integrity/ima/ima.h new file +170 -0
170 lines not on this page · raw message
security/integrity/ima/ima_api.c new file +348 -0
348 lines not on this page · raw message
security/integrity/ima/ima_crypto.c new file +153 -0
153 lines not on this page · raw message
security/integrity/ima/ima_fs.c new file +473 -0
473 lines not on this page · raw message
security/integrity/ima/ima_init.c new file +105 -0
105 lines not on this page · raw message
security/integrity/ima/ima_main.c new file +354 -0
354 lines not on this page · raw message
security/integrity/ima/ima_policy.c new file +334 -0
334 lines not on this page · raw message
security/integrity/ima/ima_queue.c new file +124 -0
124 lines not on this page · raw message
Signature · 1 line
1.5.5.1
Serge E. Hallyn
maintainerRe: [PATCH 3/3] integrity: IMA as an integrity service provider
Quoted 795 lines · Mimi Zohar
This is a re-release of Integrity Measurement Architecture(IMA) as an independent Linunx Integrity Module(LIM) service provider.
This version addresses the merge issues resulting from the removal of the nameidata parameter to
inode_permission().
- The parameter changes tointegrity_inode_permission()are reflected here in this patch.As a LIM integrity provider, IMA implements the new LIM
must_measure(),collect_measurement(),store_measurement(), anddisplay_template()API calls. Thestore_measurement()call supports two types of data, IMA (i.e. file data) and generic template data.IMA provides hardware (TPM) based measurement and attestation for both files and other types of template measurements. As the Trusted Computing (TPM) model requires, IMA measures all files before they are accessed in any way (on the
bprm_check_integrity,file_mmapandinode_permissionhooks), and commits the measurements to the TPM. In addition, IMA maintains a list of these hash values, which can be used to validate the aggregate PCR value. The TPM can sign these measurements, and thus the system can prove to itself and to a third party these measurements in a way that cannot be circumvented by malicious or compromised software.When
store_measurement()is called for the IMA type of data, the file measurement and the file name hint are used to form an IMA template. IMA then calculates the IMA template measurement(hash) and submits it to the TPM chip for inclusion in one of the chip's Platform Configuration Registers (PCR).When
store_measurement()is called for generic template data, IMA calculates the measurement(hash) of the template data, and submits the template measurement to the TPM chip for inclusion in one of the chip's Platform Configuration Registers(PCR).In order to view the contents of template data through securityfs, the
template_display()function must be defined in the registeredtemplate_operations. In the case of the IMA template, the list of file names and files hashes submitted can be viewed through securityfs.As mentioned above, IMA maintains a list of hash values of executables and other sensitive system files loaded into the run-time of the system. Our work has shown that requests for integrity appraisal and measurement need to be based on knowledge of the filesystem, requiring the system to either be labeled with integrity data or depend on the existent LSM security labels. The previous set of integrity patches modified the LSM modules to be integrity context aware, meaning that the LSM modules made integrity data/metadata appraisal and measurement API calls based on an understanding of the LSM security labels. Both of the LSM maintainers felt that the changes were too intrusive and that integrity enforcement should be made by the integrity provider, not the LSM module.
To address these concerns, Stephen Smalley suggested using the
security_audit_rule_match(), renamed tosecurity_filter_rule_match(), to define LSM specific integrity measurement policy rules, in lieu of modifying the LSM modules. In the current set of patches, the integrity API calls can be made either by IMA, based on an LSM specific integrity policy, or by an integrity context aware LSM.Signed-off-by Mimi Zohar <[email protected]>--- Documentation/ABI/testing/ima_policy | 60 +++++ Documentation/kernel-parameters.txt | 5 + include/linux/ima.h | 46 ++++ security/integrity/Kconfig | 5 +- security/integrity/Makefile | 2 + security/integrity/ima/Kconfig | 48 ++++ security/integrity/ima/Makefile | 9 + security/integrity/ima/ima.h | 170 ++++++++++++ security/integrity/ima/ima_api.c | 348 +++++++++++++++++++++++++ security/integrity/ima/ima_crypto.c | 153 +++++++++++ security/integrity/ima/ima_fs.c | 473 ++++++++++++++++++++++++++++++++++ security/integrity/ima/ima_init.c | 105 ++++++++ security/integrity/ima/ima_main.c | 354 +++++++++++++++++++++++++ security/integrity/ima/ima_policy.c | 334 ++++++++++++++++++++++++ security/integrity/ima/ima_queue.c | 124 +++++++++ 15 files changed, 2233 insertions(+), 3 deletions(-) create mode 100644 Documentation/ABI/testing/ima_policy create mode 100644 include/linux/ima.h create mode 100644 security/integrity/ima/Kconfig create mode 100644 security/integrity/ima/Makefile create mode 100644 security/integrity/ima/ima.h create mode 100644 security/integrity/ima/ima_api.c create mode 100644 security/integrity/ima/ima_crypto.c create mode 100644 security/integrity/ima/ima_fs.c create mode 100644 security/integrity/ima/ima_init.c create mode 100644 security/integrity/ima/ima_main.c create mode 100644 security/integrity/ima/ima_policy.c create mode 100644 security/integrity/ima/ima_queue.cDocumentation/ABI/testing/ima_policy new file +60
-0@@ -0,0 +1,60 @@ +What: security/ima/policy +Date: May 2008 +Contact: Mimi Zohar <[email protected]> +Description: + The Trusted Computing Group(TCG) runtime Integrity + Measurement Architecture(IMA) maintains a list of hash + values of executables and other sensitive system files + loaded into the run-time of this system. At runtime, + the policy can be constrained based on LSM specific data. + Policies are loaded into security/ima/policy by opening + the file, writing the rules one at a time and then + closing the file. The new policy takes effect after + the security/ima/policy is closed. + + rule format: action [condition ...] + + action: measure | dont_measure + condition:= base | lsm + base: [[func=] [mask=] [fsmagic=] [uid=]] + lsm: [[subj_user=] [subj_role=] [subj_type=] + [obj_user=] [obj_role=] [obj_type=]] + + base: func:= [BPRM_CHECK][FILE_MMAP][INODE_PERMISSION] + mask:= [MAY_READ] [MAY_WRITE] [MAY_APPEND] [MAY_EXEC] + fsmagic:= hex value + uid:= decimal value + lsm: are LSM specific + + default policy: + # PROC_SUPER_MAGIC + dont_measure fsmagic=0x9fa0 + # SYSFS_MAGIC + dont_measure fsmagic=0x62656572 + # DEBUGFS_MAGIC + dont_measure fsmagic=0x64626720 + # TMPFS_MAGIC + dont_measure fsmagic=0x01021994 + # SECURITYFS_MAGIC + dont_measure fsmagic=0x73636673 + # SELINUX_MAGIC + dont_measure fsmagic=0xF97CFF8C + + measure func=BPRM_CHECK + measure func=FILE_MMAP mask=MAY_EXEC + measure func=INODE_PERM mask=MAY_READ uid=0 + + The default policy measures all executables in bprm_check, + all files mmapped executable in file_mmap, and all files + open for read by root in inode_permission. + + Examples of LSM specific definitions: + + SELinux: + dont_measure obj_type=var_log_t + dont_measure obj_type=auditd_log_t + measure subj_user=system_u func=INODE_PERM mask=MAY_READ + measure subj_role=system_r func=INODE_PERM mask=MAY_READ + + Smack: + measure subj_user=_ func=INODE_PERM mask=MAY_READDocumentation/kernel-parameters.txt +5
-0@@ -44,6 +44,7 @@ parameter is applicable: FB The frame buffer device is enabled. HW Appropriate hardware is enabled. IA-64 IA-64 architecture is enabled. + IMA Integrity measurement architecture is enabled. INTEGRITY Integrity support is enabled. IOSCHED More than one I/O scheduler is enabled. IP_PNP IP DHCP, BOOTP, or RARP is enabled.@@ -858,6 +859,10 @@ and is between 256 and 4096 characters. It is defined in the file ihash_entries= [KNL] Set number of hash buckets for inode cache. + ima_hash= [IMA] runtime ability to define hash crypto algorithm. + Format: { "MD5" | "SHA1" } + Default is "SHA1". + in2000= [HW,SCSI] See header of drivers/scsi/in2000.c.include/linux/ima.h new file +46
-0@@ -0,0 +1,46 @@ +/* +* ima.h +* +* Copyright (C) 2008 IBM Corporation +* Author: Mimi Zohar <[email protected]> +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License as published by +* the Free Software Foundation, version 2 of the License. +*/ + +#ifndef _LINUX_IMA_H +#define _LINUX_IMA_H + +/* IMA LIM Data */ +enum ima_type {IMA_DATA ,IMA_METADATA ,IMA_TEMPLATE }; + +struct ima_args_data { +const char *filename; +struct file *file; +struct path *path; +struct dentry *dentry; +struct inode *inode; +enum lim_hooks function; +u32 osid; +int mask; +}; + +struct ima_store_data { +char *name; +int len; +char *data; +int violation; +}; + +struct ima_data { +enum ima_type type; +union { +struct ima_args_data args; +struct ima_store_data template; + } data; +}; + +void ima_fixup_argsdata (struct ima_args_data *data,struct file *file, +struct path *path,int mask,int function); +#endif security/integrity/Kconfig +2
-3@@ -2,8 +2,6 @@ # Integrity configuration # -menu "Integrity options" - config INTEGRITY bool "Enable different integrity models" help@@ -21,4 +19,5 @@ config INTEGRITY_AUDIT allows integrity auditing to be disabled at boot. If this option is selected, integrity auditing can be disabled with 'integrity_audit=0' on the kernel command line. -endmenu + +source security/integrity/ima/Kconfigsecurity/integrity/Makefile +2
-0@@ -4,3 +4,5 @@ # Object file lists obj-$(CONFIG_INTEGRITY) += integrity.o integrity_audit.o + +obj-$(CONFIG_IMA) += ima/security/integrity/ima/Kconfig new file +48
-0@@ -0,0 +1,48 @@ +# +# IBM Integrity Measurement Architecture +# + +config IMA + bool "Integrity Measurement Architecture(IMA)" + depends on INTEGRITY + depends on ACPI + select CRYPTO + select CRYPTO_HMAC + select CRYPTO_MD5 + select CRYPTO_SHA1 + select TCG_TPM + select TCG_TIS + help + The Trusted Computing Group(TCG) runtime Integrity + Measurement Architecture(IMA) maintains a list of hash + values of executables and other sensitive system files + loaded into the run-time of this system. If your system + has a TPM chip, then IMA also maintains an aggregate + integrity value over this list inside the TPM hardware. + These measurements and the aggregate (signed inside the + TPM) can be retrieved and presented to remote parties to + establish system properties. If unsure, say N. + +config IMA_MEASURE_PCR_IDX + int "PCR for Aggregate (8 <= Index <= 14)" + depends on IMA + range 8 14 + default 10 + help + IMA_MEASURE_PCR_IDX determines the TPM PCR register index + that IMA uses to maintain the integrity aggregate of the + measurement list. If unsure, use the default 10. + +config IMA_BASE_HOOKS + bool "IMA base hooks" + depends on IMA + default n + help + Enable this option to allow the LSM module to enforce integrity. + +config IMA_LSM_RULES + bool "Enable LSM measurement policy rules" + depends on IMA && (SECURITY_SELINUX || SECURITY_SMACK) + default y + help + Disabling this option will not enforce LSM based policy rules.security/integrity/ima/Makefile new file +9
-0@@ -0,0 +1,9 @@ +# +# Makefile for building Trusted Computing Group's(TCG) runtime Integrity +# Measurement Architecture(IMA). +# + +obj-$(CONFIG_IMA) += ima.o + +ima-y := ima_fs.o ima_queue.o ima_init.o ima_main.o ima_crypto.o ima_api.o \ + ima_policy.osecurity/integrity/ima/ima.h new file +170
-0@@ -0,0 +1,170 @@ +/* +* Copyright (C) 2005,2006,2007,2008 IBM Corporation +* +* Authors: +* Reiner Sailer <[email protected]> +* Mimi Zohar <[email protected]> +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License as +* published by the Free Software Foundation, version 2 of the +* License. +* +* File: ima.h +* internal ima definitions +*/ + +#ifndef __LINUX_IMA_H +#define __LINUX_IMA_H + +#include <linux/types.h> +#include <linux/crypto.h> +#include <linux/security.h> +#include <linux/integrity.h> +#include <linux/hash.h> +#include <linux/tpm.h> + +#define ima_printk(level, format, arg...) \ + printk(level "ima (%s): " format, __func__, ## arg) + +#define ima_error(format, arg...) \ + ima_printk(KERN_ERR, format, ## arg) + +#define ima_info(format, arg...) \ + ima_printk(KERN_INFO, format, ## arg) + +/* digest size for IMA, fits SHA1 or MD5 */ +#define IMA_DIGEST_SIZE 20 +#define IMA_EVENT_NAME_LEN_MAX 255 + +#define IMA_HASH_BITS 9 +#define IMA_MEASURE_HTABLE_SIZE (1 << IMA_HASH_BITS) + +/* set during initialization */ +extern int ima_used_chip; +extern char *ima_hash; + +struct ima_measure_entry { +u8 digest[IMA_DIGEST_SIZE ];/* sha1 or md5 measurement hash */ +char template_name[IMA_EVENT_NAME_LEN_MAX +1 ];/* name + \0 */ +int template_len; +char *template; +}; + +struct ima_queue_entry { +struct hlist_node hnext;/* place in hash collision list */ +struct list_head later;/* place in ima_measurements list */ +struct ima_measure_entry *entry; +}; +extern struct list_head ima_measurements;/* list of all measurements */ + +/* declarations */ +extern int ima_template_mode; +extern const struct template_operations ima_template_ops; + +/* Internal IMA function definitions */ +int ima_init (void ); +void ima_cleanup (void ); +int ima_fs_init (void ); +void ima_fs_cleanup (void ); +void ima_create_htable (void ); +int ima_add_measure_entry (struct ima_measure_entry *entry,int violation); +struct ima_queue_entry *ima_lookup_digest_entry (u8 *digest); +int ima_calc_hash (struct file *file,struct path *path,char *digest); +int ima_calc_template_hash (int template_len,char *template,char *digest); +void ima_add_violation (struct inode *inode,const unsigned char *fname, +char *op,char *cause); + +enum ima_action {DONT_MEASURE ,MEASURE }; +int ima_match_policy (struct inode *inode,enum lim_hooks func,int mask); +int ima_add_rule (int ,char *subj_user,char *subj_role,char *subj_type, +char *obj_user,char *obj_role,char *obj_type, +char *func,char *mask,char *fsmagic,char *uid); +void ima_init_policy (void ); +void ima_update_policy (void ); + + +/* LIM API function definitions */ +int ima_must_measure (void *d); +int ima_collect_measurement (void *d); +int ima_appraise_measurement (void *d); +void ima_store_measurement (void *d); +void ima_template_show (struct seq_file *m,void *e, +enum integrity_show_type show); + + +/* +* used to protect h_table and sha_table +*/ +extern spinlock_t ima_queue_lock; + +struct ima_h_table { +atomic_long_t len;/* number of stored measurements in the list */ +atomic_long_t violations; +unsigned int max_htable_size; +struct hlist_head queue[IMA_MEASURE_HTABLE_SIZE ]; +atomic_t queue_len[IMA_MEASURE_HTABLE_SIZE ]; +}; +extern struct ima_h_table ima_htable; + +static inline unsigned long IMA_HASH_KEY (u8 *digest) +{ +return (hash_ptr (digest,IMA_HASH_BITS )); +} + +/* TPM "Glue" definitions */ + +#define IMA_TPM ((((u32)TPM_ANY_TYPE)<<16) | (u32)TPM_ANY_NUM) +static inline void ima_extend (const u8 *hash) +{ +if (!ima_used_chip) +return ; + +if (tpm_pcr_extend (IMA_TPM ,CONFIG_IMA_MEASURE_PCR_IDX , hash) !=0 ) +ima_error ("Error Communicating to TPM chip\n" ); +} + +static inline void ima_pcrread (int idx,u8 *pcr,int pcr_size) +{ +if (!ima_used_chip) +return ; + +if (tpm_pcr_read (IMA_TPM , idx, pcr) !=0 ) +ima_error ("Error Communicating to TPM chip\n" ); +} + +struct ima_inode_measure_entry { +u8 digest[IMA_DIGEST_SIZE ];/* sha1/md5 measurement hash */ +char file_name[IMA_EVENT_NAME_LEN_MAX +1 ];/* name + \0 */ +}; + +/* inode integrity data */ +struct ima_iint_cache { +u64 version; +int measured; +u8 hmac[IMA_DIGEST_SIZE ]; +u8 digest[IMA_DIGEST_SIZE ]; +struct mutex mutex; +}; + +/* LSM based policy rules require audit */ +#ifdef CONFIG_IMA_LSM_RULES + +#define security_filter_rule_init security_audit_rule_init +#define security_filter_rule_match security_audit_rule_match + +#else + +static inline int security_filter_rule_init (u32 field,u32 op,char *rulestr, +void **lsmrule) +{ +return -EINVAL ; +} + +static inline int security_filter_rule_match (u32 secid,u32 field,u32 op, +void *lsmrule,struct audit_context *actx) +{ +return -EINVAL ; +} +#endif +#endif security/integrity/ima/ima_api.c new file +284
-0@@ -0,0 +1,348 @@ +/* +* Copyright (C) 2008 IBM Corporation +* +* Author: Mimi Zohar <[email protected]> +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License as +* published by the Free Software Foundation, version 2 of the +* License. +* +* File: ima_api.c +* - implements the LIM API +*/ +#include <linux/module.h> +#include <linux/integrity.h> +#include <linux/magic.h> +#include <linux/writeback.h> +#include <linux/string.h> +#include <linux/list.h> +#include <linux/audit.h> +#include <linux/ima.h> + +#include "ima.h" + +const struct template_operations ima_template_ops = { + .must_measure = ima_must_measure, + .collect_measurement = ima_collect_measurement, + .store_measurement = ima_store_measurement, + .display_template = ima_template_show +}; + +/** +* mode_setup - for compatability with non-template IMA versions +* @str: is pointer to a string +*/ +int ima_template_mode =1 ; +static int __init mode_setup (char *str) +{ +if (strncmp (str,"ima" ,3 ) ==0 ) + ima_template_mode =0 ; +if (strncmp (str,"template" ,7 ) ==0 ) + ima_template_mode =1 ; +ima_info ("template_mode %s \n" , + ima_template_mode ?"template" :"ima" ); +return 1 ; +} + +__setup ("ima_mode=" , mode_setup); + +/** +* ima_digest_cpy - copy the hash in the IMA template structure to a digest +* @template_name: string containing the name of the template (i.e. "ima") +* @template: pointer to template structure +* @digest: pointer to the digest +* +* Returns 0 on success, error code otherwise +*/ +static int ima_digest_cpy (char *template_name,void *template,u8 *digest) +{ +int rc, result =0 ; +struct ima_inode_measure_entry *inode_template = + (struct ima_inode_measure_entry *)template; + + rc =strcmp (template_name,"ima" ); +if (rc ==0 ) +memcpy (digest, inode_template->digest, +sizeof inode_template->digest); +else + result = -ENODATA ; +return result; +} + +/** +* ima_store_template_measure - collect and protect template measurements +* @template_name: string containing the name of the template (i.e. "ima") +* @template_len: length of the template data +* @template: actual template data +* @violation: invalidate pcr measurement indication +* @audit_cause: string containing the audit failure cause +* +* Calculate the hash of a template entry, add the template entry +* to an ordered list of measurement entries maintained inside the kernel, +* and also update the aggregate integrity value (maintained inside the +* configured TPM PCR) over the hashes of the current list of measurement +* entries. +* +* Applications retrieve the current kernel-held measurement list through +* the securityfs entries in /sys/kernel/security/ima. The signed aggregate +* TPM PCR (called quote) can be retrieved using a TPM user space library +* and is used to validate the measurement list. +* +* Returns 0 on success, error code otherwise +*/ +static int ima_store_template_measure (char *template_name,int template_len, +char *template,int violation, +char **audit_cause) +{ +struct ima_measure_entry *entry; +u8 digest[IMA_DIGEST_SIZE ]; +struct ima_queue_entry *qe; +int count, result =0 ; + +memset (digest,0 ,IMA_DIGEST_SIZE ); +if (!violation) { +int rc = -ENODATA ; + +if (!ima_template_mode) + rc =ima_digest_cpy (template_name, template, digest); +if (rc <0 ) + result =ima_calc_template_hash (template_len, template, + digest); + +/* hash exists already? */ + qe =ima_lookup_digest_entry (digest); +if (qe) { + *audit_cause ="hash_exists" ; + result = -EEXIST ; + goto out; + } + } + +/* create new entry and add to measurement list */ + entry =kzalloc (sizeof (*entry),GFP_KERNEL ); +if (!entry) { + *audit_cause ="ENOMEM" ; + result = -ENOMEM ; + goto out; + } + + entry->template =kzalloc (template_len,GFP_KERNEL ); +if (!entry->template) { + *audit_cause ="ENOMEM" ; + result = -ENOMEM ; + goto out; + } +if (!template_name) { + *audit_cause ="null_template_name" ; + count =1 ; + }else { + count =strlen (template_name); +if (count >IMA_EVENT_NAME_LEN_MAX ) + count =IMA_EVENT_NAME_LEN_MAX ; +memcpy (entry->template_name, template_name, count); + } + entry->template_name[count] ='\0' ; + entry->template_len = template_len; +memcpy (entry->template, template, template_len); +memcpy (entry->digest, digest,IMA_DIGEST_SIZE ); + + result =ima_add_measure_entry (entry, violation); +if (result <0 ) +kfree (entry); +out: +return result; +} + +/** +* ima_store_inode_measure - create and store an inode template measurement +* @name: ascii file name associated with the measurement hash +* @hash_len: length of hash value in bytes (16 for MD5, 20 for SHA1) +* @hash: actual hash value pre-calculated +* +* Returns 0 on success, error code otherwise +*/ +static int ima_store_inode_measure (struct inode *inode, +const unsigned char *name, +int hash_len,char *hash,int violation) +{ +struct ima_inode_measure_entry measure_entry, *entry = &measure_entry; +int result; +int namelen; +char *op ="add_measure" ; +char *cause =" " ; + +memset (entry,0 ,sizeof *entry); +if (!violation) +memcpy (entry->digest, hash, hash_len >IMA_DIGEST_SIZE ? +IMA_DIGEST_SIZE : hash_len); +if (name) { + namelen =strlen (name); +memcpy (entry->file_name, name, namelen >IMA_EVENT_NAME_LEN_MAX + ?IMA_EVENT_NAME_LEN_MAX : namelen); + entry->file_name[namelen] ='\0' ; + } + result =ima_store_template_measure ("ima" ,sizeof *entry, (char *)entry, + violation, &cause); +if (result <0 ) +integrity_audit_msg (AUDIT_INTEGRITY_PCR , inode, + name, op, cause, result); +return result; +} + +/** +* ima_add_violation - add violation to measurement list. +* @inode: inode associated with the violation +* @fname: name associated with the inode +* @op: string pointer to audit operation (i.e. "invalid_pcr", "add_measure") +* @cause: string pointer to reason for violation (i.e. "ToMToU") +* +* Violations are flagged in the measurement list with zero hash values. +* By extending the PCR with 0xFF's instead of with zeroes, the PCR +* value is invalidated. +*/ +void ima_add_violation (struct inode *inode,const unsigned char *fname, +char *op,char *cause) +{ +int result; + +/* can overflow, only indicator */ +atomic_long_inc (&ima_htable.violations); + + result =ima_store_inode_measure (inode, fname,0 ,NULL ,1 ); +integrity_audit_msg (AUDIT_INTEGRITY_PCR , inode, fname, op, + cause, result); +} + +/** +* skip_measurement - measure only regular files, skip everything else. +* @inode: inode being measured +* @mask: contains the permission mask +* +* Quick sanity check to make sure that only regular files opened +* for read-only or execute are measured. +* +* Return 1 to skip measure, 0 to measure +*/ +static int skip_measurement (struct inode *inode,int mask) +{ +if (S_ISCHR (inode->i_mode) ||S_ISBLK (inode->i_mode)) +return 1 ;/* can't measure */ + +if (special_file (inode->i_mode) ||S_ISLNK (inode->i_mode)) +return 1 ;/* don't measure */ + +if (S_ISREG (inode->i_mode)) +return 0 ;/* measure */ +return 1 ;/* don't measure */ +} + +/** +* ima_must_measure - measure decision based on policy. +* @template_data: pointer to struct ima_data containing ima_args_data +* +* The policy is defined in terms of keypairs: +* subj=, obj=, type=, func=, mask=, fsmagic= +* subj,obj, and type: are LSM specific. +* func: INODE_PERMISSION | BPRM_CHECK | FILE_MMAP +* mask: contains the permission mask +* fsmagic: hex value +* +* Return 0 to measure. For matching a DONT_MEASURE policy, no policy, +* or other error, return an error code. +*/ +int ima_must_measure (void *template_data) +{ +struct ima_data *idata = (struct ima_data *)template_data; +struct ima_args_data *data = &idata->data.args; +int rc; + +if ((data->mask &MAY_WRITE ) || (data->mask &MAY_APPEND )) +return -EPERM ; + +if (skip_measurement (data->inode, data->mask)) +return -EPERM ; + + rc =ima_match_policy (data->inode, data->function, data->mask); +if (rc) +return 0 ; +return -EACCES ; +} + +/** +* ima_collect_measurement - collect file measurements and store in the inode +* @template_data: pointer to struct ima_data containing ima_args_data +* +* Return 0 on success, error code otherwise +*/ +int ima_collect_measurement (void *template_data) +{ +struct ima_iint_cache *iint; +struct ima_data *idata = (struct ima_data *)template_data; +struct ima_args_data *data = &idata->data.args; +struct dentry *dentry = data->dentry; +struct inode *inode = data->inode;
security/integrity/ima/ima_api.c line 294
Quoted 10 lines
security/integrity/ima/ima_api.c new file +10
-0+int result =0 ; + +if (idata->type !=IMA_DATA ) +return -EPERM ; + +if (!inode || !dentry) +return -EINVAL ; + + iint = inode->i_integrity; +mutex_lock (&iint->mutex);
ima_collect_measurement will be called under rcu_read_lock(), won't it? So you can't take a mutex, bc that could sleep.
Quoted 20 lines
security/integrity/ima/ima_api.c new file +20
-0+if (!iint->measured) { +memset (iint->digest,0 ,IMA_DIGEST_SIZE ); + result =ima_calc_hash (data->file, data->path, iint->digest); + }else + result = -EEXIST ; +mutex_unlock (&iint->mutex); +return result; +} + +/** +* ima_store_measurement - store file and template measurements +* @template_data: pointer to struct ima_data containing ima_args_data, +* used to create an IMA template, or a template. +* +* For file measurements, first create an IMA template and then store it. +* For all other types of template measurements, just store it. +*/ +void ima_store_measurement (void *template_data) +{ +struct ima_data *idata = (struct ima_data *)template_data;
security/integrity/ima/ima_api.c line 324
Quoted 10 lines
security/integrity/ima/ima_api.c new file +10
-0+int result; +char *op ="add_template_measure" ; +char *cause ="" ; + +if (idata->type ==IMA_DATA ) { +struct ima_args_data *data = &idata->data.args; +struct ima_iint_cache *iint; + + iint = data->inode->i_integrity; +mutex_lock (&iint->mutex);
Same here.
-serge