X Windows on a Production Server

  • Xel02
  • Proficient
  • Proficient
  • Xel02
  • Posts: 261

Post 3+ Months Ago

Hi all,

Ever since I've gotten into systems administration I've been told that I shouldn't have X Windows on a production server as it just adds another possible source for vulnerabilities.

However I'm planning to deploy a test Linux application server running FreeNX and one of the requirements for the applications will probably be X (since we'll be exporting graphical programs)

Does anyone know if there are any serious problems with X on a server which will also act as a webserver and a database server?

If so is there any recommended solution other than splitting the servers up? Has anyone had luck chrooting X?

Thanks a lot.

  • Daemonguy
  • Moderator
  • Web Master
  • User avatar
  • Posts: 2696
  • Loc: Somewhere outside the box in Sarasota, FL.

Post 3+ Months Ago

X itself has a slew of vulnerabilities, which is why most servers that are internet facing do not run X.
However, if you require X to install/configure a package but NOT to actually run it you might consider simply having X NOT initiate at startup.
Use the command line function to begin X rather than xdm control.

Exporting graphical programs does not in and of itself *require* that the server be running a graphical environment. I would look into that a bit more.

Post Information

  • Total Posts in this topic: 2 posts
  • Users browsing this forum: No registered users and 33 guests
  • You cannot post new topics in this forum
  • You cannot reply to topics in this forum
  • You cannot edit your posts in this forum
  • You cannot delete your posts in this forum
  • You cannot post attachments in this forum

© 1998-2017. Ozzu® is a registered trademark of Unmelted, LLC.