December 2003 - cypherpunks-legacy

Re: how to release code if the programmer is a target for (fwd)
by Jim Choate 17 Dec '03

17 Dec '03

Forwarded message: > Subject: Re: how to release code if the programmer is a target for (fwd) > From: Ryan Lackey <rdl(a)mit.edu> > Date: 17 Jan 1998 19:07:10 -0500 > Eternity delivers data. It's up to the user to verify that the data is > what they want > The original question was how to verify the eternity server source code. How are these fundamently different? Assume for a moment that as a user of an eternity server the source is the data I want. > I assume the following: > * a potentially corrupted author (give rdl $100 000 and he'll probably > make a minor modification which has no apparent mal effects, give him > $100 000 000 and he'll be a hired gun). The author is optionally > anonymous. The point I am making is that whether the author is corrupt or not is irrelevant. > * A community of publically-known cypherpunks and code-verifiers, > not all of which are corrupted, but some of which may be. Ok. > * A random user who has the public keys of at least (thresh) number of the > cypherpunks, optionally the key of the author of the document/product before > the system becomes questionable, perhaps by looking in the NY Times > for 1 Jan 1999 which has a full page ad taken out by Cypherpunks Anonymous > with the PGP public keys for the 100 leading cypherpunks. Pretty expensive and rather unrealistic I suspect. Where does this random user come from? What is '(thresh)'? What good would an anonymous key signature provide? You can't verify it within the web of trust model, that would imply the author wasn't anonymous which takes us back to the 'friends' attack. How do we know that some number of these cypherpunks aren't turned? Are you proposing that the user test all 100 of the signatures? Which realisticaly is the only way to verify any given one of them. Not very many people will go to that extreme simply for grins and giggles. > * The piece of code to be verified is bloody long, that is, longer than > any one cypherpunk can afford to verify alone (shooting practice, > installing the minefields and poison gas sprinkler system, etc. take > lots of time) The standard is programs over ~10k lines is not comprehensible by a single individual on a line by line basis. > * The user can tell by visual inspection that a small compilation > system does what they want it to do, and can understand basic logic > enough to tell what signatures imply. 'small compilation system' of what? What who wants it to do? The author? Mallet? The end user? > Then: > 1) The author releases the code into the network in an optionally > anonymous way. There is no reason to trust the code -- even if it > is signed with rdl's eternity dds signing key, no one has any reason > to believe that it isn't an NSA front, since rdl is assumed to be > corrupt, signing anything put in front of him (as long as sufficient > money is put there too) It isn't the key of the author or the eternity server that is under attack by Mallet. It is the security of the individual user who is under assault. > 2) The user wants to run the code, because it's Just That Cool. We're talking here about users who want to get data that is illegal or otherwise incriminating or dangerous to one group or another. In particular let's consider the situation of a Lebanese freedom fighter in Isreal or perhaps a 'Free Burma' revolutionary in China. > 3) No one can verify the entire code. So, Cypherpunks begin signing > small sections of the code with their own previously-established key. > Their keys are established as their reputation is established on > the list, or perhaps by personally meeting these people, in the > traditional PGP web of trust scheme. There is no central Cypherpunks > Registry, just a decentralized mesh. Which doesn't effect the ability of Mallet to resign that code at the users end in order to break the users local security. > 4) The user executes the compilation script. [material describing script verification deleted] Mallet can re-write said script, especialy with the sorts of latency that the Eternity Server forces on the end user, such that it is consistent with the bogus keys the end-user gets. It is simply much easier to write scripts in a day than say 10 minutes. > I fail to see how the specifics of Eternity are relevant -- it's > just basically a PGP web of trust issue. The transport is irrelevant -- > it's untrusted code until it's been verified by people the user > trusts. The end user may not have people available to trust is the point. The reason the transport mechanism is relevant is that it is much easier to spoof a verification script if the user is not going to be surprised with 24 hour turn around on requests, whereas a responce time measured in minutes lessens the window of opportunity to Mallet significantly. It may come as a surprise to you and others but not everyone in the world can pick up a phone and call a 100 people all over the world and not raise some suspicion. > Implementing a keyserver in Eternity has the same issues While it is perfectly permissible to design Eternity or any data haven with inherent key servers, I believe it is a bad idea from a design perspective because it makes the code even larger, decreases the potential for monetary motives for indipendant key servers to appear, and if the server is compromised then the key server is also. It is more expensive if Mallet can be forced to deal with two indipendenat operators then a single monolithic operator. [rest deleted] ____________________________________________________________________ | | | The most powerful passion in life is not love or hate, | | but the desire to edit somebody elses words. | | | | Sign in Ed Barsis' office | | | | _____ The Armadillo Group | | ,::////;::-. Austin, Tx. USA | | /:'///// ``::>/|/ http://www.ssz.com/ | | .', |||| `/( e\ | | -====~~mm-'`-```-mm --'- Jim Choate | | ravage(a)ssz.com | | 512-451-7087 | |____________________________________________________________________|

2 1

uh,
by wabe 17 Dec '03

17 Dec '03

