hash collision

2012-03-13 Thread John M Bliss
FYI: Adobe warns of hash collision in #ColdFusion | ZDNet http://zd.net/ymjDEy -- John Bliss - http://about.me/jbliss ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155

Re: hash collision

2012-03-13 Thread Judah McAuley
: FYI: Adobe warns of hash collision in #ColdFusion | ZDNet http://zd.net/ymjDEy -- John Bliss - http://about.me/jbliss ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp

Re: hash collision

2012-03-13 Thread Leigh
The vulnerability they are describing seems to be the one described here From the comment below, I think it is the same issue  http://forums.adobe.com/message/4264032#4264032 -Leigh ~| Order the Adobe Coldfusion Anthology

Re: hash collision

2012-03-13 Thread Judah McAuley
Thanks, Leigh, looks like that verifies that it is the same issue. Now I'm curious why it took Adobe til the middle of March to fix a vulnerability that everyone else fixed by early January at the latest. At least it is fixed. Cheers, Judah On Tue, Mar 13, 2012 at 12:29 PM, Leigh

Re: hash collision

2012-03-13 Thread Leigh
Judah - I was wondering the same thing. When it was first announced, I could not seem to find any CF specific details. I just assumed it was applicable because java was vulnerable.   -Leigh From: Judah McAuley Sent: Tuesday, March 13, 2012 3:36 PM Subject: Re: hash collision Thanks, Leigh

Re: hash collision

2012-03-13 Thread Jochem van Dieten
On Tue, Mar 13, 2012 at 8:36 PM, Judah McAuley wrote: Thanks, Leigh, looks like that verifies that it is the same issue. Now I'm curious why it took Adobe til the middle of March to fix a vulnerability that everyone else fixed by early January at the latest. Just like with their other

Re: hash collision

2012-03-13 Thread Judah McAuley
On Tue, Mar 13, 2012 at 1:06 PM, Jochem van Dieten joch...@gmail.com wrote: On Tue, Mar 13, 2012 at 8:36 PM, Judah McAuley wrote: Thanks, Leigh, looks like that verifies that it is the same issue. Now I'm curious why it took Adobe til the middle of March to fix a vulnerability that everyone