Processing 1.0 - Processing Discourse - Killing JOGL certificate and other dialogs

We closed this forum 18 June 2010. It has served us well since 2005 as the ALPHA forum did before it from 2002 to 2005. New discussions are ongoing at the new URL http://forum.processing.org. You'll need to sign up and get a new user account. We're sorry about that inconvenience, but we think it's better in the long run. The content on this forum will remain online.

Index › Programming Questions & Help › OpenGL and 3D Libraries › Killing JOGL certificate and other dialogs

‹ Previous Topic | Next Topic ›

Pages: 1

Killing JOGL certificate and other dialogs (Read 1504 times)

threesixty3d

Killing JOGL certificate and other dialogs
Jun 9^th, 2009, 8:06am

I thought this could be a FAQ, but I couldn't find any solution in this forum or search engines.

When running an opengl applet from a website, I have to confirm that I want to trust the JOGLAppletLauncher certificate (which has expired).
It's not a problem for me, but it's definitely a big problem for the average user that will try to run the applet.

Even worse, the first time JOGL loads on a machine, it pops up a dialog (deployment.properties) asking some crazy stuff about JAVA2D and directdraw, explained using 3D jargon that only a programmer can understand.
Is it possible to suppress those useless requests somehow?

Btw I'm using processing 1.0.3 and testing under XP32 and XP64 on 10 different boxes.

Thanks,
Michele

threesixty3d

Re: Killing JOGL certificate and other dialogs
Reply #1 - Jun 9^th, 2009, 9:07am

ok, after looking into this problem a bit more, I've found this:
http://download.java.net/media/jogl/builds/nightly/javadoc_public/com/sun/opengl/util/JOGLAppletLauncher.html
It might help solve the 2nd problem, except that I've no idea where to add or set that extra parameter.

Code:

The behavior of the noddraw-related dialog box can be changed via two applet parameters. The jogl.silent.noddraw.check  parameter, if set to "true", silences the two dialog boxes associated with this check, forcing it to always be performed and deployment.properties to be silently updated if necessary (unless the user previously saw such a dialog box and dismissed it by saying "No, Don't Ask Again"). The noddraw check can be disabled completely by setting the jogl.disable.noddraw.check  applet parameter to "true".

gll

Re: Killing JOGL certificate and other dialogs
Reply #2 - Jun 9^th, 2009, 9:12am

I have the same problem. It was a mystery for me, I think I understand a bit better the mechanism. Someone might correct me if I am wrong.

The applet could access JAVA ressources without requiring any extra security prompts. This is the JAVA default security setup. JAVA could request ressources outside of the initial environement (you could for example request the OS to write on the drive). In this case, because of the potential problems for security, JAVA is requesting for security aknowledgments. Each time you have something like TextIO.write() in your JAR, you should have a security prompt in a browser, unless you sign it. Signatures works with a server of trusted application and is expensive. You could auto sign your own applet, but the user is still asked to trust it.

Now, for JOGL, JAVA is requesting for extra ressources outside (an access to the graphic card accelerations). This is why you get those security prompts.

If you then want to reduce the prompts, you need to sign them. There's an article on this: (http://www.processing.org/hacks/hacks:signapplet)

Here's a brief discussion we had on JOGL security:
http://processing.org/discourse/yabb2/?num=1233139829

LaBelle / ANAR.ch / LaBelle.spaceKIT.ca

gll Full Member Offline Posts: 186 Switzerland	Re: Killing JOGL certificate and other dialogs Reply #3 - Jun 9^th, 2009, 9:16am Ok, you already found something... I was wandering if it would be possible to rewrite a P5-Opengl preloader that will make the things more fluid...
	LaBelle / ANAR.ch / LaBelle.spaceKIT.ca

threesixty3d

Re: Killing JOGL certificate and other dialogs
Reply #4 - Jun 9^th, 2009, 10:09am

Hi gll, thanks for replying!

It makes sense for the example you pointed out (writing to a drive), but still ... the dialog remains useless and annoying, I can't think of how a programmer accessing a gpu could cause damage to the user.

Definitely a better p5ogl preloader would rock, but I guess it would be a though job for most p5 developers, considering the amount of systems that one would have to test to ensure maximum compatibility.

Anyway, the only dialogs I need to remove are the jogl security warning and the deployment.properties thing (i'm working on the 2nd one right now); both things can be set and their values can be saved, so that a smart user would not be requested multiple times for the same thing, but ... the 2nd one requires a browser restart, and I've noticed many times that it might freeze the browser or make it unstable.

threesixty3d YaBB Newbies Offline Posts: 22 Italy	Re: Killing JOGL certificate and other dialogs Reply #5 - Jun 9^th, 2009, 10:11am Oh and btw, I don't think this stuff can be signed ... I mean jogl already has a certificate, but it's expired (!?). And the 2nd one has nothing to do with certificates, it's just an annoying option that jogl asks when you run an applet on a browser for the 1st time.

threesixty3d

Re: Killing JOGL certificate and other dialogs
Reply #6 - Jun 9^th, 2009, 10:35am

Ok, adding
<param name="jogl.silent.noddraw.check" value="true" />
inside
<body/div/div/object classid="java:com.sun.opengl.util.JOGLAppletLauncher.class">
solved the 2nd problem.

Then the next question is ... is it possible to integrate this change (and other modifications) whenever I export my applet with ctrl + E?
In most c++ IDEs I can create what vc++ calls post-build steps, basically small scripts that are executed after compiler and linker are done with their work.
Or perhaps there's a template somewhere in the processing folder that is used to generate the .html everytime?

Pages: 1

‹ Previous Topic | Next Topic ›