From owner-freebsd-perl@FreeBSD.ORG Wed Apr 27 04:31:48 2005 Return-Path: Delivered-To: freebsd-perl@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37B1E16A4CE for ; Wed, 27 Apr 2005 04:31:48 +0000 (GMT) Received: from 301south.net (14.piel1.xdsl.nauticom.net [209.195.172.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD3F843D39 for ; Wed, 27 Apr 2005 04:31:47 +0000 (GMT) (envelope-from brandon@301south.net) Received: by 301south.net (Postfix, from userid 500) id 0E349102AC; Wed, 27 Apr 2005 00:31:47 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by 301south.net (Postfix) with ESMTP id 0A114FECF for ; Wed, 27 Apr 2005 00:31:47 -0400 (EDT) Date: Wed, 27 Apr 2005 00:31:46 -0400 (EDT) From: Brandon Kuczenski To: perl@freebsd.org Message-ID: <20050426220155.C77061@ocean.301south.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: SpamAssassin-3.0.2 patch? X-BeenThere: freebsd-perl@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: maintainer of a number of perl-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2005 04:31:48 -0000 A bug has been reported with SpamAssassin running under BSD regarding the way perl deals with dropping root privileges. Since SpamAssassin-3.0.0, when spamd spawns child processes, they run with root privileges, even if the parent process is running as an unprivileged user. There is a patch in SpamAssassin bug #3897: http://bugzilla.spamassassin.org/show_bug.cgi?id=3897 It seems to work. This is being discussed on the SA mailing list in this thread: http://thread.gmane.org/gmane.mail.spam.spamassassin.general/66190 A developer reports that "It's specifically a problem with perl on *BSD platforms." Because the patch involves behavior as root, I thought it best to bring it to your attention immediately, rather than wait for the change to percolate through normal channels. It also occurs to me that possibly the port should create a directory, /var/run/spamd, in which spamd.pid could be stored (since, IIRC, the default behavior is to create an unprivileged user spamd, and run as it, and spamd does not have write permissions to /var/run.) Currently, default behavior is to use /var/run/spamd.pid as the pidfile, which generates an error. Thanks to all who read this message for maintaining FreeBSD. -Brandon