| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Joe Conway <mail(at)joeconway(dot)com> |
| Subject: | Re: Support getrandom() for pg_strong_random() source |
| Date: | 2025-10-07 08:40:11 |
| Message-ID: | 84FF81D8-6B0E-4D7D-A396-393595F66EEE@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 6 Oct 2025, at 20:41, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> Are there any use cases other than UUID that want CSPRNG guarantees
> without needing CSPRNG security?
None come to mind, and it seems increasingly likely that designing API which we
confidently can document how to use is too complicated. Maybe it's better to
re-focus on just the usecase in the UUID code and leave the API at pg_prng()
and pg_strong_random()? (We already have UUID code in contrib which in some
cases use arc4random after all.)
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-10-07 08:44:26 | Re: git head build failure |
| Previous Message | Daniel Gustafsson | 2025-10-07 08:25:46 | Re: Support getrandom() for pg_strong_random() source |