| 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>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Support getrandom() for pg_strong_random() source |
| Date: | 2025-07-28 11:36:31 |
| Message-ID: | D120EC9F-D885-45B0-AD81-A5222D4940C0@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 23 Jul 2025, at 19:11, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> .. maybe the pendulum has swung far enough that we can expect any
> kernel supporting getentropy() to be able to do the job just as well
> as OpenSSL does in userspace, except also faster? I think it might be
> worth a discussion.
There has in the past been discussions (at least off-list in hallway tracks)
about allowing randomness to be chosen separately from underlying factors such
as OpenSSL support, at the time it didn't seem worth the trouble but that may
well have changed.
With OpenSSL 1.1.1 being the baseline we can also make use of the _priv_bytes
functions to get increased isolation.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2025-07-28 11:43:08 | Re: Conflict detection for update_deleted in logical replication |
| Previous Message | Xuneng Zhou | 2025-07-28 11:29:23 | Re: Add progressive backoff to XactLockTableWait functions |