<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: IP address authentication considered harmful</title>
	<atom:link href="http://blogs.semantico.com/discovery-blog/2009/06/ip-address-authentication-considered-harmful/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.semantico.com/discovery-blog/2009/06/ip-address-authentication-considered-harmful/</link>
	<description>Semantico looks at online publishing</description>
	<lastBuildDate>Thu, 11 Mar 2010 14:52:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Richard Padley</title>
		<link>http://blogs.semantico.com/discovery-blog/2009/06/ip-address-authentication-considered-harmful/comment-page-1/#comment-24626</link>
		<dc:creator>Richard Padley</dc:creator>
		<pubDate>Mon, 22 Jun 2009 11:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.semantico.com/discovery-blog/?p=273#comment-24626</guid>
		<description>Hi Nicole,

There are a number of use cases for authenticated RSS from publishers. One common one for us is to deliver search results as an RSS feed - this allows users to store canned searches in their feed readers and check back regularly to see when new content is added to the system matching their search criteria.

For a paid-to-access abstracts service, like CAB Direct for example, the search results must be protected, and so therefore any RSS derived from it must be also.

The fact the RSS can be used for delivering rich services such as search as well as content syndication means that robust authentication is a key requirement for many publishers.</description>
		<content:encoded><![CDATA[<p>Hi Nicole,</p>
<p>There are a number of use cases for authenticated RSS from publishers. One common one for us is to deliver search results as an RSS feed &#8211; this allows users to store canned searches in their feed readers and check back regularly to see when new content is added to the system matching their search criteria.</p>
<p>For a paid-to-access abstracts service, like CAB Direct for example, the search results must be protected, and so therefore any RSS derived from it must be also.</p>
<p>The fact the RSS can be used for delivering rich services such as search as well as content syndication means that robust authentication is a key requirement for many publishers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicole Harris</title>
		<link>http://blogs.semantico.com/discovery-blog/2009/06/ip-address-authentication-considered-harmful/comment-page-1/#comment-24424</link>
		<dc:creator>Nicole Harris</dc:creator>
		<pubDate>Tue, 16 Jun 2009 17:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.semantico.com/discovery-blog/?p=273#comment-24424</guid>
		<description>Interested as to why you would want authenticated access to an RSS feed?  Surely such feeds should be openly accessible, with authentication only being required at the last possible moment to access full content.  I can see the argument for authenticated RSS feeds from, say, banks and credit card companies, but not sure of a publishing use case?</description>
		<content:encoded><![CDATA[<p>Interested as to why you would want authenticated access to an RSS feed?  Surely such feeds should be openly accessible, with authentication only being required at the last possible moment to access full content.  I can see the argument for authenticated RSS feeds from, say, banks and credit card companies, but not sure of a publishing use case?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Padley</title>
		<link>http://blogs.semantico.com/discovery-blog/2009/06/ip-address-authentication-considered-harmful/comment-page-1/#comment-24263</link>
		<dc:creator>Richard Padley</dc:creator>
		<pubDate>Thu, 11 Jun 2009 09:01:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.semantico.com/discovery-blog/?p=273#comment-24263</guid>
		<description>Hi Dom,

Very good point re: the &lt;code&gt;X-Forwarded-For&lt;/code&gt; header. Since there are no standards for this header, we&#039;ve seen no end of cruft end up in there from ill behaved proxy servers.</description>
		<content:encoded><![CDATA[<p>Hi Dom,</p>
<p>Very good point re: the <code>X-Forwarded-For</code> header. Since there are no standards for this header, we&#8217;ve seen no end of cruft end up in there from ill behaved proxy servers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Hellman</title>
		<link>http://blogs.semantico.com/discovery-blog/2009/06/ip-address-authentication-considered-harmful/comment-page-1/#comment-24256</link>
		<dc:creator>Eric Hellman</dc:creator>
		<pubDate>Wed, 10 Jun 2009 20:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.semantico.com/discovery-blog/?p=273#comment-24256</guid>
		<description>Yes, harmful. Nonetheless, the reality is that IP address authentication, patched up with rewriting proxy-servers, is less harmful than any of the alternatives.</description>
		<content:encoded><![CDATA[<p>Yes, harmful. Nonetheless, the reality is that IP address authentication, patched up with rewriting proxy-servers, is less harmful than any of the alternatives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dominic Mitchell</title>
		<link>http://blogs.semantico.com/discovery-blog/2009/06/ip-address-authentication-considered-harmful/comment-page-1/#comment-24249</link>
		<dc:creator>Dominic Mitchell</dc:creator>
		<pubDate>Wed, 10 Jun 2009 10:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.semantico.com/discovery-blog/?p=273#comment-24249</guid>
		<description>Don&#039;t forget the awful workarounds that get put in to place because of the desire for IP Authentication: The &lt;code&gt;X-Forwarded-For&lt;/code&gt; header.

If you can&#039;t distinguish based on the IP address of the institutional proxy, there&#039;s a desire to use the IP address &lt;em&gt;behind&lt;/em&gt; the proxy.  But this method is wide-open to abuse.  There&#039;s no way to stop anyone supply their own &lt;code&gt;X-Forwarded-For&lt;/code&gt; header with your IP address.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t forget the awful workarounds that get put in to place because of the desire for IP Authentication: The <code>X-Forwarded-For</code> header.</p>
<p>If you can&#8217;t distinguish based on the IP address of the institutional proxy, there&#8217;s a desire to use the IP address <em>behind</em> the proxy.  But this method is wide-open to abuse.  There&#8217;s no way to stop anyone supply their own <code>X-Forwarded-For</code> header with your IP address.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
