Foralllinux.blogspot.com Website Review

its been long time since i posted something here. i am trying to make time to write something and make this blog more active. as you know, vnc protocol is unencrypted. even though the log in process has some encryption, it is possible to sniff vnc traffic and collect sensitive infomration. you can fully secure a vnc session by tunnelling it via a ssh tunnel. another advantage of tunnelling vnc via ssh is that you do not need to open vnc ports – tcp 590x on your subnet’s security list. the existing rule for ssh traffic will do i expect you have desktop environment installed on the instance. by default, vnc is configured to use xterm as the terminal emulator and $ sudo yum -y install tigervnc-server pixman pixman-devel libxfont we are setting up vnc for the default user ‘opc’, if you want to set it up for another user, just change the steps accordingly. log in to the user opc and set up vnc pas*word $ su – opc 3.     add a vnc service configuration file. the vnc daemon configuration file is available in systemd directory description=remote desktop service (vnc) after=syslog.target network.target do remember to change the user name if you are setting vnc for a different user, here we are setting it up for user opc. also, please note that the parameter “-localhost” makes vnc server to listen on loopback interface and accept connection from a tunnel only. you must reload the systemd system initialization program after setting up the vnc server. 4.     start vnc server. you can now start your vnc server using: the vnc configuration is different in previous versions on rhel based systems. you may follow the below steps to set up a secure vnc server. 3.     set vnc pas*word log in to the user opc and set up vnc pas*word we have set up the vnc server to be available only via a secure tunnel. as such, we need to create an ssh tunnel from the client to       on windows clients, you may set up ssh tunnelling using putty.