<?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>Aotearoa Web Design Ltd - WordPress Website Design and Development &#187; security</title>
	<atom:link href="http://www.aotearoawebdesign.co.nz/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.aotearoawebdesign.co.nz</link>
	<description>WordPress Website Design and Development</description>
	<lastBuildDate>Sun, 29 Jan 2012 02:40:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>WordPress Security Revisited &#8211; Table Prefixes</title>
		<link>http://www.aotearoawebdesign.co.nz/blog/wordpress-security-revisited-table-prefixes/</link>
		<comments>http://www.aotearoawebdesign.co.nz/blog/wordpress-security-revisited-table-prefixes/#comments</comments>
		<pubDate>Sun, 06 Dec 2009 09:18:35 +0000</pubDate>
		<dc:creator>Jason Koning</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[prefix]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[table]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.aotearoawebdesign.co.nz/?p=876</guid>
		<description><![CDATA[Recently, as another added security measure I decided to change the table prefix of my WordPress database in MySQL. Easy enough done, log in to phpMyAdmin and change all the wp_ to, well &#8211; whateveryoulike_ For example: wp_options becomes yournewprefix_options The only catch here is WordPress actually saves some options using the wp_ prefix &#8211; [...]]]></description>
		<wfw:commentRss>http://www.aotearoawebdesign.co.nz/blog/wordpress-security-revisited-table-prefixes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Security</title>
		<link>http://www.aotearoawebdesign.co.nz/blog/wordpress-security/</link>
		<comments>http://www.aotearoawebdesign.co.nz/blog/wordpress-security/#comments</comments>
		<pubDate>Tue, 22 Sep 2009 04:38:01 +0000</pubDate>
		<dc:creator>Jason Koning</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.aotearoawebdesign.co.nz/?p=758</guid>
		<description><![CDATA[Quick micro-blog here, but useful and important information. Upload an .htaccess file to the wp-admin folder within your WordPress installation, then restrict access based on IP address, like so; AuthType Basic order deny,allow deny from all # whitelist home IP address allow from 00.000.000.00 # whitelist work IP address allow from 00.000.000.000 Replacing 00.000.000.000 with [...]]]></description>
		<wfw:commentRss>http://www.aotearoawebdesign.co.nz/blog/wordpress-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

