Re: crypt_checkpass.3: mention additional failure case for crypt_newhash

2017-07-22 Thread Scott Cheloha
> On Jul 21, 2017, at 10:24 PM, Ted Unangst wrote: > > Scott Cheloha wrote: >> crypt_newhash(3) will return -1 and set errno to EINVAL if hashsize is >> too small to accommodate bcrypt's hash space. I imagine this would >> also be the case if anything other than bcrypt were

Re: crypt_checkpass.3: mention additional failure case for crypt_newhash

2017-07-21 Thread Ted Unangst
Scott Cheloha wrote: > crypt_newhash(3) will return -1 and set errno to EINVAL if hashsize is > too small to accommodate bcrypt's hash space. I imagine this would > also be the case if anything other than bcrypt were supported. i went ahead and reworked the page a bit. i think it clarifies a few

crypt_checkpass.3: mention additional failure case for crypt_newhash

2017-07-21 Thread Scott Cheloha
Hi, crypt_newhash(3) will return -1 and set errno to EINVAL if hashsize is too small to accommodate bcrypt's hash space. I imagine this would also be the case if anything other than bcrypt were supported. Test program: #include #include #include int main(int argc, char *argv[]) {