Difference between revisions of "JASigning Platform Issues"
John.Glauert (talk | contribs) (Instructions on disabling GateKeeper) |
John.Glauert (talk | contribs) (Update for Java 7u45) |
||
| Line 9: | Line 9: | ||
JASigning applications and applets are launched using [http://en.wikipedia.org/wiki/Java_Web_Start Java Web Start] through Java Network Launching Protocol (JNLP) files, which have extension <code>.jnlp</code>. | JASigning applications and applets are launched using [http://en.wikipedia.org/wiki/Java_Web_Start Java Web Start] through Java Network Launching Protocol (JNLP) files, which have extension <code>.jnlp</code>. | ||
| − | On modern browsers, the use of JNLP files for applets is mostly seamless. | + | On modern browsers, the use of JNLP files for applets is mostly seamless. However, changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions, and for older JASigning releases with current Java release (Java 7u45). |
For applications, launching of Java Web Start is sometimes automatic, but sometimes requires further action. Apple makes it increasingly difficult to deploy components using JNLP so for recent versions of Mac OS X it is necessary to override the default protection regime even though the components are correctly signed. See below for notes on using particular browsers. | For applications, launching of Java Web Start is sometimes automatic, but sometimes requires further action. Apple makes it increasingly difficult to deploy components using JNLP so for recent versions of Mac OS X it is necessary to override the default protection regime even though the components are correctly signed. See below for notes on using particular browsers. | ||
| Line 47: | Line 47: | ||
Before installing and running JASigning applications, the corresponding JNLP file must be downloaded. The application is then launched using Java Web Start. The user will be warned that the application (its JNLP file) has been downloaded from the Internet. The user will also be asked to confirm that they trust the publisher. | Before installing and running JASigning applications, the corresponding JNLP file must be downloaded. The application is then launched using Java Web Start. The user will be warned that the application (its JNLP file) has been downloaded from the Internet. The user will also be asked to confirm that they trust the publisher. | ||
| − | Under the default settings for GateKeeper on Mac OS X 10.8 Mountain Lion and 10.7.5 Lion onwards, JASigning applications are blocked from running because they do not come from the App Store or an identified developer. To run blocked applications it is necessary to locate the JNLP file, typically in the Downloads folder, and open it by double-clicking with the control-key down or by right-clicking and choosing Open. GateKeeper can be disabled using the General tab of Security & Privacy in the System Preferences. | + | Under the default settings for GateKeeper on Mac OS X 10.9 Mavericks, 10.8 Mountain Lion, and 10.7.5 Lion onwards, JASigning applications are blocked from running because they do not come from the App Store or an identified developer. To run blocked applications it is necessary to locate the JNLP file, typically in the Downloads folder, and open it by double-clicking with the control-key down or by right-clicking and choosing Open. GateKeeper can be disabled using the General tab of Security & Privacy in the System Preferences. |
As documented in [[JASigning Release Notes]], on Mac OS X 10.6 Snow Leopard some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player. This seems to be related to use of Java 6 so can occur with MacOS 10.7 Lion and 10.8 Mountain Lion as initially installed. | As documented in [[JASigning Release Notes]], on Mac OS X 10.6 Snow Leopard some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player. This seems to be related to use of Java 6 so can occur with MacOS 10.7 Lion and 10.8 Mountain Lion as initially installed. | ||
Revision as of 16:51, 27 October 2013
Code Signing
JASigning components are digitally signed using a Code Signing Certificate issues by GlobalSign to SYS Consulting Limited. When installing applications or applets, users will be asked to confirm that they trust the publisher. Users can choose to trust the publisher permanently to avoid future confirmation requests.
Java Web Start
JASigning applications and applets are launched using Java Web Start through Java Network Launching Protocol (JNLP) files, which have extension .jnlp.
On modern browsers, the use of JNLP files for applets is mostly seamless. However, changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions, and for older JASigning releases with current Java release (Java 7u45).
For applications, launching of Java Web Start is sometimes automatic, but sometimes requires further action. Apple makes it increasingly difficult to deploy components using JNLP so for recent versions of Mac OS X it is necessary to override the default protection regime even though the components are correctly signed. See below for notes on using particular browsers.
Platforms
The current version of JASigning is intended to run on Windows (XP, Vista, 7) and on the latest releases of Mac OS X 10.5 and later. JASigning is not supported on Linux at present. It is preferable to run JASigning with an up-to-date Java 6 run-time (JRE), although it should run with the latest versions of Java 5.
On the supported platforms, that is, Windows and Mac OS X, JASigning supports both 32-bit and 64-bit operation. Which of this modes it actually runs in on any given occasion depends on several factors:
- Whether or not the processor supports 64-bit operation.
- Whether or not the operating system supports 64-bit operation.
- Whether the system has a 32-bit or a 64-bit Java installation (or both) -- and what options are set in the Java Control Panel (Windows) or Java Preferences app (Mac OS X).
- For a JASigning applet: whether the browser is running in 32-bit or 64-bit mode.
Windows
JASigning applications and applets (apart from the SiGML Service Client) on Windows may require the appropriate Microsoft Visual Studio C++ 2010 Redistributable Package to be installed on the system.
On many Windows systems the required Redistributable package will already have been installed. But if not, each JASigning application and applet will display a message at launch time giving the URLs from which the package can easily be downloaded and installed. These URLs can be copied from the Java console and pasted into a web browser.
There is a 32-bit (x86) and a 64-bit (x64) version of the Redistributable package. One or both of these should be installed, to match the system's JRE (Java Runtime Environment) installation(s).
Mac OS X
Before installing and running JASigning applications, the corresponding JNLP file must be downloaded. The application is then launched using Java Web Start. The user will be warned that the application (its JNLP file) has been downloaded from the Internet. The user will also be asked to confirm that they trust the publisher.
Under the default settings for GateKeeper on Mac OS X 10.9 Mavericks, 10.8 Mountain Lion, and 10.7.5 Lion onwards, JASigning applications are blocked from running because they do not come from the App Store or an identified developer. To run blocked applications it is necessary to locate the JNLP file, typically in the Downloads folder, and open it by double-clicking with the control-key down or by right-clicking and choosing Open. GateKeeper can be disabled using the General tab of Security & Privacy in the System Preferences.
As documented in JASigning Release Notes, on Mac OS X 10.6 Snow Leopard some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player. This seems to be related to use of Java 6 so can occur with MacOS 10.7 Lion and 10.8 Mountain Lion as initially installed.
Browsers
Firefox is generally the easiest browser to use for running JASigning applets and launching JASigning applications.
JASigning applets may work with browsers other than those mentioned below, but our testing in such cases is at best limited. Let us know!
Windows
JASigning web applets should work with Safari, Firefox, Opera, Chrome, and Internet Explorer.
Mac OS X
JASigning web applets should work with Firefox and Safari. Recent versions of MacOS X require applets from JASigning 095j or JASigning 095l. JASigning applets from older releases should work with Firefox 3.6.28 (which is no longer supported).
Safari will block applets by default but clicking on the avatar display area will allow the applet plug-in to be enabled.
Chrome does not support Java 7 on the Mac so can only be used to run JASigning applets on MacOS 10.6 Snow Leopard or on MacOS 10.7 Lion or 10.8 Mountain Lion as initially installed.
If GateKeeper is active, launching of applications will be blocked. See the Platforms section above. Even if GateKeeper is disabled: Safari does not consider Java Web Start to be safe so JNLP files may be downloaded to a temporary area and can only be launched by clicking on the icon for the downloaded file in the Downloads window; JNLP files for applications can be downloaded and launched from Chrome but a warning suggests that JNLP files can be harmful.