Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 17 Sep 2012 11:36:46 -0400 (EDT)
From: Josh Bressers <>
Cc: argyros george <>,
        Aggelos Kiayias <>,
        Vladimir Vorontsov <>,
        gifts <>
Subject: Re: Randomness Attacks Against PHP Applications

----- Original Message -----
> On Wed, Aug 22, 2012 at 02:31:07PM +0400, Solar Designer wrote:
> > On Thu, Aug 09, 2012 at 11:19:14AM -0700, Yves-Alexis Perez wrote:
> > > Paper authors tried to port this to PHP security team, but it seems
> > > the answer was that it was an application problem.
> > 
> > Here's a vulnerability in and attack on session IDs of PHP proper:
> > 
> >
> > 
> > This is not exactly the same topic (PHP apps vs. PHP itself), yet it's
> > closely related and the timing of it was provoked by the same research.
> FWIW, here's a PHP mt_rand() seed cracker that I wrote:
> It finds possible seeds given the very first mt_rand() output after
> being seeded with mt_srand().


> Maybe these PoCs will help convince someone.

I'm skeptical they will. I've been doing a lot of work for the past year on
various proactive security efforts. I keep coming back to two basic things.

1) Most people don't understand security (if they can learn is another
2) We suck at explaining security concepts.

Item 1 is solvable to a certain degree with training, but this particular
issue I bet is #2.

WE see why this is a problem and have trouble understanding why the PHP
guys don't. Has anyone tried to talk to them about this further to see if
the issue is they don't understand, or are they being stubborn?

I'm quite interested in this problem (the general communication issue, not
specially this PHP problem).



Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.