December 2003 - cypherpunks-legacy

Re: Take it to sci.math
by proff＠suburbia.net 17 Dec '03

17 Dec '03

> >and > > > >4) This bullshit is extremely annoying to those of us who has some real > > training in math, even more so than the regular bullshit on this list. Perhaps your 'real training in math' could show itself and put an end to the discussion.

1 0

Re: You can now subscr. to the moderated/unmoderated/flames lists
by Toto 17 Dec '03

17 Dec '03

Dale Thorn wrote: > I don't like to admit to it, but I've practiced baiting for many years This startling announcement ranks right up there at the top of the 'surprise' scale, along with K.D. Lang's announcement that she is gay. (Like the Butch (crew-cut) hairstyle was not a major hint.) By the way, when I espoused my opinion that the moderation announcement's "your suggestions will be considered" was merely political rhetoric, I was offered (and took) a bet of 50,000 electronic porno byte-credits on whether or not I was right. My opponent and I agreed that lack of any serious recognition of the list member's input would be taken as a sign of my supposition being correct. I am of the belief that I have won the bet. Does anyone have any proof to the contrary? Toto

1 0

Re: Quantum computers/Java of a different sort
by Mike McNally 17 Dec '03

17 Dec '03

Mike McNally poorly edited a forwarded note: > ... junk ... Sorry. -- ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ Mike McNally -- Egregiously Pointy -- Tivoli Systems, "IBM" -- Austin mailto:m5@tivoli.com mailto:m101@io.com http://www.io.com/~m101 ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^

1 0

Re: Quantum computers/Java of a different sort
by Peter Trei 17 Dec '03

17 Dec '03

> From: Mike McNally <m5(a)vail.tivoli.com> > To: cypherpunks(a)toad.com > Subject: Quantum computers/Java of a different sort > For all you quantum computer fans, see > > http://sciencenow.sciencemag.org/html/970117c.htm > -- > Mike McNally -- Egregiously Pointy -- Tivoli Systems, "IBM" -- Austin Shades of the Infinite Improbability Drive! (cf Hitchhikers Guide to the Galaxy) Peter Trei trei(a)process.com

1 0

Nex type2.list/pubring.mix
by John A. Perry 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- Hello Everyone! There is a new type2.list/pubring.mix combination on jpunix.com. The Web version is located at www.jpunix.com and the FTP version is at ftp.jpunix.com. This version reflects the introduction of the wazoo remailer. John Perry KG5RG perry(a)alpha.jpunix.com PGP-encrypted e-mail welcome! Amateur Radio Address: kg5rg(a)kg5rg.ampr.org WWW - http://www.jpunix.com PGP 2.62 key for perry(a)jpunix.com is on the keyservers. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMuSrVFOTpEThrthvAQF3VQP/WnfaCY5FYNyImKDX2p5HqjevMzw98bxR SsiKqWVUTRxEd10rTxPTBfVpq/d+kfDkWs3HQEc/Z2a3LYXwZ/8bFkr9qXTP2wOq L5PjjpD3QwfJVa2wv+DWYgn07rTyKhe5kOti4YfTt//M7F3S0T/BLMuggG/BXKyB ccUyqt16PL4= =+wMo -----END PGP SIGNATURE-----

1 0

Re: Dr. Vulis' social engineering experiment
by Mike McNally 17 Dec '03

17 Dec '03

Jane Jefferson wrote: > > That appears to be the main brunt of his efforts, to "push the > envelope" of free speech in order to force it's definition. Well, the irritating part is that I think he's pushing the wrong envelope. Why anyone would expect any particular degree of "freedom" to use a service run for free by a private individual is beyond me. I appreciate the service, but I don't take it for granted and I certainly don't take it as an inalienable right. ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ Mike McNally -- Egregiously Pointy -- Tivoli Systems, "IBM" -- Austin mailto:m5@tivoli.com mailto:m101@io.com http://www.io.com/~m101 ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^

1 0

Re: Disseminating public-key crypto source code
by Greg Broiles 17 Dec '03

17 Dec '03

