summaryrefslogtreecommitdiff
path: root/deattack.c
diff options
context:
space:
mode:
authorDarren Tucker <dtucker@zip.com.au>2016-07-15 13:32:45 +1000
committerDarren Tucker <dtucker@zip.com.au>2016-07-15 13:45:42 +1000
commit9286875a73b2de7736b5e50692739d314cd8d9dc (patch)
treeda8bbecb3d639077b3ca94d31f0e94253009b061 /deattack.c
parenta162dd5e58ca5b224d7500abe35e1ef32b5de071 (diff)
Determine appropriate salt for invalid users.
When sshd is processing a non-PAM login for a non-existent user it uses the string from the fakepw structure as the salt for crypt(3)ing the password supplied by the client. That string has a Blowfish prefix, so on systems that don't understand that crypt will fail fast due to an invalid salt, and even on those that do it may have significantly different timing from the hash methods used for real accounts (eg sha512). This allows user enumeration by, eg, sending large password strings. This was noted by EddieEzra.Harari at verint.com (CVE-2016-6210). To mitigate, use the same hash algorithm that root uses for hashing passwords for users that do not exist on the system. ok djm@
Diffstat (limited to 'deattack.c')
0 files changed, 0 insertions, 0 deletions