<?xml version="1.0" encoding="UTF-8"?>
<rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>EnvyGeeks ~ By Jordon Bedwell</title>
	
	<link>http://www.envygeeks.com</link>
	<description>Engineering and administration for the simple and complicated mind</description>
	<lastBuildDate>Tue, 02 Feb 2010 21:26:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.envygeeks.com/envygeeks-blog" /><feedburner:info uri="envygeeks-blog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Lower Pricing ~ More time per slot</title>
		<link>http://feeds.envygeeks.com/~r/envygeeks-blog/~3/gtZr7G6uRgk/lower-pricing-more-time-per-slot</link>
		<comments>http://www.envygeeks.com/archives/lower-pricing-more-time-per-slot#comments</comments>
		<pubDate>Mon, 01 Feb 2010 16:18:28 +0000</pubDate>
		<dc:creator>EnvyGeeks</dc:creator>
				<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://www.envygeeks.com/archives/lower-pricing-more-time-per-slot</guid>
		<description>EnvyGeeks has done it again, and not only have we done it again, we've added more! We have extended our slots to 1 hour (previously 30 minutes) and reduced the price of 30 minutes by $10 (previously $30 per half hour).  We did this because a lot of people would love to get our service, but the prices are way to expensive for them! To top that off, we have lowered the price of &lt;a href="/services#Server-Management" title="Server Management"&gt;server management&lt;/a&gt;, our &lt;a href="/services#Server-Administration"&gt;basic package&lt;/a&gt; is now $100 a month and our &lt;a href="/services#Server-Administration"&gt;extreme package&lt;/a&gt; is only $200 a month! Previously our extreme package was $400 a month, but a lot of clients wanted to jump to extreme and just couldn't justify the cost, and now they can. To top that off, we now offer managed hosting, in two packages, &lt;a href="/services#Managed-Hosting" title="Managed Hosting"&gt;1GB of ram for $160&lt;/a&gt; a month or &lt;a href="/services#Managed-Hosting" title="Managed Hosting"&gt;2GB of ram for $260&lt;/a&gt; a month and it includes all the perks of management.  To kick off the opening of our new managed hosting, we will be offering a free upgrade to Extreme management for our managed hosting packages for the next two weeks.  &lt;a href="/services"&gt;So go check out our new services and pricing now&lt;/a&gt;.&lt;img src="http://feeds.feedburner.com/~r/envygeeks-blog/~4/gtZr7G6uRgk" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.envygeeks.com/archives/lower-pricing-more-time-per-slot/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.envygeeks.com/archives/lower-pricing-more-time-per-slot</feedburner:origLink></item>
		<item>
		<title>How to [truly] securely enable Root login</title>
		<link>http://feeds.envygeeks.com/~r/envygeeks-blog/~3/pfo20I6-ngg/how-to-truly-securely-enable-root-login</link>
		<comments>http://www.envygeeks.com/archives/how-to-truly-securely-enable-root-login#comments</comments>
		<pubDate>Wed, 27 Jan 2010 12:15:24 +0000</pubDate>
		<dc:creator>EnvyGeeks</dc:creator>
				<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://www.envygeeks.com/?p=617</guid>
		<description>Recently we had a spur of clients ask us to enable root for them.  Mostly because we don't allow our clients to root into most of our dedicated servers, we force clients to login as a normal user and then sudo -i into root (root login is completely disabled, no password so no ability to login ~ no su).  The problem was, even though we had fail2ban, this would not stop a large bot-net attack as fast as they could cycle, unless we got really strict, which we can't because of a catch 22.  Either be real strict and have to deal with abnormal amount of requests that we could not cover feasibly while keeping up our goal of being efficient or reduce security a tiny bit and come up with a user-name that would be as hard to guess as the password making it twice as hard to haxor up our shit.  The problem here is, as we saw more and more root requests come in and we rejected more and more unlocking (we always tell them they can enable it themselves but we will not cover it ~ if our investigation concludes a brute force into root) we started to take this as a challenge. Not really since we already knew how to do it.&lt;img src="http://feeds.feedburner.com/~r/envygeeks-blog/~4/pfo20I6-ngg" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.envygeeks.com/archives/how-to-truly-securely-enable-root-login/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.envygeeks.com/archives/how-to-truly-securely-enable-root-login</feedburner:origLink></item>
		<item>
		<title>Case Study: SEO and Index.PHP Removal</title>
		<link>http://feeds.envygeeks.com/~r/envygeeks-blog/~3/a6iBlgiHg0Y/case-study-seo-and-index-php-removal</link>
		<comments>http://www.envygeeks.com/archives/case-study-seo-and-index-php-removal#comments</comments>
		<pubDate>Wed, 27 Jan 2010 11:22:38 +0000</pubDate>
		<dc:creator>EnvyGeeks</dc:creator>
				<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://www.envygeeks.com/?p=593</guid>
		<description>Removing index.php from most applications results in a subjective removal. Index.PHP is still available to impact SEO (possibly ~ depending on Engine) and Index.PHP is available for Rewrites. Our biggest example is Expression Engine and Code Ignitor, and WP back in the day. Removing Index.PHP allows for "SEO Friendly" URL's but does not create an SEO friendly site. EXP: /url is available via /index.php/url and / is available via Index.PHP.&lt;img src="http://feeds.feedburner.com/~r/envygeeks-blog/~4/a6iBlgiHg0Y" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.envygeeks.com/archives/case-study-seo-and-index-php-removal/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.envygeeks.com/archives/case-study-seo-and-index-php-removal</feedburner:origLink></item>
		<item>
		<title>A donation from EnvyGeeks</title>
		<link>http://feeds.envygeeks.com/~r/envygeeks-blog/~3/_345TEo2SyA/a-donation-from-envygeeks</link>
		<comments>http://www.envygeeks.com/archives/a-donation-from-envygeeks#comments</comments>
		<pubDate>Fri, 15 Jan 2010 09:08:08 +0000</pubDate>
		<dc:creator>EnvyGeeks</dc:creator>
				<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://www.envygeeks.com/?p=455</guid>
		<description>It's that time of the year.  EnvyGeeks has a strong faith in giving back to the community that supports us.  Every month EnvyGeeks secretly donates some of our hours back to charity such as soup kitchens and people who can't afford our services but severely need it. We do this not only because it's good to remember where you came from, but to give back. This month we are are offering up something we hope the world will love FREE services for a select few people, and donating $15 of every Single-slot single-problem help purchase by a client to the American Red Cross.&lt;img src="http://feeds.feedburner.com/~r/envygeeks-blog/~4/_345TEo2SyA" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.envygeeks.com/archives/a-donation-from-envygeeks/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://www.envygeeks.com/archives/a-donation-from-envygeeks</feedburner:origLink></item>
		<item>
		<title>Installing Exim4 for PHP only</title>
		<link>http://feeds.envygeeks.com/~r/envygeeks-blog/~3/D9vJhIzkEVY/installing-exim4-for-php-only</link>
		<comments>http://www.envygeeks.com/archives/installing-exim4-for-php-only#comments</comments>
		<pubDate>Sun, 27 Dec 2009 12:49:24 +0000</pubDate>
		<dc:creator>EnvyGeeks</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://www.envygeeks.com/?p=207</guid>
		<description>Many times and many more times I hear about people who install Exim4 and then forget to properly secure it, or even disable parts of it. This is most of the time the case on a lot of companies default images for VPS servers and even on Debian/Ubuntu default install on it’s own. Today we are going to learn how to install Exim4 and configure it for PHP only email because most of the time we use external email providers for our actual emails, so lets get started shall we? First we need to start by installing exim4&lt;img src="http://feeds.feedburner.com/~r/envygeeks-blog/~4/D9vJhIzkEVY" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.envygeeks.com/archives/installing-exim4-for-php-only/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.envygeeks.com/archives/installing-exim4-for-php-only</feedburner:origLink></item>
		<item>
		<title>Bash Looping Tips and Tricks</title>
		<link>http://feeds.envygeeks.com/~r/envygeeks-blog/~3/OM90gqTJ6fg/bash-looping-tips-and-tricks</link>
		<comments>http://www.envygeeks.com/archives/bash-looping-tips-and-tricks#comments</comments>
		<pubDate>Sun, 27 Dec 2009 11:48:33 +0000</pubDate>
		<dc:creator>EnvyGeeks</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Programming]]></category>

		<guid isPermaLink="false">http://www.envygeeks.com/?p=182</guid>
		<description>Here are some bash programming tips that some Linux administrators will find useful.  With the soon to be public release of my client IPTables script, I feel the need to explain some of the methods and tricks I use in my bash programming and to help spread good programming in Bash scripting.&lt;img src="http://feeds.feedburner.com/~r/envygeeks-blog/~4/OM90gqTJ6fg" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.envygeeks.com/archives/bash-looping-tips-and-tricks/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.envygeeks.com/archives/bash-looping-tips-and-tricks</feedburner:origLink></item>
		<item>
		<title>Hardened HTTP Server /etc/sysctl.conf</title>
		<link>http://feeds.envygeeks.com/~r/envygeeks-blog/~3/5T_xAP_mtdQ/hardened-http-server-etcsysctl-conf</link>
		<comments>http://www.envygeeks.com/archives/hardened-http-server-etcsysctl-conf#comments</comments>
		<pubDate>Thu, 24 Dec 2009 06:27:26 +0000</pubDate>
		<dc:creator>EnvyGeeks</dc:creator>
				<category><![CDATA[Config Files]]></category>

		<guid isPermaLink="false">http://www.envygeeks.com/?p=100</guid>
		<description>The following /etc/sysctl.conf is a basic hardened /etc/sysctl.conf for a server that contains an http server, smtp server and mysql as well as the average applications that a normal web server would contain.&lt;img src="http://feeds.feedburner.com/~r/envygeeks-blog/~4/5T_xAP_mtdQ" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.envygeeks.com/archives/hardened-http-server-etcsysctl-conf/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.envygeeks.com/archives/hardened-http-server-etcsysctl-conf</feedburner:origLink></item>
		<item>
		<title>A Thought on Passwords</title>
		<link>http://feeds.envygeeks.com/~r/envygeeks-blog/~3/Lt0FCyOOSz0/thinking-different-yes-different</link>
		<comments>http://www.envygeeks.com/archives/thinking-different-yes-different#comments</comments>
		<pubDate>Wed, 23 Dec 2009 06:11:36 +0000</pubDate>
		<dc:creator>EnvyGeeks</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[password security]]></category>

		<guid isPermaLink="false">http://www.envygeeks.com/?p=36</guid>
		<description>as the world turns many people often don't realize how much information they give away.  how much of this information can actually hurt them and how to combat this.  what do I mean by this? I mean simply put, that, if you give out information and you are entirely uniform in your thinking you could lead yourself to the ultimate demise, the same demise that plagues a lot of people, password hacks.&lt;img src="http://feeds.feedburner.com/~r/envygeeks-blog/~4/Lt0FCyOOSz0" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.envygeeks.com/archives/thinking-different-yes-different/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://www.envygeeks.com/archives/thinking-different-yes-different</feedburner:origLink></item>
		<item>
		<title>NGINX Efficiency Tricks</title>
		<link>http://feeds.envygeeks.com/~r/envygeeks-blog/~3/kssPTu5Gndo/hello-world</link>
		<comments>http://www.envygeeks.com/archives/hello-world#comments</comments>
		<pubDate>Sun, 18 Oct 2009 20:31:54 +0000</pubDate>
		<dc:creator>EnvyGeeks</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://www.envygeeks.com/?p=1</guid>
		<description>NGINX (pronounced Engine-X) is one of the most lightweight and efficient HTTPD servers you could ever come across, but it's no stranger to lack of performance tuning from the average user.  Today we will be going through some basic tips and tricks to keep NGINX performing in tip top shape and learning a bit about how to adjust spawns based on situation.&lt;img src="http://feeds.feedburner.com/~r/envygeeks-blog/~4/kssPTu5Gndo" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.envygeeks.com/archives/hello-world/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.envygeeks.com/archives/hello-world</feedburner:origLink></item>
		<item>
		<title>Optimize a Site for Speed</title>
		<link>http://feeds.envygeeks.com/~r/envygeeks-blog/~3/UzSrxoWq8uU/optimize-a-site-for-speed</link>
		<comments>http://www.envygeeks.com/archives/optimize-a-site-for-speed#comments</comments>
		<pubDate>Sat, 20 Jun 2009 06:46:37 +0000</pubDate>
		<dc:creator>EnvyGeeks</dc:creator>
				<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://www.envygeeks.com/?p=61</guid>
		<description>Speed of a site, it's not just about how fast a server is, but how fast the front-end is too. It's a multi-way street, that is for sure. Everybody knows this. EnvyGeeks takes high-impact and makes it low-impact for it's audience, high-availability is always a thing of concern, whether it be speed or other. As part of a 3 Part tutorial from server to site to celebrate my one month happiness with VPS.Net, we will start with our sites. How can we improve their speed and make them faster.&lt;img src="http://feeds.feedburner.com/~r/envygeeks-blog/~4/UzSrxoWq8uU" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.envygeeks.com/archives/optimize-a-site-for-speed/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.envygeeks.com/archives/optimize-a-site-for-speed</feedburner:origLink></item>
	</channel>
</rss>
