Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bPxE5-00068A-5v for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Jul 2016 19:32:13 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bPxE4-0002nM-8E for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Jul 2016 19:32:12 +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 1bPxE2-0002mP-Tq for pgsql-hackers@postgresql.org; Wed, 20 Jul 2016 19:32:11 +0000 Received: from mail-qk0-x231.google.com ([2607:f8b0:400d:c09::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bPxDy-0002qI-8q for pgsql-hackers@postgresql.org; Wed, 20 Jul 2016 19:32:10 +0000 Received: by mail-qk0-x231.google.com with SMTP id o67so54918853qke.1 for ; Wed, 20 Jul 2016 12:32:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=6Hqoe7P3zAmAomRwd/g3Tblv+6WFutO8ID90rNOX1TA=; b=XiiPEmZsEMKe2Q2sHWRA6t0OS2zkY2lmCev4HmdnCIKysm8A1vlOh0T1YgzTIVmQxc RsLsSdIv9ZJIJDrF1CNrBpnsWqjlNFRHKa/nnD5/Qc7yhUPYYZBUACnmWNB8DwcgugAg ojpgAeSg+ynmXZ4dzwj9EvkN2729QgqFmJFBio1oBI+VtArNegIrXo2Wyj1T0k+ietB7 1DXnByHrGR4n/AvaPyY9ZEMkzTDIXN7Ho9n0M0n2N9gUXpqpPNwqFUrKeDANPbc4z1TR kurFGFkB0+u/fMaWBiUP7q/zAjwgjGKgbouKNZo8zlnd6P8Woz8FMbexPQQVMMdsQ9ac +7AA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=6Hqoe7P3zAmAomRwd/g3Tblv+6WFutO8ID90rNOX1TA=; b=dVarfuvJFj/HKO6yJAQc356YyFgb32Bmzw3R0KPNzbgF9C43LMBDbqepveF5oVS7Fk /S16U/rtalDYifVHkfE9TZNnAH6mh0OLweJQtfEhIk4f2Ity1PlCwoBVSV9nLJRBqpC0 QzinQYJNAoweAF7xc76UbJzi8fcYgSW38y4JjirBeRJMS3vmcSTR0aAQn2L2t2VxOGoN OmPhqOoq45uuMoBtHfNo4Vc8uvduXflkTnwA4X1PYdoWJtYi8gMRC3YY9YIc4ypbn5sh JQGdbOwx9Hvv4XPS86nacbohfSZe5ZEkVAur4u2KAhljYreQ8Z1cqibhVrLNgjEkhjVx WYYw== X-Gm-Message-State: ALyK8tJuZzjRZqX6hHxeSnagODQSVxbXqR8HQvKZyh5s/hX8WaQsGl8lZcoig3wlNOwKcYXD X-Received: by 10.55.141.193 with SMTP id p184mr65120685qkd.47.1469043123752; Wed, 20 Jul 2016 12:32:03 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([186.37.23.38]) by smtp.gmail.com with ESMTPSA id w185sm2226100qkd.23.2016.07.20.12.32.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jul 2016 12:32:03 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id 8BB64558; Wed, 20 Jul 2016 14:12:57 -0400 (CLT) Date: Wed, 20 Jul 2016 14:12:57 -0400 From: Alvaro Herrera To: Michael Paquier Cc: Magnus Hagander , Peter Eisentraut , Heikki Linnakangas , Robert Haas , Julian Markwort , Stephen Frost , David Steele , PostgreSQL mailing lists , Valery Popov Subject: Re: Password identifiers, protocol aging and SCRAM protocol Message-ID: <20160720181257.GA686053@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -1.1 (-) 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 Michael Paquier wrote: > On Wed, Jul 6, 2016 at 4:18 PM, Michael Paquier > wrote: > > OK, after hacking that for a bit I have finished with option 2 and the > > set of PG-like set of routines, the use of USE_SSL in the file > > containing all the SHA functions of OpenBSD has proved to be really > > ugly, but with a split things are really clear to the eye. The stuff I > > got builds on OSX, Linux and MSVC. pgcrypto cannot link directly to > > libpgcommon.a, so I am making it compile directly with the source > > files, as it is doing on HEAD. > > Btw, attached is the patch I did for this part if there is any interest in it. After quickly eyeballing your patch, I agree with the decision of going with (2), even if my gut initially told me that (1) would be better because it'd require less makefile trickery. I'm surprised that you say pgcrypto cannot link libpgcommon directly. Is there some insurmountable problem there? I notice your MSVC patch uses libpgcommon while the Makefile symlinks the files. -- Álvaro Herrera 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