* 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 <email address hidden> Thu, 14 May 2020 17:13:17 -0700
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: memcached. conf) to sasl, which was memcached. conf/memcached. conf). sasl2/memcached .conf/, and putting the configuration file
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/
interpreting it as a directory, and looking for a configuration
file inside it (i.e., /etc/sasl2/
Users could workaround this bug by creating a directory named
/etc/
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 <email address hidden> Thu, 14 May 2020 17:13:17 -0700