At 01:11 PM 1/20/97 -0500, Jon Orwant wrote: > 2) PKPesque: Using public-key crypto is an infringement, > although disseminating/possessing the source > code is not. Disseminating (and even writing) the source code may be an infringement. 35 USC 271 says: "Infringement of patent (a) Except as otherwise provided in this title, whoever without authority makes, uses, or sells any patented invention, within the United States during the term of the patent therefor, infringes the patent. (b) Whoever actively induces infringement of a patent shall be liable as an infringer. (c) Whoever sells a component of a patented machine, manufacture, combination or composition, or a material or apparatus for use in practicing a patented process, constituting a material part of the invention, knowing the same to be especially made or especially adapted for use in an infringement of such patent, and not a staple article or commodity of commerce suitable for substantial noninfringing use, shall be liable as a contributory infringer. [...]" Sorry. Software/algorithm patents make it difficult to develop and distribute free software. If that pisses you off, tell your congresspeople you don't like software/algorithm patents. Perhaps someday Congress will develop a sensible scheme for "protecting" creators' rights in their software. But they haven't yet. -- Greg Broiles | US crypto export control policy in a nutshell: gbroiles(a)netbox.com | http://www.io.com/~gbroiles | Export jobs, not crypto. |

1 0

Re: "Technical data" exemptions in new crypto regs
by Richard L. Field 17 Dec '03

17 Dec '03

In reply to Solveig Bernstein's First Amendment challenge questions: I read the new regs as permitting: (i) publication of source code in paper form (including publications reproduced on microfilm or on prerecorded phonograph records), or in the form of a motion picture film and soundtrack (section 734.3(b)(2)); and, separately, (ii) teaching or discussion of information "about" cryptography (section 744.9). The export of other encryption materials (including the distribution to non-US persons of source or object code on diskettes) is restricted, even if the materials are publicly available "educational information" for release by instruction in catalog courses and associated teaching laboratories of academic institutions (section 734.9). Technical assistance activities that go beyond "mere" teaching or discussion of information about cryptography are restricted, if they show "intent" to aid a foreign person in the development or manufacture, outside the United States, of controlled encryption commodities and software. This is a General Prohibition (see section 736.2(b)(7)(ii)). I think one question to be resolved is: could the "mere" teaching about cryptography (which is okay), *coupled* with distribution of source code in paper form (which is otherwise okay because it is not, by itself, subject to the EAR - see note to section 734.3(b)(2) and (b)(3)), be considered a violation of the EAR because it demonstrates "intent" to aid a foreign person in the development of encryption software? One would hope not (see Bernstein), but the new 734.9 seems to imply that such a combination may be restricted. Thus, a potental First Amendment challenge to the new regs would be a challenge to a restriction on teaching coupled with paper publication/distribution of source code. Another would be a challenge to the restriction on non-paper publication/distribution, whether or not coupled with teaching. - Richard Field (For discussion purposes only. Not legal advice or a legal opinion.) On Mon, 20 Jan 1997 14:45:44 -0500 (EST) you wrote (to Declan McCullagh): > >What have the new crypto regs done to the "technical data" and the "public >domain" exemptions from ITAR? > >The problem is this: as I understand it, the Commerce Dept. regs exempt >teaching and print presentations generally, but these exemptions do not >apply to "encryption software." > >Does this mean that the exemptions do not apply to *teaching about* >encryption software or *publications about* encryption software? Or *only* >that the exemptions do not apply to diskette-contained source code or object >code. > >In other words, the new regs might completely decontrol teaching and >publication of something like Professor Bernstein's Snuffle. > >On the other hand, the new regs might, like ITAR, restrict teaching and >publication of Snuffle (as well as publication of source code in diskette >format). > >The purpose of the question is to understand whether a First Amendment >challenge to the new regs is a First Amendment challenge to a restriction on >*teaching, publication, and program distribution* or just a challenge to a >restriction on *program distribution.* > > >Solveig Bernstein, Esq. >(202) 789-5274 >(202) 842-3490 (fax) > >Assistant Director of Telecommunications & Technology Studies >Cato Institute >1000 Mass. Ave. NW >Washington, DC 20001

1 0

Re: Disseminating public-key crypto source code
by Michael Paul Johnson 17 Dec '03

17 Dec '03

