NoMachine 7.7.4

What's new in this version:

- Adding support for Okta primary authentication with public application in NX protocol
- Automatically rebuild nxusb.ko kernel module after its upgrade
- Replacing the UserNXDirectoryPath key with UsersDirectoryPath
- Updating nxhtd in packages v. 7 and 6. to Apache v. 2.4.51
- Possible local privileges escalation by USB forwarding
- A NoMachine server/node host becomes unreachable when it gets the subscription reminder
- After updating to macOS 11 (Big Sur), keyboard and mouse are no longer responsive in the login window
- Authentication fails in NIS environment on Fedora 33, RHEL 8 and CentOS 8
- Black screen occurs when connecting to macOS Big Sur (M1) with display turned off
- Black screen occurs when rebooting macOS 11 (Big Sur) or when making logout
- Cannot generate any longer OTP password to connect to the Cloud Server node
- Cannot synchronize the cluster db when more than 900 profile rules are set
- Copy&paste inside the session results in pasting the text previously selected
- Display server terminates unexpectedly on multi-monitor Mac
- Error 'nxserver.exe is not valid' is not valid occurs when connecting by the web to Linux running on Hyper-V
- First connection to a Windows node of a Cloud Server fails with "The session negotiation failed"
- Frequent termination of the nxserver.bin daemon on some Linux machines
- Grabbing the keyboard doesn't work when Wayland is enabled
- Kerberos Keyring Cache is not correctly cleaned up
- Maximizing applications expands across all monitors when 'full screen on all monitors' is selected
- NoMachine client uses by default the system username also when connecting with the library SSH client
- NoMachine does not restore resolution after disconnection on Mac OS with M1
- NoMachine does not work correctly after installing on Windows XP 64 bit
- Option "Change the remote display resolution to match the window" is not disabled in the UI when the server is configured to forbid resize
- Session fails to start when the file path contains the word 'keeper'
- Starting a connection through a proxy fails with "invalid argument" error
- The connection monitor is shut down and restarted every seconds causing high CPU consuming
- The connection panel in the NoMachine client menu shows an incorrect UDP port
- The first reconnection attempt to macOS after system reboot, fails
- The screen blanking is not deactivated on Mac M1 upon session disconnection
- When key-based authentication is chosen, the key must be added twice
- NoMachine failover cluster is not working properly with SSH protocol