Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dhy68-0007i1-HB for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Aug 2017 13:11:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dhy67-00019W-NS for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Aug 2017 13:10:59 +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 1dhy66-00016F-Ez for pgsql-hackers@postgresql.org; Wed, 16 Aug 2017 13:10:58 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dhy61-0000eE-5z for pgsql-hackers@postgresql.org; Wed, 16 Aug 2017 13:10:57 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 8F36A206AC for ; Wed, 16 Aug 2017 09:10:51 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Wed, 16 Aug 2017 09:10:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=MX/ZrbCFDkliW1lO2i TG4fG39KQTbMXp1jRGUds/2Gg=; b=kIg5Dw327kDyRES2MgVS6WPC6aOgTMecFp J/TVxh8ZhD51ogpsJcer0oPsVjJQFiLLXnbGtzxqePFc8GN73bqTkHInoo1EJtsL ZCRce0BAM3DdvcQ4Gxfrc9l2G/RkVX3ugllDaUtEK5lf3rGqdEJ5I+wALd55Dnl+ HRW3lrRUn4RLnUbTVYLLB5bvaQrNu7bbXRfF8WBy/SzJtAW2M9BKJG5g9J8Jjd1W r8rkXsFV98hcmZ0BuPXtKixsskiJRQRxhA6uO4J+Z9JYahULQSZz8/1GM+Va98W5 T8WlM7Y4a6OBYS61QkAUawqwA/VLgn9qli4EbL73pdKL1z8Q2Imw== X-ME-Sender: X-Sasl-enc: 0KwjLbx3vyo9ZWSGy+KRCo/F2e9botc8n+2Og68MCXiJ 1502889051 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 572A4240AF for ; Wed, 16 Aug 2017 09:10:51 -0400 (EDT) To: pgsql-hackers From: Peter Eisentraut Subject: SCRAM salt length Organization: 2ndQuadrant Message-ID: <12cc9297-7e05-932f-d863-765e5626ead4@2ndquadrant.com> Date: Wed, 16 Aug 2017 09:10:51 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 The SCRAM salt length is currently set as /* length of salt when generating new verifiers */ #define SCRAM_DEFAULT_SALT_LEN 12 without further comment. I suspect that this length was chosen based on the example in RFC 5802 (SCRAM-SHA-1) section 5. But the analogous example in RFC 7677 (SCRAM-SHA-256) section 3 uses a length of 16. Should we use that instead? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers