December 2003 - cypherpunks-legacy

Mail to News gateways
by don＠cs.byu.edu 17 Dec '03

17 Dec '03

I am compiling a quick list (for my own use, mostly) of mail 2 news gateways to link to from my homepage. (As opposed to, for example, posting it to Usenet or something) A while back there was Yet-Another-Rehash[tm] of this theme and I saved the messages: Homer's lightlink.com and Alex de Joode's mail2news(a)utopia.hacktic.nl. mail2news(a)c2.org used to be alive, but either wasn't getting the groups I was posting to or it was shut down. (Sameer: email me please about this) Anyway, if anyone knows of anything else please tell me. Oh, and the URL is http://students.cs.byu.edu/~don/mail2news.html Thanks. Don Oh, by the way, anyone have any cool PGP/crypto icons to Inline into my web page? <g>

2 1

Need Mail-to-News gates
by bluebird＠alpha.c2.org 17 Dec '03

17 Dec '03

Could someone PLEASE netmail me some _known reliable_ gates that use the straight netmail address format (alt.whatnot(a)bosco.kollege.edu)? All of the old reliables are shut down and none of the ones listed in the last remailer helpfile I got work either: group.name(a)news.demon.co.uk group.name(a)dispatch.demon.co.uk group.name(a)bull.com group.name(a)cass.ma02.bull.com group.name(a)paris.ics.uci.edu group.name(a)crs4gw.crs4.it group.name(a)berlioz.crs4.it group.name.usenet(a)canaima.Berkeley.EDU NONE of these work, or were nonfunctional when I tested them, anyway. I use the other gates like mail2news(a)utopia.hacktic.nl with the Newsgroups: field format, but the straight address format is useful for some other purposes. Thanks.

3 3

ANNOUNCEMENT: sepp-talk mailing list
by Erik Bataller 17 Dec '03

17 Dec '03

The sepp-talk mailing list is a forum for comments and discussion regarding the Secure Electronic Payment Protocol (SEPP), proposed by MasterCard to support credit card payments over the Internet. The SEPP specification is available for review from the MasterCard home page: http://www.mastercard.com The CommerceNet consortium operates this mailing list as a service to the Internet community. To subscribe to the sepp-talk mailing list, send email to: majordomo(a)commerce.net ...with a message body of: subscribe sepp-talk <your full name> You should receive a confirmation message which includes instructions for unsubscribing from the list. Shortly, CommerceNet will provide a WWW archive of this list on it's server. A notice will be sent to the mailing list.

1 0

Re: Mark Twain Bank's DigiCash offer
by Andrew Loewenstern 17 Dec '03

17 Dec '03

Hal writes: > As far as I can tell there is no charge for moving funds between > your ecash wallet and the "mint" at the bank. The charges are for > moving between the "mint" and the world access account. If you > had a shop which was able to pay much of its expenditures in ecash > it sounds like there would be no percentage fee to the bank. The gotcha being that as long as your money is in the "mint" it is not under FDIC protection... Just how safe your cash is when it is in the mint is entirely related to the security of Mark Twain's systems, which are high-profile machines that will surely be subjected to many cracking attempts. Some may prefer to keep complete control over their cash and store all of it themselves. Unlike physical cash, this stuff can be split up, encrypted, and stored in multiple places, possibly offering more security than the Mark Twain "mint." andrew

2 1

FBI/CIA/NSA, let's merge them all into one. [???!!!]
by Brad Dolan 17 Dec '03

17 Dec '03

AP on 10/25/95: FBI Gets CIA Help On Olympics The FBI and CIA are working together to deal with "substantial" threats to security at next summer's Atlanta Olympics, top administration officials told senators Wednesday. [...] Sen. Bob Kerrey of Nebraska ... chided the FBI for seeking to build a $37 million code encryption center that he said would duplicate facilities operated by the National Security Agency.

1 0

