You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/_data/changelog.yml
+21-1Lines changed: 21 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,23 @@
1
+
- date: '2026-02-19'
2
+
updates:
3
+
crypto_providers:
4
+
version: 6.0.1
5
+
breaking_changes:
6
+
- text: |
7
+
The Windows CSP component for the deprecated [Windows CAPI](https://docs.microsoft.com/en-us/windows/win32/seccrypto/cryptographic-service-providers) (Crypto API) is not longer supported.
8
+
- text: |
9
+
The following configuration settings have been removed: `Timeouts.HttpRequest`, `Timeouts.FirstRetryDelay` and `Timeouts.RetryCount`.
10
+
11
+
Instead, use the new settings `ServiceUnavailableTimeoutInSeconds` and `HttpRequestTimeoutInSeconds`.
12
+
13
+
See [timeout settings](/crypto-providers#timeout-settings) for details.
14
+
- text: |
15
+
The Cryptoki library for Windows is now provided as a separate download and not part of the Windows installer any more (see [download section](/crypto-providers#download)).
16
+
- text: |
17
+
Logging: new file naming scheme; now a single log file gets written instead of one per process (see [logging settings](/crypto-providers#crypto-provider-config-values-logging)).
18
+
new_features:
19
+
- text: The Crypto Providers are now available via stable links on our download share. See the [download section](/crypto-providers#download) for details.
20
+
issues: [SIGN-8265]
1
21
- date: '2026-02-17'
2
22
updates:
3
23
powershell_module:
@@ -940,7 +960,7 @@
940
960
- date: '2024-10-21'
941
961
updates:
942
962
macos_cryptotokenkit:
943
-
version: '2.0'
963
+
version: '2.0.0'
944
964
breaking_changes:
945
965
- text: 'Renamed the command-line parameters to align with the other client tools.'
These download links refer to the latest available {{ include.major }}.x version. This is recommended for automated downloads from build scripts. See <ahref="/changelog/">Product changes</a> for stable links to a specific version. SignPath Crypto Providers use <ahref="https://semver.org/">semantic versioning</a>.
Copy file name to clipboardExpand all lines: docs/crypto-providers/cryptoki.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,12 +34,13 @@ This section provides general information about using the SignPath Cryptoki libr
34
34
| RedHat | 8 (latest minor) |
35
35
| RedHat | 9 (latest minor) |
36
36
37
+
<!-- TODO: this panel (and the next?) is not needed any more - right -->
37
38
{:.panel.info}
38
39
> **Dependency on OpenSSL and `ca-certificates`**
39
40
>
40
41
> The Crypto Providers use OpenSSL internally to perform HTTPS requests. So the packages `openssl` and `ca-certificates` (which contains the HTTPS/TLS root certificates) must be present on your system.
41
42
>
42
-
> If you see log messages like `Error in SSL handshake`, these dependencies may be missing. You can test connectivity via the following command:
43
+
> If you see log messages like `Error in SSL handshake` or `The SSL connection could not be established`, these dependencies may be missing. You can test connectivity via the following command:
43
44
>
44
45
> ```bash
45
46
> curl https://app.signpath.io/Api/healthz
@@ -58,15 +59,11 @@ This section provides general information about using the SignPath Cryptoki libr
58
59
59
60
#### Windows
60
61
61
-
The Cryptoki library is installed to `%ProgramFiles%\SignPath\CryptoProviders\SignPath.Cryptoki.dll` by the [MSI installer](/crypto-providers/windows#installation).
62
-
63
-
Alternatively, you can copy-deploy `Windows\SignPath.Cryptoki.dll` from the Crypto Providers ZIP archive to your target system.
62
+
You can copy-deploy `SignPath.Cryptoki.dll` from the Crypto Providers `.zip` archive to your target system.
64
63
65
64
#### Linux
66
65
67
-
Copy-deploy the Cryptoki library `Linux/libSignPath.Cryptoki/$OpenSslVersion/libSignPath.Cryptoki.so` from the Crypto Providers ZIP archive to your target system.
68
-
69
-
Check the output of `openssl version` on your target system to selectthe correct OpenSSL version.
66
+
Copy-deploy the Cryptoki library `libSignPath.Cryptoki.so` from the Crypto Providers `.tar.gz` archive to your target system.
The SignPath Crypto Providers allow signing tools such as [SignTool.exe](/crypto-providers/windows#signtool), [OpenSSL](/crypto-providers/cryptoki#openssl) or [jarsigner](/crypto-providers/cryptoki#jarsigner) to sign files locally using keys or certificates stored and managed by SignPath.
14
14
15
-
Crypto Providers are generally used to provide a device-independent API for using secure key storage devices such as USB key tokens or Hardware Security Modules (HSMs). You may think of them as device drivers for crypto hardware. Most software tools used for code signing support one Crypto Provider technology, such as Microsoft KSP/CSP or PKCS #11 Cryptoki.
15
+
Crypto Providers are generally used to provide a device-independent API for using secure key storage devices such as USB key tokens or Hardware Security Modules (HSMs). You may think of them as device drivers for crypto hardware. Most software tools used for code signing support one Crypto Provider technology, such as Microsoft KSP or PKCS #11 Cryptoki.
16
16
17
17
The SignPath Crypto Providers do not access the crypto hardware directly. Instead, they implement these interfaces to provide access to SignPath _Projects_ and _Signing Policies_. During the entire operation, the private key will remain on the HSM.
18
18
19
19
{:.panel.info}
20
20
> **Version info**
21
21
>
22
-
> This documentation contains information about the latest version of the CryptoProviders. See the [CryptoProvider changelog](/changelog?component=crypto_providers) or the [macOS CryptoTokenKit changelog](/changelog?component=macos_cryptotokenkit) for updates.
22
+
> This documentation contains information about the latest version of the Crypto Providers. See the [Crypto Provider changelog](/changelog?component=crypto_providers) or the [macOS CryptoTokenKit changelog](/changelog?component=macos_cryptotokenkit) for updates.
23
23
24
24
### Crypto Providers
25
25
@@ -29,7 +29,6 @@ The following Crypto Providers are available for SignPath:
@@ -68,15 +67,21 @@ With small platform-specific variations, the general flow of a signing operation
68
67
69
68
As always, the private key does not leave the boundaries of the HSM.
70
69
71
-
## Installation and usage
70
+
## Download and installation {#download}
72
71
73
-
Depending on the signing tool you're using, the corresponding Crypto Provider needs to be installed (on all build nodes). See the respective pages:
72
+
Choose the correct package and install it on all build agents:
74
73
75
-
*[SignPath KSP and CSP](/crypto-providers/windows) for _SignTool.exe_ and most native Windows tools
76
-
*[SignPath Cryptoki](/crypto-providers/cryptoki) for _OpenSSL_, _jarsigner_, and many other Open Source tools
77
-
*[GPG-based tools](/crypto-providers/gpg), such as _gpg_, _rpm_, or _dkpg-sig_ use the [SignPath Cryptoki Crypto Provider](/crypto-providers/cryptoki) but require additional configuration steps
74
+
*[SignPath Windows KSP](/crypto-providers/windows) for _SignTool.exe_ and most native Windows tools
75
+
*[SignPath Cryptoki library](/crypto-providers/cryptoki) for _OpenSSL_, _jarsigner_, and many other Open Source tools
76
+
*[GPG-based tools](/crypto-providers/gpg), such as _gpg_, _rpm_, or _dkpg-sig_ use the [SignPath Cryptoki library](/crypto-providers/cryptoki) but require additional configuration steps
78
77
*[SignPath CryptoTokenKit](/crypto-providers/macos) for macOS _codesign_
79
-
* Instead of using a CryptoProvider, it is also possible to [sign hashes directly using the REST API](/crypto-providers/rest-api)
78
+
79
+
<!-- should really include notation_plugin here also and merge other PR -->
80
+
{% include download-cryptoproviders-panel.md major="6" components="cryptoki,windows_ksp" %}
81
+
82
+
{% include download-cryptoproviders-panel.md major="2" components="macos_cryptotokenkit" title_details="MacOS CryptoTokenKit" %}
83
+
84
+
Instead of using a CryptoProvider, it is also possible to [sign hashes directly using the REST API](/crypto-providers/rest-api)
80
85
81
86
## Configuration {#crypto-provider-configuration}
82
87
@@ -107,7 +112,7 @@ The [MSI installer](/crypto-providers/windows#installation) for Windows creates
107
112
You will usually specifiy the Project and Signing Policy and let SignPath select the matching certificate.
108
113
109
114
The following values
110
-
* should be provieded for other [PKCS #11/Cryptoki](cryptoki) signing tools that don't accept a _key ID_ parameter
115
+
* should be provided for other [PKCS #11/Cryptoki](cryptoki) signing tools that don't accept a _key ID_ parameter
111
116
* are internally used for GPG signing via PKCS #11 (see [GPG](gpg#configure-gnupg))
112
117
* can be provided for macOS CryptoTokenKit as default values (see [macOS](macos#usage-project-signing-policy))
Within `Log.File.Directory`/`SIGNPATH_LOG_FILE_DIRECTORY` the log file is named `SignPath.CryptoProviders.<Interface>.txt` (e.g. `SignPath.CryptoProviders.KSP.txt`). In case the log file would exceed 10 MB, the log file gets rotated (up to five "old" log file copies).
| `ServiceUnavailableTimeoutInSeconds` | `SIGNPATH_SERVICE_UNAVAILABLE_TIMEOUT_IN_SECONDS ` | `600` | Total time in seconds that the command will wait for a single service call to succeed (across several retries).
143
+
| `HttpRequestTimeoutInSeconds` | `SIGNPATH_HTTP_REQUEST_TIMEOUT_IN_SECONDS` | `30` | Timeout for HTTP calls in seconds per attempt
137
144
{: .break-column-2}
138
145
139
146
HTTP timeouts and 5xx server errors (e.g. 503 Service Unavailable errors) are treated as failed requests.
@@ -224,7 +231,7 @@ In order to perform hash-based signing with the Crypto Providers, perform the fo
224
231
225
232
### Linux samples {#linux-docker-samples}
226
233
227
-
The Crypto Provider package contains Linux sample scripts that demonstrate the use of different signing tools, their configuration, and the required dependencies in the `Scenarios` directory. See the `README.md` for the full list.
234
+
The Cryptoki package for Linux contains sample scripts that demonstrate the use of different signing tools, their configuration, and the required dependencies in the `Scenarios` directory. See the `README.md` for the full list.
228
235
229
236
For supported Linux distributions, you can execute the samples using the provided Docker container configurations. See the `Linux/Samples` directory in the Crypto Provider package. See `README.md` for further information and details how to use the `RunScenario.sh` and `RunScenario.ps1` entry point scripts to invoke samples.
0 commit comments