How to hash password in .NET

[@samuelbaron6741]

It's perfect this video!!! Could you make a video on folder structures? That's would be a great help to me and others, your code is very clean!

[@dingusdingus9899]

i agree

[@NoNameBack810]

Nice explanation, Thank you.

[@TuCominek]

Keep good work Remik thanks for the video❤

[@remigiuszzalewski]

Thanks for the feedback ❤

[@Tamer_Ali]

Thanks a lot for that useful video 👍.
Could your create a video tutorial of how to Encrypt and Decrypt data or QueryString value without using IDataProtector?
Because IDataProtector has a limited life time
and also because url coding cause decrypting issue with encrypted querystring value

[@remigiuszzalewski]

Thanks 😊 I was thinking about that topic for one of my future videos. Sooner or later it will be covered for sure!

[@lighr6886]

That was a really great video, by any change there is a video where you created that whole dependency injection container

[@remigiuszzalewski]

Thanks for the feedback 😁 You can check out how I built .NET 8 Web API with similar separation of dependencies in layers:
th-cam.com/video/g3is3wQK70Q/w-d-xo.html

[@frimen310]

Very useful. Thanks! :)

[@remigiuszzalewski]

You’re welcome! 😁

[@SocialExde]

Great Video, thanks. Can you tell me, which column type your HashedPassword-Column in users-table has?

[@remigiuszzalewski]

Thanks Deepert 😁. In my case it is normal varchar that was converted from the string type in c#

[@mau9175]

thank you!

[@BlackSkorpion123]

Why did you fill in the value of the Password Hasher fields in this form: "128/8"?

[@remigiuszzalewski]

It’s actually 16. I wanted to show that it came from 128 bits / 8 = 16 bytes of the SaltSize (which is recommended) ☺️

[@robgreene3956]

In the past, I have used a subset of the user email as part of the password. I did not need a separator between the salted part and the hashed password. In your opinion, how would my method compare to yours?

[@remigiuszzalewski]

I think that it does not matter. If you were able to normally retreive plain password after storing it that way then it is totally fine!

[@marcmcconnell]

@@remigiuszzalewski Except when the user needs to change their email address you will then need to rehash the password. That might be okay but it does mean the encrypted password will change whenever the email does.

[@jafetfigueroa9796]

thanks for your help I needed a video like this, May you make a video JWT authentication?

[@remigiuszzalewski]

Thanks a lot! Of course in the future there will be a video about JWT Auth

[@binojdaniel7]

What does your jwtGenerator do? can you share info about that?

[@remigiuszzalewski]

Hi Daniel, jwtGenerator is creating a JSON Web token (JWT) after the successful login in order to return it to the client. In that manner he will be authenticated based on that token when calling an endpoint that is marked as [Authorize] in our API

[@binojdaniel7]

@@remigiuszzalewski Can you go over the JWT and authorization code too in a video?

[@Farhan-ks2fq]

this great video, but do you have explanation for JWT in .netcore dudee ?

[@remigiuszzalewski]

Thanks 😁, for sure in the future I will create a video about JWT/other types of Auth

[@98pawi]

🔝

[@veniamingi2809]

can you explain, why u don t write SaltSiza = 16??

[@remigiuszzalewski]

It was just left as a reminder, that generally it came from 128 bits 😁

[@rs.wright]

While trying to verify my hashed password against the plaintext password, I was getting an error that the hashed password contained a malformed base64 string. Took me an hour or so to realize that I set up the password column in the db to only accept 50 characters... Hope someone else can learn from this one. 😅

[@mohammedidreesalikhan7341]

Please share GitHub link for this project

[@savage030_9]

First