From owner-freebsd-security Fri Mar 29 5:52:59 2002 Delivered-To: freebsd-security@freebsd.org Received: from ns.tb.by (ns.tb.by [212.98.163.84]) by hub.freebsd.org (Postfix) with ESMTP id EE4C337B419 for ; Fri, 29 Mar 2002 05:52:54 -0800 (PST) Received: from franc ([10.20.1.109]) by ns.tb.by (8.11.3/8.11.3) with ESMTP id g2TDna543250; Fri, 29 Mar 2002 15:49:47 +0200 (EET) Date: Fri, 29 Mar 2002 15:38:42 +0200 From: Dmitry Shupilov X-Mailer: The Bat! (v1.47 Halloween Edition) Personal Reply-To: Dmitry Shupilov X-Priority: 3 (Normal) Message-ID: <192258005672.20020329153842@ns.tb.by> To: security@FreeBSD.ORG Cc: roam@ringlet.net Subject: Re[2]: SSH or Telnet? In-reply-To: <20020329143538.B340@straylight.oblivion.bg> References: <20020328201100.E6672-100000@cactus.fi.uba.ar> <72250498197.20020329133335@ns.tb.by> <20020329143538.B340@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Friday, March 29, 2002, 2:35:38 PM, you wrote: PP> Other than that, IPSec is a step towards a solution. If you don't like IPSec you can try VLAN's. VLAN's are what I use in my office to connect to critical hardware (routers, servers etc). But this solution is accomplished though the Cisco switches. The new Cisco switch support access lists per port (this is not Cisco advertisement:). PP> Still, I personally PP> would not trust telnet even in an IPSec environment, but then I *am* PP> somewhat paranoid :) Actually I use SSH2 in my network as well. -- Best regards, Dmitry mailto:root@ns.tb.by To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message