Activity for resolir
-
resolir posted a comment on ticket #4
Salve, L'installer (e soprattutto j4sign) è testato e può funzionare solo fino a jdk 8.
-
Version set to 0.2.2 in README
-
Commented option to put bc in container classloader
-
Make getHashString use StringBuilder, Code leanup.
-
Remove obsolete dss v5.3.2 libs
-
Remove j4sign core v0.2.1 lib
-
Upgrade dss libs to v5.4.3, j4sign core to v0.2.2
-
Raise generic Exception
-
Upgrade j4sign-core lib to v0.2.2
-
Version set to 0.2.2
-
Various modifications for RFC8017 compliancy (DERNull Parameter in AlgorithmIdentifier) with new AlgorithmIdBuilder utility class for generation. Obsolete example CMSServlet and GUITest classes removed.
-
Use a NULL parameter as of rfc8017 https://datatracker.ietf.org/doc/html/rfc8017#section-9.2; apply Pkcs#1 padding of correct size (RSA key modulus).
-
Corrected progress number for Aruba-Infocamere card 22->23
-
Added Aruba-Infocamere card "3BFF9600FF8131FE55006B02090403010101434E5310318014"
-
Catch FileUploadException sooner
-
CRL download and check now iterates on all distribution points in certificate
-
CRL verification now explores all distribution points present in the certificate
-
Corrected generation of file names for files being signed.
-
Improve dealing with malformed CMS
-
Updated j4sign-core to v0.2.1, improving dealing with malformed CMS files
-
Corrected generation of nested items file names
-
Implementation of nested signatures verification.
-
Switch classpath of Bouncycastle libraries relative to specific BC_HOME variable
-
Upgrade DSS libs to v5.4.3
-
Pass mime types for signature/verification to FileItemProcessor constructor
-
Update LOTL signers after 2019 modification restoring verification functionality.
-
Update LOTL signers after 2019 modification restoring verification functionality.
-
Added merge test
-
Added merge test
-
Il 18/02/21 15:34, Julian Del Vecchio ha scritto: Hi All, the version 0.3.4 still have the same problem. Is it possible to modify your application to work with openjdk? Thx a lot. Sorry, now I read the stacktrace below. Which Java runtime version? j4sign at the moment works only with java8 included. Openjdk is perfectly fine for Freesigner. rob [bugs:#3] issue installing on ubuntu 20.04 Status: open Group: v1.0 (example) Created: Thu Oct 15, 2020 11:11 AM UTC by Nur Aiman Fadel Last Updated: Thu...
-
Il 18/02/21 15:34, Julian Del Vecchio ha scritto: Hi All, the version 0.3.4 still have the same problem. Is it possible to modify your application to work with openjdk? Thx a lot. Which application? Freesigner? rob
-
Already answered at previous post. No support for jdk (any provider) over 8 is in sight. Openjdk 8 is perfectly fine.
-
Corrected some typos in a log message and traslated comment
-
Il 29/10/20 09:40, Nur Aiman Fadel ha scritto: hi, the default version on ubuntu 20.04: openjdk version "11.0.9" 2020-10-20 OpenJDK Runtime Environment (build 11.0.9+11-Ubuntu-0ubuntu1.20.04) OpenJDK 64-Bit Server VM (build 11.0.9+11-Ubuntu-0ubuntu1.20.04, mixed mode, sharing) Firstly: may you subscribe to the j4sign-users mailing list and post your questions there? (it will be easier for me and others to read and answer). Freesigner doesn to works at the moment with java runtime over jre 8; it is...
-
Il 15/10/20 13:11, Nur Aiman Fadel ha scritto: [bugs:#3] issue installing on ubuntu 20.04 Status: open Group: v1.0 (example) Created: Thu Oct 15, 2020 11:11 AM UTC by Nur Aiman Fadel Last Updated: Thu Oct 15, 2020 11:11 AM UTC Owner: nobody I tried to install it on Ubunto 20.04 but I had the following error: ./freesigner-0.3.3-setup.jar Command line arguments: Cannot find named resource: 'packsLang.xml' AND 'packsLang.xml_fur' ==================== * Installation started Exception in thread "IzPack...
-
And, by the way, may you post your questions thru the user mailing list? https://sourceforge.net/p/j4sign/mailman/j4sign-users/
-
Hello, which kind and version of java runtime are you using? Which operating system? Bye, rob
-
Fixing 'origin' header for Tyrus webstart client websocket connections adding http or https scheme.
-
Removed jwt keystore in favor of jwt certificate (no need of a keystor for passing a public key)
-
Introduced ant buildfile and removed hardcoded jwt keystore parameters
-
Delete ROOTS configuration content and jws keystore
-
First release
-
First release
-
Reintroduce JNLP streamer servlet
-
Java Webstart applet, 2019 LOTL signer modifications
-
Java Webstart applet, 2019 LOTL signer modifications
-
Java Webstart applet, 2019 LOTL signer modifications
-
Java Webstart applet, 2019 LOTL signer modifications
-
Logback configuration
-
Updated servlet package with upcoming classes from jaxrs service
-
websocket package for interacting with new webstart signature applet implementation
-
Updated servlet package with upcoming classes from jaxrs service
-
Update commons-fileupload to v1.4
-
-
Update commons-fileupload to v1.4
-
websocket package for interacting with new webstart signature applet implementation
-
Updated servlet package with upcoming classes from jaxrs service
-
Comments editing
-
Added copyright notice, javadoc comments
-
README and ISTALL updated with java runtime requirements and TSL verification news.
-
v0.2.0 related changes
-
Upgrade DSS to 5.4.3, removing 5.3.2 libs
-
2019 updates to LOTL location and new signers, smartcardio based card detection
-
Updated core j4sign to version 0.1.9, which uses dss project libraries v5.3.2; LOTL signers are now refreshed and updated from (pivot) LOTLs themselves.
-
Add dependencies to configure.web.dist needed for triggering inclusion of firma.jsp
-
Small corrections in HTML markup.
-
dss libraries upgraded to v5.3.2, LOTL signers dynamically refreshed from pivot LOTL
-
Removed tag
-
dss libraries upgraded to v5.3.2, LOTL signers dynamically refreshed from pivot LOTL
-
j4sign lib upgraded to v0.1.9
-
j4sign lib upgraded to v0.1.9
-
Prepare to 0.1.9 release
-
- Added tsl-keystore-first.jks, aligned to euoj published fingerprints
-
- Added tsl-keystore-first.jks, aligned to euoj published fingerprints
-
Prepare to 0.1.9 release
-
Prepare to 0.1.9 release
-
Prepare to 0.1.9 release
-
- Introduced kcsLOTL for storing update LOTL signers certificates after LOTL initialization
-
Removed deprecated references to DERObjectIdentifier
-
Prepare to 0.1.9 release
-
Added basicVerify test to full verification
-
Removed deprecated references to DERObjectIdentifier
-
Switch version to 0.1.9
-
- Preparing for release 0.3.3
-
- Preparing for release 0.3.3
-
- Preparing for release 0.3.3
-
- Preparing for release 0.3.3
-
- Preparing for release 0.3.3
-
- Preparing for release 0.1.8
-
Salve, Una serie nutrita di domande ... le chiedo cortesemente però di riformularle nella mailing list: https://sourceforge.net/projects/j4sign/lists/j4sign-users Cercherò di rispondere in quella sede. Salve, Roberto Resoli
-
Salve, Sì, il progetto è attivo e correntemente mantenuto. Vi chiedo cortesemente però di usare la mailing list j4sign-users[1] per eventuali richieste. Cordiali Saluti, Roberto Resoli [1] https://sourceforge.net/projects/j4sign/lists/j4sign-users
-
LOTL signer changed with new certificate (see 191 pivot list), updated keystore and added new fingerprint.
-
LOTL signer changed with new certificate (see 191 pivot list), updated keystore and added new fingerprint.
-
Updated EU TSL signers keystore, and related fingerprints in configuration. Note that these are different from EU OJ issue, since they were updated in the TSL itself. See README. Added TSL caching function on filesystem. Disabled by default.
-
Corrected dss sources filtering out in dist.src building.
-
Deleted for modifying build.xml.
-
Updated EU TSL signers keystore, and related fingerprints in configuration. Note that these are different from EU OJ issue, since they were updated in the TSL itself. See README. Added TSL caching function on filesystem. Disabled by default.
-
Deleted for modifying commit description.
-
LOTL signers update, bugfixes.
-
Filtering out TSL in caching directory.
1 >