<?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: Basic Auth &#8211; Just Say No</title>
	<atom:link href="http://www.techper.net/2009/12/04/basic-auth-just-say-no/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techper.net/2009/12/04/basic-auth-just-say-no/</link>
	<description>About Technology in My Life</description>
	<lastBuildDate>Tue, 27 Jul 2010 08:01:33 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ram Pathak</title>
		<link>http://www.techper.net/2009/12/04/basic-auth-just-say-no/comment-page-1/#comment-37371</link>
		<dc:creator>Ram Pathak</dc:creator>
		<pubDate>Tue, 23 Feb 2010 20:46:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.techper.net/?p=304#comment-37371</guid>
		<description>It is good (better, easier, straight forward) as long as you use it within internal network (intranet environment), usually for admin related tool.</description>
		<content:encoded><![CDATA[<p>It is good (better, easier, straight forward) as long as you use it within internal network (intranet environment), usually for admin related tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Himmelman</title>
		<link>http://www.techper.net/2009/12/04/basic-auth-just-say-no/comment-page-1/#comment-37155</link>
		<dc:creator>John Himmelman</dc:creator>
		<pubDate>Tue, 16 Feb 2010 21:18:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.techper.net/?p=304#comment-37155</guid>
		<description>I&#039;d never use basic auth for a client/frontend login but its great for walling-out users from backend pages, or more specifically directories with analytic scripts and other sensitive material (over HTTPS though).</description>
		<content:encoded><![CDATA[<p>I&#8217;d never use basic auth for a client/frontend login but its great for walling-out users from backend pages, or more specifically directories with analytic scripts and other sensitive material (over HTTPS though).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lantrix</title>
		<link>http://www.techper.net/2009/12/04/basic-auth-just-say-no/comment-page-1/#comment-37030</link>
		<dc:creator>Lantrix</dc:creator>
		<pubDate>Tue, 09 Feb 2010 02:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.techper.net/?p=304#comment-37030</guid>
		<description>I&#039;m using basic auth in two instances.
In an internal private non-commercial network for squid authentication for proxy users. Change password is performed using a cgi running on the squid server.

I&#039;m also using it on an externally facing web server; but the caveat is that I make apache httpd enforce use of HTTPS.

It&#039;s useful for adhoc authentication for a small amount of users - as long as HTTPS is enforced for public networks.

That said, I would actually recommend other methods of authentication such as &lt;a href=&quot;http://www.h5l.org/&quot; rel=&quot;nofollow&quot;&gt;Kerberos&lt;/a&gt; or &lt;a href=&quot;http://www.openbsd.org/faq/pf/authpf.html&quot; rel=&quot;nofollow&quot;&gt;authpf&lt;/a&gt;; especially for external user authentication.</description>
		<content:encoded><![CDATA[<p>I&#8217;m using basic auth in two instances.<br />
In an internal private non-commercial network for squid authentication for proxy users. Change password is performed using a cgi running on the squid server.</p>
<p>I&#8217;m also using it on an externally facing web server; but the caveat is that I make apache httpd enforce use of HTTPS.</p>
<p>It&#8217;s useful for adhoc authentication for a small amount of users &#8211; as long as HTTPS is enforced for public networks.</p>
<p>That said, I would actually recommend other methods of authentication such as <a href="http://www.h5l.org/" rel="nofollow">Kerberos</a> or <a href="http://www.openbsd.org/faq/pf/authpf.html" rel="nofollow">authpf</a>; especially for external user authentication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: polesen</title>
		<link>http://www.techper.net/2009/12/04/basic-auth-just-say-no/comment-page-1/#comment-35619</link>
		<dc:creator>polesen</dc:creator>
		<pubDate>Fri, 11 Dec 2009 15:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.techper.net/?p=304#comment-35619</guid>
		<description>@johnstock: Yes, thats true.</description>
		<content:encoded><![CDATA[<p>@johnstock: Yes, thats true.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johnstok</title>
		<link>http://www.techper.net/2009/12/04/basic-auth-just-say-no/comment-page-1/#comment-35618</link>
		<dc:creator>johnstok</dc:creator>
		<pubDate>Fri, 11 Dec 2009 15:56:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.techper.net/?p=304#comment-35618</guid>
		<description>There are lots of HTTP clients besides browsers :-)

In many cases HTTPS + Basic auth can be sufficient for confidential, authenticated access to resources.

An obvious example being the twitter API.</description>
		<content:encoded><![CDATA[<p>There are lots of HTTP clients besides browsers <img src='http://www.techper.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>In many cases HTTPS + Basic auth can be sufficient for confidential, authenticated access to resources.</p>
<p>An obvious example being the twitter API.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: polesen</title>
		<link>http://www.techper.net/2009/12/04/basic-auth-just-say-no/comment-page-1/#comment-35459</link>
		<dc:creator>polesen</dc:creator>
		<pubDate>Sat, 05 Dec 2009 17:57:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.techper.net/?p=304#comment-35459</guid>
		<description>Nope - none of the problems I mention are solveable by the application itself emitting the headers.

It will still be the browser, that pops up the dialog and does all the handling itself. No way to control that.</description>
		<content:encoded><![CDATA[<p>Nope &#8211; none of the problems I mention are solveable by the application itself emitting the headers.</p>
<p>It will still be the browser, that pops up the dialog and does all the handling itself. No way to control that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Girouard</title>
		<link>http://www.techper.net/2009/12/04/basic-auth-just-say-no/comment-page-1/#comment-35458</link>
		<dc:creator>Mike Girouard</dc:creator>
		<pubDate>Sat, 05 Dec 2009 17:51:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.techper.net/?p=304#comment-35458</guid>
		<description>I agree... but I assume you&#039;re speaking of the de-facto server-supplied basic auth right?

I imagine that all of the problems you identify above are solved if you have a server-side app emitting the basic auth headers.

Cheers,
Mike G.</description>
		<content:encoded><![CDATA[<p>I agree&#8230; but I assume you&#8217;re speaking of the de-facto server-supplied basic auth right?</p>
<p>I imagine that all of the problems you identify above are solved if you have a server-side app emitting the basic auth headers.</p>
<p>Cheers,<br />
Mike G.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
