NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #783 most downloaded on NuGet
A fixed, enhanced and namespace compatible version of BCrypt.Net port of jBCrypt implemented in C#. It uses a variant of the Blowfish encryption algorithm’s keying schedule, and introduces a work factor, which allows you to determine how expensive the hash function will be, allowing the algorithm to be "future-proof".
Latest stable
4.2.0
Last release 6 months ago
11 May 2026
Ships unpredictably
gaps range from 8 days to 4.0 years
Most releases are documented
notes for 15 of 20 stable releases
6 versions withdrawn
withdrawn after publishing
127 years old
26 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Drops dotnet 2.0 / 3.5 support (as msft ripped it out of windows 11 and set the new standalone installers minimum windows version to an inside release
Full Changelog: v4.1.0...v4.2.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Bump xunit.runner.visualstudio from 2.4.3 to 2.4.4 by @dependabot [bot] in #107
Full Changelog: 4.0.3...v4.1.0
Bump Microsoft.NET.Test.Sdk from 16.7.1 to 16.8.0 by @dependabot-preview in https://github.com/BcryptNet/bcrypt.net/pull/77
Full Changelog: https://github.com/BcryptNet/bcrypt.net/compare/4.0.2...4.0.3
Sets using/dispose pattern on shaxxx usage in enhanced entropy version
*v4.0.0 (breaking changes)* - A bug in Enhanced Hashing was discovered that causes the hashes created to be inoperable between different languages. V4…
v4.0.0 (breaking changes) - A bug in Enhanced Hashing was discovered that causes the hashes created to be inoperable between different languages.
V4 provides the fix for this as well as adding test vectors from PHP and Python to ensure the issue remains fixed in the future. V4 also removes the legacy 384 option that came before Base64 was added.
See https://github.com/BcryptNet/bcrypt.net/releases
See https://github.com/BcryptNet/bcrypt.net/releases
A bug in Enhanced Hashing was discovered that causes the hashes created to be inoperable between different languages.
As part of the fix 3.5 release contains the ability to Verify and HashPassword were given an additional v4CompatibleEnhancedEntropy parameter.
This allows the user to verify their Enhanced hash as normal; then re-hash + store using V4. This functionality is purely to allow migration and is removed in V4.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Performance (heap reduction) and removal of regex
Performance (heap reduction) and removal of regex
Big thanks to Jos Vandertil (@jvandertil) for the help.
Nothing published for this version
Nothing published for this version
Resolves https://github.com/BcryptNet/bcrypt.net/issues/25 Added serializable attribute to exception types
Resolves https://github.com/BcryptNet/bcrypt.net/issues/25 Added serializable attribute to exception types
If you updated to 3.1.1 (now delisted), any credentials created using 3.1.1 will need resetting.
If you updated to 3.1.1 (now delisted), any credentials created using 3.1.1 will need resetting.
Test run
https://ci.appveyor.com/project/ChrisMcKee/bcrypt-net/build/tests
Adds HashType to EnhancedVerify and Verify.
Enhanced entropy defaults to SHA384 which is base64 encoded.
SHA384 which is base64 encoded.Nothing published for this version
Nothing published for this version
Enhanced entropy defaults to Legacy384 which is basically the way it operated prior to this version anyway this will be maintained for v2.
Legacy384 which is basically the way it operated prior to this version anyway this will be maintained for v2.Match versions between Strong-Signed / Normal package
https://github.com/BcryptNet/bcrypt.net/compare/2.1.1...62a57cd
https://github.com/BcryptNet/bcrypt.net/compare/2.1.1...62a57cd
Deployment made for typos/netstandard.
PasswordNeedsReshash to PasswordNeedsRehash- Minor csproj changes / typo
Adds enhanced mode; enhanced hashing allows you to opt-in to ensuring optimal entropy on your users passwords by first making use of the fast SHA384 a
PasswordNeedsReshash(string hash, int newMinimumWorkLoad) as a helper method for developers to use when logging a user in to increase legacy workloadsValidateAndReplacePassword method to allow inline password validation and replacement. Throws BcryptAuthenticationException in the event of authentication failure.Corrects usage of Secure random number generator
Fresh release packaged for the majority of .net & containing safe-equals to reduce the risks from timing attacks https://en.wikipedia.org/wiki/Timing_
Fresh release packaged for the majority of .net & containing safe-equals to reduce the risks from timing attacks https://en.wikipedia.org/wiki/Timing_attack / https://cryptocoding.net/index.php/Coding_rules#Compare_secret_strings_in_constant_time Technically the implementation details of BCrypt theoretically mitigate against a timing attacks. But the Bcrypt.net official validation function was vulerable to timing attacks as it returned as soon as a non-matching byte was found in the hash comparison..
https://www.nuget.org/packages/BCrypt.Net-Next/2.0.0
One column per quarter.