| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | rightfold(at)gmail(dot)com, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: gen_random_uuid security not explicit in documentation |
| Date: | 2017-06-23 01:23:36 |
| Message-ID: | CAB7nPqTm1SaSwaQS87Xx8Y2Zx9ZthRqwCVWtw76FVd2LqaSy7A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Fri, Jun 23, 2017 at 3:02 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> I'm inclined to change gen_random_uuid() to throw an error if the server is
> built with --disable-strong-random, like gen_random_bytes() does. That way,
> they would behave the same.
No objections to do that. I guess you don't need a patch. As this is
new to 10, I have added an open item.
> Thoughts?
There is this comment in pgcrypto.c with a typo:
* Generate random bits. pg_backend_random() will do here, we don't promis
s/promis/promise/.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerard Matthews | 2017-06-23 06:14:34 | Re: nothing ever works |
| Previous Message | Joe Conway | 2017-06-22 23:25:08 | Re: nothing ever works |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2017-06-23 01:28:21 | Re: Multi column range partition table |
| Previous Message | Masahiko Sawada | 2017-06-23 01:22:43 | Re: Setting pd_lower in GIN metapage |