Date: Fri, 7 Feb 2003 10:46:57 -0700 From: jrm@crackpot.org To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/48055: bug report Message-ID: <20030207174657.GA23263@ami.crackpot.org>
next in thread | raw e-mail | index | archive | help
>Number: 48055
>Category: ports
>Synopsis: eterm-0.9.1_1 fails to properly drop root permissions
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Feb 07 09:50:07 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: John R. Makosky
>Release: FreeBSD 4.7-STABLE i386
>Organization:
not important
>Environment:
System: FreeBSD mirabell 4.7-STABLE FreeBSD 4.7-STABLE #0: Fri Jan 31
12:16:47 CST 2003 root@mirabell:/usr/obj/usr/src/sys/MIRABELL i386
>Description:
When running eterm-0.9.1_1 from a home directory located
on an NFS partition that "squashes" root access, Eterm fails
to start. Ktracing around revealed that $HOME/.Xauthority
could not be opened (permission denied). Removing setuid
bit on Eterm binary allowed $HOME/.Xauthority to be read, and
Eterm to start (but not update wtmp); Hrmm...
>How-To-Repeat:
Install Eterm, run from an NFS-mounted home directory that
doesn't allow root access.
>Fix:
Build Eterm without patch
/usr/ports/x11/eterm/files/patch-src:startup.c. This patch
appears to be erroneous.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030207174657.GA23263>