[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [PATCH/RFC] use-sasl=true in --without-sasl builds: make that a fatalerror?

From: Bert Huijben <bert_at_qqmail.nl>
Date: Sat, 30 Apr 2016 09:43:02 +0200

Isn’t this a documented default value?

If it is, changing the behavior will likely break many users that don’t use sasl.


Sent from my Windows 10 phone

From: Daniel Shahaf
Sent: zaterdag 30 april 2016 02:53
To: dev_at_subversion.apache.org
Subject: [PATCH/RFC] use-sasl=true in --without-sasl builds: make that a fatalerror?

Currently, if use-sasl=true is set in svnserve.conf but svnserve was
compiled without SASL support, SASL is silently not used. That's
actually documented:

    ### 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 line
    ### reading 'Cyrus SASL authentication is available.'
    # use-sasl = true

But documentation notwithstanding, it seems like a misfeature. Should
we change this, so --without-sasl builds will error out if use-sasl=true
is set? The patch would be simple enough (attached).



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.
Received on 2016-04-30 09:43:12 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.