--What is that weird lawsuit all about wheresome director of the NSA is getting sued forsomething? Does anyone know?-wabe --digsig EojdyErVslc/s6aQeIHwnOlMw3lUKJhdZc/ZeCNfe7H L4ctAUj8gI6C830BTXaeFrhHME7aCeT3ev4HKbeT 4HICjjQYriAdlICrERT+zrSEtB1bkK+b6iRoC6a0y

5 8

Eternity - an alternative aproach (take 2)
by Kay Ping 17 Dec '03

17 Dec '03

"Romeo, she is a female Homo Sapiens, not a full rotation of the Earth during the season when the incident solar radioation is at a higher angle" "Yes, I know that. It was just a metaphore." I got several comments about my posting, all of them about the possibility of detecting the location of radio transmitters or receivers. You just didn't get it, did you? I was using radio as a METAPHORE for the use of broadcast to provide anonymity to receivers and packets with false source addresses for the anonymity of transmitters. You can read the original posting at http://infinity.nus.sg/cypherpunks/current/0107.html ----------------- Kay Ping nop 'til you drop finger kping(a)nym.alias.net for key DF 6D 91 18 A6 59 41 96 - 89 01 69 B7 9D0 4 AE 53

1 0

Unofficial transcript of Bernstein hearing published
by John Gilmore 17 Dec '03

17 Dec '03

EFF has published an unofficial transcript of the hearing in front of three judges at the Ninth Circuit Court of Appeals in San Francisco on December 8. The hearing discussed whether the export controls on cryptography are an unconstitutional prior restraint on publication. See http://www.eff.org/pub/Privacy/ITAR_export/Bernstein_case/Legal/ There is no news on the judges' decision from that hearing. John Gilmore Electronic Frontier Foundation

2 1

Re: (eternity) Eternity as a secure filesystem/backup medium
by Ryan Lackey 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- > Since documents placed on eternity by specification last forever (assuming, > of course, that > eternity will too) and assuming that computational power and cryptanalysis > will always > get better (say for arguments sake that moore's law continues to be held) - > doesn't that > mean that it will be feasible (in time) to break all eternity documents? :) Documents by specification last only as long as someone is willing to pay to keep them up. This is not necessarily forever. Once your DBC escrow "account" runs out, the data is worthless -- someone could then choose to store it on their own, and potentially charge others for this in a recursive model, but there is no reason why a piece of data must remain in Eternity forever if no one cares enough about it to pay to have it stored. > > Of course "in time" may very well be a very long (or astronomical) time, > but dependent on the crypto > used who knows what rate "feasible" breaking of a particular algorithm > might progress at, say > in d(key length)/d(year)? Can we assume that using Moore's law this is at > least 1 bit every > 18 months for symmetric crypto? Perhaps we might see this relationship > through the RSA challenges > over time. I am designing Eternity DDS with IDEA/3DES/Blowfish level private-key crypto and an equivalent level of DH/RSA public key crypto. These will be strong (provided back door attacks, fundamental breakthroughs in cryptography, etc. are not made...a bet I'm forced to make, even though I don't like it) well into the future. How far? I think unless Quantum Cryptanalysis becomes a reality, the underlying hard problems will not be solved through anything but a fundamental change in mathematics. As Prof. Micali said, "Gauss (Karl Friedrich Gauss, the reknowned mathematician/physicist/general smart guy) worked on these problems. The test of whether a problem is sufficiently hard to be a basis for a cryptosystem is if Gauss tried to solve it and failed." or something similar. > > [If Wiener's $1m DES machine in '93 took 7 hours, in today's technology $1m > in 1998 dollars should > be able to do this in less than 100 minutes, shouldn't it?] I don't think anyone would argue that 56bit is secure enough for anything but ephermeal channel authentication. I'd make the same argument for 64bit -- if you had a purpose-built machine with an intelligent key distribution system, a well nigh unlimited budget (read: US Military), and PE's which contained either ultrahigh performance GaAs logic or massively parallel on a single chip silicon logic, you could probably brute force a 64bit algorithm. Do the math, though, for 128bit. There are traditional analyses which include the amount of silicon on the earth, the number of atoms in the universe, etc. The general consensus is that traditional techniques are not feasible for brute forcing 128bit ciphers before the heat death of the universe. > > Since documents cannot be retracted or re-encrypted you really have to > assume that someday they > will be broken. This really turns the notion of what crypto to use for > encrypting eternity documents > into an upfront question of "how long do I want this information to be > secure?". 20 years? 50 years? > 100 years? > > matt Actually, Eternity is no different than emailing a file, given a SIGINT capability at the attacker which allows all internet traffic to be monitored. If the data is still relevant and worth breaking in 50 years, they could just intercept the encrypted email, store it in a government vault for 50 years, then attack it (even more amusingly, they could simply post it to Eternity themselves, encrypted with their own key :), a true turn about). If you do not postulate that level of signals collection capability on the part of the attacker, yeah, Eternity is a bit different than email. But I think that would be an unreasonable model of the attacker. - -- Ryan Lackey rdl(a)mit.edu http://mit.edu/rdl/ -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQEVAwUBNMISuKwefxtEUY69AQFB1Qf9GWDn6bwhWyJcDY0Liypo21ntpH5yzORu RXwkPSI8pbmqhVZAVGXC1WbcqY0pYn7vPRFq5AKszFsjpTOOYiHwsugmVKjrxVww GRKSBqn308aAjMogNtPwEfohJrQxOED/Hy7ykV6gHV76pUFoMazQ4OdUL2iM1hLF cCMzwtpfJM5eWvyLeQcQq307998epJ9hF1e3Sn4v6ZKEPIlr0yqr5tvM7/XWxC2s 6t82EUPmOZIbn75QQqLBIFK5MlOLuvalFr0xR3u7fYltOczAMC23hx7Tjk65e9a4 6XSeEXyMp2j2GWqcE5lUZp4OnewZvSoFhEj0rDo5PEN9ce0mJEKMow== =7IBY -----END PGP SIGNATURE-----

