Trusty has reached its end of standard support.
** Changed in: krb5 (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1817955
Is the fix released in Trustu ESM repository ? I don't see it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1817955
Title:
Getting new "DN is out of the realm subtree"
** Also affects: krb5 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: krb5 (Ubuntu Trusty)
Status: New => Triaged
** Changed in: krb5 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: krb5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
Even explicitly added subtree doesn't work:
# kdb5_ldap_util -D "cn=admin,dc=example,dc=com" -H
ldap://ldapserver.example.com modify -r TEST.EXAMPLE.COM -subtrees
'dc=example,dc=com:ou=People,dc=example,dc=com"
# kdb5_ldap_util -D "cn=admin,dc=example,dc=com" -H
ldap://ldapserver.example.com
Same error after upgrading krb5 packages from 1.12+dfsg-2ubuntu5.3 to
1.12+dfsg-2ubuntu5.4.
Adding a principal in a subtree outside the realm container fails.
Realm container DN is
"cn=TEST.EXAMPLE.COM,cn=krbContainer,dc=example,dc=com"
But realm has subtree "dc=example,dc=com", with scope =
I do not think so, but I may not fully understand what "subtree"
implies.
The realm was initially created with a command equivalent to:
kdb5_ldap_util -D cn=admin,dc=example,dc=com create -subtrees
dc=example,dc=com -r TEST.EXAMPLE.COM -s -H
ldap://ldapserver.example.com
with user entries like:
7 matches
Mail list logo
