linux-kernel - Re: [PATCH 5/5] eCryptfs: Filename Encryption: mount option

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: <20081106141304.b675cb9e.akpm@linux-foundation.org>
Date:	Thu, 6 Nov 2008 14:13:04 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Michael Halcrow <mhalcrow@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, dustin.kirkland@...il.com,
	sandeen@...hat.com, tchicks@...ibm.com, shaggy@...ibm.com
Subject: Re: [PATCH 5/5] eCryptfs: Filename Encryption: mount option

On Tue, 4 Nov 2008 15:43:13 -0600
Michael Halcrow <mhalcrow@...ibm.com> wrote:

> Enable mount-wide filename encryption by providing the Filename
> Encryption Key (FNEK) signature as a mount option. Note that the
> ecryptfs-utils userspace package versions 61 or later support
> this option.

A usage example would, as always, be useful here.

Do we actually provide a secure key on the command line?  If so, do any
special steps need to be taken to prevent unauthorised viewing of it? 
Fancy things like `cat /proc/mounts' :)


--
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/