Very Computer

PLEASE HELP!!!

I can't get non-root users of dip to be able to dial
out...

First, it tries to create dip.pid in /etc, and gets
"permission denied".  Fine.  This is my home computer
and I'm the only user.  I'll make /etc 777 so that
dip can create the file.

Now, whenever I run a dip script, everything checks
out fine, but whenever I try to rlogin to anywhere,
I get:

filigree % rlogin mussel

mussel: network is unreachable

How can I figure out what's going on???

Thanks,
Dan
--

Dan Langrill

Quote:> PLEASE HELP!!!

> I can't get non-root users of dip to be able to dial
> out...

> First, it tries to create dip.pid in /etc, and gets
> "permission denied".  Fine.  This is my home computer
> and I'm the only user.  I'll make /etc 777 so that
> dip can create the file.

> Now, whenever I run a dip script, everything checks
> out fine, but whenever I try to rlogin to anywhere,
> I get:

> filigree % rlogin mussel

> mussel: network is unreachable

> How can I figure out what's going on???

dip must be owned by root and setuid:

chmod 2755 dip

_Hans

______________________________________________________________________

            'I never set out to be weird.
                 It was always other people who called me weird.' [fz]
______________________________________________________________________

Why can't you read the README files in DIP dist kit?!
It spells out clearly that DIP *has* to be set-uid
root.
--
Regards,

------------
<Disclaimer>
I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.

That's funny...It doesn't seem to say it in the distribution
kit that I'm reading...

filigree 158 % grep root README*

README:3. "chown root.dip /usr/sbin/dip"
README.NEWBIES:root ~/# ping 130.149.1.10          try if connection is okay
README.SKEY:will have to run as root, so that it can update /etc/skeykeys after a
README.SKEY:successful login. [I think that diplogin already has to run as root,
README.SKEY:that diplogin has to run suid root, which is not a good idea, as
README.SKEY:root, because of the security implications.  How do people normally

I have SKEY compiled out, so why should I read that?

The README says to do a chown on dip.  It doesn't say that you can't
use dip unless you're root.

Maybe you should update the README more clearly...

Anyhow, who reads directions? :-)
--

Dan Langrill

I said "READ the F README files", not GREP them. (:-) (:-(

Quote:> filigree 158 % grep root README*

> README:3. "chown root.dip /usr/sbin/dip"

Were you not smart-assy and actually read the file - you'd see:

3. "chown root.dip /usr/sbin/dip"

4. "chmod u=rx,g=x,o= /usr/sbin/dip"

5. Now you can "chmod u+s /usr/sbin/dip"

Quote:> I have SKEY compiled out, so why should I read that?

So don't read THAT, read just the README file... For
your own sake, by Lord...

Quote:> The README says to do a chown on dip.  It doesn't say that you can't
> use dip unless you're root.
> Maybe you should update the README more clearly...

Learn how to read...

Quote:> Anyhow, who reads directions? :-)

Yes, that''s the problem these days - illiteracy to the point
of complete inability to read (:-).
--
Regards,

------------
<Disclaimer>
I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.