Category Archives: Howto Tutorials (EN)

Knowledge Network for Tutorials, Howto’s, Workaround, DevOps Code for Professionals.

Secure VNC connection over SSH Tunnel

SSH Tunnel to Linux VNC Servers

VNC connections are considered unsafe because they are not encrypted. VNC sessions can be encrypted with OpenSSH, where traffic is routed through a secure SSH tunnel and is protected.

The SSH tunnel requires user login and the VNC port. The client command runs in the Linux CLI as follows:

$ ssh -L 5901:127.0.0.1:5901 -N -f -l USER 10.127.55.77

If user USER replaces it with the actual user name, a password is prompted to run the tunnel. Please note that this is the password for the SSH login, the user login to the VNC can ideally be the same UID, then the password is the same. The port that needs to be tunneled is 5901. The command runs on the computer of the VNC viewer. Registration takes place as usual:

login as: USER
USER@10.127.55.77's password:
Last login: Thu Oct 11 07:59:26 2018 from 10.127.55.70
[USER@fedora ~]$

With the VNC viewer, the virtual desktop session can now be run to the loopback address:

vncviewer 127.0.0.1:5901

Note: The options must be enabled for the OpenSSH Server in the /etc/ssh/sshd_config configuration file.

AllowTcpForwarding yes
X11Forwarding yes

SSH tunnel on Windows to vnC server

On Windows, an SSH tunnel to the VNC server can be opened using PuTTY or KiTTY, tunneling via the loopback interface and port 5901.

VNC connection over SSH Tunnel, KiTTY Configuration

Under the Category, Connection – SSH – Tunnels, at Source Port 5901 is entered, Destination is 127.0.0.1:5901, then by clicking on Add the tunnel is added.

VNC connection over SSH Tunnel, KiTTY SSH Tunnel Configuration

Clicking on Open starts the tunnel by logging in to the VNC host.

The secure SSH connection to the VNC server can now be initialized. Remote Host registers the loopback address 127.0.0.1 with port 5901 in the TightVNC viewer: 127.0.0.1:5901

VNC connection over SSH Tunnel, TightVNC Connection

After registration, Connection provides information about the current connection by clicking on the icon in the menu bar.

connection information

Registry Key Jumper

Registry Key Jumper helps you to find registry keys

The free utility helps you to find a registry key and automatically jumps to the registry path where regedit.exe with the handy parameter is opened, as an example here to the registy key Run.

HKEY_LOCAL_MACHINE-SOFTWARE\Microsoft\Windows\CurrentVersion\Run
registry key jumper
Illustration: Registry Key Jumper

In the Registry Key Jumper you can insert keys from the menu, create new entries, the keys are added directly from the clipboard, the keys can be edited and remain saved, so that they are quickly and easily reopened in the Microsoft Registry Editor when re-edited.

jump to registry key

Sources Link: https://www.sordum.org/

Remarks

Windows Registry is a hierarchical database that stores low-level settings for the Microsoft Windows operating system and for applications that opt to use the registry. The kernel, device drivers, services, Security Accounts Manager, and user interfaces can all use the registry. The registry also allows access to counters for profiling system performance.

Windows Registry information

Windows Registry contains information, settings, options, and other values for programs and hardware installed on all versions of Microsoft Windows operating systems. For example, when a program is installed, a new subkey containing settings such as a program’s location. Its version, and how to start the program, are all added to the Windows Registry.

Prior to the Windows Registry, .INI files stored each program settings as a text file or binary file. They often located in a shared location that did not provide user-specific settings in a multi-user scenario. By contrast, the Windows Registry stores all application settings in one logical repository and in a standardized form.

Registry Keys and values

The registry contains two basic elements: keys and values. Registry keys are container objects similar to folders. Registry values are non-container objects similar to files. The keys may contain values and subkeys. Keys are referenced with a syntax similar to Windows’ path names, using backslashes to indicate levels of hierarchy. Keys must have a case insensitive name without backslashes.

The hierarchy of registry keys can only be accessed from a known root key handle (which is anonymous but whose effective value is a constant numeric handle) that is mapped to the content of a registry key preloaded by the kernel from a stored “hive”, or to the content of a subkey within another root key, or mapped to a registered service or DLL that provides access to its contained subkeys and values.