From owner-freebsd-current@FreeBSD.ORG Fri Aug 20 11:05:09 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 83DF616A4CF for ; Fri, 20 Aug 2004 11:05:09 +0000 (GMT) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 647B543D4C for ; Fri, 20 Aug 2004 11:05:08 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received-SPF: pass (mp2.macomnet.net: domain of maxim@macomnet.ru designates 127.0.0.1 as permitted sender) receiver=mp2.macomnet.net; client_ip=127.0.0.1; envelope-from=maxim@macomnet.ru; Received: from localhost (6f3by5yx@localhost [127.0.0.1]) by mp2.macomnet.net (8.12.11/8.12.11) with ESMTP id i7KB50Y8029748; Fri, 20 Aug 2004 15:05:00 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Fri, 20 Aug 2004 15:05:00 +0400 (MSD) From: Maxim Konovalov To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= In-Reply-To: Message-ID: <20040820150433.A29713@mp2.macomnet.net> References: <200408131332.09164.ilkerozupak@yahoo.com> <20040813104934.GL87690@submonkey.net> <20040813153607.GF4198@dan.emsphone.com> <20040820114001.R28976@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Ceri Davies cc: Ilker Ozupak cc: Dan Nelson 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 11:05:09 -0000 On Fri, 20 Aug 2004, 12:20+0200, Dag-Erling Sm?rgrav wrote: > 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. Ah, OK, thanks for the clarification. -- Maxim Konovalov