|
Bugzilla – Full Text Bug Listing |
| Summary: | Permissions on Yast modules (other than main entry one) appear to permit general user access when accessed directly | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Tony Hall <afsh> |
| Component: | YaST2 | Assignee: | Stanislav Visnovsky <visnov> |
| Status: | RESOLVED INVALID | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | gp, security-team |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Tony Hall
2006-03-19 00:37:10 UTC
Forgot to mention that the Yast items were included in the "Other" menu list in XFMenu. Thanks. Apologies for hassling you again. However should this really be in the global group? I am a bit of a newbie, and probably a bit paranoid, but is advertising this a good idea? Again, apologies and thanks. Humblest apologies from the nuisance. I wasn't thinking straight. Users should be aware, that is the point of being open. If it si possible please remove comment #2 and this one. Thanks, and again, apologies. In what way is YaST envoked by this menu? Actually, calling `/sbin/yast2 <module>' starts the modules also with a normal user. Maby we should deny the start of these modules (all but release_notes and media_check), they would not work anyway and there is a chance that one of these modules could actually corrupt something. Adding the security-Team to CC and reassigning. This was always the case. The modules that absolutely require root access, will show a pop up. For others, they behave like read-only and they don't have only the rights of the user that started the module. *** Bug 158483 has been marked as a duplicate of this bug. *** |