This bug was fixed in the package memcached - 1.5.10-0ubuntu3.1
---------------
memcached (1.5.10-0ubuntu3.1) eoan; urgency=medium
* d/p/fix-bug-where-sasl-will-load-config-the-wrong-path.patch:
Fix the path from which SASL configuration is loaded. (LP: #1878721)
The bug happened because sasl expects memcached to provide a
path (i.e., a directory, not a filename) where the sasl
configuration file(s) is (are). However, memcached was passing
the filename (/etc/sasl2/memcached.conf) to sasl, which was
interpreting it as a directory, and looking for a configuration
file inside it (i.e., /etc/sasl2/memcached.conf/memcached.conf).
Users could workaround this bug by creating a directory named
/etc/sasl2/memcached.conf/, and putting the configuration file
inside it. This patch not only fixes this bug (by passing the
right directory, /etc/sasl2/, to sasl) but also supports the
workaround described above.
-- Anders Kaseorg <ande...@mit.edu> Thu, 14 May 2020 17:13:17 -0700
** Changed in: memcached (Ubuntu Eoan)
Status: Fix Committed => Fix Released
** Changed in: memcached (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878721
Title:
memcached looks for SASL configuration at wrong path
/etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
