Forum Replies Created
But let me summarize: you make a lot of noise for basically nothing
It is not basically nothing. It is a security fault, NX or Apple or another SW. A user may authenticate and use another one account.
and in the end your problem is that now you have to pay a moderate amount for the privilege of running such a (in your words) wonderful terminal server
I did not talk about paying.
I used NX 3.5 with linux machines a few years ago. It was wonderful. Remote sessions were opened only with user credentials and without being presented at local display, I also authenticated with my own ssh key. One local user even did not notice that there were other users with graphical interfaces running in parallel. Accessing remotely did not expose the session to whoever could be next the computer. This is an important issue.
Since Linux as desktop have many problems and too much misanderstanding between distributions I migrated to another unix like SO, the OSX. Where I finally integrated my PIN apps with my cel phone and tablet.
Although it is unix , the same behavior does not occur.
It would be nice if it could happen the same way as with Linux. A sharing display app to give remote support is VNC or Teamviewer or RDP. NX should be more than that. An app to really work remotely, not depending on third party internet server authentication, specially now with NSA exposed spying. Who knows if third party authentication servers places back doors to governments or others?
VNC also does not have the graphical quality and security robustness as NX/SSH.
I hope you could improve NX on OSX as it was for Linux.
Britgirl, In relation to exposing the problem, It was my first test with nx on MAC.
I was trying to open a remote session to use a MAC session on another non MAC machine, while another user is already using the foreground session.
It is not a hidden or difficult problem to trigger. It is the obvious and immediate operation.
When connecting to MAC (from Windows machine) with the third user credential (username and password) I got the screen of the session of the first or the second user sessions already running on MAC. The password of the third user had to be correct. With an erroneous password the connection was not completed.
With 2 running sessions on MAC the connection of the third brought the screen of the second MAC user that was open in background.
Closing the second user session, so only the first user session was running in foreground, repeating the connection with the third user credentials brought the first user active session to the viewing windows machine. In both cases the third user, using its own personal credentials could see the other sessions on windows nx client viewing machine.
The problem is that a user could see the session of another user without the credential of that session. I do not know if the security issue is caused by Apple Fast User Switching mechanism or by NX server authentication.