Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!mel.dit.csiro.au!yarra!melba.bby.oz.au!gnb From: gnb@duke.bby.com.au (Gregory N. Bond) Newsgroups: comp.unix.bsd Subject: Re: Fix for problem with tip in 386BSD Message-ID: <1992Jul29.233429.9420@melba.bby.oz.au> Date: 29 Jul 92 23:34:29 GMT References: <5940@pdxgate.UUCP> Sender: usenet@melba.bby.oz.au (news READER id) Organization: Burdett, Buckeridge & Young, Melbourne, Australia Lines: 25 In-Reply-To: brians@rigel.cs.pdx.edu's message of 28 Jul 92 15:03:07 GMT Nntp-Posting-Host: duke >>>>> On 28 Jul 92 15:03:07 GMT, brians@rigel.cs.pdx.edu (Brian Smith) said: >> So, I then recommend that newbies such as myself make tip sgid. I have just been playing with tipx (based on the 4.3/net2 tip; I assume the 386BSD one is similar). I have installed it setgid to a uucp group (which has write permission in the /var/spool/locks directory and the /var/adm/aculog file and read permissions on /etc/phones and /etc/remote). The problem was that tip does various setregid() calls going into and out of privileged mode and can't open the phone file (which it does from non-privileged mode). A temporary workaround is either remove the setreuid calls (there are three, I think) or make the phones file world readable (OK on a PC, possible privacy/security implications on a "real" system). I also have a dialer for v32 hayes-like modems if anyone needs them. Greg. -- Gregory Bond <gnb@bby.com.au> Burdett Buckeridge & Young Ltd Melbourne Australia ``USL has never sold long distance. You're going after the wrong men in black hats. (Or, in the case of Plan 9, black space suits)'' - Tom Limoncelli