From owner-freebsd-ports@freebsd.org Thu Jan 5 10:43:28 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 069CFC9E01B for ; Thu, 5 Jan 2017 10:43:28 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C0C13168C for ; Thu, 5 Jan 2017 10:43:27 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cP5W2-000JTX-Ss; Thu, 05 Jan 2017 11:43:26 +0100 Date: Thu, 5 Jan 2017 11:43:26 +0100 From: Kurt Jaeger To: Jan Bramkamp Cc: freebsd-ports@freebsd.org Subject: Re: openldap-client vs openldap-sasl-client Message-ID: <20170105104326.GB2648@home.opsec.eu> References: <34b66662-a2d7-706d-3653-e0ffc9bf81b2@rlwinm.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <34b66662-a2d7-706d-3653-e0ffc9bf81b2@rlwinm.de> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 10:43:28 -0000 Hi! [openldap-client vs openldap-sasl-client and libreoffice etc] > Yes and yes it sucks. The "solution" is to build your own repo and set > the right flags to always use the same LDAP client port. With binary > packages and the speed of modern x86_64 systems I for one no longer see > removing SASL support from OpenLDAP as useful enough to justify the > complexity. The other question is: What's the use of SASL anyway ? I've seen it for years in mailserver setups, etc, and it always caused trouble. -- pi@opsec.eu +49 171 3101372 3 years to go !