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] [day] [month] [year] [list]
Message-ID: <9c61d812-9ec8-006d-bf24-775879678865@nod.at>
Date:   Wed, 30 Nov 2016 09:29:40 +0100
From:   Richard Weinberger <richard@....at>
To:     Joe Richey <joerichey@...gle.com>
Cc:     linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Ext4 Developers List <linux-ext4@...r.kernel.org>,
        Michael Halcrow <mhalcrow@...gle.com>,
        Theodore Ts'o <tytso@....edu>, muslukhovi@...il.com,
        David Gstir <david@...ma-star.at>
Subject: Re: Idea behind EXT4_IOC_GET_ENCRYPTION_PWSALT?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