Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bw4E5-0007cS-UO for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Oct 2016 09:28:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bw4E5-0004Ss-09 for pgsql-hackers@arkaria.postgresql.org; Mon, 17 Oct 2016 09:28:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bw4Cg-0002tD-2m for pgsql-hackers@postgresql.org; Mon, 17 Oct 2016 09:27:30 +0000 Received: from mail-lf0-x22a.google.com ([2a00:1450:4010:c07::22a]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bw4CY-0004nK-0M for pgsql-hackers@postgresql.org; Mon, 17 Oct 2016 09:27:29 +0000 Received: by mail-lf0-x22a.google.com with SMTP id l131so234649875lfl.2 for ; Mon, 17 Oct 2016 02:27:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=BoAcluPbGcdPkZsjFRmup1tAoL8PFJHn5AFNi6RtKx4=; b=aSdryMbBxBwyfMb1raI65/gkFCyIrqWh1/MvkSqSLGOuhBCQpgcuj7SIehe79LoNYg auJxzp1xaMV4pJpR2S5q7kEG4qUn75wK7JkwtrN19Di+jCtEtfzUNY609cebtbDUvBwV MXU6bksQilLUadBsX1kIO6ceru2/k/ekLyM559Md4IRHsf2b2SP6WP2JhmZsctNCZbEW LdtD47W3QmWma4ZO+FmAOKiEp7Y0USaUjjsoJADER/dHuCATvodO8OnAdCDs66ZuUYz8 sGjqQ88QOkCaohoxFN6jzWQIogpSVWlnmK8HgpMhWFaeD0zKDIKn2kB/GB+LDPG54Wlr +UOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:to:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=BoAcluPbGcdPkZsjFRmup1tAoL8PFJHn5AFNi6RtKx4=; b=isC1EAVWkeAAlchczEyrG0Yy5aUyYX6lDSDvutMwGIDJ2rOuZYTF9kZQkSokxaAY5q rqqSYNfkwjZaLdXYfOgo8vYQTsearkd8J5xXYhl2XL3M8yCTgXRsmru965KVun14qIek VV8SVUOb0VlXHuaxJGmVUIyrGYhzTM3xkyrsfMLlzcCSKbbmc6wy7cHU9Vpbt62EgjaE MjuHgcTn25IeFY34mCjEY38PCjAK8OZK8yw1njssdzTb5Po9OOnv4qpt4BagGfgg4zx5 LvIxr3k2jHagaq37EU5hdPpO0ZVDD7eMlx93+RD8+VpI4pakIlD9/dkRGqCKzR3NyGId /wkw== X-Gm-Message-State: AA6/9RmL+RF+xHk1pvoVIz+qp4H1hBilXkwXKidwoUoTHEW7v2WO2E3J/I9b1l+Po2rERw== X-Received: by 10.25.23.33 with SMTP id n33mr13681503lfi.139.1476696439108; Mon, 17 Oct 2016 02:27:19 -0700 (PDT) Received: from [192.168.1.111] (dsl-hkibrasgw1-58c38f-82.dhcp.inet.fi. [88.195.143.82]) by smtp.gmail.com with ESMTPSA id p3sm7367895lfe.1.2016.10.17.02.27.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Oct 2016 02:27:18 -0700 (PDT) Subject: Re: Password identifiers, protocol aging and SCRAM protocol To: Michael Paquier References: <47be24f5-12a5-7af8-efc0-9486a7dbd413@iki.fi> <79774ac1-df34-6b20-1659-c020c3842ce1@iki.fi> <4f3a9e71-cb1b-ca44-a780-36d503671e45@iki.fi> Cc: David Steele , Tom Lane , Robert Haas , David Fetter , Alvaro Herrera , Magnus Hagander , Peter Eisentraut , Julian Markwort , Stephen Frost , PostgreSQL mailing lists , Valery Popov From: Heikki Linnakangas Message-ID: <4e0ae28b-b61a-248c-d96c-207c9befc125@iki.fi> Date: Mon, 17 Oct 2016 12:27:17 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 10/17/2016 12:18 PM, Michael Paquier wrote: > You removed the part of pgcrypto in charge of randomness, nice move. I > was wondering about how to do with the perfc and the unix_std at some > point, and ripping them off as you did is fine for me. Yeah. I didn't understand the need for the perfc stuff. Are there Windows systems that don't have the Crypto APIs? I doubt it, but the buildfarm will tell us in a moment if there are. And if we don't have a good source of randomness like /dev/random, I think it's better to fail, than try to collect entropy ourselves (which is what unix_std did). If there's a platform where that doesn't work, someone will hopefully send us a patch, rather than silently fall back to an iffy implementation. - Heikki -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers