Use a salted hash of the lock passphrase instead of plain text and do
authordtucker <dtucker@openbsd.org>
Fri, 15 May 2015 05:44:21 +0000 (05:44 +0000)
committerdtucker <dtucker@openbsd.org>
Fri, 15 May 2015 05:44:21 +0000 (05:44 +0000)
commitcb653e3c059f989c4546fd1f4813ae2592d38680
treeda4b60779a07acf1f7d7331d0f991142e1f1a710
parentf1bfdb2b2c4958e7577ffd21cef2643c0e658f1b
Use a salted hash of the lock passphrase instead of plain text and do
constant-time comparisons of it. Should prevent leaking any information about
it via timing, pointed out by Ryan Castellucci.  Add a 0.1s incrementing delay
for each failed unlock attempt up to 10s.  ok markus@ (earlier version), djm@
usr.bin/ssh/ssh-agent.c