- cypherpunks-legacy - lists.cpunks.org

Re: True democracy the electronic way
by tcmay＠got.net 17 Dec '03

17 Dec '03

At 3:03 AM 2/15/96, Vladimir Z. Nuri wrote: >1. this is an extremely interesting problem in my opinion. the ideal >form of government has not been achieved in many millenia. could it >be solved given the full power of the information age, i.e. ... >if anyone knows of >a mailing list to discuss this concept of trying to apply technology >to government, I would be most interested. the closest I can see You might try the "Cypherwonks" mailing list that L. Detweiler set up a couple of years ago to explore the very ideas you are supporting here. You might find you have a lot in common with him. --Klaus!, a tentacle Boycott espionage-enabled software! We got computers, we're tapping phone lines, we know that that ain't allowed. ---------:---------:---------:---------:---------:---------:---------:---- Timothy C. May | Crypto Anarchy: encryption, digital money, tcmay(a)got.net 408-728-0152 | anonymous networks, digital pseudonyms, zero W.A.S.T.E.: Corralitos, CA | knowledge, reputations, information markets, Higher Power: 2^756839 - 1 | black markets, collapse of governments. "National borders aren't even speed bumps on the information superhighway."

4 4

Need ride from SF to CP meeting
by mbriceno＠netcom.com 17 Dec '03

17 Dec '03

I need a ride from SF to Saturday's meeting. If you are going there and would like to split the cost for gas, email me with your phone number or leave a message on my voice mail at (415) 435-7939. Please respond before 11 a.m. TIA, -- Marc Briceno <mbriceno(a)netcom.com> PGP public key by finger Big Brother Chips? The Clinton Administration has decided to foster use of "Clipper Chips" in government communications equipment, thus allowing the FBI et al. to eavesdrop on computerized messages. The FBI reportedly is also investigating increased use of "sniffer" programs, which steal passowrds and access to private data on the Internet. Time Magazine, February 14, 1994, page 18

1 0

No Subject
by owner-cypherpunks＠toad.com 17 Dec '03

17 Dec '03

>When asked, he also indicated that the PGP 3.0 message formats would be >embedded into the API in such a way that it would not be possible to use >the library to generate or process stealth. Mmmmm.... It seems that there a market demand for a stealth-capable product. Many peoples here seems to discuss it. And for the time being, AFAIK, this type of products are used by a specific class of peoples, most of which knows what 'stealth' means. So why is it that they design a program that would not permit the use of a feature considered desirable by it's customer base? Regards to most CypherPunk. JFA **** NEW PGP 2.6.2 KEY ********* 2048 bits Key ID:24201BA1 1996/02/13 Jean-Francois Avon <jf_avon(a)citenet.net> Key fingerprint = 23 B6 24 31 86 67 FB 35 C7 A7 AF 12 A1 61 E9 3D **** OLD KEY: DO NOT USE ANYMORE UNLESS FOR VERIFYING SIGNATURES **** 1024 bits Key ID:57214AED 1995/10/04 Jean-Francois Avon <jf_avon(a)citenet.net> Key fingerprint = 84 96 76 AE EB 7C AB 15 88 47 87 B0 18 31 74 9F

1 0

No Subject
by owner-cypherpunks＠toad.com 17 Dec '03

17 Dec '03

John Gilmore <gnu(a)toad.com> reported: >My favorite was his summary report on the OECD meeting in December, >~steptoe/286908.htm, at which the US tried to parade some of the >fruits of its behind-the-scenes efforts to convince other governments >to become as authoritarian as the US government on crypto policy. Why help "potential enemies"? Why a govt risks it's cherished 'national security'? >If the US government can quietly convince other countries to support >Clipper-like systems (including "mandatory key escrow" and "trusted It probably means that they already cracked the code... :) Definitely, they are insane beyond the safety level... JFA **** NEW PGP 2.6.2 KEY ********* 2048 bits Key ID:24201BA1 1996/02/13 Jean-Francois Avon <jf_avon(a)citenet.net> Key fingerprint = 23 B6 24 31 86 67 FB 35 C7 A7 AF 12 A1 61 E9 3D **** OLD KEY: DO NOT USE ANYMORE UNLESS FOR VERIFYING SIGNATURES **** 1024 bits Key ID:57214AED 1995/10/04 Jean-Francois Avon <jf_avon(a)citenet.net> Key fingerprint = 84 96 76 AE EB 7C AB 15 88 47 87 B0 18 31 74 9F

