phc-discussions - Re: [PHC] Best use of ROM in password hashing

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 linux-cve-announce 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]

Message-ID: <23834.1398012733@critter.freebsd.dk>
Date: Sun, 20 Apr 2014 16:52:13 +0000
From: "Poul-Henning Kamp" <phk@....freebsd.dk>
To: discussions@...sword-hashing.net,
        Krisztián Pintér <pinterkr@...il.com>
Subject: Re: [PHC] Best use of ROM in password hashing

In message <1792820670.20140420183951@...il.com>, =?iso-8859-1?Q?Kriszti=E1n_Pi
nt=E9r?= writes:

>reading this gave me an idea. what if we do the exact opposite?
>
>what if we make a device that is slow to read. it would have many TBs
>of data, but you could only read 1 bit at a time, and the device is so
>slow, [...]

That's not in any material way different from what I proposed about
offloading the entire password hash to a ARM chip with an USB port,
except for the fact that the "many TBs of data" will set you back
many coins in cost.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@...eBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.