phc-discussions - Re: [PHC] escrypt naming (Re: [PHC] TigerPHS paper and code ready for review)

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]

Date: Wed, 12 Mar 2014 08:18:02 +0400
From: Solar Designer <solar@...nwall.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] escrypt naming (Re: [PHC] TigerPHS paper and code ready for review)

On Wed, Mar 12, 2014 at 08:11:53AM +0400, Solar Designer wrote:
> I'd prefer a name for escrypt that would derive from and hint to its
> qualities, not refer to who's behind it.  A reference and homage to
> scrypt would be appropriate, though.  JtR is not terribly relevant.

BTW, speaking of naming escrypt based on who's behind it, I briefly
thought of names like owcrypt and wowcrypt (such very appropriate in the
year of dogecoin), referring to Openwall, but like I said I dislike this
approach.  I think the name should be "vendor-neutral".

Alexander