<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Warzone on System Overlord</title><link>https://systemoverlord.com/tags/warzone.html</link><description>Recent content in Warzone on System Overlord</description><generator>Hugo</generator><language>en-us</language><managingEditor>david@systemoverlord.com (David Tomaschik)</managingEditor><webMaster>david@systemoverlord.com (David Tomaschik)</webMaster><lastBuildDate>Sun, 21 Aug 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://systemoverlord.com/tags/warzone/index.xml" rel="self" type="application/rss+xml"/><item><title>(Slightly) Securing Wargame Servers</title><link>https://systemoverlord.com/2016/08/21/slightly-securing-warzone-servers.html</link><pubDate>Sun, 21 Aug 2016 00:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2016/08/21/slightly-securing-warzone-servers.html</guid><description>&lt;p&gt;I was setting up some wargame boxes for a private group and wanted to reduce the
risk of malfeasence/abuse from these boxes. One option, used by many public
wargames, is locking down the firewall. While that&amp;rsquo;s a great start, I decided
to go one step further and prevent directly logging in as the wargame users,
requiring that the users of my private wargames have their own accounts.&lt;/p&gt;
&lt;h3 id="step-1-setup-the-private-accounts"&gt;Step 1: Setup the Private Accounts&lt;/h3&gt;
&lt;p&gt;This is pretty straightforward: create a group for these users that can SSH
directly in, create their accounts, and setup their public keys.&lt;/p&gt;</description></item></channel></rss>