From owner-freebsd-questions@FreeBSD.ORG Mon Jan 24 21:10:26 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7DEA16A4CE for ; Mon, 24 Jan 2005 21:10:26 +0000 (GMT) Received: from helium.webpack.hosteurope.de (helium.webpack.hosteurope.de [217.115.142.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FF8443D39 for ; Mon, 24 Jan 2005 21:10:26 +0000 (GMT) (envelope-from me@hexren.net) Received: by helium.webpack.hosteurope.de running Exim 4.34 using asmtp helo=hexren.steenbuck.net) id 1CtBTc-0000xF-Ie; Mon, 24 Jan 2005 22:10:24 +0100 Date: Mon, 24 Jan 2005 22:10:23 +0100 From: Hexren X-Mailer: The Bat! (v1.62i) Business X-Priority: 3 (Normal) Message-ID: <12318458361.20050124221023@hexren.net> To: Kosta Kilim In-Reply-To: <20050124210109.GA14171@SDF.LONESTAR.ORG> References: <20050124210109.GA14171@SDF.LONESTAR.ORG> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: sshd port number ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Hexren List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 21:10:26 -0000 KK> Hello, KK> while reading some mail archives about SSH somebody argued KK> that sshd shouldn't be started on a port bigger than 1024, KK> since ports below that are priveleged ports. KK> How does that make sshd less secure if its on a port above KK> 1024 ? KK> Thanks KK> _______________________________________________ KK> freebsd-questions@freebsd.org mailing list KK> http://lists.freebsd.org/mailman/listinfo/freebsd-questions KK> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" --------------------------------------------- If ssh ever goes down, a user could start his own compromised version of ssh and do some nasty stuff. The same user could not do that if the connecting side would expect sshd to be on a privileged port because the system ensures that only procs running with superuser privileges can bind to a privileged port. Hexren