Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dPLbi-0004pI-WF for pgsql-docs@arkaria.postgresql.org; Mon, 26 Jun 2017 04:26:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dPLbi-0004UD-6n for pgsql-docs@arkaria.postgresql.org; Mon, 26 Jun 2017 04:26:38 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dPLbh-0004TT-93 for pgsql-docs@postgresql.org; Mon, 26 Jun 2017 04:26:37 +0000 Received: from mail-pg0-x22d.google.com ([2607:f8b0:400e:c05::22d]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dPLbd-0000xE-Ky for pgsql-docs@postgresql.org; Mon, 26 Jun 2017 04:26:35 +0000 Received: by mail-pg0-x22d.google.com with SMTP id u62so42937224pgb.3 for ; Sun, 25 Jun 2017 21:26:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=HZ2QIdw/4AhZraROYn/SC0XGVDNRtigmKvrCvHfT11o=; b=U7eIoPsLqCmc3nQr8nc4GIiW0HuNYme4up7aR0d2WIzcKcEERTTMC7Rtp6xdl7VKCO DLNCRhxTSMO3Q4H5h7XT2qvcrQK2Xr+9IEKm8Cnrsd3AxeFESrGLJLi397TEMBi7PTtS N4i2YE1NlZUxRj99Xkr6gu0JCbwp45gOC9BV0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=HZ2QIdw/4AhZraROYn/SC0XGVDNRtigmKvrCvHfT11o=; b=FUTDUW/WAZxKQz7Jn2Q+mfZQTWXVl1RVk1aWdzH4PO2hhQSl20+LTqVN0C8715uMpq gX99DoIaXO03v+jZ3vl4wPFexcXdoZX0WYm/BjZsGpbsKTwI+bQ775m2kAC9lGf0W4Q1 iyZF64vzPx+f5oOxEW1BL/ndRXR6obNZIaBKB453F/shWd7u2CbxkNZQBGlppzP9J5K+ Ak0zHz2vv7U9gLgDcdWl2jfXr56eSRTVO5kq2J4seGZfEKJ6DSbkwnPvuGYpjtENcR/J lvls4vORSUUoghTjDI4smxM9Rv7RNbW2qUYgAGaK1OHnCMub7AhLbPi0PYRarp0M0Tcv 0kPA== X-Gm-Message-State: AKS2vOz2gttQWXs06HxVdjbyzgdsdNG2X90EcrbMg11Y/AyYceuHTi7g mnyyXxCWoN+MiRY5 X-Received: by 10.99.97.146 with SMTP id v140mr19809284pgb.62.1498451191618; Sun, 25 Jun 2017 21:26:31 -0700 (PDT) Received: from rfd.leadboat.com (c-73-158-248-138.hsd1.ca.comcast.net. [73.158.248.138]) by smtp.gmail.com with ESMTPSA id v21sm24064217pfk.75.2017.06.25.21.26.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 25 Jun 2017 21:26:30 -0700 (PDT) Date: Sun, 25 Jun 2017 21:26:28 -0700 From: Noah Misch To: Heikki Linnakangas Cc: Michael Paquier , rightfold@gmail.com, pgsql-docs@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: gen_random_uuid security not explicit in documentation Message-ID: <20170626042628.GA1995569@rfd.leadboat.com> References: <20170101232054.10135.50528@wrigleys.postgresql.org> <22b132fc-e7cb-f40b-aa8e-7a54da41bf96@iki.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Fri, Jun 23, 2017 at 10:23:36AM +0900, Michael Paquier wrote: > On Fri, Jun 23, 2017 at 3:02 AM, Heikki Linnakangas 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 -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs