Bump net.jsign:jsign-core from 6.0 to 7.6

[dependabot]

Bumps net.jsign:jsign-core from 6.0 to 7.6.

Release notes

Sourced from net.jsign:jsign-core's releases.

7.6

• The Azure credentials can now be specified with --storepass <tenantId>|<clientId>|<clientSecret> or with the AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_SECRET environment 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 CRYPTOCERTUM storetype (no PKCS#11 module required)
• The new command line option --version displays the version of Jsign
• The certificate chain is no longer fetched from the keystore when the certfile parameter 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

7.2

• ECS container credentials are now supported when signing with AWS KMS (contributed by Alejandro González)
• The keystore parameter can now be specified with the ETOKEN storetype 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 timestamp and tag commands have been fixed for MSI, catalog and script files
• The RPM package no longer removes the installation directory when upgrading
• The --debug, --verbose and --quiet parameters now work for all commands

... (truncated)

Commits

• edc7b87 Release version 7.6
• 298ecf2 Upgraded Bouncy Castle LTS to 2.73.13 (#363)
• db48ba7 The Maven plugin no longer timestamps by default (Fixes #366)
• 0cb85cb No longer map MSI files into memory (Fixes #365)
• 1ac1c90 Fixed the title of the man page
• db843d7 Update the date in the man page at build time
• b36e23c Fixed a typo in the documentation
• 375d304 Azure authentication with credentials (Fixes #313, #319)
• 0b1f75a Disabled Bouncy Castle NativeLoader debug logging
• eee8b75 Initialize the read-write POI filesystem only when needed
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)