JASigning Platform Issues - Revision history

John.Glauert: macOS Quarantine

2025-09-19T18:01:20Z

macOS Quarantine

← Older revision		Revision as of 18:01, 19 September 2025
Line 12:		Line 12:

	The software is supported on Windows and macOS, but not Linux.		The software is supported on Windows and macOS, but not Linux.

			==== macOS ====

			Security measures in macOS make it increasingly hard to distribute software. See [[macOS Quarantine]]

	== Java Web Start ==		== Java Web Start ==

John.Glauert: /* CWA Signing Avatars */

2025-09-19T17:47:39Z

CWA Signing Avatars

← Older revision		Revision as of 17:47, 19 September 2025
Line 5:		Line 5:

	== CWA Signing Avatars ==		== CWA Signing Avatars ==
	The core [[CWA Signing Avatars]] software is implemented in JavaScript for HTML5 web pages using WebGL. It functions on most platforms. See [[CWASA Platform Issues]] for details.		The core [[CWA Signing Avatars]] software is implemented in JavaScript for HTML5 web pages using WebGL. It functions on most platforms: Windows, macOS, Linux, and smart phones and tablets. See [[CWASA Platform Issues]] for details.

	= Legacy Software : Java =		= Legacy Software : Java =

John.Glauert: /* Legacy Software : Java */

2025-09-19T17:46:45Z

Legacy Software : Java

← Older revision		Revision as of 17:46, 19 September 2025
Line 9:		Line 9:
	= Legacy Software : Java =		= Legacy Software : Java =

	A Java Runtime Environment (JRE) must be installed. In the Security settings of the Java Control Panel you may need to add https://vhg.cmp.uea.ac.uk to the Exception Site List.		A 64bit Java Runtime Environment (JRE) must be installed. In the Security settings of the Java Control Panel you may need to add https://vhg.cmp.uea.ac.uk to the Exception Site List.

			The software is supported on Windows and macOS, but not Linux.

	== Java Web Start ==		== Java Web Start ==

John.Glauert: Use macOS for Mac OS X

2025-09-19T17:42:55Z

Use macOS for Mac OS X

John.Glauert: More security notes. Changed http to https.

2024-04-29T15:09:25Z

More security notes. Changed http to https.

