From owner-freebsd-chat@FreeBSD.ORG Thu Oct 2 10:42: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 5DE1C16A4B3 for ; Thu, 2 Oct 2003 10:42:49 -0700 (PDT) Received: from mta4.adelphia.net (mta4.adelphia.net [68.168.78.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id BACC243F85 for ; Thu, 2 Oct 2003 10:42:45 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([24.53.179.151]) by mta4.adelphia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20031002174247.ZWNC1341.mta4.adelphia.net@potentialtech.com>; Thu, 2 Oct 2003 13:42:47 -0400 Message-ID: <3F7C6394.6000805@potentialtech.com> Date: Thu, 02 Oct 2003 13:42:44 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Terry Lambert References: <3F7ABB8A.3050408@potentialtech.com> <3F7C5CE9.FDFD537A@mindspring.com> In-Reply-To: <3F7C5CE9.FDFD537A@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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:42:49 -0000 Terry Lambert wrote: > 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". Hmm ... why not do the same with "English"? "A method of encrypting complex ideas into a serious of sounds that can be represented by written symbols." I mean ... at that point, when somebody decrypts a message written in plaintext+english, you've got a _sure_ case. I mean, they circumvented TWO enctyption systems! -- Bill Moran Potential Technologies http://www.potentialtech.com