Message195361
| Author |
christian.heimes |
| Recipients |
christian.heimes, hynek, jcea, neologix, pitrou, tarek, vstinner |
| Date |
2013年08月16日.16:54:31 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<520E5947.2000405@cheimes.de> |
| In-reply-to |
<CAH_1eM3OGdFTLJXemgkiKtHDiDmdfVJvLKSsQueOM9nONDFs5A@mail.gmail.com> |
| Content |
Am 16.08.2013 18:47, schrieb Charles-François Natali:
> I don't think it can be fixed. I think Christian's working on a PEP
> for random number generators, which would probably make it easier,
> although I din't have a look at it.
In the light of the recent Android issue with PRNGs [1] I don't think
that Python should roll out its own CPRNG. I'd rather use the operation
system's CPRNG or OpenSSL's CPRNG. After all we aren't crypto experts.
I'd rather point my finger to OpenSSL than take the blame for a faulty
CPRNG.
[1] http://bitcoin.org/en/alert/2013-08-11-android |
|