Closed michnovka closed 2 years ago
Does it happen when you use the jsignpdf.sh
script?
The script contains additional arguments for Java to avoid the warnings.
@kwart Hi, yes, the same happens with bash wrapper:
superuser@TheTower:~/Applications/jsignpdf-2.0.0$ ./jsignpdf.sh
FINE Relaxing SSL security.
FINE Registering SunPKCS11 provider from configuration in conf/pkcs11.cfg
FINE PKCS11 provider registered with name SunPKCS11-eObcanka
FINE PKCS11 provider registered with name JSignPKCS11-eObcanka
INFO Starting JSignPdf
INFO Checking input and output PDF paths.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by net.sf.jsignpdf.utils.KeyStoreUtils (file:/home/superuser/Applications/jsignpdf-2.0.0/JSignPdf.jar) to field java.security.KeyStore.keyStoreSpi
WARNING: Please consider reporting this to the maintainers of net.sf.jsignpdf.utils.KeyStoreUtils
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Nice catch.
The KeyStore access was fixed now in the master
branch by adding --add-opens java.base/java.security=ALL-UNNAMED
argument.
There may be other places that need to be granted additional access. Please create a new issue or reopen this one if you find such one.
Jsignpdf 2.0.0
I am opening this issue because this will be an issue in the future version of OpenJDK (and I imagine also Java)
My JAVA version:
Contents of conf/pkcs11.cfg: