<?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>Southern Bread &#187; security</title>
	<atom:link href="http://www.southernbread.org/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.southernbread.org</link>
	<description>Southern History, American Freedom, Christian Liberty</description>
	<lastBuildDate>Sat, 04 Feb 2012 21:12:04 +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>Safe Online Holiday Shopping Tips</title>
		<link>http://www.southernbread.org/safe-online-holiday-shopping-tips/</link>
		<comments>http://www.southernbread.org/safe-online-holiday-shopping-tips/#comments</comments>
		<pubDate>Mon, 30 Nov 2009 15:46:34 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[Misc]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://www.southernbread.org/?p=2384</guid>
		<description><![CDATA[I&#8217;m a network administrator by trade so I deal with online security issues pretty much daily. After reading Brian Krebs recent post on tips for safe online holiday shopping I figured I&#8217;d tweak his list a bit and post it here. I didn&#8217;t agree on a couple of points, but most of his tips are [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m a network administrator by trade so I deal with online security issues pretty much daily.  After reading Brian Krebs <a href="http://voices.washingtonpost.com/securityfix/2009/11/eight_tips_for_safe_online_sho.html?wprss=securityfix">recent post</a> on tips for safe online holiday shopping I figured I&#8217;d tweak his list a bit and post it here.  I didn&#8217;t agree on a couple of points, but most of his tips are good ones.  So here goes.</p>
<p>1.        <strong>Shop with a credit card, not a debit card</strong>.  The procedures for dealing with fraudulent credit card activities are much more entrenched(and easier to deal with) since credit cards have been around for years.  Debit cards are still a relatively new thing, and since they are tied to your actual checking account can be a mess to sort out if checks have bounced or payments have been missed.  Credit cards still offer a layer of protection that debit cards don’t.</p>
<p>2.       <strong>Use Firefox</strong>.  This could have been number one on the list.  I suggest all home users use Firefox at all times, instead of Internet Explorer.  And, with online shopping, it’s even more important.  The fact is, Internet Explorer remains the single biggest target for viruses and spyware in existence.  To get Firefox just go to <a href="http://www.mozilla.org" target="_blank">http://www.mozilla.org</a> and download it.</p>
<p>3.<strong> Look for the padlock symbol</strong>.  The presence of this symbol:   in your browser’s address  bar means that the purchase you are about to make is encrypted as it travels across the internet.</p>
<p>4.       <strong>Avoid prices that are way out of line</strong>.  What I mean is, if the price seems to be way higher or lower than market price then move on.  What you will find is that most of the time these low prices are accompanied by ridiculously high shipping rates to compensate.  Extremely low prices are a sign that all is not right with this vendor.</p>
<p>5. <strong> Don’t rush</strong>.  Take your time when making a purchase from an online vendor that you’ve never dealt with before.  Step through each page and read all the fine print during checkout.</p>
<p>6.       <strong>Use different passwords</strong>.  If you are making a purchase from a new vendor and they require “registration” or that you set up an account with them, don’t use a common password.  Use a different password for each account.  I know it’s a pain, but you can write them down and keep them in a desk drawer or something to make it easier.  Having the same password on all of your website accounts is a major security risk for you.</p>
<p>7.       <strong>Use one-time use e-credit cards if you can</strong>.  I use these all the time through paypal.  Basically, you can generate credit card numbers that are tied to your paypal account.  These numbers are only valid for one transaction.  That way, if someone hacks your account at that particular site all they will get is a useless card number.  Paypal offers these numbers as do many banks.</p>
<p>8.       <strong>Check seller ratings</strong>.  If you are dealing with a vendor that you’ve never heard of before, consider looking them up on a rating service such as <a href="http://www.bizrate.com">bizrate.com</a> or <a href="http://www.pricegrabber.com">pricegrabber.com</a>.</p>
<p>Hope these help.  Shop safe and keep your radar up.  If something seems fishy just close your browser and don’t go back to the site.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.southernbread.org/safe-online-holiday-shopping-tips/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SQL Injection Defense &#8211; Part I (Authentication)</title>
		<link>http://www.southernbread.org/sql-injection-defense-part-i-authentication/</link>
		<comments>http://www.southernbread.org/sql-injection-defense-part-i-authentication/#comments</comments>
		<pubDate>Wed, 27 Sep 2006 11:31:00 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[sql injection]]></category>

		<guid isPermaLink="false">http://www.southernbread.org/programming/1149998399.html</guid>
		<description><![CDATA[I want to do a couple of posts on SQL injection attack prevention. I am going to show some of the techniques I use to ward them off. For example, we use a three pronged approach at the authentication point: variable binding, row counting, and syntax detection. When a username and password are entered on [...]]]></description>
			<content:encoded><![CDATA[<p>I want to do a couple of posts on SQL injection attack prevention.  I<br />
am going to show some of the techniques I use to ward them off.  For example,<br />
we use a three pronged approach at<br />
the authentication point:  variable binding, row counting, and syntax<br />
detection.  When a username and password are entered on the login form<br />
we check to make sure that there is nothing obviously wrong with the<br />
input, like password being of acceptable length and such.  The next<br />
thing we do is check to make sure there is no known SQL syntax within<br />
the username or password.  For example, if someone inputs a password<br />
like this:</p>
<p><pre><code>
&amp;#8217; OR 1=1
</code></pre></p>
<p>it will get rejected at this step.  All of the SQL keywords are<br />
stored in big lookup table and checked against.  The next step then is<br />
to bind the variables instead of passing them in as plain strings.  This<br />
is a crucial step to avoid SQL injection.  So instead of:</p>
<p><pre><code>
$sql=&quot;SELECT * FROM users WHERE username=&quot;$username&quot; AND 
password=&quot;$password&quot; LIMIT 1
</code></pre></p>
<p>we use:</p>
<p><pre><code>
$sql=&quot;SELECT * FROM users WHERE username=? AND password=? LIMIT 1
$sth=$dbh-&gt;prepare($sql);
$sth-&gt;execute($username,$password);
</code></pre></p>
<p>The final thing we do is check the row count of the result set.  Even<br />
though we used &#8220;LIMIT 1&#8243;, if there is an injection going on then we must<br />
assume that it has been changed.  Be sure and check that you have a row<br />
count that is sane for the operation you are performing.  If you are<br />
logging someone in then you should return an error if the result count<br />
is 0 or greater than 1, like this:</p>
<p><pre><code>
die unless($sth-&gt;rows() eq 1);
</code></pre></p>
<p>Next time I&#8217;ll focus on SQL injection that happens beyond the front<br />
gate.  Sometimes you can&#8217;t be so strict on row counts and syntax checks<br />
once a user is inside.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.southernbread.org/sql-injection-defense-part-i-authentication/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Personal Warning</title>
		<link>http://www.southernbread.org/a-personal-warning/</link>
		<comments>http://www.southernbread.org/a-personal-warning/#comments</comments>
		<pubDate>Thu, 04 May 2006 08:40:00 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://www.southernbread.org/dave/1146667222.html</guid>
		<description><![CDATA[I have been seeing a lot lately about myspace.com. You may have heard of it. It&#8217;s a social networking site where people can chat, share photos, and communicate with other myspace users easily. It has also become a major hangout for child predators. It&#8217;s become so bad that it has caused Microsoft to hire a [...]]]></description>
			<content:encoded><![CDATA[<p>I have been seeing a lot lately about <a href="http://www.myspace.com">myspace.com</a>.<br />
You may have heard of it.  It&#8217;s a social networking site where people<br />
can chat, share photos, and communicate with other myspace users<br />
easily.  It has also become a major hangout for child predators.  It&#8217;s<br />
become so bad that it has caused Microsoft to hire a full time Chief<br />
Security Officer for myspace.com who was formerly a U.S. Prosecuter<br />
chasing down child predators.  <b>Please be sure to scrutinize your<br />
children&#8217;s online activities.  Especially if they use these social<br />
networking sites like myspace.com.</b>  It&#8217;s not just viruses any<br />
more.  The threats to our kids online are real.  Here is a recent<br />
article by InformationWeek that goes into some detail about myspace and<br />
some things to watch for:<br/><br />
<br/><br />
<a<br />
 href="http://www.informationweek.com/shared/printableArticle.jhtml?articleID=187001704">http://www.informationweek.com/shared/printableArticle.jhtml?articleID=187001704</a><br/><br />
<br/><br />
The most important thing is that your kids know that talking to<br />
strangers on the internet is just as bad as talking to strangers on the<br />
street.  You never know what information they could glean about you<br />
from an offhand comment.  The other thing is that kids should <b>NEVER</b><br />
give out any personal information on the internet.  Sites like myspace<br />
make it waaay to easy to give out personal info and most kids don&#8217;t<br />
have the forethought to see that it could be a bad idea to give out<br />
there cell phone number to their myspace &#8220;friends&#8221; or something like<br />
that.  If your kid has a computer in their room and their own cell<br />
phone, it&#8217;s time to check it out and see <i>exactly</i> what they are<br />
doing online.<br/></p>
]]></content:encoded>
			<wfw:commentRss>http://www.southernbread.org/a-personal-warning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