1 0

Top 10 anagrams - "Communications Decency Act"
by Rishab Aiyer Ghosh 17 Dec '03

17 Dec '03

Terribly sorry, I've a mail backlog a mile long, haven't seen this yet, etc etc. Besides, it's so short, and so brilliant, that it deserves being posted more than once. -Rishab ---begin forwarded text--- From: Mike Morton <mike(a)morton.com> Date: Sun, 11 Feb 96 20:25:35 -1000 Subject: Top Ten Anagrams -- 'Communications Decency Act' Copyright (c) 1996 by the author, Mike Morton <mike(a)morton.com>. All rights reserved. You may reproduce this, in whole or in part, in any form provided you retain this paragraph unchanged. Top Ten Anagrams for "Communications Decency Act" 10. Caution cynic: Scan modem, etc. 9. Communist, candy, cocaine, etc. 8. Academic custom: Cynic on 'Net 7. Connect CIA, communist decay 6. I disconnect my Acme account 5. [This anagram too offensive to post] 4. Condoms, etc., can cue intimacy 3. Decency? Commit a sin, account! 2. Cut my academic connections And the number one anagram for "Communications Decency Act": 1. Comic scene: Nudity act on Mac Runners-up: A succinct edict: man, economy CIA? Disconnect me, my account? Connect Mosaic; induce my act Cute, cosmetic cynic: Madonna I accuse; condemn my tactic, no? I accused: Connect into my Mac I can't commend saucy conceit Media custom: Connect a cynic Mice may disconnect account Scan me: CIA concocted mutiny ---end forwarded text--- ---------------------------------------------------------------------- The Indian Techonomist - newsletter on India's information industry http://dxm.org/techonomist/ rishab(a)dxm.org Editor and publisher: Rishab Aiyer Ghosh rishab(a)arbornet.org Vox +91 11 6853410; 3760335; H 34 C Saket, New Delhi 110017, INDIA

1 0

Re: CyberAngels
by E. ALLEN SMITH 17 Dec '03

17 Dec '03

From: IN%"joseph(a)genome.wi.mit.edu" 13-FEB-1996 02:57:56.92 >I agree with allen, about the issues of 'nym. But looking at other aspects >of these cyberangels I'm unsure how to feel. On one hand they seem resonable, >protecting only the children. "Acts bewteen consenting adults are okay" say >they. But the protect the children was what the CDA hid under. The 'CyberAngels' are rather like the CDA in that they keep using child pornography as a red herring to avoid talking about everything else they want to do. I will not be surprised if they wind up being informants for the CDA. The following CuDigest issues may shed some light on the issue. Both I and tallpaul have done some responding to them, incidentally. (In all of these, http://www.soci.niu.edu/~cudigest/ should be put in front of the web addresses.): Vol 7, Issue 86: CUDS7/cud786 Vol 7, Issue 87: CUDS7/cud787 Vol 7, Issue 91: CUDS7/cud791 Vol 7, Issue 93: CUDS7/cud793 (I will note that the relevant article contains an inaccuracy on bestiality, claiming that it is illegal in all states. This is not the case, as some later CuDigests explain.) Vol 7, Issue 94: CUDS7/cud794 Vol 8, Issue 4: CUDS7/cud804 Vol 8, Issue 6: CUDS8/cud806 (I would appreciate some responses explaining the difference between an anonymous remailer and methods for mailbombing using forgeries - "Gabriel" does not seem to understand this. Vol 8, Issue 13: CUDS8/cud813 -Allen

1 0

Setting up a Magic Money server
by anonymous＠extropia.wimsey.com 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- Magic Money seems to have reached a usable state. (Open mouth, insert foot, bite down firmly :-) ) Someone needs to set up the first server. Here's how: You can set up a Magic Money server on any machine with a net connection. You need to be able to run a program when mail comes in. You do not need root access. Running a Magic Money server is no harder than running a cypherpunks remailer. Unlike a remailer, there is no possibility of your server being used to harass or mailbomb anyone. Get Magic Money and PGP Tools (needed to compile it) from csn.org. Get pgptl10c.zip and mgmny10e.zip. If mgmny10e.zip isn't up yet, get mgmny10d.zip and fix the bug in mms_mint() by moving the free(fp); to the end of the function. This is the only change in version e. This version has been reported to work on both big and little endian machines. If your machine has assembly-language speedups, get them from the pgp23a source code. Use the same defines PGP uses to compile on your machine, and take out the NO_ASM define in my makefile. This will speed up your server quite a bit. Compile the client and the server. Define UPTON or one of the other modmult functions, because I have had problems with Smith's modmult. The hash file is currently set to about half a meg. It grows if it fills up. If you need to use less disk space, change the settings in mm.h. Put the server program "s" in one directory, and the client program "c" in another. Put something random (i.e. unknowable to an attacker) in a file called rand.dat in each directory. The programs won't work without this. The directories should be otherwise empty. Go to the server directory and run "s i" to initialize the server. It will ask you for the name of your server, size of your key, name of your coins, and denominations to use. Powers of 2 make good denominations. For example, you might use 1,2,4,8... up to 32768. With these 16 coin values, you can transfer any sum up to 65535 with 16 or fewer coins. After you have entered all the information, the server generates a PGP key pair, and an e/d list pair. Your server's ascii-armored public key is saved to bank.asc. You will need to distribute this key to everyone who wants to use your server. Copy bank.asc into the directory with the client. In that directory, run "c -i" to setup the client. The client generates a key, then creates a message "output.asc" which should be sent to the server. For example, if "client" and "server" were subdirectories in a common directory, you could run "s < ../client/output.asc > ../client/reply.asc" from the server's directory. Now go back to the client directory and run "c reply.asc" to finish setting up your client. You will be running this sequence a lot if you play with the system, so write a script. Your client now knows the name of your coins, and has the elist. This information is updated automatically when the server discovers the client's copy is out of date. Go back to the server directory and run "s m <x>" where x is one of your higher-value coins. You will have problems if you are using version d and did not fix the bug as described above. This mints a coin and writes it out to coins.dat. Go back to the client directory and run "c ../server/coins.dat". The client reads the coin, checks it, and asks you for values of new coins to create. Create several smaller coins. The client keeps prompting you until you have created coins with a value equalling that of the old coin. The client creates another "output.asc". Run your script to pass it through the server, and run "c reply.asc" to process the results. The client now takes the signed coins from the server and the blinding factors from proto.dat, and unblinds the coins. The result is written to allcoins.dat. Now run "c -p" to withdraw coins from allcoins.dat. Enter the denominations to withdraw, and 0 to end. Now you have a coins.dat in the client's directory, so run "c coins.dat" to process it. It will count up the coins you withdrew, and prompt you for new coin values again, then produce another output.asc for the server. You can create a second client in another directory, and pass coins from one to the other. Try creating a "msg.txt" file in the server's directory. The client will then display the contents of the message whenever it processes a reply from the server. The client waits for a keypress after the message. Now that you know the server works, set it up so that incoming mail to your account is passed to the server, and the output from the server is sent back to the person who sent the mail. If you want to use the same account for the server and regular mail, have users put a specific word in the subject line of messages to the server. Announce your server, including its public key from bank.asc. You might want to provide binaries of the client for DOS, either by ftp or by automatic mail. You might also want to write a better makefile for the Unix version. Now you need to mint and distribute some, but not too much, money for people to play with. Give a few coins to the first x people who send a message to your system. Later you can have lotteries, post puzzles and simple ciphers for people to break, etc. to put more money into circulation. But keep your money scarce. People should be able to get a few coins to play with, but they should always want more than they have. Good luck! Pr0duct Cypher -----BEGIN PGP SIGNATURE----- Version: 2.3a iQCVAgUBLVyldMGoFIWXVYodAQGo4AP/SQz82XRtWC1W/qjGQWouVDn/82TBBGne ktNIfmPE92lPpH0V3f7EizBs466AEXTwaxq5qVpj4Fx6low1ceiaKBQxhNosB8Wa BydiS2E2iC6kQ1RPj5jb6UOdLTQzl2MM7UrI8J3KpxszQWjhbgM/5ddHoDXgqs/J VjjeM/iqNF8= =2ggl -----END PGP SIGNATURE-----

1 0

