Does not ask to grant additional permissions

[Soren Hansen]

Binary package hint: icedtea-gcjwebplugin

My homebanking system needs access to a key file in my home directory. When trying to do so, Java's security bits rejects it without asking me about it. To make it work, I need to manually add stuff to java.policy (and since I have no clue how to do it correctly, I just temporarily put AllPermission into the default and removed it when I'm done doing my homebanking thing).

Obviously, what should happen is that I should get the friendly dialog box asking if I trust the software vendor and if I'm cool with the applet accessing my home directory.

This is on amd64, by the way.

[sludge99 (allnightlong69)]

i am having the same problem, i cant get sun java working with 32bit firefox as a workaround either, (think there is a seperate bug with ia32-sun-java-bin package) this is a real pain since this worked just fine in gusty

[Martin Kalén (martin-kalen)]

Same problem on AMD 32 / i686, see bug #202883. The default permissions must be different between Sun Java and Icedtea/gcj.

[Matthias Klose (doko)]

please recheck with icedtea6-plugin in the openjdk PPA (and the ca-certficates-java package installed)

[Martin Kalén (martin-kalen)]

On Intrepid beta with the icedtea6-plugin from the openjdk PPA firefox core-dumps when openjdk is displaying the dialog asking the user whether to trust the (signed) applet or not. See attached stacktrace from running firefox in gdb (firefox -g).

[Martin Kalén (martin-kalen)]

Attaching icedtea-plugin output. The thread with the accept dialog is still alive after the segmentation fault signal. If the user chooses the "always trust" option no segmentation fault occurs on additional applet runs.

The applet from https://test.bankid.com/TestBankidCom/Templates/TestPage.aspx?id=29 still does not work 100% but the error reported in this bug (ie no question asking for additional permission) is fixed in the PPA versions (although introducing a regression in form of the reported segfault).

[Matthias Klose (doko)]

fixed in 6b12~pre2. please report any new/outstanding issues in a new report