From: Heikki Linnakangas <hlinnaka@iki.fi>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: rightfold@gmail.com
Cc: pgsql-docs@postgresql.org
Subject: Re: gen_random_uuid security not explicit in documentation
Date: Mon, 3 Jul 2017 12:22:25 +0300
Message-ID: <7aff5b9c-a7f2-96cd-0739-d2808cc3508a@iki.fi> (raw)
In-Reply-To: <CAB7nPqTm1SaSwaQS87Xx8Y2Zx9ZthRqwCVWtw76FVd2LqaSy7A@mail.gmail.com>
References: <20170101232054.10135.50528@wrigleys.postgresql.org>
<CAB7nPqQuvGF=fqmSUnDZ6-qmCR_w0GygcaztFfDxVg05wk0k8w@mail.gmail.com>
<22b132fc-e7cb-f40b-aa8e-7a54da41bf96@iki.fi>
<CAB7nPqTm1SaSwaQS87Xx8Y2Zx9ZthRqwCVWtw76FVd2LqaSy7A@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
On 06/23/2017 04:23 AM, Michael Paquier wrote:
> On Fri, Jun 23, 2017 at 3:02 AM, Heikki Linnakangas <hlinnaka@iki.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.
Ok, pushed a fix to do that.
Thanks for bringing this up, Radek!
- Heikki
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: hlinnaka@iki.fi, michael.paquier@gmail.com, rightfold@gmail.com
Subject: Re: gen_random_uuid security not explicit in documentation
In-Reply-To: <7aff5b9c-a7f2-96cd-0739-d2808cc3508a@iki.fi>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox