Updates the salt hashing example in passwordhasher.cs for dotnet 6

[viniciusmorgado]

Updates the salt hashing example in passwordhasher.cs for dotnet 6 using RandomNumberGenerator instead RNGCryptoServiceProvider (outdated).

[guardrex]

Hello @viniciusmorgado ... Thanks for sending this in.

This change must be versioned, so inside this folder ...

https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/security/data-protection/consumer-apis/password-hashing/samples

... create 5.x and 6.x folders. Leave the existing file as it is and place it in the 5.x folder. Make your changes to a copy of the file and place it into the 6.x folder. In the article at ...

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/security/data-protection/consumer-apis/password-hashing.md

... structure the markdown for Lines 22-24 like this (and I'm adding in a little INCLUDE that we use now for reference source to help devs find the right version of ref source code) ...

:::moniker range=">= aspnetcore-6.0"

[!code-csharp[](password-hashing/samples/6.x/passwordhasher.cs)]

:::moniker-end

:::moniker range="< aspnetcore-6.0"

[!code-csharp[](password-hashing/samples/5.x/passwordhasher.cs)]

:::moniker-end

See the [source code](https://github.com/dotnet/AspNetCore/blob/main/src/Identity/Extensions.Core/src/PasswordHasher.cs) for ASP.NET Core Identity's `PasswordHasher` type for a real-world use case.

[!INCLUDE[](~/includes/aspnetcore-repo-ref-source-links.md)]

However, you might need to duplicate all of the content in the article if this change requires some or all of the earlier content (the paragraphs above the code link prior to Line 22) to change (i.e., the existing content is incorrect for 6.0 or later and/or the guidance needs to call out what's going on with the RandomNumberGenerator use). If that's the case, ping me back here, and I'll give you a new content versioning plan for the article.

[guardrex]

One more little thing ... GH prefers an LF at the ends of files ...

... so for the last line of passwordhasher.cs, tap the enter/return key to get on a new line. You'll see the warning indicator on the diff go away after you make that change to the file.

[guardrex]

@viniciusmorgado ... I'd prefer not to submit a commit to your PR to resolve this (I'm OOF until Friday); so if you feel like you'd like to leave the versioning updates to the team, then we'll either ping one of the other doc authors to commit to your branch or they'll close this and submit a new PR with all of the updates. Let me know how you would like to proceed. 👂

[Rick-Anderson]

Sample output shouldn't be changed.

[Rick-Anderson]

@viniciusmorgado @guardrex I'll get this cleaned up.

[guardrex]

Thx @Rick-Anderson 🍻!

[dnfadmin]

All CLA requirements met.

[viniciusmorgado]

@viniciusmorgado ... I'd prefer not to submit a commit to your PR to resolve this (I'm OOF until Friday); so if you feel like you'd like to leave the versioning updates to the team, then we'll either ping one of the other doc authors to commit to your branch or they'll close this and submit a new PR with all of the updates. Let me know how you would like to proceed. 👂

Thanks @guardrex

Hi @Rick-Anderson, I commit an update with the versioning of the passwordhasher.cs file, for the update of the content in password-hashing.md I need to duplicate all the content in the article, should I versioning the file as well? And can the file be versioned directly on aspnetcore\security\data-protection\consumer-apis? with two folders 5.x and 6.x as the passwordhasher.cs?

Edit1: Sorry I don´t answer @guardrex question, If someone on the team wants to close this request and submit a new PR with all of the updates it ´s ok to me.

[Rick-Anderson]

Thanks for the contribution. Be sure to check out your name as a contributor about the 3rd of next month on the What's new page in the Community contributors section at the bottom.