NoMachine 6.4.6

What's new in this version:

List of enhancements:
- Integrating Linux or Mac system groups into NoMachine trusted groups
- Limiting trusted users to specific users' desktops
- Extending access to physical desktop to unprivileged users with Linux Terminal Server products
- Adding a configuration key to show or hide the NoMachine virtual clipboard when text is copied
- Extending the UserScriptAfterLogin custom script to accept the client ip parameter
- Adding the possibility to require connection's authorization also for administrators
- Extending the 'nxplayer --session' command to always create a new session
- Giving the possibility to show servers' hierarchy in a tree structure on console
- Integration of Web Sockets technology into WebPlayer

This latest release also provides the following fixes:
- Pulldown menus are displayed only on one monitor when running a custom session in floating window mode in a multimonitor set-up
- Cannot use microphone with Skype, Slack or browsers
- Authentication dialog box appears while creating a virtual session requesting user to authenticate
- Cannot connect to NoMachine on Windows with usernames similar to ' -))'
- Cannot authenticate to the server's UI when the administrator's password contains Unicode characters
- The NoMachine client doesn't restore the fullscreen state on all screens
- Can't create virtual desktops having a 7680x2880 screen or above
- License for Raspberry doesn't match the OS and platform
- Creating display fails on headless machines when connecting by SSH protocol
- NoMachine packages don't detect openSUSE Tumbleweed
- NoMachine installation doesn't detect SUSE SLED/SLES 15
- Incorrect error message to modify during installation on Arch Linux
- The server doesn't run the sessreg command on the system even if it's enabled in the configuration
- Connections to macOS Mojave are not interactive
- Two factor authentication hangs with NoMachine when SecureAuth RADIUS v. 8.0 is used
- An unitialized memory read in the nxfs.sys driver allows a local user to cause BSOD on Windows 10