From owner-freebsd-security Sat Aug 22 00:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07345 for freebsd-security-outgoing; Sat, 22 Aug 1998 00:11:13 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from Tyr.office.EFN.org ([204.214.99.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07339 for ; Sat, 22 Aug 1998 00:11:10 -0700 (PDT) (envelope-from spy@tyr.office.efn.org) Received: from Tyr.office.EFN.org (IDENT:spy@Tyr.office.EFN.org [204.214.99.45]) by Tyr.office.EFN.org (8.9.1/8.9.1) with SMTP id AAA05672; Sat, 22 Aug 1998 00:10:25 -0700 (PDT) Date: Sat, 22 Aug 1998 00:10:25 -0700 (PDT) From: Ben Reply-To: ben@efn.org To: security@FreeBSD.ORG cc: ben@efn.org Subject: libkvm and user-info tools patches (was ps(1)) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A few weeks ago I released a patch to make ps -a 'break' for normal user's preventing them from seeing other people that are logged in, and what they are doing. I finshed those patches for w, who and top too. After taking a look at libkvm I've decided it would be easier if kvm_getprocs was controlled by a sysctl oid(kern.usersecure). This would prevent user's from using it in any program that called it, by checking if kern.usersecure was a certian number, much like securelevel is now. Take a look at what I came up with and give me some feedback. I've been using it for 3 days now with no problems at all. Text info on it: http://www.efn.org/~ben/security/README.txt The tarball of source diff's (diff -c against 2.2.7 stable): http://www.efn.org/~ben/security/kvm.tgz -ben@efn.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message