From owner-freebsd-chat@FreeBSD.ORG Thu Oct 2 10:15:49 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 6B33516A4B3 for ; Thu, 2 Oct 2003 10:15:49 -0700 (PDT) Received: from firecrest.mail.pas.earthlink.net (firecrest.mail.pas.earthlink.net [207.217.121.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 954DC43FE1 for ; Thu, 2 Oct 2003 10:15:47 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfi2e.dialup.mindspring.com ([165.247.200.78] helo=mindspring.com) by firecrest.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1A572a-0005id-00; Thu, 02 Oct 2003 10:15:01 -0700 Message-ID: <3F7C5CE9.FDFD537A@mindspring.com> Date: Thu, 02 Oct 2003 10:14:17 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Moran References: <3F7ABB8A.3050408@potentialtech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4f42ba7020b7cab26c60bdc9c4032d173a8438e0f32a48e08350badd9bab72f9c350badd9bab72f9c cc: "Jason C. Wells" 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: Thu, 02 Oct 2003 17:15:49 -0000 Bill Moran wrote: > Jason C. Wells wrote: > > 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? It's a Caeser cipher with a periodicity of 13. The point is not to be cryptographically strong... it's to be able to claim that anyone who decodes the content is in violation of the DMCA. Therefore, you can, for example, post DeCSS in ROT-13, and if the MPAA or DVDA comes after you for the sources being a DMCA violation, you can point out that their decoding of the sources is a DMCA violation. I've personally been lobbying for a cryptographic type definition from IANA for a crypto system called "plaintext". 8-). -- Terry