Re: kppp non root users

2002-09-08 Thread Rob Weir
On Sat, Sep 07, 2002 at 09:20:27AM +0200, Craig Main wrote:
 I have changed the auth to noauth before I tried to connect...? still no
 luck...:(

Are you in the 'dialout' group?  Or is it the 'dip' group...?

-rob


pgpndF8nk9Tlb.pgp
Description: PGP signature


Re: kppp non root users

2002-09-07 Thread Craig Main
On Fri, 2002-09-06 at 19:57, Greg C. Madden wrote:

 
 I think it has to do with the 'auth' option in the /etc/ppp/options
 file.You can test by changing the line to 'noauth'. 
 
 # Require the peer to authenticate itself before allowing network
 # packets to be sent or received.
 # Please do not disable this setting. It is expected to be standard in
 # future releases of pppd. Use the call option (see manpage) to disable
 # authentication for specific peers.
 auth
 
I have changed the auth to noauth before I tried to connect...? still no
luck...:(

Thanks anyway.

Regards
Craig



 -- 
 Greg C. Madden
 Debian GNU/Linux
 
-- 
Craig Main
RHCE
ST Solutions
Cell: 082-323-4670
Home Tel: 011-760-1900




Re: kppp non root users

2002-09-07 Thread Jerry Dimitriou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 I have changed the auth to noauth before I tried to connect...? still no
 luck...:(

 Thanks anyway.

 Regards
 Craig


as root:
$chgrp dialout /usr/bin/kppp
$chmod 764 /dev/ttyS0

Assuming that your modem is connected at ttyS0.

Obviously this is a hack to make kppp run, and it is not probably very secure.


- -- 
Jerry Dimitriou

Software Development
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9e2IdEpcfIh1U3i4RAidyAJ0d3mMFg3XEcPE6dp9X5iVgu4EFCwCeO4sB
f2frtcv1xT15xoV3M3EzR7s=
=q4pv
-END PGP SIGNATURE-




Re: kppp non root users[Bug Report ?]

2002-09-07 Thread Simon Hepburn
Craig Main wrote:
 I have changed the auth to noauth before I tried to connect...? still no
 luck...:(

I experienced the same difficulties when I upgraded to 3.x. Change  kppp to be 
SUID. See the kppp handbook ( help:/kppp/security-why-suid.html ) for an 
explanation. kppp 3.0.3-1 is shipped SGID. Is there a good reason for this or 
is it a bug ? I don't recall ever having to do this with 2.x.x.

-- 
Simon Hepburn.




Re: kppp non root users[Bug Report ?]

2002-09-07 Thread tomas p
On Sat, 7 Sep 2002, Simon Hepburn wrote:

 Craig Main wrote:
  I have changed the auth to noauth before I tried to connect...? still no
  luck...:(

 I experienced the same difficulties when I upgraded to 3.x. Change  kppp to be
 SUID. See the kppp handbook ( help:/kppp/security-why-suid.html ) for an
 explanation. kppp 3.0.3-1 is shipped SGID. Is there a good reason for this or
 is it a bug ? I don't recall ever having to do this with 2.x.x.

AFAI remember if you install ppp, debconf will ask you whether to install
pppd suid. And AFAIK iif you install it suid then you don't need to suid
kppd. You only have to make sure that the user can access the device
(adduser whoever dialout). I'm not using kppp, I might be wrong though.
*t

--
  to
ma
  s
p




Re: kppp non root users[Bug Report ?]

2002-09-07 Thread Simon Hepburn
tomas p wrote:

 AFAI remember if you install ppp, debconf will ask you whether to install
 pppd suid. And AFAIK iif you install it suid then you don't need to suid
 kppd.

No, on my box pppd is SUID, I still experienced the same prob's as Craig. The 
problem is that kppp_2.2.2-14 ships SUID and kppp_3.0.3-1 ships SGID. 
Upgrading results in only root being able to connect with kppp.

-- 
Simon Hepburn.




kppp non root users

2002-09-06 Thread Craig Main
Hi All,

I need a bit of help here, I am trying to get kppp to work with a normal
user. The user is a member of dialup and dip. Every time the user dials
up I get the following output to the console (I started kppp from
command line):

[EMAIL PROTECTED]:/usr/share/doc/kppp$ kppp
Opener: received SetSecret
Opener: received OpenLock

Opener: received OpenDevice
Opener: received ExecPPPDaemon
In parent: pppd pid 2040
Kernel supports ppp alright.
Couldn't find interface ppp0: No such device
Couldn't find interface ppp0: No such device
It was pppd that died
pppd exited with return value 19
Sending 2036 a SIGUSR1
Opener: received RemoveSecret
Opener: received RemoveSecret
Opener: received OpenResolv
Opener: received OpenResolv
error opening resolv.conf!
Opener: received RemoveLock
Opener: received PPPDExitStatus
Opener: received OpenSysLog

According to man pppd, exit code 19 is failure to authenticate to peer.
I have checked the username and passwords and they are correct.

If I run kppp as root with the same settings, it dials up fine without
problems.

I am convinced it has something to do with permissions, but don't know
what more to check. I'm running sid  KDE3.

TIA

Craig
-- 
Craig Main
RHCE
ST Solutions
Cell: 082-323-4670
Home Tel: 011-760-1900




Re: kppp non root users

2002-09-06 Thread Greg C. Madden
On Fri, 2002-09-06 at 07:20, Craig Main wrote:
 Hi All,
 
 I need a bit of help here, I am trying to get kppp to work with a normal
 user. The user is a member of dialup and dip. Every time the user dials
 up I get the following output to the console (I started kppp from
 command line):
 
 [EMAIL PROTECTED]:/usr/share/doc/kppp$ kppp
 Opener: received SetSecret
 Opener: received OpenLock
 
 Opener: received OpenDevice
 Opener: received ExecPPPDaemon
 In parent: pppd pid 2040
 Kernel supports ppp alright.
 Couldn't find interface ppp0: No such device
 Couldn't find interface ppp0: No such device
 It was pppd that died
 pppd exited with return value 19
 Sending 2036 a SIGUSR1
 Opener: received RemoveSecret
 Opener: received RemoveSecret
 Opener: received OpenResolv
 Opener: received OpenResolv
 error opening resolv.conf!
 Opener: received RemoveLock
 Opener: received PPPDExitStatus
 Opener: received OpenSysLog
 
 According to man pppd, exit code 19 is failure to authenticate to peer.
 I have checked the username and passwords and they are correct.
 
 If I run kppp as root with the same settings, it dials up fine without
 problems.
 
 I am convinced it has something to do with permissions, but don't know
 what more to check. I'm running sid  KDE3.
 
 TIA
 
 Craig

I think it has to do with the 'auth' option in the /etc/ppp/options
file.You can test by changing the line to 'noauth'. 

# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
auth

-- 
Greg C. Madden
Debian GNU/Linux



signature.asc
Description: This is a digitally signed message part