Return-Path: X-Original-To: apmail-subversion-dev-archive@minotaur.apache.org Delivered-To: apmail-subversion-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 748C918122 for ; Sat, 30 Apr 2016 07:43:09 +0000 (UTC) Received: (qmail 52182 invoked by uid 500); 30 Apr 2016 07:43:09 -0000 Delivered-To: apmail-subversion-dev-archive@subversion.apache.org Received: (qmail 52106 invoked by uid 500); 30 Apr 2016 07:43:09 -0000 Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@subversion.apache.org Received: (qmail 52095 invoked by uid 99); 30 Apr 2016 07:43:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Apr 2016 07:43:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 64C7C180591 for ; Sat, 30 Apr 2016 07:43:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=qqmail.nl Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id czfCf0LqrVLR for ; Sat, 30 Apr 2016 07:43:05 +0000 (UTC) Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E28AC5F1D4 for ; Sat, 30 Apr 2016 07:43:04 +0000 (UTC) Received: by mail-wm0-f54.google.com with SMTP id e201so51382961wme.0 for ; Sat, 30 Apr 2016 00:43:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qqmail.nl; s=google; h=message-id:mime-version:to:from:subject:date:importance:in-reply-to :references; bh=H1dG4hPokvqB3rSXjO5Qaov0bt42IOFauD8Tw9L4p0M=; b=aKZt1iiAoOEdUyl2M6vy2/oFFLAegZAmjgq9OfTsHFOLdsrp34TvzHU0hXzIGT0Xtu Y6PxXV9+8Fvm3qrZK1cRxT00EY8TdNx5wURp+Kq5cYZPbALTU4G976Wd/Z8q4iXDz5+F i5ACd09NUK982UT38m04FnemS8GHJv+nEdphY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:mime-version:to:from:subject:date :importance:in-reply-to:references; bh=H1dG4hPokvqB3rSXjO5Qaov0bt42IOFauD8Tw9L4p0M=; b=f22CArCGUFX4sSk48pShbUURccD1bkO3Q+M9aOjXRGAuwkQgN+WmD6at8STcHIGKxc zCDmtRooOnvQ9qhamOhF9fGkofEB8qj+I1HkQly18qS3i3YKfbxqJdRqCfOdsdvSkA3u tMoIisGfHrJRXE6WvZmmavyGFCKRCtbMvkoFtM3KA+A9iA8gFFAZ1VHPlgE8PGfyJM7s lNeCAKJ8mFD0bo4k+KRu6QOkDjNIyK8oMcPCp3P4WUBN/vbQSxB+JsZC9Cem1Mf7ov6g nDwxZu4DeEWQ6ruTVAI4IfPfyELJkozXT5LC3eVtjeiMBaYH0PhgAbUpYADpHrGZrfzH zJDw== X-Gm-Message-State: AOPr4FWApdgqKYNN5UwKSdTcB7+aJOI8t8Fjn1QwjoAqvSfo5yBvEH18WROxY3Ddf4qSfg== X-Received: by 10.194.14.6 with SMTP id l6mr29558466wjc.48.1462002184599; Sat, 30 Apr 2016 00:43:04 -0700 (PDT) Received: from ?IPv6:2001:610:66e:0:55cf:2ae4:bfd:99ac? ([2001:610:66e:0:55cf:2ae4:bfd:99ac]) by smtp.gmail.com with ESMTPSA id c85sm6861784wmd.0.2016.04.30.00.43.03 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 30 Apr 2016 00:43:03 -0700 (PDT) Message-ID: <57246207.58811c0a.83f4b.477a@mx.google.com> MIME-Version: 1.0 To: Daniel Shahaf , "dev@subversion.apache.org" From: Bert Huijben Subject: RE: [PATCH/RFC] use-sasl=true in --without-sasl builds: make that a fatalerror? Date: Sat, 30 Apr 2016 09:43:02 +0200 Importance: normal X-Priority: 3 In-Reply-To: <20160430005350.GA23087@tarsus.local2> References: <20160430005350.GA23087@tarsus.local2> Content-Type: multipart/alternative; boundary="_11791DCF-C504-46A5-AA0D-A8D42CF3C43D_" --_11791DCF-C504-46A5-AA0D-A8D42CF3C43D_ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Isn=E2=80=99t this a documented default value? If it is, changing the behavior will likely break many users that don=E2=80= =99t use sasl. Bert Sent from my Windows 10 phone From: Daniel Shahaf Sent: zaterdag 30 april 2016 02:53 To: dev@subversion.apache.org Subject: [PATCH/RFC] use-sasl=3Dtrue in --without-sasl builds: make that a = fatalerror? Currently, if use-sasl=3Dtrue is set in svnserve.conf but svnserve was compiled without SASL support, SASL is silently not used. That's actually documented: svnserve.conf: [sasl] ### This option specifies whether you want to use the Cyrus SASL ### library for authentication. Default is false. ### This section will be ignored if svnserve is not built with Cyrus ### SASL support; to check, run 'svnserve --version' and look for a lin= e ### reading 'Cyrus SASL authentication is available.' # use-sasl =3D true But documentation notwithstanding, it seems like a misfeature. Should we change this, so --without-sasl builds will error out if use-sasl=3Dtrue is set? The patch would be simple enough (attached). Cheers, Daniel P.S. The 'password-db' setting is in the same boat: it's ignored when SASL is enabled, and documented this way. However, I'm not convinced a change to that setting's handling is needed. --_11791DCF-C504-46A5-AA0D-A8D42CF3C43D_ Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

Isn=E2=80=99t this = a documented default value?

=  

If it is, changing = the behavior will likely break many users that don=E2=80=99t use sasl.=

 <= /span>

Bert

 

Sent from m= y Windows 10 phone

 

From: Daniel Shahaf=
Sent: zaterdag 30 april 2016 02:53
To: dev@subversion.apache.org
Subje= ct: [PATCH/RFC] use-sasl=3Dtrue in --without-sasl builds: make that a f= atalerror?

 

Currently, if use-sasl=3Dtrue is set in svnserve.conf but svnserve= was

compiled without SASL support, SASL is silentl= y not used.=C2=A0 That's

actually documented:

 

=C2=A0 svnserv= e.conf:

=C2=A0=C2=A0=C2=A0 [sasl]

=C2=A0=C2=A0=C2=A0 ### This option specifies whether you want to use= the Cyrus SASL

=C2=A0=C2=A0=C2=A0 ### library for = authentication. Default is false.

=C2=A0=C2=A0=C2= =A0 ### This section will be ignored if svnserve is not built with Cyrus

=C2=A0=C2=A0=C2=A0 ### SASL support; to check, run 's= vnserve --version' and look for a line

=C2=A0=C2=A0= =C2=A0 ### reading 'Cyrus SASL authentication is available.'

=C2=A0=C2=A0=C2=A0 # use-sasl =3D true

 

But documentation notwithstanding, = it seems like a misfeature.=C2=A0 Should

we change = this, so --without-sasl builds will error out if use-sasl=3Dtrue

is set?=C2=A0 The patch would be simple enough (attached).

 

Cheers,

=

 

Daniel

 

P.S. The 'pass= word-db' setting is in the same boat: it's ignored

= when SASL is enabled, and documented this way.=C2=A0 However, I'm not

convinced a change to that setting's handling is needed.=

 

&nb= sp;

= --_11791DCF-C504-46A5-AA0D-A8D42CF3C43D_--