Verify() :: Unknown Salt - Porting to NetCore Version

Question

Verify() :: Unknown Salt - Porting to NetCore Version

iby-dev opened this issue 6 years ago · 4 comments

HI, I think I have a similar situation to other issues on here.

I have been using this for a while now but with with an older api that i inherited and i don't know the salt value. We are porting it to netcore and noticed the same call to verify works in the older lib but with this new one. Any ideas?

The hashed passwords all come from a financial db that we call into to so i have no idea how they are hashed.

All we did before was provide a password and a matching hash was found linked to the email address and then this was pushed into Verify().

So i am not so sure now what to do?

Answer 1 · 2019-04-08T23:58:39.000Z

Sorry - copy and pasta'd!!!

Working now.

Answer 2 · 2019-04-09T08:27:56.000Z

Cool; as I've said in the previous ones the hashes and salts shouldn't really be split; and salt generation should be left to the hash call rather than generated separately. Down the line I'll probably depreciate and remove the direct call to salt.

Answer 3 · 2019-04-09T15:21:51.000Z

Hey no problem - thanks Chris. Grateful it was a copy and paste issue and nothing else as this would have been a major blocker for me porting this older api i wrote. Cheers

…

-------- Original message -------- From: Chris McKee <notifications@github.com> Date: 09/04/2019 01:27 (GMT-08:00) To: "BcryptNet/bcrypt.net" <bcrypt.net@noreply.github.com> Cc: Ibrar Mumtaz <ibrar@outlook.com>, State change <state_change@noreply.github.com> Subject: Re: [BcryptNet/bcrypt.net] Verify() :: Unknown Salt - Porting to NetCore Version (#33) Cool; as I've said in the previous ones the hashes and salts shouldn't really be split; and salt generation should be left to the hash call rather than generated separately. Down the line I'll probably depreciate and remove the direct call to salt. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FBcryptNet%2Fbcrypt.net%2Fissues%2F33%23issuecomment-481154524&data=02%7C01%7C%7C98800c70ee57418ff08108d6bcc544f6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636903952777600575&sdata=KcmouqP9ZA8Ro52wvPBbSOolSxlK5MKSZ4cucBkzGdc%3D&reserved=0>, or mute the thread<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALtHO5eX45p5cEnL-ESaPFzWDW2JKcORks5vfE8MgaJpZM4cjQvD&data=02%7C01%7C%7C98800c70ee57418ff08108d6bcc544f6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636903952777610580&sdata=ZsSXdd1nvQ%2BbaUz2yBhtK6JjieW6uY7bMHz%2FOSK9kYc%3D&reserved=0>.

Answer 4 · 2019-04-10T14:05:01.000Z

Thanks for the update; copy & paste gets us all in the end 😉