Bug 62195
Summary: | userhelper "Password:" Infinite Loop in console | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Warren Togami <wtogami> |
Component: | pam | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | skipjack-beta1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-03-28 16:35:08 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: | |||
Bug Depends On: | |||
Bug Blocks: | 61590 |
Description
Warren Togami
2002-03-28 10:44:41 UTC
This actually turns out to be a bug in libpam_misc, which will be fixed in pam-0.75-31 and later. Thanks! Tested in Skipjack beta 2: userhelper no longer infinite loops, but it wont die when the calling program has been killed. The parent process changes to 1 (init) instead, and it co-exists with the console prompt. After a while it dies, but the console (at least in konsole) acts strangely. userhelper should be swiftly killed when the calling process has been killed rather than change its parent to init. Should I re-open this bug or post a new one? Also.... I've seen this strange behavior in the bash console that is the result of this userhelper terminating in other cases before and I suspect that THAT may be another seperate bug. I know two cases that triggers it, but I don't know how to describe it. Hmm. The userhelper process is setuid, so the caller can't kill it, and because it's blocked reading from stdin, it can't notice that its parent's gone. Not sure how to fix this aside from making sure it doesn't happen. |