From owner-freebsd-current Wed Nov 11 08:38:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05187 for freebsd-current-outgoing; Wed, 11 Nov 1998 08:38:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05172 for ; Wed, 11 Nov 1998 08:38:42 -0800 (PST) (envelope-from entropy@compufit.at) Received: from unet3-167.univie.ac.at ([131.130.232.167] helo=darkstar) by darkstar.psa.at with smtp (Exim 2.05 #1) id 0zddO3-0001RP-00; Wed, 11 Nov 1998 17:44:56 +0100 Date: Wed, 11 Nov 1998 17:36:31 +0100 From: Alexander Sanda To: Phillip Salzman Cc: freebsd-current@FreeBSD.ORG Subject: Re: SSH 2.0.10 BUG? (!) In-Reply-To: References: Message-Id: <3649BD0F21A.EE5FENTROPY@darkstar.psa.at> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.24.16 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998 03:29:25 +0000 (GMT) Phillip Salzman wrote: > make it +s I don't think this is a good idea. sshd is already started with root permissions (either standalone or from inetd), so it's not necessary to make it suid root. I have several FreeBSD boxen running sshd (both version 1 and 2); none of the daemons is suid root, and they don't show the problem which is subject of this thread. -- # /AS/ # GNU is not Unix, BSD is. # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message