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: Tue, 19 Feb 2013 01:35:12 -0800
From: Larry Bugbee <>
Subject: Re: [PHC] Coding of the in[inlen] array for PHS( )

On Feb 19, 2013, at 12:07 AM, Larry Bugbee <> wrote:
> ...all interface details should be unambigiously specified...

Now or later, but fully specified/documented.  

I can live with fully documented later unless it is a requirement going in.

Powered by blists - more mailing lists