Aspects. Security. Cryptography. Ciphers
THE CLASSES FROM THE CIPHERS PACKAGES DO NOT IMPLEMENT ANY CRYPTOGRAPHIC ALGORITHMS. They leverage the cryptographic algorithms implemented by the .NET cryptographic service providers.
The Ciphers package helps in addressing a common application requirement for achieving confidentiality, integrity and source authentication of data-at-rest, data-in-motion, and data-in-use, e.g. for PII (Personally Identifiable Information) fields.
* The package uses industry strong cryptographic algorithms for encryption, hashing and signing included in the .NET framework.
* It is very easy to integrate with a Dependency Injection container like Unity, i.e. the behaviors are abstracted with a handful of simple interfaces.
* It is very easy to use and configure the objects. Omitting configuration parameters defaults to sensible defaults.
* The package depends on:
- .NET Standard
This package will only be available to download with SemVer 2.0.0 compatible NuGet clients, such as Visual Studio 2017 (version 15.3) and above or NuGet client 4.3.0 and above. Read more
Install-Package vm.Aspects.Security.Cryptography.Ciphers -Version 2.1.5-beta.24
dotnet add package vm.Aspects.Security.Cryptography.Ciphers --version 2.1.5-beta.24
<PackageReference Include="vm.Aspects.Security.Cryptography.Ciphers" Version="2.1.5-beta.24" />
paket add vm.Aspects.Security.Cryptography.Ciphers --version 2.1.5-beta.24
Note: this package inherits from the Ciphers package but the name has changed for consistency's sake with the other vm.Aspects packages.
Refactored the library to drop the dependency on Common Service Locator - no assumption of DI container anymore.
Refactored a number of c-tors to take additional dependencies, which were previously resolved from the CSL.
Combined all key management utilities in one - KeyFile.
Added the utility FileCrypt that can encrypt and decrypt files (for more information run FileCrypt help/FileCrypt help encrypt/FileCrypt help decrypt)
The utilities KeyFile and FileCrypt are supported in source code form only: they are not packaged.
Refactored the utilities to use CommandLineParser.
Built and tested with .NET Standard 2.0.
- No dependencies.
This package is not used by any popular GitHub repositories.