[Wine] Homefront dedicated Server

Martin Gregorie martin at gregorie.org
Thu Apr 14 07:41:32 CDT 2011


On Thu, 2011-04-14 at 06:47 -0500, zap-hosting wrote:
> thanks martin, but to change the run level to multi-user use of wine
> won't solve my problem.
> 
You asked about starting without a graphical interface as a way to avoid
getting hacked, so I explained how to start a *NIX server without a
graphical interface. 

The only other generic approaches to preventing a server getting hacked
involve:
- running the firewall (enabling IPTables for both IPV4 and IPV6) with
  absolutely all port ranges excluded apart from those used by your
  server software  

- Enabling SELinux and/or Apparmor and custom configuring it to support
  your server software.

Since both these are off-topic for Wine (apart from configuring SELinux
and/or Apparmor to support Wine apps), further discussion belongs on
your distro's forums.

For this thread you really need to explain exactly what you're trying to
achieve, what sort of attach you are expecting your Homefront server to
attract and what sort of attack you're trying to prevent rather than
talking about the configuration options for running Homefront and asking
vague questions about anti-hacking measures.

My personal take is that no Windows application is likely to be secure
enough to run in any environment where it may be exposed to malicious
activity and that wrapping it in an unhardened work in progress, such as
Wine, can only make matters worse.

As a subsidiary question, why should you even care about securing what
is after all merely a game server that should be running on your home
network behind a NAT-capable router that, by itself, will keep external
intruders out unless you're unwise enough to enable port forwarding.


Martin





More information about the wine-users mailing list