<?xml version="1.0" encoding="UTF-8"?><feed
  xmlns="http://www.w3.org/2005/Atom"
  xmlns:thr="http://purl.org/syndication/thread/1.0"
  xml:lang="en-US"
  xml:base="http://www.frameloss.org/wp-atom.php"
   >
	<title type="text"></title>
	<subtitle type="text"></subtitle>

	<updated>2013-10-17T01:34:17Z</updated>

	<link rel="alternate" type="text/html" href="http://www.frameloss.org" />
	<id>http://www.frameloss.org/feed/atom/</id>
	<link rel="self" type="application/atom+xml" href="http://www.frameloss.org/feed/atom/" />

	<generator uri="http://wordpress.org/" version="3.7.1">WordPress</generator>
	<entry>
		<author>
			<name>tag</name>
					</author>
		<title type="html"><![CDATA[Moving off of gmail? What about all those filter rules?]]></title>
		<link rel="alternate" type="text/html" href="http://www.frameloss.org/2013/10/16/moving-off-of-gmail-what-about-all-those-filter-rules/" />
		<id>http://www.frameloss.org/?p=798</id>
		<updated>2013-10-17T01:34:17Z</updated>
		<published>2013-10-17T01:32:30Z</published>
		<category scheme="http://www.frameloss.org" term="Security" />		<summary type="html"><![CDATA[So, for one reason or another, I decided that I was going to move away from gmail.  It&#8217;s easy to underestimate the massive pain that is running a mail server, especially if you expect anti-spam, ant-virus, and the thousand (seemingly so at least) other features that are offered for free from most web mail providers. <a href='http://www.frameloss.org/2013/10/16/moving-off-of-gmail-what-about-all-those-filter-rules/' class='excerpt-more'>[...]</a>]]></summary>
			<link rel="replies" type="text/html" href="http://www.frameloss.org/2013/10/16/moving-off-of-gmail-what-about-all-those-filter-rules/#comments" thr:count="1"/>
		<link rel="replies" type="application/atom+xml" href="http://www.frameloss.org/2013/10/16/moving-off-of-gmail-what-about-all-those-filter-rules/feed/atom/" thr:count="1"/>
		<thr:total>1</thr:total>
	</entry>
		<entry>
		<author>
			<name>tag</name>
					</author>
		<title type="html"><![CDATA[Making Java (slightly) safer on Windows]]></title>
		<link rel="alternate" type="text/html" href="http://www.frameloss.org/2013/07/10/making-java-slightly-safer-on-windows/" />
		<id>http://www.frameloss.org/?p=764</id>
		<updated>2013-07-10T19:54:09Z</updated>
		<published>2013-07-10T19:54:09Z</published>
		<category scheme="http://www.frameloss.org" term="Security" /><category scheme="http://www.frameloss.org" term="Web Security" />		<summary type="html"><![CDATA[Here&#8217;s a suggestion that can make it a little safer to run the Java plugin in your web browser on Windows (Vista, Win 7, and Win 8&#8211;but not XP.)  This doesn&#8217;t stop exploits, and is probably not entirely effective, but it can stop some bad things from happening.  Don&#8217;t be fooled into feeling safe by <a href='http://www.frameloss.org/2013/07/10/making-java-slightly-safer-on-windows/' class='excerpt-more'>[...]</a>]]></summary>
			<link rel="replies" type="text/html" href="http://www.frameloss.org/2013/07/10/making-java-slightly-safer-on-windows/#comments" thr:count="0"/>
		<link rel="replies" type="application/atom+xml" href="http://www.frameloss.org/2013/07/10/making-java-slightly-safer-on-windows/feed/atom/" thr:count="0"/>
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>tag</name>
					</author>
		<title type="html"><![CDATA[Even easier brute-force login protection for wordpress]]></title>
		<link rel="alternate" type="text/html" href="http://www.frameloss.org/2013/04/26/even-easier-brute-force-login-protection-for-wordpress/" />
		<id>http://www.frameloss.org/?p=783</id>
		<updated>2013-04-26T22:25:59Z</updated>
		<published>2013-04-26T22:06:44Z</published>
		<category scheme="http://www.frameloss.org" term="Security" /><category scheme="http://www.frameloss.org" term="Web Security" />		<summary type="html"><![CDATA[Here&#8217;s another *easy* way to help with those pesky wordpress brute-force logins we have been hearing about.  Most automated attacks make a lot of assumptions.  Like where your blog&#8217;s login page is located, and what information is needed to login via that page.  It&#8217;s really easy to take those assumptions and make them wrong.  The <a href='http://www.frameloss.org/2013/04/26/even-easier-brute-force-login-protection-for-wordpress/' class='excerpt-more'>[...]</a>]]></summary>
			<link rel="replies" type="text/html" href="http://www.frameloss.org/2013/04/26/even-easier-brute-force-login-protection-for-wordpress/#comments" thr:count="0"/>
		<link rel="replies" type="application/atom+xml" href="http://www.frameloss.org/2013/04/26/even-easier-brute-force-login-protection-for-wordpress/feed/atom/" thr:count="0"/>
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>tag</name>
					</author>
		<title type="html"><![CDATA[Kerberos ticket renewal on MacOS Mountain Lion]]></title>
		<link rel="alternate" type="text/html" href="http://www.frameloss.org/2013/01/30/macos-kerberos-tgt/" />
		<id>http://www.frameloss.org/?p=775</id>
		<updated>2013-01-30T21:17:50Z</updated>
		<published>2013-01-30T20:55:14Z</published>
		<category scheme="http://www.frameloss.org" term="Apple" /><category scheme="http://www.frameloss.org" term="Network Security" /><category scheme="http://www.frameloss.org" term="Security" />		<summary type="html"><![CDATA[The active directory integration in Mountain Lion is getting pretty good, certainly much better than the early 10.7 days.  Several applications integrate quite well, offering kerberos single sign on, such as Safari, and the Microsoft Office apps.  One thing I do not like about kerberos on MacOS is that when my TGT expired it would <a href='http://www.frameloss.org/2013/01/30/macos-kerberos-tgt/' class='excerpt-more'>[...]</a>]]></summary>
			<link rel="replies" type="text/html" href="http://www.frameloss.org/2013/01/30/macos-kerberos-tgt/#comments" thr:count="0"/>
		<link rel="replies" type="application/atom+xml" href="http://www.frameloss.org/2013/01/30/macos-kerberos-tgt/feed/atom/" thr:count="0"/>
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>tag</name>
					</author>
		<title type="html"><![CDATA[IPv6 on Comcast using OpenWRT]]></title>
		<link rel="alternate" type="text/html" href="http://www.frameloss.org/2013/01/12/ipv6-on-comcast-using-openwrt/" />
		<id>http://www.frameloss.org/?p=752</id>
		<updated>2013-01-12T22:40:27Z</updated>
		<published>2013-01-12T22:34:58Z</published>
		<category scheme="http://www.frameloss.org" term="Miscellaneous" />		<summary type="html"><![CDATA[I bought a new wireless router (TP-Link N750 TL-WDR4300) that had fantastic hardware specs. It was to replace what I had been using, an Airport extreme, that was having problems dealing with the number of DHCP leases on my network. I also didn&#8217;t like the lack of flexibility in firewalling, DHCP options, and on and <a href='http://www.frameloss.org/2013/01/12/ipv6-on-comcast-using-openwrt/' class='excerpt-more'>[...]</a>]]></summary>
			<link rel="replies" type="text/html" href="http://www.frameloss.org/2013/01/12/ipv6-on-comcast-using-openwrt/#comments" thr:count="0"/>
		<link rel="replies" type="application/atom+xml" href="http://www.frameloss.org/2013/01/12/ipv6-on-comcast-using-openwrt/feed/atom/" thr:count="0"/>
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>tag</name>
					</author>
		<title type="html"><![CDATA[Always &#8220;hover&#8221; before you click!?  Wrong.]]></title>
		<link rel="alternate" type="text/html" href="http://www.frameloss.org/2012/10/28/hover-fail/" />
		<id>http://www.frameloss.org/?p=724</id>
		<updated>2012-10-29T20:43:06Z</updated>
		<published>2012-10-29T00:53:31Z</published>
		<category scheme="http://www.frameloss.org" term="Wait, that was wrong." />		<summary type="html"><![CDATA[RETRACTION: So, sometimes I am wrong. This attack does work, but it&#8217;s irrelevant, and here&#8217;s why: if someone has control of the DOM the game is already over, there’s nothing the browser can do for you in that case. It doesn’t really matter that the hover-status can be spoofed at that point. I&#8217;ll leave the <a href='http://www.frameloss.org/2012/10/28/hover-fail/' class='excerpt-more'>[...]</a>]]></summary>
			<link rel="replies" type="text/html" href="http://www.frameloss.org/2012/10/28/hover-fail/#comments" thr:count="46"/>
		<link rel="replies" type="application/atom+xml" href="http://www.frameloss.org/2012/10/28/hover-fail/feed/atom/" thr:count="46"/>
		<thr:total>46</thr:total>
	</entry>
		<entry>
		<author>
			<name>tag</name>
					</author>
		<title type="html"><![CDATA[Yet another neat $PS1 prompt for bash]]></title>
		<link rel="alternate" type="text/html" href="http://www.frameloss.org/2012/10/26/yet-another-neat-ps1-prompt-for-bash/" />
		<id>http://www.frameloss.org/?p=711</id>
		<updated>2012-10-27T05:58:20Z</updated>
		<published>2012-10-27T04:11:53Z</published>
		<category scheme="http://www.frameloss.org" term="Miscellaneous" />		<summary type="html"><![CDATA[(With  google returning more than a million hits for the search &#8220;bash PS1&#8243;, it may be a little presumptive that I have anything to add to the conversation, but this was an interesting exercise for me, so I&#8217;ll share it anyways.  Besides this may actually be my most nitpicky *nix nerd post yet.) Here&#8217;s my <a href='http://www.frameloss.org/2012/10/26/yet-another-neat-ps1-prompt-for-bash/' class='excerpt-more'>[...]</a>]]></summary>
			<link rel="replies" type="text/html" href="http://www.frameloss.org/2012/10/26/yet-another-neat-ps1-prompt-for-bash/#comments" thr:count="1"/>
		<link rel="replies" type="application/atom+xml" href="http://www.frameloss.org/2012/10/26/yet-another-neat-ps1-prompt-for-bash/feed/atom/" thr:count="1"/>
		<thr:total>1</thr:total>
	</entry>
		<entry>
		<author>
			<name>tag</name>
					</author>
		<title type="html"><![CDATA[Stored Cross-site Flashing?]]></title>
		<link rel="alternate" type="text/html" href="http://www.frameloss.org/2012/10/21/stored-cross-site-flashing/" />
		<id>http://www.frameloss.org/?p=703</id>
		<updated>2012-10-21T18:38:25Z</updated>
		<published>2012-10-21T18:36:33Z</published>
		<category scheme="http://www.frameloss.org" term="Security" /><category scheme="http://www.frameloss.org" term="Web Security" />		<summary type="html"><![CDATA[The title for this post posed somewhat of a conundrum for me. That&#8217;s because I think technically, cross-site flashing is more about attacking a flash applet that already lives on a website.  But what if you are allowed to add one to said website?  Is attacking the document object model through an uploaded flash applet <a href='http://www.frameloss.org/2012/10/21/stored-cross-site-flashing/' class='excerpt-more'>[...]</a>]]></summary>
			<link rel="replies" type="text/html" href="http://www.frameloss.org/2012/10/21/stored-cross-site-flashing/#comments" thr:count="0"/>
		<link rel="replies" type="application/atom+xml" href="http://www.frameloss.org/2012/10/21/stored-cross-site-flashing/feed/atom/" thr:count="0"/>
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>tag</name>
					</author>
		<title type="html"><![CDATA[Installing WebGoat.net using Apache on Ubuntu]]></title>
		<link rel="alternate" type="text/html" href="http://www.frameloss.org/2012/05/23/installing-webgoat-net-using-apache-on-ubuntu/" />
		<id>http://www.frameloss.org/?p=671</id>
		<updated>2012-05-23T19:45:59Z</updated>
		<published>2012-05-23T17:50:39Z</published>
		<category scheme="http://www.frameloss.org" term="Security" /><category scheme="http://www.frameloss.org" term="Web Security" />		<summary type="html"><![CDATA[At the recent OWASP Snowfroc conference in Denver, Jerry Hoff presented a new OWASP project called WebGoat.net, a .NET application designed for training classes.  It is designed to run on Linux using the Apache web server.  You can probably easily also run it on nginx or even IIS on Windows if you were so inclined.  I <a href='http://www.frameloss.org/2012/05/23/installing-webgoat-net-using-apache-on-ubuntu/' class='excerpt-more'>[...]</a>]]></summary>
			<link rel="replies" type="text/html" href="http://www.frameloss.org/2012/05/23/installing-webgoat-net-using-apache-on-ubuntu/#comments" thr:count="0"/>
		<link rel="replies" type="application/atom+xml" href="http://www.frameloss.org/2012/05/23/installing-webgoat-net-using-apache-on-ubuntu/feed/atom/" thr:count="0"/>
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>tag</name>
					</author>
		<title type="html"><![CDATA[Making WordPress Stable on EC2-Micro]]></title>
		<link rel="alternate" type="text/html" href="http://www.frameloss.org/2011/11/04/making-wordpress-stable-on-ec2-micro/" />
		<id>http://www.frameloss.org/?p=590</id>
		<updated>2011-11-04T22:10:45Z</updated>
		<published>2011-11-04T22:10:45Z</published>
		<category scheme="http://www.frameloss.org" term="Miscellaneous" />		<summary type="html"><![CDATA[EC2 Micro Instance Limitations EC2 offers a lot of advantages over many web site hosting options.  I am a bit of a control freak and like having full control over my web server.  This has advantages and disadvantages of course, meaning more work but more flexibility.  Running a WordPress blog on a micro instance can <a href='http://www.frameloss.org/2011/11/04/making-wordpress-stable-on-ec2-micro/' class='excerpt-more'>[...]</a>]]></summary>
			<link rel="replies" type="text/html" href="http://www.frameloss.org/2011/11/04/making-wordpress-stable-on-ec2-micro/#comments" thr:count="0"/>
		<link rel="replies" type="application/atom+xml" href="http://www.frameloss.org/2011/11/04/making-wordpress-stable-on-ec2-micro/feed/atom/" thr:count="0"/>
		<thr:total>0</thr:total>
	</entry>
	</feed>
<!-- CDN Linker <https://github.com/wmark/CDN-Linker/tags> active -->