From: Richard Weinberger Subject: Re: Idea behind EXT4_IOC_GET_ENCRYPTION_PWSALT? Date: Wed, 30 Nov 2016 09:29:40 +0100 Message-ID: <9c61d812-9ec8-006d-bf24-775879678865@nod.at> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: linux-fsdevel , "linux-kernel@vger.kernel.org" , Ext4 Developers List , Michael Halcrow , Theodore Ts'o , muslukhovi@gmail.com, David Gstir To: Joe Richey Return-path: In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org Joe, On 30.11.2016 01:44, Joe Richey wrote: > Richard, > > Our current design for fscrypt (tentative name for the userspace > filesystem encryption manager) does not use the global filesystem salt > (EXT4_IOC_GET_ENCRYPTION_PWSALT), we are planning on having a > different salt for each password used in the system. We are using > planning on using Argon2id as the password stretching algorithm, so > we'll have costs for memory, time, and parallelism stored for each > password as well as a salt. Makes sense. So, for now I'll not implement this ioctl command in UBIFS. Thanks, //richard