Path: utzoo!attcan!uunet!ethos!pcid!gizzmo!fthood!egray
From: egray@fthood.UUCP
Newsgroups: unix-pc.bugs
Subject: Re: Glitch in logging with PCOMM 1.2 (b
Message-ID: <11100001@fthood>
Date: 10 Feb 89 13:51:00 GMT
References: <552@kosman.UUCP>
Lines: 26
Nf-ID: #R:kosman.UUCP:552:fthood:11100001:000:1096
Nf-From: fthood.UUCP!egray    Feb 10 07:51:00 1989


Reference: Permission problems with set-user-id Pcomm v1.2

Yeah, the Unix PC is broke when it comes to switching back and forth
between the real and effective user ID (oddly enough, it works fine with
the group ID!).

The reason for no error messages, is that the errors are being
discovered inside the pcomm_input routine, not in pcomm.  (I know that's
not a very good answer...  sorry)

Here is what I do on my system with HDB uucp.  I change the permissions
on the /usr/spool/locks directory to 775, change the permissions on the
/dev/ph1 device to 664 and then set the group ownership to a new group
called uucp.  (Is there already a group called "uucp"...  I can't
remember).  That way I can have Pcomm configured to be set-GROUP-id to
uucp instead of set-USER-id to uucp.  In this case, you don't need to
set the 'SETUID_BROKE' variable.

Pcomm can't correct a broken kernel...

Emmet P. Gray				US Army, HQ III Corps & Fort Hood
...!uunet!uiucuxc!fthood!egray		Attn: AFZF-DE-ENV
					Directorate of Engineering & Housing
					Environmental Management Office
					Fort Hood, TX 76544-5057