From owner-freebsd-security Fri Aug 21 09:39:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29754 for freebsd-security-outgoing; Fri, 21 Aug 1998 09:39:52 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29749 for ; Fri, 21 Aug 1998 09:39:48 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA15257; Fri, 21 Aug 1998 12:38:59 -0400 (EDT) (envelope-from wollman) Date: Fri, 21 Aug 1998 12:38:59 -0400 (EDT) From: Garrett Wollman Message-Id: <199808211638.MAA15257@khavrinen.lcs.mit.edu> To: dima@best.net Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), jkh@time.cdrom.com, security@FreeBSD.ORG Subject: Re: Scaring the bezeesus out of your system admin as a normal user: In-Reply-To: <199808211637.JAA25475@burka.rdy.com> References: <199808211204.IAA14546@khavrinen.lcs.mit.edu> <199808211637.JAA25475@burka.rdy.com> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org <> It would be fairly simple for us to simply pass the user's credentials >> along with the message, and then have syslogd differentiate. > I don't think it will solve the problem. Sending log message doesn't require > any special priveleges, so if you'll force logger to send user credentials, > someone can simply write a program that will go around it. You missed the point. Credentials passed over PF_LOCAL sockets are by design unforgeable. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message