remarkable-linux/security/integrity
Dmitry Kasatkin a35c3fb649 ima: use dynamically allocated hash storage
For each inode in the IMA policy, an iint is allocated.  To support
larger hash digests, the iint digest size changed from 20 bytes to
the maximum supported hash digest size.  Instead of allocating the
maximum size, which most likely is not needed, this patch dynamically
allocates the needed hash storage.

Changelog:
- fix krealloc bug

Signed-off-by: Dmitry Kasatkin <d.kasatkin@samsung.com>
Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
2013-10-25 17:17:00 -04:00
..
evm ima: pass full xattr with the signature 2013-10-25 17:16:59 -04:00
ima ima: use dynamically allocated hash storage 2013-10-25 17:17:00 -04:00
digsig.c ima: pass full xattr with the signature 2013-10-25 17:16:59 -04:00
digsig_asymmetric.c ima: read and use signature hash algorithm 2013-10-25 17:16:59 -04:00
iint.c ima: use dynamically allocated hash storage 2013-10-25 17:17:00 -04:00
integrity.h ima: use dynamically allocated hash storage 2013-10-25 17:17:00 -04:00
integrity_audit.c integrity: move integrity_audit_msg() 2013-06-20 07:47:49 -04:00
Kconfig integrity: move integrity_audit_msg() 2013-06-20 07:47:49 -04:00
Makefile integrity: move integrity_audit_msg() 2013-06-20 07:47:49 -04:00