On Mon, 20 Jan 1997, Jon Orwant wrote: > I've written a few Perl routines for public-key cryptography. I'd > like to freely disseminate the source code (starting with ElGamal) to > as many people as I can, > > It's my understanding that there are two orthogonal restrictions: > > 1) ITAResque: I can't give code to non-U.S. citizens. > 2) PKPesque: Using public-key crypto is an infringement, > although disseminating/possessing the source > code is not. > > While I'm sure these are oversimplifications, it would seem that I can > release my source code over the Internet provided I install a simple > verification mechanism (cf. MIT's PGP distribution) to ensure that > only people claiming to be U.S. citizens have access privileges. > > Am I correct? If so, why aren't more people doing this? Point 2 is the easier one -- you can research, create, and distribute patented algorithms for free. It is just in using or selling them that you need to get a license from the patent holder (directly or indirectly). Point 1 is a bit muddier, but the new EAR (which replace the ITAR) actually defines what you need to do to freely distribute cryptographic software in North America, essentially describing something like MIT's PGP distribution system and my system at http://www.sni.net/~mpj/usa/warning.htm (at least as far as is practical): ____ (ii) The export of encryption source code and object code software controlled for EI reasons under ECCN 5D002 on the Commerce Control List (see Supplement No. 1 to part 774 of the EAR) includes downloading, or causing the downloading of, such software to locations (including electronic bulletin boards, Internet file transfer protocol, and World Wide Web sites) outside the U.S., or making such software available for transfer outside the United States, over wire, cable, radio, electromagnetic, photooptical, photoelectric or other comparable communications facilities accessible to persons outside the United States, including transfers from electronic bulletin boards, Internet file transfer protocol and World Wide Web sites, unless the person making the software available takes precautions adequate to prevent unauthorized transfer of such code outside the United States. Such precautions shall include: (A) Ensuring that the facility from which the software is available controls the access to and transfers of such software through such measures as: (1) The access control system, either through automated means or human intervention, checks the address of every system requesting or receiving a transfer and verifies that such systems are located within the United States; (2) The access control system, provides every requesting or receiving party with notice that the transfer includes or would include cryptographic software subject to export controls under the Export Administration Act, and that anyone receiving such a transfer cannot export the software without a license; and (3) Every party requesting or receiving a transfer of such software must acknowledge affirmatively that he or she understands that the cryptographic software is subject to export controls under the Export Administration Act and that anyone receiving the transfer cannot export the software without a license; or (B) Taking other precautions, approved in writing by the Bureau of Export Administration, to prevent transfer of such software outside the U.S. without a license. ____ Point (1) above is done at my site, to something of an approximation, by using a .htaccess file. I'm working on improving this, some, due to some server problems, but I think that it is close enough to meet the "such measures as" criteria, especially since (2) and (3) are met pretty literally by the mechanism that routinely breaks links that attempt to bypass the warning page. Of course, this isn't perfect, and no coderpunk worth his salt would have difficulty bypassing the system if he or she were inclined to break the law, but it does allow me to post strong cryptographic software without worrying about breaking the law. Why don't more people do this? Probably because the law has usually been even more muddy than the above, and at least as irrational, and because it is more of a pain than just posting the stuff, which few people want to flaunt their disregard for the law so publicly. There is another, better way, to comply with the above using CGI scripting, but my ISP is reluctant to let me do so, so far. By the way, there is no automated way to add files to my crypto site, but if you are interested in posting quality crypto software, libraries, and documentation (like maybe some DES challenge code or RC5 cracker code), please email me at mpj(a)csn.net. Michael Paul Johnson Opinions herein are not necessarily Exabyte's. Work: mpj(a)exabyte.com http://www.exabyte.com Personal: mpj(a)csn.net http://www.csn.net/~mpj BBS 303-772-1062

1 0

Re: Dr. Vulis' social engineering "experiment"
by Toto 17 Dec '03

17 Dec '03

Bill Campbell wrote: > While many of you think that the ability of a list to withstand > constant spamming is an important issue; the government is busily > working to outlaw encryption and privacy, and I fear that much > is lost by the side issue of the "how easily can I kill a list". The "About Cypherpunks" intro to the list states, "Cypherpunks know how to attack a system and how to defend it." "Cypherpunks love to practice." If I choose to join the "Venemous Snakes" list, I'm not going to complain about getting bit every now and again. > I feel we at a *critical* crossroads in this debate, and one of the > more important voices has *very* effectively been silenced. Dr. Vulis? There was an 'attempt' to silence him, but it hasn't worked, to date. > I cannot understand why you think that > the attempt to disrupt and destroy this list a necessary step > in the task of resisting this governmental effort. I haven't seen any evidence of an attempt to destroy this list. I've seen many attempts to manipulate the list's direction, but that is another matter. > Again, I can't understand why "killing the messenger" is advancing > the issues of privacy and crypto issues. There was a crypto-messenger named DataETRetch that 'advanced' their version of crypto on this list, and they left their heads on the chopping block on their way out. If your team can't even make it through the scrimmages, then they don't belong in the game. And if you find yourself suggesting, "Why don't we just play 'touch', instead of 'tackle'.", then you're probably getting too old and tired to play in the major leagues. > How does the posting of numerous crude anti-Tim May messages promote > personal privacy? It doesn't. 'Stopping' the annoyance of these messages promotes personal privacy. > > > "In peacetime, a warlike man sets upon himself." -- Nietzsche > > "In times of war, a peacelike man sets upon others." > > Bubba Rom Dos > > This seems horribly to describe the current situation. No shit, Sherlock. Toto

1 0