From owner-freebsd-chat@FreeBSD.ORG Wed Oct 1 07:50:20 2003 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00BB716A4BF for ; Wed, 1 Oct 2003 07:50:20 -0700 (PDT) Received: from hermes.pressenter.com (hermes.pressenter.com [69.58.128.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B81CC43FD7 for ; Wed, 1 Oct 2003 07:50:18 -0700 (PDT) (envelope-from nospam@hiltonbsd.com) Received: from [69.58.129.103] (helo=daggar.sbgnet.local) by hermes.pressenter.com with smtp (Exim 3.35 #1) id 1A4iIv-0001ot-00; Wed, 01 Oct 2003 09:50:13 -0500 Date: Wed, 1 Oct 2003 09:50:12 -0500 From: Stephen Hilton To: Bill Moran Message-Id: <20031001095012.7898752e.nospam@hiltonbsd.com> In-Reply-To: <3F7ABB8A.3050408@potentialtech.com> References: <3F7ABB8A.3050408@potentialtech.com> X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: jcw@highperformance.net cc: chat@freebsd.org Subject: Re: Ack! SYSTEMTYPE=WIN32 X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2003 14:50:20 -0000 On Wed, 01 Oct 2003 07:33:30 -0400 Bill Moran wrote: > Jason C. Wells wrote: > > On Tue, 30 Sep 2003, Bill Moran wrote: > > > > > >>Are you serious? ROT_13 isn't encryption, it's a Caption Amazing > >>Decoder Ring. > > > > What's wrong with ROT_13? Is there a sploit for it? > > I think it was born 'sploited. > > > I figure if the guys at MIT allow it, it must be just fine. That Sam > > Hartman is a sharp guy. Why do you ask? > > Is this the same ROT_13 that Netscape mail used to use? ... that I > (seriously) had a Spiderman decoder ring for when I was a kid? Am > I getting it confused with something else? > Bill, I am just guessing about Jasons methods, but here goes. The authentication _is_ secure for telnet using kerberos, then he encrypts the telnet session with the decoder ring ROT_13 because the data flowing through the connection is not that sensitive, just the login credentials are felt by the OP to need a real level of encryption. My 2 cents, Stephen Hilton nospam@hiltonbsd.com