31 Dec
2011
31 Dec
'11
10:48 p.m.
Le samedi 31 décembre 2011 à 10:14 +0100, Alain Knaff a écrit :
A, so that is the reason why openjdk fails with so
many applets. Thanks
for having found this out.
Always a pleasure :-)
Apparently, it is possible to grant permission by
codebase (i.e. where
applet has been downloaded from), rather than globally:
grant codeBase "https://www.bcee.lu/..." {
permission java.security.AllPermission;
};
Just tried with
grant codeBase "https://www.bcee.lu/*" {
permission java.security.AllPermission;
}
grant codeBase "https://bcee.snet.lu/*" {
permission java.security.AllPermission;
};
since I suspect either URL may be involved. I also tried different
wildcards and other variants, and I think I have avoided caching issues,
but it still doesn't work, and there are few things on earth I loathe as
much as digging into java code... (well, fortran qualifies as a worthy
second). The only thing that seems to work is:
grant {
permission java.security.AllPermission;
};
In any case, the true problem lies with laymen, who will simply state
that "linux doesn't work", as usual. And in this case, they will be
right (especially with ubuntu's recent automatic removal of the sun java
plugin). We can't ask them to edit a config file. Why doesn't icedtea
just spit out a popup like sun java?...
In any case, I find it hard to believe that no one coding for openjdk
has met the problem; it must on the contrary be pervasive, as you hinted
yourself. I tried to google for an explanation, to no avail.
Regards, and have a nice slide into the new Year!
Thanks, and a happy new year too !
Alain