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  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 9 Jan 2014 17:06:32 +0000
From: Peter Maxwell <peter@...icient.co.uk>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] What's your favorite entry so far, and why?

On 9 January 2014 13:52, CodesInChaos <codesinchaos@...il.com> wrote:

> > Do you really want to allocate 1GB of RAM on a tablet or smartphone to
> > perform the login process? A lot of those devices have less then
> > 1GB of RAM. In general I'm not convinced that a significant amount of
> > useres/admins are not pleased with a login process that
> > allocates a huge amount of the systems RAM. On many host, such a
> > solution will virtually enforce swapping. Just saying. :-)
>
> It's one of the reasons why I like time-memory tradeoffs. A device with
> less RAM
> can tune down the memory cost, increasing the computation time.
>
> I think most devices should be able to afford at least 100MB per CPU core.
>


What sort of size of memory requirement does one actually need to impose to
cause difficulty for i. GPUs, ii. FPGA/ASICs?

Content of type "text/html" skipped

Powered by blists - more mailing lists