linux-kernel - Re: [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation

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]

Date:	Fri, 2 Nov 2007 13:10:31 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Michael Halcrow <mhalcrow@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, ecryptfs-devel@...ts.sourceforge.net,
	trevor.highland@...il.com
Subject: Re: [PATCH 3/3] eCryptfs: Set inode key only once per crypto
 operation

On Fri, 2 Nov 2007 13:53:08 -0500
Michael Halcrow <mhalcrow@...ibm.com> wrote:

> There is no need to keep re-setting the same key for any given
> eCryptfs inode. This patch optimizes the use of the crypto API and
> helps performance a bit.
> 
> Signed-off-by: Trevor Highland <trevor.highland@...il.com>
> Signed-off-by: Michael Halcrow <mhalcrow@...ibm.com>

I've inferred from this that Michael authored this patch.  Please
let me know if that was incorrect.

The way in which we indicate authorship is to put a From: line right
at the top of the changelog.  If no such line appears then the From:
line from the mail headers is used.
-
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/