Kppp works only for root (KDE2.1)

Kppp works only for root (KDE2.1)

Post by shavin » Mon, 12 Mar 2001 05:49:53



Please read this through your Newbe Glasses.

I run Caldera eDesktop2.4 on a laptop with a Linux compatible PCMCIA modem
on ttyS1.
The version of KDE that came with the distro worked great. including the
Ksaferppp dialer.

I recently installed KDE2.1 from RPM and found the dialer would only work
if I were logged in as root.

Logged in as a user, the symptom origenaly was "can't connect to modem" no
matter what device setting I used (modem, cua1 or ttyS1). After a lot of
prodding and poking I noticed that /dev/ttyS1 rights were set so that only
root and some odd group named uucp could r/w to it. Once I fixed that,
lowly users could dial out via Kppp.

BUT

Then, once connection and hadshake was successful. pppd fails with a code
16.  I looked it up and no joy there.

Remember, Kppp works great if I login as root.

I then went to /opt/kde2/bin/ and set the rights (attributes?) of
everything that contained ppp in the name so the users group could rwx.  No
joy. Then I set the suid bit on in pppd. Still no worky.

I have given up and added a menu icon for the old Ksaferppp program. Works
fine. (using it now)

I would really like to get the Kppp dialer working without creating a
security hole (like "run as root"). Can anyone help? Please?

For extra bonus points can anyone tell me what the hell the user group uucp
is and why it is so pervasive?

Sean Havins
Colorado, USA

--
Don't believe everything you think.

 
 
 

Kppp works only for root (KDE2.1)

Post by walt » Mon, 12 Mar 2001 09:07:51



> ...I recently installed KDE2.1 from RPM and found the dialer would only work
> if I were logged in as root...

kppp needs to be suid root if you want to use it as an ordinary user:

chmod +s /usr/bin/kppp

 
 
 

Kppp works only for root (KDE2.1)

Post by shavin » Mon, 12 Mar 2001 12:09:56




>> ...I recently installed KDE2.1 from RPM and found the dialer would only
>> work if I were logged in as root...

> kppp needs to be suid root if you want to use it as an ordinary user:

> chmod +s /usr/bin/kppp

YESSSSS!!!!!!!
Thank you. that was it exactly.

When I tried the command you sent me I got the following:


chmod: /usr/bin/kpp: No such file or directory


As you can see,  when I figured out where the file is in my installation it
worked fine. When I went back and checked the properties, I noticed that
Both the UID and GID bits got set. Of course you knew that.

Score one for a command line interface. I had read about Set UID before and
had always used the "permitions" tab of "properties" and set just that.

Thanks Again
Sean

BTW, What is the "uucp" group?

--
Don't believe everything you think.

 
 
 

Kppp works only for root (KDE2.1)

Post by akar 'th 'orribl » Mon, 12 Mar 2001 22:10:52


The undercover alien spy known as shavins extruded a tentacle and
scratched:



>>> ...I recently installed KDE2.1 from RPM and found the dialer would
>>> only work if I were logged in as root...

>> kppp needs to be suid root if you want to use it as an ordinary user:

>> chmod +s /usr/bin/kppp

> YESSSSS!!!!!!!
> Thank you. that was it exactly.

> When I tried the command you sent me I got the following:


> chmod: /usr/bin/kpp: No such file or directory


> As you can see,  when I figured out where the file is in my
> installation it worked fine. When I went back and checked the
> properties, I noticed that Both the UID and GID bits got set. Of
> course you knew that.

> Score one for a command line interface. I had read about Set UID
> before and had always used the "permitions" tab of "properties" and
> set just that.

> Thanks Again
> Sean

> BTW, What is the "uucp" group?

I think its Unix to Unix Communication Protocol which is why kppp is
probably a member. So the correct  solution to your problem would be to
give your users membership of this group so they can operate diallers
etc. The same as sound devices should all be in an audio etc. making
things suid root creates security holes. Thats why you will find all
those strange users and groups on your computer that arent real people!
But of course I could be wrong ( it has happened :-) )

Andrew

--
C'mon, What are you waiting for?
Imminentize the eschaton NOW!!!

 
 
 

1. strange kppp problems only with kppp in kde2

Hello!

I upgraded from kde to kde2 and in the beginning still used my old
kppp (from the old kde) which worked as before.

Now that I installed the updated kppp for kde2 as well, there are some
funny problems I don't understand!
The problem with setuid or write permission for the lock file was only
a minor problem, but the real problem now is:

Agent running under wine now gives me an error: not enough memory to
initialize winsock... !?
I really can't see the reason for this recent error with the new kppp;
I have lots of free memory, and moreover, other internet applications
work o.k., like netscape, ftp etc. And still I can't get Agent to
connect any longer.

So I went back to my still fully functional kppp from the old kde1,
apart from using pure dip and chat scripts which I mostly used anyway
instead of tools like kppp.

Anyone else noticed this annoyance, and perhaps someone know the
reason and a good solution?

thanks
Peter

2. Lost in NIS... help!

3. Getting Kppp to Work Other than in Root?

4. I'm lost with installation

5. kppp only works as root

6. Y2K & AIX 4.1.1.0

7. kppp works as root not as user

8. How to tell what ver. of kde and koffice?

9. kppp only works for root, not for other users (2.2.3 kernel)

10. Docking kppp in the panel (KDE2)

11. kde2, kppp & compuserve

12. strange kppp problems only with kde2

13. KDE2 KPPP Problem