Date: Mon, 7 Nov 2005 14:32:08 GMT From: aeonflux <aeonflux@aeonflux.no-ip.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/88602: privoxy poor defaults Message-ID: <200511071432.jA7EW8ue029856@www.freebsd.org> Resent-Message-ID: <200511071440.jA7EeCDl087419@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 88602 >Category: ports >Synopsis: privoxy poor defaults >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 07 14:40:12 GMT 2005 >Closed-Date: >Last-Modified: >Originator: aeonflux >Release: it's a port, but 5.4 and 6.0 >Organization: private >Environment: The problem lays in the port of privoxy >Description: the privoxy port by default runs as root, when you run the /usr/local/etc/rc.d/privoxy.sh script the daemon binds to the privoxy port and listens as uid=0! Seriously, it's a non priviledged port there's no reason to have this daemon listenning to a network socket as root. >How-To-Repeat: run the rc.d script, look at what uid is running the daemon. >Fix: Small fix to the privoxy.sh script to allow it to run as a privoxy/squid/cache user of some type. Maybe fix some of the defaults to let it write to it's log file. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511071432.jA7EW8ue029856>