2 1

Re: (eternity) Eternity as a secure filesystem/backup medium
by Adam Back 17 Dec '03

17 Dec '03

[horrible line wraps btw. 100 chars to the line! I reformatted.] Matt Barrie writes: > Since documents cannot be retracted or re-encrypted you really have > to assume that someday they will be broken. This really turns the > notion of what crypto to use for encrypting eternity documents into > an upfront question of "how long do I want this information to be > secure?". 20 years? 50 years? 100 years? There are 3 distinct threats. 1. communications crypto used by the author in submitting the document is broken 2. the eternity architecture contains encrypted documents to frustrate attempts to locate documents, and to hide the contents of documents from individual servers 3. communications crypto used to request and deliver documents is broken thus revealing the readers identity For threat 1. the attacker needs archives of old communications which could potentially be eternity submissions. (I say potentially because they could be steganographically encoded). It is probably reasonable to assume that the NSA has a full historic archive of USENET. Also it is probably reasonable to assume they have a historic archive of all inter remailer traffic. For threat 2. it seems feasible to upgrade this security over time, in that documents could be super encrypted with newer ciphers when vulnerabilities are found in older ciphers. No protection for historic access requests, but at least we can adapt to protect new requests. For threat 3. again newer ciphers can be used as attacks are found. So it is useful to design upgrade paths for ciphers into the protocols where possible. Other approaches we could take are to use very conservative cipher key sizes and protocols combining multiple ciphers in ways which gives us the security of the best of the ciphers. For example: R = random, C = 5DES( R ) || blowfish-484( M xor R ) Where 5DES is say E-D-E-D-E with 5 independent DES keys. Constructs to combine in strong ways hash functions, macs, symmetric and asymmetric ciphers would be useful. Is there much research in this area? Adam

1 0

Re: (eternity) Eternity as a secure filesystem/backup medium (fwd)
by Jim Choate 17 Dec '03

17 Dec '03

Forwarded message: > Subject: Re: (eternity) Eternity as a secure filesystem/backup medium > Date: Sun, 18 Jan 1998 09:33:30 EST > From: Ryan Lackey <rdl(a)mit.edu> > Documents by specification last only as long as someone is willing to pay > to keep them up. This is not necessarily forever. Admiral Hopper used to give a talk about the worth of data and she had a very nice chart that would demonstrate the worth of data over time. Initialy it is worth a lot because it is hard to reproduce, obtain, or distribute. As time goes on it becomes less and less important. In her particular context it was related to the economic decision of when to move data offline in large database applications. > Once your DBC escrow > "account" runs out, the data is worthless That's a jump of logic. The data may infact be quite popular even though you don't offer it anymore (might even do this in order to increase its worth, say some sort of insider trader newsletter). It's probably not in the best interest of the data haven model to speculate on exactly why a particular source decides to quit sourcing. > remain in Eternity forever if no one cares enough about it to pay to > have it stored. Then again, if it was really important I might intentionaly want to attack the ability to provide long-term income. A better model might be to charge for the access and let the actual submission be no charge. A portion of the retrieval charge could then be piped back to the source. Consider the case of say nuclear or biological information for a weapon. That sort of data would be accessed only infrequently (unless you're giving something this expensive to obtain and verify away - a d-h operator error, no.) but should be quite expensive to retrieve. > If the data is still relevant and worth breaking in 50 years, they could > just intercept the encrypted email, store it in a government vault for > 50 years, More realisticaly they would have somebody just add it to a batch job and let the spare cycles of the machines crank away at it. Or perhaps set up a key challenge and get people all over the world to work on it in their spare cycles. Who knows, perhaps the source of the data woudl be intriqued enough to provide spare cycles unknowingly. > If you do not postulate that level of signals collection capability on the It's not just their sig-int capability but their complete processing resource capability that must be considered as well as their psychological motivation. Granted, all of these are extremely difficult to measure let alone verify. Perhaps a little paranoia might be a good thing. ____________________________________________________________________ | | | The most powerful passion in life is not love or hate, | | but the desire to edit somebody elses words. | | | | Sign in Ed Barsis' office | | | | _____ The Armadillo Group | | ,::////;::-. Austin, Tx. USA | | /:'///// ``::>/|/ http://www.ssz.com/ | | .', |||| `/( e\ | | -====~~mm-'`-```-mm --'- Jim Choate | | ravage(a)ssz.com | | 512-451-7087 | |____________________________________________________________________|

1 0

diplomacy
by bill payne 17 Dec '03

17 Dec '03

