[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: crypt(3) interface to scrypt

To: Robert Ransom <rransom.8774@gmail.com>
Subject: Re: crypt(3) interface to scrypt
From: Colin Percival <cperciva@tarsnap.com>
Date: Wed, 21 Apr 2010 03:46:40 -0700
Cc: scrypt@tarsnap.com
In-reply-to: <20100408123028.34561421@gmail.com>
Mailing-list: contact scrypt-help@tarsnap.com; run by ezmlm
References: <20100408134443.GA13080@openwall.com> <20100408091348.16efac91@gmail.com> <4BBE04EB.1090605@alaska.net> <20100408123028.34561421@gmail.com>

Robert Ransom wrote:
> If you are only worried about attackers who are not competent enough to
> backdoor your server software, keep in mind that the easiest attack to
> mount is a DoS, and using scrypt for password hashing on a web server
> makes DoS attacks very easy indeed.  In this case, using scrypt only
> reduces your server's security.

With appropriate parameters, scrypt doesn't make a website DoS any easier
than other KDFs.

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid

References:
- crypt(3) interface to scrypt
  - From: Solar Designer <solar@openwall.com>
- Re: crypt(3) interface to scrypt
  - From: Robert Ransom <rransom.8774@gmail.com>
- Re: crypt(3) interface to scrypt
  - From: Royce Williams <royce@alaska.net>
- Re: crypt(3) interface to scrypt
  - From: Robert Ransom <rransom.8774@gmail.com>

Prev by Date: Re: crypt(3) interface to scrypt
Next by Date: Re: parallelism in a single instance of scrypt
Previous by thread: Re: crypt(3) interface to scrypt
Next by thread: Re: crypt(3) interface to scrypt
Index(es):
- Date
- Thread