[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
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 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
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 Thu, 14 May 2020 17:13:17 -0700 -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
eoan verification: First, reproducing the problem: memcached: Installed: 1.5.10-0ubuntu3 Candidate: 1.5.10-0ubuntu3 Version table: *** 1.5.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Command fails: # memcping --servers=127.0.0.1 --binary --username=foo --password=bar Failed to ping 127.0.0.1:11211 WRITE FAILURE With the updated package from proposed: memcached: Installed: 1.5.10-0ubuntu3.1 Candidate: 1.5.10-0ubuntu3.1 Version table: *** 1.5.10-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu eoan-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.5.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages The command succeeds: # memcping --servers=127.0.0.1 --binary --username=foo --password=bar # echo $? 0 eoan verification succeeded. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Hello Anders, or anyone else affected, Accepted memcached into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/memcached/1.5.10-0ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: memcached (Ubuntu Eoan) Status: Triaged => Fix Committed ** Tags added: verification-needed-eoan -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
This bug was fixed in the package memcached - 1.5.22-2ubuntu0.1 --- memcached (1.5.22-2ubuntu0.1) focal; 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 Thu, 14 May 2020 17:13:17 -0700 ** Changed in: memcached (Ubuntu Focal) 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
I assume Rafael added block-proposed mistakenly; there is no staged upload involved. -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Tags removed: block-proposed-eoan block-proposed-focal block- proposed-groovy -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Verified that 1.5.22-2ubuntu0.1 works on focal with the config file in all four locations. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
why is this bug marked block-proposed? -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Hello Anders, or anyone else affected, Accepted memcached into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/memcached/1.5.22-2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: memcached (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Description changed: [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/commit/80dd99d831535ddeec73d55a0adcaeaac8cb7298 https://github.com/memcached/memcached/pull/366 + and fixed upstream in 1.6.0~15: + https://github.com/memcached/memcached/commit/6207330c2705fdb5f02de13b99a0d994f7c4f14a + + The reason this bug happens is because sasl works with paths (i.e., + directories) when determining which configuration files it should load, + whereas, after the two commits mentioned above (version 1.5.7~3), + memcached started to pass a full pathname (including the filename) of + the configuration file. + + So, while in a "normal" setup memcached's configuration file would live + at /etc/sasl2/memcached.conf, meaning that memcached would tell sasl + that the config path is "/etc/sasl2/", with the buggy memcached sasl + would think that the configuration directory is + "/etc/sasl2/memcached.conf/", and would try to look for a + "memcached.conf" file inside it. + + Users could workaroud this bug by creating a directory named + "/etc/sasl2/memcached.conf/". For this reason, the backported patch + also takes this workaround into account. The patch also accepts the + "/etc/sasl/" directory. [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 - echo '-S' >> /etc/memcached.conf - systemctl restart memcached - memcping --servers=127.0.0.1 --binary --username=foo --password=bar + To test the fix, one can do: - Succeeds in bionic (with no output); fails in focal with “Failed to ping - 127.0.0.1:11211 UNKNOWN READ FAILURE” or “Failed to ping 127.0.0.1:11211 - WRITE FAILURE”; should succeed with the patch. + $ lxc launch ubuntu-daily:focal memcached-bug1878721 + $ lxc shell memcached-bug1878721 + # apt update && apt upgrade -y + # apt install -y memcached libmemcached-tools libsasl2-modules sasl2-bin + # mkdir -p /etc/sasl2 + # cat > /etc/sasl2/memcached.conf << __EOF__ + mech_list: plain + sasldb_path: /etc/sasl2/memcached-sasldb2 + __EOF__ + # echo bar | saslpasswd2 -p -f /etc/sasl2/memcached-sasldb2 -a memcached foo + # chown memcache: /etc/sasl2/memcached-sasldb2 + # echo '-S' >> /etc/memcached.conf + # systemctl restart memcached.service + # memcping --servers=127.0.0.1 --binary --username=foo --password=bar - If you want to test alternate locations for the SASL config file, here - are all four locations that will now work by default: + With the last command, you should see an error like: - • /etc/sasl/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should succeed with the patch - • /etc/sasl/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch - • /etc/sasl2/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should succeed with the patch - • /etc/sasl2/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch + Failed to ping 127.0.0.1:11211 WRITE FAILURE + + or: + + Failed to ping 127.0.0.1:11211 READ FAILURE + + You can also check its exit status: + + # echo $? + 1 + + It is possible to test the workaround workaround mentioned in the + previous section by doing: + + # mv /etc/sasl2/memcached.conf /tmp/ + # mkdir /etc/sasl2/memcached.conf + # mv /tmp/memcached.conf /etc/sasl2/memcached.conf/ + # systemctl restart memcached.service + # memcping --servers=127.0.0.1 --binary --username=foo --password=bar + # echo $? + 0 + + Using the fix provided, one can verify that both tests above will work. + + Here are all four locations that will now work by default: + + • /etc/sasl/memcached.conf/memcached.conf + • /etc/sasl/memcached.conf + • /etc/sasl2/memcached.conf/memcached.conf + • /etc/sasl2/memcached.conf [Regression Potential] Low risk. The upstream patch is targeted and applies cleanly to 1.5.22. It looks for the SASL configuration at both the incorrect and correct paths, so even in the (unlikely) event that someone worked around this bug by manually creating a configuration file at the incorrect path /etc/sasl2/memcached.conf/memcached.conf, that will continue to be respected. If there were to be a regression, it would likely manifest as an authentication failure, which clients may display as a read or write failure,
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Description changed: [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 + echo '-S' >> /etc/memcached.conf systemctl restart memcached memcping --servers=127.0.0.1 --binary --username=foo --password=bar Succeeds in bionic (with no output); fails in focal with “Failed to ping 127.0.0.1:11211 UNKNOWN READ FAILURE” or “Failed to ping 127.0.0.1:11211 WRITE FAILURE”; should succeed with the patch. If you want to test alternate locations for the SASL config file, here are all four locations that will now work by default: • /etc/sasl/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should succeed with the patch • /etc/sasl/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch • /etc/sasl2/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should work with the patch • /etc/sasl2/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch [Regression Potential] Low risk. The upstream patch is targeted and applies cleanly to 1.5.22. It looks for the SASL configuration at both the incorrect and correct paths, so even in the (unlikely) event that someone worked around this bug by manually creating a configuration file at the incorrect path /etc/sasl2/memcached.conf/memcached.conf, that will continue to be respected. If there were to be a regression, it would likely manifest as an authentication failure, which clients may display as a read or write failure, like the failure mode of the regression being fixed here. ** Description changed: [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 echo '-S' >> /etc/memcached.conf systemctl restart memcached memcping --servers=127.0.0.1 --binary --username=foo --password=bar Succeeds in bionic (with no output); fails in focal with “Failed to ping 127.0.0.1:11211 UNKNOWN READ FAILURE” or “Failed to ping 127.0.0.1:11211 WRITE FAILURE”; should succeed with the patch. If you want to test alternate locations for the SASL config file, here are all four locations that will now work by default: • /etc/sasl/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should succeed with the patch • /etc/sasl/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch - • /etc/sasl2/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should work with the patch + • /etc/sasl2/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should succeed with the patch • /etc/sasl2/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch [Regression Potential] Low risk. The upstream patch is targeted and applies cleanly to 1.5.22. It looks for the SASL configuration at both the incorrect and correct paths, so even in the (unlikely) event that someone worked around this bug by manually creating a configuration file at the incorrect path /etc/sasl2/memcached.conf/memcached.conf, that will continue to be respected. If there were to be a regression, it would
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Description changed: [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 - echo '-S' >> /etc/memcached.conf 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”. + Succeeds in bionic (with no output); fails in focal with “Failed to ping + 127.0.0.1:11211 UNKNOWN READ FAILURE” or “Failed to ping 127.0.0.1:11211 + WRITE FAILURE”; should succeed with the patch. + + If you want to test alternate locations for the SASL config file, here + are all four locations that will now work by default: + + • /etc/sasl/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should succeed with the patch + • /etc/sasl/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch + • /etc/sasl2/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should work with the patch + • /etc/sasl2/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch [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 + It looks for the SASL configuration at both the incorrect and correct + paths, so even in the (unlikely) event that someone worked around this + bug by manually creating a configuration file at the incorrect path /etc/sasl2/memcached.conf/memcached.conf, that will continue to be respected. + + If there were to be a regression, it would likely manifest as an + authentication failure, which clients may display as a read or write + failure, like the failure mode of the regression being fixed here. -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Description changed: [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 + echo '-S' >> /etc/memcached.conf 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. -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/memcached/+git/memcached/+merge/384764 ** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/memcached/+git/memcached/+merge/384765 -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** No longer affects: memcached (Ubuntu Bionic) -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Rafael: I said that bionic is *not* affected, both because bionic has 1.5.6 while the bug was introduced in 1.5.7, and because the test case passes on bionic. What makes you think otherwise? -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
It seems that bionic is also affected: (c)rafaeldtinoco@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 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Also affects: memcached (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: memcached (Ubuntu Eoan) Status: New => Triaged -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Thanks for reporting this bug and also the provided patch. ** Tags added: server-next ** Changed in: memcached (Ubuntu) Importance: Undecided => High ** Also affects: memcached (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: memcached (Ubuntu Focal) Status: New => Confirmed ** Changed in: memcached (Ubuntu Focal) Importance: Undecided => High ** Changed in: memcached (Ubuntu) Status: Confirmed => 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: memcached (Ubuntu) Status: New => Confirmed -- 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
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Here’s a debdiff with the upstream patch. I built this in https://launchpad.net/~andersk/+archive/ubuntu/ppa and verified it against the test case. ** Patch added: "memcached_1.5.22-2_lp1878721.debdiff" https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+attachment/5371790/+files/memcached_1.5.22-2_lp1878721.debdiff ** Tags added: patch -- 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
