Re: Support getrandom() for pg_strong_random() source
От | Jacob Champion |
---|---|
Тема | Re: Support getrandom() for pg_strong_random() source |
Дата | |
Msg-id | CAOYmi+khvFu_a4zLDhVanzN3sTV2dHYp31=wxDM_EqgMhqbyZA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Support getrandom() for pg_strong_random() source (Peter Eisentraut <peter@eisentraut.org>) |
Ответы |
Re: Support getrandom() for pg_strong_random() source
|
Список | pgsql-hackers |
On Wed, Jul 30, 2025 at 4:09 AM Peter Eisentraut <peter@eisentraut.org> wrote: > The POSIX description of getentropy() says: > > "The intended use of this function is to create a seed for other > pseudo-random number generators." > > So using getentropy() for generating the random numbers that are passed > back to the application code would appear to be the wrong use. What are the situations in which a stream of numbers would be suitable for seeding a CSPRNG, but not suitable as output from a CSPRNG? On Wed, Jul 30, 2025 at 4:10 AM Peter Eisentraut <peter@eisentraut.org> wrote: > The point still stands that the number of installations without OpenSSL > support is approximately zero, so what is the purpose of this patch if > approximately no one will be able to use it? Upthread I'd suggested that we put some thought into making it configurable, with the understanding that we'd need to document exactly what we think the advantages of the approaches are. --Jacob
В списке pgsql-hackers по дате отправления: