Bug 756586 - Add support for Scrypt hash function for password authentication
Summary: Add support for Scrypt hash function for password authentication
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-24 00:16 UTC by Ben Segal
Modified: 2016-11-24 15:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 756682 (view as bug list)
Environment:
Last Closed: 2011-11-24 09:39:38 UTC
Type: ---


Attachments (Terms of Use)

Description Ben Segal 2011-11-24 00:16:16 UTC
Modern GPUs are able to brute-force hashed passwords faster than ever, even when PBKDF2 or bcrypt are used. Scrypt (http://www.tarsnap.com/scrypt.html) is a key derivation function that is resistant to GPU-based attacks. I would like to see Fedora support the use of Scrypt password authentication. Please see the more detailed paper (http://www.tarsnap.com/scrypt/scrypt.pdf) on Scrypt for further details.

Comment 1 Tomas Mraz 2011-11-24 08:48:58 UTC
The currently supported SHA256 and SHA512 hashed passwords allow choosing the iteration counts relatively freely.

If the scrypt should be supported in Fedora it would have to be included in the glibc crypt() implementation.

Comment 2 Ben Segal 2011-11-24 09:23:34 UTC
Increasing the number of iterations can increase the time needed to compute a hash by a constant factor for both attackers with GPUs (or other specialized hardware) and ordinary users. Thus, the number of iterations necessary to make brute force attacks with GPUs unfeasible would also require ordinary users to wait a very long time for their CPUs to complete all of the hash iterations when using their passwords.

In contrast, Scrypt is designed such that hashes run relatively quickly on an ordinary user's CPU, but very slowly on GPUs used by potential brute-force attackers, forcing attackers to go back to brute-forcing with CPUs, and thus to surrender the advantage provided by GPUs for brute-forcing passwords hashed with current methods.

I apologize for filing this under the wrong component, however, and ask that it be looked at by the glibc team.


Note You need to log in before you can comment on or make changes to this bug.