[ 
https://issues.apache.org/jira/browse/FELIX-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019160#comment-14019160
 ] 

Rob Walker commented on FELIX-4281:
-----------------------------------

Karl

It goes a little deeper than that I believe. The dexfile stuff is one instance 
of the root problem. If you patch around that code (which I have) you hit the 
next instance of the same problem, which occurs when registering URLHandlers.

Both of these cases use Class.forName() calls - which are documented in several 
articles as problematic in a JNLP environment where the JNLP classloader is 
being used. 

So at present, I now have 2 cases which cause the same problem. What I've yet 
to find is a common solution. The 1st one (the dexfile case) can be gotten 
around with a simple property check - even though I don't believe that's the 
right solution. The second one I'll dig more into tomorrow - getting late here!

> Security Warning: Felix with Java Web Start
> -------------------------------------------
>
>                 Key: FELIX-4281
>                 URL: https://issues.apache.org/jira/browse/FELIX-4281
>             Project: Felix
>          Issue Type: Bug
>         Environment: Windows 7 with Java 7 update 40, 64 bits
>            Reporter: Cesar Souza
>            Priority: Minor
>         Attachments: message.zip, viewer.jnlp
>
>
> Since the release of Java 7 update 40 the following warning occurs when you 
> try to execute a signed (with valid certificate) Java Web Start application: 
> -----------------------------
> Security Warning
> Do you want to run this application?
> An unsigned application from the location below is requesting permission to 
> run.
> http://......
> Running unsigned applications like this will be blocked in a future
> release because it is potentially unsafe and a security risk
> -----------------------------
> Although the Java recognizes the certificate in the first dialog, it shows 
> the warning message when the Felix's init method is invoked.
> I have tested a same application over Java 7 update 21 and everything is ok.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to