| 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: Fri, 14 Dec 2012 13:00:33 +0100 (CET) From: lkml@...verphorums.com To: linux-kernel@...r.kernel.org Subject: Re: [PATCH v5 0/7] eCryptfs: added support for the encrypted key type Hi there, Either this is completely braindead, or I'm missing something very obvious. Why mess up encrypted keys with various "format" fixes. I hope this doesn't start a trend. The right (and disturbingly simpler) approach to fixing the auth_token vs. raw key material issue would be to put the fix in eCryptfs. In fact, all the relevant bits for filling the token from the key_desc/sig should be moved from security/keys/encrypted/ecryptfs_format.c to fs/ecryptfs/ecryptfs_kernel.h, and all the format cruft in encrypted-keys reverted. Then pretty much any "default" encrypted key could be used for ecryptfs… What am I missing? --@; --- posted at http://www.serverphorums.com http://www.serverphorums.com/read.php?12,341340,618745#msg-618745 -- 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/
Powered by blists - more mailing lists