Setting up a Magic Money server
by anonymous＠extropia.wimsey.com 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- Magic Money seems to have reached a usable state. (Open mouth, insert foot, bite down firmly :-) ) Someone needs to set up the first server. Here's how: You can set up a Magic Money server on any machine with a net connection. You need to be able to run a program when mail comes in. You do not need root access. Running a Magic Money server is no harder than running a cypherpunks remailer. Unlike a remailer, there is no possibility of your server being used to harass or mailbomb anyone. Get Magic Money and PGP Tools (needed to compile it) from csn.org. Get pgptl10c.zip and mgmny10e.zip. If mgmny10e.zip isn't up yet, get mgmny10d.zip and fix the bug in mms_mint() by moving the free(fp); to the end of the function. This is the only change in version e. This version has been reported to work on both big and little endian machines. If your machine has assembly-language speedups, get them from the pgp23a source code. Use the same defines PGP uses to compile on your machine, and take out the NO_ASM define in my makefile. This will speed up your server quite a bit. Compile the client and the server. Define UPTON or one of the other modmult functions, because I have had problems with Smith's modmult. The hash file is currently set to about half a meg. It grows if it fills up. If you need to use less disk space, change the settings in mm.h. Put the server program "s" in one directory, and the client program "c" in another. Put something random (i.e. unknowable to an attacker) in a file called rand.dat in each directory. The programs won't work without this. The directories should be otherwise empty. Go to the server directory and run "s i" to initialize the server. It will ask you for the name of your server, size of your key, name of your coins, and denominations to use. Powers of 2 make good denominations. For example, you might use 1,2,4,8... up to 32768. With these 16 coin values, you can transfer any sum up to 65535 with 16 or fewer coins. After you have entered all the information, the server generates a PGP key pair, and an e/d list pair. Your server's ascii-armored public key is saved to bank.asc. You will need to distribute this key to everyone who wants to use your server. Copy bank.asc into the directory with the client. In that directory, run "c -i" to setup the client. The client generates a key, then creates a message "output.asc" which should be sent to the server. For example, if "client" and "server" were subdirectories in a common directory, you could run "s < ../client/output.asc > ../client/reply.asc" from the server's directory. Now go back to the client directory and run "c reply.asc" to finish setting up your client. You will be running this sequence a lot if you play with the system, so write a script. Your client now knows the name of your coins, and has the elist. This information is updated automatically when the server discovers the client's copy is out of date. Go back to the server directory and run "s m <x>" where x is one of your higher-value coins. You will have problems if you are using version d and did not fix the bug as described above. This mints a coin and writes it out to coins.dat. Go back to the client directory and run "c ../server/coins.dat". The client reads the coin, checks it, and asks you for values of new coins to create. Create several smaller coins. The client keeps prompting you until you have created coins with a value equalling that of the old coin. The client creates another "output.asc". Run your script to pass it through the server, and run "c reply.asc" to process the results. The client now takes the signed coins from the server and the blinding factors from proto.dat, and unblinds the coins. The result is written to allcoins.dat. Now run "c -p" to withdraw coins from allcoins.dat. Enter the denominations to withdraw, and 0 to end. Now you have a coins.dat in the client's directory, so run "c coins.dat" to process it. It will count up the coins you withdrew, and prompt you for new coin values again, then produce another output.asc for the server. You can create a second client in another directory, and pass coins from one to the other. Try creating a "msg.txt" file in the server's directory. The client will then display the contents of the message whenever it processes a reply from the server. The client waits for a keypress after the message. Now that you know the server works, set it up so that incoming mail to your account is passed to the server, and the output from the server is sent back to the person who sent the mail. If you want to use the same account for the server and regular mail, have users put a specific word in the subject line of messages to the server. Announce your server, including its public key from bank.asc. You might want to provide binaries of the client for DOS, either by ftp or by automatic mail. You might also want to write a better makefile for the Unix version. Now you need to mint and distribute some, but not too much, money for people to play with. Give a few coins to the first x people who send a message to your system. Later you can have lotteries, post puzzles and simple ciphers for people to break, etc. to put more money into circulation. But keep your money scarce. People should be able to get a few coins to play with, but they should always want more than they have. Good luck! Pr0duct Cypher -----BEGIN PGP SIGNATURE----- Version: 2.3a iQCVAgUBLVyldMGoFIWXVYodAQGo4AP/SQz82XRtWC1W/qjGQWouVDn/82TBBGne ktNIfmPE92lPpH0V3f7EizBs466AEXTwaxq5qVpj4Fx6low1ceiaKBQxhNosB8Wa BydiS2E2iC6kQ1RPj5jb6UOdLTQzl2MM7UrI8J3KpxszQWjhbgM/5ddHoDXgqs/J VjjeM/iqNF8= =2ggl -----END PGP SIGNATURE-----

