<?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 for PHP++</title>
	<atom:link href="http://www.rhapsody.intheblackbox.com/blog/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.rhapsody.intheblackbox.com/blog</link>
	<description>when you occasionally dream of tetris</description>
	<pubDate>Mon, 06 Sep 2010 09:42:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Dynamically Generated Greasemonkey Scripts by Geekfish</title>
		<link>http://www.rhapsody.intheblackbox.com/blog/?p=28&#038;cpage=1#comment-310</link>
		<dc:creator>Geekfish</dc:creator>
		<pubDate>Mon, 08 Feb 2010 12:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhapsody.intheblackbox.com/blog/?p=28#comment-310</guid>
		<description>@Kano
I'm glad this finally helped someone :)


@darasion
Chrome might be trying to do the same work as Greasemonkey, but it most likely has differences in the way it treats the scripts. I'd be interested to know why it doesn't work, and will most certainly update this post if I have to time to look into it.
I hope you find the solution.</description>
		<content:encoded><![CDATA[<p>@Kano<br />
I&#8217;m glad this finally helped someone <img src='http://www.rhapsody.intheblackbox.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>@darasion<br />
Chrome might be trying to do the same work as Greasemonkey, but it most likely has differences in the way it treats the scripts. I&#8217;d be interested to know why it doesn&#8217;t work, and will most certainly update this post if I have to time to look into it.<br />
I hope you find the solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dynamically Generated Greasemonkey Scripts by darasion</title>
		<link>http://www.rhapsody.intheblackbox.com/blog/?p=28&#038;cpage=1#comment-309</link>
		<dc:creator>darasion</dc:creator>
		<pubDate>Mon, 08 Feb 2010 12:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhapsody.intheblackbox.com/blog/?p=28#comment-309</guid>
		<description>Does not work in google chrome.</description>
		<content:encoded><![CDATA[<p>Does not work in google chrome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Juggling routines by jordan taylor</title>
		<link>http://www.rhapsody.intheblackbox.com/blog/?p=66&#038;cpage=1#comment-304</link>
		<dc:creator>jordan taylor</dc:creator>
		<pubDate>Sat, 30 Jan 2010 21:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhapsody.intheblackbox.com/blog/?p=66#comment-304</guid>
		<description>thanks he is real good.... but could be much beter if all done smaller  lol thnx</description>
		<content:encoded><![CDATA[<p>thanks he is real good&#8230;. but could be much beter if all done smaller  lol thnx</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dynamically Generated Greasemonkey Scripts by Karlo</title>
		<link>http://www.rhapsody.intheblackbox.com/blog/?p=28&#038;cpage=1#comment-284</link>
		<dc:creator>Karlo</dc:creator>
		<pubDate>Tue, 22 Dec 2009 13:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhapsody.intheblackbox.com/blog/?p=28#comment-284</guid>
		<description>Thanks a heap, you saved my day. That's the solution i was looking for the last days...</description>
		<content:encoded><![CDATA[<p>Thanks a heap, you saved my day. That&#8217;s the solution i was looking for the last days&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About by Gatoni</title>
		<link>http://www.rhapsody.intheblackbox.com/blog/?page_id=4&#038;cpage=1#comment-157</link>
		<dc:creator>Gatoni</dc:creator>
		<pubDate>Wed, 25 Mar 2009 22:35:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhapsody.intheblackbox.com/blog/?page_id=4#comment-157</guid>
		<description>Congratulations! Nice blog! Why didn´t you tell me about it!?

By the way... "Code Monkey" is not something flattering -"code monkeys" are the dudes and dudettes who write tones of simple and boring code -usually the most simple parts of a project:

"The term code monkey generally refers to a computer programmer or other person who writes computer code for a living. More specifically, it refers to a person only capable of grinding out code, but unable to perform the more intellectually complex tasks of software architecture, analysis, and design. The term is thus considered mildly insulting, and is often applied to the most junior people on a programming team."

You're not a code monkey, Woman! ;)</description>
		<content:encoded><![CDATA[<p>Congratulations! Nice blog! Why didn´t you tell me about it!?</p>
<p>By the way&#8230; &#8220;Code Monkey&#8221; is not something flattering -&#8221;code monkeys&#8221; are the dudes and dudettes who write tones of simple and boring code -usually the most simple parts of a project:</p>
<p>&#8220;The term code monkey generally refers to a computer programmer or other person who writes computer code for a living. More specifically, it refers to a person only capable of grinding out code, but unable to perform the more intellectually complex tasks of software architecture, analysis, and design. The term is thus considered mildly insulting, and is often applied to the most junior people on a programming team.&#8221;</p>
<p>You&#8217;re not a code monkey, Woman! <img src='http://www.rhapsody.intheblackbox.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on To GET or to POST? Edit: Deezer.com example by dionyziz</title>
		<link>http://www.rhapsody.intheblackbox.com/blog/?p=15&#038;cpage=1#comment-138</link>
		<dc:creator>dionyziz</dc:creator>
		<pubDate>Tue, 10 Feb 2009 18:22:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhapsody.intheblackbox.com/blog/?p=15#comment-138</guid>
		<description>It's awesome (even though I use RSS :-))</description>
		<content:encoded><![CDATA[<p>It&#8217;s awesome (even though I use RSS :-))</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on To GET or to POST? Edit: Deezer.com example by Geekfish</title>
		<link>http://www.rhapsody.intheblackbox.com/blog/?p=15&#038;cpage=1#comment-116</link>
		<dc:creator>Geekfish</dc:creator>
		<pubDate>Sat, 31 Jan 2009 11:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhapsody.intheblackbox.com/blog/?p=15#comment-116</guid>
		<description>heheh, right, it's a stupid-get-usage-issue :P
Actually I never really liked email confirmation for this type of sites, it just slows you down. Especially if the mail goes to spam for some reason, or doesn't get delivered at all. Or/And if you have to put unreadable Captchas,  The Deezer guys didn't answer me actually when I told them, and took them quite a while (years? :P) to "fix" this.


(how do you like the new blog theme btw? ^^)</description>
		<content:encoded><![CDATA[<p>heheh, right, it&#8217;s a stupid-get-usage-issue <img src='http://www.rhapsody.intheblackbox.com/blog/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /><br />
Actually I never really liked email confirmation for this type of sites, it just slows you down. Especially if the mail goes to spam for some reason, or doesn&#8217;t get delivered at all. Or/And if you have to put unreadable Captchas,  The Deezer guys didn&#8217;t answer me actually when I told them, and took them quite a while (years? :P) to &#8220;fix&#8221; this.</p>
<p>(how do you like the new blog theme btw? ^^)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Non Compatible by Geekfish</title>
		<link>http://www.rhapsody.intheblackbox.com/blog/?p=22&#038;cpage=1#comment-115</link>
		<dc:creator>Geekfish</dc:creator>
		<pubDate>Sat, 31 Jan 2009 10:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhapsody.intheblackbox.com/blog/?p=22#comment-115</guid>
		<description>It's because I moved the blog from the wordpress server. I'm searching for those images/videos I had, cause I'd made a whole series of them :(</description>
		<content:encoded><![CDATA[<p>It&#8217;s because I moved the blog from the wordpress server. I&#8217;m searching for those images/videos I had, cause I&#8217;d made a whole series of them <img src='http://www.rhapsody.intheblackbox.com/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Non Compatible by dionyziz</title>
		<link>http://www.rhapsody.intheblackbox.com/blog/?p=22&#038;cpage=1#comment-114</link>
		<dc:creator>dionyziz</dc:creator>
		<pubDate>Sat, 31 Jan 2009 09:56:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhapsody.intheblackbox.com/blog/?p=22#comment-114</guid>
		<description>404's :-(</description>
		<content:encoded><![CDATA[<p>404&#8217;s <img src='http://www.rhapsody.intheblackbox.com/blog/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on To GET or to POST? Edit: Deezer.com example by dionyziz</title>
		<link>http://www.rhapsody.intheblackbox.com/blog/?p=15&#038;cpage=1#comment-113</link>
		<dc:creator>dionyziz</dc:creator>
		<pubDate>Sat, 31 Jan 2009 09:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhapsody.intheblackbox.com/blog/?p=15#comment-113</guid>
		<description>The Deezer.com issue is not really a GET/POST issue. They should be using GET indeed to verify your e-mail address (as there is no other technical way of having you open POST links in e-mails). Furthermore, even if it were POST, it wouldn't have solved the problem, as one could easily craft a POST request to their page by simply incorporating a custom HTML form.

The correct way of solving this would be to generate a random hash for every user account (for example a 32-character-long hex string) that would be passed as a parameter along with the e-mail address in the link. That way, if you don't get the e-mail, you won't be able to know the secret hash, and hence won't be able to fake an e-mail validation.

Seems like Deezer.com has read your blog post and fixed the issue, but they fixed it wrong. The confirmation link now looks like this:

http://www.deezer.com/confirm.php?email=ZGlvbnl6aXpAZ21haWwuY29t&amp;c=1 

Security through obscurity! Any geek would easily be able to find that this is a base64-encoded e-mail address; how lame. Apparently they don't realize that  encrypting the e-mail address won't help them, as one can easily decrypt any kind of encryption since they're able to have access to as large a dataset they like (by making as many accounts as they like). The only way to solve this properly is through a hash.

dionyziz@orion:~$ php -r "echo base64_decode( 'ZGlvbnl6aXpAZ21haWwuY29t' );"
dionyziz@gmail.com

So yeah. Thanks for the post! I'll also let the Deezer.com guys know about the second security issue.</description>
		<content:encoded><![CDATA[<p>The Deezer.com issue is not really a GET/POST issue. They should be using GET indeed to verify your e-mail address (as there is no other technical way of having you open POST links in e-mails). Furthermore, even if it were POST, it wouldn&#8217;t have solved the problem, as one could easily craft a POST request to their page by simply incorporating a custom HTML form.</p>
<p>The correct way of solving this would be to generate a random hash for every user account (for example a 32-character-long hex string) that would be passed as a parameter along with the e-mail address in the link. That way, if you don&#8217;t get the e-mail, you won&#8217;t be able to know the secret hash, and hence won&#8217;t be able to fake an e-mail validation.</p>
<p>Seems like Deezer.com has read your blog post and fixed the issue, but they fixed it wrong. The confirmation link now looks like this:</p>
<p><a href="http://www.deezer.com/confirm.php?email=ZGlvbnl6aXpAZ21haWwuY29t&amp;c=1" rel="nofollow">http://www.deezer.com/confirm.php?email=ZGlvbnl6aXpAZ21haWwuY29t&amp;c=1</a> </p>
<p>Security through obscurity! Any geek would easily be able to find that this is a base64-encoded e-mail address; how lame. Apparently they don&#8217;t realize that  encrypting the e-mail address won&#8217;t help them, as one can easily decrypt any kind of encryption since they&#8217;re able to have access to as large a dataset they like (by making as many accounts as they like). The only way to solve this properly is through a hash.</p>
<p>dionyziz@orion:~$ php -r &#8220;echo base64_decode( &#8216;ZGlvbnl6aXpAZ21haWwuY29t&#8217; );&#8221;<br />
<a href="mailto:dionyziz@gmail.com">dionyziz@gmail.com</a></p>
<p>So yeah. Thanks for the post! I&#8217;ll also let the Deezer.com guys know about the second security issue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
