From owner-freebsd-current@FreeBSD.ORG Fri Aug 20 14:18:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A698916A4CE for ; Fri, 20 Aug 2004 14:18:31 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A99B43D45 for ; Fri, 20 Aug 2004 14:18:31 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.11/8.12.11) id i7KEIRcu016971; Fri, 20 Aug 2004 09:18:28 -0500 (CDT) (envelope-from dan) Date: Fri, 20 Aug 2004 09:18:27 -0500 From: Dan Nelson To: Dag-Erling Smorgrav Message-ID: <20040820141827.GD8165@dan.emsphone.com> References: <200408131332.09164.ilkerozupak@yahoo.com> <20040813104934.GL87690@submonkey.net> <200408131436.12750.ilkerozupak@yahoo.com> <20040813153607.GF4198@dan.emsphone.com> <20040820114001.R28976@mp2.macomnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: Ceri Davies cc: Ilker Ozupak cc: freebsd-current@freebsd.org Subject: Re: suid bit sshd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Aug 2004 14:18:31 -0000 In the last episode (Aug 20), Dag-Erling Smorgrav said: > Maxim Konovalov writes: > > DES, is it OK to commit a following patch? Or you were going to > > deprecate ENABLE_SUID_SSH? We still have it in make.conf(5), > > share/examples/etc/make.conf and ssh-keysign/Makefile. > > The whole point with ssh-keysign is to separate out the parts of ssh > that need a setuid bit. It should not be necessary for ssh to have a > setuid bit if ssh-keysign does, which is what ENABLE_SUID_SSH > controls these days. ssh-keysign doesn't yet handle SSH 1 keys, though, and a non-root ssh can't use UsePrivilegedPort which may be needed for RhostsRSAAuthentication with older servers. If you're only using SSH-2 keys, and you're only talking to new sshds, then no, you don't need ENABLE_SUID_SSH. -- Dan Nelson dnelson@allantgroup.com