Derek Slager's BCrypt Class for C# Check Password Method failed

[ahmed_one]

Garth J Lancaster wrote:

if (!BCrypt.CheckPassword(txtPass.Text.Trim().ToString(), hashpassdb))

is wrong - which I think stems from this

txtHash.Text = BCrypt.HashPassword(txtPass.Text.Trim().ToString(),BCrypt.GenerateSalt(12));

Thanks for your reply... But txtPass.Text.Trim().ToString() is not generated from txtHash.Text = BCrypt.HashPassword(txtPass.Text.Trim().ToString(),BCrypt.GenerateSalt(12)); Infact, there is no txtHash textbox in user login form, it only has 2 textboxes, username and password. Then uses password value (txtPass.Text.Trim.ToString())with BCrypt.CheckPassword routine with hashpassdb (retrieve from database). txtHash textbox is used in the Form where new user is created with Username and password. It is actually hidden textbox, use only to save hash value of password in database.

[Garth J Lancaster]

Im sorry, I think you're missing the point - you're not getting the correct results because you're not comparing 'apples with apples' If you start with a password A And generate Hashed-Salted-Password-A (and then store Hashed-Salted-Password-A) And then want to compare that with Password B You have to compare Hashed-Salted-Password-A with HashPassword(Password B, Hashed-Salted-Password-A) 'g'

[ahmed_one]

Garth J Lancaster wrote:

Im sorry, I think you're missing the point - you're not getting the correct results because you're not comparing 'apples with apples'

Actually I am also trying to do the same, but what I don't understand is why it is not working. Let me re-phrase my problem without code: Form User Creation: 1.New User create with Username and Password, password is hashed and stored in db,using a hidden textbox (txtHash). Form User Login: 1. User enter username and password. 2. Get hashed password from db and stored it in hashpassdb string. 3. Now compare the user entered password with BCrypt.CheckPassword(txtPass.Text.Trim().ToString(), hashpassdb)) I know there is something wrong in logic behind User login form, but I am unable to track it. I've used breakpoints in BCrypt.Checkpassword function to check what values are in, and they are different. But the question is why?

[Garth J Lancaster]

ahmed_one wrote:

3. Now compare the user entered password with BCrypt.CheckPassword(txtPass.Text.Trim().ToString(), hashpassdb))

yes, but, arnt you doing something funky in txtPass.Leave event ? that means the result you get from

txtPass.Text.Trim().ToString()

is effectively

HashPassword(user entered password ,BCrypt.GenerateSalt(12));

?

[ahmed_one]

As you've quote point number 3, which is related to User login form, there is no txtPass.leave event used in User Login form. It is only used in User Creation Form, so ultimately there is no:

HashPassword(user entered password ,BCrypt.GenerateSalt(12));

Used for txtPass. It's the plaintext where user enter password. I know what you are trying to say, that when comparing password, what I am doing is to generate new hash due to the result of GenerateSalt(12). But this is not the case, I simply get hash value from db and put it in CheckPassword method alongwith plaintext password enter by user. I am sure BCrypt.GenerateSalt(12) is not call anywhere in UserLogin form. I am following this guide in my application.

[Garth J Lancaster]

ok, which version of BCrypt are you using ?

[ahmed_one]

Derek Slagers Bcrypt class. Downloaded from http://derekslager.com/blog/posts/2007/10/bcrypt-dotnet-strong-password-hashing-for-dotnet-and-mono.ashx[^]

[Garth J Lancaster]

There appears to be a more up-to-date version here http://bcrypt.codeplex.com/[^] Nonetheless, I did a quick and dirty test with that version you used with VS2005 :-

namespace DSBcryptTest
{
class Program
{
static void Main(string[] args)
{
String Password_Text = "Lorem_ipsum_dolor_sit_amet";

        String Password\_Hashed = BCrypt.HashPassword(Password\_Text, BCrypt.GenerateSalt(12));
        Console.WriteLine("Hashed Password {0}", Password\_Hashed);

        String Test\_Password\_Text = Password\_Text;

        if (BCrypt.CheckPassword(Test\_Password\_Text, Password\_Hashed))
        {
            Console.WriteLine("Passwords Match");
        }

    }
}

and there was nothing wrong / I got the expected result - obviously I should be using Nunit/unit tests etc, but meh ... I copied BCrypt.cs into a new project, removed the assembly directive at the top, then used it directly as opposed to the dll version - but that wouldn't matter - it just means I can step into the code So, Im sorry, I cant think of where to go

[ahmed_one]

Thanks for reply.

Garth J Lancaster wrote:

I copied BCrypt.cs into a new project, removed the assembly directive at the top, then used it directly as opposed to the dll version - but that wouldn't matter - it just means I can step into the code

I didn't get the above part "removed the assembly directive"?? what does it mean? I am also using BCrypt.cs file not the dll.. May be assembly directive has something to do with my problem?

[Garth J Lancaster]

nup, not the issue - you wouldn't even be able to build it if that were the issue - I had a 'Duplicate AssemblyVersion Attribute' error with the same in AssemblyInfo.cs - so I removed [assembly: System.Reflection.AssemblyVersion("0.1")] from near the top of my copy of BCrypt.cs All I proved was there's nothing obviously wrong with that version of BCrypt.cs, but it was only one test

[Garth J Lancaster]

btw - what is the length of the hashed password you get back from the DB ?

[ahmed_one]

Ok so may be I need to also test it with simple code, after the successful test I will add it to my project. I will let you know the result of test. Thanks

[ahmed_one]

BCrypt hashed password is returning 60 Char length in my case.

[ahmed_one]

I don't believe it...I've done hours and hours of testing and all of them is succeed...And guess what is the stupid mistake I was doing?? I've accidentally set CharacterCasing to upper when creating new user...And in Login Form it is set to default normal. Now it is working... Thanks for be patient with my stupidity. Ahmed

[Pete OHanlon]

Well done for fixing it. Don't be worried about it - we've all made mistakes like this at one time or another.

[ahmed_one]

Thanks....as a beginner these mistakes surely hard to find, but no doubt they make me learn something.....

[Garth J Lancaster]

as POH said 'well done' - you got there in the end 'next time', when using someone else's code, knock up a set of unit tests and make sure its working before you start coding against it in anger - that will eliminate it from the things you have to consider when it all looks pear-shaped 'g'

[ahmed_one]

Thanks...I will follow your guidelines..