<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Technology, Theology, and Anything In Between &#187; computer security</title>
	<atom:link href="http://www.technotheologian.us/tag/computer-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.technotheologian.us</link>
	<description>This blog explores theology, technology, and (sometimes) the relation between the two.</description>
	<lastBuildDate>Sat, 23 Jul 2011 03:51:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Basic UNIX security on the Internet</title>
		<link>http://www.technotheologian.us/2009/09/basic-unix-security-on-the-internet/</link>
		<comments>http://www.technotheologian.us/2009/09/basic-unix-security-on-the-internet/#comments</comments>
		<pubDate>Tue, 15 Sep 2009 02:58:53 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[computer security]]></category>
		<category><![CDATA[cracking]]></category>
		<category><![CDATA[freebsd]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://www.technotheologian.us/?p=151</guid>
		<description><![CDATA[<p>I realize very few people that are my friends will need this information, but there are a few that may benefit from it. To that end, I wanted to write about an ongoing problem I&#8217;ve had with a break-in that happened to me. One of my development systems on the Internet was compromised recently.</p> <p>I [...]]]></description>
			<content:encoded><![CDATA[<p>I realize very few people that are my friends will need this information, but there are a few that may benefit from it.  To that end, I wanted to write about an ongoing problem I&#8217;ve had with a break-in that happened to me.  One of my development systems on the Internet was compromised recently.</p>
<p>I had just opened an account and was trying the system out, and one morning I woke up to find abuse emails pouring into my mailbox.  When I logged in and looked at the system, I found several new usernames created, and hacking scripts.  Since then, my machine has been re-imaged to prevent the possibility that a rootkit had been installed.  The abuse reports are still pouring in from machines who were attacked from mine.  It is a big paperwork mess and not fun at all.</p>
<p>To prevent this in the future, or at least reduce the risk by a large amount:</p>
<p>1.  Disable PermitRootLogin.  I didn&#8217;t think to do this, because most of my Internet systems are FreeBSD, and this option is set to &#8220;yes&#8221; by default.  Most Linux distros (at least CentOS and Debian) set this to &#8220;yes&#8221;.  This is not a good option, as &#8220;root&#8221; is an easy username to guess, and after that, it is only a matter of brute-force cracking.</p>
<p>2.  Move SSH to a different port if you can.  This will keep most &#8220;script kiddies&#8221; out, as they probably aren&#8217;t going to do a complete port scan of the machine.</p>
<p>3.  If possible, write some firewall rules that are very strict to only allow the IP addresses and ports that are really needed.  In other words, grant only as many privileges per IP address and port to provide the services you are advertising.  Anything more can create extra vulnerabilities.</p>
<p>Again, my production systems have been locked down in this manner.  I didn&#8217;t think to do it on a development system, since it was only a week old and I was trying to get Xen virtualization working on it first.  I&#8217;ve learned my lesson:  secure the machine first.  I was surprised how many attacks happen every day with crackers connecting via SSH.</p>
<p>Please do at least secure your systems with these ideas, and you will have less chance of a machine being compromised by malicious attacks.   There are scripts available that will email you if they see any failed login attempts.    If you have any additional ideas, please feel free to post them!  I hope this has been helpful to someone, and a reminder that computer security is an important item we need to be vigilant about.  I dropped my guard for a week and I was taken advantage of.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.technotheologian.us/2009/09/basic-unix-security-on-the-internet/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
