Bug 7838
Summary: | Can't get non-root user ability to use kppp | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Steve Cohen <stevecoh> |
Component: | kdeutils | Assignee: | Bernhard Rosenkraenzer <bero> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | dbmorris, dickson |
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: | 1999-12-17 15:10:55 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
Steve Cohen
1999-12-16 12:41:54 UTC
It's not a bug, it's a security feature. In countries where you pay for connections, you don't want non-privileged users to open connections. If you want to permit non-privileged users to connect using kppp, either make kppp setuid root, or use sudo to grant them root access to just kppp. This answer answers nothing, unfortunately. Did you even read my report? Which "kppp" are you talking about? The one in /usr/sbin which is not on the path of non-root users, or the one is on their path, the one in /usr/bin? Was my solution of removing the symlink in /usr/bin which pointed to consolehelper and replacing it with one that pointed to /usr/sbin/kppp (which I DID setuid root) the correct one? Or is there better? And if it was correct, why am I getting all those messages about not being able to find the interface ppp0? I did set up the interface to be accessible to all users which is proven anyway by the fact that RP3 is able to find it without difficulty. My point, really, is that there were simple instructions in the kppp documentation that tell you how to set things up so that non-root users can access kppp. Since Redhat has seen fit to set things up differently than the setup envisioned by the authors of that documentation, and that documentation is no longer correct, Redhat owes its users clear replacement documentation. Sorry, I automatically sent a standard reply after reading the first paragraph, because the security features often get reported as bugs. Yes, it was right to rm /usr/bin/kppp and ln -s /usr/sbin/kppp /usr/bin. The can't find ppp0 bug looks like a problem with pppd... Did you update the ppp package? There have been a couple of problems with the stock 6.1 one. No,I'm using the stock ppp. I'll try that. Thanks. You might want to pass on my comments on documentation to you documentation people. Since you didn't enter anything more, I assume updating pppd fixed this. |