[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)

[Rafael David Tinoco]

It seems that bionic is also affected:

(c)rafaeldtinoco at groovy:~$ rmadison memcached
...
 memcached | 1.5.6-0ubuntu1          | bionic           |
 memcached | 1.5.6-0ubuntu1.2        | bionic-security  |
 memcached | 1.5.6-0ubuntu1.2        | bionic-updates   |
 memcached | 1.5.10-0ubuntu1         | disco            |
 memcached | 1.5.10-0ubuntu1.19.04.2 | disco-security   |
 memcached | 1.5.10-0ubuntu1.19.04.2 | disco-updates    |
 memcached | 1.5.10-0ubuntu3         | eoan             |
 memcached | 1.5.22-2                | focal            |
 memcached | 1.6.6-1                 | groovy           |

subscribed @sergiodj to check everything out.

thx!

** Tags added: block-proposed-eoan block-proposed-focal block-proposed-
groovy

** Changed in: memcached (Ubuntu)
     Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

** Also affects: memcached (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Changed in: memcached (Ubuntu Bionic)
       Status: New => Triaged

** Changed in: memcached (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: memcached (Ubuntu Bionic)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
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)

Status in memcached package in Ubuntu:
  Fix Released
Status in memcached source package in Bionic:
  Triaged
Status in memcached source package in Eoan:
  Triaged
Status in memcached source package in Focal:
  Confirmed

Bug description:
  [Impact]

  memcached 1.5.22 in focal has a bug where it looks for its SASL
  configuration at /etc/sasl2/memcached.conf/memcached.conf instead of
  /etc/sasl2/memcached.conf.  This causes a memcached setup with
  authentication that was working in bionic to fail in focal.

  The bug was introduced upstream in 1.5.7~3:
  https://github.com/memcached/memcached/commit/39151c870c5e598f039714bdb790bd46f614856e
  https://github.com/memcached/memcached/pull/366
  and fixed upstream in 1.6.0~15:
  https://github.com/memcached/memcached/commit/6207330c2705fdb5f02de13b99a0d994f7c4f14a

  [Test Case]

  apt-get install memcached libmemcached-tools libsasl2-modules sasl2-bin
  mkdir /etc/sasl2
  echo 'mech_list: plain' > /etc/sasl2/memcached.conf
  echo 'sasldb_path: /etc/sasl2/memcached-sasldb2' >> /etc/sasl2/memcached.conf
  echo bar | saslpasswd2 -p -f /etc/sasl2/memcached-sasldb2 -a memcached foo
  chown memcache: /etc/sasl2/memcached-sasldb2
  systemctl restart memcached
  memcping --servers=127.0.0.1 --binary --username=foo --password=bar

  Works in bionic; fails in focal with “Failed to ping 127.0.0.1:11211
  WRITE FAILURE”.

  [Regression Potential]

  Low risk.  The upstream patch is targeted and applies cleanly to
  1.5.22.  It looks for the SASL configuration at both locations, so if
  someone worked around this bug by creating
  /etc/sasl2/memcached.conf/memcached.conf, that will continue to be
  respected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+subscriptions