I sure hope the following was diplomatic enough. NSA exhibited NO SENSE OF HUMOR when I pointed out 'deficiencies' in its crypto algorithm work. But, too, the agrieve Islamic fundamentalists may not have too good senses of humor. But with that experience, my sensitivities are hightened. Later, guys. Back to POSTCARD COMMUNICATIONS! Sunday 1/18/98 6:24 AM Jim Allen Thanks for the call on Friday night. You said that there might be a problem in the way the interrupts were turned on. I told you I would give this some thought. Here is the routine to turn on the interrupts ;* Call DasIntOn(IoPointer&, ErrorFlag&, SystemState&, IoData&(0, 0), ;* IoParm&(0, 0), LgradThres) from Visual Basic. DasIntOn PROTO FAR, VBIoPointer:dword, VBErrorFlag:dword, VBSystemState:dword, VBIoData:dword, VBIoParm:dword, VBLGradThres:dword DasIntOn PROC FAR EXPORT, VBIoPointer:dword, VBErrorFlag:dword, VBSystemState:dword, VBIoData:dword, VBIoParm:dword, VBLGradThres:dword Prolog ;* Stage 1 Get addresses of IOPointer, ErrorFlag, SystemState, ;* IoData, IoParm, LGradThres which point back into VB static array. mov eax, VBIoPointer ; get VB IoPointer address mov IoPointer, eax ; move it to asm mov eax, VBErrorFlag ; get VB ErrorFlag address mov ErrorFlag, eax ; mov it to asm mov eax, VBSystemState ; get VB SystemState address mov SystemState, eax ; move it to asm mov eax, VBIoData ; get VB IoData address mov IoData, eax ; move it to asm mov eax, VBIoParm ; get VB IoParm address mov IoParm, eax ; move it to asm mov eax, VBLGradThres ; get VB LGradThres address mov LGradThres, eax ; move it to asm ;* Stage 2 zero the interrupt counter and system state mov IntCount, 0 mov LocalSysState, 0 ;* Stage 3 install dummy interrupt vector call SetDummyIntVector ; Set dummy IrqLevel interrupt ;* Stage 4 make sure interrupt is masked on the das board call DisableDasInt ;* Stage 5 Set up Irq level in bits 4-6 of register 9 call SetDasIrqLevel ;* Stage 6 set up counter 0 with number of rows AND enable ;* hardware trigger. This is done in Counter0SetUp. call Counter0SetUp ;* Stage 7 Enable interrupt on 8259a call EnableIrqMask ;* Stage 8 Set Irq 5 highest prority in 8259a - didn't seem to ;* make any difference in performance ; call Irg5HighestPriority ;* Stage 9 Burst length set-up call EnableDasBurstMode ;* Stage 10 - clear fifo call InitDasFifo ; read and discard 256 fifo words ;* Stage 11 Set application interrupt vector call SetDasIntVector ; Set IrqLevel interrupt vector ;* Stage 12 Set LocalIop to DataRows - 1. MOV ax, DataRows - 1 ; set LocalIop = DataRows mov LocalIop, ax ; les bx, IoPointer ; get address IoPointer% mov es:[bx], ax ; also set VB IoPointer% = 0 ;* Stage 13 Set hardware trigger call SetHardwareTrigger ;* Stage 14 Clear flip-flop on Pin 25 call ClearDasPin25 ;* Stage 15 Enable interrupt on das board call EnableDasInt Epilog ret 24 DasIntOn ENDP This got a bit complicated. The ComputerBoard clone of the Keithly-Metrabyte a/d converter powers-up in an UNKNOWN state. Or at least partially UNKNOWN. One of the random states includes triggering spurious interrupt. So a dummy handler had to be inserted to possibly field bad data. The attempt was made to interface directly to hardware without a microcontoller buffer was partially successful. Sampling at the 1 Khz rate revealed that Windows occasionally did its own thing as a result of a task switch and, therfore, interrupts were missed. To detect when this happened we modified the ComputerBoards das 1400 board so that a hardware count of interrupts received could be compared to the software count. Since the a/d values were buffered a FIFO, the FAST Pentium could catch up. But this caused the interrupt handler to increase in size from about 1 K lines, including white space and comments, to 2 K lines. Naturally we wish to be in the problem solving, as opposed to problem creating, or assignation of blame. I think we have to consider all possible problem sources. I am looking at the AC POWER INTERFACE LS SOV Schematic dated 11-8-96. I see that the power to the analog and digital cards was run via a serial port db 25 cable and connector. Pin assignment are Pin Function 1 -15 G 2 +15 GS 3 +5 G 4 +15 G 5 5 GS 6 tied to pin 7 7 +15S 8 15 S 9 5 10 tied to pin 10 11 +15 12 tied to pin 11 13 15 S 14 tied to pin 1 15 +5 GS 16 tied to pin 3 17 nc 18 tied to pin 5 19 +24 ground 20 tied to pin 19 21 +5 S 22 tied to pin 9 23 tied to pin 22 24 +24 volts 25 tied to pin 24 The +24 volts runs to solenoids. The remaining power runs to both digital and analog Ics. While some are left wondering why engineers had not thought of running analog, digital and solenoid power down an inexpensive 24 pin PC serial port cable before, perhaps, we might all guess, other engineers lack sufficient innovative audacity. One engineer opined last summer, when I was working in the shop on the digital FX, that the PC Data System boards may have to be redesigned. Lets hope that such a major revision is not required. Naturally, me being a TOTAL CONSERVATIVE [as evidenced by Morales and my genocide court filing], I plan to physically separate the analog and digital IC s on the digital FX. And I am thinking about on-board power regulation to keep the 80c32, analog, and digital chips super-happy. In the field, of course. I will leave in several hours. In my grey rabbit. Air travel safety worries me more now. Especially after publication of last book. Just in case, I will bring my passport. The thought of two machines located 180 miles NW of Edmonton not working well is, of course, chilling. I sure glad the 8051 version of PC Data System is working fairly well. And is MAKING money for Metriguard. See you on Tuesday, Allah willing. Later bill Title: Payne/Morales v. NSA -- Defendant's Response to Motion for Summary Judgment 16 January 1998 Source: William H. Payne See related files: http://jya.com/whpfiles.htm U.S. Department of Justice United States Attorney District of New Mexico __________________________________________________________ Post Office Box 607 Albuquerque, New Mexico 87103 505/766-3341 505/766-2868 FAX 505/766-8517 January 5, 1998 W.H. Payne P.O. Box 14838 Albuquerque, New Mexico 87191 Re: Payne & Morales v. Minihan USDC NM CIV 97-0266 SC/DJS Dear Mr. Payne: Enclosed is a court-endorsed copy of Defendant's Response to Plaintiffs' Motion for Summary Judgment Based on Evidence from Admissions. Sincerely, JOHN J. KELLY United States Attorney [Signature] JAN ELIZABETH MITCHELL Assistant U. S. Attorney JEM/yh Enclosure cc/enc: Arthur R. Morales [Stamp] FILED United States District Court District of New Mexico 98 JAN -5 PM 3:46 Robert M. Marsh District Clerk IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF NEW MEXICO WILLIAM H. PAYNE ) ARTHUR R. MORALES ) ) Plaintiffs, ) ) vs. ) CIVIL NO. 97-026 SC/DJS ) LT GEN KENNETH A. MINIHAN ) USAF Director, National Security ) Agency, ) ) Defendant. DEFENDANT'S RESPONSE TO PLAINTIFFS' MOTION FOR SUMMARY JUDGMENT BASED ON EVIDENCE FROM ADMISSIONS Defendant Minihan responds to Plaintiff's Motion for Summary Judgment Based On Evidence From Admissions1 as follows: 1. Commencing in October, 1997, Plaintiffs served numerous sets of Requests for Admissions on various employees of the National Security Agency and on current and past employees of the Sandia National Laboratory. 2. Counsel for Defendant was not served with copies of any of said Requests for Admissions until sometime after the individuals had been served.2 ____________________ 1 It should be noted that the instant Motion for Summary Judgment constitutes Plaintiffs' second motion for summary judgment. Plaintiffs filed an initial Motion for Summary Judgment on June 4, 1997 to which Defendant responded on June 19, 1997, and Plaintiffs filed a Reply on July 1, 1997. Said initial Motion for Summary Judgment has not been ruled upon. In addition, Defendant filed a Motion to Dismiss Plaintiff Arthur R. Morales on September 23, 1997, and a Motion seeking dismissal of Plaintiff William Payne's Freedom of Information Act action on October 3, 1997. All briefing by all parties has been completed on those Motions. 2 On October 13, 1997, Plaintiffs mailed a First Set of Admissions to Kenneth Minihan. However, not until November 3, 1997, did Plaintiffs mail a copy of said First Set of Request for 3. Upon becoming aware that Plaintiffs had served Requests for Admissions on a number of individuals, on October 23, 1997, Counsel for Defendant filed a Motion and Memorandum To Strike Any And All Of Plaintiffs' First Set of Requests For Admissions To Various Employees Of The National Security Agency And To Various Employees Of Sandia National Laboratory, (hereinafter "Motion and Memorandum.") 4. As grounds for the Motion and Memorandum, Defendant argued that Plaintiffs had blatantly disregarded this Court's Order pertaining to the conduct of discovery and the deadline for discovery in this Freedom of Information Act action. 5. In Defendant's Motion and Memorandum, Counsel for Defendant also objected to Plaintiffs' sua sponte decision to modify the Court's June 11 Order to reflect the delay of the Court's October 7 Order and the establishment, without leave of this Court, of new deadlines for discovery, motions practice, and the filing of the PreTrial Order. (Motion and Memorandum ¶ 9, at 4.) 6. In the Motion and Memorandum, Defendant requested that this Court strike any and all "First Set of Request for Admission" propounded by Plaintiffs. (Motion and Memorandum, at 5.) 7. Plaintiffs responded to the Motion and Memorandum on November 5, 1997, specifically seeking that this Court "take no action in this case until Supreme court takes action on writs on ____________________ Admissions to Counsel for Defendant. Counsel for Defendant was not provided with copies of any other Requests for Admissions sent to employees of NSA or employees of the Sandia National Laboratory. 2 mandamus, prohibition, and criminal complaint affidavits filed against judges Svet and Campos and US Attorney Mitchell." (Plaintiffs' Response to Motion And Memorandum To Strike Any And All Of Plaintiffs' First Set Of Request For Admissions To Various Employees Of The National Security Agency And To Various Employees Of Sandia National Laboratories, ¶ 11, at 10.) 8. To date, no order has been issued by this Court on the matters raised in the Motion and Memorandum, nor has any other court issued any orders concerning Plaintiffs' cause of action and various complaints. 9. By their own request, Plaintiffs sought to stay a ruling on the Defendant's Motion and Memorandum. Absent any ruling on either the Motion and Memorandum or Plaintiffs' Response, Defendant Minihan, employees of NSA, and employees of Sandia National Laboratory, were not obligated to respond to the Requests for Admissions as provided by Fed.R.Civ.P. 36.3 For Plaintiffs to now assert in their "Motion for Summary Judgment On Based On Evidence From Admissions" that because the individuals have not responded to the Requests for Admissions they are deemed admitted, flies in the face of their own prayer to this Court to stay a ruling on the Defendant's Motion to strike the Requests for Admissions until the Supreme Court takes action. ____________________ 3 Despite the fact that Defendant's employees and other individuals are not required to respond to the Requests for Admissions based upon the outstanding pleadings which have yet to be ruled on by this Court, Plaintiffs characterize that all admissions are admitted and then publish those admissions on the Internet. 3 10. Defendant requests that this Court either rule upon Defendant's Motion and Memorandum granting the request to strike the Requests for Admissions, or grant Plaintiffs' request to stay this action pending the issuance of the order sought by Plaintiffs in another forum. Should this Court deny Defendant's Motion and Memorandum, Defendant respectfully requests that the individuals to whom Requests for Admissions are appropriate in this action be given the thirty days to respond to said admissions as provided by the Federal Rules of Civil Procedure. 11. Plaintiffs requested a stay. Absent a ruling from this Court denying their request, they cannot proceed to assert that the Requests for Admissions are deemed admitted. Accordingly, Plaintiffs' "Motion For Summary Judgment On Based On Evidence From Admissions" must be denied. Respectfully submitted, JOHN J. KELLY United States Attorney [Signature] JAN ELIZABETH MITCHELL Assistant U.S. Attorney P.O. Box 607 Albuquerque, New Mexico 87103 (505) 766-3341 I HEREBY CERTIFY that a true copy of the foregoing pleading was mailed to PRO SE PLAINTIFFS, this 5th day of January, 1998. [Signature] JAN ELIZABETH MITCHELL Assistant U. S. Attorney 4 UNITED STATES DISTRICT COURT FOR THE DISTRICT OF NEW MEXICO William H. Payne ) Arthur R. Morales ) ) Plaintiffs, ) ) v ) CIV NO 97 0266 ) SC/DJS ) Lieutenant General Kenneth A. Minihan, USAF ) Director, National Security Agency ) National Security Agency ) ) Defendant ) REPLY TO DEFENDANT'S RESPONSE TO PLAINTIFFS' MOTION FOR SUMMARY JUDGMENT BASED ON EVIDENCE FROM ADMISSIONS 1 COMES NOW plaintiffs Payne [Payne] and Morales [Morales] [Plaintiffs], pro se litigants to exercise their rights guaranteed under the Constitution, Rules of Civil Procedure, and Local Civil Rules to respond to Defendant's MOTION filed on 98 JAN-5 within the 14 days allowed by local rule 7.3(b)(4). 2 US Attorney Mitchell [Mitchell] writes, Counsel for Defendant was not served with copies of any of said Requests for Admissions until sometime after the individuals had been served.2 Mitchell WAS SERVED PLAINTIFFS' FIRST SET OF REQUEST FOR ADMISSION TO NSA DIRECTOR KENNETH MINIHAN I HEREBY CERTIFY that a copy of the foregoing request for admissions was mailed to Jan Elizabeth Mitchell, Assistant US Attorney, 525 Silver SW, ABQ, NM 87102 this Monday November 3, 1997. Michell was not served with any other admissions since Mitchell is not representing others. Plaintiffs' served Defendant Minihan properly. And Minihan failed to respond to Minihan's admissions within the time allotted by law. 3 US Attorney Mitchell writes, As grounds for the Motion and Memorandum, Defendant argued that Plaintiffs had blatantly disregarded this Court's Order pertaining to the conduct of discovery and the deadline for discovery in this Freedom of Information Act action. Judges Svet and Campos willfully violated Plaintiffs' right to Discovery. And thereby earned criminal complaint affidavits filed with judge Scalia of the Supreme Court. 4 US Attorney Mitchell writes, In Defendant's Motion and Memorandum, Counsel for Defendant also objected to Plaintiffs' sua sponte decision to modify the Court's June 11 Order to reflect the delay of the Court's October 7 Order and the establishment, without leave of this Court, of new deadlines for discovery, motions practice, and the filing of the PreTrial Order. (Motion and Memorandum 9, at 4.) Judge Svet and Campos attempt to deny Plaintiffs' right to Discovery, again, earned Svet and Campos criminal complaint affidavits. Plaintiffs exercise their right under the Federal Rules of Civil Procedure and the Constitution to conduct Discovery WITHOUT LEAVE OF COURT! 5 US Attorney Mitchell writes, By their own request, Plaintiffs sought to stay a ruling on the Defendant's Motion and Memorandum. Absent any ruling on either the Motion and Memorandum or Plaintiffs' Response, Defendant Minihan, employees of NSA, and employees of Sandia National Laboratory, were not obligated to respond to the Requests for Admissions as provided by Fed.R.Civ.P. 36.3 For Plaintiffs to now assert in their "Motion for Summary Judgment On Based On Evidence From Admissions" that because the individuals have not responded to the Requests for Admissions they are deemed admitted, flies in the face of their own prayer to this Court to stay a ruling on the Defendant's Motion to strike the Requests for Admissions until the Supreme Court takes action. Plaintiffs' have REPEATEDLY asked judge Svet and Campos to disqualify themselves from any rulings on this case because Campos and Svet do NOT obey the Federal Rules of Civil Procedure. Replace judges Svet and Campos because these judges have demonstrated, IN WRITING, they do not follow the Federal Rules of Civil Procedure. Plaintiffs' pleas are directed a replacement judge[s]. Not Svet and Campos. Therefore, Svet and Campos' failure to remove themselves does not stop the legal process. Mitchell cites NO law to support her claim that time constraints imposed under Fed.R.Civ.P. 36.3 are inapplicable as a result of Svet's and Campos' failure to remove themselves. 6 US Attorney Mitchell writes, Defendant requests that this Court either rule upon Defendant's Motion and Memorandum granting the request to strike the Requests for Admissions, or grant Plaintiffs' request to stay this action pending the issuance of the order sought by Plaintiffs in another forum. Should this Court deny Defendant's Motion and Memorandum, Defendant respectfully requests that the individuals to whom Requests for Admissions are appropriate in this action be given the thirty days to respond to said admissions as provided by the Federal Rules of Civil Procedure. REPLACEMENT JUDGES of the Court should realize the outcome of the lawsuit has attained international interest as a result of the 1 bungled NSA spy sting on Iran 2 US government agencies NSA, NIST, and the FBI's attempt to control cryptography. Mitchell's DEFENDANT'S RESPONSE TO PLAINTIFFS' MOTION FOR SUMMARY JUDGMENT BASED ON EVIDENCE FROM ADMISSIONS was posted on Internet at jya.com, click cryptome nsasuit8.htm USA/NSA Responds to Payne/Morales Motion January 16, 1998 Importance of this posting is summed-up in the Toronto Sun, Jan. 11, 1998 US, Iran Need Each Other by Eric Margolis Iran launched a surprise charm offensive last week, throwing Washington into serious confusion. In a lengthy interview on CNN, Iran's new president, Mohammad Khatami, skillfully analyzed the bitter relations between the two nations and cautiously extended an olive branch to Washington, calling for an end to their 19-year cold war. Khatami's diplomatic ju-jitsu flummoxed the Clinton administration, which was busy trying to rally international support against Tehran - and to overthrow Iran's elected government. Both capitals are split over the question of relations. In Washington, the military establishment and conservative Republicans have inflated Iran into a bogeyman to justify military budgets and keep U.S. forces in the Mideast. ... America incited Iraq to invade Iran in 1980. They did this to crush the Islamic revolution, then provided massive war aid to Saddam Hussein. Half a million Iranians died. The US got caught involved in genocide. Using high tech. This is one subject of this lawsuit. Albuquerque Journal Tuesday 1/13/98 carried the editorial. Khatami Move Is Profile in Courage Richard Reeves Syndicated Columnist LOS ANGELES - If an American leader had done what Iranian President Mohammed Khatami did last Wednesday, it would have been hailed as a profile in courage. ... Miscalculation! We armed and pampered Saddam Hussein in the hope that Iraq would destroy Iran. Now that's policy and behavior to think about. Here is something to think about: If Presidents Eisenhower and Kennedy had pursued any kind of sensible policy toward Cuba and Fidel Castro - opposed to the policy of trying to assassinate him - there never would have been a Cuban missile crisis. I think Iranians have financed and encouraged terrorism against the interests of the United States and Israel. I would not be surprised at all if something like proof emerges soon, perhaps anonymously, from the CIA and other government agencies, where many officials have built their careers on sanctioning and isolating Iran, to try to straighten the backbones of the president and people of the United States. If they succeed, America fails. What would be more effective in closing down Iranian terrorism? More hostility, sanctions and charges? Or beginning the process toward more normal relations with a country positioned and born to be great? ... Clearly genocide fits into Now that's policy and behavior to think about. The wired world is watching what this Court, hopefully minus judges Svet and Campos, will do. What is there to be? A series of possibly unfortunate events? Or does this Court order release the lawfully requested documents to help settle this American tragedy? WHEREFORE. 7 Have replacement judges of this Court DENY Mitchell's Plaintiffs requested a stay. Absent a ruling from this Court denying their request, they cannot proceed to assert that the Requests for Admissions are deemed admitted. Accordingly, Plaintiffs' "Motion For Summary Judgment On Based On Evidence From Admissions" must be denied. for reason that Mitchell's request to subvert both the Discovery processes and its time limits have no basis in law. And appears to plead to judges who do not obey the Federal Rules of Civil Procedure. 9 IMMEDIATELY ORDER Defendant to release the requested documents in the interest of national safety so that this matter can be settled. Aggrieved victims of US genocide are reading these pleadings. Respectfully submitted, _________________________ William H. Payne 13015 Calle de Sandias NE Albuquerque, NM 87111 _________________________ Arthur R. Morales 1024 Los Arboles NW Albuquerque, NM 87107 Pro se litigants CERTIFICATE OF SERVICE I HEREBY CERTIFY that a copy of the foregoing memorandum was mailed to Lieutenant General Kenneth A. Minihan, USAF, Director, National Security Agency, National Security Agency, 9800 Savage Road, Fort George G. Meade, MD 20755-6000 and hand delivered to John J. Kelly, US Attorney, 525 Silver SW, ABQ, NM 87102 this Tuesday January 20, 1997. 5 Title: Model 7200 HCLT High Capacity Lumber Tester The Metriguard Model 7200 High Capacity Lumber Tester was introduced in 1993. This machine is now certified by grading agencies in the United States, Canada and UK. Also in use in Japan and Austria. Speed capacity is unknown. We have run tests in excess of 2,000 ft/min, and have not seen any limitations or indications that it would not run faster. We expect this machine to keep up with planer developments and run in the neighborhood of 3,000 ft/min sometime within the next ten years. The machine is available with a number of options, including the recently introduced PC Data System, which adds new capability in marking options, shift reports, and internal error checking. Yet to come in Metriguard's program of continuous improvement are automatic wood temperature compensation, automatic zero tracking, scanner inputs. Please contact Metriguard Sales office for further information about how this machine can improve your lumber grading and mill profits. Return to home page

