Alert to show someone is remoted in

[Heman]

Hi Team,

I often remote into my client's computers to troubleshoot and want to assure them that I have logged off. Also want to make sure they know that I am actively still troubleshooting the computer. Other than the UltraVNC system tray icon, there is no other indication that there is an active session?

I've seen other products show a message in the bottom right corner of the desktop. See examples: https://www.screencast.com/t/APvKCiOBN0

Is there any way I can show a clear message on the remote computer that someone is remotely controlling their computer?

[fvoigt]

Hi all,

is there any solution for this request?

It would be awesome if the client get an message for activate/disable the session.

best regards

[AnotherUVNCuser]

If this is being implemented, please make it optional/toggleable

[glac]

Hello,

I am interested in that feature too.

In fact, we have to stop using UltraVNC because having that clear indication is an obligation through RGPD.

UltraVNC system tray icon is not enought.

[RudiDeVos]

Accepted, look indeed a good idea

[alazif66]

Accepted, look indeed a good idea

This is the Autoit code that displays a transparent banner over all applications, I think in C it will be possible to write similarly

Code: Select all

#include <GuiConstants.au3>

GuiCreate("My message box", 400, 78,(@DesktopWidth-400)/2, (@DesktopHeight-78)/2, $WS_POPUP + $WS_DLGFRAME)
WinSetTrans("My message box", "", 150)
WinSetOnTop("My message box", "", 1)


$Button_1 = GuiCtrlCreateButton("OK", 340, 20, 50, 30)
$Label_2 = GuiCtrlCreateLabel("Here is some text", 20, 20, 300, 40)
GUICtrlSetFont($Label_2, 24)
GuiSetState()
While 1
    $msg = GuiGetMsg()
    Select
       Case $msg = $Button_1
        ExitLoop
    EndSelect
WEnd

When it comes to security, I have two ideas for improving it that would not integrate into the VNC implementation.

The first is to extend the blocking time after unsuccessful login attempts. E.g. 3 unsuccessful attempts = 5 minutes blockade, another attempt = 15 minutes, another 30 minutes, etc.

The second idea is to add the PIN function after successful login. If you do not provide the correct PIN after e.g. 3 minutes from logging in, the session is disconnected. This would provide a two-level password and would not require NT login etc. The PIN could be saved encrypted in the ultravnc.ini