Emmanuel Bourg
Emmanuel Bourg
Jsign doesn't depend on Mockito at runtime, it's only used in its tests and shouldn't interfere with your version of Mockito or Byte Buddy.
@nauni77 Did you figure out the issue?
> Can you reproduce the error? I can't sorry, maybe you could create a minimal test case triggering the error? The error occurs only with the ETOKEN storetype and not...
I get this: ``` >gradle :testEtoken --stacktrace > Task :testEtoken CodeSigningTestETOKEN > testSigning() FAILED java.lang.IllegalStateException at DefaultCacheAwareContextLoaderDelegate.java:180 Caused by: org.springframework.boot.context.config.ConfigDataLocationNotFoundException at ConfigDataEnvironment.java:391 1 test completed, 1 failed > Task :testEtoken...
I don't have an Etoken to test unfortunately. What happens if you wrap the call to Jsign with try/catch Throwable? Do you get a different exception?
Actually my project (https://github.com/ebourg/jsign) supports Java 8 to 21 and uses a custom SecurityManager to test the value returned by `System.exit()`. The build fails on Java 24 and I hoped...
This is incomplete, the path separators have to be normalized too.
If this feature is implemented it would be nice to use the keys defined in `~/.ssh/config`
The tsmode defaults to Authenticode but http://timestamp.acs.microsoft.com supports only RFC3161. That's why tsaurl alone or tsaurl with tsmode Authenticode fail. That said, with `--storetype TRUSTEDSIGNING` you can simply remove the...
Are you sure the token used the second time is valid?