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
| ||
|
Date: Tue, 27 Dec 2016 21:28:14 -0500 From: Theodore Ts'o <tytso@....edu> To: Eric Biggers <ebiggers@...gle.com> Cc: linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, Jaegeuk Kim <jaegeuk@...nel.org>, Richard Weinberger <richard@....at>, David Gstir <david@...ma-star.at> Subject: Re: [RFC PATCH 1/5] fscrypt: use ENOKEY when file cannot be created w/o key On Mon, Dec 05, 2016 at 11:12:44AM -0800, Eric Biggers wrote: > As part of an effort to clean up fscrypt-related error codes, make > attempting to create a file in an encrypted directory that hasn't been > "unlocked" fail with ENOKEY. Previously, several error codes were used > for this case, including ENOENT, EACCES, and EPERM, and they were not > consistent between and within filesystems. ENOKEY is a better choice > because it expresses that the failure is due to lacking the encryption > key. It also matches the error code returned when trying to open an > encrypted regular file without the key. > > I am not aware of any users who might be relying on the previous > inconsistent error codes, which were never documented anywhere. > > This failure case will be exercised by an xfstest. > > Signed-off-by: Eric Biggers <ebiggers@...gle.com> Applied to the fscrypt branch, thanks. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists