Releases: daverayment/Cryptography.Fernet
Releases · daverayment/Cryptography.Fernet
Minor documentation fix
This release fixes an issue with the NuGet link to RELEASE.md
being at the wrong level. It also corrects some minor formatting issues in the same area of the NuGet UI.
v1.1.0
Version 1.1.0
New functionality
- A
saveTimestamp
parameter was added toEncrypt
. This defaults totrue
, which provides the same functionality as prior releases. Setting tofalse
means the token will be generated with a zeroed-out creation timestamp. This is a solution for certain scenarios where unencrypted timestamps such as Fernet's are regarded as sensitive information. Decrypt
now features automatic validation for 'clock drift' situations. This is where the decrypting system's internal clock differs from the system which generated the token. An exception is thrown if a token's creation timestamp is too far in the future. The maximum discrepancy is stored within theMaxClockDrift
TimeSpan in the main project'sFernet.cs
file.
Testing
A significant number of new tests were added to the unit test project, bringing the total up to more than 30:
- Tests added to exercise the entire specification, validation and generation documentation from the Fernet project repository.
- Tests added for the
Utility.Base64UrlEncoder
class.
Most tests now include at least summary documentation.
API Changes
Base64UrlEncoder.DecodeBytes
now throws aSystem.FormatException
instead of aSystem.ArgumentException
if the string passed in is invalid.
Documentation Fix
Updates
- Small update to ReadMe to correctly format icon link.
Initial Release
First deployment to NuGet. Encryption, Decryption, base64url utilities etc. all tested working. Unit test project included. Compatibility tested with Python implementation and token examples given in the specification repository.