This bug was fixed in the package cyrus-sasl2 - 2.1.26.dfsg1-14ubuntu0.1
---
cyrus-sasl2 (2.1.26.dfsg1-14ubuntu0.1) xenial; urgency=medium
* d/p/dont_hang_when_imap_closes.patch: Don't hang when IMAP
server closes connection. (LP: #997217)
-- Andreas Hasenack Wed, 24 Oct
xenial verification
Confirming bug:
ubuntu@xenial-saslauthd:~$ apt-cache policy sasl2-bin
sasl2-bin:
Installed: 2.1.26.dfsg1-14build1
Candidate: 2.1.26.dfsg1-14build1
Version table:
*** 2.1.26.dfsg1-14build1 500
500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Roberto, are you able to test this update? If not, I can do it, but it
would be better if someone not involved with the fix could do it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
Hello David, or anyone else affected,
Accepted cyrus-sasl2 into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cyrus-
sasl2/2.1.26.dfsg1-14ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Description changed:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This condition
can be easily encountered when an authentication is happening and the
imap service is being restarted.
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/cyrus-sasl2/+git/cyrus-sasl2/+merge/357779
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
** Description changed:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This condition
can be easily encountered when an authentication is happening and the
imap service is being restarted.
Ok, trusty isn't affected because the loop there has an exit clause:
+ ret = read(s, rbuf+rc, sizeof(rbuf)-rc);
+ if ( ret<0 ) {
+ rc = ret;
+ break;
+ } else {
+ if (ret == 0) {
+ loopc += 1;
I'm unable to trigger this bug when running the test case on trusty,
even though the same code is there. I also tried adjusting the sleep.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
** Description changed:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This condition
can be easily encountered when an authentication is happening and the
imap service is being restarted.
-
-
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ The rimap authentication mechanism in saslauthd can hit a condition
+ where it will start spinning and using all available CPU. This condition
+ can be easily encountered when an authentication is
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test
** Changed in: cyrus-sasl2 (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: cyrus-sasl2 (Ubuntu Xenial)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: cyrus-sasl2 (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: cyrus-sasl2 (Ubuntu
I reproduced the problem in xenial by timing a "testsaslauthd" call with
a "service dovecot stop" one (dovecot being my test imap server on
localhost).
This is good enough for an SRU test case, thanks all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Trusty has 0034-fix_dovecot_authentication.patch, but it lacks the above
fix as well.
** Also affects: cyrus-sasl2 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Tags removed: precise
** Tags added: server-next
** Changed in: cyrus-sasl2 (Ubuntu Trusty)
Status: New =>
The patch 0034 mentioned in comment #10 is applied in the xenial package
2.1.26.dfsg1-14build1, so what Roberto hit could be a different issue
requiring a different fix.
Might have been this:
cyrus-sasl2 (2.1.26.dfsg1-15) unstable; urgency=medium
* Add fix for auth_rimap infinite loop (hang)
I reply to myself: while the version in Xenial is *still* affected with
this bug, any of the later versions is fixed. The version
2.1.26.dfsg1-14 is bugged, but the next one, 2.1.26.dfsg1-15 is not. I
backported the one in Bionic easily and it's working now without
problems.
--
You received this
I'm seeing this exact same problem with saslauthd in sasl2-bin
2.1.26.dfsg1-14, using Ubuntu 16.04.4. Is there any other possible
cause?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
18 matches
Mail list logo
