From owner-freebsd-security Fri Mar 22 6:46:44 2002 Delivered-To: freebsd-security@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with SMTP id A6A2D37B404 for ; Fri, 22 Mar 2002 06:46:29 -0800 (PST) Received: (qmail 40281 invoked by uid 501); 22 Mar 2002 14:46:27 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Mar 2002 14:46:27 -0000 Date: Fri, 22 Mar 2002 11:46:27 -0300 (BRT) From: Paulo Fragoso To: security@freebsd.org Subject: Maildrop vs. Procmail Message-ID: <20020322103140.O10588-100000@mirage.nlink.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, We have a mail server without shell access for all users. We are thinking to use maildrop to implement mail filters (anti-spam) but we guess there is a security problem with maildrop for this case. We didn't found any configure options to restrict its use, like procmail's option: #define RESTRICT_EXEC 1000 So any user could be albe to exec some script by $HOME/.mailfilter. Are we wrong? Now we are restricting .qmail shell by a smrsh patched (qmail-local.c was patched too), this way any user can exec by .qmail. We are using procmail for two administrator, their UID are minor than 1000. Are there any way to restrict mailfilter for our users? Thanks, Paulo. -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message