From owner-freebsd-current@FreeBSD.ORG Fri Mar 27 01:26:27 2009 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9306F106564A for ; Fri, 27 Mar 2009 01:26:27 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id 5B35A8FC14 for ; Fri, 27 Mar 2009 01:26:27 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.38] (S0106001372fd1e07.vs.shawcable.net [70.71.171.106]) (authenticated bits=0) by sippysoft.com (8.14.3/8.14.3) with ESMTP id n2R1Pxoi017553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 26 Mar 2009 18:26:00 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <49CC2B14.10408@FreeBSD.org> Date: Thu, 26 Mar 2009 18:25:40 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Julian Elischer References: <995845.90009.qm@web63905.mail.re1.yahoo.com> <49CA6754.4030302@elischer.org> In-Reply-To: <49CA6754.4030302@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: barney_cordoba@yahoo.com, Ruben de Groot , Ian FREISLICH , Chuck Robey , current@FreeBSD.org Subject: Re: Telnet root login X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Mar 2009 01:26:27 -0000 Julian Elischer wrote: >> Then use ssh and set "PermitRootLogin yes" in /etc/ssh/sshd_config > > this doesn't work if you are usinf a set of machines run from a central > machine using nc (netcat) to do scripted i/o through a telnet session on > the other machines (for example). > > The advantage of telnet is you can pipe nc straight into it. Dude, ssh with password-less master key on client and correct certificate on server in ~/authorized_keys2 is your friend. You can pipe right to ssh in scripts just fine and it's all nice and secure. You can also do other interesting things with port forwarding over ssl link. -Maxim