Date: Mon, 13 Oct 1997 10:08:18 -0700 (PDT) From: Paul Traina <pst@Shockwave.COM> To: FreeBSD-gnats-submit@FreeBSD.ORG Cc: security-officer@FreeBSD.ORG, bde@FreeBSD.ORG, phk@FreeBSD.ORG Subject: kern/4755: coredump refusal of setuid programs too restrictive Message-ID: <199710131708.KAA08172@precipice.shockwave.com> Resent-Message-ID: <199710131710.KAA07599@hub.freebsd.org>
index | next in thread | raw e-mail
>Number: 4755 >Category: kern >Synopsis: we should allow coredumps of setuid code if uid==0 >Confidential: no >Severity: non-critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Oct 13 10:10:01 PDT 1997 >Last-Modified: >Originator: Paul Traina >Organization: Juniper Networks >Release: FreeBSD 3.0-CURRENT i386 >Environment: This is relevant in 2.2.x and 3.0. >Description: Currently, if a program is setuid, we don't take a core, period. This makes it very difficult to debug certain types of problems. >How-To-Repeat: Dump core in a setuid program invoked by root. >Fix: The code should be changed to check the uid (maybe saved uid?) of the current invoker and remove the restriction if that uid is 0. >Audit-Trail: >Unformatted:home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710131708.KAA08172>