Skip to main content
System.Security.Cryptography.Primitives package icon

System.Security.Cryptography.Primitives

Provides common types for the cryptographic libraries. Commonly Used Types: System.Security.Cryptography.ICryptoTransform System.Security.Cryptography.AsymmetricAlgorithm System.Security.Cryptography.SymmetricAlgorithm System.Security.Cryptography.HashAlgorithm System.Security.Cryptography.KeyedHashAlgorithm System.Security.Cryptography.HMAC System.Security.Cryptography.KeySizes System.Security.Cryptography.CryptographicException System.Security.Cryptography.CipherMode System.Security.Cryptography.PaddingMode System.Security.Cryptography.CryptoStream System.Security.Cryptography.CryptoStreamMode When using NuGet 3.x this package requires at least version 3.4.

Total Downloads
2.9B
2,858,800,583
Published
Jun 27, 2016
Latest stable version

Install

.NET CLI
dotnet add package System.Security.Cryptography.Primitives --version 4.0.0
Package Manager Console
Install-Package System.Security.Cryptography.Primitives -Version 4.0.0
PackageReference
<PackageReference Include="System.Security.Cryptography.Primitives" Version="4.0.0" />

Frameworks

MonoAndroid1.0 MonoTouch1.0 .NETFramework4.6 .NETStandard1.3 Xamarin.iOS1.0 Xamarin.Mac2.0 Xamarin.TVOS1.0 Xamarin.WatchOS1.0

Dependencies

[4.0.11, )
System.Globalization
.NETStandard1.3
[4.0.11, )
System.IO
.NETStandard1.3
[4.1.0, )
[4.0.1, )
System.Runtime
.NETStandard1.3
[4.1.0, )
System.Threading
.NETStandard1.3
[4.0.11, )
System.Threading.Tasks
.NETStandard1.3
[4.0.11, )

Adoption guide

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

Compatibility metadata lists 8 target frameworks; confirm the exact target used by your application.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.