FastX 4 Desktop Client Release Notes | StarNet Communications

Release Channel: 4.1.18

Mac Client: 4.1.16

Linux Client: 4.0.48

Early Access Channel: 4.1.18

Case 94285: When launched from the FastX web client, performance settings are now saved and retrieved properly
Case 93499: On Windows, “FastX 4” is now directly in the start menu instead of being in a “FastX 4” folder.

Windows:

Create a key pair using PuttyGen. Note: A RSA key won’t work yet until we resolve case 94379.
Save the private key to a file.
Copy the public key from the section where it tells you to copy and paste to the public_keys file.
Save the public key to the file $HOME/.ssh/authorized_keys on the Linux system.
Run Pageant. It will show up in the notification area.
Double-click the pageant icon in the notification area and add the private key you saved in step 2.
Install FastX Windows client 4.1.16 is available on FastX Server.

MacOS:

Create a key pair by running:
ssh-keygen -t dsa
Copy the public key by appending the contents of $HOME/.ssh/id_dsa.pub to $HOME/.ssh/authorized_keys on the Linux server
Add the key to the agent by running:
ssh-add
Install FastX client 4.1.16 is available on FastX Server.
Run the script:
/Applications/Scripts/postinstall
(This will change in the future!)

Case 94278: [Windows] View menu is disabled when not showing and active window connected to a server
Case 94257: Mouse wheel works properly when ALT key is down.

Case 94272, 94187: Fixed the use of Windows OpenSSH client instead of Plink, even when the connection had the “Use Plink” box checked. This version fixes that.
The “Plink Options” field is now merged with “SSH Options”.
Case 94235: The “File Manager” icon has been removed. File Manager has not yet been implemented in FastX4.
Case 93968, 94111: The wrong port was being used for SSH connections.
Case 94091: There is an option to reject fx-url requests (to prevent potential RCE). This facility will be improved in a future version.

Case 93865: Direct connections can be made to sessions running on a different server (a “compute node”), even when the connection to the “head node” is using SSH.
Case 93026: OpenId Connect authentication can now work on a server with a self-signed certificate, if the “Ignore SSL errors” box is checked.
OpenID Connect now works with a 4.1 server. (Earlier versions of the desktop client were not able to connect to a 4.1 server because of a breaking change regarding the token cookie.)
Case 93968: Minor changes to connection editor: “Route all Connections through SSH” option to disable new direct connect feature mentioned above. Separate tabs replaced with an always-visible “Advanced” box.
Case 93934: The “SSH_ASKPASS_REQUIRE” environment variable is set in order to support the new OpenSSH client included in Windows (and perhaps future versions of MacOS).

Case 92215: The Performance menu is now obtained using ClientComm.
This means that the customized performance menu works even when launching the desktop session from a web connection.
Case 93132: Instead of including all the application icons in one result, the icons are downloaded separately. Customers with a small number of applications probably won’t notice, but for a customer like PGS who creates a large number, this could populate the “start session” dialog faster, as the icons for the applications that are not shown don’t have to be downloaded. For SSH connections, this optimization requires at least server version 4.0.45.