On Tue, 26 Aug 2014, Ihno Krumreich wrote:
> On Tue, Aug 26, 2014 at 10:48:35AM +0000, Walters, Gene P wrote:
> > bring up a web page and go to the new instance to start a
> > VNC session, it tells me that my security settings wont
> > let me run the old version of Java that is being
> > downloaded from the VNC server(the new Linux instance).
We ship a Java based VNC client, and have encountered problems
with:
- the Code Signing of the .JAR file had expired, and
so a local Java installation refused to run it, deeming it
insecure. Solution was to update what we shipped with a more
corrent copy
- the Java on the local machine, which was being
started by the browser, was 'stale' and had been updated
upstream; Solution there was an update of that Java (This
especially seen on OS/X units)
- the Code Signing key used to sign the .JAR was
counteresigned by a CA (Certificate Authority) not known to
the local Java installation. Solution was to add that CA's
'chain of trust' into the local ancillary install for the
local Java install
Reading the messages closely is needed, to understand what is
in play
-- Russ herrold
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
