(Don't trust descriptions though, since strong encryption may hide an insecure implementation). Use the most secure implementation you can - First, check the list here: (look at the "Features" table where encryption is listed), reject the versions that don't have the features you need, and research the ones that look promising. connecting from work to home or vice-verse, how much you can trust your IT team or people at home, your ISP, your operating system), I'll just give a list for the most paranoid setup: Still use a password though, a compromised local device can still do damage you don't want to spread. Additionally if possible, you can use a firewall to limit access to only the local network. If you password is sent in plain-text, it can be intercepted. If that's not an option, definitely use a strong random password and ensure that your communication to the server is encrypted.Using port-forwarding, the VNC server can be configured to only accept connections on the remote desktop ports from itself and not any external connections. For a super-secure setup, you can handle this be using a secured connection to the server, with something like an SSH tunnel.Use strong authentication, never short or simple passwords.This software need not be proprietary, there are open-source options to choose fome. Some operating systems come with a default one, though it may not always be the ideal piece of software. Only use trusted remote-desktop software.Is there a way to mitigate or minimize this security risk?
0 Comments
Leave a Reply. |