<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Yabfog &#187; security</title>
	<atom:link href="http://yabfog.com/blog/tag/security/feed" rel="self" type="application/rss+xml" />
	<link>http://yabfog.com/blog</link>
	<description>Yet another blog full of gas</description>
	<lastBuildDate>Tue, 13 Dec 2011 02:45:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
<cloud domain='yabfog.com' port='80' path='/blog/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>Twitbin Fixes Security Flaw</title>
		<link>http://yabfog.com/blog/2007/10/26/twitbin-fixes-security-flaw</link>
		<comments>http://yabfog.com/blog/2007/10/26/twitbin-fixes-security-flaw#comments</comments>
		<pubDate>Fri, 26 Oct 2007 21:25:21 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[uncategorized]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://yabfog.com/blog/2007/10/26/twitbin-fixes-security-flaw</guid>
		<description><![CDATA[Brian Breslin, of Twitbin, left a comment saying that Twitbin fixed the security flaw I previously pointed out. Cooool!]]></description>
			<content:encoded><![CDATA[<p>Brian Breslin, of <a href="http://twitbin.com">Twitbin</a>, left a <a href="http://yabfog.com/blog/2007/10/23/twitbin-fails-basic-password-security#comment-41506">comment saying that Twitbin fixed the security flaw I previously pointed out</a>. Cooool! <img src='http://yabfog.com/blog/wp-includes/images/smilies/icon_cool.gif' alt=':cool:' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://yabfog.com/blog/2007/10/26/twitbin-fixes-security-flaw/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
	</item>
		<item>
		<title>Twitbin Fails Basic Password Security</title>
		<link>http://yabfog.com/blog/2007/10/23/twitbin-fails-basic-password-security</link>
		<comments>http://yabfog.com/blog/2007/10/23/twitbin-fails-basic-password-security#comments</comments>
		<pubDate>Tue, 23 Oct 2007 14:35:34 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[uncategorized]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://yabfog.com/wp/2007/10/23/twitbin-fails-basic-password-security</guid>
		<description><![CDATA[UPDATE: FIXED. See the comments below. A couple weeks ago, I installed twitbin, a Firefox extension that loads twitter in a sidebar. But, I just happened to be checking my browser cookies, and I noticed that my twitter username and PASSWORD were stored in my browser cookies in plaintext! This is not even a session [...]]]></description>
			<content:encoded><![CDATA[<p><strong>UPDATE: FIXED. See the comments below.</strong></p>
<p>A couple weeks ago, I installed <a href="http://www.twitbin.com">twitbin</a>, a Firefox extension that loads <a href="http://twitter.com">twitter</a> in a sidebar. But, I just happened to be checking my browser cookies, and I noticed that my twitter username and <strong>PASSWORD</strong> were stored in my browser cookies in <strong><em>plaintext</em></strong>! This is not even a session cookie -- it is persistent, with a one-year expiration.</p>
<p>Are you kidding me?! Twitbin -- uninstalled.</p>
<p>"[I]t is never appropriate for cookies to contain plaintext user names and passwords." [<a href="http://www.w3.org/Security/Faq/wwwsf2.html#CLT-Q10">The World Wide Web Security FAQ</a>]</p>
]]></content:encoded>
			<wfw:commentRss>http://yabfog.com/blog/2007/10/23/twitbin-fails-basic-password-security/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
	
	</item>
		<item>
		<title>WordPress and JavaScript Hijacking</title>
		<link>http://yabfog.com/blog/2007/04/13/wordpress-and-javascript-hijacking</link>
		<comments>http://yabfog.com/blog/2007/04/13/wordpress-and-javascript-hijacking#comments</comments>
		<pubDate>Fri, 13 Apr 2007 15:56:25 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[uncategorized]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://yabfog.com/blog/2007/04/13/wordpress-and-javascript-hijacking/</guid>
		<description><![CDATA[I read this paper that Bruce Schneier linked to regarding JavaScript hijacking. Seems to me that WordPress plugin developers who piggyback on WordPress's builtin security features shouldn't have anything to worry about. Judging from what little buzz there was, I think that's probably true, but I'm interested in others' thoughts.]]></description>
			<content:encoded><![CDATA[<p>I read this <a href="http://www.fortifysoftware.com/servlet/downloads/public/JavaScript_Hijacking.pdf">paper</a> that Bruce Schneier linked to regarding <a href="http://www.schneier.com/blog/archives/2007/04/javascript_hija.html">JavaScript hijacking</a>. Seems to me that WordPress plugin developers who piggyback on WordPress's builtin <a href="http://codex.wordpress.org/Hardening_WordPress">security</a> <a href="http://codex.wordpress.org/Plugin_API/Action_Reference#Advanced_Actions">features</a> shouldn't have anything to worry about.</p>
<p>Judging from what <a href="http://technorati.com/search/www.schneier.com%2Fblog%2Farchives%2F2007%2F04%2Fjavascript_hija.html?sub=toolsearch">little</a> <a href="http://technorati.com/search/www.fortifysoftware.com%2Fnews-events%2Freleases%2F2007%2F2007-04-02.jsp?sub=toolsearch">buzz</a> there was, I think that's probably true, but I'm interested in <a href="http://yabfog.com/blog/2007/04/13/wordpress-and-javascript-hijacking/#respond" rel="nofollow">others' thoughts</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://yabfog.com/blog/2007/04/13/wordpress-and-javascript-hijacking/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
	</item>
		<item>
		<title>Yikes! WordPress Hacked!</title>
		<link>http://yabfog.com/blog/2007/03/02/yikes-wordpress-hacked</link>
		<comments>http://yabfog.com/blog/2007/03/02/yikes-wordpress-hacked#comments</comments>
		<pubDate>Fri, 02 Mar 2007 22:59:01 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[uncategorized]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://yabfog.com/wp/2007/03/02/yikes-wordpress-hacked/</guid>
		<description><![CDATA[The WordPress crew have announced that the WordPress 2.1.1 download got cracked by an unnamed attacker who injected some code that would allow remote code execution. I'm glad I haven't upgraded!]]></description>
			<content:encoded><![CDATA[<p>The WordPress crew have <a href="http://wordpress.org/development/2007/03/upgrade-212/#more-199">announced that the WordPress 2.1.1 download got cracked</a> by an unnamed attacker who injected some code that would allow remote code execution. I'm glad I haven't upgraded!</p>
]]></content:encoded>
			<wfw:commentRss>http://yabfog.com/blog/2007/03/02/yikes-wordpress-hacked/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
	</item>
		<item>
		<title>Scheduled Tasks - Running Tasks Without A Password</title>
		<link>http://yabfog.com/blog/2005/10/06/scheduled_tasks_running_tasks_without_a_</link>
		<comments>http://yabfog.com/blog/2005/10/06/scheduled_tasks_running_tasks_without_a_#comments</comments>
		<pubDate>Thu, 06 Oct 2005 12:13:32 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[uncategorized]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[For XP Pro: Go to Start/Administrative Tools/Local Security Policy/Security Settings/Local Policies/Security Options Accounts: Limit local account use of blank passwords to console logon only. This is enabled by default, disable it. For XP Home: (Keith Miller) Go to Start/Run/Regedit and navigate to this key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa Value name: limitblankpassworduse, Type: REG_DWORD, Data: 0 (disabled) 1 (enabled) [...]]]></description>
			<content:encoded><![CDATA[<p>For XP Pro:  Go to Start/Administrative Tools/Local Security Policy/Security Settings/Local Policies/Security Options<br />
Accounts: Limit local account use of blank passwords to console logon only. This is enabled by default, disable it.</p>
<p>For XP Home: (Keith Miller) Go to Start/Run/Regedit and navigate to this key:<br />
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa</p>
<p>Value name: limitblankpassworduse, Type: REG_DWORD, Data: 0 (disabled) 1 (enabled)</p>
<p>For Home: Run Scheduled Task without a Password (Line 67)<br />
<a href="http://www.kellys-korner-xp.com/xp_tweaks.htm">http://www.kellys-korner-xp.com/xp_tweaks.htm</a></p>
<p><em>Source:</em><br />
<a href="http://www.softwaretipsandtricks.com/windowsxp/articles/573/1/Windows-XP-FAQ-S">Windows XP FAQ</a></p>
]]></content:encoded>
			<wfw:commentRss>http://yabfog.com/blog/2005/10/06/scheduled_tasks_running_tasks_without_a_/feed</wfw:commentRss>
		<slash:comments>7</slash:comments>
	
	</item>
	</channel>
</rss>

