Björn Ketelaars wrote:
> On Thu 02/01/2020 06:27, Björn Ketelaars wrote:
> > On Wed 01/01/2020 23:03, Ted Unangst wrote:
> > > Björn Ketelaars wrote:
> > > > - When estimating the amount of available RAM, scrypt ignores
> > > > RLIMIT_DATA on systems which have mmap.
> > >
> > > This is wrong on
On Sun, 12 Jan 2020 15:38:21 +0100
Björn Ketelaars wrote:
> On Thu 02/01/2020 06:27, Björn Ketelaars wrote:
> > On Wed 01/01/2020 23:03, Ted Unangst wrote:
> > > Björn Ketelaars wrote:
> > > > - When estimating the amount of available RAM, scrypt ignores
> > > > RLIMIT_DATA on systems which have
On Sun 12/01/2020 15:38, Björn Ketelaars wrote:
> On Thu 02/01/2020 06:27, Björn Ketelaars wrote:
> > On Wed 01/01/2020 23:03, Ted Unangst wrote:
> > > Björn Ketelaars wrote:
> > > > - When estimating the amount of available RAM, scrypt ignores
> > > > RLIMIT_DATA on systems which have mmap.
> >
On Thu 02/01/2020 06:27, Björn Ketelaars wrote:
> On Wed 01/01/2020 23:03, Ted Unangst wrote:
> > Björn Ketelaars wrote:
> > > - When estimating the amount of available RAM, scrypt ignores
> > > RLIMIT_DATA on systems which have mmap.
> >
> > This is wrong on OpenBSD. I sent an email to Colin, b
On Wed 01/01/2020 23:03, Ted Unangst wrote:
> Björn Ketelaars wrote:
> > - When estimating the amount of available RAM, scrypt ignores
> > RLIMIT_DATA on systems which have mmap.
>
> This is wrong on OpenBSD. I sent an email to Colin, but the update should
> patch this out in the meantime.
Alth
Björn Ketelaars wrote:
> - When estimating the amount of available RAM, scrypt ignores
> RLIMIT_DATA on systems which have mmap.
This is wrong on OpenBSD. I sent an email to Colin, but the update should
patch this out in the meantime.
Diff below brings security/scrypt to 1.3.0. Significant changes since
1.2.1 [0]:
- In addition to the scrypt command-line utility, a library
"libscrypt-kdf" can now be built and installed by passing the
--enable-libscrypt-kdf option to configure.
- On x86 CPUs which support them, RDRAND and SHA