From: FutureScalper on 29 Jun 2010 16:10 My Swing application is controlled by Web Start, and I explicitly give this flag to avoid the Security Warning popup. Yes, it suppresses the Security warning, for a long while, and then while the app is running, sometimes after many hours of continuous running, it can still pop up the Security warning. Saying "No" is too late, because it's already throwing security exceptions inside the code, thus breaking things... <property name="deployment.security.mixcode" value="DISABLE"/> This property is supposed to disable that mixed code security warning, so how can it reappear in a session when nothing special is being done except running for an extended period of time? Thanks for any ideas ! Is this a Bug ?
From: FutureScalper on 29 Jun 2010 19:54 On Jun 29, 4:10 pm, FutureScalper <futurescal...(a)gmail.com> wrote: > My Swing application is controlled by Web Start, and I explicitly give > this flag to avoid the Security Warning popup. > > Yes, it suppresses the Security warning, for a long while, and then > while the app is running, sometimes after many hours of continuous > running, it can still pop up the Security warning. Saying "No" is too > late, because it's already throwing security exceptions inside the > code, thus breaking things... > > <property name="deployment.security.mixcode" value="DISABLE"/> > > This property is supposed to disable that mixed code security warning, > so how can it reappear in a session when nothing special is being done > except running for an extended period of time? > > Thanks for any ideas ! Is this a Bug ? Dialog crashes my code, and won't even respond to clicking its Yes or No so everything breaks. "Java has discovered application components that could indicate a security concern." "Block potentially unsafe components from being run? (recommended)" "The application contains both signed and unsigned code."
From: FutureScalper on 29 Jun 2010 20:45 On Jun 29, 7:54 pm, FutureScalper <futurescal...(a)gmail.com> wrote: > On Jun 29, 4:10 pm, FutureScalper <futurescal...(a)gmail.com> wrote: > > > > > > > My Swing application is controlled by Web Start, and I explicitly give > > this flag to avoid the Security Warning popup. > > > Yes, it suppresses the Security warning, for a long while, and then > > while the app is running, sometimes after many hours of continuous > > running, it can still pop up the Security warning. Saying "No" is too > > late, because it's already throwing security exceptions inside the > > code, thus breaking things... > > > <property name="deployment.security.mixcode" value="DISABLE"/> > > > This property is supposed to disable that mixed code security warning, > > so how can it reappear in a session when nothing special is being done > > except running for an extended period of time? > > > Thanks for any ideas ! Is this a Bug ? > > Dialog crashes my code, and won't even respond to clicking its Yes or > No so everything breaks. > > "Java has discovered application components that could indicate a > security concern." > > "Block potentially unsafe components from being run? (recommended)" > > "The application contains both signed and unsigned code." OK, I have set the <property name="deployment.security.mixcode" value="HIDE_RUN" /> hoping this will eliminate the unsigned jar issue. Perhaps this is the correct setting. I can't have my app apparently randomly crashing several hours into operation or requiring some user input if it's unattended. Aargh.
From: FutureScalper on 30 Jun 2010 22:51 On Jun 29, 8:45 pm, FutureScalper <futurescal...(a)gmail.com> wrote: > On Jun 29, 7:54 pm, FutureScalper <futurescal...(a)gmail.com> wrote: > > > > > > > On Jun 29, 4:10 pm, FutureScalper <futurescal...(a)gmail.com> wrote: > > > > My Swing application is controlled by Web Start, and I explicitly give > > > this flag to avoid the Security Warning popup. > > > > Yes, it suppresses the Security warning, for a long while, and then > > > while the app is running, sometimes after many hours of continuous > > > running, it can still pop up the Security warning. Saying "No" is too > > > late, because it's already throwing security exceptions inside the > > > code, thus breaking things... > > > > <property name="deployment.security.mixcode" value="DISABLE"/> > > > > This property is supposed to disable that mixed code security warning, > > > so how can it reappear in a session when nothing special is being done > > > except running for an extended period of time? > > > > Thanks for any ideas ! Is this a Bug ? > > > Dialog crashes my code, and won't even respond to clicking its Yes or > > No so everything breaks. > > > "Java has discovered application components that could indicate a > > security concern." > > > "Block potentially unsafe components from being run? (recommended)" > > > "The application contains both signed and unsigned code." > > OK, I have set the > > <property name="deployment.security.mixcode" value="HIDE_RUN" /> > > hoping this will eliminate the unsigned jar issue. Perhaps this is > the > correct setting. I can't have my app apparently randomly crashing > several > hours into operation or requiring some user input if it's unattended. > Aargh. OK, I believe I now understand that this needs to be a deployment property and not specified in the JNLP. So, I created deployment.config and deployment.properties in hopes it will eliminate this issue. All of my users are instructed to place these files on their systems in this location: c:\Windows\Sun\Java\Deployment deployment.config contains: deployment.system.config=file:/C:/windows/Sun/Java/Deployment/ deployment.properties deployment.system.config.mandatory=true deployment.properties contains: deployment.security.mixcode=DISABLE Thanks for the help.
From: Roedy Green on 30 Jun 2010 23:34 On Tue, 29 Jun 2010 16:54:25 -0700 (PDT), FutureScalper <futurescalper(a)gmail.com> wrote, quoted or indirectly quoted someone who said : >"The application contains both signed and unsigned code." I always thought if you had any signed jars, they all had to be signed and with the same key. I think there is a way around that with multiple JNLP files, but all-signed is the standard way to handle it. -- Roedy Green Canadian Mind Products http://mindprod.com There is no harm in being sometimes wrong especially if one is promptly found out. ~ John Maynard Keynes (born: 1883-06-05 died: 1946-04-21 at age: 62)
|
Pages: 1 Prev: dll creation from java source Next: Change jnlp invalidates desktop shortcut |