2 1

*** OFF-SHORE INVESTMENTS ***
by ForInformationVisitUs＠OurWebSite.Now 17 Dec '03

17 Dec '03

********************************************************************* - Remove from list information is after this important message - ********************************************************************* ******* *** OFF-SHORE INVESTMENTS *** Get A Higher Rate of Return on Your Investments Projects Audited by *** Coopers & Lybrand and Price Waterhouse *** Ever wished you could earn a rate of return on your investments that have traditionally been enjoyed only by the very wealthy? Welcome to Cyber Ventures Ltd. - Your gateway to outstanding and private off-shore investment opportunities. Cyber Ventures Ltd. is an on-line venture capital and financing company incorporated under the laws of the Isle of Man. Its primary function is to raise equity capital for profitable venture capital projects. Each project promoted by Cyber Ventures Ltd. complies to established investment criteria and is fully audited to increase the security of your investments. Cyber Ventures Ltd. takes an equity stake in each project right along with you the investor and is a part of the management team of all target investments. Cyber Ventures Ltd. is designed for the relatively small investor so investments are as little as $30 and a maximum of $30,000 for any single transaction. Investors profit through: - Project profit share - Capital appreciation - Interest on capital - Referral commission on sales For more information regarding Cyber Ventures Ltd., its Policies, Project Selection Criteria, Investment Criteria, Current Projects, the Investment Structure, Auditors, and how you can participate in this outstanding and private investment vehicle, you may contact us at: Cyber Ventures Web Site: http://www.cvltd.com E-mail: Info(a)cvltd.com Fax-On-Demand: +1(703) 834-8990 Doc #110 (Please call from a fax) Direct FAX : +27(21) 948-3188 Toll Free USA FAX : +1(888) 218-7034 Message Center: +1(888) 218-7034 Cyber Venture Orders: +27(21) 948-3183 ****************************************************************** ****************************************************************** TO BE REMOVED FROM OUR MAILING LIST, TYPE: Bergston(a)ix.netcom.com in the (TO:) area and (REMOVE) in the subject area of a new E-mail and send. ****************************************************************** ******************************************************************

