Bug 122523
Summary: | restarts ssh but with incorrect security context | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tim Waugh <twaugh> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | drepper, dwalsh |
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: | 2004-09-30 18:20:41 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
Tim Waugh
2004-05-05 14:13:25 UTC
I thing I updated my system today without explicitly restarting ssh (i.e., the glibc spec file did). Login still works. Can somebody confirm this is still a problem? If yes, will we need to use the new su-replacement? Not sure; I'm not using SELinux at the moment I'm afraid. This should not be a problem. The 'su' replacement (Which it is not) is only used for init startup scripts and cron jobs. Basically any place where you don't need the suid and pam stuff. Dan So you're saying the whole bug should not be an issue and can be closed? Was there something back in May which could have caused problems? And: What is the reason for posting the URL? Yes rpm updates were doing a service restart which caused ssh to come up in the wrong state. Oops, I pasted the html in the wrong page. Got to stop reading two bugzillas at once. |