qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Hendley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-1834) Misconfiguration of config path for Debian libsasl2-2 (SASL support)
Date Thu, 21 Jul 2011 19:00:59 GMT

    [ https://issues.apache.org/jira/browse/QPID-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069136#comment-13069136
] 

Sam Hendley commented on QPID-1834:
-----------------------------------

I just tried this on ubunutu and it doesn't seem to have any affect. I see the log message
in the qpidd logs:

info SASL: config path set to /etc/sasl2/qpidd.conf

But when I try connecting it is still looking at /etc/sasldb2.  I verified this by adding
different users to /etc/sasldb2 and /var/lib/qpidd/qpidd.sasldb and attempting to log in with
both, the ones listed in /etc/sasldb2 worked.

I built qpidd using the PPA package on launchpad. This is not a blocker for me, I can just
use default sasldb2 location, but the sasl-config option doesn't appear to do the job fully.

 

> Misconfiguration of config path for Debian libsasl2-2 (SASL support)
> --------------------------------------------------------------------
>
>                 Key: QPID-1834
>                 URL: https://issues.apache.org/jira/browse/QPID-1834
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>    Affects Versions: M4
>         Environment: Debian "squeeze"
>            Reporter: Garrett Smith
>
> The libsasl2-2 package is configured with the option:
>   --with-configdir=/etc/sasl:/usr/lib/sasl2
> Background on this decision can be found here:
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211156
> cpp/etc/Makefile.in specifies SASL_CONF as /etc/sasl2, which isn't on the config path
that the Debian package is compiled with. The result is that the qpid sasl configuration is
never used. This is a pain to debug as the missed configuration is silently ignored.
> I'm not sure what the ideal solution is here, but I think this ought to be addressed
given we're talking about Debian.
> A config option for qpidd would probably be appropriate, or, in keeping with the hard
coding strategy, create a link from /etc/sasl to /etc/sasl2. Just a couple ideas though.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message