1 0

Signed document - a thought...
by Jim Choate 17 Dec '03

17 Dec '03

Hi, I was pondering the security issues regarding signed documents and key security. It occured to me that in all the discussion it is assumed that the document is transmitted after the key is transmitted. It seems to be that a higher level of security could be obtained by submitting the signed document first and then submit the signing key. This way when the document goes out Mallet has no idea what key to replace and any fudging of the document will destroy the sign. Then when the key goes out if it is replaced the document won't pass testing either since the server already has a unmod'ed copy. In short, instead of having each author have a signing key, have each document have a signature key and always submit the signed document prior to the signing key. After all it's the document and not the author (who we assume is already using an anonymous submission mechanism) we wish to verify from the end users perspective. The mechanims provides a means for the data haven server to verify the authenticity of the document and this allows them to pass that trust on to the end user in the same sort of way. ____________________________________________________________________ | | | The most powerful passion in life is not love or hate, | | but the desire to edit somebody elses words. | | | | Sign in Ed Barsis' office | | | | _____ The Armadillo Group | | ,::////;::-. Austin, Tx. USA | | /:'///// ``::>/|/ http://www.ssz.com/ | | .', |||| `/( e\ | | -====~~mm-'`-```-mm --'- Jim Choate | | ravage(a)ssz.com | | 512-451-7087 | |____________________________________________________________________|

2 1