- Vnc vs ssh overhead how to#
- Vnc vs ssh overhead install#
- Vnc vs ssh overhead software#
- Vnc vs ssh overhead code#
- Vnc vs ssh overhead windows#
Vnc vs ssh overhead code#
You can connect over SSH into another machine from Visual Studio Code and interact with files and folders anywhere on that remote filesystem.
Other desktop environments aren't much better.SSH, or the secure shell protocol, lets you access a remote computer or virtual machine securely over a network connection. That is huge, imagine the extra attack surface this ex-server will have once it's installed.
Vnc vs ssh overhead install#
Trying to install a Gnome desktop environment on my Archlinux server tells me "Total Installed Size: 1370.86 MiB".
Vnc vs ssh overhead windows#
configuration ? Who needs human-readable config files ? Let's store everything in binary databases that you can't really see nor edit unless you use their provided utilities, just like the Windows registry, and also let's start a bunch of daemons as root to use up resources even when you're not using the desktop).
Vnc vs ssh overhead software#
Once of the other reasons why I don't recommend this software and most of the Linux desktop environments is that they take over the entire system almost like a rootkit, and implement their own versions of everything (authentication ? No more rock solid users and groups, let's run this Policykit nonsense as root that gives permissions based on some unreadable, obscure XML files. Once you install all this desktop-grade Gnome (or similar) software you can already consider your server compromised, since there are so many bugs left to be exploited in this horrible, huge collection of applications (besides the fact that it's not designed for productivity and uses a ton of resources). You're going to install VNC to access what, a black screen ? No, you wanted to access an entire desktop environment, and that is the real problem. The problem isn't VNC - don't get me wrong, VNC is a horrible protocol and has many flaws (the biggest being the lack of encryption support so everything goes over the network in plain text), but it isn't the main reason its usage is not recommended on servers.
Vnc vs ssh overhead how to#
Heck, even Windows server can be installed GUI-free these days, and if that doesn't make you think about the relative merits of only knowing how to click on things, I really don't know what to say to you. You'll also find your future employment opportunities severely limited if you can't script and automate away your job - the industry is going away from GUI admin tools. Clicking on things feels productive, but it's actually about the worst way to do something deeply technical. Operator efficiency: GUIs do not lend themselves to scripting and other forms of automation. Not running them means more resources for doing useful work. System efficiency: X11, and the GUI environments that people tend to run on them, consume a decent amount of RAM, especially on a limited resources system like a NUC.
Actually, "ruin your day" probably applies to the previous point, too. Not sure if that makes a difference.Īttack surface: more programs, especially networked ones, means more opportunities for someone to find a bug and get in.ĭefect surface: as above, but replace "someone" with " Murphy", and "get in" with "ruin your day". It's hosting a number of other applications. What are the downsides of installing VNC on a server?Įdit: this isn't just a web server. VNC would only be able to be accomplished inside our subnet, so I'm at a loss as to why this would be an issue other than "it's another package to maintain", and with Ubuntu's apt package manager that becomes a non-issue. Obviously you're opening up another port for an attacker rebuttal: we're behind two university firewalls (the main university network firewall as well as our subnet's own special firewall). Is there some miraculous downside to having VNC access to a server that I am unaware of? It isn't hooked up to a monitor the only access into it through SSH. I would much prefer not to run X or VNC on the server if we can get away with it. However, he replied with the following comment: I suggested to our new technical director that we install VNC on this server to make my life a lot easier (in fact it had VNC installed before he was hired, and then he uninstalled it). I'm comfortable with the terminal and SSH-ing into the server, however I find that a lot of tasks that I need to do are just so much easier through screen-sharing (VNC). We have an Intel NUC in my university's language department that will soon host a web application used by faculty and students in the department.
0 kommentar(er)
