Repository navigation
Releases
Releases · ebourg/jsign
7.6
- The Azure credentials can now be specified with
--storepass <tenantId>|<clientId>|<clientSecret>
or with theAZURE_TENANT_ID,AZURE_CLIENT_IDandAZURE_CLIENT_SECRETenvironment variables - Jsign can now open read-only or locked files
- MSI files are no longer mapped into memory (this solves write issues on Windows with mounted volumes)
- The terminally deprecated method warning displayed when signing MSI files has been fixed (from the build tools and the API)
- The "missing provider" error with the Jsign JCA provider has been fixed (contributed by Lukas Schmitt)
- The Maven plugin no longer timestamps the signature by default (contributed by Daniel Fischer)
- The Gradle plugin published on the Gradle plugin portal is compiled with Java 8 again
- Upgraded Bouncy Castle LTS to 2.73.13
7.5
- The "Unknown JSON value type" error with DigiCert ONE has been fixed (contributed by Rhys Hansen)
- An Azure Trusted Signing endpoint with a trailing slash no longer causes a 404 error
- The terminally deprecated method warning displayed when signing MSI files has been fixed (from the command line only)
- LDAP URLs in the Authority Information Access attribute are now ignored and no longer cause an error
- The Yubikey PKCS#11 library is now also searched in the Homebrew installation directory (
/opt/homebrew/lib/)
used on Apple Silicon and on DYLD_LIBRARY_PATH (contributed by ye4241)
7.4
- The CryptoCertum cryptographic card is now supported with the new
CRYPTOCERTUMstoretype (no PKCS#11 module required) - The new command line option
--versiondisplays the version of Jsign - The certificate chain is no longer fetched from the keystore when the
certfileparameter is specified - Upgraded Bouncy Castle LTS to 2.73.9
7.3
- Multiple signatures are now supported for EFI files
- The root and intermediate certificates stored in the PIV slots 82 to 95 are now used to build the certificate chain
- Self-signed certificates are no longer removed from the certificate store embedded in the signature (contributed by Christian Renz)
- The proxy settings are now applied to the connections to the cloud signing services
- API changes:
- New
Signable.setSignatures(List<CMSSignedData>)method to set multiple signatures (nesting is handled automatically) SignatureUtils.getSignatures()now removes the nested signatures from the first signature in the list
- New
7.2
- ECS container credentials are now supported when signing with AWS KMS (contributed by Alejandro González)
- The
keystoreparameter can now be specified with theETOKENstoretype to distinguish between multiple connected devices - The Gradle plugin can now sign multiple files by defining a fileset
- The command line tool on Windows now works even if the installation path contains a space (contributed by Tres Finocchiaro)
- The file handle is now properly closed when probing the file format
- The error handling with DigiCert ONE has been improved (contributed by Alejandro González)
- Upgraded Bouncy Castle LTS to 2.73.8
7.1
- New signing service: SignPath
- The "Unsupported file" error when using the Ant task has been fixed
- The
timestampandtagcommands have been fixed for MSI, catalog and script files - The RPM package no longer removes the installation directory when upgrading
- The
--debug,--verboseand--quietparameters now work for all commands
7.0
- New signing services:
- Azure Trusted Signing
- Oracle Cloud
- GaraSign
- HashiCorp Vault Transit (contributed by Eatay Mizrachi)
- Keyfactor SignServer (contributed by Björn Kautler)
- Signing of NuGet packages has been implemented (contributed by Sebastian Stamm)
- Commands have been added:
timestamp: timestamps the signatures of a filetag: adds unsigned data (such as user identification data) to signed filesextract: extracts the signature from a signed file, in DER or PEM formatremove: removes the signature from a signed file
- The intermediate certificates are downloaded if missing from the keystore or the certificate chain file
- File list files prefixed with
@are now supported with the command line tool to sign multiple files - Wildcard patterns are now accepted by the command line tool to scan directories for files to sign
- Jsign now checks if the certificate subject matches the app manifest publisher before signing APPX/MSIX packages (with contributions from Scott Cooper)
- The new
--debug,--verboseand--quietparameters control the verbosity of the output messages - The JCA provider now works with apksigner for signing Android applications
- RSA 4096 keys are supported with the
PIVstoretype (for Yubikeys with firmware version 5.7 or higher) - Certificates using an Ed25519 or Ed448 key are now supported (experimental)
- Signatures on MSI files with gaps in the mini FAT are no longer invalid
- The APPX/MSIX bundles are now signed with the correct Authenticode UUID
- The signed APPX/MSIX files no longer contain a
[Content_Types].oldentry - The error message displayed when the password of a PKCS#12 keystore is missing has been fixed
- The log4j configuration warning displayed when signing a MSI file has been fixed (contributed by Pascal Davoust)
- The value of the
storetypeparameter is now case insensitive - The Azure Key Vault account no longer needs the permission to list the keys when signing with jarsigner
- The DigiCert ONE host can now be specified with the
keystoreparameter - The
AWS_USE_FIPS_ENDPOINTenvironment variable is now supported to use the AWS KMS FIPS endpoints (contributed by Sebastian Müller) - On Windows the YubiKey library path is automatically added to the PATH of the command line tool
- Signing more than one file with the
YUBIKEYstoretype no longer triggers aCKR_USER_NOT_LOGGED_INerror - MS Cabinet files with a pre-allocated reserve are now supported
- The
--certfileparameter can now be used to replace the certificate chain from the keystore - PVK and PEM key files are now properly loaded even if the extension is not recognized (contributed by Alejandro González)
- API changes:
- The keystore builder and the JCA provider are now in a separate
jsign-cryptomodule - The PEFile class has been refactored to keep only the methods related to signing
- The java.util.logging API is now used to log debug messages under the
net.jsignlogger Signableimplementations are now discovered dynamically using the ServiceLoader mechanismSignable.createContentInfo()has been replaced withSignable.createSignedContent()
- The keystore builder and the JCA provider are now in a separate
- Switched to BouncyCastle LTS 2.73.7
6.0
- Signing of APPX/MSIX packages has been implemented (thanks to Maciej Panek for the help)
- Signing of Microsoft Dynamics 365 extension packages has been implemented
- PIV cards are now supported with the new
PIVstoretype - SafeNet eToken support has been improved with automatic PKCS#11 configuration using the new
ETOKENstoretype - The certificate chain in the file specified by the
certfileparameter can now be in any order - VBScript, JScript and PowerShell XML files without byte order marks are now parsed as Windows-1252 instead of ISO-8859-1
- The
keystoreparameter can now be specified with theOPENPGPstoretype to distinguish between multiple connected devices - The format detection based on the file extension is now case insensitive (contributed by Mathieu Delrocq)
- Only one call to the Google Cloud API is performed when the version of the key is specified in the alias parameter
- JVM arguments can now be passed using the
JSIGN_OPTSenvironment variable - API changes:
- New
net.jsign.jca.JsignJcaProviderJCA security provider to be used with other signing tools such as jarsigner - The signature can be removed by setting a null signature on the
Signableobject Signable.computeDigest(MessageDigest)has been replaced bySignable.computeDigest(DigestAlgorithm)- The value of the
http.agentsystem property is now appended to the User-Agent header when calling REST services AuthenticodeSignersets the security provider automatically if the keystore used is backed by a PKCS#11 token or a cloud serviceAmazonSigningServicenow supports dynamic credentials
- New
- Upgraded BouncyCastle to 1.77
5.0
- The AWS KMS signing service has been integrated (with contributions from Vincent Malmedy)
- Nitrokey support has been improved with automatic PKCS#11 configuration using the new
NITROKEYstoretype - Smart cards are now supported with the new
OPENSCstoretype - OpenPGP cards are now supported with the new
OPENPGPstoretype - Google Cloud KMS via HashiCorp Vault is now supported with the new
HASHICORPVAULTstoretype (contributed by Maria Merkel) - The Maven plugin can now use passwords defined in the Maven settings.xml file
- The "X.509 Certificate for PIV Authentication" on a Yubikey (slot 9a) is now automatically detected
- SHA-1 signing with Azure Key Vault is now possible (contributed by Andrij Abyzov)
- MSI signing has been improved:
- MSI files with embedded sub storages (such as localized installers) are now supported
- Signing a MSI file already signed with an extended signature is no longer rejected
- An issue causing some MSI files to become corrupted once signed has been fixed
- A user friendly error message is now displayed when the private key and the certificate don't match
- Setting
-Djava.security.debug=sunpkcs11with theYUBIKEYstoretype no longer triggers an error - The cloud keystore name is no longer treated as a relative file by the Ant task and the Maven plugin
- The paths are resolved relatively to the Ant/Maven/Gradle subproject or module directory instead of the root directory
- Signing with SSL.com eSigner now also works when the malware scanning feature is enabled
- API changes:
- The
KeyStoreUtilsclass has been replaced byKeyStoreBuilder
- The
- Upgraded BouncyCastle to 1.73
4.2
- Signing of Windows catalog files has been implemented
- The syntax to invoke the Gradle plugin with the Kotlin DSL has been simplified
- Several OutOfMemoryError caused by invalid input files have been fixed (thanks to OSS-Fuzz)
- API changes:
- The Signable interface now extends Closeable and can be used in try-with-resources blocks
- Files are no longer closed after signing
- Most parsing errors are now rethrown as IOException
- Upgraded BouncyCastle to 1.71.1