🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.mail.misc
Article #5691

Re: MMDF II .forward permissions

#5691
From: Jim Sullivan
Date: Wed, 22 Jun 1994 17:22
41 lines
3068 bytes
In <Crr9xE.5LB@ssi.edc.org> gunther@ssi.edc.org (Gunther Anderson) writes:
>Recently, my users have gotten more technically savvy, and have learned
>how to change permissions on their home directories.  MMDF requires that
>the file .forward be owned by the user, and readable by the user 'mmdf'. 
>I'm having trouble making that work.  If users have directory permissions
>set to at least 751 (rwxr-x--x), then users' .forwards get read.  However,
>750 doesn't cut it.  (Note that all the .forwards are set to 644).  The
>users all have the same group id, 'group'.  Normally, 'mmdf' has the group
>id 'mmdf' in /etc/passwd, and is listed as part of 'group' in /etc/group. 
>When logged in as 'mmdf' I can read everyone's .forward properly.  But
>msg.log from MMDF has lines like: 
>
>[SYSERR(13)Permission denied]  lc_forward: stat(/u/gunther/.forward)
>
>whenever a message goes to an account with a .forward.  I have tried 
>setting the /etc/passwd group designation of 'mmdf' to 'group' and that 
>hasn't helped either.  It's like the system is ignoring group permissions 
>on the directories, so that only world file-searching (--x) permission 
>allows MMDF to get to the .forward, which it can then read because of 
>world-readability on the file.

I suspect that the confusion is related to the use of supplemental groups.
Permissions are mapped to the users/programs [RE]UID and [RE]GID.  For
users that have logged into the system, there is support for supplemental
groups, but I don't think that applies to the mmdf programs.  So, the GID
for the mmdf programs default to mmdf.

If it is true that supplemental groups do not apply to the mmdf programs
(since they are not logged in, per se), then removing the directory search
permissions on the home directory would have the described effect (EACCESS
is returned, errno 13).

This is my reading of the situation.  Since the delivery programs are started
up at boot time, they may not (and it appears that they don't) use
supplemental groups.  This would explain the ability to read the files while
logged on as mmdf but not via the delivery programs.
--
Jim Sullivan				
SCO Canada, Inc. Toronto, Ontario	 "I like picking up five 'cause it
jim@sco.com, ...!uunet!scocan!jim	  gives me more miss-a-turns" -Hilary,
416 922 1937 (8397 for fax)	 	  beating her dad in Crazy-8s
Technical Details
Message-ID: <1994Jun22.172218.32@sco.COM>
Path: arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!hookup!yeshua.marcam.com!charnel.ecst.csuchico.edu!olivea!xenitec!hobbes!scocan!jim
References: <Crr9xE.5LB@ssi.edc.org>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f4424,3b74a8d221fb84ba
X-Google-Attributes: gidf4424,public
X-Google-Thread: 1122ea,3b74a8d221fb84ba
X-Google-Attributes: gid1122ea,public
X-Google-ArrivalTime: 1994-06-22 10:30:45 PST
Newsgroups: comp.mail.misc,biz.sco.general
Path: arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!hookup!yeshua.marcam.com!charnel.ecst.csuchico.edu!olivea!xenitec!hobbes!scocan!jim
From: jim@sco.COM (Jim Sullivan)
Subject: Re: MMDF II .forward permissions
Organization: SCO Canada, Inc.
Date: Wed, 22 Jun 1994 17:22:18 GMT
Message-ID: <1994Jun22.172218.32@sco.COM>
References: <Crr9xE.5LB@ssi.edc.org>
Sender: news@sco.COM (News administration)
Lines: 41