Xin LI 7ac2e58818 When zero'ing out a buffer, make sure we are using right size. ... Without this change, in the worst but unlikely case scenario, certain administrative operations, including change of configuration, set or delete key from a GEOM ELI provider, may leave potentially sensitive information in buffer allocated from kernel memory. We believe that it is not possible to actively exploit these issues, nor does it impact the security of normal usage of GEOM ELI providers when these operations are not performed after system boot. Security: possible sensitive information disclosure Submitted by: Clement Lecigne <clecigne google com> MFC after: 3 days		2013-11-02 01:16:10 +00:00
..
g_eli_crypto.c	Update copyright years.	2010-09-23 12:02:08 +00:00
g_eli_ctl.c	When zero'ing out a buffer, make sure we are using right size.	2013-11-02 01:16:10 +00:00
g_eli_integrity.c	Add missing period at the end of the error message	2012-05-13 23:27:06 +00:00
g_eli_key_cache.c	Always initialize sc_ekey, because as of r238116 it is always used.	2012-08-10 18:43:29 +00:00
g_eli_key.c	Correct a comment and correct style of a flag check.	2012-07-04 17:43:25 +00:00
g_eli_privacy.c	Instead of allocating memory for all the keys at device attach,	2011-04-21 13:31:43 +00:00
g_eli.c	Make ELI destruction (including orphanization) less aggressive, making it	2013-09-02 10:44:54 +00:00
g_eli.h	Use correct part of the Master-Key for generating encryption keys.	2012-07-04 17:54:17 +00:00
pkcs5v2.c
pkcs5v2.h