Message195892
| Author | christian.heimes |
|---|---|
| Recipients | barry, benjamin.peterson, christian.heimes, georg.brandl, neologix, pitrou, python-dev, sbt, vajrasky, vstinner |
| Date | 2013-08-22.13:57:55 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <521618E2.1080309@cheimes.de> |
| In-reply-to | <CAMpsgwZZ+MJC+n7fZJKDp_5ZEMzSruODR1s4pntgHRY22Mb4RA@mail.gmail.com> |
| Content | |
|---|---|
Am 22.08.2013 15:20, schrieb STINNER Victor: > > STINNER Victor added the comment: > > PySSL_RAND_atfork_parent() still uses getpid(). This number is not > very random in the *parent* process :-) That's fine and doesn't diminish the properties of the PRNG. In fact the patch could use a hard coded value to perturb the PRNG. It's only important to modify the PRNG state of the *parent* process so that recycled PIDs of *child* processes don't lead to repeated pseudo-random values. PID, time and stack are just hard-to-guess properties of the process. That's all. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-08-22 13:57:56 | christian.heimes | set | recipients: + christian.heimes, barry, georg.brandl, pitrou, vstinner, benjamin.peterson, neologix, python-dev, sbt, vajrasky |
| 2013-08-22 13:57:56 | christian.heimes | link | issue18747 messages |
| 2013-08-22 13:57:55 | christian.heimes | create | |