NSign.SignatureProviders
1.0.4
dotnet add package NSign.SignatureProviders --version 1.0.4
NuGet\Install-Package NSign.SignatureProviders -Version 1.0.4
<PackageReference Include="NSign.SignatureProviders" Version="1.0.4" />
paket add NSign.SignatureProviders --version 1.0.4
#r "nuget: NSign.SignatureProviders, 1.0.4"
// Install NSign.SignatureProviders as a Cake Addin #addin nuget:?package=NSign.SignatureProviders&version=1.0.4 // Install NSign.SignatureProviders as a Cake Tool #tool nuget:?package=NSign.SignatureProviders&version=1.0.4
NSign.SignatureProviders
Signature providers for signing and verifying signatures with NSign. This library currently supports both asymmetric
algorithms (using public-key cryptography) and symmetric algorithms (using HMAC). Signature providers typically
implement both the ISigner
and the IVerifier
interfaces, but implementation can also be split into separate classes.
Asymmetric Signature Algorithms
Currently, the following asymmetrics signature algorithms are supported:
- ECDSA using curve P-256 DSS and SHA-256 (
ecdsa-p256-sha256
in [^1]), in classECDsaP256Sha256SignatureProvider
- ECDSA using curve P-384 DSS and SHA-384 (
ecdsa-p384-sha384
in [^1]), in classECDsaP382Sha384SignatureProvider
- RSASSA-PSS using SHA-512 (
rsa-pss-sha512
in [^1]) in classRsaPssSha512SignatureProvider
- RSASSA-PKCS1-v1_5 using SHA-256 (
rsa-v1_5-sha256
in [^1]) in classRsaPkcs15Sha256SignatureProvider
These signature providers can all be created by passing an instance of X509Certificate2
and having the provider
extract the public key for signature verification from there. If the provider is to be used for signing, the certificate
that is provided must have a private key too, otherwise signing will fail / an exception will be thrown. Naturally,
the keys used in the certificate must match the key parameters/formats expected by the signature provider.
For instance, to use rsa-pss-sha512
with a PEM-encoded certificate in a file called the-cert.cer
for signature
verification, creating the provider as follows will do:
var provider = new RsaPssSha512SignatureProvider(
new X509Certificate2("the-cert.cer"),
"the-cert-key-id"))
To use rsa-pss-sha512
with a PFX file called the-cert.pfx
, holding the private key for message signing, a provider
can be created as follows:
var provider = new RsaPssSha512SignatureProvider(
new X509Certificate2("the-cert.pfx", "here-goes-the-password-to-the-PFX"),
"the-cert-key-id"))
Due to their nature, asymmetric signatures are often preferable over symmetric signatures because they do not require both the signing and verifying party to share a secret (the key). Instead, the public key can be published anywhere / through any means for verifiers to download and use.
Symmetric Signature Algorithms
Currently, the following symmetric signature algorithms are supported:
- HMAC using SHA-256 (
hmac-sha256
in [^1]), in classHmacSha256SignatureProvider
This signature provider requires the (shared) key to be provided during construction.
Further Information
See also:
[^1]: See section Signature Algorithms of HTTP Message Signatures (RFC 9421), https://www.rfc-editor.org/rfc/rfc9421.html#name-signature-algorithms
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 is compatible. 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 is compatible. 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. |
.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. |
-
.NETStandard 2.0
- NSign.Abstractions (>= 1.0.4)
-
net6.0
- NSign.Abstractions (>= 1.0.4)
-
net8.0
- NSign.Abstractions (>= 1.0.4)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories (1)
Showing the top 1 popular GitHub repositories that depend on NSign.SignatureProviders:
Repository | Stars |
---|---|
Letterbook/Letterbook
Sustainable federated social media built for open correspondence
|
Version | Downloads | Last updated |
---|---|---|
1.0.4 | 530 | 8/26/2024 |
1.0.3 | 1,815 | 6/17/2024 |
1.0.2 | 693 | 5/15/2024 |
1.0.1 | 1,332 | 3/20/2024 |
1.0.0 | 121 | 2/20/2024 |
0.19.3 | 131 | 2/13/2024 |
0.19.2 | 262 | 11/27/2023 |
0.19.1 | 650 | 10/9/2023 |
0.19.0 | 183 | 8/21/2023 |
0.17.0 | 193 | 5/12/2023 |
0.16.0 | 432 | 2/13/2023 |
0.15.3 | 340 | 1/19/2023 |
0.15.2 | 301 | 1/18/2023 |
0.15.1 | 329 | 1/16/2023 |
0.15.0 | 352 | 1/12/2023 |
0.10.0 | 459 | 6/8/2022 |
0.9.0 | 457 | 3/28/2022 |
0.8.3 | 461 | 3/10/2022 |
0.8.2 | 467 | 2/21/2022 |
0.8.1 | 430 | 2/21/2022 |
0.8.0 | 455 | 2/14/2022 |
0.2.0 | 310 | 1/4/2022 |
0.1.1 | 369 | 9/20/2021 |
0.1.0 | 329 | 9/17/2021 |