From: Noah Misch <noah@leadboat.com>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: rightfold@gmail.com
Cc: pgsql-docs@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: gen_random_uuid security not explicit in documentation
Date: Thu, 29 Jun 2017 20:45:04 -0700
Message-ID: <20170630034504.GB2045345@rfd.leadboat.com> (raw)
In-Reply-To: <20170626042628.GA1995569@rfd.leadboat.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>
<20170626042628.GA1995569@rfd.leadboat.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
On Sun, Jun 25, 2017 at 09:26:28PM -0700, Noah Misch wrote:
> On Fri, Jun 23, 2017 at 10:23:36AM +0900, 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.
>
> [Action required within three days. This is a generic notification.]
>
> The above-described topic is currently a PostgreSQL 10 open item. Heikki,
> since you committed the patch believed to have created it, you own this open
> item. If some other commit is more relevant or if this does not belong as a
> v10 open item, please let us know. Otherwise, please observe the policy on
> open item ownership[1] and send a status update within three calendar days of
> this message. Include a date for your subsequent status update. Testers may
> discover new open items at any time, and I want to plan to get them all fixed
> well in advance of shipping v10. Consequently, I will appreciate your efforts
> toward speedy resolution. Thanks.
>
> [1] https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com
This PostgreSQL 10 open item is past due for your status update. Kindly send
a status update within 24 hours, and include a date for your subsequent status
update. Refer to the policy on open item ownership:
https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com
--
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: noah@leadboat.com, hlinnaka@iki.fi, michael.paquier@gmail.com, rightfold@gmail.com, pgsql-hackers@postgresql.org
Subject: Re: gen_random_uuid security not explicit in documentation
In-Reply-To: <20170630034504.GB2045345@rfd.leadboat.com>
* 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