So I cannot reproduce the issue any more. Quickly tested file transfer too which worked fine for me at least when a user is logged in. When logging out all users no file transfers are possible but this behavior was explained in another thread as UVNC cannot know which credentials to apply as it uses the one of the logged-on user. I was just wondering if potentially the permissions of the VNC authentication user could be used in such case - at least if mslogon authentication is used where the remote connection is using a local authentication. This would of course not work for built-in VNC authentication as there is no mapping to a local Windows user account. But it would work if mslogon is selected. However it would yield the question if the impersionation should change to the logged on user as soon as one is logged on and only use the mslogon username when no user is logged on (as a fallback) or always the mslogon user should be used (as it is the one the client essentially uses to authenticate to the server). I would personally prefer to use the currently logged on user credentials when available and fallback to mslogon user when none is available as users might rather expect to get access to the same files as the user they are remotely controlling regardless of the authentication credentials of VNC.īut I see no security issue right now if all users are logged out to use the credentials of the mslogon authenticated account. In my specific case I admit the user does not have permissions to log on and it's only used for VNC authentication and also it does not have admin credentials.Īs in many cases it would also be possible to log on to the system using the very same account (known to the client).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |