Hi All,
A new version of Signotaur has been released and is available from Signotaur Downloads. The latest stable version of Signotaur is 2.1.0.278.
Changes in v2.1.0.278
New Enterprise Features
-
Document signing.
SignotaurToolcan now produce ETSI Advanced Electronic Signatures as well as code signatures. XML files are signed as XAdES and PDFs as PAdES; other files can be signed as CAdES with--format cades. Choose the signature level with--level:baseline,timestamped,long-termorarchival. Long-term and archival signatures embed the certificate chain and revocation evidence, helping them to remain verifiable after the signing certificate expires. PDF signatures can have a visible appearance, and encrypted PDFs can be signed. Theverifycommand recognises all three formats. -
Document-signing certificates. Document-signing certificates can now be registered alongside code-signing certificates, or issued from the Internal CA or Microsoft AD CS. Certificates issued by Signotaur carry the Microsoft, Adobe and RFC 9336 document-signing usages, so they are accepted by Adobe Acrobat and by other verifiers. Certificates registered before upgrading are recorded as code signing; re-register one to pick up a second purpose.
-
Validation Authority. The Internal CA can now publish revocation information for the certificates it issues, answering OCSP requests and publishing CRLs and CA certificates, optionally over a dedicated plain HTTP port. Certificates can be revoked from the managed certificates list, and are revoked automatically when deleted or replaced by a renewal. The CRL and CA certificates can also be published to an external destination over SFTP, FTP/FTPS, WebDAV or S3-compatible storage, so that revocation can be checked from outside your network. Only certificates issued after the Validation Authority is enabled carry its addresses; existing certificates cannot be updated.
-
Multiple Intermediate CAs. The Internal CA is no longer limited to a single intermediate. Several can now be added, each scoped to web (TLS), code signing, document signing or all purposes. Each can be reissued or paused independently. Existing installations keep their current intermediate as an all-purpose one.
-
Certificate identities and policies. Issued signing certificates can now carry a full structured subject following ETSI EN 319 412-2/-3, identifying either a natural person or an organisation, with email addresses as subject alternative names. Renewal preserves the whole subject rather than reducing it to the common name. Certificates can also state the ETSI EN 319 411-1 policy they were issued under (LCP, NCP or NCP+), with an optional link to your CP/CPS.
Improvements
-
The managed certificates list gains a Certificate authorities view, showing each Root with its Intermediate CAs nested beneath it, and now marks both the certificate currently served by the web interface and any revoked certificates. A whole certificate chain can be downloaded as a single PEM or
.p7bfile. -
The Code Signing Certificates page is now Signing Certificates, and both it and My Certificates gain a Purpose column and filter where document signing is licensed. My Certificates now shows the same certificate details as the administration page.
-
Renewal now re-signs a certificate under the intermediate that originally issued it rather than the newest one, so a certificate no longer moves to a different CA.
-
Regenerating the Root CA no longer requires a restart unless the web certificate was issued by the Internal CA and must also be reissued.
-
Website Settings now warns that changing the server address will make the revocation addresses already stored in issued certificates unreachable.
Changes
-
The signing certificate’s purpose is now enforced before signing begins. If the certificate is unsuitable for any artefact in a batch, the entire run fails without signing anything; previously, signing continued regardless. Certificates whose Key Usage permits neither digital signature nor non-repudiation are also refused. Pass
--warn-wrong-purposeto warn and sign anyway. Verification reports these conditions as warnings, so existing signatures still verify. -
An unsupported file type now stops a signing run before anything is signed, rather than after part of the batch has already been signed. Use
--continue-on-failto sign the rest of the batch, as before. -
SignotaurToolnow returns dedicated exit codes for invalid or mutually exclusive arguments, unsuitable certificates, document-signing timestamp failures, invalid input formats and rate-limited requests. It also returns a new code when document signing is not licensed. Existing codes have not been renumbered, but some failures previously returned a different, generic or success code, so check any pipeline that depends on specific codes against the exit code reference. -
The server now identifies the occupied port and returns a dedicated exit code when it cannot start because the website port is already in use.
Bug Fixes
- Fixed automatic web-certificate renewal failing because the stored AD CS password was not decrypted.
- Fixed certificate issuance failing with an unclear error when the requested validity extended beyond the issuing CA’s expiry. The validity is now capped at the issuer’s expiry.
- Fixed an AD CS root or intermediate being shown in place of the Internal CA’s own on servers using both.
- Fixed overlapping column headers on the certificate tables.
- Fixed renewed certificates not being marked as superseded on My Certificates.
- Reworked several settings and certificate forms to react correctly to edits, fixing cases where the Save button could remain disabled.
Infrastructure
- The server now requires .NET Runtime 10.0.10; the installer installs it if it is missing.
- Various third-party package updates.