From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7018 invoked by alias); 19 Nov 2009 05:10:25 -0000 Received: (qmail 6965 invoked by uid 48); 19 Nov 2009 05:10:08 -0000 Date: Thu, 19 Nov 2009 05:10:00 -0000 From: "fche at redhat dot com" To: systemtap@sources.redhat.com Message-ID: <20091119051007.10984.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/10984] New: restrict unprivileged mode operation to "stapusr" or similar X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00596.txt.bz2 Considering the potential size of the worm can, for an early non-experimental deployment of unprivileged mode, let's allow sysadmins to restrict staprun to run even signed code only for some users. If we don't wish to build an elaborate ACL setup (or even a simple one like /etc/ftpusers), how about restricting signed mode to only "stapusr" people. That way, two separate actions are required by a local sysadmin: the approval of the compilation environment, and approval of individual users. Reuse of "staprun" as the groupid is probably plausible since it's already a "lower privilege" sort of systemtap user, which can only run precompiled stuff specifically installed under /lib/modules/`uname -r`/systemtap. The proposal here is to also permit such people to run --unprivileged scripts / signed modules. (Another option is to create a third user group, like "stapunpriv", but I can't think of a good case for it as distinct from stapusr.) -- Summary: restrict unprivileged mode operation to "stapusr" or similar Product: systemtap Version: unspecified Status: NEW Severity: normal Priority: P2 Component: runtime AssignedTo: systemtap at sources dot redhat dot com ReportedBy: fche at redhat dot com OtherBugsDependingO 10907 nThis: http://sourceware.org/bugzilla/show_bug.cgi?id=10984 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.