#Tag
Bowl with two pearl chasing dragons among clouds, anonymous, c. 1680 - c. 1720
Mr and Mrs Drucker-Fraser Bequest, Montreux
turning, h 9.6cm × d 20.4cm
http://www.rijksmuseum.nl/en/collection/AK-RBK-16285-B
#rijksmuseum #musea #collection #art #mastodonart #mastoart #random
Bowl with two pearl chasing dragons among clouds, anonymous, c. 1680 - c. 1720
Mr and Mrs Drucker-Fraser Bequest, Montreux
turning, h 9.6cm × d 20.4cm
http://www.rijksmuseum.nl/en/collection/AK-RBK-16285-B
#rijksmuseum #musea #collection #art #mastodonart #mastoart #random
Earlier today, the dog went on full alarm mode at the gate. Barking, snarling, warning of intruders. Kept on doing it! Couldn't figure out what he was going on about.
It was a...er... fierce BEACH BALL... Neighbor's grandkids were over at their pool yesterday and a beach ball ended up over the wall, and it was in the street. Every time it would blow back and forth on the street, the dog would go into a frenzy!
(walked him over there, let him smell the ball, and threw it back over the wall into their pool).
About the #random thingie ... I need random data in #swad to generate unpredictable #session IDs.
I previously had an implementation trying the #Linux-originating #getrandom if available, with a fallback to a stupid internal #xorshift#PRNG, which could be disabled because it's obviously NOT cryptographically secure, and WAS disabled for the generation of session IDs.
Then I learned #arc4random is available on many systems nowadays (#FreeBSD, #NetBSD, even Linux with a recent-enough glibc), so I decided to add a compile check for it and replace the whole mess with nothing but an arc4random call IF it is available.
arc4random originates from #OpenBSD and provides the only sane way to get cryptographically secure random data. It automatically and transparently (re-)seeds from OS entropy sources, but uses an internal CSPRNG most of the time (nowadays typically #ChaCha20, so it's a misnomer, but hey ...). It never fails, it never blocks. It just works. Awesome.
I revisited that, AGAIN. Getting #random data in #poser now has yet another fallback, in case we don't have #arc4random and we also don't have #getrandom: read from /dev/random and/or /dev/urandom, "old style" 🙈. Still better to try this before resorting to a simple little #xorshift.
In the best case — arc4random found — this is still all the code of PSC_Random_bytes() 😆:
arc4random_buf(buf, count);
return count;
https://zirias.github.io/poser/api/latest/class_p_s_c___random.html
More #poser improvements:
* Use arc4random() if available, avoids excessive syscalls just to get high-quality random data
* Add a "resolver" to do #reverse#DNS lookups in a batch, remove the reverse lookup stuff from the connection which was often useless anyways, when a short-lived connection was deleted before resolving could finish 🙈
As a result, #swad can now reliably log requests with reverse lookups enabled 🥳
About the #random thingie ... I need random data in #swad to generate unpredictable #session IDs.
I previously had an implementation trying the #Linux-originating #getrandom if available, with a fallback to a stupid internal #xorshift#PRNG, which could be disabled because it's obviously NOT cryptographically secure, and WAS disabled for the generation of session IDs.
Then I learned #arc4random is available on many systems nowadays (#FreeBSD, #NetBSD, even Linux with a recent-enough glibc), so I decided to add a compile check for it and replace the whole mess with nothing but an arc4random call IF it is available.
arc4random originates from #OpenBSD and provides the only sane way to get cryptographically secure random data. It automatically and transparently (re-)seeds from OS entropy sources, but uses an internal CSPRNG most of the time (nowadays typically #ChaCha20, so it's a misnomer, but hey ...). It never fails, it never blocks. It just works. Awesome.
A space for Bonfire maintainers and contributors to communicate
