** Changed in: cyrus-sasl2 (Ubuntu Cosmic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015819
Title:
sb_sasl_generic_pkt_length: received illegal packet
I need to add an important note here:
Even this bug is marked as fixed, the change in Cyrus SASL now breaks RFC 4752.
See my comment:
https://github.com/cyrusimap/cyrus-sasl/issues/419#issuecomment-566981689
Technically, one would now need to create an issue in Launchpad that
Cyrus SASL GSSAPI
** Changed in: cyrus-sasl2
Status: Unknown => 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/1015819
Title:
sb_sasl_generic_pkt_length: received illegal packet length when using
Given the upstream bug status and version where it was fixed, we believe
this is fixed in the upcoming Ubuntu Disco release:
cyrus-sasl2 | 2.1.27+dfsg-1 | disco |
source
It will therefore be marked as "fix released", but I will open a task for
bionic and cosmic.
Given the upstream bug status and version where it was fixed, we believe
this is fixed in the upcoming Ubuntu Disco release:
cyrus-sasl2 | 2.1.27+dfsg-1 | disco |
source
It will therefore be marked as "fix released", but I will open a task for
bionic and cosmic.
Upstream bug: https://github.com/cyrusimap/cyrus-sasl/issues/419
** Bug watch added: github.com/cyrusimap/cyrus-sasl/issues #419
https://github.com/cyrusimap/cyrus-sasl/issues/419
** Also affects: cyrus-sasl2 via
https://github.com/cyrusimap/cyrus-sasl/issues/419
Importance: Unknown
Upstream bug: https://github.com/cyrusimap/cyrus-sasl/issues/419
** Bug watch added: github.com/cyrusimap/cyrus-sasl/issues #419
https://github.com/cyrusimap/cyrus-sasl/issues/419
** Also affects: cyrus-sasl2 via
https://github.com/cyrusimap/cyrus-sasl/issues/419
Importance: Unknown
Thank you, Johnny Westerlund!
At least adding "sasl_secprops minssf=0,maxssf=0" to /etc/openldap/ldap.conf
works around the error, so things seem to work for me.
Not sure whether it is different now for Michael Osipov.
--
You received this bug notification because you are a member of Ubuntu
Exact same error here in 2019.
I set Windows Server 2019 up, default AD DS & AD CS (for TLS).
Clients tried:
Ubuntu 18.04: libsasl2-modules-gssapi-mit:amd64
2.1.27~101-g0780600+dfsg-3ubuntu2
Alpine Edge: cyrus-sasl-gssapiv2-2.1.27-r1
Have anyone tried asking in Cyrus SASL mailing list?
Just hit the same problem while debugging bug #1576799
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1015819
Title:
sb_sasl_generic_pkt_length: received illegal packet length
Just hit the same problem while debugging bug #1576799
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015819
Title:
sb_sasl_generic_pkt_length: received illegal packet length when using
Active
11 matches
Mail list logo