phc-discussions - Re: [PHC] Transforming hash to different cost setting

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: <532D54B5.2020306@uni-weimar.de>
Date: Sat, 22 Mar 2014 10:15:33 +0100
From: Christian Forler <christian.forler@...-weimar.de>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Transforming hash to different cost setting

On 22.03.2014 09:57, Krisztián Pintér wrote:
> 
> Jeremi Gosney (at Saturday, March 22, 2014, 8:46:40 AM):
>> These are not hard requirements, they are simply critera that will be
>> evaluated in each candidate. You may choose not to support a particular
>> feature in your design.
> 
> 
> so far, i have heard only one reason for offline cost upgrade, and it
> is the problem of abandoned passwords. however, for that problem, we
> have the obvious solution of simply deleting old passwords.

For the weak password problem, we have the obvious solution of
simply using strong password. SCNR! :-)

Companies usually do not delete user/costumer accounts/records/files
since they rate those data as mission critical.

BTW I fully agree with your position. Inactive users should be disabled.


Best regards,
Christian



Download attachment "signature.asc" of type "application/pgp-signature" (535 bytes)