MD4-derived hash functions
by JMKELSEY＠delphi.com 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- >Date: Tue, 24 Oct 1995 13:14:41 -0400 >From: hallam(a)w3.org >Subject: Re: MD5 weakness >Ron has not mentioned such an event to me and if that were the case I would >seriously doubt that he would not have been told about it. The only comment he >generally makes is that he wrote MD5 because "MD4 was making me nervous". In the MD5 RFC, I seem to recall the statement that MD4 was trading off too much strength for additional speed. However, sometime around that time, it came out that there were attacks on two-round variants of MD4, which is the stated reason for the development of RIPE-MD. Does anyone know whether Rivest was motivated to design MD5 by the partial attacks on MD4, or whether those came later? (This is totally idle curiousity.) >NIST and the NSA trusted MD4 sufficiently to base SHA upon it. SHA is preferable >in many ways to MD5, it has a different approach to extending the scheduling and >resist differential cryptanalysis. There is a problem with the compressor >function of MD5 which I dislike. All of the well-known software hash functions seem to be based on MD4 these days, but that doesn't mean much about the security of MD4--3DES with three independent keys looks pretty strong, as does 3DES with two independent keys, but that doesn't mean that single DES is a strong enough cipher for modern applications. One issue that exists with MD5, but not with SHA or the longer hash versions of Haval, is that MD5 has only a 128 bit hash function output, which corresponds loosely to having a 64-bit key. This implies that a wealthy enough opponent could determine a pair of MD5 inputs that collide, and conceivably use this in an attack. I think we should stick to 160 bit or longer hashes for future designs. (See P. van Oorschot and M. Weiner, "Parallel Collision Search with Application to Hash Functions and Discrete Logarithms," in the proceedings of the 1994 Fairfax Conference, for example). As an aside, what hash functions are there out there that look reasonably strong, have hash outputs of at least 160 bits, and aren't based on MD4? Some of the Snefru variants with many passes (eight?) come to mind, and the GOST hash function fits all the criteria, except I have a hard time convincing myself it's as strong as it claims to be. Is there a generic construction for arbitrary-length hash functions from good block or stream ciphers? > Phill --John Kelsey, jmkelsey(a)delphi.com PGP 2.6 fingerprint = 4FE2 F421 100F BB0A 03D1 FE06 A435 7E36 -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMI+Mc0Hx57Ag8goBAQFJ9gP/VMvNefSm77prSY/NMbJfGO1EVmQrUAHn kEQEse+cXiaoJTe7njxUqycuDX0PN09C4XhNVOQJ6IBpCPZOKQMiXsI9FwAfjGWb mibwSfzyiXwxny1kYgfDCffS8KwdlWiVjxj1+MhvqhGQnxPsVA6UVrSCyAyHPZVJ UTXUWBJlJho= =2Pti -----END PGP SIGNATURE-----

7 6

Re: Let's Not Merge Mailing Lists, OK?
by rah＠shipwright.com 17 Dec '03

17 Dec '03

I'm cc:-ing this to both lists just this once, because this message is more or less administrative. I'm not trying to merge www-buyinfo with cypherpunks. tcmay(a)got.net (Timothy C. May) said: >There is great danger in constantly "casting the net wider," in trying to >reach more and more people. I understand the temptation for some on both >lists to cross-post some messages. I urge that they do this, as Bob H. has >done on occasion, by personally forwarding the message, with only _one_ of >the lists getting it. (This because the real danger is as above, where >multiple lists are in the recipient or cc: fields, and followups semi-spam >multiple lists.) I agree with Tim. I've been doing one-way forwards from cypherpunks to www-buyinfo for most of a year now. Most of the people on www-buyinfo are business people who understand that digital commerce *is* financial cryptography, but they don't have time to read all of cypherpunks to find the e$ juicy-bits. When I do this, I put a "(cpx)" in the subject line so that the sizable community of cypherpunks on www-buyinfo can filter them out and won't have to see double. I've gotten a lot of fan-mail for this, even though it's not really in keeping with the original charter for www-buyinfo, which seems to have been subsumed by other groups, like the e-payments list and others. Recently Dave Kristol has said that he's going to retool www-buyinfo, and when he does, I'm hoping to have set up my own structure of 3 hypermail archived e$ lists (a netwide e$ digest, a discussion list, and a newsletter). I'm talking to about 3 or 4 different people about it, and I should have the details worked out within a few days, with an announcement next week, if I'm lucky. Anyway, I've sent a few messages in the opposite direction on occasion (from www-buy to c'punx), but I do try to hold it down, mostly because whatever the topic is, we've usually talked about it on cypherpunks before. I should note, however, that there's a good-sized discussion, for www-buy, anyway, going on over on over there about anonymity, which has heated up over the past few days. I forwarded a message here from Nick Szabo as an example of it yesterday. The cross-posting Tim's talking about is a result of that discussion. There's a whole lot of "what do we need anonymity for, anyway?" opinion in the business community, and it should be addressed with as much reason as possible, and not by shouting them down with moral arguments to the contrary, no matter how right those moral arguments are. Fortunately, I believe there's a great business case for anonymity, and frankly, there had better be, because, in a cryptoanarchic geodesic economy like the one we're fixing to have, nothing is going to survive without a market. Anyway, like I said, I agree with Tim. If you want to post to cypherpunks, you should subscribe to cypherpunks, and suffer the firehose like the rest of us have to do. However, those of us who are on both lists, especially those of us longer-term cypherpunks like Hal, and Nick, and Adam Shostack, should be the ones to forward messages, if any, to cypherpunks, because they are the ones who know whether cypherpunks has seen this before. For instance, the posting of Nick Szabo's that I sent to cypherpunks was more of a rah-rah exercise (no pun intended) than anything else. It was so well thought out that I thought it bore passing around a bit. However, as an actual contribution to the information content on cypherpunks, what Nick said has been said on cypherpunks before, if not typically with such eloquence. Cheers, Bob Hettinga ----------------- Robert Hettinga (rah(a)shipwright.com) Shipwright Development Corporation, 44 Farquhar Street, Boston, MA 02131 USA (617) 323-7923 "Reality is not optional." --Thomas Sowell >>>>Phree Phil: Email: zldf(a)clark.net http://www.netresponse.com/zldf <<<<<

1 0

New release of CFS Unix encrypting file system available
by Matt Blaze 17 Dec '03

17 Dec '03

Source code for the latest version (release 1.3.1) of CFS, the Cryptographic File System, is now available upon request for research and experimental use in the US and Canada. CFS pushes encryption services into the Unix(tm) file system. It supports secure storage at the system level through a standard Unix file system interface to encrypted files. Users associate a cryptographic key with the directories they wish to protect. Files in these directories (as well as their pathname components) are transparently encrypted and decrypted with the specified key without further user intervention; cleartext is never stored on a disk or sent to a remote file server. CFS employs a novel combination of DES stream and codebook cipher modes to provide high security with good performance on a modern workstation. CFS can use any available file system for its underlying storage without modification, including remote file servers such as NFS. System management functions, such as file backup, work in a normal manner and without knowledge of the key. CFS runs under SunOS and several other BSD-derived systems with NFS. It is implemented entirely at user level, as a local NFS server running on the client machine's "loopback" interface. It consists of about 5000 lines of code and supporting documentation. You must have "root" access to install CFS. CFS was first mentioned at the work-in-progress session at the Winter '93 USENIX Conference and was more fully detailed in: Matt Blaze. "A Cryptographic File System for Unix", Proc. 1st ACM Conference on Computer and Communications Security, Fairfax, VA, November 1993. (PostScript available by anonymous ftp from research.att.com in the file dist/mab/cfs.ps.) and in Matt Blaze. "Key Management in an Encrypting File System", Proc. Summer '94 USENIX Tech. Conference, Boston, MA, June 1994. (PostScript available by anonymous ftp from research.att.com in the file dist/mab/cfskey.ps.) Version 1.3 of CFS also includes ESM, the Encrypting Session Manager. ESM provides shell-to-shell encrypted sessions across insecure links and requires no OS or network support. It is useful for typing cfs passphrases when logged in over the network. ESM needs RSAREF 2.0 to compile and is tested only on SunOS and BSDI. ESM is the first released part of a suite of session encryption tools that are described in Matt Blaze and Steve Bellovin. "Session-layer Encryption." Proc. 1995 USENIX Security Workshop, Salt Lake City, June 1995. (PostScript is available from ftp://research.att.com/dist/mab/sesscrypt.ps) The new version of CFS differs from the version described in the papers in a few ways: * The DES-based encryption scheme has been strengthened, and now provides greater security but with the online latency of only single-DES. * Support for the smartcard-based key management system is not included and a few of the tools are not included. * An impoved key management scheme now allows chaning the passphrase associated with a directory. * The performance has been improved. * The security of the system against certain non-cryptanalytic attacks has been improved somewhat. * User-contributed ports to a number of additional platforms. * Hooks for adding new ciphers. * 3-DES, MacGuffin, and SAFER-SK128 encryption options. * Timeout options allow automatic detach of encrypted directories after a set time or period of inactivity. CFS is distributed as a research prototype; it is COMPLETELY UNSUPPORTED software. No warranty of any kind is provided. We will not be responsible if the system deletes all your files and emails the cleartext directly to the NSA or your mother. Also, we do not have the resources to port the software to other platforms, although you are welcome to do this yourself. The software was developed under SunOS and BSDI, and there are also unsupported user-contributed ports available for AIX, HP/UX, Irix, Linux, Solaris and Ultrix. We really can't promise to provide any technical support at all, beyond the source code itself. We also maintain a mailing list for CFS users and developers; subscription information is included with the source code. Because of export restrictions on cryptographic software, we are only able to make the software available within the US and Canada to US and Canadian citizens and permanent residents. Unfortunately, we cannot make it available for general anonymous ftp or other uncontrolled access, nor can we allow others to do so. Sorry. Legal stuff from the README file: * Copyright (c) 1992, 1993, 1994, 1995 by AT&T. * Permission to use, copy, and modify this software without fee * is hereby granted, provided that this entire notice is included in * all copies of any software which is or includes a copy or * modification of this software and in all copies of the supporting * documentation for such software. * * This software is subject to United States export controls. You may * not export it, in whole or in part, or cause or allow such export, * through act or omission, without prior authorization from the United * States government and written permission from AT&T. In particular, * you may not make any part of this software available for general or * unrestricted distribution to others, nor may you disclose this software * to persons other than citizens and permanent residents of the United * States and Canada. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED * WARRANTY. IN PARTICULAR, NEITHER THE AUTHORS NOR AT&T MAKE ANY * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. If you would like a copy of the CFS source code, please read to the end of this message and then send email to: cfs(a)research.att.com DO NOT REPLY DIRECTLY TO THIS MESSAGE. You must include a statement that you are in the US or Canada, are a citizen or legal permanent resident of the US or Canada, and have read and understand the license conditions stated above. Be sure to include an email address in a US- or Canada-registered domain. The code will be sent to you via email in a "shar" shell archive (a little over 300K bytes long).

6 5

Re: Anonymity: A Modest Proposal
by loki＠obscura.com 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- At 3:35 PM 10/23/95, Futplex wrote: >Lance Cottrell writes: >> I think one solution to this problem is to encourage (require) the use of >> pseudonym servers. Having a server like alpha as the entity on the from >> line has several advantages. >> >> 1) Less Spam since it takes some effort to set up the nym and it will be >> taken away as soon as the spam starts. > >I fear this will be a short-lived gain. User-friendly scripts for >establishing pseudonymous accounts are pretty easy to write. They may be >beyond the average Fast Money Maker, but I expect myself and others will be >putting them out on the Net for general consumption. One need not automate the process of setting up anonymous accounts. One might also require some sort of exchange before activating the nym to verify that the return address is working. <SNIP> >Semi-permanent account status confers privileges to the user, IMHO. I >believe a pseudonymous account ideally should be treated the same as a >regular account on an ISP. For example, an admin will not unilaterally close >an account upon receiving a single complaint about the account user. >Certainly I don't know of an ISP that routinely blocks its users' accounts >from sending mail to selected other accounts. Lest I seem too presumptuous, >let me say that I realize all immediately foreseeable pseudonymizers are >free services. Clearly these service providers can set whatever policies they >wish, and are not directly competing with the fee-charging ISPs. Perhaps >future fee-charging pseudonymizers will consider these criteria in offering >enhanced services. > >-Futplex <futplex(a)pseudonym.com> I agree. With both free and for-fee nym servers must clearly spell out what actions will result in the termination of the nym. Perhaps 1 spam, 1 systematic harassment, or more than 5 serious complaints per month. Obvious this would need to be tuned to preserve free speech while allowing abusers to be quickly squelched. I would imagine an ecology of these servers would develop with some short lived permissive servers mixed with long lived more restrictive ones. -Lance -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQEVAwUBMI8kEfPzr81BVjMVAQF3QAgAh+Q03VU3b69uQqylri/S2EJvfS5MqQ4V JRTZRu8ZQTjb7Ic6KowQXogXG0yAv/GUa6jEWup+fO1omR2t/s7AtXjcFC6du1hh iwSeRw1QVtyspDu6FHAJNL98uG3b0taSHJxfAueA4CA8lZm00vP1exM1A0ndPjXN 6/oM/O5xdUET2tanlpcW2WDdVOZDDGQGvMORlrG8WmJKWebmcg9GnrE5gyZLs3Wr ijze7CccyPLnET4dZiry9Qd/NRx2hgdfkDopTNiTbvmGCXulzqBpqSZ689KDITAK MNgSagZKgOsy7pRGCFSK9EPljZ2IwPtCrE/s9YX0kkJtDhq84SU3EQ== =UBy5 -----END PGP SIGNATURE----- ---------------------------------------------------------- Lance Cottrell loki(a)obscura.com PGP 2.6 key available by finger or server. Mixmaster, the next generation remailer, is now available! http://obscura.com/~loki/Welcome.html or FTP to obscura.com "Love is a snowmobile racing across the tundra. Suddenly it flips over, pinning you underneath. At night the ice weasels come." --Nietzsche ----------------------------------------------------------

1 0

Re: [Noise] Paranoia in the Comics
by Duncan Frissell 17 Dec '03

17 Dec '03

At 11:27 PM 10/25/95 -0700, you wrote: >This has no real crypto relevance, but some anarchistic relevance. > >Sometimes you find anti-government paranoia in the strangest of places... >In the Ziggy strip for 10/25/95, Ziggy is in a Psychiatrist's office. The >shrink is stating "You're afraid of the government, are you? I'm required >to report that sort of thing you know." Ziggy has long been a libertarian/right winger. Note a Sunday strip of a few years ago. Ziggy bends over and looks closely at some red ants who are carrying picket signs reading "Down with Communism", "Freedom Now", etc. Ziggy observes "It had to happen sometime." Since we are being semi-irrelevant here, yesterday's Broom Hilda strip was good for the net "Universal Access" wars. Broom Hilda sits down at a computer to take a ride on the Information Superhighway. The computer says "Sorry, the information superhighway is a toll road." "What's the toll"? "Brains." So Broom Hilda gives up and sets off on a tour of the back roads of America. Note the proof that competition provides better service than government-monopoly Universal Service. After years of being one of the few Local Telcos that charged residential customers metered rates for local calls, NYNEX (New York Telephone) has announced some flat rate pricing plans. Nothing like a little local loop competition. DCF "School Bus Safety - Are your children safe? - Story at 11:00" -- They're safer on the bus than they are when they arrive at their local institution for the mentally/morally defective.

1 0