Learn more about these different git repos.
Other Git URLs
Currently we just put a plain IPv6 address in the kdc info file and add a port to the address separated by a : . The locator plugin takes case that address and port are split in the right way, but it might be useful and more accordind to standards to put the address in brackets e.g.{{{[::1]:749}}}.
Fields changed
description: Currently we just put a plain IPv6 address in the kdc info file and add a port to the address separated by a : . The locator plugin takes case that address and port are split in the right way, but it might be useful and more accordind to standards to put the address in brackets [...]. => Currently we just put a plain IPv6 address in the kdc info file and add a port to the address separated by a : . The locator plugin takes case that address and port are split in the right way, but it might be useful and more accordind to standards to put the address in brackets e.g.{{{[::1]:749}}}.
Without brakets the syntax is ambiguous and you cannot know if the last element is a port or part of the address. This should be fixed asap because it is otherwise technically 'broken'.
milestone: NEEDS_TRIAGE => SSSD 1.5.9
milestone: SSSD 1.5.9 => SSSD 1.6.0
owner: somebody => jhrozek
patch: 0 => 1 status: new => assigned
master: 97c9385
resolution: => fixed status: assigned => closed
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=785896
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=785896 785896]
Metadata Update from @sbose: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.6.0
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1951
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.