Comment by tptacek

So I have this straight, you're concerned that the raw output of lrand48 seeded by a timestamp taken at the time the curves were known to be generated might happen to collide with a hash function output, or, better yet, the precise value needed to trip an unknown elliptic curve vulnerability?

I have that right?