|
Bugzilla – Full Text Bug Listing |
| Summary: | wrong permissions on ttyS0 | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Robert Simai <robert.simai> |
| Component: | Basesystem | Assignee: | Ludwig Nussel <lnussel> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | security-team |
| Version: | RC 4 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Robert Simai
2005-09-22 09:12:28 UTC
For security reasons the serial line is only for the system user or the uucp subsystem available. You may add an own entry for the line /dev/ttyS0 to /etc/permissions.local and run SuSEconfig. It's not a problem for me, it's with regards to inexperienced users. The default is omitting the fact that there are users who want to connect a serial device and therefore should be changed. At least there has to be a notification while installation or whatever. For all I care write it to the release notes if it's not possible to change the default. Andreas, who can/will add this to the release notes? Btw, I think changing the permissions would need to be done in udev nowadays,,, A user never had access to ttyS0 by default. So there is no change compared to 9.3 and previous. So, what is the best solution to do here? An SDB article maybe. The article could explain how to adjust permissions using udev rules or how to involve resmgr to do it. OK, even if I don't understand this default, it seems to be a proper solution. Maybe you can just write this in short to me and I'll make an article out of it? Same wit an external modem on /dev/ttyS1: During installation Test ok, but later no access... After new installation I checked the permissions (using an external modem on /dev/ttyS1 for internet...) and it seems that kinternet doesn't and kppp needs full access to the serial port. Maybe I can't use them both together... what to do here? resmgr addition and then ACL settings would help if the user really needs access. I sent Robert instructions so he can make an SDB article but forgot to close the bug. |