lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 23 Sep 2011 19:47:05 -0400
From:	Valdis.Kletnieks@...edu
To:	Parag Amritkar <paragamritkar@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Use of inode for storing security info

On Fri, 23 Sep 2011 23:48:36 +0530, Parag Amritkar said:
> Can we use any field of inode for storing information like storing
> encryption key of that file?

You probably want to look at how the various security LSMs use
the "security.*" extended attribute namespace to store labels and
similar information.

Protip: You don't want to store the encryption key of the file there.
That's basically leaving the key under the doormat - and a sign saying
"look under doormat for key".

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