1 0

Re: I've just unsubscribed from cypherpunks
by cmca＠alpha.c2.org 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- [To: willer(a)carolian.com (Steve Willer), Rich Salz <rsalz(a)osf.org>] [Subject: Re: I've just unsubscribed from cypherpunks] [Cc: cypherpunks(a)toad.com] willer(a)carolian.com (Steve Willer) wrote: >I don't understand what the issue is. I understand perfectly what the issue is. Rich wrote an important informational message about "MS CAPI export issue" - which raises questions about how exactly MicroSloth got away with exporting CAPI. I for one dearly want to hear the answer. Instead he gets a JimBell rant about conspiracies or something (I didn't read it to the end). He CAN'T just killfile the subject. It's HIS subject, and he wants to read the answer. The thread is relevent. When the noise level exceeds the threshold, even in threads which you want to read or indeed initiated, something is fundamentally wrong. I'd unsubscribe myself, except I can't. ObCrypto: I think the govmint goofed, letting this out. Perhaps someone should (anonymousely) alert the DoJ to start a grand jury to indict Bill Gates. Someone overseas should ASAP interface PGP to it and publish it. Chris McAuliffe <cmca(a)alpha.c2.org> (No, not that one.) -----BEGIN PGP SIGNATURE----- Version: 2.6 iQCUAwUBMSJqPoHskC9sh/+lAQFsuQP2JWma2HNFXSLg5h0pEUn3J/BlEmOu2kBa avtfvbvLL+25JkTR2Fn3K+zw1b7OyREX1fSj7lKdfRf6WukUJ55snPrqJmaRYeWS 0b7XVAP4bxYNBVV+IjhU+IaZSOE9YY1zuAQ07lSLTmprNiCCQm37loxfyBRiJsrU VfGxKUXyqA== =RiJ/ -----END PGP SIGNATURE-----

1 0

Re: FCPUNX:Beta Testers Wanted
by Ken D Hayes 17 Dec '03

17 Dec '03

At 12:28 AM 2/12/96 -0500, you wrote: > > >> Please let me beta test the new puffer! I just started using it. Its great! >> I know next to nothing about crypto and am using Windows 3.1, but puffer >> provides me with easy access to file security. >> >> Ken Hayes >> >> KDHayes(a)earthnet.net >> > >> > >> >> > >> > >> Ken Hayes (KDHayes(a)Earthlink.net) Veiws expressed represent only my own. >> >> > >========================================================================== > + ^ + | Ray Arachelian |Emptiness is loneliness, and loneliness| _ |> > \|/ |sunder(a)dorsai.org|is cleanliness and cleanliness is god-| \ | ><--+-->| |liness and god is empty, just like me,| \| > /|\ | Just Say |intoxicated with the maddness, I'm in| <|\ > + v + | "No" to the NSA!|love with my sadness. (Pumpkins/Zero)| <| n >===================http://www.dorsai.org/~sunder/========================= > > >[This Bible excerpt awaiting review under the Communications Decency Act] >And then Lot said, "I have some mighty fine young virgin daughters. Why >don't you boys just come on in and do em right here in my house - I'll just >watch!"....Later, up in the mountains, the younger daughter said. "Dad's >getting old. I say we should do him." So the two daughters got him drunk and >did him all that night. Sure enough, Dad got em pregnant....Onan really >hated the idea of doing his brother's wife and getting her pregnant while >his brother got all the credit, so he whacked off first....Remember, it's >not a good idea to have sex with your sister, your brother, your parents, >your pet dog, or the farm animals. [excerpts from the Old Testament, Modern >Vernacular Translation, TCM, 1996] > > > > Ken Hayes (KDHayes(a)Earthlink.net) Veiws expressed represent only my own.

1 0