Learn more about these different git repos.
Other Git URLs
Kerberos allows the autodiscovery of realm via setting the krb5.conf option dns_lookup_realm. We should have a similar option in SSSD.
dns_lookup_realm
Fields changed
component: SSSD => Kerberos Provider milestone: NEEDS_TRIAGE => SSSD 1.3.0
We have decided that this feature is potentially dangerous as it allows the client to be presented with arbitrary realm with spoofed DNS replies. We will defer it until it is requested. In the mean time, the WIP code is in my personal git repository on fedorapeople, so we can always resume from there.
milestone: SSSD 1.3.0 => SSSD Deferred
This would be a useful feature for me - do the security concerns also exist when using the krb5.conf option?
coverity: => patch: => 0 upgrade: => 0
milestone: SSSD Deferred => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => SSSD 1.7.0
cc: => tmraz
milestone: SSSD 1.8.0 => SSSD 1.7.0
rhbz: => summary: autodiscover Kerberos domain through TXT records => [RFE] autodiscover Kerberos domain through TXT records
milestone: SSSD 1.7.0 => SSSD 1.9.0
blockedby: => blocking: => milestone: SSSD 1.9.0 => SSSD Kerberos improvements
rhbz: => 0
Replying to [comment:3 danieljamesscott]:
According to nalin kerberos libraries are smart enough to negotiate the right ticket securely using cross realm referrals without relying on the TXT records.
It might not make sense to add this functionality ever. Putting in Differed for now.
feature_milestone: => milestone: SSSD Kerberos Improvements Feature => SSSD Deferred proposed_priority: => Undefined
Metadata Update from @jhrozek: - Issue assigned to jhrozek - Issue set to the milestone: SSSD Patches welcome
Metadata Update from @jhrozek: - Assignee reset
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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/1523
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.