← Older revision		Revision as of 15:09, 29 April 2024
Line 8:		Line 8:

	= Legacy Software : Java =		= Legacy Software : Java =

			A Java Runtime Environment (JRE) must be installed. In the Security settings of the Java Control Panel you may need to add https://vhg.cmp.uea.ac.uk to the Exception Site List.

	== Java Web Start ==		== Java Web Start ==

	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>. Web pages using the more recent JASigning implementation for HTML5 using JavaScript and WebGL is not dependent on JNLP.		JASigning applications and applets are launched using [https://en.wikipedia.org/wiki/Java_Web_Start Java Web Start] through Java Network Launching Protocol (JNLP) files, which have extension <code>.jnlp</code>. Web pages using the more recent JASigning implementation for HTML5 using JavaScript and WebGL is not dependent on JNLP.

	The use of JNLP files for applets is deprecated in modern browsers. Where it is supported, it is fairly seamless, but changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions.		The use of JNLP files for applets is deprecated in modern browsers. Where it is supported, it is fairly seamless, but changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions.
Line 19:		Line 21:
	== Code Signing ==		== Code Signing ==

	JASigning components are digitally signed using a Code Signing Certificate issues by [~~http~~://www.globalsign.com/code-signing/ GlobalSign] to [~~http~~://www.uea.ac.uk/business/consultancy UEA Consulting Ltd]. Before 2014, certificates were issued to [http://www.sys-consulting.co.uk/ 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.		JASigning components are digitally signed using a Code Signing Certificate issues by [https://www.globalsign.com/code-signing/ GlobalSign] to [https://www.uea.ac.uk/business/consultancy UEA Consulting Ltd]. Before 2014, certificates were issued to [http://www.sys-consulting.co.uk/ 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.

	The certificates have a limited lifetime and have now expired. Unfortunately, it is therefore necessary to ignore security warnings to use the software. Components can still be used if http://vhg.cmp.uea.ac.uk is added to the Exception Site List via the Security tab on the Java control panel.

	~~== Legacy Web Applications : Java Applets ==~~
	~~Support for Java Applets is now minimal and the HTML5 approach should be used wherever possible.~~

	~~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 '''Internet Explorer'''. The 32-bit (x86) release of Java should be installed.~~

	~~==== OS X ====~~
	~~JASigning web applets should work with '''Safari'''.~~

	'''Safari''' will block applets by default but clicking on the avatar display area will allow the applet plug-in to be enabled. '''Safari 7''' and later impose a ''safe'' mode which blocks access to the local disk even though requested by the Java security settings. JASigning will operate in safe mode but will operate more slowly and will not work so well offline as a local cache will be disabled. The Safari Security preferences can be used to disable safe mode for JASigning applets, allowing the local cache to be used.

	~~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~~.		The certificates have a limited lifetime and have now expired. Unfortunately, it is therefore necessary to ignore security warnings to use the software. Components can still be used if https://vhg.cmp.uea.ac.uk is added to the Exception Site List via the Security tab on the Java control panel.

	== Legacy Standalone Applications : Java ==		== Legacy Standalone Applications : Java ==
	The security constraints on running Java-based applications mean that the [[CWA Signing Avatars]] applications are strongly preferred. At present, however, some functionality is only available in the Java software.		The security constraints on running Java-based applications mean that the [[CWA Signing Avatars]] applications are strongly preferred. At present, however, some functionality is only available in the Java software.

	Java-based applications for the [~~http~~://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7) and on the latest releases of OS X 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.		Java-based applications for the [https://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7, 10) and on the latest releases of OS X 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.

	On the supported platforms, that is, Windows and 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:		On the supported platforms, that is, Windows and 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:
Line 64:		Line 51:
	a web browser.		a web browser.

	There is a 32-bit ([~~http~~://www.microsoft.com/en-us/download/details.aspx?id=5555 x86]) and a 64-bit ([~~http~~://www.microsoft.com/en-us/download/details.aspx?id=14632 x64])		There is a 32-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=5555 x86]) and a 64-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=14632 x64])
	version of the Redistributable package.		version of the Redistributable package.
	One or both of these should be installed, to match the system's		One or both of these should be installed, to match the system's
Line 76:		Line 63:

	As documented in [[JASigning Release Notes]], on OS X 10.6 Snow Leopard and later some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player.		As documented in [[JASigning Release Notes]], on OS X 10.6 Snow Leopard and later some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player.

			== Legacy Web Applications : Java Applets ==
			Support for Java Applets is now minimal and the HTML5 approach should be used wherever possible.

			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 '''Internet Explorer'''. The 32-bit (x86) release of Java should be installed.

			==== OS X ====
			JASigning web applets should work with '''Safari'''.

			'''Safari''' will block applets by default but clicking on the avatar display area will allow the applet plug-in to be enabled. '''Safari 7''' and later impose a ''safe'' mode which blocks access to the local disk even though requested by the Java security settings. JASigning will operate in safe mode but will operate more slowly and will not work so well offline as a local cache will be disabled. The Safari Security preferences can be used to disable safe mode for JASigning applets, allowing the local cache to be used.

			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.


	----		----
	[[Main Page]] >> [[JASigning]]		[[Main Page]] >> [[JASigning]]

John.Glauert: /* CWA Signing Avatars */

2021-01-15T18:37:15Z

CWA Signing Avatars

← Older revision		Revision as of 18:37, 15 January 2021
Line 5:		Line 5:

	== CWA Signing Avatars ==		== CWA Signing Avatars ==
	The core CWA Signing Avatars software is implemented in JavaScript for ~~wHTML5eb~~ pages using WebGL. It functions on most platforms. See [[CWASA Platform Issues]] for details.		The core [[CWA Signing Avatars]] software is implemented in JavaScript for HTML5 web pages using WebGL. It functions on most platforms. See [[CWASA Platform Issues]] for details.

	= Legacy Software : Java =		= Legacy Software : Java =

John.Glauert at 18:35, 15 January 2021

2021-01-15T18:35:09Z

← Older revision		Revision as of 18:35, 15 January 2021
Line 5:		Line 5:

	== CWA Signing Avatars ==		== CWA Signing Avatars ==
	The core CWA Signing Avatars software is implemented in ~~HTML5~~ using ~~JavaScript and~~ WebGL. It functions on most platforms. See [[CWASA Platform Issues]] for details.		The core CWA Signing Avatars software is implemented in JavaScript for wHTML5eb pages using WebGL. It functions on most platforms. See [[CWASA Platform Issues]] for details.

	= Legacy Software : Java =		= Legacy Software : Java =

John.Glauert at 16:55, 15 January 2021

2021-01-15T16:55:31Z

← Older revision		Revision as of 16:55, 15 January 2021
Line 1:		Line 1:
	[[Main Page\|Home]] >> [[JASigning]]		[[Main Page\|Home]] >> [[JASigning]]
	----		----
	~~= Supported Software : JavaScript =~~

	=~~= Web Applications~~ : ~~HTML5~~ JavaScript ~~and WebGL~~ ==		= Core Software : JavaScript =
	The core JASigning software is implemented in HTML5 using JavaScript and WebGL. It functions on OS X, Windows, Linux, iOS, and some Android devices. It may work on other platforms. Linux usage has been tested only on Ubuntu at present.

	==~~== OS X ==~~==		== CWA Signing Avatars ==
	~~JASigning WebGL~~ software ~~should work with '''Firefox''', '''Chrome''', '''Opera''', and '''Safari'''.~~		The core CWA Signing Avatars software is implemented in HTML5 using JavaScript and WebGL. It functions on most platforms. See [[CWASA Platform Issues]] for details.

	~~==== Windows ====~~
	~~JASigning WebGL software should work with '''Firefox''', '''Chrome''', '''Opera''', '''Edge''', and '''Internet Explorer'''.~~

	~~==== Linux ====~~
	~~JASigning WebGL software should work with '''Firefox''', '''Chrome''', '''Opera''', '''Chromium''', and '''Vivaldi'''.~~

	~~==== iOS ====~~
	~~JASigning WebGL software should work with '''Safari'''.~~

	~~== Standalone Applications : Node.js and Electron ==~~
	~~Applications based on the~~ HTML5 JavaScript and WebGL ~~implementation can be installed on OS X, Windows, and Linux. Linux usage has been tested only on Ubuntu~~. ~~Experience of use~~ on ~~other versions would be welcomed~~.

	In addition to being able to animate SiGML data provided as text or via a URL, the applications act as a server, receiving SiGML data from any host on port 8052. A suitable client program is available as a Java Web Start application. ALternatively, on Unix systems, the command <code>nc localhost 8052 < mySigns.sigml</code> will send SiGML data to the application.

	~~==== OS X ====~~
	The software is provided in a Disk Image via a '''.dmg''' file. The image should be mounted and the application copied to disk. Security preferences may prevent the application being opened immediately because they do not come from the App Store or an identified developer. To run blocked applications it is necessary to open them by double-clicking with the control-key down or by right-clicking and choosing ''Open''. On future occasions the software should launch normally.

	~~==== Windows ====~~
	~~The software is provided as an executable '''.exe''' file that can be run to install and launch the software. A shortcut to the application will then be placed on the desktop.~~

	~~==== Linux ====~~
	The software is provided in an application image '''.AppImage''' file which is program that will install the software. The downloaded application image file must be made executable and then run. This may be done by right-clicking the file, selecting Properties, selecting the Permissions tab, and choosing to allow executing the file as program. Alternatively, the command <code>chmod +x SiGML-Player.AppImage</code> can be entered in a shell.

	= Legacy Software : Java =		= Legacy Software : Java =
Line 64:		Line 39:

	== Legacy Standalone Applications : Java ==		== Legacy Standalone Applications : Java ==
	The security constraints on running Java-based applications mean that the ~~JavaScript JASigning~~ applications are strongly preferred. At present, however, some functionality is only available in the Java software.		The security constraints on running Java-based applications mean that the [[CWA Signing Avatars]] applications are strongly preferred. At present, however, some functionality is only available in the Java software.

	Java-based applications for the [http://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7) and on the latest releases of OS X 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.		Java-based applications for the [http://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7) and on the latest releases of OS X 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.

John.Glauert at 15:18, 15 January 2021

2021-01-15T15:18:49Z

← Older revision		Revision as of 15:18, 15 January 2021
Line 1:		Line 1:
	[[Main Page]] >> [[JASigning]]		[[Main Page\|Home]] >> [[JASigning]]
	----		----
	= Supported Software : JavaScript =		= Supported Software : JavaScript =
Line 76:		Line 76:

	==== Windows ====		==== Windows ====
	[[JASigning]] applications and applets		[[JASigning\|Home]] applications and applets
	(apart from the SiGML Service Client) on Windows may require the appropriate		(apart from the SiGML Service Client) on Windows may require the appropriate
	<em>Microsoft Visual Studio C++ 2010 Redistributable Package</em>		<em>Microsoft Visual Studio C++ 2010 Redistributable Package</em>

John.Glauert: /* Standalone Applications : Node.js and Electron */

2020-11-02T13:15:08Z

Standalone Applications : Node.js and Electron

← Older revision		Revision as of 13:15, 2 November 2020
Line 19:		Line 19:

	== Standalone Applications : Node.js and Electron ==		== Standalone Applications : Node.js and Electron ==
	Applications based on the HTML5 JavaScript and WebGL implementation can be installed on OS X, Windows, and Linux. Linux usage has been tested only on Ubuntu ~~at present~~.		Applications based on the HTML5 JavaScript and WebGL implementation can be installed on OS X, Windows, and Linux. Linux usage has been tested only on Ubuntu. Experience of use on other versions would be welcomed.

	In addition to being able to animate SiGML data provided as text or via a URL, the applications act as a server, receiving SiGML data from any host on port 8052. A suitable client program is available as a Java Web Start application.		In addition to being able to animate SiGML data provided as text or via a URL, the applications act as a server, receiving SiGML data from any host on port 8052. A suitable client program is available as a Java Web Start application. ALternatively, on Unix systems, the command <code>nc localhost 8052 < mySigns.sigml</code> will send SiGML data to the application.

	==== OS X ====		==== OS X ====

← Older revision		Revision as of 17:42, 19 September 2025
Line 17:		Line 17:
	The use of JNLP files for applets is deprecated in modern browsers. Where it is supported, it is fairly seamless, but changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions.		The use of JNLP files for applets is deprecated in modern browsers. Where it is supported, it is fairly seamless, but changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions.

	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 ~~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 macOS it is necessary to override the default protection regime even though the components are correctly signed. See below for notes on using particular browsers.

	== Code Signing ==		== Code Signing ==
Line 28:		Line 28:
	The security constraints on running Java-based applications mean that the [[CWA Signing Avatars]] applications are strongly preferred. At present, however, some functionality is only available in the Java software.		The security constraints on running Java-based applications mean that the [[CWA Signing Avatars]] applications are strongly preferred. At present, however, some functionality is only available in the Java software.

	Java-based applications for the [https://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7, 10) and on the latest releases of ~~OS X~~ 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.		Java-based applications for the [https://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7, 10) and on the latest releases of macOS 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.

	On the supported platforms, that is, Windows and ~~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:		On the supported platforms, that is, Windows and macOS, 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 processor supports 64-bit operation.
	* Whether or not the operating system 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 (~~OS X~~).		* 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 (macOS).
	* For a JASigning applet: whether the browser is running in 32-bit or 64-bit mode.		* For a JASigning applet: whether the browser is running in 32-bit or 64-bit mode.

Line 56:		Line 56:
	JRE (Java Runtime Environment) installation(s).		JRE (Java Runtime Environment) installation(s).

	==== ~~OS X~~ ====		==== macOS ====

	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 ~~OS X~~ 10.7.5 Lion and 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''. On some versions, GateKeeper can be disabled using the General tab of Security & Privacy in the System Preferences.		Under the default settings for GateKeeper on macOS 10.7.5 Lion and 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''. On some versions, GateKeeper can be disabled using the General tab of Security & Privacy in the System Preferences.

	As documented in [[JASigning Release Notes]], on ~~OS X~~ 10.6 Snow Leopard and later some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player.		As documented in [[JASigning Release Notes]], on macOS 10.6 Snow Leopard and later some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player.

	== Legacy Web Applications : Java Applets ==		== Legacy Web Applications : Java Applets ==
Line 72:		Line 72:
	JASigning web applets should work with '''Internet Explorer'''. The 32-bit (x86) release of Java should be installed.		JASigning web applets should work with '''Internet Explorer'''. The 32-bit (x86) release of Java should be installed.

	==== ~~OS X~~ ====		==== macOS ====
	JASigning web applets should work with '''Safari'''.		JASigning web applets should work with '''Safari'''.