mahovictim / rapla

Automatically exported from code.google.com/p/rapla
0 stars 0 forks source link

"java.lang.reflect.ReflectPermission" "suppressAccessChecks") #425

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. logo to rapla 1.8Beta
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
Rapla 1.8 windows 7

Please provide any additional information below.

Original issue reported on code.google.com by icare4.rapla@gmail.com on 15 Jun 2014 at 4:17

Attachments:

GoogleCodeExporter commented 9 years ago
Please note : 1.8Beta own build with java 8 no signature.

Original comment by icare4.rapla@gmail.com on 16 Jun 2014 at 6:47

GoogleCodeExporter commented 9 years ago
Can only be fixed by signing rapla. You can use a selfsigned certificate if you 
lower the java security on the client to medium, which you have to do anyway 
because, java no longer permitts unsigned jars in high. 
i attached a self signed keystore with the password raplaselfsigned
change build.properties to
keystore.file=raplaselfsigned.ks
keystore.password=raplaselfsigned

Original comment by christop...@gmail.com on 14 Aug 2014 at 6:33

Attachments:

GoogleCodeExporter commented 9 years ago
Hi Chris,

This is working.
I see this type of messages in the build:

*  [signjar] Warning:  [signjar] The signer certificate will expire within
six months.  [signjar] No -tsa or -tsacert is provided and this jar is not
timestamped. Without a timestamp, users may not be able to validate this
jar after the signer certificate's expiration date (2014-11-12) or after
any future revocation date.  [signjar] Signing JAR:
C:\Users\Icare\rapla18\build\war\WEB-INF\lib\smtp-1.4.7.jar to
C:\Users\Icare\rapla18\build\war\WEB-INF\lib\smtp-1.4.7.jar as rapla
[signjar] jar signed.*

Can this be extended, or is there another solution as I suppose users will
not resign the jars themselves.

Original comment by icare4.rapla@gmail.com on 15 Aug 2014 at 4:23

GoogleCodeExporter commented 9 years ago
yes i think this can be extended. I sign the builds with my valid certificate 
from thawte, which is valid until 2/2015.
I hoped to finish the gwt client before, but i think i have to extend the 
certificate for another year for 200,-

Original comment by christop...@gmail.com on 15 Aug 2014 at 3:19

GoogleCodeExporter commented 9 years ago
Would this be valid for those who build themselves ?

2014-08-15 17:19 GMT+02:00 <rapla@googlecode.com>:

Original comment by icare4.rapla@gmail.com on 15 Aug 2014 at 5:37

GoogleCodeExporter commented 9 years ago

Original comment by christop...@gmail.com on 18 Aug 2014 at 2:08