Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cxnK2-0002Lo-PC for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Apr 2017 04:22:31 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cxnK2-0008OF-1Q for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Apr 2017 04:22:30 +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 1cxnK0-0008Mg-Ey for pgsql-hackers@postgresql.org; Tue, 11 Apr 2017 04:22:28 +0000 Received: from mail-pg0-x22d.google.com ([2607:f8b0:400e:c05::22d]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cxnJw-0004BR-HO for pgsql-hackers@postgresql.org; Tue, 11 Apr 2017 04:22:27 +0000 Received: by mail-pg0-x22d.google.com with SMTP id g2so114571584pge.3 for ; Mon, 10 Apr 2017 21:22:23 -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=l8hLziB1xlwPjzvSRR/U8cf4FoSP0vofSo0reXp9G3o=; b=I9yb+KxEPN4HFcOM+79hlRLXcMSCN0x/VUm4QywlIpN7jSDJ1f76OCvwagomZ81oZ9 vlPPEz+Kqb/cVhGyKIJWfRkJcF1pXnJQfsbd46lA95XSmq9KOBTZc59OAub4YlTDpdD8 GS0a+BcSPhTgjY2Xwio9fB3TM3sMrmclA6+DI= 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=l8hLziB1xlwPjzvSRR/U8cf4FoSP0vofSo0reXp9G3o=; b=UHmdCa6r3dFVoHS7/h7WkrAyOiPQlxDoGPro3GB534AZaozeB3ZqYeD6T+LAFQDhm5 UL3qgf3B2KqIjRkdsOoRZxwzQ4R7dHmC7wL/KgwToWY3e7wMVZqLahYrxp4wcF7eS4pI ibSZRbc00bqg4kcaZrBoPayRq+MEGPqNoniLlke4JbkwrfoODXSA/a0kubUSMNF3aTRK 8WmJ4ykVus13cCftaejwzgGth981v185c25J5Dd9TyVlKcDEaUBMKbazPnTKGQdCBNoW q+NpWQpaO27XumSkGbhllQ5QY6zvb3lVtdr0DgZBy+trPSs1+zOx2eMqgz+EZNH0asyv fPIQ== X-Gm-Message-State: AFeK/H2zd7vhwU9YIoiNAh2iqW1CTcoqsEbwNH7w1C1+GBnyfzfdj+wOaOzWZcS3LSfKfg== X-Received: by 10.84.218.130 with SMTP id r2mr72101352pli.79.1491884542003; Mon, 10 Apr 2017 21:22:22 -0700 (PDT) Received: from tornado.leadboat.com (c-98-248-47-228.hsd1.ca.comcast.net. [98.248.47.228]) by smtp.gmail.com with ESMTPSA id n7sm27310109pfn.0.2017.04.10.21.22.20 (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 10 Apr 2017 21:22:20 -0700 (PDT) Date: Tue, 11 Apr 2017 00:22:18 -0400 From: Noah Misch To: Heikki Linnakangas Cc: pgsql-hackers@postgresql.org Subject: Re: pgsql: Use SASLprep to normalize passwords for SCRAM authentication. Message-ID: <20170411042218.GA2870410@tornado.leadboat.com> References: 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) X-Pg-Spam-Score: -2.0 (--) 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 Fri, Apr 07, 2017 at 11:58:10AM +0000, Heikki Linnakangas wrote: > No documentation changes included, because there is no details on the > SCRAM mechanism in the docs anyway. An overview on that in the protocol > specification would probably be good, even though SCRAM is documented in > detail in RFC5802. I'll write that as a separate patch. An important thing > to mention there is that we apply SASLprep even on invalid UTF-8 strings, > to support other encodings. [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-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers