From owner-freebsd-bugs Sun Jul 8 21:20: 5 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 733A937B403 for ; Sun, 8 Jul 2001 21:20:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.3/8.11.3) id f694K3X50882; Sun, 8 Jul 2001 21:20:03 -0700 (PDT) (envelope-from gnats) Date: Sun, 8 Jul 2001 21:20:03 -0700 (PDT) Message-Id: <200107090420.f694K3X50882@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Brad Huntting Subject: Re: bin/28333: rtprio/idprio setuid problems Reply-To: Brad Huntting Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/28333; it has been noted by GNATS. From: Brad Huntting To: Kris Kennaway Cc: Brad Huntting , FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/28333: rtprio/idprio setuid problems Date: Sun, 08 Jul 2001 22:17:21 -0600 > Have you positively determined that sudo or another such existing tool > can't be used to do what you want? After looking around, I think POSIX1e Capabilities are probably the best solution to this problem. It comes with alot of security bagage, but it's probably the "right" way to solve which is essentially a fine-grain security issue. thanx, brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message