---

I, JOHN J. HOY, hereby declare and state as follows:

1. I make this Reply Declaration in further support of Plaintiff DVD Copy Control Association's ("DVD CCA") application for a Preliminary Injunction for two reasons: first, to correct certain factual misstatements and reply to the contentions made in the Declarations and papers submitted on behalf of Defendants Andrew McLaughlin and Andrew Bunner in opposition to DVD CCA's application for a preliminary injunction; and second, to provide further clarification of the stringent measures taken by DVD CCA, and its predecessor, to secure the trade secrets of the CSS technology which it licenses. As stated in my previous Declaration submitted in support of DVD CCA's application for a preliminary injunction ("Hoy Decl."), I am the President of DVD CCA and have been intimately involved in all issues relating to the adoption of the DVD format and specifically in all aspects of the implementation and protection of CSS technology. (Hoy Decl., ¶¶ 1-4).

The Original "Hack" of CSS was Through the Xing License

2. Two postings on the Internet, one dated October 6, 1999 and one dated October 25, 1999, reveal that the original access to the CSS technology was a "hack" around the license issued by Xing Technology Corporation ("Xing"). (A true and correct copy of the October 6, 1999 posting is attached hereto as Exhibit A. A true and correct copy of the October 25, 1999 posting is attached hereto as Exhibit B.)

3. The October 6, 1999 posting appeared at http://mmadb.no/hwplus, the web site which, on information and belief, was authored by Jon Johansen, the original Norwegian hacker. That posting required the "object code" to be downloaded. Object code is a code that computers understand.¹ With respect to the information downloaded from this posting, performed the following tests to determine whether it included the Xing "master key." First, took a DVD disc of a motion picture and played it on the DVD drive of a personal computer ("PC") to determine that the PC and DVD drive actually worked. The motion picture played properly on the PC. Second, using the DeCSS program which had been posted on October 6, 1999, I copied the digital images from the DVD disc onto the hard drive of the same PC. Again, the motion picture played properly, thus proving that DeCSS could descramble the digital images from the DVD disc. Third, I then "zeroed out" (i.e., nullified) the Xing "master key" in the DVD ROM buffer memory and, using the same DeCSS program, copied the digital data from the DVD disc and the other "master keys" onto the hard drive of that PC. When I attempted to use the copied digital data, a message appeared on the computer screen stating that the motion picture could not be played. Finally, I "zeroed out" all of the other "master keys in the DVD ROBA buffer memory, but activated the Xing "master key" only. Using the same DeCSS program, copied the digital data from the DVD disc and the Xing key onto the computer's hard drive. When I attempted to play the motion picture from the hard drive this time, it played properly. From this experiment, I concluded that the October 6, l999 posting contained both the CSS technology and only the Xing "master key."

___________________

1 Programmers write computer programs in a form called "source code." The source code consists of a set of instructions in a particular language like "C" or "FORTRAN." Compilers change the source code into an intermediary form called "object code," which is understood by a particular type of computer. The object code is then transformed into a low-level language called machine language which the computer actually executes.

