|
Revision tags: lighttpd-1.4.69, lighttpd-1.4.68, lighttpd-1.4.67, lighttpd-1.4.66, lighttpd-1.4.65, lighttpd-1.4.64, lighttpd-1.4.63, lighttpd-1.4.62, lighttpd-1.4.61, lighttpd-1.4.60, lighttpd-1.4.59, lighttpd-1.4.58, lighttpd-1.4.57, lighttpd-1.4.56, lighttpd-1.4.56-rc7, lighttpd-1.4.56-rc6, lighttpd-1.4.56-rc5, lighttpd-1.4.56-rc4, lighttpd-1.4.56-rc3, lighttpd-1.4.56-rc2, lighttpd-1.4.56-rc1, lighttpd-1.4.55, lighttpd-1.4.54, lighttpd-1.4.53, lighttpd-1.4.52, lighttpd-1.4.51, lighttpd-1.4.50, lighttpd-1.4.49, lighttpd-1.4.48, lighttpd-1.4.47, lighttpd-1.4.46 |
|
| #
6e171bd4 |
| 21-Sep-2017 |
Glenn Strauss <[email protected]> |
[core] adjust li_rand_pseudo* interfaces
|
|
Revision tags: lighttpd-1.4.45, lighttpd-1.4.44 |
|
| #
c64c2173 |
| 05-Dec-2016 |
Glenn Strauss <[email protected]> |
[core] rename li_rand() to li_rand_pseudo_bytes()
to be more explicit that the result is pseudo-random data
and not cryptographically random.
|
|
Revision tags: lighttpd-1.4.43, lighttpd-1.4.42 |
|
| #
7f4e156e |
| 13-Oct-2016 |
Glenn Strauss <[email protected]> |
[core] rand.[ch] to use better RNGs when available
prefer RAND_pseudo_bytes() (openssl), arc4random() or jrand48(),
if available, over rand()
These are not necessarily cryptographically secure, but
[core] rand.[ch] to use better RNGs when available
prefer RAND_pseudo_bytes() (openssl), arc4random() or jrand48(),
if available, over rand()
These are not necessarily cryptographically secure, but should be better
than rand()
show more ...
|