https://github.com/datajuggler/datajuggler.cryptography
DataJuggler.Cryptography has been updated to .NET 9.
https://github.com/datajuggler/datajuggler.cryptography
Last synced: 5 months ago
JSON representation
DataJuggler.Cryptography has been updated to .NET 9.
- Host: GitHub
- URL: https://github.com/datajuggler/datajuggler.cryptography
- Owner: DataJuggler
- Created: 2021-11-18T02:08:20.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2024-11-22T23:33:25.000Z (over 1 year ago)
- Last Synced: 2025-07-04T08:29:17.111Z (12 months ago)
- Language: C#
- Homepage:
- Size: 44.9 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: License/License.txt
Awesome Lists containing this project
README
# Nuget Package Name: DataJuggler.Cryptography
This version is for .NET 9. Use a 8.x version for .NET 8, a 7.x for .NET 7.
# News
Update 11.21.2025: DataJuggler.Cryptography has been updated to .NET 10.
Update 11.19.2024: DataJuggler.Cryptography has been updated to .NET 9.
Update 11.20.2023: DataJuggler.UltimateHelper was updated.
Update 11.14.2023: DataJuggler.Cryptography has been updated to .NET 8.
Update 8.13.2023: DataJuggler.UltimateHelper was updated.
Update: 7.16.2023
I opened this project for the first time in a long time, and discovered the constructor for
Rfc2898DeriveBytes was deemed obsolete. I changed the HashAlgorithm name to
HashAlgorithmName.SHA512. This probably breaks any existing users, and for that I apologize.
# DataJuggler.Cryptography
This is a port of CryptographyHelper from DataJuggler.Core.UltimateHelper for dot net framework. This class uses System.Security.AesManaged for encrypt / decryption and Konscious.Security.Cryptography.Argon2 by Keef Aragon for password hashing.
This is a copy of CryptographyHelper class from DataJuggler.Core.UltimateHelper for
the .Net Framework. Originally I added this class to the Dot Net Core version
of UltimateHelper called DataJuggler.UltimateHelper.Core, but Nuget needs to add about
50 or 60 packages for Argon2, so I moved this class to its own library.
To use this package:
Install Package: DataJuggler.Cryptography
There are two main functions for the project:
1. Encryption / Decryption, with or without an encryption key using System.Security.Cryptography.AesManaged
2. Password Hashing using Konscious.Security.Cryptography.Argon2
To use in your own projects after you install the package via Nuget
using DataJuggler.Cryptography;
There is a constant available called DefaultPassword. The Encryption / Decryption methods and the GeneratePasswordHash
methods contain overrides that allow you to supply your own keyCode or you may use the DefaultPassword:
# Default Password
public const string DefaultPassword = "NotASecret";
# Encryption
public static string EncryptString(string stringToEncrypt, string password)
To encrypt a string, call the EncryptString method
To use your own password
string encrypted = CryptographyHelper.EncryptString(stringToEncrypt, password);
To use default password
string encrypted = CryptographyHelper.EncryptString(stringToEncrypt);
The encryption algorithm will return a different result every time you encrypt a string.
# Decryption
public static string DecryptString(string stringToDecrypt, string password)
You muse use the same password key to decrypt a string that you used to encrypt.
To use your own password
string decrypted = CryptographyHelper.DecryptString(stringToDecrypt, password);
To use default password
string decrypted = CryptographyHelper.DecryptString(stringToDecrypt);
# Password Hashing
public static string GeneratePasswordHash(string password, string keyCode)
This method hashes the password using Konscious.Security.Cryptography's implementation of Argon2 by Keef Aragon.
# Salt
Source: https://learncryptography.com/hash-functions/password-salting
Password salting is the process of securing password hashes from something called a Rainbow Table attack. The problem with non-salted passwords is that they do not have a property that is unique to themselves – that is, if someone had a precomputed rainbow table of common password hashes, they could easily compare them to a database and see who had used which common password. A rainbow table is a pre-generated list of hash inputs to outputs, to quickly be able to look up an input (in this case, a password), from its hash. However, a rainbow table attack is only possible because the output of a hash function is always the same with the same input.
(I didn't want to try and define salt because I knew I would not do it justice).
The salt is returned with the password separated by 4 | pipe characters.
You can decrypt the encrypted password hash to determine the password hash and salt, but you
cannot decrypt from password hash back to the original password.
# To generate a Password Hash using your own keyCode
string passwordHash = CryptographyHelper.GeneratePasswordHash(password, keyCode);
# To generate a Password Hash using your the default keyCode
string passwordHash = CryptographyHelper.GeneratePasswordHash(password);
# VerifyHash
public static bool VerifyHash(string userTypedPassword, string keyCode, string storedPasswordHash)
To implement login functionality you need to verify the user typed in password can verify against your stored password hash.
If you supplied a keyCode to generate a password hash you must supply the same keyCode to verify.
To verify using your own keyCode
bool verifiedLogin = CryptographyHelper.VerifyHash(userTypedInPassword, keyCode, storedPasswordHash);
To verify using default keyCode
bool verifiedLogin = CryptographyHelper.VerifyHash(userTypedInPassword, storedPasswordHash);
# How VerifyHash works
Your storedPasswordHash is first decrypted using either the supplied keyCode or the DefaultPassword of NotASecret depending on which override you called.
The result will then contain a string made up of the passwordHash followed by a separator of 4 pipe characters in a row |||| and then the salt.
This is an example, just to show the decrypted text of the password hash uses Unicode characters
憭紷줧悐纴Ꮄ⫘||||䣿別坵ࠀ恆쁿냞
Next the PasswordHash is determined from the left half of the 4 pipe characters.
The salty string is the characters after the 4 pipe characters.
Both salt and storedHash are both byte arrays.
byte[] salt = null;
byte[] storedHash = null;
// get the index
int index = decryptedHash.IndexOf("||||");
// if the index was found
if (index >= 0)
{
// get the password
password = decryptedHash.Substring(0, index);
salty = decryptedHash.Substring(index + 4);
salt = Encoding.Unicode.GetBytes(salty);
storedHash = Encoding.Unicode.GetBytes(password);
}
At this point, the salt and storedHash should be loaded, so we can call another verifyHash override.
public static bool VerifyHash(string password, byte[] salt, byte[] storedHash)
The verifyHash method creates a new passwordHash and compares it to the storedHash using Linq.
// generate the loginHash again
var newHash = HashPassword(password, salt);
// set the return value
verified = storedHash.SequenceEqual(newHash);
I just built a Blazor.Crypto sample, but I wanted to publish the Nuget package first.
The sample is located here:
https://github.com/DataJuggler/Blazor.Crypto