4. The October 25, 1999 posting (an anonymous posting to the Livid mailing list at http://livid.on.openprojects.net) contained "source code." Source code is the language in which programmers write computer programs. From looking at the text of this posting (without performing a test as that described in Paragraph 3 above), I can determine (i) that it contains the Xing "master key" and (ii) and that it does not contain any other "master key." I am informed and believe that the code posted on October 25, 1999 operates as a CSS descrambler module.

5. Thus, as of October 25, 1999, the date which DVD CCA alleges in its Complaint that CSS technology first appeared in source code form on the Internet (Complaint, ¶ 45) -- and the date which Frank A. Stevenson claims (through his Declaration filed on behalf or defendants Bunner and McLaughlin, see discussion at ¶¶ 6-14, infra) was the first date on which cryptanalysis of CSS ciphers was publicly disclosed on the Internet -- there was a posting of CSS source code which contained only the Xing "master key." I am not aware of any other posting of the CSS technology on the Internet as of October 25, 1999 which contained any of the other "master keys." Access to CSS technology was thus obtained in violation of the specific provision in the Xing end-user license "click wrap" agreement which prohibits reverse engineering. (See Reply Decl. of Chris Eddy, ¶ 7 and Ex. A).

Declaration of Frank A Stevenson

6. Declarant Frank A. Stevenson ("Stevenson") states that to the best of his knowledge, he is the "first [person] that publicly disclosed the cryptanalysis on the CSS ciphers. (Stevenson Decl., ¶ 3). Mr. Stevenson's Declaration demonstrates that both he, and others working to hack CSS through the Livid project (a forum whose sole purpose was "to provid[e] Video and DVD playback capabilities to the Linux computing platform", id., ¶ 4) knew, or had reason to know, that CSS was proprietary trade secret technology that was protected by a series of "master keys."

7. For example, as demonstrated in the Reply Declaration of Jonathan S. Shapiro, Esq. ("J. Shapiro Decl."), members of the Livid project were aware as early as July 25, 1999 that CSS technology -- the trade secrets that are at the heart of this action -- was protected by a series of "master keys" and that the only way to access the CSS encryption codes was to hack through those keys, each belonging to a company that had entered into a license agreement with DVD CCA's predecessor. (Hoy Decl., ¶¶ 14-15). On July 25, 1999, one member of the Livid project wrote:

I am new to this list, and with great interest, I read about your progress on CSS unlocking and decrypting.

There is one thing I don't understand. Why don't you take a look at the existing software decoders that are available for Windows? I've got installed 4 of them (XingDVD, WinDVD, Cinmaster engine, PowerDVD) and each one is capable of playing every CSS encrypted DVD I own. In theory it should be possible to take out the CSS decrypting code part and use it in the LiViD project. Even copyright reasons hold you back from re-using the code, it should help to learn a lot about the process.

(J. Shapiro Decl., ¶ 53) (emphasis added). To my knowledge, all of the software licensees of CSS technology, including Xing, require end users to enter a "click wrap" license which specifically prohibits reverse engineering.

8. Moreover, the Internet postings of those individuals who were developing and/or discussing the means to hack through the master keys to gain access to CSS technology, referred to in the Shapiro Reply Declaration, demonstrate that they knew, or had reason to know, that such actions were wrongful.

9. For example, postings on slashdot.org as early as July 1999 clearly establish the state of mind of the hacker community. The following is a sample of posts made on July 15, 1999:

With DVD all the decoding is done locally, and if the d[e]coding can be done in software (which it often is, under windows, anyway) than that code can be RIPPED and ported to other platforms. Period. The Law? F**k the law. Someone will do it regardless and post it to USENET and ftp servers in countries where US law is meaningless, and the SW will spread and no one will be able to stop it. The secret nature of DVD decoding is already doomed and has been since day one when software was released to do it. If they really wanted to keep it secret, they'd have had a better chance if they kept all the decoding in hardware. But it's too late now. The genie is out of the bottle. (by root at megami dot org) (emphasis in original).

My impression is that the decryption algorithms for DVD are kept as a big secret to prevent movie piracy (which as most of us know is becoming the next big thing on the net). In order for Linux to get a decoder, it would have to come from either (a) hardware or (b) some group who has access to the decryption scheme.... (by spam2(itheresistance.net) (emphasis added).

There is an incorrect perception that copyright and patent and RE [reverse engineering] laws are universal. They are not. If someone in say, Taiwan, or some other non-Berne non-WIPO country REs the code and posts it to the usenet, how is this illegal? Now I suppose it's illegal for Jo[e] US Citizen to download and use this code, but the genie will be out of the bottle so to say, and it will then be impossible to suppres [sic] the knowledge anymore. (by anonymous coward) (emphasis added).

Yes, it is true, we have now all the needed parts for software decoding of DVDs, but any software doing so will be illegal and/or non-free....

The information about CSS is obtained by reverse engineering some DVD software decoder. Reverse engineering is nearly every time prohibited by license agreements, and for example european law allows reverse engineering only for software compatibility issues. So the CSS source was not obtained in a legal way, and it is at least a very problematic issue if we may use this source however. I'm unsure if CSS is also protected by patents. (by kjuZ)debian dot org) (emphasis added).

I'm sure Matthew P. and the source codes 'creator' will be contacted to cease and desist distribution of the code. The anonymous source (who isn't entirely anonymous, as far as I know, as he made himself known on other forums), will be at the most risk here for legal problems. Best idea now is to download the code. Get it spread around as widely as possible. It may not be able to be used legally when all is said and done, but at least it will be out there for others to work with. (by Sontas) (emphasis added).

What are the laws regarding reverse engineering, specifically reverse engineering a piece of software that has a specific clause in it's usage license not to reverse engineer or dissasemble [sic] the code? Are there any ways around a reverse engineering clause of a software product? (by Sontas) (emphasis added).

. . . I don't see how Reing [reverse engineeringj the CSS mechanisms in a DVD player would be considered legal. You are not maintaining any kind of compatibility. The only way I can see it being able to be legal under that law [Norway] is to claim you did it for maintaining compatibility with other DVD authoring software. Even then, one could only legally RE the encryption algorithm used and perhaps where on the disc hone has to place the disc and title keys. (by Sontas) (emphasis added).

What if I buy a machine with software already installed? These are shipped ready-to-run, and don't present all the EULA screens that the setup programs offer. Nobody could prove I even saw a license agreement, let alone approved it. (by artg) (emphasis added).

The windows EULA says you cannot reverse engineer. It also says that if you do not agree to the terms of the agreement, you are entitled to a refund. How many people actually got refunds? If microsoft doesn't honor their side of the agreement, legally you don't have to either. (by nagumo@.linuxstart.com).

What are the laws of reverse engineering, specifically reverse engineering a piece of software that has a specific clause in it's usage license not to reverse engineer or dissasemble [sic] the code? (by r.e.wolffE).BitWizard.nl/).

I think criminal charges are up to 3 years in jail and $10,000 per violation. That would of course be for serious violations, or if someone was out to destroy you. (by anonymous coward) (emphasis added).

(J. Shapiro Reply Decl., at ¶¶ 18-22, 24-28).

10. Declarant Stevenson states that on or about October 25, 1999, anonymous post of CSS C source code was made to the Livid project mailing list. Stevenson posted a copy of this on his Web site. (Stevenson Decl., ¶ 14). Stevenson states that the "anonymous source" could not "be executed as a program" and did "not contain any player keys" (id., ¶ 7), a clear acknowledgement that the means to obtain the CSS technology was through one of the keys owned by the licensees of the CSS technology. (A portion of Stevenson's posting to the Internet, attached as Exhibit C to his Declaration, is titled "The Divide and conquer attack, Deviced and written by Frank A. Stevenson 26 Oct 1999 . . . Released under the GPL license.")

11. Stevenson then states that he posted a "break on the CSS cipher used for encrypting movie files" on October 27, 1999. (Id., ¶ 15). He states that this "attack reduced the workload for finding a CSS key used to encrypt an individual block of movie data . . ." (id.), thus again recognizing the importance of the "master keys" as the means to gain access.

12. On October 28, 1999, Stevenson made a post, titled "Working PlayerKey cracker," "describing a break on the player keys to the Livid mailing list," stating that "[t]his attack will enable a competent programmer to derive all 400 or so player keys from a single known player key in 5 to 10 minutes on an ordinary PC." (Id., ¶ 16 and Ex. E) (emphasis added).

13. On October 30, 1999, Stevenson made another post "describing an attack on the disk hash" to the Livid project. (Id., ¶ 17). He states: "This attack described a method for extracting a title key directly from this hash, thus negating the need for any player keys when viewing a DVD movie." (Id.) (emphasis added). Thus again, Stevenson recognizes that the purpose and intent of those hacking into to the CSS technology was to "negate" the need for the "master keys" which DVD CCA and its predecessor had put into place for the specific purpose of protecting the CSS technology -- the trade secrets at issue here.

14. Although Mr. Stevenson states that "[t]here are a variety of methods that can achieve the cracking of the encryption scheme without ever seeing or agreeing to a Xing license agreement," (id., ¶ 19), he fails to state any. In any event, that is beside the point. His Declaration clearly proves that he was aware that CSS was technology that was licensed pursuant to an agreement that contained anti-reverse engineering provisions and that the "master keys" were the means used to protect it.

Declaration of Defendant Andrew Bunner

15. Defendant Andrew Bunner submitted a Declaration in which he fails to state where he actually obtained the trade secrets which he disseminated on his web site. He states only that he became aware of the "deCSS program" on or about October 25, 1999 by reading and participating in discussions held on the slashdot.org web site. (Bunner Decl., ¶ 3-4). As set forth in Paragraphs 4-5 above, an October 25, 1999 posting of DeCSS included information that it came from the Xing software, a fact that has been discussed on slashdot.org. (See Shapiro Reply Decl., ¶¶ 48-96). In any event, as demonstrated above, as well as in the Shapiro Reply Declaration, the discussions on slashdot.org contained numerous references to the wrongful nature and questionable legality of the CSS hack. Given these facts, Bunner's statement that at the time he posted the DeCSS program on his web site, he had "no information suggesting that the 'deCSS' program contained any trade secrets" and had "no reason to believe the 'deCSS' program was not either properly reverse engineered or independently created" (id., ¶¶ 13-14) is not credible.

Defendant Andrew McLaughlin Fails to Submit Any Declaration

16. Defendant Andrew McLaughlin has submitted no Declaration explaining how he acquired the CSS trade secrets. McLaughlin's pre-litigation comments on his web site -- "Mark of the scofflaw! Here's my local copy of CSS decryption software, enjoy!" -- establish that he knew he was in possession of and was freely disseminating material that he had wrongfully obtained. (See Complaint, ¶ 50). That statement has now been replaced with "Here's the disputed code" and is followed by copies of the DeCSS program.

Declaration of David Wagner

17. Although Declarant David Wagner ("Wagner") states that he has worked extensively reporting "serious flaws" in the techniques used for encrypting credit card numbers and in the privacy codes of U.S. and European digital cellular phones (Wagner Decl., ¶¶ 5-7), and that he has been "closely watching this case" (id. ¶ 14), he has never made any contact with me, or to my knowledge, any employee of DVD CCA or its predecessor, any of the creators of CSS technology or any of the licensees of that technology to report the alleged weaknesses which he proclaims to have known. Similarly, I know of no academic research published by Mr. Wagner on the subject of CSS encryption technology. If Mr. Wagner was truly concerned that "as electronic commerce becomes more prevalent, criminals gain an increasing financial incentive to exploit security vulnerabilities in our critical systems" (id. at ¶ 8) and believed that "it is the scientific community's duty to study these issues and to report on systemic risks that the public at large may not be aware of," (id. at ¶ 10), he should have reported his concerns of the alleged weaknesses in CSS encryption to DVD CCA.

18. In contrast to Mr. Wagner's assertions, DVD CCA is not attempting to "ban[] research into DVD security systems" or to "ban[] the publication of the DVD security weaknesses which are the results of that research." (Id. at ¶ 14). DVD CCA would welcome such research. Rather, DVD CCA is seeking to stop something quite different -- the illegal publication of the trade secrets for the CSS technology which DVD CCA licenses. The publication of DVD CCA's trade secrets serves no academic or scientific interest. Instead, Defendants have published and distributed these trade secrets for one purpose only -- to enable Defendants and others to violate the intellectual property of the motion picture industry.

19. Mr. Wagner's Declaration in fact supports DVD CCA's assertion that the CSS technology is a trade secret. He states his "understanding . . . that the DVD security design relies in part on distributing software in an 'obscured' form -- hidden in locations that are not obvious." (Id. at ¶ 21 ) (emphasis added). Wagner states further:

. . . I am aware of tools and techniques which apparently allow interested parties to bypass the standard installation process and gain access to the DVD player software without ever seeing or agreeing to any license agreements that may restrict reverse engineering. I am also aware of a tool which purports to allow one to continue the standard installation process without agreeing to any license agreement (see, e.g., http://picosoft.freeservers.com /No License htm).

(Id., ¶ 27) (emphasis added). The fact that one must "bypass" a license agreement to gain access to the installation software indicates a conscious decision to evade one of the principal protection mechanisms required by DVD CCA to protect the trade secrets which it licenses.

20. Mr. Wagner criticizes CSS because it uses a 40-bit encryption system. (Id. at 25). However, at the time CSS technology was developed and put into place, the export laws of many industrialized countries, including the United States, prohibited the export of any encryption system that was longer than 40 bits. Because CSS technology is exported throughout the world, a security system longer than 40 bits would have been illegal.² Thus, the maximum encryption system permitted by law was put into place. Mr. Wagner does not state any additional facts to support his allegation that "CSS was extremely poorly designed" (id. at ¶ 31) and that there was "sloppy workmanship in the DVD security measures." (Id. at ¶ 32).

____________________

2 Indeed, Mr. Stevenson recognizes this fact in his November 8, 1999 posting to the Internet. attached as Exhibit A to his Declaration. He states: "CSS was designed with a 40 bit keylength to comply with US government export regulation, and as such it [is] easily compromised through brute force attacks (such are the intentions of export control)."

21. Mr. Wagner's conclusions about the effects of the "hack" of CSS technology are contradictory. On one hand, he states that "the ability to break the CSS revealed in October [1999] does not appear to make large-scale piracy significantly easier today." (Id. at 33). Yet, in the next paragraph, he states that "it is fundamentally impossible to secure software DVD players against copying and piracy by dedicated individuals. Even if the CSS had been designed properly, the unpleasant truth is that it will still be a straightforward cryptanalysis exercise to circumvent the DVD copy protection measures by technical means." (Id. at ¶ 34) Thus, Mr. Wagner again recognizes that the way to gain access to the trade secrets which DVD CCA seeks to protect in this action is through "circumvention," not by any proper means.

Declaration of John Gilmore

22. The Declaration of John Gilmore ("Gilmore Decl.") is premised on the incorrect statement that "[t]here are many legitimate reasons" for allowing one to use the DeCSS software for Windows and the "similar 'readdvd' software" for the Linux operating system to make copies of a DVD disc onto his or her hard drive by circumventing the products of CSS licensees. (Gilmore Decl. at ¶ 9-10). CSS is proprietary technology licensed by DVD CCA. The only proper way to gain access to that technology is by using the products properly licensed by DVD CCA and its predecessor.

23. Gilmore goes on to state that "[o]ne major reason [for making such copies] is to allow Linux developers and users to watch their DVDs on their non-Windows computers." (Id. at 10). Linux is an alternative operating system to Windows. It was developed as an "open" system which is available at no charge to the user. To date, no person or entity has taken a license from DVD CCA or its predecessor to use CSS in a Linux application. If a person or entity were prepared to take a license on the same terms as existing licensees, such a license would be granted. At that point, Linux users could lawfully view motion pictures on their non-Windows operating system. Until then, Linux users have no "right," via a "hack" around other software licenses, like the Xing license, to gain access to this proprietary technology.

24. Mr. Gilmore attempts to minimize the significance of the illegal activities of the Linux defendants by stating that the current state of technology does not support large-scale piracy. (Id. at ¶¶ 19-20). First, this argument virtually concedes that the actions of these defendants is illegal. Second, this argument ignores the prospect that sophisticated and well-funded entities can indeed use the stolen trade secrets to support large-scale piracy. Finally, the technology for the transmission of motion pictures over the Internet is developing quickly. The potential for large-scale piracy through that medium is overwhelming.

25. Mr. Gilmore purports to criticize the CSS system although he admits that he "does not yet have access to the actual specifications of the DVD Content Scrambling System." (Id. at ¶ 30). Like Wagner, his only real criticism of the CSS system appears to be that it is protected by a 40-bit key. As discussed above, the trade regulations of the United States and other industrialized countries prevented the export of an encryption product with more than 40 bits. DVD CCA and its predecessor complied with the governing regulations regarding security at the time CSS was developed and implemented.

26. Both Mr. Gilmore and Mr. Wagner appear to have a fundamentally flawed view as to the development and implementation of trade secrets. Gilmore states that "modern day encryption systems are shielded by law from scientific inquiry." (Id. at 36). Wagner states that "the DVD industry elected to keep its inner workings secret." (Wagner Decl., ¶ 26). The CSS technology was created under the strictest security for the very purpose of preserving trade secret protection. After its development, access to the technology was strictly limited to licensees who agreed to comply with the stringent security specifications set forth in the CSS License Agreement. (See Hoy Decl., ¶¶ 14-19; see also discussion at ¶¶ 24-27, infra).

27. Mr. Gilmore does get one thing right. He states: "Miscreants are free to discover and exploit weaknesses, whether to listen in on 'private' cell phone calls, to steal intellectual property, etc." (Gilmore Decl., ¶ 41). That is exactly the point of this lawsuit. The defendants in this action have gained access to DVD CCA's trade secrets with knowledge that this information has been gained illegally. The discussions on the Internet among the defendants and others about the "hack" of CSS does not have any semblance of an "educational" or "scientific" inquiry into encryption. Rather, the sustained comments of these defendants proves that the intent of this community was and is to misappropriate the trade secrets licensed by DVD CCA and to use those trade secrets to violate the copyright of the motion picture industry. As Mr. Wagner states in his Declaration: "It appears that, because there was no commercial entity creating DVD software for Linux, the programmers did it for themselves." (Wagner Decl., ¶ 26).

DVD CCA and its Predecessor Took Substantial Steps To Protect the Trade Secret Status of the CSS Technology.

28. As described in my Declaration submitted in support of DVD CCA's Application for a Preliminary Injunction, dated December 24, 1999, DVD CCA's predecessor began licensing CSS technology on our about October 31, 1996. (Hoy Decl., ¶ 14). A true and correct copy of the Amended and Restated CSS Interim License Agreement that each of the licensees of CSS has executed ("The CSS License Agreement") is attached hereto as Exhibit C.³ (See Hoy Decl., ¶¶ 14-19).

____________________

3 For reasons of confidentiality, the names of all companies mentioned in the Agreement have been redacted. Additionally, the CSS Agreement consists of both the CSS License Agreement and an agreement pertaining to specifications for the CSS technology. Because the latter agreement contains highly confidential proprietary information that is not at issue in this lawsuit, it is not attached.

29. Section 5.4 of the CSS License Agreement requires all licensees to comply with all applicable rules and regulations of the United States and other countries and jurisdictions "relating to the export or re-export of commodities, software and technical data insofar as they relate to the activities under this Agreement, and shall obtain an approval required for such rules and regulations whenever it is necessary for such export or re-export." At the time that DVD CCA's predecessor began licensing CSS technology, the United States and other industrialized countries provided that no exported product containing encryption technology could contain more than 40 bits (See ¶¶ 20, 25 supra).

30. The CSS License Agreement specifically prohibits licensees from reverse engineering the CSS technology. Section 5.3 of that agreement provides:

Licensee shall under no circumstances reverse engineer, decompile, disassemble or otherwise determine the operation of CSS Specifications, including, without limitation, any encryption/decryption or scrambling/descrambling algorithm or logic of CSS, except that Licensee may, to the minimum extent necessary for the purposes of testing, debugging, integration or tuning of Licensee's own CSS Compliant Product to ensure that it works in its intended operational environment with other CSS Compliant Products (the 'Analysis Purpose'), conduct performance or electrical analyses with respect to the operation of other CSS Compliant Products that form part of such intended operational environment ('Analysis'), subject to the following conditions:

(a) Licensee shall not perform any Analysis, in whole or in part, for the purpose of deriving or discovering CSS Specifications that have not been made available and licensed by DVD CCA to Licensee hereunder (the 'Derived Information').

(b) To the extent Licensee obtains Derived Information, inadvertently or otherwise, Licensee shall immediately notify DVD CCA, and upon instruction of DVD CCA, Licensee shall within ten (10) days thereafter return or destroy any portion of Derived Information that is not solely necessary for the Analysis Purpose and cease any use of same for any purpose.

(c) Subject to Section 5.3(b) above, the Derived Information: (i) shall only be used for the Analysis Purpose and for no other purpose; and (ii) shall be treated as confidential in the manner corresponding to the same type of information as specified in Section 5.2.

(d) Nothing herein shall be construed as an inducement for Licensee to reverse engineer any products of any CSS Licensee or third party.

(e) For purposes of this Section 5.3: (i) 'testing' shall mean a process of evaluating Licensee's CSS Compliant Product to ensure proper operation; (ii) 'debugging' shall mean a process of finding the cause of an error in a Licensee's or other's CSS Compliant Product, but not analysis for the purpose of exposing possible design features; (iii) 'integration' shall mean a process of evaluating the performance of Licensee's CSS Compliant Product in combination with other CSS Compliant Products to ensure that they properly operate together; and (iv) 'tuning' shall mean a process of evaluating and improving Licensee's CSS Compliant Products to work more efficiently with other CSS Compliant Products.

Clearly, the end users of the products manufactured by the licensees under the CSS Licensee Agreement can have no greater rights than the licensees have under the CSS License Agreement.

31.   Section 5.2 of the CSS License Agreement contains the confidentiality restrictions imposed on the licensees to protect the trade secret status of the CSS technology. The CSS License Agreement requires licensees to maintain the confidentiality of certain defined pieces of information, such as the algorithms and "master keys." As such, licensees are subject to a stringent set of rules to ensure the maintenance of confidentiality within the group of licensees:

(a) Among the safeguards taken is the requirement that only those licensees that absolutely need to know a particular algorithm and/or key are provided with such information. For example, a manufacturer of semiconductor chips for descrambling CSS content in stand-alone DVD players is provided with information necessary for manufacturing such chips but not with information concerning the scrambling process itself or the authentication between DVD drives and the descrambling module used for computer-based implementations. Companies that merely assemble parts and components produced by others may be required to be licensees in order to purchase such parts and components, but these companies are not provided with the proprietary CSS information at issue.

(b) The CSS License Agreement mandates that licensees only provide the proprietary CSS technology at issue to the strictest minimum number of licensee's employees who require access to the information, beginning with only three employees and expanding beyond three only upon notification to the licensor of the names of the additional employees Licensees who violate these requirements are subject to liquidated damages in the amount of $1 million per violation (with a cap based on profits made from the sale of licensed products).

(c) Licensees implementing authentication and descrambling functions in software are required to do so only in a manner that obscures the proprietary CSS technology at issue, so as to effectively frustrate anyone seeking to obtain such proprietary information. Specific means of accomplishing this protection requirement are provided to licensees to illustrate the types of measures to be taken and the level of technical skill that must be employed to defeat any such measures. Failure to abide by these operating restrictions can subject the licensee to injunctions prohibiting the sale of the product in which the failure occurs, through actions brought either by the licensor or by third party beneficiary content owners (motion picture companies that are licensees under the CSS License Agreement and have made copyrighted content available on DVD discs encrypted using CSS technology).

I declare under penalty of perjury that the foregoing is true and correct.

Dated: January 13, 2000
Morgan Hill, California

[Signature]

John J. Hoy

---

[3 pages.]

EXHIBIT A

[Fax header:   Jan-10 00 10:52AM; Pages 2, 3, 4]

                           readme DeCSS11.txt



******************************************
*                                        * 
*             DeCSS 1.1b                 *
*                                        *
******************************************

ASPI Problems:
If you get an error message saying:
"Could not load aspi layer", then please
try the aspi player included with DeCSS.

wnaspi32.w98.dll: Use this for Win98 :P
wnaspi32.w2k.dll: Use this for Win2k and NT.

(Remember to rename it to wnaspi32.dll!)

- Authors of DeCSS
10/06/99 - 06:27


























                                Page 1


----------------------------------------------------------------------




                           readme DeCSS12.txt


*****************************************
*                                       * 
*             DeCSS 1.2b                *
*                                       *
*****************************************
* 1.2.1b:                               *
* - Fixed an integer divide by zero bug *
*                                       *
* 1.2b:                                 *
*  - Added multiple selection of files  *
*  - Transfer Rate and ETA              *
*  - Checks if you have enough hd space *
*  - You can now merge vob files        *
*  - "Integer division by 0"-bug fixed  *
*                                       *
* 1.1b:                                 *
*  - First public release               *
*                                       *
#########################################
# - ASPI Problems                       #
#########################################
# If you get an error message saying:   #
# "Could not load aspi layer", then try #
# the aspi player included with DeCSS.  #
#                                       #
# wnaspi32.w98.dll: Use this for Win98  #
# wnaspi32.w2k.dll: Use this for Win2k  #
#                                       #
# Remember to rename it to wnaspi32.dll #
#                                       #
#########################################
# - How do I select audio stream?       #
#########################################
#                                       #
# You don't. DeCSS is just a decryptor, #
# nothing else. Copy all the files to a #
# video ts folder on your hd, and then  #
# try playing the movie.                #
#                                       #
#########################################
# - The aspect radio is weird?          #
#########################################
#                                       #
#   Same reason as above.               #
#                                       #
#########################################
|                                       |
| Credits/Greetings (in no part. order) |
| [ Canman, S0upaFr0g ]                 |
|                                       |
| - Authors of DeCSS                    |







                                Page 1


----------------------------------------------------------------------




                           readme DeCSS12.txt




| 10/09/99 - 18:22                      |
|                                       |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~







































                                Page 2

---

[8 pages. Oversized code characters and line wraps in original.]

EXHIBIT B

[Fax header:   Jan-10 00 10:52-54AM; Pages 5, 6, 7, 8/12, 9/12, 10/12, 11/12, 12/12]

[Handmarked "DeCSS 10/25"]

                                 CSSscrambleT.txt




unsigned int CSStab0[11]={5,0,1,2,3,4,0,1,2,3,4};

unsigned char CSStab1[256]=
{
	0x33,0x73,0x3b,0x26,0x63,0x23,0x6b,0x76,0x3e,0x7e,0x36,0x2b,0
x6e,0x2e,0x66,0x7b,
	0xd3,0x93,0xdb,0x06,0x43,0x03,0x4b,0x96,0xde,0x9e,0xd6,0x0b,0
x4e,0x0e,0x46,0x9b,
	0x57,0x17,0x5f,0x82,0xc7,0x87,0xcf,0x12,0x5a,0x1a,0x52,0x8f,0
xca,0x8a,0xc2,0x1f,
	0xd9,0x99,0xd1,0x00,0x49,0x09,0x41,0x90,0xd8,0x98,0xd0,0x01,0
x48,0x08,0x40,0x91,
	0x3d,0x7d,0x35,0x24,0x6d,0x2d,0x65,0x74,0x3c,0x7c,0x34,0x25,0
x6c,0x2c,0x64,0x75,
	0xdd,0x9d,0xd5,0x04,0x4d,0x0d,0x45,0x94,0xdc,0x9c,0xd4,0x05,0
x4c,0x0c,0x44,0x95,
	0x59,0x19,0x51,0x80,0xc9,0x89,0xc1,0x10,0x58,0x18,0x50,0x81,0
xc8,0x88,0xc0,0x11,
	0xd7,0x97,0xdf,0x02,0x47,0x07,0x4f,0x92,0xda,0x9a,0xd2,0x0f,0
x4a,0x0a,0x42,0x9f,
	0x53,0x13,0x5b,0x86,0xc3,0x83,0xcb,0x16,0x5e,0x1e,0x56,0x8b,0
xce,0x8e,0xc6,0x1b,
	0xb3,0xf3,0xbb,0xa6,0xe3,0xa3,0xeb,0xf6,0xbe,0xfe,0xb6,0xab,0
xee,0xae,0xe6,0xfb,
	0x37,0x77,0x3f,0x22,0x67,0x27,0x6f,0x72,0x3a,0x7a,0x32,0x2f,0
x6a,0x2a,0x62,0x7f,
	0xb9,0xf9,0xb1,0xa0,0xe9,0xa9,0xe1,0xf0,0xb8,0xf8,0xb0,0xa1,0
xe8,0xa8,0xe0,0xf1,
	0x5d,0x1d,0x55,0x84,0xcd,0x8d,0xc5,0x14,0x5c,0x1c,0x54,0x85,0
xcc,0x8c,0xc4,0x15,
	0xbd,0xfd,0xb5,0xa4,0xed,0xad,0xe5,0xf4,0xbc,0xfc,0xb4,0xa5,0
xec,0xac,0xe4,0xf5,
	0x39,0x79,0x31,0x20,0x69,0x29,0x61,0x70,0x38,0x78,0x30,0x21,0
x68,0x28,0x60,0x71,
	0xb7,0xf7,0xbf,0xa2,0xe7,0xa7,0xef,0xf2,0xba,0xfa,0xb2,0xaf,0
xea,0xaa,0xe2,0xff
};

unsigned char CSStab2[256]=
{
	0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x09,0x08,0x0b,0x0a,0
x0d,0x0c,0x0f,0x0e,
	0x12,0x13,0x10,0x11,0x16,0x17,0x14,0x15,0x1b,0x1a,0x19,0x18,0
x1f,0x1e,0x1d,0x1c,


                                      1 peeji [Japanese for "page"]


--------------------------------------------------------------------------------


                                CSSscrambleT.txt





	0x24,0x25,0x26,0x27,0x20,0x21,0x22,0x23,0x2d,0x2c,0x2f,0x2e,0
x29,0x28,0x2b,0x2a,
	0x36,0x37,0x34,0x35,0x32,0x33,0x30,0x31,0x3f,0x3e,0x3d,0x3c,0
x3b,0x3a,0x39,0x38,
	0x49,0x48,0x4b,0x4a,0x4d,0x4c,0x4f,0x4e,0x40,0x41,0x42,0x43,0
x44,0x45,0x46,0x47,
	0x5b,0x5a,0x59,0x58,0x5f,0x5e,0x5d,0x5c,0x52,0x53,0x50,0x51,0
x56,0x57,0x54,0x55,
	0x6d,0x6c,0x6f,0x6e,0x69,0x68,0x6b,0x6a,0x64,0x65,0x66,0x67,0
x60,0x61,0x62,0x63,
	0x7f,0x7e,0x7d,0x7c,0x7b,0x7a,0x79,0x78,0x76,0x77,0x74,0x75,0
x72,0x73,0x70,0x71,
	0x92,0x93,0x90,0x91,0x96,0x97,0x94,0x95,0x9b,0x9a,0x99,0x98,0
x9f,0x9e,0x9d,0x9c,
	0x80,0x81,0x82,0x83,0x84,0x85,0x86,0x87,0x89,0x88,0x8b,0x8a,0
x8d,0x8c,0x8f,0x8e,
	0xb6,0xb7,0xb4,0xb5,0xb2,0xb3,0xb0,0xb1,0xbf,0xbe,0xbd,0xbc,0
xbb,0xba,0xb9,0xb8,
	0xa4,0xa5,0xa6,0xa7,0xa0,0xa1,0xa2,0xa3,0xad,0xac,0xaf,0xae,0
xa9,0xa8,0xab,0xaa,
	0xdb,0xda,0xd9,0xd8,0xdf,0xde,0xdd,0xdc,0xd2,0xd3,0xd0,0xd1,0
xd6,0xd7,0xd4,0xd5,
	0xc9,0xc8,0xcb,0xca,0xcd,0xcc,0xcf,0xce,0xc0,0xc1,0xc2,0xc3,0
xc4,0xc5,0xc6,0xc7,
	0xff,0xfe,0xfd,0xfc,0xfb,0xfa,0xf9,0xf8,0xf6,0xf7,0xf4,0xf5,0
xf2,0xf3,0xf0,0xf1,
	0xed,0xec,0xef,0xee,0xe9,0xe8,0xeb,0xea,0xe4,0xe5,0xe6,0xe7,0
xe0,0xe1,0xe2,0xe3
};

unsigned char CSStab3[512]=
{
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,


                                      2 peeji


--------------------------------------------------------------------------------


                                CSSscrambleT.txt





	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,


                                      3 peeji


--------------------------------------------------------------------------------


                                CSSscrambleT.txt





	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
	0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff
};

unsigned char CSStab4[256]=
{
	0x00,0x80,0x40,0xc0,0x20,0xa0,0x60,0xe0,0x10,0x90,0x50,0xd0,0
x30,0xb0,0x70,0xf0,
	0x08,0x88,0x48,0xc8,0x28,0xa8,0x68,0xe8,0x18,0x98,0x58,0xd8,0
x38,0xb8,0x78,0xf8,
	0x04,0x84,0x44,0xc4,0x24,0xa4,0x64,0xe4,0x14,0x94,0x54,0xd4,0
x34,0xb4,0x74,0xf4,
	0x0c,0x8c,0x4c,0xcc,0x2c,0xac,0x6c,0xec,0x1c,0x9c,0x5c,0xdc,0
x3c,0xbc,0x7c,0xfc,
	0x02,0x82,0x42,0xc2,0x22,0xa2,0x62,0xe2,0x12,0x92,0x52,0xd2,0
x32,0xb2,0x72,0xf2,
	0x0a,0x8a,0x4a,0xca,0x2a,0xaa,0x6a,0xea,0x1a,0x9a,0x5a,0xda,0
x3a,0xba,0x7a,0xfa,
	0x06,0x86,0x46,0xc6,0x26,0xa6,0x66,0xe6,0x16,0x96,0x56,0xd6,0
x36,0xb6,0x76,0xf6,
	0x0e,0x8e,0x4e,0xce,0x2e,0xae,0x6e,0xee,0x1e,0x9e,0x5e,0xde,0
x3e,0xbe,0x7e,0xfe,
	0x01,0x81,0x41,0xc1,0x21,0xa1,0x61,0xe1,0x11,0x91,0x51,0xd1,0
x31,0xb1,0x71,0xf1,
	0x09,0x89,0x49,0xc9,0x29,0xa9,0x69,0xe9,0x19,0x99,0x59,0xd9,0
x39,0xb9,0x79,0xf9,
	0x05,0x85,0x45,0xc5,0x25,0xa5,0x65,0xe5,0x15,0x95,0x55,0xd5,0
x35,0xb5,0x75,0xf5,
	0x0d,0x8d,0x4d,0xcd,0x2d,0xad,0x6d,0xed,0x1d,0x9d,0x5d,0xdd,0
x3d,0xbd,0x7d,0xfd,
	0x03,0x83,0x43,0xc3,0x23,0xa3,0x63,0xe3,0x13,0x93,0x53,0xd3,0
x33,0xb3,0x73,0xf3,
	0x0b,0x8b,0x4b,0xcb,0x2b,0xab,0x6b,0xeb,0x1b,0x9b,0x5b,0xdb,0
x3b,0xbb,0x7b,0xfb,
	0x07,0x87,0x47,0xc7,0x27,0xa7,0x67,0xe7,0x17,0x97,0x57,0xd7,0
x37,0xb7,0x77,0xf7,
	0x0f,0x8f,0x4f,0xcf,0x2f,0xaf,0x6f,0xef,0x1f,0x9f,0x5f,0xdf,0
x3f,0xbf,0x7f,0xff


                                      4 peeji


--------------------------------------------------------------------------------


                                CSSscrambleT.txt




};

unsigned char CSStab5[256]=
{
	0xff,0x7f,0xbf,0x3f,0xdf,0x5f,0x9f,0x1f,0xef,0x6f,0xaf,0x2f,0
xcf,0x4f,0x8f,0x0f,
	0xf7,0x77,0xb7,0x37,0xd7,0x57,0x97,0x17,0xe7,0x67,0xa7,0x27,0
xc7,0x47,0x87,0x07,
	0xfb,0x7b,0xbb,0x3b,0xdb,0x5b,0x9b,0x1b,0xeb,0x6b,0xab,0x2b,0
xcb,0x4b,0x8b,0x0b,
	0xf3,0x73,0xb3,0x33,0xd3,0x53,0x93,0x13,0xe3,0x63,0xa3,0x23,0
xc3,0x43,0x83,0x03,
	0xfd,0x7d,0xbd,0x3d,0xdd,0x5d,0x9d,0x1d,0xed,0x6d,0xad,0x2d,0
xcd,0x4d,0x8d,0x0d,
	0xf5,0x75,0xb5,0x35,0xd5,0x55,0x95,0x15,0xe5,0x65,0xa5,0x25,0
xc5,0x45,0x85,0x05,
	0xf9,0x79,0xb9,0x39,0xd9,0x59,0x99,0x19,0xe9,0x69,0xa9,0x29,0
xc9,0x49,0x89,0x09,
	0xf1,0x71,0xb1,0x31,0xd1,0x51,0x91,0x11,0xe1,0x61,0xa1,0x21,0
xc1,0x41,0x81,0x01,
	0xfe,0x7e,0xbe,0x3e,0xde,0x5e,0x9e,0x1e,0xee,0x6e,0xae,0x2e,0
xce,0x4e,0x8e,0x0e,
	0xf6,0x76,0xb6,0x36,0xd6,0x56,0x96,0x16,0xe6,0x66,0xa6,0x26,0
xc6,0x46,0x86,0x06,
	0xfa,0x7a,0xba,0x3a,0xda,0x5a,0x9a,0x1a,0xea,0x6a,0xaa,0x2a,0
xca,0x4a,0x8a,0x0a,
	0xf2,0x72,0xb2,0x32,0xd2,0x52,0x92,0x12,0xe2,0x62,0xa2,0x22,0
xc2,0x42,0x82,0x02,
	0xfc,0x7c,0xbc,0x3c,0xdc,0x5c,0x9c,0x1c,0xec,0x6c,0xac,0x2c,0
xcc,0x4c,0x8c,0x0c,
	0xf4,0x74,0xb4,0x34,0xd4,0x54,0x94,0x14,0xe4,0x64,0xa4,0x24,0
xc4,0x44,0x84,0x04,
	0xf8,0x78,0xb8,0x38,0xd8,0x58,0x98,0x18,0xe8,0x68,0xa8,0x28,0
xc8,0x48,0x88,0x08,
	0xf0,0x70,0xb0,0x30,0xd0,0x50,0x90,0x10,0xe0,0x60,0xa0,0x20,0
xc0,0x40,0x80,0x00
};

void CSSdescramble(unsigned char *sec,unsigned char *key)
{
	unsigned int t1,t2,t3,t4,t5,t6;
	unsigned char *end=sec+0x800;

	t1=key[0]^sec[0x54]|0x100;


                                      5 peeji


--------------------------------------------------------------------------------


                                CSSscrambleT.txt





	t2=key[1]^sec[0x55];
	t3=(*((unsigned int *)(key+2)))^(*((unsigned int *)(sec+0x56)
));
	t4=t3&7;
	t3=t3*2+8-t4;
	sec+=0x80;
	t5=0;
	while(sec!=end)
	{
		t4=CSStab2[t2]^CSStab3[t1];
		t2=t1>>1;
		t1=((t1&1)<<8)^t4;
		t4=CSStab5[t4];
		t6=(((((((t3>>3)^t3)>>1)^t3)>>8)^t3)>>5)&0xff;
		t3=(t3<<8)|t6;
		t6=CSStab4[t6];
		t5+=t6+t4;
		*sec++=CSStab1[*sec]^(t5&0xff);
		t5>>=8;
	}
}

void CSStitlekey1(unsigned char *key,unsigned char *im)
{
	unsigned int t1,t2,t3,t4,t5,t6;
	unsigned char k[5];
	int i;

	t1=im[0]|0x100;
	t2=im[1];
	t3=*((unsigned int *)(im+2));
	t4=t3&7;
	t3=t3*2+8-t4;
	t5=0;
	for(i=0;i<5;i++)
	{
		t4=CSStab2[t2]^CSStab3[t1];
		t2=t1>>1;
		t1=((t1&1)<<8)^t4;
		t4=CSStab4[t4];
		t6=(((((((t3>>3)^t3)>>1)^t3)>>8)^t3)>>5)&0xff;
		t3=(t3<<8)|t6;
		t6=CSStab4[t6];
		t5+=t6+t4;


                                      6 peeji


--------------------------------------------------------------------------------


                                CSSscrambleT.txt





		k[i]=t5&0xff;
		t5>>=8;
	}
	for(i=9;i>=0;i--)
		key[CSStab0[i+1]]=k[CSStab0[i+1]]^CSStab1[key[CSStab0
[i+1]]]^key[CSStab0[i]];
}

void CSStitlekey2(unsigned char *key,unsigned char *im)
{
	unsigned int t1,t2,t3,t4,t5,t6;
	unsigned char k[5];
	int i;

	t1=im[0]|0x100;
	t2=im[1];
	t3=*((unsigned int *)(im+2));
	t4=t3&7;
	t3=t3*2+8-t4;
	t5=0;
	for(i=0;i<5;i++)
	{
		t4=CSStab2[t2]^CSStab3[t1];
		t2=t1>>1;
		t1=((t1&1)<<8)^t4;
		t4=CSStab4[t4];
		t6=(((((((t3>>3)^t3)>>1)^t3)>>8)^t3)>>5)&0xff;
		t3=(t3<<8)|t6;
		t6=CSStab5[t6];
		t5+=t6+t4;
		k[i]=t5&0xff;
		t5>>=8;
	}
	for(i=9;i>=0;i--)
		key[CSStab0[i+1]]=k[CSStab0[i+1]]^CSStab1[key[CSStab0
[i+1]]]^key[CSStab0[i]];
}

void CSSdecrypttitlekey(unsigned char *tkey,unsigned char *dkey)
{
	int i;
	unsigned char im1[6];
	unsigned char im2[6]={0x51,0x67,0x67,0xc5,0xe0,0x00};


                                      7 peeji


--------------------------------------------------------------------------------


                                CSSscrambleT.txt





	for(i=0;i<6;i++)
		im1[i]=dkey[i];

	CSStitlekey1(im1,im2);
	CSStitlekey2(tkey,im1);
}


































                                      8 peeji

---

[33 pages.]

EXHIBIT C

[Footer all pages: ]

Interim License Agreement                                                                  CONFIDENTIAL
                                                                    C: \WINDOWS\TEMP\CSSINTER . DOC

AMENDED AND RESTATED CSS INTERIM LICENSE AGREEMENT

This AMENDED AND RESTATED CSS INTERIM LICENSE AGREEMENT, including the related CSS PROCEDURAL AND AMENDED AND RESTATED TECHNICAL SPECIFICATIONS, (collectively, this "Agreement") is made and entered into as of ____________ (the "Effective Date") by and between:(i); [Blank                                                                                           ] ("Blank); and (ii) ______________, a ____________________ corporation having offices located ___________________ at ("Licensee"). This Agreement shall be effective as of the Effective Date provided that it is executed by the parties hereto.

RECITALS

A. [Blank] and [Blank] (as defined below) have developed a Contents Scramble System (as defined below) to provide reasonable security to the contents of DVD Discs and thereby provide protection for copyrighted content against unauthorized consumer copying, and have filed patent applications with respect to the Content Scramble System.

B. [Blank] and [Blank] intend to license the Contents Scramble System to a new independent entity which will administer such system.

C. The independent entity is expected to be established by [Blank], [Blank] and others in the DVD industry within several months.

D. During the period from the Effective Date until the establishment and operation of the entity, [Blank] has granted to [Blank] a license to rights to the Contents Scramble System and [Blank] will serve as the licensing agent for the Contents Scramble System to grant licenses to third parties which desire to implement such system in DVD products.

E. This Agreement: (i) is intended to be an interim agreement that is effective until the entity is established and makes available its standard license agreement; and (ii) sets forth the terms and conditions under which [Blank] will grant Licensee the right to implement the security system on its DVD products.

AGREEMENT

1. DEFINITIONS. In addition to the other capitalized terms used in this Agreement and in addition to the terms defined in the CSS Procedural Specifications (which terms shall have the meanings set forth in the Procedural Specifications), the following terms shall have the following meanings:

1.1 "Absolutely Necessary Claim" shall mean any claim(s) of patent(s) or patent application(s) are infringed by the manufacture, import, use or sale of CSS Compliant Products because: (i) the CSS Specifications pertaining to CSS are read on by such claim(s); or (ii) products that, solely because of the requirement to implement the CSS Specifications pertaining to CSS, cannot be manufactured, used, distributed, offered to be sold, sold, imported, or otherwise transferred without infringing such claim(s).

1.2 "Associate Licensee" shall mean any third party that enters into an agreement, containing substantially the same terms as those set out in Attachment D ("Associate License").

1.3 "Associate Licensee Reseller" shall mean an Associate Licensee entering an Associate License for the purpose of being authorized to purchase and resell Schedule 1 and Schedule 2 Products, subject to the redistribution requirements of the Associate License.

1.4 "Confidential Information" shall mean Proprietary Information that is either marked "confidential" or "proprietary" when disclosed in written form or indicated as "confidential" or n proprietary" when disclosed orally and confirmed in writing within thirty (30) days after such disclosure.

1.5 "Controlled Company" shall mean (i) any Majority-Owned Affiliate, and (ii) any other entity that controls, is controlled by, or is under common control with another entity. For purposes of this Section, "control" means possession, direct or indirect, of the power to direct or cause the direction of the management and policies of an entity with respect to the matters set out in this Agreement, whether through the possession of voting power or by contract encompassing such matters. In determining whether an entity is covered by (ii) above, where a Licensee's control does not extend to directing the commencement or termination of legal actions as described herein, "control" is not deemed to be present.

1.6 "CSS" or "Contents Scramble System" shall mean the Contents Scramble System developed by [Blank] and [Blank] and designed to provide reasonable protection for the contents of DVD Disks, as more fully described in the CSS Specifications, excluding any unrelated or independent technology incidentally referenced by or used with the CSS Specifications such as MPEG technology and DVD technology.

1.7 "CSS Compliant Products" shall mean DVD Products which are compliant with the CSS Specifications.

1.8 "CSS Licensee" shall mean any third party that enters into an agreement with where such agreement contains substantially the same terms as those set forth in this Agreement and is valid and in effect. CSS Licensees shall include [Blank] and [Blank] in each of their respective capacities in manufacturing, using, distributing, offering for sale, selling importing or otherwise transferring DVD Products.

1.9 "CSS Specifications" shall mean the documentation relating to CSS entitled "CSS Specifications" (including the Procedural Specifications and the Technical Specifications) that [Blank] makes available to Licensee pursuant to the Membership Categories selected by Licensee, as such documentation may be revised from time to time consistent with Sections 4.2 and 10.7 hereof.

1.10 "Disc IP" shall mean any copyright, trade secret, or other intellectual property inherent in the CSS Specifications pertaining to CSS or any patent claim(s) (including but not limited to any Absolutely Necessary Claims or Relatively Necessary Claims) relating to implementation of CSS in any DVD Disc.

1.11 "DVD Products" shall mean the following products if they incorporate any portion of CSS: DVD Players, DVD-ROM Drives, Descramblers, Authenticators, DVD Decoders (implemented in hardware as DVD Decoder Cards and/or in software as DVD Decoder Software), DVD Disc Formatters, DVD Discs and Integrated Products.

1.12 "Entity" shall mean the organization to administer CSS to be established by [Blank], [Blank] and other DVD industry members.

1.13 "Highly Confidential Information" shall mean Proprietary Information that is either marked "Highly Confidential Information" when disclosed in written form or indicated as "Highly Confidential Information" when disclosed orally and confirmed in writing within thirty (30) days after such disclosure. Such information shall be limited to information constituting or disclosing: (i) the algorithms used for scrambling, descrambling, authentication and key recovery; (ii) master, disc, title or authentication keys; and (iii) information for testing product compliance with CSS where such information makes use of or reveals information described in (i) or (ii).

1.14 "Integrated Product" shall mean a combination of any one or more of a DVD Player, DVD-ROM Drive, Descrambler, Authenticator, or DVD Decoder with any other product, device or component into a single integrated unit that permits, or that is designed for further integration into a product that permits, the transmission of unscrambled content in digital or analog format to any internal or external output or connection, provided that use of the term "Integrated Product" does not affect the obligations or provisions pertaining to any separately defined DVD Product. Integrated Products may include by way of example and not of limitation: (i) integration of DVD-ROM Drives or DVD Decoder Cards with or into computer systems; and (ii) integration of DVD-ROM Drives or DVD Players with or into television receivers and videocassette recorders. The term "Integrated Product" shall include a combination of products linked together through a form of common operation that controls the transfer of CSS Data among the products.

1.15 "Licensed Rights" shall mean all Absolutely Necessary Claims, copyrights, trade secret rights, and other proprietary rights in any jurisdiction, and all applications and registrations therefor in and to CSS (including the Proprietary Information), that (during the term of this Agreement) owns or has the right to grant licenses of the scope granted herein without the agreement of, or requirement for payment (or provision of other consideration) to any person or entity.

1.16 "Majority-Owned Affiliate" shall mean any corporation, partnership or other entity that, directly or indirectly, owns, is owned by, or is under common ownership with, Licensee, for so long as such ownership exists. For purposes of the foregoing, "own," "owned" or "ownership" shall mean holding ownership, or the right, to more than fifty percent (50%) of the voting stock or ownership interest entitled to elect a board of directors or a comparable managing authority.

1.17 "Proprietary Information" shall mean any and all information relating to CSS made available to Licensee directly by [Blank], by any other CSS License or pursuant to Section 5.3 prior hereto or during the term of this Agreement including, without limitation, CSS Specifications, software, hardware, firmware, documentation, designs, flow charts, technical data, outlines, blueprints, notes, drawings, prototypes, templates, systems, manuals, know-how, processes and methods of operation.

1.18 "Protected" shall mean a configuration in which a data stream or signal is not output except (i) via encrypted, scrambled, or otherwise secure link or method authorized hereunder either through a device's or component's authorized output or to the next component or device which in turn has an authorized output; or (ii) directly as uncompressed video data to a graphics subsystem via an internal computer path. For purposes of this definition, authorized outputs and methods hereunder are those compliant with requirements contained in Section 6.2 of the CSS Procedural Specifications, including any upgrades or modifications thereto. By way of example and not limitation, the following CSS Compliant Products, if so configured, would be considered to be Protected:

(a) A DVD Decoder Card incorporating MPEG decoding and any or all of the following outputs:

(i) NTSC with appropriate AGC and Colorstripe;

(ii) Computer Monitor SVGA (or other computer monitor RGB); or

(iii) Uncompressed digital video directed via an internal computer path to a computer graphic subsystem for display;

(b) DVD Decoder Software incorporating MPEG decoding and supporting the output described in subsection (a)(iii);

(c) A DVD Decoder which implements the interrogation or identification functions referenced in Section 6.2.8.2 of the CSS Procedural Specifications; and

(d) A DVD Player which meets the requirements of section 6.2.1 of the CSS Procedural Specifications.

1.19 "Relatively Necessary Claim" shall mean, any claim(s) of patent(s) or patent application(s), that: (i) are not Absolutely Necessary Claims; and (ii) with respect to which the implementation of all or any portions of the CSS Specifications pertaining to CSS involves a design-around to such patent claim(s) which would have a commercially significant effect on performance, manufacturability or manufacturing cost, although the cost of designing-around itself shall not be taken into account.

1.20 "Reseller" shall mean an entity that purchases Schedule 1 or Schedule 2 Products from a CSS Licensee for the purpose of reselling such products without modification and only to another CSS Licensee.

1.21 "Schedule 1 Product" shall mean a CSS Compliant Product licensed hereunder which:

(a) is not a Schedule 2 or 3 Product, or

(b) is

(i) an Authenticator, or

(ii) a Descrambler, or

(iii) a CSS Decoder or partial implementation thereof or otherwise is a device which has an output which is not permitted in a Schedule 2 or 3 Product, or

(c) is a DVD Disc Formatter.

1.22 "Schedule 2 Product" shall mean a CSS Compliant Product licensed hereunder which is not Protected and which outputs descrambled CSS Video Data only in decompressed form.

1.23 "Schedule 3 Product" shall mean (a) a CSS Compliant Product licensed hereunder which outputs CSS Data only in a Protected manner or (b) a DVD Disc.

1.24 "[Blank]" shall mean [Blank] Corporation and is a registered trademark thereof.

2. LICENSES FROM

2.1 Nonexclusive License. Subject to the terms and conditions of this Agreement, grants Licensee a royalty-free, non-exclusive, nontransferable right, under the Licensed Rights:

(a) to use and implement CSS to develop, manufacture and use CSS Compliant Products that are in the Membership Categories selected by Licensee in Exhibit "A", and to practice any methods necessary for the manufacture or use of such CSS Complaint Products; and

(b) according to Licensee's membership categories, to purchase, distribute, offer to sell, sell import and otherwise transfer CSS Compliant Products either made or received pursuant to authority hereunder only as follows:

(i) Schedule 1 Products only to CSS Licensees or to Associate Licensee Resellers;

(ii) Schedule 2 Products only to CSS Licensees or to Associate Licensees; or

(iii) Schedule 3 Products to any person or entity.

(c) to provide prototype or sample DVD Products incorporating CSS to prospective customers or retained test companies, in each case solely for evaluation in contemplation of purchase of such products or performance of specified testing of such products, as applicable, provided that Licensee (i) may not provide such customers or test companies with any CSS Confidential or Highly Confidential Information unless such information would be provided to companies subject to [Blank]'s CSS Non-Disclosure Agreement; and (ii) must have a written agreement with each such customer and test company that effectively protects the confidentiality of CSS Confidential and Highly Confidential Information by providing at least equivalent protections as are provided in [Blank] CSS Non Disclosure Agreement (Exhibit F).

(d) Licensee agrees not distribute, offer to sell, sell, import, or otherwise transfer any DVD Products that it makes or receives except in accordance with Sections 2. l(b) and (c) above.

2.2 Copyright License. Subject to the terms and conditions of this Agreement, including without limitation the confidentiality provisions of Section 5 .2, for any copyrightable information included in CSS Specifications, [Blank] grants Licensee a royalty-free, non exclusive, nontransferable copyright license to use and reproduce CSS Specifications for internal purposes solely in connection with the implementation of CSS as permitted under Section 2.1 hereof.

2.3 Right to Have Made. Licensee shall have the right under the licenses granted herein to have third parties make CSS Compliant Products or subparts thereof for the sole account of Licensee, but only if said CSS Compliant Products or subparts thereof

(a) are to be sold, used, leased or otherwise disposed of, by Licensee under the trademark, tradename, or other commercial indicia

(i) of Licensee or

(ii) of a person or entity to which Licensee is authorized by this Agreement to sell

(1) the CSS Compliant Product that is the subject of the "have made" agreement or

(2) an Intragated Product that is a CSS Compliant Product made using such CSS Compliant Product, and

(b) are made by such third parties using design specifications or manufacturing drawings supplied by Licensee.

Such third parties shall be required to be either CSS Licensees or subject to an applicable [Blank] CSS Non-Disclosure Agreement with [Blank] (Exhibit F) if such manufacture requires disclosure to such third parties of (1) Confidential Information or Highly Confidential Information; or (2) other information or materials from which Confidential Information or Highly Confidential Information could reasonably be derived. Licensee shall remain liable for such third parties' compliance with Sections 2.5, 4.2, 5.3, 5.4, 6.2, and 6.3 under this Agreement and with the Non-Disclosure Agreement, if applicable, where such third parties are not CSS Licensees. Such third parties shall receive no license, sublicense, or implied license.

2.4 Sublicenses to Majority-Owned Affiliates. Subject to the requirements of the following subsections (a) and (b), Licensee shall have the right to sublicense to any of its Majority Owned Affiliates, and such sublicensed Majority-Owned Affiliates shall be referred to elsewhere in this Agreement as "Permitted Sublicensees."

(a) Licensee shall have the right to sublicense to any of its Majority-Owned Affiliates  owned directly by Licensee ("Majority-Owned Subsidiaries"), at Licensee's sole discretion, any of Licensee's rights under Sections 2.1, 2.2 and 2.3 provided that: (i) Licensee notifies [Blank] of the identity of each Majority-Owned Subsidiary receiving a sublicense and the type of Confidential Information or Highly Confidential Information provided to such Majority-Owned Subsidiary; (ii) each such Majority-Owned Subsidiary receiving a sublicense shall abide by the terms of this Agreement with the same rights (without the right to grant any sublicense) and the same obligations as, including without limitation, the covenant not to sue and patent license offer provisions of Section 5.1 hereof, (iii) such sublicense coterminates with this Agreement and/or terminates at any time such Majority-Owned Subsidiary ceases to qualify as a "Majority Subsidiary"; and (iv) Licensee may sublicense only those rights for the Membership Categories to which currently belongs.

(b) Licensee shall further have the right to sublicense to any of its Majority-Owned Affiliates (other than Majority-Owned Subsidiaries) any of Licensee's rights under Sections 2.1, 2.2 and 2.3 provided that: (i) each such Majority-Owned Affiliate receiving a sublicense shall execute and deliver to . a written acknowledgment and agreement that such Majority-Owned Affiliate has read and agrees to abide by the terms of this Agreement which acknowledgement and agreement shall be in the form attached hereto as Exhibit "B"; and (ii) Licensee may sublicense only those rights for the Membership Categories to which Licensee currently belongs. (c) Licensee shall be responsible and liable jointly and severally for its Permitted Sublicensees' compliance with the terms and conditions of this Agreement.

2.5 No Sublicense or Implied Licenses. Except as set forth in Section 2.4, Licensee's licenses hereunder include no right to sublicense any rights hereunder. No products or services provided by Licensee give rise to any implied licenses to third parties. Licensee acknowledges and agrees that the licenses granted herein are the only licenses granted to Licensee, and that no other licenses are granted, expressly, by implication or estoppel now or in the future. All rights not expressly granted to Licensee under this Agreement in and to CSS and the Proprietary Information are reserved and retained by [Blank].

3. MEMBERSHIP CATEGORIES AND ADMINISTRATION FEE.

3.1 Selection of Membership Categories. Upon the execution of this Agreement, Licensee shall select one or more membership categories set forth in Exhibit "A" (the [Blank] "Membership Categories"). Licensee may from time to time add or delete Membership Categories upon providing [Blank] prior written notice and payment of the Administration Fee (as defined below) for each additional Membership Category in accordance with Section 3.2 hereof

3.2 Administration Fee. Concurrent with Licensee's selection of the Membership Categories pursuant to Section 3.1, Licensee shall pay [Blank], a nonrefundable sum of 1,000,000 Japanese Yen for each Membership Category selected by Licensee (the "Administration Fee") which fee shall be used to offset the costs associated with [Blank] administration of CSS. Licensee shall not be entitled to any refund in connection with any deletion of Membership Categories. As of June 1, 1997, [Blank] shall have the right to assess from time to time reasonable and nondiscriminatory increases to the Administration Fee as necessary to offset the costs associated with administration of CSS; provided that such increases shall not in the aggregate in any calendar year exceed three hundred percent of the Administration Fee. Unless Licensee shall have exercised its right to terminate this Agreement pursuant to Section 6. l(d) hereof, Licensee shall pay such assessments.

4. CSS SPECIFICATIONS.

4.1 Delivery of CSS Specification. Upon Licensee's selection of one or more Membership Categories in accordance with Article 3, payment of appropriate Administration Fee(s) and after the appropriate approval by the Japanese Government, [Blank] shall distribute to Licensee the portions of Proprietary Information and/or CSS Specifications appropriate to its Membership Category or Categories. In the event Licensee deletes any Membership Categories, Licensee shall within ten ( 10) days thereafter return such portions of Proprietary Information and/or CSS Specifications relevant to such deleted Membership Categories.

4.2 Compliance with CSS Specifications. Licensee shall comply with the CSS Specifications as may be amended by [Blank] from time to time. Each DVD Product shall comply with the version of the CSS Specifications which is in effect at the time such DVD Product is manufactured. With respect to any changes to the CSS Specifications made after the date on which this Agreement is entered into the following risks shall apply. All changes shall be notified to all CSS licensees and shall provide Licensee with sufficient information to incorporate the changes in its design and manufacture of CSS Compliant Products. All changes shall be applied on a non-discriminatory basis among all CSS Licensees. may make changes to clarify or amplify elements of the CSS Specifications in order to preserve essential functions of the CSS Specifications ("Emergency Changes"). Licensee shall implement an Emergency Change as soon as reasonably possible, taking into account the danger to Content Providers being addressed by the Emergency Change. It shall be presumed that Licensee shall implement an Emergency Change not later than 60 days from receipt of notice of the Emergency Change if it does not require a material change in product design or manufacturing processes.

Licensee shall implement all other changes to the CSS Specifications not later than eighteen (18) months from the date [Blank] notifies Licensee of a change in the CSS Specifications. [Blank] may request that the eighteen-month-time period be shortened with respect to a specific change in the CSS Specifications, and Licensee agrees not to unreasonably withhold its consent to such request. Licensee may request that such time period be extended with respect to a specific change in the CSS Specifications, and A agrees not to unreasonably withhold its consent to such request, provided that any such consent will not be effective without the further consent of all other CSS Licensees where the request is subject to the provisions of Section 10.7. The foregoing time periods for implementation of changes in the CSS Specifications shall not be interpreted or applied so as to alter any time limitations set forth in the CSS Procedural Specifications.

5. ADDITIONAL LICENSEE OBLIGATIONS.

5.1 Access to Intellectual Property.

(a) Absolutely Necessary Claim. Licensee shall not, and shall cause each of its Controlled Companies not to, assert any Absolutely Necessary Claim(s) allegedly contained in the portions of the CSS Specifications pertaining to CSS, against [Blank] or any CSS Licensee (including its Permitted Sublicensees) or vendor, distributor, purchaser or other person in the chain of distribution for the manufacture, use, distribution, offer to sell, sale, import, or other transfer of a CSS Compliant Product which was made under license from [Blank] provided that this Section 5.1(a) only applies to those aspects of such CSS Compliant Product which are required for compliance with CSS Specifications and which cannot be implemented without infringing (but for this covenant) the Absolutely Necessary Claim(s) and further provided that this Covenant shall not apply with respect to an entity which is asserting an Absolutely Necessary Claim against Licensee.

(b) Disc Immunity. Licensee shall not, and shall cause each of its Controlled Companies not to, assert any claim(s) based on Disc IP against any CSS licensee who is a Content Provider, Authoring Studio, or DVD Disc Replicator or vendor, distributor, purchaser or other person in the chain of distribution for the manufacture, use, distribution, offer to sell, sale, import, or other transfer of DVD Disc that: (i) is a CSS Compliant Product; and (ii) was made under license from [Blank] provided that (1) this paragraph only applies to those aspects of such DVD Discs which are present for the purpose of complying with the portions of the CSS Specifications pertaining to CSS; and (2) this section shall only apply to DVD Discs themselves, and shall not apply to any apparatus for the manufacture thereof.

(c) Termination of Suits.

(i) If Licensee or any of its Controlled Companies asserts any Absolutely Necessary Claim(s) or Disc IP claim(s) in violation of the above provisions, Licensee shall terminate or cause to be terminated such assertion of claim.

(ii) In the case of an entity which is not a Controlled Company but in which Licensee or any of its Controlled Companies holds any voting security or any other ownership interest (a "Partially Owned Company"), Licensee shall not knowingly vote, and shall cause each Controlled Company not to vote, any voting security or ownership interest in any such Partially Owned Company in favor of asserting any claim which Licensee would be prohibited from asserting hereunder. Licensee agrees to use reasonable efforts to vote, and use reasonable efforts to cause each Controlled Company to vote, all voting securities and ownership interests in each Partially Owned Company to terminate any such claim(s). The termination of any such claim(s) under Absolutely Necessary Claim(s) or Disc IP claim(s), as the case may be, shall relieve Licensee of all liability for voting in favor of such claim without knowledge that such claim(s) was under any Absolutely Necessary Claim(s) or Disc IP claim(s), as applicable.

(d) Patent License Offer. Licensee shall offer, and shall cause its Controlled Companies to offer, a patent license for any of its/their claims for which Relatively Necessary Claim(s) exist, provided that such license may be limited to Relatively Necessary Claim(s) that are within the scope of the other CSS Licensee's from [Blank]. Such license shall be made available on reasonable and non-discriminatory terms to any CSS Licensee in good standing and/or its Permitted Sublicensees. To the extent that a Relatively Necessary Claim that would otherwise be governed by this paragraph is subject to the Disc Immunity governed by Section 5.1(b), such Relatively Necessary Claim shall be governed by Section 5.1(b) rather than this paragraph.

(e) Applicability.

(1) The provisions of this Section 5.1 related to Absolutely Necessary Claims and Relatively Necessary Claims shall apply with respect to the CSS Specifications in effect on the date on which this Agreement is entered and to any subsequent revision to CSS Specifications where Licensee has specifically agreed in writing to apply Section 5.1 to such revisions.

(2) Subject to the terms of Section 6.2 hereof, the covenant shall remain in effect for the life of any patent issued throughout the world with a first priority date prior to or during the term of the license granted to Licensee under Article 2.

(3) Any executed patent license entered into pursuant to Section 5.1(d) shall survive the termination of this Agreement in accordance with its terms.

(4) Notwithstanding the termination of this Agreement, the obligation to offer a patent license under Section 5. l(d) shall continue after such termination with respect to CSS Compliant Products that were made prior to, or are in production as of, the date of such termination for a license period ending concurrently with the applicable permitted period of distribution set forth in Sections 6.2(a), (b), or (c) as the case may be.

5.2 Confidentiality.

(a) Permitted Use. Licensee and its Permitted Sublicensees shall use Proprietary Information, Confidential Information and/or Highly Confidential Information (and tangible embodiments of any of the foregoing) solely for purposes of its own implementation of CSS in accordance with the terms of this Agreement and the CSS Specifications, and shall not use any mentally-retained recollections thereof to circumvent or copy the methods disclosed in Proprietary Information or Confidential Information or to circumvent any obligations under this Agreement.

(b) Highly Confidential Information. Licensee and its Permitted Sublicensee shall maintain the confidentiality of Highly Confidential Information in the following manner:

(i) Licensee and its Permitted Sublicensees shall employ procedures for safeguarding Highly Confidential Information at least as rigorous as Licensee and/or its Permitted Sublicensees would employ for its own most highly confidential information, such procedures to include, at a minimum: (1) maintaining on Licensee's and/or Permitted Sublicensees' premises a secure location in which any and all Highly Confidential Information shall be stored; (2) such secure location shall be accessible only by Authorized Employees (as defined below); (3) Authorized Employees shall sign in and out each time such employees visit such secure location; and (4) when Highly Confidential Information is not in use, such information shall be stored in a locked safe at such secure location.

(ii) Licensee may disseminate Highly Confidential Information only to the strictest minimum possible number of full-time employees of Licensee or its Permitted Sublicensees: (1) who have an absolute need to know such Highly Confidential Information in order to enable Licensee or its Permitted Sublicensees to implement CSS in compliance with the CSS Specifications; (2) who are bound in writing by obligations of confidentiality sufficient to protect the Highly Confidential Information in accordance with the terms of this Agreement; (3) who, prior to the disclosure of such Highly Confidential Information, have: (x) been identified in writing by Licensee to [Blank]; and (y) read and executed the acknowledgment attached as Exhibit "C" hereto (a copy of such executed acknowledgement to be sent to [Blank] ("Authorized Employee"). Licensee and its Permitted Sublicensees shall at all times cause Authorized Employees to strictly abide by their obligations hereunder and shall use the same efforts to enforce the confidentiality obligations of each Authorized Employee after the termination of his/her employment as Licensee uses to enforce with respect to Licensee's own similarly confidential information provided that Licensee shall not use less than reasonable efforts in such enforcement. Licensee and its Permitted Sublicensees shall make all reasonable efforts to assist [Blank] in relation to any claim, action, suit, proceeding, or litigation with respect to the acts of any of its former employees. Notwithstanding any contrary provision, Licensee shall under no circumstances disseminate any DVD Keys (as defined in CSS Specifications) to more than three (3) Authorized Employees for each Membership Category to which Licensee is and is licensed entitled to disclosure of DVD Keys from [Blank] ("Key Employees"). Licensee may only substitute a Key Employee in the event of the death, permanent or long-term disability or resignation or termination of an existing Key Employee or reassignment of an existing Key Employee to a substantially different department, section, division or other type of business unit that is not involved in the development, manufacture or sale of CSS Compliant Product. Licensee shall inform [Blank] in writing prior to the substitution of any Key Employee.

(iii) Licensee shall not make any copies of any document containing Highly Confidential Information. Licensee may request [Blank] to provide Licensee with additional copies of such documents. [Blank] may, in its sole discretion, fulfill any such request, provided that [Blank] shall not unreasonably refuse to provide requested additional copies.

(c) Confidential Information. Licensee may disclose Confidential Information only to full-time employees of Licensee and/or its Permitted Sublicensees who have a reasonable need-to-know and are bound in writing by obligations of confidentiality sufficient to protect the Confidential Information in accordance with the terms of this Agreement. Licensee and/or its Permitted Sublicensees shall use the same degree of care, but no less than a reasonable degree of care, to avoid unauthorized disclosure or use of Confidential Information as such party employs with respect to its comparably important confidential information. Licensee may discuss or disclose Confidential Information with other CSS Licensees, provided such CSS Licensees are licensed to receive the same type of Confidential Information and are obligated in writing to treat the Confidential Information as if received directly from [Blank]. Furthermore, Licensee may disclose to potential customers or suppliers the fact that Licensee has obtained a license to CSS from [Blank] and show a certificate to such effect provided by to Licensee. Upon Licensee's written request to [Blank], [Blank] shall maintain the fact that such Licensee is a CSS Licensee confidential during the period prior to Licensee's public announcement of its DVD Product intentions or its actual marketing of a DVD Product, whichever is earlier. Except as provided in the immediately preceding sentence, [Blank] shall have the right to disclose to third parties the fact that Licensee has a license to CSS and the membership categories to which such license is applicable.

(d) Contact Person and Provision of CSS Information. Licensee shall designate a single Authorized Employee who shall receive all Confidential Information and Highly Confidential Information (the "Licensee Contact") disclosed by The initial Licensee Contact shall be the individual designated on Exhibit "C" hereto. Prior to the provision of any Highly Confidential Information to the Licensee Contact, such Licensee Contact shall have comPlied with all of his/her obligations under Section 5.2(b) hereof. Furthermore, prior to providing any Highly Confidential Information to the Licensee Contact, [Blank] shall provide the Licensee Contact a brief non-confidential description of the generic nature of such Highly Confidential Information. Within five (5) days after such notice, Licensee shall notify [Blank] in writing whether it desires to receive or decline to receive such Highly Confidential Information, provided that any decision to decline shall have no effect on any of Licensee's obligations under this Agreement and Licensee shall have no right or license whatsoever with respect to the declined portions of the Highly Confidential Information. Notwithstanding the foregoing, Licensee may waive its rights to receive [Blank]'s prior notice of the generic nature of Highly Confidential Information set forth above by notifying [Blank] of such waiver in writing.

(e) No Publication. Except as otherwise expressly provided in Sections 2.2 and 5.2, Licensee shall not publish, disseminate or otherwise disclose or make available Proprietary Information received hereunder to any person, firm or corporation without prior written consent of [Blank].

(f) Notification of Unauthorized Use or Disclosure. Licensee shall notify [Blank] in writing immediately upon discovery of any unauthorized use or disclosure of Proprietary Information, and will cooperate with [Blank] in every reasonable way to regain possession of Proprietary Information and prevent its further unauthorized use or disclosure.

(g) Disclosure Required by Law. In the event Licensee is required by law, regulation or order of a court or other authority of competent jurisdiction to disclose Confidential Information or Highly Confidential Information, Licensee shall notify [Blank] as promptly as possible, and shall, upon such [Blank] request, reasonably cooperate in challenging or restricting the scope of such required disclosure.

(h) Confidentiality Exceptions. The confidentiality restrictions contained in Sections 5.2(a), (b) and (c) herein shall not apply to information that Licensee can demonstrate: (i) is either Confidential or Highly Confidential Information which is or becomes generally known to the public through no breach of Licensee's obligations owed to [Blank] hereunder and which [Blank] failed to remove from public availability or to enjoin such public disclosure within ninety (90) days after the date such information is or becomes generally known as set forth above; or (ii) is or has been developed by Licensee's employees (whether independently or jointly with others) without having access (whether directly or through any intermediaries) to any such Confidential Information or Highly Confidential Information (or any translation, derivation or abstractions of Confidential Information or Highly Confidential Information) and without any breach of Licensee's obligations to [Blank] , provided that the confidentiality restrictions shall continue to apply to DVD Keys provided to Licensee.

(i) Prior Agreements. The obligations of this Section 5.2 shall apply to any and all disclosures of Proprietary Information to Licensee prior to the execution of this Agreement. This Agreement shall supersede any inconsistent provisions contained in any confidentiality agreement relating to CSS between the parties hereto including that certain Confidential Disclosure Agreement dated as of ______________.

5.3 Reverse Engineering. Licensee shall under no circumstances reverse engineer, decompile, disassemble or otherwise determine the operation of CSS Specifications, including, without limitation, any encryption/decryption or scrambling/descrambling algorithm or logic of CSS, except that Licensee may, to the minimum extent necessary for the purposes of testing, debugging, integration or tuning of Licensee's own CSS Compliant Product to ensure that it works in its intended operational environment with other CSS Compliant Products (the "Analysis Purpose"), conduct performance or electrical analyses with respect to the operation of other CSS Compliant Products that form part of such intended operational environment ("Analysis"), subject to the following conditions:

(a) Licensee shall not perform any Analysis, in whole or in part, for the purpose of deriving or discovering CSS Specifications that have not been made available and licensed by [Blank] to Licensee hereunder (the "Derived Information").

(b) To the extent Licensee obtains Derived Information, inadvertently or otherwise, Licensee shall immediately notify [Blank], and upon the instruction of Licensee shall within ten ( 10) days thereafter return or destroy any portion of Derived Information that is not solely necessary for the Analysis Purpose and cease any use of the same for any purpose.

(c) Subject to Section 5.3(b) above, the Derived Information: (i) shall only be used for the Analysis Purpose and for no other purposes; and (ii) shall be treated as confidential in the manner corresponding to the same type of information as specified in Section 5.2.

(d) Nothing herein shall be construed as an inducement for Licensee to reverse engineer any products of any CSS Licensee or third party.

(e) For purposes of this Section 5.3: (i) "testing" shall mean a process of evaluating  Licensee's CSS Compliant Product to ensure proper operation; (ii) "debugging" shall mean a process of finding the cause of an error in a Licensee's or other's CSS Compliant Product, but not analysis for the purpose of exposing possible design features; (iii) "integration" shall mean a process of evaluating the performance of Licensee's CSS Compliant Product in combination with other CSS Compliant Products to ensure that they properly operate together; and (iv) "tuning" shall mean a process of evaluating and improving Licensee's CSS Compliant Products to work more efficiently with other CSS Compliant Products.

5.4 Export. Licensee will comply with all applicable rules and regulations of the United States, Japan and other countries and jurisdictions relating to the export or re-export of commodities, software and technical data insofar as they relate to the activities under this Agreement, and shall obtain an approval required under such rules and regulations whenever it is necessary for such export or re-export. Licensee agrees that commodities, software and technical data provided under this Agreement are subject to restrictions under the export control laws and regulations of the United States, Japan and other countries and jurisdictions, as applicable, including but not limited to the U.S. Export Administration Act and the U.S. Export Administration Regulations and the Japanese Foreign Exchange and Foreign Trade Control Law, and shall obtain any approval required under such laws and regulations whenever it is necessary for such export or re-export.

6. TERM/TERMINATION.

6.1 Termination. This Agreement shall be effective upon the Effective Date and shall continue until earlier terminated in accordance with any of the following events:

(a) Breach. If a party hereto defaults on any of its obligations under this Agreement (the "Defaulting Party"), the other party hereto (the "Non-Defaulting Party") shall have the right to terminate this Agreement by written notice describing the nature of the default, wherein such notice shall automatically result in termination unless within thirty (30) calendar days of receiving such written notice of such default, the Defaulting Party remedies the default (the "Cure Period"). The provision of a Cure Period is not intended to imply that an acceptable remedy of a default is limited in any particular case to prospective activities. Notwithstanding the foregoing, the Non-defaulting Party shall have the right to immediately terminate the Defaulting Party upon notice without any Cure Period in the event of the Defaulting Party's material breach of Section 5.2 hereof. Notwithstanding the foregoing, (i) Eligible Licensees shall be entitled to equitable remedies as provided in Sections 9.2 and 9.4 without regard to the foregoing Cure Period; and (ii) the foregoing Cure Period shall not be interpreted or applied so as to extend any time limitations set forth in the CSS Procedural Specifications.

(b) Failure to Manufacture and Distribute CSS Compliant. If Licensee has failed to exercise the rights granted under Article 2 to manufacture and commercially distribute CSS Compliant Products: (i) within the first twelve (12) month period commencing upon the execution of this Agreement, provided that such period shall be eighteen (18) months if Licensee is a DVD Disc Formatter, or (ii) during any consecutive twelve (12) month period thereafter during the term of this Agreement, then [Blank] may terminate this Agreement upon thirty (30) days prior written notice to Licensee if Licensee continues to manufacture and commercially distribute CSS Compliant Products during such thirty (30) day period. For these purposes, Licensee shall be deemed to have failed to exercise the rights granted under Article 2 to manufacture and commercially distribute CSS Compliant Products only if neither Licensee, nor any other CSS Licensee for which Licensee has designed or manufactured to CSS Compliant Product, shall have manufactured and commercially distributed a CSS Compliant Product.

(c) Upon Establishment of the Entity. In the event the Entity is formed, [Blank] interests in this Agreement shall be automatically assigned to the Entity effective ten (10) days after the Entity first commences operations, and this Agreement shall thereafter continue in full force and effect (subject to Sections 6. l(a) and (b)) until the earlier of: (i) the effective date of a new agreement between Licensee and the Entity; (ii) the effective date of the termination of this Agreement pursuant to written notice provided by Licensee; or (iii) ninety (90) days after the effective date of [Blank]'s assignment of this Agreement to the Entity, unless this time period has been extended by the Entity, in which case this clause (iii) shall be deemed to be automatically and without any further action by any party be amended to the date established in the extension; and/or [Blank]

(d) Failure to Establish the Entity. In the event the Entity is not formed and operating as of October 1, 1997 ("Preliminary Target Date") or an applicable Extended Date as set forth below, [Blank] or Licensee may thereafter terminate this Agreement by sending the other party ninety (90) days prior written notice, in which case the provisions of Section 6.2(c) shall apply. Prior to the Preliminary Target Date, if reasonable terms to establish the Entity as soon as possible are being negotiated in good faith, then the date in this provision shall automatically be extended for a period of two months ("Extended Date") so that the right to terminate for failure to establish the Entity does not come into being. Prior to the Extended Date, if the Entity is not yet formed and operating but if reasonable terms to establish the Entity as soon as possible are being negotiated in good faith, said Extended Date shall be automatically extended for a further period of two months so that the right to terminate for failure to establish the Entity will not come into being. Such extensions will continue to be made in the same manner until the Entity is formed, provided that reasonable terms to establish the Entity as soon as possible are being negotiated in good faith. For purposes of the foregoing, automatic extension as aforesaid shall be deemed to occur, unless [Blank] gives written notice to the contrary not later that two (2) weeks prior to the Preliminary Target Date or Extended Date (as applicable). For purposes of the foregoing, the fact that any party to the negotiations takes a position with respect to one or more issues during the course of the negotiations or fails to reach an agreement with respect to one or more issues during the course of negotiations shall not constitute failure to negotiate in good faith on reasonable terms. If [Blank] gives Licensee notice that it is terminating this Agreement, [Blank] agrees that a similar notice will be provided to all CSS Licensees within a reasonable period of time before or after [Blank] provides such notice to Licensee.

6.2 Effect of Termination.

(a) Material Breach or Failure to Manufacture or Distribute CSS Compliant Products. If [Blank] terminates this Agreement pursuant to Section 6.1(a) or 6.1(b), all licenses granted by [Blank] to Licensee shall terminate. If Licensee terminates this Agreement pursuant to Section 6.1(a), the covenant not to sue granted by Licensee under Section 5. l(a) shall terminate, provided, however, Licensee agrees that [Blank] and the CSS Licensees, and their Permitted Sublicensees, for a period of ninety (90) days after termination, shall have the right, subject to the conditions of Section 2. l(d), to distribute all CSS Compliant Products that have been produced or are in production as of the date of Licensee's termination notice. If [Blank] terminates this Agreement pursuant to Section 6.1(a) or 6.1(b), the covenant not to sue granted by Licensee under Section 5.1 shall terminate, provided, however, that [Blank] and the CSS Licensees, and their Permitted Sublicensees, for a period of one (1) year after termination, shall have the right subject to the conditions of Section 2.1(d), to distribute all CSS Compliant Products that have been produced or are in production as of the date of [Blank] termination notice. Notwithstanding any of the foregoing, the covenant not to sue granted in Sections 5.1(b) and Section 5.1(c) with respect to Disc IP shall not terminate in any event.

(b) Upon Establishment of Entity. If this Agreement is terminated pursuant to Section 6.1(c): (i) all licenses granted by [Blank] to Licensee shall terminate, provided, however, that Licensee, for a period of ninety (90) days after termination, shall have the right, subject to the conditions contained in Section 2. l(d), to distribute all CSS Compliant Products that have been produced or are in production as of the date of [Blank] termination notice; and (ii) the covenant not to sue granted by Licensee under Section 5.1(a) shall terminate, provided, however, that [Blank] and the CSS Licensees, and their Permitted Sublicensees, for a period of ninety (90) days after termination, shall have the right, subject to the conditions of Section 2.1(d), to distribute all CSS Compliant Products that have been produced or are in production as of the effective date of termination. Notwithstanding any of the foregoing, the covenant not to sue granted in Sections 5.1(b) and Section 5.1(c) with respect to Disc IP shall not terminate in any event.

(c) Upon Failure to Establish the Entity. If this Agreement is terminated pursuant to Section 6.1(d): (i) all licenses granted by to [Blank] Licensee shall terminate, provided, however, that Licensee, for a period of eighteen (18) months after termination, shall have the right, subject to the conditions of Section 2. l(d), to distribute all CSS Compliant Products that have been produced or are in production as of the date of [Blank] termination notice; and (ii) the covenant not to sue granted by Licensee under Section 5.1 (a) shall terminate, provided, however, that [Blank] and the CSS Licensees, and their Permitted Sublicensees, for a period of eighteen (18) months after termination, shall have the right, subject to the conditions of Section 2.1(d), to distribute all CSS Compliant Products that have been produced or are in production as of the date of termination. [Blank] agrees that, after such notices have been provided to CSS Licensees, it will not itself engage in any act that would have been permitted pursuant to this Agreement but would be prohibited to a Licensee whose license has been terminated pursuant to Section 6.1(d). Notwithstanding any of the foregoing, the covenant not to sue granted in Sections 5.1(b) and Section 5.1(c) with respect to Disc IP shall not terminate in any event.

6.3 Return of Materials. Within thirty (30) days after termination of this Agreement, Licensee shall either: (i) return all Proprietary Information to [Blank]; or (ii) destroy all Proprietary Information in its possession and certify such destruction in writing to [Blank] unless: (a) Licensee has then executed a license agreement for CSS with the Entity; and (b) Licensee sends written notice to [Blank] certifying that Licensee has entered into such agreement.

6.4 Survival. The terms of Sections 1, 5.1 (subject to Sections 6.2(a)-(c)), 5.2, 5.3, 5.4, 6.2 and 6.3 and Articles 7. 8. 9 and 10 shall survive the termination of this Agreement.

7. OWNERSHIP. All Proprietary Information and media containing Proprietary Information as provided by to Licensee shall remain the property o' or its licensors. Except as provided in Article 2, this Agreement does not give Licensee any license or other right to the Proprietary Information.

8. DISCLAIMER AND LIMITATION OF LIABILITY.

8.1 Disclaimer. ALL PROPRIETARY INFORMATION IS PROVIDED "AS IS." [Blank] MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, AND EXPRESSLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND ANY EQUIVALENTS UNDER THE LAWS OF ANY JURISDICTION THAT MIGHT ARISE FROM THE PROPRIETARY INFORMATION OR LICENSEE'S IMPLEMENTATION OR ATTEMPTED IMPLEMENTATION OF SUCH INFORMATION OR CSS. [Blank] FURTHER DISCLAIMS ANY WARRANTY THAT CSS AND/OR THE CONTENTS OF THE PROPRIETARY INFORMATION, OR ANY PRODUCT IMPLEMENTING CSS OR SUCH PROPRIETARY INFORMATION. IN WHOLE OR IN PART, WILL BE FREE FROM INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY OR PROPRIETARY RIGHTS

8.2 Limitation of Liability. SUBJECT TO SECTION 10.8, [Blank] OR [Blank], OR THEIR RESPECTIVE DIRECTORS, OFFICERS, OR EMPLOYEES (COLLECTIVELY, THE "AFFECTED PARTIES") SHALL NOT BE LIABLE TO LICENSEE FOR ANY DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR PUNITIVE DAMAGES ARISING OUT OF ANY CAUSE OF ACTION RELATING TO THIS AGREEMENT, OR BASED ON MAKING, USING, SELLING OR IMPORTING ANY PRODUCTS OF LICENSEE THAT IMPLEMENT PROPRIETARY INFORMATION OR CSS, WHETHER UNDER THEORY OF CONTRACT, TORT, INDEMNITY, PRODUCT LIABILITY OR OTHERWISE. TO THE EXTENT THAT ANY COURT OF COMPETENT JURISDICTION RENDERS JUDGMENT AGAINST [Blank] NOTWITHSTANDING THE ABOVE LIMITATION, [Blank] TOTAL [Blank] LIABILITY TO LICENSEE IN CONNECTION WITH THIS AGREEMENT OR CSS SHALL IN NO EVENT EXCEED THE AMOUNTS OF MONEY RECEIVED BY MEI FROM LICENSEE UNDER THIS AGREEMENT. THIS LIMITATION OF LIABILITY SHALL NOT BE CONSTRUED TO LIMIT OR RELIEVE [Blank] OR TOSHIBA, RESPECTIVELY, FOR ANY BREACH OF ITS OBLIGATIONS IN ITS CAPACITY AS A CSS LICENSEE.

9. REMEDIES.

9.1 Indemnification. Licensee shall indemnify and hold, in their roles as developers and licensors of CSS, [Blank] and their respective Controlled Companies, each of their respective officers, directors and employees, harmless from and against any and all any claims, actions, suits, proceedings or litigation and any losses, deficiencies, damages, liabilities, costs and expenses including without limitation, reasonable attorneys' fees and all related costs and expenses, to be paid or otherwise incurred in connection with the defense of any claim, action, suit, proceeding or litigation ("Claims") which result from: (i) any breach of any covenant, agreement, representation and warranties herein by Licensee, its employees, former employees who had access to Confidential Information or Highly Confidential Information pursuant to this Agreement, provided that Licensee's indemnity with respect to acts of former employees shall be limited to circumstances in which Licensee has failed to comply with its obligations as to former employees pursuant to Section 5.2(b)(ii) hereof; (ii) Licensee's manufacture, sale or use of any DVD Products, provided, that such indemnity shall not extend to: (a) any Claim that the CSS Specifications infringe the intellectual property rights of any third parties, or (b) any Claim or any portions thereof that is independently attributable to the terms of the CSS Specifications themselves; and/or (iii) Licensee's activities under Section 5.3.

9.2 Equitable Relief. Licensee and [Blank] recognize and agree that due to the unique nature of certain provisions hereof and the lasting effect of and harm from a breach of such provisions, including making available the means for widespread unauthorized copying of copyrighted content intended to be protected using CSS, in the event that Licensee breaches its obligations under Section 2.1, 2.3, 2.5, 4.2, 5, or 10 hereof; money damages alone will not adequately compensate an injured party, including an injured Eligible Licensee pursuant to Section 9.4, and that injury to such party will be irreparable. Licensee and [Blank] therefore agree that, in addition to all other remedies available to the injured party at law, in equity, by agreement or otherwise, the injured party, including an Eligible Licensee pursuant to Section 9.4, upon showing to the relevant court's satisfaction that applicable factors other than the fact that harm will be irreparable and that monetary damages are not sufficient to remedy the injury have been fulfilled, shall be entitled to specific performance or other temporary, preliminary, or permanent injunctive or equitable relief including corrective actions appropriate to the circumstances for the enforcement of any such obligation (whether or not there have been commercial sales of products subject to the requested relief).

9.3 Specific Remedies. Licensee acknowledges that due to the critical importance of maintaining the integrity of CSS and the inability to calculate the damage to CSS users in the event of any material breach of Section 5.2, , in addition to any other remedies in equity, but in lieu of any and all other claims for monetary damages, may recover liquidated damages for each material breach from Licensee in the amount of one million U.S. dollars ($1,000,000), provided that the parties agree that Licensee may request and the court may grant such request that this amount be reduced to take account of the fact that Licensee brought the breach to [Blank]'s attention in a timely and reasonable manner. For purposes of this Section 9.3, a series of substantially related events shall constitute a single material breach. For purposes of this Section 9.3, the following is a non-exclusive list of circumstances in which there is no material breach of Section 5.2: (1) if no Confidential Information or Highly Confidential Information was released to a third party not permitted hereunder to have such information or could reasonably have been expected to have been released to such third party as a result of the breach; (2) if Licensee maintains an internal program to assure compliance with Section 5.2 (including a program to assure maintenance of confidentiality of information for purposes in addition to compliance with this Agreement), the breach was inadvertent or otherwise unintentional, and the breach did not have a material adverse effect on the integrity or security of CSS; or (3) if Licensee brought the breach to [Blank]'s attention in a timely manner as required by this Agreement and such breach did not have a material adverse effect on the integrity or security of CSS.

9.4 Third Party Beneficiary Rights. The parties hereto acknowledge and agree that the compliance of Licensee, other CSS Licensees, and Associate Licensees with the terms of the licenses granted by this Agreement or the Associate License, as applicable, is essential to maintain the integrity and security of the Contents Scramble System in order to protect prerecorded motion pictures contained on DVD Discs. As part of the consideration of the licenses granted herein, Licensee, for itself and its Permitted Sublicensees, hereby confers a third-party beneficiary right upon certain CSS Licensees ("Eligible Licensees") that fall into one of two classes: (i) Content Providers ("Eligible Content Providers") or (ii) manufacturers of CSS Compliant Products other than DVD Discs ("Eligible Implementers"), in order to enforce certain of Licensee's obligations, subject to the following conditions:

(a) Either an Eligible Content Provider who has commercially released one or more prerecorded motion pictures on DVD Disc or an Eligible Implementer who has commercially released one or more CSS Compliant Products other than DVD Discs shall be entitled to initiate or institute a claim or action ("Beneficiary Claim") to enforce only those obligations of Licensee specified as follows (collectively, the "Eligible Obligations"): (i) for any Beneficiary Claim initiated by Eligible Content Providers, Licensee's obligations under Section 2.1 [Nonexclusive License], 2.3 [Right to Have Made], 2.4 [Sublicenses], 2.5 [No Sublicense or Implied Licenses], 4.2 [Compliance with Specifications], 5.1 [Access to Intellectual Property], 5.2 [Confidentiality], 5.3 [Reverse Engineering], 9.2 [Equitable Relief], 9.4(d) [Settlement Restrictions] and Section 10 [Miscellaneous] and including any equivalent provisions contained in any Associate License (Exhibit D); and (ii) for any Beneficiary Claim initiated by Eligible Implementers, Licensee's obligations under Section 4.2 [Compliance with Specifications] solely as such obligations pertain to Section 5.4 [Non alteration of the Secured Disc Key Set] and Section 6.3 [Motion Picture Scrambling] of the CSS Procedural Specifications, Section 5.1 [Access to Intellectual Property] and Section 9.4(d) [Settlement Restrictions] . Each Eligible Licensee who has not initiated the Beneficiary Claim but falls into the same class of Eligible Licensee as the initiating Eligible Licensee pursuant to this Section 9.4, shall be eligible to join such Beneficiary Claim. The remedies for any Beneficiary Claim shall be limited to equitable relief provided under Section 9.2, subject to Section 9.5.

(b) Prior to initiating or instituting any Beneficiary Claim against Licensee ("Defendant Licensee"), an Eligible Licensee ("Plaintiff Licensee") shall provide MEI notice and consultation reasonable under the circumstances regarding a proposed Beneficiary Claim; provided that such consultation with [Blank] shall not affect an Eligible Licensee's complete discretion in initiating such a Beneficiary Claim. Such Eligible Licensee shall further provide [Blank] with notice of actual filing of a Beneficiary Claim and upon [Blank]'s request, any copies of material documents to be filed in Plaintiff Licensee's initiation or pursuit of such Beneficiary Claim. [Blank] shall cooperate reasonably with such Eligible Licensee in providing appropriate and necessary information in connection with the Beneficiary Claim to the extent that such cooperation is consistent with the preservation of the integrity and security of CSS. Documents provided to under this Section 9.4(b) shall not include any documents filed or to be filed under seal in connection with such Beneficiary Claim.

(c) [Blank] shall provide all Eligible Content Providers or Eligible Implementers, as the case may be, with prompt notice of Plaintiff Licensee's Beneficiary Claim against Defendant Licensee (a "Claim Notice") in accordance with Section 10.6. Within sixty (60) days of the date of mailing of a Claim Notice, all such Eligible Licensees shall elect whether to join in such Beneficiary Claim, and the failure of any such Eligible Licensee to provide written notice to [Blank] of such election and to join in such Beneficiary Claim within such sixty (60) day period shall be deemed a waiver of such Eligible Licensee's third party beneficiary right under this Section 9.4 with respect to all Beneficiary Claims against such Defendant Licensee arising out of the alleged breach by such Defendant Licensee raised in such Beneficiary Claims. Plaintiff Licensee shall support, and Defendant Licensee shall not oppose, any motion to intervene by such Eligible Licensees or [Blank] electing to join such Beneficiary Claim within such sixty (60) day period. Neither an Eligible Licensee's failure to notify or consult [Blank] with or provide copies of documents to as [Blank] required by Section 9.4(b), nor [Blank]'s failure to give notice under this Section 9.4(c) shall be a defense against any Beneficiary Claim or grounds for a request to delay the granting of any preliminary relief requested.

(d) Eligible Licensees shall have no right to, and Licensee agrees that it will not, enter into any settlement that: (i) amends any material term of this Agreement or of the Associate License (Exhibit D); (ii) has a material adverse effect on the integrity and/or security of CSS; or (iii) impacts any of [Blank]'s rights in and to CSS or any intellectual property right embodied therein unless [Blank] shall have provided prior written consent thereto.

(e) NOTWITHSTANDING SECTION 10.4(b), LICENSEE AGREES THAT ALL BENEFICIARY CLAIMS INSTITUTED UNDER THIS SECTION 9.4 SHALL BE GOVERNED BY AND CONSTRUED IN ACCORDANCE WITH THE LAWS OF THE STATE OF CALIFORNIA, EXCLUDING THAT BODY OF LAW RELATING TO CONFLICTS OF LAW PRINCIPLES, AND SHALL BE CONDUCTED IN FEDERAL AND STATE COURTS LOCATED IN ANY COUNTY IN THE STATE OF CALIFORNIA AND HEREBY IRREVOCABLY CONSENTS TO (i) THE EXCLUSIVE JURISDICTION AND VENUE IN THE FEDERAL AND STATE COURTS LOCATED IN THE STATE OF CALIFORNIA; AND (ii) THE SERVICE OF PROCESS OF SAID COURTS IN ANY MATTER ARISING OUT OF THIS SECTION 9.4 BY PERSONAL DELIVERY OR BY MAILING OF PROCESS BY REGISTERED OR CERTIFIED MAIL, POSTAGE PREPAID, AT THE ADDRESSES AS SPECIFIED IN THIS AGREEMENT OR TO THE AGENT REQUIRED BY SECTION 10.4(c). LICENSEE WAIVES ANY OBJECTION TO THE JURISDICTION, PROCESS, AND VENUE OF ANY SUCH COURT, AND TO THE EFFECTIVENESS, EXECUTION, AND ENFORCEMENT OF ANY ORDER OR JUDGMENT (INCLUDING, BUT NOT LIMITED TO, A DEFAULT JUDGMENT) OF SUCH COURT PERTAINING TO THIS AGREEMENT, TO THE MAXIMUM EXTENT PERMITTED BY THE LAW OF THE PLACE WHERE ENFORCEMENT OR EXECUTION OF ANY SUCH ORDER OR JUDGMENT MAY BE SOUGHT AND BY THE LAW OF ANY PLACE WHOSE LAW MIGHT BE CLAIMED TO BE APPLICABLE REGARDING THE EFFECTIVENESS, ENFORCEMENT, OR EXECUTION OF SUCH ORDER OR JUDGMENT, INCLUDING PLACES OUTSIDE OF THE STATE OF CALIFORNIA AND OF THE UNITED STATES.

9.5 Nothing contained in Section 9.2 or Section 9.4 is intended to limit remedies or relief available pursuant to statutory or other claims that a CSS Licensee may have under separate legal authority.

10. MISCELLANEOUS.

10.1 Entire Agreement. This Agreement, the exhibits hereto and the CSS Specifications constitute the entire Agreement between the parties hereto and supersede all oral or written agreements, either entered prior to or contemporaneously with this Agreement. Subject to Section 10.7, this Agreement may not be modified except by written agreement dated subsequent to the date of this Agreement and signed by both parties.

10.2 Assignment. The licenses granted hereunder are personal to Licensee, and Licensee's rights under this Agreement shall not be assigned or otherwise transferred without the written approval of [Blank] , which shall not be unreasonably withheld, except where such assignment is to a corporation controlling, controlled by or under common control with Licensee or to the purchaser of all or substantially all of the outstanding capital stock or assets of Licensee or to the surviving entity in a merger, reorganization, or other business combination and where notice of such assignment has been provided in advance to [Blank]. Subject to the limitations set forth in this Agreement, this Agreement will inure to the benefit of and be binding upon the parties, their successors and permitted assigns. may assign or transfer this Agreement to another party that agrees to assume [Blank]'s obligations hereunder, and will provide Licensee with written notice thereof. Either party may assign or transfer any of its Disc IP, Absolutely Necessary Claims, or Relatively Necessary Claims provided that the successor-in-interest agrees to be bound by such party's obligations with respect to the Disc IP, Absolutely Necessary Claims, and Relatively Necessary Claims under the terms of this Agreement.

10.3 Presumptions. In construing the terms of this Agreement, no presumption shall operate in either party's favor as a result of its counsel's role in drafting the terms or provisions hereof.

10.4 Governing Law; Jurisdiction. (a) THIS AGREEMENT SHALL BE GOVERNED BY AND CONSTRUED IN ACCORDANCE WITH THE LAWS OF THE STATE OF CALIFORNIA, EXCLUDING THAT BODY OF LAW RELATING TO CONFLICTS OF LAW PRINCIPLES. (b) IN CONNECTION WITH ANY LITIGATION BETWEEN THE PARTIES HERETO ARISING OUT OF OR RELATING TO THIS AGREEMENT, EACH PARTY HERETO IRREVOCABLY CONSENTS TO: ( i) THE EXCLUSIVE JURISDICTION AND VENUE IN THE FEDERAL AND STATE COURTS LOCATED IN THE COUNTY OF SANTA CLARA, CALIFORNIA; AND (ii) THE SERVICE OF PROCESS OF SAID COURTS IN ANY MATTER RELATING TO THIS AGREEMENT BY PERSONAL DELIVERY OR BY MAILING OF PROCESS BY REGISTERED OR CERTIFIED MAIL, POSTAGE PREPAID, AT THE ADDRESSES SPECIFIED IN THIS AGREEMENT. OR TO THE AGENT TO BE APPOINTED PURSUANT TO (c), BELOW. (c) LICENSEE SHALL APPOINT AN AGENT IN THE STATE OF CALIFORNIA FOR ACCEPTANCE OF SERVICE OF PROCESS PROVIDED FOR UNDER THIS AGREEMENT AND SHALL NOTIFY MEI OF THE IDENTITY AND ADDRESS OF SUCH AGENT WITHIN THIRTY (30) DAYS AFTER THE EFFECTIVE DATE; (d) LICENSEE WAIVES ANY OBJECTION TO THE JURISDICTION, PROCESS, AND VENUE OF ANY SUCH COURT, AND TO THE EFFECTIVENESS, EXECUTION, AND ENFORCEMENT OF ANY ORDER OR JUDGMENT (INCLUDING, BUT NOT LIMITED TO, A DEFAULT JUDGMENT) OF SUCH COURT PERTAINING TO THIS AGREEMENT, TO THE MAXIMUM EXTENT PERMITTED BY THE LAW OF THE PLACE WHERE ENFORCEMENT OR EXECUTION OF ANY SUCH ORDER OR JUDGMENT MAY BE SOUGHT AND BY THE LAW OF ANY PLACE WHOSE LAW MIGHT BE CLAIMED TO BE APPLICABLE REGARDING THE EFFECTIVENESS, ENFORCEMENT, OR EXECUTION OF SUCH ORDER OR JUDGMENT, INCLUDING PLACES OUTSIDE OF THE STATE OF CALIFORNIA AND OF THE UNITED STATES.

10.5 Severability; Waiver. Subject to Section 10.7, should any clause, sentence, or paragraph of this Agreement judicially be declared to be invalid, unenforceable, or void, such decision shall not have the effect of invalidating or voiding the remainder of this Agreement. The parties agree that the part or parts of this Agreement so held to be invalid, unenforceable, or void shall be reformed without further action by the parties hereto and only to the extent necessary to make such part or parts valid and enforceable. Subject to Section 10.7, a waiver by either of the parties hereto of any of the covenants to be performed by the other party or any breach thereof shall not be effective unless made in writing and signed by the waiving party and shall not be construed to be a waiver of any succeeding breach thereof or of any covenant herein contained.

10.6 Notice. All notices to be provided pursuant to this Agreement shall be given in writing and shall be effective when either served by personal delivery or upon receipt via certified mail, return receipt requested, postage prepaid, overnight courier service or sent by facsimile transmission with hard copy confirmation sent by certified mail, in each case to the party at the addresses listed below:

If to [Blank]
________________________
________________________
________________________
Attn: ___________________
Fax: ____________________

If to Licensee:
________________________
________________________
________________________
Attn: ___________________
Fax: ____________________

10.7 Amendment. No agreement pertaining to CSS similar to this Agreement or to the Associate License that is Exhibit D hereto between [Blank] and any CSS Licensee or Associate Licensee may be entered into on terms other than those contained in this Agreement or the Associate License, as applicable, to the extent that any modified terms would have a material adverse effect on the integrity or security of CSS or the protections provided to Eligible Licensees pursuant to Section 9.4 hereof (including any of the Sections referenced therein) or in the Associate License, and no agreement between [Blank] and any CSS Licensee or Associate Licensee having terms contained herein or the Associate License, as applicable may be modified or its terms waived if such modification or waiver would have a material adverse effect on the integrity or security of CSS or the protections provided to Eligible Licensees pursuant to Section 9.4 hereof (including any of the Sections referenced therein) or in the Associate License.

10.8 MEI Obligations. [Blank] agrees that as the interim licensor, it shall have the following affirmative obligations, breach of which shall be subject to the remedies provided below.

(a) Prior to the transfer of this Agreement to the Entity, and consistent with its roles as developer of CSS, interim licensor of CSS, and promoter of adoption of CSS, [Blank] agrees that it will make good faith efforts to maintain the confidentiality of CSS Confidential Information and Highly Confidential Information. [Blank] shall not be liable for breaches of this Section that are not material. As non-exclusive examples of situations in which a breach is not material under this section, the situations described in Section 9.3 (1), (2), and (3) shall [Blank] be applicable to in any determination of whether a breach is material. In the event that [Blank] materially breaches its confidentiality obligation set forth in this Section, [Blank]'s total liability to all CSS Licensees for such breach shall be limited to one million dollars ($1,000,000) for each such material breach. For purposes of this Section, a series of related events shall constitute a single material breach.

(b) [Blank] and Licensee acknowledge that affirmative obligations under this Agreement (other than as provided in subsection (a) above), consist of the following:

(i) having filed patent applications as stated in Recital A;

(ii) delivery of the CSS Specifications pursuant to Section 4.1;

(iii) providing written notice and extending the date of the Entity's formation pursuant to Section 6.1(d);

(iv) cooperating reasonably in providing appropriate and necessary information in connection with a Beneficiary Claim filed by Eligible Licensees pursuant to Section 9.4;

(v) providing prompt notice to all Eligible Licensees of a Beneficiary Claim pursuant to Section 9.4(c);

(vi) providing written notice to Licensee in the event [Blank] assigns this Agreement pursuant to Section 10.2;

(vii) amending, as soon as reasonably possible following the finalization of this Agreement, the specifications applicable to licensees of CSS that entered licenses prior to the use of this Agreement, so that (1) such specifications contain these Procedural Specifications and related Technical Specifications, and (2) each such licensee of CSS is required to comply with such amended specifications no later than 30 days following receipt of [Blank]'s notice containing the amended specifications;

(viii) making all reasonable efforts, as soon as possible, to obtain all required consents, from all licensees of CSS that entered licenses prior to the use of this Agreement, to an amended and restated license conforming to this Agreement;

(ix) not amending or waiving provisions of this Agreement or of the Associate License pursuant to the conditions set forth in Section 10.7;

(x) not unreasonably withholding its consent where such consent is called for under this Agreement;

(xi) notifying and applying to Licensee modifications to the Specifications in accordance with Section 4.2;

(xii) not unreasonably withholding agreement for Licensee to receive additional copies of documents containing Highly Confidential Information pursuant to Section 5 .2(b)(iii); and

(xiii) maintaining confidentiality regarding Licensee in accordance with Section 5.2(c).

In the event that [Blank] fails to perform any of the affirmative obligations set forth in this Section 10.8(b) above, Licensee's sole and exclusive remedy against shall be to have [Blank] specifically perform such obligations.

IN WITNESS WHEREOF, the parties have executed this Agreement as of the date first above written.

[Blank]		Licensee
______________________________ Signature		______________________________ Signature
JIRO KAJINO ______________________________ Printed Name		______________________________ Printed Name
Director,   CSS Interim License Organization ______________________________ Title		______________________________ Title
November 20, 1997 ______________________________ Date		______________________________ Date

__________________________________________________________________

EXHIBIT "A"
TO
CSS INTERIM AGREEMENT

MEMBERSHIP CATEGORIES

[  ] Content Provider

[  ] Authoring Studio

[  ] DVD Disc Replicator

[  ] DVD Disc Formatter Manufacturer

[  ] DVD Player Manufacturer

[  ] DVD-ROM Drive Manufacturer

[  ] DVD Decoder Manufacturer (hardware and/or software)

[  ] Descramble Module Manufacturer (hardware and/or software)

[  ] Authentication Chip Manufacturer for DVD-ROM Drive

[  ] Authenticator Manufacturer for DVD Decoder (hardware and/or software)

[  ] Integrated Product Manufacturer

[  ] Reseller

__________________________________________________________________

EXHIBIT "B"
TO
CSS INTERIM AGREEMENT

ACKNOWLEDGMENT AND AGREEMENT TO ABIDE BY TERMS

___________________,a ___________________corporation having a place of business at _______________________________("Sublicensee"), hereby acknowledges and agrees that:

(i) it is a Majority-Owned Affiliate of _____________________________ ("Licensee"), as such term is defined in Section 1.16 of the CSS Interim License Agreement (the "Interim License Agreement") executed on ________________ between Licensee and [Blank];

(ii) it has received a sublicense from Licensee (the "Sublicense") pursuant to Section 2.4 of the Interim License Agreement;

(iii) it has read and understood the Interim License Agreement and agrees to abide by its terms with the same rights (without the right to grant a sublicense) and the same obligations as Licensee including without limitation, the covenant not to sue and patent license offer provisions of Section 5.1 thereof;

(iv) the Sublicense coterminates with the Interim License Agreement and also terminates at such time that Sublicensee ceases to qualify as a "Majority-Owned Affiliate";

(v) in the event Sublicensee fails to abide by the terms of the Interim License Agreement, [Blank] and/or Eligible Licensees (as third party beneficiaries) shall, in their respective sole discretion, be entitled to bring an action at law or in equity against Sublicensee to enforce the terms of the Interim License Agreement.

IN WITNESS WHEREOF, Sublicensee has executed this Acknowledgment and Agreement as of the date written below.

Signed: ____________________

Name:_____________________

Title: _____________________

Date: _____________________

__________________________________________________________________

EXHIBIT "C"
TO
CSS INTERIM LICENSE AGREEMENT

ACKNOWLEDGMENT BY AUTHORIZED EMPLOYEES

I, __________, a full-time employee of _____________,a ____________("Licensee"), acknowledge that I have been designated by Licensee as an "Authorized Employee" to receive on behalf of Licensee access to Confidential Information and Highly Confidential Information of [Blank] for which Licensee is obligated to maintain strictly confidential under the terms of the CSS Interim License Agreement between and [Blank] Licensee. With respect to Highly Confidential Information, I acknowledge that the CSS Interim License Agreement requires Licensee to employ procedures for safeguarding Highly Confidential Information which procedures include, at a minimum: (i) maintaining on Licensee's premises a secure location in which any and all Highly Confidential Information shall be stored; (ii) such secure location shall be accessible only by Authorized Employees; (iii) Authorized Employees shall sign in and out each time such employees visit such secure location; and (iv) when Highly Confidential Information is not in use, such information shall be stored in a locked safe at such secure location.

I further acknowledge that I have signed a prior written agreement with Licensee pursuant to which I have agreed to maintain the confidentiality of third party confidential information received by Licensee. I acknowledge that I am bound by such agreement to adhere to procedures established by Licensee to maintain the confidentiality of Confidential Information and Highly Confidential Information during my employment and after my employment with Licensee.

By signing below, I attest that I have read and understood this acknowledgment.

Signed: ____________________

Name:_____________________

Date: _____________________

cc:

__________________________________________________________________

EXHIBIT "D"
TO
CSS INTERIM LICENSE AGREEMENT

ASSOCIATE LICENSE AGREEMENT

[To be provided at a later date]

__________________________________________________________________

EXHIBIT "E"
TO
CSS INTERIM LICENSE AGREEMENT

CONTACT PERSON

Name:

Title:

Division:

Company:

Address:

Telephone Number:

Facsimile Number:

---

[End Hoy Reply Declaration.]

Transcription and HTML by Cryptome.

---

The following was substituted for the original Hoy Reply file on March 1, 2001.

2 March 2001: Add responses.

1 March 2001

See related: http://cryptome.org/mpaa-v-dvc.htm

---

[Certified mail March 1, 2001.]

DVD Copy Control Association

225 B Cochrane Circle
Morgan Hill, CA 95037

February 26, 2001

Mr. John Young
251 West 89th Street Suite 6E
New York, New York 10024

Dear Mr. Young:

On behalf of DVD Copy Control Association ("DVD CCA"), I am writing to demand that you immediately remove material posted at the following URL:

cryptome.org/dvd-hoy-reply.htm

from the above-referenced web site. Your web site is illegally posting trade secrets licensed by DVD CCA in violation of two Orders issued by the Santa Clara County Superior Court in California on January 21, 2000 and January 26, 2000.

By way of background, DVD CCA is the sole licensor of trade secrets which comprise the Content Scramble System ("CSS"), encryption/decryption technology designed to protect motion pictures released on Digital Versatile Discs ("DVDs"). In late October 1999, it became apparent that a program titled DeCSS was developed which allowed CSS to be circumvented by incorporating DVD CCA's trade secrets, and was being posted illegally on the Internet.

On December 27, 1999, DVD CCA filed a Complaint in the Santa Clara County Superior Court in the State of California (Case No. CV 786804) against 21 defendants, 72 "Doe" defendants for whom a web site address had been identified and an additional 428 Doe Defendants. (A true and correct copy of the Complaint is attached as Exhibit A.) At the same time, DVD CCA also filed an Application for a Preliminary Injunction seeking to have the Court prohibit these defendants from posting the CSS trade secrets. On January 21, 2000, the Court granted DVD CCA's Application and issued a preliminary injunction which provides as follows:

The named Defendants, their officers, directors, principals, agents, servants, employees, attorneys, successors and assigns, representatives and all persons acting in concert with them, are hereby enjoined from: Posting or otherwise disclosing or distributing, on their websites or elsewhere, the DeCSS program, the master keys or algorithms of the Content Scrambling System ("CSS"), or any other information derived from this proprietary information.

(Preliminary Injunction at 1-2). (A true and correct copy of the Court's Order Granting Preliminary Injunction is attached hereto as Exhibit B.)

The above-referenced web site is illegally posting the CSS trade secrets in violation of the Preliminary Injunction.

On January 26, 2000, after the Preliminary Injunction was granted, the Court also issued a protective order sealing the portions of the document posted at the above-referenced URL that contain CSS trade secrets. (A true and correct copy of the Court's Protective Order Placing Under Seal Exhibits A and B to the Reply Declaration of John Hoy (the "Seal Order") is attached hereto as Exhibit C.) The posting of the document at the above-referenced URL is in violation of the Court's Seal Order.

DVD CCA demands that you cause the immediate removal from the above web site the above-referenced document, as well as any other information derived from this proprietary information, including the DeCSS program, the master keys and CSS algorithms. Please confirm in writing within five (5) business days that you have effected removal of this material. If we have not received a response from you, we will use all forms of relief available to have the offending material removed.

We appreciate your immediate cooperation in this matter.

Sincerely,

John J. Hoy
President and Chief Operating Officer

[Exhibits A, B and C omitted.]

---

By fax: 408-779-9291

March 1, 2001

Mr. John J. Hoy
President and Chief Operating Officer
DVD Copy Control Association
225 B Cochrane Circle
Morgan Hill, CA 95037

Dear Mr. Hoy,

In response to your letter of February 26, 2001, received today, the document at :

cryptome.org/dvd-hoy-reply.htm

has been removed and your letter and this response published in its place.

Regards,

John Young

---

Date: Thu, 1 Mar 2001 12:41:55 -0700
From: Paul Fenimore <fenimore@roadrunner.com>
To: dvd-discuss@eon.law.harvard.edu
Subject: [dvd-discuss] March 2001: DVD Hoy Reply Demand Letter

<http://cryptome.org/dvd-hoy-reply.htm>

<quote>
   [Certified mail March 1, 2001.]

  DVD Copy Control Association

   225 B Cochrane Circle
   Morgan Hill, CA 95037

   February 26, 2001

   Mr. John Young
   251 West 89th Street Suite 6E
   New York, New York 10024

   Dear Mr. Young:

   On behalf of DVD Copy Control Association ("DVD CCA"), I am writing to
   demand that you immediately remove material posted at the following
   URL:

     cryptome.org/dvd-hoy-reply.htm

   from the above-referenced web site. Your web site is illegally posting
   trade secrets licensed by DVD CCA in violation of two Orders issued by
   the Santa Clara County Superior Court in California on January 21,
   2000 and January 26, 2000.

[ blah blah blah ]
</quote> 



Date: Thu, 1 Mar 2001 13:00:42 -0800
From: S
To: jy@cryptome.org
Subject: Re: [dvd-discuss] March 2001: DVD Hoy Reply Demand Letter

It seems kind of out of character for you to have removed a 
document from Cryptome immediately upon receipt of a demand letter.
Did you think that Mr. Hoy's argument was correct?  Were you
concerned that the DVD CCA would sue you?

Are you nitpicking over the particular choice of URL and planning
to publish that document elsewhere?  Or is something else going on?




Date: Thu, 1 Mar 2001 04:25 PM
To: S
From: jya@pipeline.com
Subject: Re: [dvd-discuss] March 2001: DVD Hoy Reply Demand Letter

I expected Hoy to immediately go to Verio to have the doc yanked
or Cryptome itself yanked, based on Verio's reaction to the MPAA 
letter in January which is linked at the letter -- and which surely 
prompted Hoy's demand, as we assumed it would.

Moreover, the document has been massively downloaded, so
somebody else will offer it. [Downloads >200,000]

And, we're wrestling other alligators right now, so this is one that
is not on our fight card; it's available for another battler.

John



Date: Thu, 1 Mar 2001 13:55:48 -0800
From: S
To: John Young <jya@pipeline.com>
Subject: Re: [dvd-discuss] March 2001: DVD Hoy Reply Demand Letter

I did find a couple of copies easily by searching for "DVD Hoy reply"
on Google.  Do you think you would incur liability or headaches by
linking to somebody else's version?

I'm sure you're pretty busy between the current trial in SDNY and the
upcoming one in Washington.




Date: Thu, 1 Mar 2001 05:23 PM
To: S
From: jya@pipeline.com
Subject: Re: [dvd-discuss] March 2001: DVD Hoy Reply Demand Letter

I'd rather not name a target for Hoy to shoot. Folks should
know how to find the file like you did, that's why I left the
name and Hoy's avid description.

John



Date: Fri, 2 Mar 2001 00:31:56 -0500
From: Brian Ristuccia <brian@ristuccia.com>
To: dvd-discuss@eon.law.harvard.edu
Subject: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

And in a way quite odd for John Young, he has complied with their request:

  Dear Mr. Hoy,

  In response to your letter of February 26, 2001, received today, the
  document at :
  cryptome.org/dvd-hoy-reply.htm

  has been removed and your letter and this response published in its place.

  Regards,

  John Young

-- 
Brian Ristuccia
brian@ristuccia.com
bristucc@cs.uml.edu



From: Anonymous
To: jya@pipeline.com

The letter refers to the "URL": cryptome.org/dvd-hoy-reply.htm
Since this does not include the access method (probably HTTP), it is
not a proper URL.

And now for a question about Trade Secrets. The letter almost
acknowledges that the only reason they have for asking you to remove
the posting is the court injunction.

If Trade Secrets are exposed, then they have no protection, according
to my limited understanding (a quick disclaimer: IANAL, IANAA (I Am
Not An American :))




Date: Thu, 01 Mar 2001 23:55:41 -0600
From: Chris Moseng <moseng@mninter.net>
To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

Brian Ristuccia wrote:

> And in a way quite odd for John Young, he has complied with their request:

He's done that before, with a PDF leaked from the Times, and
subsequently made the document available again. He's probably just
mulling over an appropriate response.

But don't take my word for it, let's ask him.



Date: Fri, 02 Mar 2001 07:48:49 -0500
To: dvd-discuss@eon.law.harvard.edu
From: John Young <jya@pipeline.com>
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

We had been expecting a letter since January when MPAA
sent our ISP, Verio, a letter about the same file, alleging it
offered DeCSS, which it did not and which we denied in
a response to Verio. We expected Hoy to go to Verio
to have the file removed if we did not, and we think Verio
would have yanked it or yanked Cryptome, based on prior
correspondence with Verio's legal department. We linked
to the Verio correspondence in the replacement file.

Moreover, the file has been heavily downloaded, the single
most from Cryptome, so it is widely distributed. Those who
want it will find it through search engines. And somebody
will probably offer it, or maybe several somebodies as the
word spreads, emulating DeCSS distribution.

Hoy is probably as surprised as others that the file was
yanked. Now he's got to worry about the consequences,
and what the evildoers will do.

Listen, doing the unexpected is a tonic. Now hear this:

Proskauer wrote a couple a days ago and asked if Cryptome
would publish its CA2 appeal brief, and sent along an
un-footnoted version. I answered that we already had 
done that, with footnotes. Sorry, said Proskauer, didn't 
know that. 

We asked to be sent their briefs in digital form to save us 
a load of labor to scan hardcopy. Proskauer said will do,
and maybe that will happen.

The option to publish Prokauer's request is awaiting a
goad -- wait a minute I just got goaded by Hoy. The 
Proskauer request for help would be an apt bicoastal
cohort to Hoy's demand for help.

Evil abounds.



From: Craig Markwardt <craigm@cow.physics.wisc.edu>
Date: Fri, 2 Mar 2001 08:10:53 -0600 (CST)
To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

While the Hoy declaration might possibly be removed for containing
trade secrets, it's hard to make a case that the CSS Procedural
Specifications are still trade secrets.  After all, the DVDCCA itself
has published the specifications here:

  http://www.dvdcca.org/dvdcca/data/css/

and now mirrored by Tom here:

  http://www.lemuria.org/DeCSS/decss.html

The DVDCCA site in fact has several versions of the Specifications
document, among some more mundane application forms and paperwork.

How can Hoy now claim that these are still trade secrets?  John, can
you not publish one of these versions instead?

Craig



Date: Fri, 02 Mar 2001 09:31:31 -0500
To: dvd-discuss@eon.law.harvard.edu
From: John Young <jya@pipeline.com>
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

In answer to Craig:

What the Hoy Reply file contained was the CSS code,
not the specs.

The CSS code was mislabeled as "DeCSS" and appeared
to have come from Japan for it had Japanese page numbers
on it. 

Somebody at DVD CCA's attorney overlooked the CSS code, 
due to the mislabel or general ignorance of coding, or sloth in 
filing procedures, when the doc was filed in court unsealed.

After the file was Slashdotted and reported in the news, DVD CCA
went back to court to get the doc sealed. At the time we were told
that the seal applied only to lawyers involved, that the horse was
out of the barn, again like DeCSS. DVD CCA never made a
request to remove the file, before now.

We not trying to be smart when we say we saw Hoy's letter as
an opportunity to call attention to the file and its already 
widespread distribution. There has not been much interest
in it lately, as far as we know, and MPAA's and Hoy's demands
that it be removed present new opportunities for doing what
must be done, which is feel their pain and call attention to
it.

It is possible that the file will reappear on Cryptome in the 
public interest should it become a topic of debate. But more 
likely, and best, it will become widely available elsewhere -- 
that's if anyone gives a hoot besides MPAA and DVD CCA 
and their amici.



From: "D. C. Sessions" <dvd@lumbercartel.com>
Date: Fri, 2 Mar 2001 08:10:03 -0700
To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

So -- let's be totally clear here -- the Plaintiffs are now on record,
in writing, repeatedly after the fact was pointed out to them, as
officially objecting to the distribution of their own CSS code on the
grounds that it's an illegal circumvention device?

-- 
| I'm old enough that I don't have to pretend to be grown up.|
+----------- D. C. Sessions <dcs@lumbercartel.com> ----------+




Date: Fri, 02 Mar 2001 10:29:51 -0500
To: dvd-discuss@eon.law.harvard.edu
From: John Young <jya@pipeline.com>
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

>So -- let's be totally clear here -- the Plaintiffs are now on record,
>in writing, repeatedly after the fact was pointed out to them, as
>officially objecting to the distribution of their own CSS code on the
>grounds that it's an illegal circumvention device?

No, DVD CCA is objecting to its "trade secret" CSS code being
published, more than a year after first published, widely publicized
and widely distributed.

It was the MPAA robot cease-and-desist-letter sender which 
objected to the Hoy Reply offering of DeCSS, which it did not 
contain.

This confusion on the part of DVD CCA and MPAA about the
Hoy Reply file was itself extensively discussed last year.

But the plaintiffs robots do not read the Net any better than
the plaintiffs read court filings made in their name.

What the plaintiffs do want is publicity for their view of
reality -- which is to insist on their rights no matter the
FUD over what those rights are. See Jack Valenti's statements
which affirm FUD as MPAA's proprietary FUD, absolutely, and 
if there is any doubt about that the FUD copyrighters will go 
back to Congress who will legislate the FUD as belonging to 
the FUD copyright corps, backed by FUD Copyright Office 
and multiple Judges of FUD.

Remember that FUD(c) is intellectual property for those with
the resources to legally steal it.



Date: Fri, 2 Mar 2001 11:00:31 -0500 (EST)
From: Jeremy A Erwin <jerwin@osf1.gmu.edu>
To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

The Hoy declaration contains a copy of DeCSS source code. This
document was not (initially) sealed by the California courts.

Jeremy



To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter 
Date: Fri, 02 Mar 2001 11:15:14 -0500
From: "Peter D. Junger" <junger@samsara.law.cwru.edu>

In connection with the draft of my article on the Anti-Circumvention
provisions of the DMCA, which I announced sometime back on this list,
I had posted just the CSS code taken from the Hoy Declaration on my
web site together with a link to the Cryptome version for those who
wanted to see the text in context.  Now that the Cryptome version is
gone, what should I use for a link?

By the way, the article is going very well, but rather slowly.

Here's what I have on my web site at 
<http://samsara.law.cwru.edu/dmca/csscode.html>:

\begin{quotation}

   This version of the CSS program is copied from Exhibit B to the Reply
   Declaration of John J. Hoy dated January 18, 2000 and filed in the
   case of DVD Copy Control Association v. McLaughlin in the Superior
   Court of the State of California, County of Santa Clara. See Hoy
   Declaration on Cryptome.
   

                                 CSSscrambleT.txt




unsigned int CSStab0[11]={5,0,1,2,3,4,0,1,2,3,4};

unsigned char CSStab1[256]=
{
        0x33,0x73,0x3b,0x26,0x63,0x23,0x6b,0x76,0x3e,0x7e,0x36,0x2b,0
x6e,0x2e,0x66,0x7b,
        0xd3,0x93,0xdb,0x06,0x43,0x03,0x4b,0x96,0xde,0x9e,0xd6,0x0b,0
x4e,0x0e,0x46,0x9b,
        0x57,0x17,0x5f,0x82,0xc7,0x87,0xcf,0x12,0x5a,0x1a,0x52,0x8f,0
xca,0x8a,0xc2,0x1f,
        0xd9,0x99,0xd1,0x00,0x49,0x09,0x41,0x90,0xd8,0x98,0xd0,0x01,0
x48,0x08,0x40,0x91,
        0x3d,0x7d,0x35,0x24,0x6d,0x2d,0x65,0x74,0x3c,0x7c,0x34,0x25,0
x6c,0x2c,0x64,0x75,
        0xdd,0x9d,0xd5,0x04,0x4d,0x0d,0x45,0x94,0xdc,0x9c,0xd4,0x05,0
x4c,0x0c,0x44,0x95,
        0x59,0x19,0x51,0x80,0xc9,0x89,0xc1,0x10,0x58,0x18,0x50,0x81,0
xc8,0x88,0xc0,0x11,
        0xd7,0x97,0xdf,0x02,0x47,0x07,0x4f,0x92,0xda,0x9a,0xd2,0x0f,0
x4a,0x0a,0x42,0x9f,
        0x53,0x13,0x5b,0x86,0xc3,0x83,0xcb,0x16,0x5e,0x1e,0x56,0x8b,0
xce,0x8e,0xc6,0x1b,
        0xb3,0xf3,0xbb,0xa6,0xe3,0xa3,0xeb,0xf6,0xbe,0xfe,0xb6,0xab,0
xee,0xae,0xe6,0xfb,
        0x37,0x77,0x3f,0x22,0x67,0x27,0x6f,0x72,0x3a,0x7a,0x32,0x2f,0
x6a,0x2a,0x62,0x7f,
        0xb9,0xf9,0xb1,0xa0,0xe9,0xa9,0xe1,0xf0,0xb8,0xf8,0xb0,0xa1,0
xe8,0xa8,0xe0,0xf1,
        0x5d,0x1d,0x55,0x84,0xcd,0x8d,0xc5,0x14,0x5c,0x1c,0x54,0x85,0
xcc,0x8c,0xc4,0x15,
        0xbd,0xfd,0xb5,0xa4,0xed,0xad,0xe5,0xf4,0xbc,0xfc,0xb4,0xa5,0
xec,0xac,0xe4,0xf5,
        0x39,0x79,0x31,0x20,0x69,0x29,0x61,0x70,0x38,0x78,0x30,0x21,0
x68,0x28,0x60,0x71,

        0xb7,0xf7,0xbf,0xa2,0xe7,0xa7,0xef,0xf2,0xba,0xfa,0xb2,0xaf,0
xea,0xaa,0xe2,0xff
};

unsigned char CSStab2[256]=
{
        0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x09,0x08,0x0b,0x0a,0
x0d,0x0c,0x0f,0x0e,
        0x12,0x13,0x10,0x11,0x16,0x17,0x14,0x15,0x1b,0x1a,0x19,0x18,0
x1f,0x1e,0x1d,0x1c,


                                      1 peeji [Japanese for "page"]


-------------------------------------------------------------------------------
-


                                CSSscrambleT.txt





        0x24,0x25,0x26,0x27,0x20,0x21,0x22,0x23,0x2d,0x2c,0x2f,0x2e,0
x29,0x28,0x2b,0x2a,
        0x36,0x37,0x34,0x35,0x32,0x33,0x30,0x31,0x3f,0x3e,0x3d,0x3c,0
x3b,0x3a,0x39,0x38,
        0x49,0x48,0x4b,0x4a,0x4d,0x4c,0x4f,0x4e,0x40,0x41,0x42,0x43,0
x44,0x45,0x46,0x47,
        0x5b,0x5a,0x59,0x58,0x5f,0x5e,0x5d,0x5c,0x52,0x53,0x50,0x51,0
x56,0x57,0x54,0x55,
        0x6d,0x6c,0x6f,0x6e,0x69,0x68,0x6b,0x6a,0x64,0x65,0x66,0x67,0
x60,0x61,0x62,0x63,
        0x7f,0x7e,0x7d,0x7c,0x7b,0x7a,0x79,0x78,0x76,0x77,0x74,0x75,0
x72,0x73,0x70,0x71,
        0x92,0x93,0x90,0x91,0x96,0x97,0x94,0x95,0x9b,0x9a,0x99,0x98,0
x9f,0x9e,0x9d,0x9c,
        0x80,0x81,0x82,0x83,0x84,0x85,0x86,0x87,0x89,0x88,0x8b,0x8a,0
x8d,0x8c,0x8f,0x8e,
        0xb6,0xb7,0xb4,0xb5,0xb2,0xb3,0xb0,0xb1,0xbf,0xbe,0xbd,0xbc,0
xbb,0xba,0xb9,0xb8,
        0xa4,0xa5,0xa6,0xa7,0xa0,0xa1,0xa2,0xa3,0xad,0xac,0xaf,0xae,0
xa9,0xa8,0xab,0xaa,
        0xdb,0xda,0xd9,0xd8,0xdf,0xde,0xdd,0xdc,0xd2,0xd3,0xd0,0xd1,0
xd6,0xd7,0xd4,0xd5,
        0xc9,0xc8,0xcb,0xca,0xcd,0xcc,0xcf,0xce,0xc0,0xc1,0xc2,0xc3,0
xc4,0xc5,0xc6,0xc7,
        0xff,0xfe,0xfd,0xfc,0xfb,0xfa,0xf9,0xf8,0xf6,0xf7,0xf4,0xf5,0
xf2,0xf3,0xf0,0xf1,
        0xed,0xec,0xef,0xee,0xe9,0xe8,0xeb,0xea,0xe4,0xe5,0xe6,0xe7,0
xe0,0xe1,0xe2,0xe3
};

unsigned char CSStab3[512]=
{
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,


                                      2 peeji


-------------------------------------------------------------------------------
-


                                CSSscrambleT.txt





        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0

x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,


                                      3 peeji


-------------------------------------------------------------------------------
-


                                CSSscrambleT.txt





        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff,
        0x00,0x24,0x49,0x6d,0x92,0xb6,0xdb,0xff,0x00,0x24,0x49,0x6d,0
x92,0xb6,0xdb,0xff
};

unsigned char CSStab4[256]=
{
        0x00,0x80,0x40,0xc0,0x20,0xa0,0x60,0xe0,0x10,0x90,0x50,0xd0,0
x30,0xb0,0x70,0xf0,
        0x08,0x88,0x48,0xc8,0x28,0xa8,0x68,0xe8,0x18,0x98,0x58,0xd8,0
x38,0xb8,0x78,0xf8,
        0x04,0x84,0x44,0xc4,0x24,0xa4,0x64,0xe4,0x14,0x94,0x54,0xd4,0
x34,0xb4,0x74,0xf4,
        0x0c,0x8c,0x4c,0xcc,0x2c,0xac,0x6c,0xec,0x1c,0x9c,0x5c,0xdc,0
x3c,0xbc,0x7c,0xfc,
        0x02,0x82,0x42,0xc2,0x22,0xa2,0x62,0xe2,0x12,0x92,0x52,0xd2,0
x32,0xb2,0x72,0xf2,
        0x0a,0x8a,0x4a,0xca,0x2a,0xaa,0x6a,0xea,0x1a,0x9a,0x5a,0xda,0
x3a,0xba,0x7a,0xfa,
        0x06,0x86,0x46,0xc6,0x26,0xa6,0x66,0xe6,0x16,0x96,0x56,0xd6,0
x36,0xb6,0x76,0xf6,
        0x0e,0x8e,0x4e,0xce,0x2e,0xae,0x6e,0xee,0x1e,0x9e,0x5e,0xde,0
x3e,0xbe,0x7e,0xfe,
        0x01,0x81,0x41,0xc1,0x21,0xa1,0x61,0xe1,0x11,0x91,0x51,0xd1,0
x31,0xb1,0x71,0xf1,
        0x09,0x89,0x49,0xc9,0x29,0xa9,0x69,0xe9,0x19,0x99,0x59,0xd9,0
x39,0xb9,0x79,0xf9,
        0x05,0x85,0x45,0xc5,0x25,0xa5,0x65,0xe5,0x15,0x95,0x55,0xd5,0
x35,0xb5,0x75,0xf5,
        0x0d,0x8d,0x4d,0xcd,0x2d,0xad,0x6d,0xed,0x1d,0x9d,0x5d,0xdd,0
x3d,0xbd,0x7d,0xfd,
        0x03,0x83,0x43,0xc3,0x23,0xa3,0x63,0xe3,0x13,0x93,0x53,0xd3,0
x33,0xb3,0x73,0xf3,

        0x0b,0x8b,0x4b,0xcb,0x2b,0xab,0x6b,0xeb,0x1b,0x9b,0x5b,0xdb,0
x3b,0xbb,0x7b,0xfb,
        0x07,0x87,0x47,0xc7,0x27,0xa7,0x67,0xe7,0x17,0x97,0x57,0xd7,0
x37,0xb7,0x77,0xf7,
        0x0f,0x8f,0x4f,0xcf,0x2f,0xaf,0x6f,0xef,0x1f,0x9f,0x5f,0xdf,0
x3f,0xbf,0x7f,0xff


                                      4 peeji


-------------------------------------------------------------------------------
-


                                CSSscrambleT.txt




};

unsigned char CSStab5[256]=
{
        0xff,0x7f,0xbf,0x3f,0xdf,0x5f,0x9f,0x1f,0xef,0x6f,0xaf,0x2f,0
xcf,0x4f,0x8f,0x0f,
        0xf7,0x77,0xb7,0x37,0xd7,0x57,0x97,0x17,0xe7,0x67,0xa7,0x27,0
xc7,0x47,0x87,0x07,
        0xfb,0x7b,0xbb,0x3b,0xdb,0x5b,0x9b,0x1b,0xeb,0x6b,0xab,0x2b,0
xcb,0x4b,0x8b,0x0b,
        0xf3,0x73,0xb3,0x33,0xd3,0x53,0x93,0x13,0xe3,0x63,0xa3,0x23,0
xc3,0x43,0x83,0x03,
        0xfd,0x7d,0xbd,0x3d,0xdd,0x5d,0x9d,0x1d,0xed,0x6d,0xad,0x2d,0
xcd,0x4d,0x8d,0x0d,
        0xf5,0x75,0xb5,0x35,0xd5,0x55,0x95,0x15,0xe5,0x65,0xa5,0x25,0
xc5,0x45,0x85,0x05,
        0xf9,0x79,0xb9,0x39,0xd9,0x59,0x99,0x19,0xe9,0x69,0xa9,0x29,0
xc9,0x49,0x89,0x09,
        0xf1,0x71,0xb1,0x31,0xd1,0x51,0x91,0x11,0xe1,0x61,0xa1,0x21,0
xc1,0x41,0x81,0x01,
        0xfe,0x7e,0xbe,0x3e,0xde,0x5e,0x9e,0x1e,0xee,0x6e,0xae,0x2e,0
xce,0x4e,0x8e,0x0e,
        0xf6,0x76,0xb6,0x36,0xd6,0x56,0x96,0x16,0xe6,0x66,0xa6,0x26,0
xc6,0x46,0x86,0x06,
        0xfa,0x7a,0xba,0x3a,0xda,0x5a,0x9a,0x1a,0xea,0x6a,0xaa,0x2a,0
xca,0x4a,0x8a,0x0a,
        0xf2,0x72,0xb2,0x32,0xd2,0x52,0x92,0x12,0xe2,0x62,0xa2,0x22,0
xc2,0x42,0x82,0x02,
        0xfc,0x7c,0xbc,0x3c,0xdc,0x5c,0x9c,0x1c,0xec,0x6c,0xac,0x2c,0
xcc,0x4c,0x8c,0x0c,
        0xf4,0x74,0xb4,0x34,0xd4,0x54,0x94,0x14,0xe4,0x64,0xa4,0x24,0
xc4,0x44,0x84,0x04,
        0xf8,0x78,0xb8,0x38,0xd8,0x58,0x98,0x18,0xe8,0x68,0xa8,0x28,0
xc8,0x48,0x88,0x08,
        0xf0,0x70,0xb0,0x30,0xd0,0x50,0x90,0x10,0xe0,0x60,0xa0,0x20,0
xc0,0x40,0x80,0x00
};

void CSSdescramble(unsigned char *sec,unsigned char *key)
{
        unsigned int t1,t2,t3,t4,t5,t6;
        unsigned char *end=sec+0x800;

        t1=key[0]^sec[0x54]|0x100;


                                      5 peeji


-------------------------------------------------------------------------------
-


                                CSSscrambleT.txt





        t2=key[1]^sec[0x55];
        t3=(*((unsigned int *)(key+2)))^(*((unsigned int *)(sec+0x56)
));
        t4=t3&7;
        t3=t3*2+8-t4;
        sec+=0x80;
        t5=0;
        while(sec!=end)
        {
                t4=CSStab2[t2]^CSStab3[t1];
                t2=t1>>1;
                t1=((t1&1)<<8)^t4;
                t4=CSStab5[t4];
                t6=(((((((t3>>3)^t3)>>1)^t3)>>8)^t3)>>5)&0xff;
                t3=(t3<<8)|t6;
                t6=CSStab4[t6];
                t5+=t6+t4;
                *sec++=CSStab1[*sec]^(t5&0xff);
                t5>>=8;
        }
}

void CSStitlekey1(unsigned char *key,unsigned char *im)
{
        unsigned int t1,t2,t3,t4,t5,t6;
        unsigned char k[5];
        int i;

        t1=im[0]|0x100;
        t2=im[1];
        t3=*((unsigned int *)(im+2));
        t4=t3&7;

        t3=t3*2+8-t4;
        t5=0;
        for(i=0;i<5;i++)
        {
                t4=CSStab2[t2]^CSStab3[t1];
                t2=t1>>1;
                t1=((t1&1)<<8)^t4;
                t4=CSStab4[t4];
                t6=(((((((t3>>3)^t3)>>1)^t3)>>8)^t3)>>5)&0xff;
                t3=(t3<<8)|t6;
                t6=CSStab4[t6];
                t5+=t6+t4;


                                      6 peeji


-------------------------------------------------------------------------------
-


                                CSSscrambleT.txt





                k[i]=t5&0xff;
                t5>>=8;
        }
        for(i=9;i>=0;i--)
                key[CSStab0[i+1]]=k[CSStab0[i+1]]^CSStab1[key[CSStab0
[i+1]]]^key[CSStab0[i]];
}

void CSStitlekey2(unsigned char *key,unsigned char *im)
{
        unsigned int t1,t2,t3,t4,t5,t6;
        unsigned char k[5];
        int i;

        t1=im[0]|0x100;
        t2=im[1];
        t3=*((unsigned int *)(im+2));
        t4=t3&7;
        t3=t3*2+8-t4;
        t5=0;
        for(i=0;i<5;i++)
        {
                t4=CSStab2[t2]^CSStab3[t1];
                t2=t1>>1;
                t1=((t1&1)<<8)^t4;
                t4=CSStab4[t4];
                t6=(((((((t3>>3)^t3)>>1)^t3)>>8)^t3)>>5)&0xff;
                t3=(t3<<8)|t6;
                t6=CSStab5[t6];
                t5+=t6+t4;
                k[i]=t5&0xff;
                t5>>=8;
        }
        for(i=9;i>=0;i--)
                key[CSStab0[i+1]]=k[CSStab0[i+1]]^CSStab1[key[CSStab0
[i+1]]]^key[CSStab0[i]];
}

void CSSdecrypttitlekey(unsigned char *tkey,unsigned char *dkey)
{
        int i;
        unsigned char im1[6];
        unsigned char im2[6]={0x51,0x67,0x67,0xc5,0xe0,0x00};


                                      7 peeji


-------------------------------------------------------------------------------
-


                                CSSscrambleT.txt





        for(i=0;i<6;i++)
                im1[i]=dkey[i];

        CSStitlekey1(im1,im2);
        CSStitlekey2(tkey,im1);
}









                                      8 peeji
\end{quotation}

--
Peter D. Junger--Case Western Reserve University Law School--Cleveland, OH
EMAIL: junger@samsara.law.cwru.edu    URL:  http://samsara.law.cwru.edu   
        NOTE: junger@pdj2-ra.f-remote.cwru.edu no longer exists



Date: Fri, 02 Mar 2001 11:12:57 -0500
To: dvd-discuss@eon.law.harvard.edu
From: John Young <jya@pipeline.com>
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

Jeremy wrote:

>The Hoy declaration contains a copy of DeCSS source code. This
>document was not (initially) sealed by the California courts.

Sorry to belabor this point, but the Hoy file did not contain DeCSS.
The only DeCSS-related items were two brief DeCSS introductory 
notes (Exhibit A), but not the DeCSS code itself. The only code in the
doc (Exhibit B) was that of CSS, mislabeled in handwriting
"DeCSS," but titled in print "CSSscrambleT.txt".

CSS is the trade secret, not DeCSS -- well, DeCSS is the trade
unsecret of MoE.

Gosh, we might have to post Exhibits A and B here to present 
the evidence for ajudication. But then bottomless-pocketed 
Harvard would become a demand target.



To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter 
Date: Fri, 02 Mar 2001 11:39:25 -0500
From: "Peter D. Junger" <junger@samsara.law.cwru.edu>

John Young writes:

: Gosh, we might have to post Exhibits A and B here to present 
: the evidence for ajudication. But then bottomless-pocketed 
: Harvard would become a demand target.

O! dear me, why didn't I think of that?

--
Peter D. Junger--Case Western Reserve University Law School--Cleveland, OH
EMAIL: junger@samsara.law.cwru.edu    URL:  http://samsara.law.cwru.edu   
        NOTE: junger@pdj2-ra.f-remote.cwru.edu no longer exists



Date: Fri, 02 Mar 2001 10:45:15 -0600
From: Chris Moseng <moseng@mninter.net>
To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

"Peter D. Junger" wrote:
> Now that the Cryptome version is
> gone, what should I use for a link?

There are hundreds of results on google for "hoy reply," but I humbly
offer <a
href="http://www.underwhelm.org/decss/dvd-hoy-reply.html">mine</a>.

Pros: Hosted on my own computer, of which domain I am the owner; haven't
gotten a threat from the MPAA since I sent them <a
href="http://www.underwhelm.org/decss/reply.html">this email.</a>

Cons: Hosted on a 256k DSL line with no redundant link off a 95% uptime
linux box; no QOS guarantee.
-- 
moseng@mninter.net
I use PGP 6.5.3  --  http://www.underwhelm.org/pgp



To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter 
Date: Fri, 02 Mar 2001 12:06:57 -0500
From: "Peter D. Junger" <junger@samsara.law.cwru.edu>

Chris Moseng writes:

: There are hundreds of results on google for "hoy reply," but I humbly
: offer <a
: href="http://www.underwhelm.org/decss/dvd-hoy-reply.html">mine</a>.

Thank you.  The link now points at your version.

--
Peter D. Junger--Case Western Reserve University Law School--Cleveland, OH
EMAIL: junger@samsara.law.cwru.edu    URL:  http://samsara.law.cwru.edu   
        NOTE: junger@pdj2-ra.f-remote.cwru.edu no longer exists



Date: Fri, 2 Mar 2001 08:56:44 -0800 (PST)
From: Bryan Taylor <bryan_w_taylor@yahoo.com>
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter
To: dvd-discuss@eon.law.harvard.edu

My (non-lawyer) understanding is that if you obtained the document from
unsealed (at the time) court records, then that act was not a misappropriation
of a trade secret, since you have no duty to maintain secrecy of unsealed court
records. The fact that the records are now sealed probably does not change the
status of the act of obtaining them. 

Since you published them on the web, with much fanfare and announcements on
several highly visible mailing lists and news sites like Slashdot, I think it
is likely that the CSS trade secret status has been permanently lost,
especially because your posting was unchallenged for so long. I also believe
that anyone who obtained them from you has not misappropriated anything.

After all, a trade secret must be secret and it must be defended.

I would think some of the defendents in the CA case would have an interest in
helping you get a declaratory judgement that your posting was not
misappropriation and brings to an end the CSS trade secret status.

I understand that you might not want to engage the motion picture industry in a
legal battle, but if my understanding of the law is correct (second opinions?)
you might consider getting representation, because it looks like a naked
attempt to bully you by the MPAA.



From: "John Zulauf" <johnzu@ia.nsc.com>
To: dvd-discuss@eon.law.harvard.edu
Subject: RE: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter
Date: Fri, 2 Mar 2001 11:06:20 -0700

Bryan Taylor  Sent: Friday, March 02, 2001 9:57 AM

> After all, a trade secret must be secret and it must be defended.

This occurred to me as well.  How long has the Hoy declaration been
published?  Do you have a list of the number and places the publication of
the declaration was made known publically?  For how long would a web search
have turned up hits on the declaration?  Wouldn't that fine legal fiction of
the "reasonable man" need respond in something substantially 13 months it
has take them to send you the C&D.  Clearly a "reasonable man" would have
been doing web searches.  Clearly the MPAA has done so in the much shorter
period since the lower courts decision.

IANAL -- any lawyers want to comment on how quickly a trade secret must be
defended?  Any standard of thoroughness (and typing "hoy declaration" into
google is pretty low effort) for searching out and irradicating copies of an
unintentionally leak document?  It's not as if this file was encrypted on
"evil.f.ing.hackers.com" available only to script-kiddies and those with the
secrect decoder ring.  It wasn't even Rot-13'd or uuencoded to obscure it.
It was posted on the electronic equivalent of a billboard** -- visible to
anyone who looked for it worldwide (that's a darn big billboard) on a site
well known for it's involvement in the CSS/deCSS/DMCA/DVD-CCA matters.

While "hoy declaration" returns many bogus links searching for something
more disctintive from the document like

peeji & "0x33,0x73,0x3b,0x26,0x63,0x23,0x6b,0x76,0x3e,0x7e"

takes one right to several copies of the Hoy CSS document.  Now Hoy might
complain the he is no internet search expert -- well there are many to be
found.  Hiring security or other experts to protect a trade secret certainly
is within the bounds of what a "reasonable man" would be expected to do.
This seems especially true when the holder of a secret is in the midst of a
lawsuit to keep that same information secret.

It strikes me that the whole of the CA case is now moot. If this subject of
the trade secret case has been on the web for more than a year easily
discoverable by the most casual attempts, the P's clearly aren't trying to
keep this a secret they're just trying to frighten people to defend their
licensing scheme.

"All your base are now belong to us."  Game over!

John Zulauf




Date: Fri, 2 Mar 2001 10:29:00 -0800
From: Seth David Schoen <schoen@loyalty.org>
To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

John Young writes:

> Sorry to belabor this point, but the Hoy file did not contain DeCSS.
> The only DeCSS-related items were two brief DeCSS introductory 
> notes (Exhibit A), but not the DeCSS code itself. The only code in the
> doc (Exhibit B) was that of CSS, mislabeled in handwriting
> "DeCSS," but titled in print "CSSscrambleT.txt".

I'm a little skeptical of that because that code bears a number of
similarities to the descramble code hosted in Professor Touretzky's
Gallery, including function and variable names (im1, im2, sec,
csstab1..5, and so on).

The DMCA makes me fear to post here excerpts of the two in order to
discuss whether or not they have the same origin.  And I think that's
lovely example number one billion of the DMCA's adverse effects on
speech which has no connection to "circumvention".

I would _like_ to quote the C code from the Gallery and I would _like_
to quote the Hoy declaration you formerly published in support of an
argument the Hoy was quoting some version of DeCSS or another
implementation that was based on DeCSS -- the "CSSscrambleT.txt"
filename notwithstanding.  But I'm afraid for the legal consequences
if I do that.

So all I can do is say that it looks to me like the Hoy declaration
was actually quoting a version of DeCSS, and if you compare it with
the descramble code in Touretzky's gallery, you will observe many
similarities.  I don't think that Hoy was actually quoting CSS
reference implementations, but of course we could always ask him.

-- 
Seth David Schoen <schoen@loyalty.org>  | And do not say, I will study when I
Temp.  http://www.loyalty.org/~schoen/  | have leisure; for perhaps you will
down:  http://www.loyalty.org/   (CAF)  | not have leisure.  -- Pirke Avot 2:5



From: "John Zulauf" <johnzu@ia.nsc.com>
To: dvd-discuss@eon.law.harvard.edu
Subject: RE: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter
Date: Fri, 2 Mar 2001 12:01:51 -0700

Seth David Schoen  Sent: Friday, March 02, 2001 11:29 AM

> So all I can do is say that it looks to me like the Hoy declaration
> was actually quoting a version of DeCSS, and if you compare it with
> the descramble code in Touretzky's gallery, you will observe many
> similarities.  I don't think that Hoy was actually quoting CSS
> reference implementations, but of course we could always ask him.

so we have Hoy on the record as citing DeCSS as CSS.  Could this be useful?

If DeCSS is CSS how can it be a circumvention of CSS.  "This is the key to
my house -- it circumvent the key to my house."  Doesn't fly logically.

If DeCSS is CSS are the same, then how can only one be illegal.  If a=b and
b=legal, a=legal or the opposite.  Thus either DeCSS cannot be banned, or
CSS must be.

Hmmm...

jz



Date: Fri, 2 Mar 2001 13:52:53 -0800
From: Seth David Schoen <schoen@loyalty.org>
To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

John Zulauf writes:

> so we have Hoy on the record as citing DeCSS as CSS.  Could this be useful?
> 
> If DeCSS is CSS how can it be a circumvention of CSS.  "This is the key to
> my house -- it circumvent the key to my house."  Doesn't fly logically.
> 
> If DeCSS is CSS are the same, then how can only one be illegal.  If a=b and
> b=legal, a=legal or the opposite.  Thus either DeCSS cannot be banned, or
> CSS must be.

CSS is a _system_, not a program.  Think of it like Blowfish or DES or
RC4 or a file format or protocol.




Date: Fri, 02 Mar 2001 15:50:46 -0500
To: dvd-discuss@eon.law.harvard.edu
From: John Young <jya@pipeline.com>
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

Seth is correct that the Hoy Reply CSS code matches
the first listed code on Dave Touretzky's DeCSS Gallery. 
I've just compared the two and they appear to be the same.

However, I've also reviewed Frank Stevenson's implementation,
from which Dave got the code, and several permutations by 
others which appeared on the LiViD list. And, correct me if 
I'm wrong, the CSS code is used within nearly all CSS 
descramblers, including the aboriginal DeCSS, but each
requires more than the CSS descrambler to function as
a "DeCSS."

So, to term the CSS code DeCSS does not appear to
be accurate, unless you believe the css-descrambler is 
"DeCSS" no matter how the descrambling is done outside 
the control of the CSS-control crowd. Hmm, I think that is
exactly what the Damn-DeCSS-mob is screeching, or
more politely, bluffing.

OK, so for the damners DeCSS is a generic euphemism, 
as well as a fit-all epithet, ready for camouflaging whatever 
deliberate weakness was designed into CSS so that DMCA 
anti-circumvention generosity could be narrowed in 
court.



From: D
To: "'jya@cryptome.org'" <jya@cryptome.org>
Subject: http://cryptome.org/dvd-hoy-reply.htm
Date: Fri, 2 Mar 2001 13:58:05 -0800 

I was trying to recall exactly what was in the
file after seeing that you had replaced it.

It turns out my recollection was more or less
correct.  I found more than a thousand copies of
the webpage with google.com (3,120, I imagine
a good chunk are discussion on how stupid it was 
letting the "trade secrets" into a public record 
(even if it was later sealed).

I seem to recall that the Federal government and
public law don't allow information that can be
found in the public domain to be classified.  Sort
of a doctrine of once public, always...

I guess some lawyers need to jack up their billable
hours, or perhaps this is how the MPAA will show
economic loss - paying for lawyers fighting windmills.

I am kind of puzzled about the legal thinking behind
demanding you take down a document that you acquired
from a publically accessible site.  The openlaw dvd
discussion seems to imply that the current court action
is separate from the trade secret issue.



Date: Fri, 2 Mar 2001 23:51:11 +0100
From: Jon Lech Johansen <jon@nanocrew.net>
To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

On Fri, Mar 02, 2001 at 10:38:32PM +0100, Tom (tom@lemuria.org) wrote:
> On Fri, Mar 02, 2001 at 11:53:55AM -0600, Eric Seppanen wrote:
> > You might want to check http://free-dvd.org.lu/ , they have a file "all
> > player keys" at http://free-dvd.org.lu/random-numbers.txt .  I have no
> > idea if they're for real.
> > 
> > Otherwise, you could try looking in the DeCSS source; there's supposed to
> > be a key in there somewhere, though I can't seem to find it.
> 
> AFAIK only the first release had the xing player key build-in. later
> releases brute-forced the key with frank's divide&conquer attack.

DeCSS has never contained any code which cracks the CSS algorithm.
The first release contained 1 player key, while the last release
contained 2 player keys. The CSS implementation in both of these
were identical.

-- 
Jon Johansen
nanocrew.net



Date: Fri, 2 Mar 2001 13:49:50 -0800
From: Seth David Schoen <schoen@loyalty.org>
To: dvd-discuss@eon.law.harvard.edu
Subject: Re: [dvd-discuss] Re: March 2001: DVD Hoy Reply Demand Letter

John Young writes:

> So, to term the CSS code DeCSS does not appear to
> be accurate, unless you believe the css-descrambler is 
> "DeCSS" no matter how the descrambling is done outside 
> the control of the CSS-control crowd. Hmm, I think that is
> exactly what the Damn-DeCSS-mob is screeching, or
> more politely, bluffing.

I agree entirely, and I think your earlier point that this declaration
does not contain a circumvention device is correct for two reasons:

(1) Software is not a device; only a machine instructed by software is
a device.
(2) (More concretely.)  The code in the declaration is not complete
and you can't possibly run it by itself or use it by itself to decrypt
DVDs.  On the other hand, you can read it to understand part of how
DVDs are decrypted.

The point that I think is important is that the Hoy declaration does
not contain a copy of any CSS implementation originally created or
published by the DVD CCA.

> OK, so for the damners DeCSS is a generic euphemism, 
> as well as a fit-all epithet, ready for camouflaging whatever 
> deliberate weakness was designed into CSS so that DMCA 
> anti-circumvention generosity could be narrowed in 
> court.

I warned here some months ago that calling all DVD descrambling code
"DeCSS" (as studios, courts, and activists who should know better have
done) is ridiculous.  "DeCSS" is a specific program written by
specific people at a specific time.

Other programs with similar or analogous functions or which
incorporate insights from DeCSS _are not DeCSS_.  The descramble code
by Derek Fawcus is definitely not DeCSS, yet it was _that_ code which
Copyleft published on their "DeCSS" t-shirt.

And any number of mirror sites which offer the original Fawcus code, or
libcss or something, invite us to "download DeCSS" when that's not
what they're providing.  That is just a factual error.

We need to say that things other than DeCSS are not DeCSS.  I think
even defense lawyers are getting this wrong.

-- 
Seth David Schoen <schoen@loyalty.org>  | And do not say, I will study when I
Temp.  http://www.loyalty.org/~schoen/  | have leisure; for perhaps you will
down:  http://www.loyalty.org/   (CAF)  | not have leisure.  -- Pirke Avot 2:5