Skip to content

Commit 2f87751

Browse files
authored
Merge pull request #50 from SignPath/SP_1.211
Add change logs for 1.211
2 parents b7a05ec + 1f984d0 commit 2f87751

2 files changed

Lines changed: 47 additions & 3 deletions

File tree

docs/_data/changelog.yml

Lines changed: 37 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,38 @@
1+
- date: '2026-05-07'
2+
updates:
3+
application:
4+
version: 1.211.0
5+
new_features:
6+
- text: |-
7+
[`<jar-sign>`](/artifact-configuration/reference#jar-sign) now supports ECDSA certificates.
8+
issues: [SIGN-8347]
9+
- text: |-
10+
New `hash-algorithm` and `manifest-hash-algorithm` options for [`<jar-sign>`](/artifact-configuration/reference#jar-sign).
11+
issues: [SIGN-8347]
12+
improvements:
13+
- text: |-
14+
When saving artifact configurations, they don't have to start with an XML declaration anymore (`<?xml ...`).
15+
issues: [SIGN-8409]
16+
- text: |-
17+
Attempting to sign using certificates which aren't valid _yet_, or have been expired recently now aborts with a specific error message.
18+
issues: [SIGN-7586]
19+
- text: |-
20+
Attempting to sign PowerShell files with UTF-16 _big endian_ now results in a specific error message (not supported by Authenticode).
21+
issues: [SIGN-8392]
22+
bug_fixes:
23+
- text: |-
24+
Fixed: some signing policy and artifact configuration drop-down list entries were missing in the new signing request list UI.
25+
issues: [SIGN-8512]
26+
self_hosted_installations:
27+
version: 1.211.0
28+
breaking_changes:
29+
- text: |-
30+
SignService breaking change: an internal API change requires a manual update. Follow the steps in the section _Update SignService with breaking changes_ of the installation guide.
31+
issues: [SIGN-8325]
32+
improvements:
33+
- text: |-
34+
Improved resilience on temporary SQL connection outages.
35+
issues: [SIGN-8533]
136
- date: '2026-04-28'
237
updates:
338
jenkins_plugin:
@@ -1363,8 +1398,8 @@
13631398
version: 1.169.0
13641399
breaking_changes:
13651400
- text: |-
1366-
Internal SignService API breaking change: when upgrading from a version below 1.165, follow the _SignService breaking changes_ steps in the installation guide, section "Version compatibility".
1367-
1401+
SignService breaking change: an internal API change requires a manual update when upgrading from a version below 1.165. Follow the steps in the section _Update SignService with breaking changes_ of the installation guide.
1402+
13681403
Details: All file-based signing operations have been removed from the SignService API. Since version 1.165, all file-based signing operations have been executed by `signing-processor-service`.
13691404
issues: [SIGN-6589]
13701405
- date: '2024-07-23'

docs/artifact-configuration/reference.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -181,6 +181,15 @@ Note that not all OPC-based formats use OPC signatures:
181181

182182
{%- include_relative render-ac-directive-table.inc directive="jar-sign" -%}
183183

184+
**Supported options:**
185+
186+
| Option | Default value | Available values | Description
187+
|---------------------------|----------------|------------------------------|---------------------------------------------------
188+
| `manifest-hash-algorithm` | `sha256` | `sha256`, `sha384`, `sha512` | Hash algorithm to use when digesting the entries of a JAR file for the manifest file (`META-INF/MANIFEST.MF`) and the `META-INF/*.SF` file. Corresponds to the [`jarsigner -digestalg`][jarsigner-options] parameter.
189+
| `hash-algorithm` | `sha256` | `sha256`, `sha384`, `sha512` | Hash algorithm to use for the actual signature. Corresponds to the hash algorithm specified with the [`jarsigner -digestalg`][jarsigner-options] parameter (the _signature algorithm_ is determined by the certificate's key).
190+
191+
[jarsigner-options]: https://docs.oracle.com/en/java/javase/26/docs/specs/man/jarsigner.html#options-for-jarsigner
192+
184193
##### Verification {#jar-sign-verification}
185194

186195
* **Java** always verifies signatures for client components. For server components, you will need to create a policy. Please consult the documentation of your application server or [Oracle's documentation](https://docs.oracle.com/javase/tutorial/security/toolsign/receiver.html).
@@ -840,4 +849,4 @@ slsa-verifier verify-vsa \
840849
[RFC 5652]: https://datatracker.ietf.org/doc/html/rfc5652
841850
[Secure Systems Lab]: https://ssl.engineering.nyu.edu/
842851
[SignPath_SLSA.pem]: /assets/other/SignPath_SLSA.pem
843-
[SignPath_SLSA-Beta.pem]: /assets/other/SignPath_SLSA-Beta.pem
852+
[SignPath_SLSA-Beta.pem]: /assets/other/SignPath_SLSA-Beta.pem

0 commit comments

Comments
 (0)