Bug 201976
Summary: | Applications using kerberos authentication segfault | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rob Riggs <rob+redhat> |
Component: | krb5 | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | triage |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://krbdev.mit.edu/rt/Ticket/Display.html?id=3313 | ||
Whiteboard: | bzcl34nup | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-06 16:13:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rob Riggs
2006-08-10 05:43:10 UTC
I'm having trouble reproducing this. Fresh i386 FC5 install with all updates applied (this takes it to 1.4.3-5.1, as you have). I run kinit, and then point curl at a page on my domain controller, which is in a different realm than I am, and have the [domain_realm] mapping set up in /etc/krb5.conf so that the library will assume it's in my local realm. When I try this, I see the "Server not found in Kerberos database" error come back from the server, and the client spews out the authorization failure text which the server sent it. Is there something I'm missing in the setup here? First, both the patch at http://krbdev.mit.edu/rt/Ticket/Display.html?id=3313 and krb5-1.5-3 from fc6t2 fix the double-free problem. This has allowed me to track down what appear to be the key features of the problem. This problem manifests itself when the server to which the request is made maps to a secondary realm whose domain name does not directly map to that realm. (There is at least one other case. The same seems to occur when the domain does not have a mapping to a valid realm.) 1. krb5.conf has a [domain_realm] section with a "domain2.name = REALM2.NAME" mapping (e.g. bar.com = BAZ.COM) 2. curl requests http://host.realm.name and starts auth_negotiate 3. DNS shows gethostbyaddr(gethostbyname(host.realm.name)) = host.domain2.name 4. curl must construct an SPN of HTTP/host.domain2.name 5. curl crashes I hope that is clear. It is still a little confusing to me. Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |