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
| ||
|
Message-ID: <20170614070614.GA1786@infradead.org> Date: Wed, 14 Jun 2017 00:06:14 -0700 From: Christoph Hellwig <hch@...radead.org> To: Eric Biggers <ebiggers3@...il.com> Cc: Christoph Hellwig <hch@...radead.org>, linux-fscrypt@...r.kernel.org, Theodore Ts'o <tytso@....edu>, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, linux-mtd@...ts.infradead.org, Eric Biggers <ebiggers@...gle.com> Subject: Re: [PATCH 1/3] ext4: require key for truncate(2) of encrypted file On Wed, Jun 14, 2017 at 12:03:57AM -0700, Eric Biggers wrote: > None of those are allowed because fallocate() requires a file descriptor, and > open() fails with ENOKEY if the encryption key is not available. truncate() is > different because it takes a path, not a file descriptor. Ok, that makes sense.
Powered by blists - more mailing lists