linux-kernel - Re: [PATCH] integrity: add ima_counts

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <7959.1246307789@jrobl>
Date:	Tue, 30 Jun 2009 05:36:29 +0900
From:	hooanon05@...oo.co.jp
To:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, James Morris <jmorris@...ei.org>,
	David Safford <safford@...son.ibm.com>,
	Mimi Zohar <zohar@...ibm.com>
Subject: Re: [PATCH] integrity: add ima_counts_put (updated) 


Mimi Zohar:
> This suggestion has been mentioned before; and yes would definitely
> resolve the annoying imbalance and iint_free() messages.  But
> incrementing/decrementing the pointers automatically each time a file is
> opened/closed would defeat their purpose - alerting us that a file was
> possibly not measured before being read/executed. 

I may be wrong since I don't fully understand IMA's purpose, but why did
you create ima_counts_get() and make it call after dentry_open() in
nfsd_open()? Isn't it same thing essentially?


J. R. Okajima
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/