Bug 10791
Summary: | Can lock up console, forcing reboot in some cases | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jack Lloyd <lloyd> |
Component: | vlock | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | ddm, federico.cozzi |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-04-13 15:39:18 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
Jack Lloyd
2000-04-13 15:39:18 UTC
This is a natural tradeoff caused by using shadow passwords; negative privildges are limited. No, I assure you it is a bug. It worked fine with shadow passwords on NIS on 60 desktops we had installed with RH 6.1, and now it doesn't on a few RH 6.2 installs. Also, I noticed that if you supply the USER's password when it asks for the ROOT password, it will unlock the terminal. If that's not a bug I don't know what is. We have about a dozen of VA Linux desktops with VA's customized RH6.2 on them, and only one of them exhibits this behavior. In addition, we have a couple of generic desktops with Stock RH6.2 on it which do not work properly. I'm thinking that it is the 6.2 UPDATE rpms that broke it, but I have not had the time to verify. Our environment has both NIS and shadow passwords, and as I said, the vast majority of our desktops work fine, but a handfull do not. They are all RH 6.2 installs, and I believe they all have had the update RPMs applied. I have no guess as to what the actual cause of the problem is, as I haven't had the time to whip out the source and debug it (unfortunately, I probably won't either). In addition, xscreensaver does not work on these same machines. I suspect the bug is in a library that these two applications share, but again, I haven't had time to look into it. |