Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bPy54-0000bt-J8 for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Jul 2016 20:26: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 1bPy54-0008VV-1e for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Jul 2016 20:26:58 +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 1bPy3i-00070D-1V for pgsql-hackers@postgresql.org; Wed, 20 Jul 2016 20:25:34 +0000 Received: from 173-164-140-181-sfba.hfc.comcastbusiness.net ([173.164.140.181] helo=fetter.org) by magus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bPy3e-0003kB-G4 for pgsql-hackers@postgresql.org; Wed, 20 Jul 2016 20:25:33 +0000 Received: by fetter.org (Postfix, from userid 1000) id D2906E0454; Wed, 20 Jul 2016 13:25:24 -0700 (PDT) Date: Wed, 20 Jul 2016 13:25:24 -0700 From: David Fetter To: Alvaro Herrera Cc: Michael Paquier , 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: <20160720202524.GA16111@fetter.org> References: <20160720181257.GA686053@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160720181257.GA686053@alvherre.pgsql> User-Agent: Mutt/1.6.2 (2016-07-01) X-Pg-Spam-Score: -0.9 (/) 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 Wed, Jul 20, 2016 at 02:12:57PM -0400, Alvaro Herrera wrote: > 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. People have, in the past, expressed concerns about linking in pgcrypto. Apparently, in some countries, it's a legal problem. Best, David. -- David Fetter http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers