Droid Assault Linux FAIL

http://www.puppygames.net/temp/droid.png

Eh? What’s all this? Why does it work fine on Mac and Windows?

Cas :slight_smile:

Under my ubuntu version it saids that the stuff checks out…

What webstart stuff do you use?

You have a digital signature, a certificate that can be verified and it doesn’t work under Linux. Would you like me to test on several machines under Linux? I can try to reproduce this bug. Give me a pointer to this JNLP file please. Is it the same link of Droïd assault than on your website? It seems to be the Sun’s JVM, not the OpenJDK, I don’t see what is wrong.

Isn’t my machine so I can’t really get much more in the way of detail. The warning appears to be triggered because the JNLP file itself is not signed, but I am unaware of any way to actually sign a JNLP file, or even that it needs to be done - it looks like a bug in the Java implementation on that Ubuntu system (openJDK?)

If you could test it out on a few other Linux systems gouessej that would be great - it’s just the ordinary link on Puppygames for Linux (http://www.puppygames.net/applets/droidassault.jnlp)

Cas :slight_smile:

Works for me on Kubuntu 0804, but I’m using the Sun JVM.

I used the openjdk one I believe this was a bug that has been fixed for a few months(not sure as I haven’t really been following the project and all) but you could ask him to upgrade, webstart under *buntu 64bit is a bit messy to get working.

Well, I’ll be dipped in dogshit - I’ve just installed a brand new JDK 6.0u11 here on Windows XP and I get the very same problem (but not at home, which I think is u10). Is this a new feature or a regression d’you think? If it’s a new feature has it been documented somewhere, and if it’s a bug, has it been reported?

Cas :slight_smile:

Your right I have the same thing on xp machine - I gues my (openjdk)version is old - since when was that silently introduced?

It must be since u11.

Cas :slight_smile:

Cas,

Please submit a bug report.

-Chris

Aha, a bit of trivial research yields this thread over on the Sun dev forums. It would seem that this behaviour is new and intentional from u11 onwards, and occurs when “untrusted” parameters are passed to the JVM. The workaround for simple JNLP deployment is to include the JNLP file itself inside a signed jar as detailed in that thread (see jnlp specification section 5.4.1).

I’ll fix that when I get home.

Cas :slight_smile:

I think thats the way it always used to be. It doesn’t mean application won’t run. It only means that sun did not verify this certificate/publisher. As far as i know that’s the way signed applets always used to work. The only difference between verified certificate and unverified is that, the information in the run dialog.
Correct me if I’m wrong.
Anyway, although i get the same message the game works fine on my linux box after i press the run button.

I’ll be fixing it at the weekend so it displays a nice information box instead of a scary warning triangle.

Cas :slight_smile:

But that dialog breaks every rule of user interface design I ever learned, nobody can realistically say that a normal user is going to read that much text, especially since they didn’t ask for that information. The most probable outcome is that some people will click ‘run’ without even reading the warning, and others will think it’s an error message of some sort.

I’m hoping that in update 12 or very soon after the dialog will completely change to something that just looks super friendly and informs you that the app is going to run.

Cas :slight_smile:

Personally i think these dialogs should look alerting, because they actually ask for full access to local resources.

so does running an executable from a browser - yet that warning is a lot LESS scary!

Right, that’s all fixed. Not a massive deal but there we go, we live and learn…

Cas :slight_smile: