December 2003 - cypherpunks-legacy

finger user@wasabi.io.com
by wcs＠anchor.ho.att.com 17 Dec '03

17 Dec '03

Neat stuff! You can finger billstewart(a)wasabi.io.com, even though I don't exactly have an account there... Is the source code available for your finger daemon? It doesn't seem to have any regular-expression matching; it mostly matches exact character strings, presumably case-insensitive. I couldn't figure out how to get it to match spaces, though: requesting 'bill stewart' got all the bills and all the stewarts, rather than getting the lines with bill stewart in them. Thanks!

1 0

Re: contemplating remailer postage
by Hal 17 Dec '03

17 Dec '03

As Jim points out, Matthew's scheme for one-bit-per-stamp has the problem that it requires non-anonymous stamps. Jim suggested a variant on Chaum's digital cash where the stamp numbers would be re-blinded by the recipient so that the remailer would not recognize them (but could verify their validity). Matthew's bitmap idea could still be used, though. The incoming stamp numbers could be hashed down to, say, 24 bits. This could then be an index into a 2^24-bit file, which would take 2 MB. Set the bit when the stamp is used, and reject the mail if the bit is already set. Granted, this would create false rejections. But email is already not perfectly reliable. You could send 160,000 messages before you had as many as 1% false rejections (2^24 / 100). I think this would be better than trying to save this many digital stamps and check through the list each time for duplications. Hal

1 0

Remailer FAQ. Details.
by catalyst-remailer＠netcom.com 17 Dec '03

17 Dec '03

I hope I can get a bit more attention to this, now that it has become more sophisticated. Please code warriers, take a break and let the human race know what the existing remailers are all about. I know exactly why they don't have enough traffic; knowledge about them is still insider knowledge. A list of remailer addresses and year-old partial info from a request made my Tim May was all I could find. Specs needed. I will send this to Gary Edstrom for the PGP FAQ if I don't have to spend the rest of my life compiling it. Mail info to qwerty(a)netcom.com. I'm interested in hearing from users as well as operators. -Nik (Xenon) Xenon's Full Disclosure Remailer List. Remailer Fast? OpLog SysLog Subj Batch RD NL CPU Phys PGP BitB ?what else? --------- ------ ----- ------ ---- ----- -- -- --- ---- --- ---- ----------- bsu-cs + ? ?/? + ? ? ? ? ? 23a ? catalyst + N? SM/MQ - - ? - PA M 23a - choas + ? ?/? + ? ? ? ? ? - - cicada ++ ? ?/? - - - - ? ? - - dis.org - ? ?/? - ? ? ? ? ? 23a ? extropia ? ? ?/? + ? ? ? Pr? ? 23a ? jarthur +/-- St SM/MQ? - ? ? ? Un ? 23a - menudo -- ? ?/? - t1 ? ? ? ? - ? merde -/-- ? ?/? - ? ? ? ? ? - ? penet.fi -- St ?/? - t? 24 + Pr H - - pmantis ++ ? ?/? - ? - - ? ? - - qwerty + C SM/MQ - - - - PA M 23a + rosebud ++/- ? ?/? - - - ? ? ? 23a ? remba ? ? ?/? ? ? ? ? ? ? 23a ? shell ++/+/- St ?/? - ? ? ? ? ? 23a - soda ++/- St+? ?/? - ? ? ? ? ? - Subj: Strips Subject header? NL: Non-linear remailing? 123->231. RD: Random delay added (max, in hours)? Batch: Batched remailing? t2 means twice daily. n5 means after 5 messages. CPU: Pr = private. PA = account on public access machine. Un = university. Phys: Physical security of the CPU, especially at night. H/M/L. BitB: BitBucket feature? Fast?: ++ <5 min + 5-10 min. - ~10-30 min delay -- Pinging isn't practical due to long delays, but may be more secure. +/- Sometimes +, sometimes - Normal internet mail delays are common, and are not equivalent in the two directions between any two remailers. Mail still gets through. OpLog: F: Full copies of all mail is archived. My large volume mailing should help put a stop to this. St: Stats logs of when mail was remailed. St+: Stats logs of when and where mail was remailed. St-: Simple counter. N: Operator keeps no logs. SysLog: SM: sendmail logs of when and where mail was exchanged. Root access. MQ: mailqueue accessible by anyone on the site. Could make logs. bsu-cs nowhere(a)bsu-cs.bsu.edu catalyst catalyst(a)netcom.com chaos remailer(a)chaos.bsu.edu cicada hh(a)cicada.berkeley.edu dis.org remailer(a)dis.org extropia remail(a)extropia.wimsey.com jarthur ebrandt(a)jarthur.claremont.edu menudo nobody(a)Menudo.UH.EDU merde remailer(a)merde.dis.org penet.fi anon.penet.fi pmantis hh(a)pmantis.berkeley.edu qwerty qwerty(a)netcom.com rosebud elee7h5(a)rosebud.ee.uh.edu shell hfinney(a)shell.portal.com soda hh(a)soda.berkeley.edu Discontinued remailers still on some lists out there: phantom(a)mead.u.washington.edu remail(a)tamaix.tamu.edu sameer(a)netcom.com (spelling?) sameer(a)berkeley.edu (spelling?) cdodhner(a)indirect.com remailer(a)entropy.linet.org?? 00x(a)uclink.berkeley.edu? remail(a)tamaix.tamu.edu? remailer(a)entropy.linet.org? Background on each remailer: bsu-cs: Run by Chael Hall. Machine: ?? Problems policy: ?? Contact ?? Software: ?? Security: ?? Comments: History: ?? catalyst: Run by Scott Collins. Machine: personal dial-up account on Netcom. Problems policy: Outgoing address blocking, with proof of ID. Contact catalyst(a)netcom.com. Software: Customized Hal's ? Security: Netcom keeps sendmail logs, which root(a)netcom.com can read. Any Netcom user could also compile his own sendmail logs, by constantly logging mail as it arrives and leaves. Comments: History: ?? chaos: Run by ?? Machine: ?? Problems policy: ?? Contact ?? Software: ?? Security: Comments: Finger remailer.help(a)chaos.bsu.edu for info using any remailer. ?? gopher chaos.bsu.edu for a collection of info about Cypherpunks. Comments: History: ?? cicada: Run by Eric Hollander. Machine: ??? Problems policy: ?? Contact ?? Software: ?? Security: Tread lightly. Being "phased out". dis.org: Run by ?? Machine: ?? Problems policy: ?? Contact ?? Software: ?? Security: ?? Comments: History: ?? extropia: Run by ?? Machine: ?? Problems policy: ?? Contact ?? Software: ?? Security: ?? Comments: Only accepts PGP remailing. ::/Encrypted:PGP header is optional. Privately owned, in Canada. History: ?? jarthur: Run by Eli Brandt. Machine: Sequent Symmetry. Problems policy: Destination blocking is available w/ sufficient ID. Contact ebrandt(a)jarthur.claremont.edu. Software: the usual, tweaked for MMDF. Hal's? Security: jarthur keeps sendmail logs. Comments: History: Set up late '92. PGP added mid-'93. menudo: Run by ?? Maching: ?? Problems policy: ?? Contact ?? Software: ?? Security: Stores messages and sends them at midnight?? Comments: History: ?? merde: Run by ?? Maching: ?? Problems policy: ?? Contact ?? Software: ?? Security: ?? Comments: History: ?? penet.fi: Run by Julf (last name?) Machine: ?? Operator owned. Problems policy: Account revokation. Contact ??(a)anon.penet.fi. Software: custom. Security: Comments: By far the most popular remailer, dwarfing in a day what the entire Cypherpunk remailers combined carry in a month. Supports easy return addresses as well as non-anonymous mailing to someone's anonymous address (na1234... instead of an1234...). Your real address is kept on Julf's hard disk, but is fairly safe there, especially if you do not abuse your anonymity to harass someone. On a bad day your mail and especially Usenet posts may be delayed up to two days. Very reliable though. Sends error messages back to you for failed mail. Limited to 48K mail. History: ?? pmantis: Run by Eric Hollander. Machine: ?? Problems policy: ?? Contact ?? Software: ?? Security: Tread lightly. Being "phased out". Comments: History: ?? qwerty: Run by Xenon. Machine: dial-up account on Netcom. Problems policy: "What problems?". Contact qwerty(a)netcom.com. Software: Hal's remailer. Security: Netcom keeps sendmail logs, which root(a)netcom.com can read. Any Netcom user could also compile his own sendmail logs, by constantly logging mil as it arrives and leaves. Comments: You must use na1234(a)anon.penet.fi not an1234(a)anon.penet.fi. Finger qwerty(a)netcom.com for a blurb on the remailer and updates on its software. Request-Remailing-To: /dev/null is a bit bucket. whitehouse.gov gets blocked and fully logged. History: Up 2/94. Set up by Xenon who needed more remailers to use to send PGP info to people with, since anon.penet.fi was overloaded. rembe: Run by ? Machine: ?? Problems policy: ?? Contact ?? Software: ?? Security: ?? Comments: ?? History: ?? rosebud: Run by Karl Barrus. Machine: ?? Problems policy: ?? Contact ?? Software: ?? Security: ?? Comments: History: ?? shell: Run by Hal Finney. Machine: ?? Problems policy: ?? Contact ?? Software: Hal's Remailer. Security: ?? Comments: whitehouse.gov blocked and fully logged. hal(a)alumni.caltech.edu forwards all mail to shell. History: ?? soda: Run by Eric Hollander. Run by: ?? Machine: ?? Problems policy: ?? Blocking of addresses. Mail sent to problem causer. Contact ?? Software: custom. ?? Security: ?? Comments: History: ?? Remailer Public Keys: (I've got these...)

1 0

info on local/regional groups & sublists
by Stanton McCandlish 17 Dec '03

17 Dec '03

For my OUTPOSTS list/FAQ, if you have any (public) inforation about local cypherpunks groups and sublists, like the Austin lists, or the UK branch, please let me know via personal email. Need to put out a new version of the FAQ soon, and am missing much info. All I have so far is: Main general: hughes(a)soda.berkeley.edu Main subscribe requests: cypherpunks-request(a)toad.com Main FTP: soda.berkeley.edu, pub/cypherpunks Hardware general: jdblair(a)nextsrv.cas.muohio.edu Hardware requests: cp-hardware-request(a)nextsrv.cas.muohio.edu Wonks general: cypherwonks-owner(a)lassie.eunet.fi Wonks requests: majordomo(a)lists.eunet.fi (message body of: subscribe cypherwonks [1st & last name] [address]) Austin general: Jim McCoy <mccoy(a)bongo.cc.utexas.edu> Doug Barnes <barnes(a)io.com> Austin req. austin-cypherpunks-request(a)bongo.cc.utexas.edu austin-cypherpunks-announce-request(a)bongo.cc.utexas.edu Austin FTP: ftp.cc.utexas.edu, pub/cypherpunks Any info on other CP groups, corrections to what little I have, pointers to other CP file sites, gopher/WWW/Wais servers, etc. all appreciated. Even some BBS number, snailmail addresses for any local groups that are getting less virtually, more physically organized, etc. That, and relevant other lists (anything that might be consider "online activist" or civil libertarian in nature) and resources. Again, please send via email to mech(a)eff.org rather than on the list. Muchas gracias in advance! -- Stanton McCandlish * mech(a)eff.org * Electronic Frontier Found. OnlineActivist F O R M O R E I N F O, E - M A I L T O: I N F O @ E F F . O R G O P E N P L A T F O R M O N L I N E R I G H T S V I R T U A L C U L T U R E C R Y P T O

1 0

CONTENT AND QUALITY NET DISCUSSION.
by CCVARGA＠delphi.com 17 Dec '03

17 Dec '03

GENTLEMEN, MOST OF MEANINGFUL DISCUSSION ON THE NET HAVE BEEN BOTH WELL THOUGHT AND INTELLECTUALLY "NON'TRIVIAL". THE REMAILING OF MULTIPLE COPIES OF HIGH NOISE INFORMATION DRIBBLE WOULD CAUSE ME TO LOOK AT THE TRAFFIC ON THE NET AND AS : IS IT WORTH IT? RIGHT NOW, THE NUMBER OF UNSUBSCRIBE MESSAGES LEADS ME TO BELIEVE THAT IT IS NOT. IF THIS IS WHAT TOAD WANTS, SO BE IT. IF THERE IS AN INDIVIDUAL AMONG YOU THAT WOULD LIKE TO MAKE A CASE FOR CONTINUED SUBSCRIPTION, I WOULD REALLY APPRECIATE SERIOUS REPLY'S. CCVARGA(a)DELPHI.COM

1 0

Subscribe
by jwc00＠cas.org 17 Dec '03

17 Dec '03

Subscribe cypherpunks Jim Cooper

1 0

Re: Prodigy Hard Drive Scans
by David Michel 17 Dec '03

17 Dec '03

Prodigy durring installation sets up a temp/swap file on your hard disk. Now this part is a funtion of DOS, Delete a file and all the data is there just the FAT entry is gone. So what ever is on the disk at the location of the temp/swap file is what can be seen at the prodigy end. davidm(a)chey.com

1 0

Re: CONTENT AND QUALITY NET DISCUSSION.
by dmandl＠lehman.com 17 Dec '03

17 Dec '03

> From: CCVARGA(a)delphi.com > > GENTLEMEN, MOST OF MEANINGFUL DISCUSSION ON THE NET HAVE BEEN BOTH > WELL THOUGHT AND INTELLECTUALLY "NON'TRIVIAL". THE REMAILING OF > MULTIPLE COPIES OF HIGH NOISE INFORMATION DRIBBLE WOULD CAUSE ME TO > LOOK AT THE TRAFFIC ON THE NET AND AS : IS IT WORTH IT? > RIGHT NOW, THE NUMBER OF UNSUBSCRIBE MESSAGES LEADS ME TO BELIEVE > THAT IT IS NOT. IF THIS IS WHAT TOAD WANTS, SO BE IT. IF THERE IS > AN INDIVIDUAL AMONG YOU THAT WOULD LIKE TO MAKE A CASE FOR > CONTINUED SUBSCRIPTION, I WOULD REALLY APPRECIATE SERIOUS REPLY'S. > CCVARGA(a)DELPHI.COM So--another noisemaker complaining about noise on the list. Why don't you decide for yourself whether it's worth continuing your subscription? Would you actually base your decision on the number of people who tell you that it's worth continuing? If you're new to the list, why don't you stick around for a while and see what you think? If not, you're probably fully capable of deciding for yourself now whether this is the place for you. Related issue: The number of people unsubscribing because of excessive noise who are so rude and clueless as to post their unsubscribe requests to the entire list (thereby increasing noise) is really getting to me. Almost no tangential or "off-topic" thread pollutes this list as much as unsubscribe requests that everyone has to read. The cypherpunks welcome message clearly states that unsubscribe messages should be sent to cypherpunks-request(a)toad.com. Simple. Again, the list administrator is a human being, not a machine, so those requests may take a couple of days to process. Big deal. Losing your patience and whining to the list is as useful as pushing the elevator call button a hundred times, and has the added disadvantage of getting hundreds of people really angry. It also makes you look like a clueless newbie. I usually send these messages to individuals, not the whole list, but it seems that there's been an increase in unsubs sent to all of us. Again, folks, if you want to unsubscribe (which I'm not encouraging you to do), it's cypherpunks-request(a)toad.com --Dave.

1 0

unsubscribe
by SERPE＠morgan.com 17 Dec '03

17 Dec '03

please unsubscribe me. Thanks and good luck!!

1 0

White House crypto briefings: Clipper, FIPS, escrow agents, export
by Stanton McCandlish 17 Dec '03

17 Dec '03

Briefings on Federal Encryption Policy/Telecommunications Security Today (Feb 4), the Administration will hold 2 briefings about cryptography and the Clipper chip. The briefings will "report on a review of federal policies and procedures for encryption and telecommunications security-related products and technologies." The first briefing, at 11am EST (i.e., in less that half an hour of this posting), will update Congressional committee staff, and the second will address concerns of industry reps, public interest groups, privacy advocates and other non-government parties. EFF will attend this second meeting, at 1pm EST. EFF will share what it learns about the results of either briefing as soon as possible. An early "heads up" from the the Administration indicates that the main subjects for the briefings will be: Administration will announce Clipper/Skipjack Federal Information Processing Standard (FIPS) Justice Dept. key escrow procedures to be announced Announcement of Treasury and NIST as Escrow Agents Decisions on encrytion products that fit under current export standards announced. Other topics also likely to be addressed (unconfirmed): State Dept. will, surprisingly, streamline procedures for export of Clipper Administration not going forward with DSS licensing agreement with PKP/RSADSI. -- Stanton McCandlish * mech(a)eff.org * Electronic Frontier Found. OnlineActivist F O R M O R E I N F O, E - M A I L T O: I N F O @ E F F . O R G O P E N P L A T F O R M O N L I N E R I G H T S V I R T U A L C U L T U R E C R Y P T O

1 0