<?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>Spread OpenID &#187; pape</title>
	<atom:link href="http://spreadopenid.org/tag/pape/feed/" rel="self" type="application/rss+xml" />
	<link>http://spreadopenid.org</link>
	<description></description>
	<lastBuildDate>Fri, 29 Jan 2010 02:55:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
			<item>
		<title>More Security for OpenID</title>
		<link>http://spreadopenid.org/2009/01/more-security-for-openid/</link>
		<comments>http://spreadopenid.org/2009/01/more-security-for-openid/#comments</comments>
		<pubDate>Wed, 07 Jan 2009 21:51:37 +0000</pubDate>
		<dc:creator>Carsten Pötter</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[nist]]></category>
		<category><![CDATA[pape]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[specification]]></category>

		<guid isPermaLink="false">http://spreadopenid.org/2009/01/07/more-security-for-openid/</guid>
		<description><![CDATA[
			
				
			
		

Just in time before year&#8217;s end the Provider Authentication Policy Extension (PAPE) was approved as an OpenID specification by votes of members of the OpenID Foundation.
PAPE will help making OpenID more secure. To quote from our Technical Terms page:
This extension (it can be used with OpenID 1.1 and 2.0) allows Relying Parties to request that [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fspreadopenid.org%2F2009%2F01%2Fmore-security-for-openid%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fspreadopenid.org%2F2009%2F01%2Fmore-security-for-openid%2F&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p><img src='http://spreadopenid.org/wp-content/uploads/2009/01/openid-icon-100x100.png' alt='OpenID logo' /></p>
<p>Just in time before year&#8217;s end the <strong>Provider Authentication Policy Extension</strong> (<abbr title="Provider Authentication Policy Extension">PAPE</abbr>) was <a href="http://openid.net/2008/12/31/pape-approved-as-an-openid-specification/" title="PAPE approved">approved</a> as an <a href="http://openid.net/specs/openid-provider-authentication-policy-extension-1_0.html" title="PAPE Specification">OpenID specification</a> by votes of members of the <a href="http://openid.net/foundation/" title="OpenID Foundation">OpenID Foundation</a>.</p>
<p><abbr title="Provider Authentication Policy Extension">PAPE</abbr> will help making OpenID more secure. To quote from our <a href="http://spreadopenid.org/technical-terms/" title="Technical Terms">Technical Terms page</a>:</p>
<blockquote><p>This extension (it can be used with OpenID 1.1 and 2.0) allows Relying Parties to request that certain authentication policies are used by OpenID Providers when authenticating users. So it is possible that a Relying Party only lets users log in with an OpenID if they have been authenticated by multi-factor authentication (e.g. by a password and a certificate).</p></blockquote>
<p>In addition Relying Parties can request to which <strong><abbr title="National Institute of Standards and Technology">NIST</abbr></strong> (National Institute of Standards and Technology) levels the authentication adheres to. <abbr title="National Institute of Standards and Technology"><a href="http://www.nist.gov/">NIST</a></abbr> is a <abbr title="United States">US</abbr> standards laboratory which also runs a <a href="http://csrc.nist.gov/" title="Computer Security Resource Center of NIST">computer security resource center</a>. In 2006 it released an <strong>Electronic Authentication Guideline</strong> which describes four levels of authentication assurance. The levels range from rather simple authentication methods like passwords at level one to very strong methods like hardware cryptographic tokens at level four. If you like to learn more about <abbr title="National Institute of Standards and Technology">NIST</abbr> levels you should read the 64-page <abbr title="Portable Document File"><a href="http://csrc.nist.gov/publications/nistpubs/800-63/SP800-63V1_0_2.pdf" title="Electronic Authentication Guideline">PDF</a></abbr>.</p>
]]></content:encoded>
			<wfw:commentRss>http://spreadopenid.org/2009/01/more-security-for-openid/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
