summaryrefslogtreecommitdiff
path: root/sapi/fpm
diff options
context:
space:
mode:
authorAnatol Belski <ab@php.net>2017-02-11 21:47:09 +0100
committerAnatol Belski <ab@php.net>2017-02-11 21:47:09 +0100
commit048aec47963ac86580a96ff64fa6d16de2f86045 (patch)
treefbad6ce961c5f0f05ddc0e9183a5090b129598b1 /sapi/fpm
parent23bd7bcde03c31e2678f23f12c72c96c24800c92 (diff)
downloadphp-git-048aec47963ac86580a96ff64fa6d16de2f86045.tar.gz
Revert "refactor php_win32_get_random_bytes()"
This reverts commit 23bd7bcde03c31e2678f23f12c72c96c24800c92. Looks like this change is unstable. If same CSP is use but multiple processers, the initialization failures are possible. Thus, CryptAcquireContext in every process, even if it won't be used at all, is not sensible. This might actually motivate to look for better CSP APIs.
Diffstat (limited to 'sapi/fpm')
0 files changed, 0 insertions, 0 deletions