From owner-freebsd-security Mon Jul 15 00:49:14 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA12365 for security-outgoing; Mon, 15 Jul 1996 00:49:14 -0700 (PDT) Received: from mercury.gaianet.net (root@mercury.gaianet.net [206.171.98.26]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA12360; Mon, 15 Jul 1996 00:49:12 -0700 (PDT) Received: (from vince@localhost) by mercury.gaianet.net (8.7.5/8.6.12) id AAA23308; Mon, 15 Jul 1996 00:49:10 -0700 (PDT) Date: Mon, 15 Jul 1996 00:49:10 -0700 (PDT) From: -Vince- To: Poul-Henning Kamp cc: jbhunt , freebsd-security-notification@freebsd.org, freebsd-security@freebsd.org, root@mercury.gaianet.net Subject: Re: New EXPLOIT located! In-Reply-To: <4914.837416816@critter.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Jul 1996, Poul-Henning Kamp wrote: > >> remove the rdist program from your system, or just remove the setuid > >> bit from it. > >> > >> Do normal "we've been hacked cleanup". > > > > While we're at the subject, is there a hole with mount_msdos also > >because the guy had some text on mount_msdos but I deleted the > >/sbin/mount_msdos and -current still installs with the setuid bit... > > Well, until proven innocent, all setuid programs are suspect. > > Make a list of them all, remove setuid on any you don't use. Consider > carefully the minimum permissions you can get away with on the rest. Okay, now besides the /sbin directory, what other binaries are setuid that are installed by -current? Vince