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-next>] [day] [month] [year] [list]
Date: Thu, 5 Mar 2015 14:09:41 +0100
From: Sascha Schmidt <>
Subject: The PHS API

I think that the wish for a standard API, as brought up by Marsh Ray,
makes it necessary to discuss the PHS API. Just in case anyone would
use it as a base for the new API. In particular I would like to point
out the input parameter  const void *in  . Since this is the password,
declaring it as const strikes me as harmful.
I can see that having one constant password in a testing environment
may make sense. Getting the password erased when calling the
password-hashing function could be seen as a side-effect from the
users perspective, but in light of garbage-collector attacks, e.g.
Heartbleed, it seems to be the only sensible solution.

Sascha Schmidt

Powered by blists - more mailing lists