Message213757
| Author | Jeffrey.Walton |
|---|---|
| Recipients | Arfrever, Jeffrey.Walton, barry, benjamin.peterson, christian.heimes, georg.brandl, larry, neologix, pitrou, python-dev, sbt, vajrasky, vstinner |
| Date | 2014-03-16.20:46:35 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1395002796.13.0.92603928915.issue18747@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> It probably is an OpenSSL bug but the declaration doesn't help us. > It's not the first time Python has to work around OpenSSL, e.g. #18709. Sorry to dig up an old issue. But here's some reading on it if interested. Ben Laurire pushed a patch to mix in PID and time. The PID was already being used, so the patch adds the time. See "Mixing time into the pool", http://www.mail-archive.com/openssl-dev@openssl.org/msg33012.html. And the commit: https://github.com/openssl/openssl/commit/3cd8547a2018ada88a4303067a2aa15eadc17f39. OpenSSL added a wiki page for reading on the subject: http://wiki.openssl.org/index.php/Random_fork-safety. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-03-16 20:46:36 | Jeffrey.Walton | set | recipients: + Jeffrey.Walton, barry, georg.brandl, pitrou, vstinner, larry, christian.heimes, benjamin.peterson, Arfrever, neologix, python-dev, sbt, vajrasky |
| 2014-03-16 20:46:36 | Jeffrey.Walton | set | messageid: <1395002796.13.0.92603928915.issue18747@psf.upfronthosting.co.za> |
| 2014-03-16 20:46:36 | Jeffrey.Walton | link | issue18747 messages |
| 2014-03-16 20:46:35 | Jeffrey.Walton | create | |