vm.Aspects.Security.Cryptography.Ciphers 2.1.4

.NET Standard 2.0 This package targets .NET Standard 2.0. The package is compatible with this framework or higher.
There is a newer prerelease version of this package available.
See the version list below for details. 
dotnet add package vm.Aspects.Security.Cryptography.Ciphers --version 2.1.4                

                    
                

            
NuGet\Install-Package vm.Aspects.Security.Cryptography.Ciphers -Version 2.1.4
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="vm.Aspects.Security.Cryptography.Ciphers" Version="2.1.4" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add vm.Aspects.Security.Cryptography.Ciphers --version 2.1.4                

                    
                

            
#r "nuget: vm.Aspects.Security.Cryptography.Ciphers, 2.1.4"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install vm.Aspects.Security.Cryptography.Ciphers as a Cake Addin
#addin nuget:?package=vm.Aspects.Security.Cryptography.Ciphers&version=2.1.4

// Install vm.Aspects.Security.Cryptography.Ciphers as a Cake Tool
#tool nuget:?package=vm.Aspects.Security.Cryptography.Ciphers&version=2.1.4

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.
           
           Features:
           * 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

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

  • .NETStandard 2.0

    • No dependencies.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on vm.Aspects.Security.Cryptography.Ciphers:

Package Downloads
vm.Aspects.Security.Cryptography.Ciphers.Xml

THE CLASSES FROM THE CIPHERS PACKAGES DO NOT IMPLEMENT ANY CRYPTOGRAPHIC ALGORITHMS. They leverage the cryptographic algorithms implemented by the .NET cryptographic service providers. This package extends vm.Aspects.Security.Cryptography.Ciphers with classes dependent on the System.Security.Cryptography.Xml. The library can be expected to work on Windows OS only until Microsoft defines and implements the System.Security.Cryptography.Xml in .NET Standard. The package depends on: - .NET Standard - System.Security.Cryptography.Xml - vm.Aspects.Security.Cryptography.Ciphers

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.1.5-beta.24 612 9/5/2018
2.1.4 3,447 9/3/2018
2.1.4-beta.24 522 9/5/2018

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.