** Changed in: cyrus-sasl2 (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/1188475
Title:
ldap group doesn't work
To manage notifications about this
** Tags removed: bitesize
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
To manage notifications about this bug go to:
** Tags removed: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
To manage notifications about this bug go to:
** Tags removed: server-next server-next-drop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
To manage notifications about this bug go to:
** Tags added: server-next-drop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
To manage notifications about this bug go to:
About comment 6- in my opinion this highly depends on your implementation and
policy.
I work for not so large company, I'd say small - just about 4200 employers-, so
our policy can be wrong - it says not show users their rights, i.e. intruder
needs to try ;-)
>From another point of view- ldap
Hello!
I'm not Debian user, so I don't think this is good idea to open bug report for
product I don't use.
And I don't see any reasons why Ubuntu can't provide support for it's packages
and have to rely on Debian :-(
Anyway, fix will be in next release, so it will work out of box in 20.04
:-D
Hi @sles,
I marked this bug as invalid because there was no answer to my question
in comment #6 for close to two months, and launchpad wouldn't set this
bug to expired. Also when I checked, upstream hadn't commented on your
github issue.
I still don't understand fully why the original behaviour
Hi @sles,
I marked this bug as invalid because there was no answer to my question
in comment #6 for close to two months, and launchpad wouldn't set this
bug to expired. Also when I checked, upstream hadn't commented on your
github issue.
I still don't understand fully why the original behaviour
** 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/1188475
Title:
ldap group doesn't work
To manage notifications about this bug go to:
Thanks sles for driving that upstream!
FYI - Merged 19 hours ago so not in any release (yet).
Now we are back to Josh's comment #3 to file it in Debian to sync to Artful
from there.
If you do open a report the please mention it here so we can link it up to get
auto-notified once it is
** Also affects: cyrus-sasl2 via
https://github.com/cyrusimap/cyrus-sasl/issues/427
Importance: Unknown
Status: Unknown
** Tags removed: needs-upstream-report
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Why invalid?
Please get into ubuntu current code :-)
https://github.com/cyrusimap/cyrus-sasl/pull/428
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For some reason bug expiration isn't working for this bug. Given that
there were no updates for over two months, I'm marking it as invalid.
Feel free to reopen it if you have more information about the problem.
Thanks!
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Incomplete => Invalid
For some reason bug expiration isn't working for this bug. Given that
there were no updates for over two months, I'm marking it as invalid.
Feel free to reopen it if you have more information about the problem.
Thanks!
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Incomplete => Invalid
Can you share your saslauthd configuration, and portions of your DIT
showing how the users and groups are organised?
At first glance, it feels correct to be using the user's DN to check for
group membership. I would certainly expect to be able to tell which
groups I belong to without having to
Can you share your saslauthd configuration, and portions of your DIT
showing how the users and groups are organised?
At first glance, it feels correct to be using the user's DN to check for
group membership. I would certainly expect to be able to tell which
groups I belong to without having to
User filed upstream bug at https://github.com/cyrusimap/cyrus-
sasl/issues/427
** Bug watch added: github.com/cyrusimap/cyrus-sasl/issues #427
https://github.com/cyrusimap/cyrus-sasl/issues/427
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
User filed upstream bug at https://github.com/cyrusimap/cyrus-
sasl/issues/427
** Bug watch added: github.com/cyrusimap/cyrus-sasl/issues #427
https://github.com/cyrusimap/cyrus-sasl/issues/427
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hello!
I created pull request in cyrus sasl repository
https://github.com/cyrusimap/cyrus-sasl/pull/428
If you don't patch debian packages, then why debian should do this,
let cyrus developers fix it ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Sorry this got dropped over the years.
This bug is present in Debian as well and Ubuntu currently does not make any
changes to the Debian package. Therefore, this bug would be best fixed
directly in Debian, and
Hello!
Still have this bug on 16.04.
Have to use my old patch, because there is the same bug...
Why???!!!
:-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
btw, more correct patch, which revert back bind from config in
lak_auth_bind
diff -ur lak.c.orig lak.c
--- lak.c.orig2013-06-07 09:15:20.098788278 +0400
+++ lak.c2013-06-08 10:17:07.548233104 +0400
@@ -1448,8 +1448,25 @@
if ( rc == LAK_OK
(ISSET(lak-conf-group_dn) ||
btw, more correct patch, which revert back bind from config in
lak_auth_bind
diff -ur lak.c.orig lak.c
--- lak.c.orig2013-06-07 09:15:20.098788278 +0400
+++ lak.c2013-06-08 10:17:07.548233104 +0400
@@ -1448,8 +1448,25 @@
if ( rc == LAK_OK
(ISSET(lak-conf-group_dn) ||
** Changed in: cyrus-sasl2 (Ubuntu)
Importance: Undecided = Medium
--
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/1188475
Title:
ldap group doesn't work
To manage
** Changed in: cyrus-sasl2 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1188475
Title:
ldap group doesn't work
To manage notifications about this bug go
26 matches
Mail list logo
