Harjo:
Scott, thanks for your reply & explanation, but
we are talking about 201 jar files (every jar I could find under application_server)
AND with every update of Servoy or 3th party plugin/bean, you have to do it again, all by hand…
This is undoable IMHO…
Well I gave you the core of what needs to happen to unsign a jar. If you wanted to automate that, then you will need to invest some of your own time and write some automated script to do that using ANT, or anything else. You could even make it a small Servoy app which loops through the jars and uses application.execute to handle the signing. Once you have your SSL Certificate, signing a jar is 1 line of code.
Also, if there are enough people interested to sponsor the project. I could write something to automate it for all plugins and beans in your Servoy directory.
usage: java -jar signtester.jar keystore password alias [overwrite]
so now you can add the parameter overwrite as last argument and it will sign all the jars with the certificate in given the keystore.
This just resigns it (i didnt remove the existing stuff, this seems to work fine for me when using 6u20)
as i said, it re-signs every jar with the provider keystore certificate.
The servoy certificate files are still in there but it is also or resigned by the one you provide
Dont know if that always works, but it does for me when testing locally.
usage: java -jar signtester.jar keystore password alias [overwrite]
so now you can add the parameter overwrite as last argument and it will sign all the jars with the certificate in given the keystore.
This just resigns it (i didnt remove the existing stuff, this seems to work fine for me when using 6u20)