New Exceptions in icedtea-web 1.4.1-0.fc19
Thomas Meyer
thomas at m3y3r.de
Sat Oct 5 03:18:32 PDT 2013
Am Samstag, den 05.10.2013, 10:25 +0200 schrieb Thomas Meyer:
> Hi,
>
> the Juniper Secure applet seems to throw new exceptions on the latest
> fedora packaged icedtea-web plugin.
>
> Either something broke in this version or my company did an upgrade of
> the Juniper server software. Anyway the plugin doesn't work correctly.
>
> I see these exceptions in the juniper log file:
>
> 1.) Deletion of file failed.
>
> java.io.IOException: Deletion of file [/home/thomas/.juniper_networks/tncc.jar] failed
> at SecureLauncherApplet.DeleteFileWithAuthorization(SecureLauncherApplet.java:1093)
> at SecureLauncherApplet.InstallTargetApp(SecureLauncherApplet.java:855)
> at SecureLauncherApplet.startTargetApp(SecureLauncherApplet.java:475)
> at SecureHCLauncher.doInstall(SecureHCLauncher.java:259)
> at SecureLauncherApplet.start(SecureLauncherApplet.java:226)
> at SecureHCLauncher.start(SecureHCLauncher.java:205)
> at sun.applet.AppletPanel.run(AppletPanel.java:476)
> at java.lang.Thread.run(Thread.java:724)
>
> 2.) Download and copy of stream/file fails:
>
> java.io.FileNotFoundException: /home/thomas/.juniper_networks/tncc.jar (Keine Berechtigung)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:171)
> at FileUtil.copyFile(FileUtil.java:221)
> at FileUtil.copyFile(FileUtil.java:206)
> at SecureLauncherApplet.InstallTargetApp(SecureLauncherApplet.java:861)
> at SecureLauncherApplet.startTargetApp(SecureLauncherApplet.java:475)
> at SecureHCLauncher.doInstall(SecureHCLauncher.java:259)
> at SecureLauncherApplet.start(SecureLauncherApplet.java:226)
> at SecureHCLauncher.start(SecureHCLauncher.java:205)
> at sun.applet.AppletPanel.run(AppletPanel.java:476)
> at java.lang.Thread.run(Thread.java:724)
>
> (Looks like some permissions got removed in the 1.4.1 version)
>
> any ideas what could have caused this?
okay, switching SELinux to Permissive mode makes the problem go away.
I think I'll file a bug in the Fedora bugzilla.
>
> with kind regards
> thomas
More information about the distro-pkg-dev
mailing list