Bcrypt vs identiy encryption

Question

0.00/5 (No votes)

See more:

I'm in the process of implementing Identity for access control on a .Net Core application.

How does its password hashing compare to Bcrypt and is there a case for replacing it with Bcrypt?

What I have tried:

NA, this is a request for opinions rather than assistance

Posted 11-Oct-18 23:43pm

Ger Hayden

Updated 12-Oct-18 3:50am

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2018-10-12T00:40:00

Solution 1

BCrypt is a hashing function!.
It's just deliberately slow to make it harder to brute force: Hashing in Action: Understanding bcrypt[^]

Posted 12-Oct-18 0:40am

OriginalGriff

Comments

Ger Hayden 12-Oct-18 6:45am

I'm happy with slow and the concept of faking the hash time in the event of an invalid username being provided to disguise that Bcrypt has not fired. Is it any better than the hashing that comes as standard with Identity?

MadMyche · Accepted Answer · 2018-10-12T03:50:00

Solution 2

In my opinion you are fine with using Identity the way it is; it is using PBKDF2+HMAC-SHA and most likely any flaws will be in the code using it as opposed to the algorithm itself.

You can read up on what Identity uses here:
Exploring the ASP.NET Core Identity PasswordHasher[^]

Posted 12-Oct-18 3:50am

MadMyche