Re: libsodium based Argon2i(d) password_hash()
| From: | Sara Golemon | Date: | Thu, 20 Jun 2019 20:58:06 +0000 |
| Subject: | Re: libsodium based Argon2i(d) password_hash() | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-106009@lists.php.net to get a copy of this message | ||
On Thu, Jun 20, 2019 at 2:34 AM Nikita Popov <nikita.ppv@gmail.com> wrote:
> On Thu, Jun 20, 2019 at 12:54 AM Sara Golemon <pollita@php.net> wrote:
>
> > I intend to move
> > https://wiki.php.net/rfc/sodium.argon.hash into voti
> >
> > For "threads" (p=# in the hash output), the current PHP default is 2,
> > while libsodium is hardcoded at 1, we can't override that.
> > ng on
> > Friday.
> >
> > Note that I need to update the PR to reflect the decision to synchronize
> > the time_cost and mem_limit defaults for libargon based hashing with
> > libsodium.
> >
> > If you have any last minute issues with this RFC, please bring them up
> now.
> >
>
> Could you please explicitly specify what the new default time/memory cost
> factors will be?
>
> Done.
> Also, what is going to happen with threads? I assume the default will
> become 1, but what happens is a larger value is specified while libsodium
> is used?
>
> Default to 1. Users will be allowed to specify higher numbers, but the
sodium implementation will produce an error with values > 1.
-Sara