Have any questions? Email: info@flynet.email. US: +1 617-778-7259. UK: +44 (0)3333 110 370.

 

Terminal Emulation without Java

Is your organisation looking to eliminate Java this year? If so, you’re not alone, many organisations are looking to eliminate all reliance on Java by the end of 2019. Especially in their business-critical applications, like their terminal emulator.

In the terminal emulation market, the move away from Java has been bubbling for some time. Historically, Java has been viewed as insecure, with a Veracode Study finding as many as 88% of Java applications containing at least one vulnerable component. As organisations became increasingly more security conscious and breaches became more widespread and damaging, many started to look for alternative solutions. In 2017/18, the decision was taken out of many organisation’s hands. The majority of browsers, and Oracle stopped supporting the Java Applet.

Unfortunately, a number of organisations moved to alternative emulators that relied on Web Start, which Oracle have recently announced they will no longer be supporting. After this disruption, and with the consequences of a breach higher than ever, 2019 looks to be the year when most large organisations will eliminate Java entirely.

So, what are the Java-free alternatives for terminal emulation?

Browser based emulation has made incredible strides recently, becoming the obvious choice for organisations looking to remove Java reliance. There is no sacrifice, as zero-client web-based emulators like Flynet Viewer are now out-performing their desktop counterparts in terms of speed and functionality. Pure HTML emulators like Flynet Viewer do not require any applets or plugins on the device and provide the organisation with maximum flexibility in terms of access devices and operating systems, without compromising functionality or security.

The centralised, server-based web applications can be secured and maintained to the highest standards. For example, Flynet Viewer communications made between the server and host are made over a telnet connection secured by a SSL/TLS wrapper. All Flynet Viewer communications made between the application server and the client are primarily conducted using Web Sockets and where this is not supported HTTPs is used.

  • Supports Secure Sockets Layer (SSL v3.0 and TLS v1.0, v.1.2 and v1.3) encryption.
  • Provides SSL authentication using digital client certificates, user generated as well as third party. Standard authentication technology is built into Flynet Viewer.
  • FIPS 140-2 Validated Cryptographic Module.
  • Supports NT domain authentication / Active Directory / Azure Directory authentication.
  • Supports multi-factor authentication
  • Supports most off the shelf and proprietary IAM and SSO solutions with templates available for integration.

Flynet offer a fully supported, free 30-day evaluation of the Flynet Terminal Emulator, please select your preferred download method.