<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Session fixation vulnerability in Devise	</title>
	<atom:link href="/2010/11/session-fixation-vulnerability-in-devise/feed/" rel="self" type="application/rss+xml" />
	<link>/2010/11/session-fixation-vulnerability-in-devise/</link>
	<description>Plataformatec&#039;s place to talk about Ruby, Ruby on Rails, Elixir, and software engineering</description>
	<lastBuildDate>Fri, 11 Feb 2011 12:13:34 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.2</generator>
	<item>
		<title>
		By: josevalim		</title>
		<link>/2010/11/session-fixation-vulnerability-in-devise/comment-page-1/#comment-1049</link>

		<dc:creator><![CDATA[josevalim]]></dc:creator>
		<pubDate>Fri, 26 Nov 2010 18:07:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1520#comment-1049</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;/2010/11/session-fixation-vulnerability-in-devise/comment-page-1/#comment-1048&quot;&gt;pjb3&lt;/a&gt;.

Rails does not allow by default to set the session ID through GET or POST and that is really not recommended. All the problems with having the session ID stored in a cookie is fixed after this release.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="/2010/11/session-fixation-vulnerability-in-devise/comment-page-1/#comment-1048">pjb3</a>.</p>
<p>Rails does not allow by default to set the session ID through GET or POST and that is really not recommended. All the problems with having the session ID stored in a cookie is fixed after this release.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: pjb3		</title>
		<link>/2010/11/session-fixation-vulnerability-in-devise/comment-page-1/#comment-1048</link>

		<dc:creator><![CDATA[pjb3]]></dc:creator>
		<pubDate>Fri, 26 Nov 2010 17:14:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=1520#comment-1048</guid>

					<description><![CDATA[Now that the security issues has been fixed, could you provide more details on the vulnerability?  I looked at the commit and I see that you are making sure a new session ID is generated upon login, which is good, but if you are only allowing the session ID to submitted via a cookie and not be set by a query string param or form param, is there still a vulnerability?]]></description>
			<content:encoded><![CDATA[<p>Now that the security issues has been fixed, could you provide more details on the vulnerability?  I looked at the commit and I see that you are making sure a new session ID is generated upon login, which is good, but if you are only allowing the session ID to submitted via a cookie and not be set by a query string param or form param, is there still a vulnerability?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
