FS#36640 - [openssl] Rand Number Generator produces equal number sequences for forked processes with equal PID

Attached to Project: Arch Linux
Opened by Lennart Riecken (lriecken) - Thursday, 22 August 2013, 21:18 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 20:49 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The Problem with the OpenSSL Random Number Generator creating predictable numbers after forking the process illustrated in this Blog Posting also applies to ArchLinux' OpenSSL version.
http://emboss.github.io/blog/2013/08/21/openssl-prng-is-not-really-fork-safe/
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Saturday, 02 November 2013, 20:49 GMT
Reason for closing:  Upstream
Comment by Dave Reisner (falconindy) - Thursday, 22 August 2013, 21:53 GMT
Arch does not seem to be affected by this... Compiling and running the C code yields:

pid=29776 \x85\xdc\x10\x73
pid=29776 \xaf\x78\xad\xfe

Running this on ubuntu 12.04 shows the vulnerability:

pid=22184 \xa1\x76\x29\xc1
pid=22184 \xa1\x76\x29\xc1
Comment by Lennart Riecken (lriecken) - Thursday, 22 August 2013, 21:54 GMT
The Blog posting contains two c code samples. The second one works on my System:
pid=2650 \xcd\xce\x97\x80
pid=2650 \xcd\xce\x97\x80
Comment by Lennart Riecken (lriecken) - Thursday, 22 August 2013, 21:56 GMT
This is the code.
   test2.c (1 KiB)
Comment by Dave Reisner (falconindy) - Thursday, 22 August 2013, 22:03 GMT
Ah, the difference is the memset which was patched in by debian. Upstream doesn't seem to care and claims that this is a programming error.

Really nothing for Arch to do until openssl upstream releases a patch.
Comment by Pierre Schmitz (Pierre) - Friday, 23 August 2013, 06:46 GMT
Right, this is an upstream bug if at all.

Loading...