December 2003 - cypherpunks-legacy

No Subject
by Anonymous 17 Dec '03

17 Dec '03

> From owner-cypherpunks(a)toad.com Tue May 31 09:34:37 1994 > Date: Tue, 31 May 1994 09:31:57 -0400 > From: Nikolaos Daniel Willmore <ndw1(a)columbia.edu> > To: cypherpunks(a)toad.com > Subject: Re: New MacPGP2.3a has arrived. > Sender: owner-cypherpunks(a)toad.com > > :: > Request-Remailing-To: cypherpunks(a)toad.com > > Nice four posts of noise toady PM. Drop everthing? How 'bout stick it > on your ftp site and shut up about it? Dork. > Heh heh. Suggestion: Read the "How To" document for the remailers before trying something like this next time, Nikolaos Daniel Willmore.

1 0

Re: New MacPGP2.3a has arrived.
by snyderra＠dunx1.ocs.drexel.edu 17 Dec '03

17 Dec '03

At 7:55 AM 5/31/94 -0400, Perry E. Metzger wrote: Is my lack of action on this topic going to be of real impact to me? >Will I be thrown in jail for not knowing what AE is, or why MacPGP >might want to be aware of it? Will my inactivity result in the deaths >of millions of sea otters? AE means Apple Event. If the new MacPGP supports Apple Events, that makes it scriptable, which is a wonderful thing. It means that I can (as I can do with RIPEM Mac today) pull down a menu in my mail reader, Eudora, and have a message encrypted or signed automatically. However, it appears to still be the infringing 2.3 code, which I won't run, given that I do live in the US. Let me know when a Mac version of 2.5/2.6 is out. Bob -- Bob Snyder N2KGO MIME, RIPEM mail accepted snyderra(a)dunx1.ocs.drexel.edu finger for RIPEM public key When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl.

1 0

Re: <no subject>
by gtoal＠an-teallach.com 17 Dec '03

17 Dec '03

: From: Anonymous <remailer-admin(a)chaos.bsu.edu> : > Nice four posts of noise toady PM. Drop everthing? How 'bout stick it : > on your ftp site and shut up about it? Dork. : > : Heh heh. : Suggestion: Read the "How To" document for the remailers before : trying something like this next time, Nikolaos Daniel Willmore. Xenon always was careless about that sort of stuff :-) I dunno why he bothers with anonymous remailers though, all those rants recently about people sitting on the source of MacPGP were *obviously* from Xenon - he doesn't even attempt to disguise his writing style... G PS I suggested it half in fun a couple of weeks back, but I'm now nearly certain that uni == tmp ... I'm also starting to suffer this really weird paranoid delusion that uni and tmp are both t.c.may - it would explain why tc never has time to post much, he's too busy being detweiler ;-) PPS While in paranoid mode, I thought I'd mention that I've noticed some of Detweiler's mannerisms emanating from email in New Delhi of all places. Weird. I think I must be cracking up.

1 0

Re: New MacPGP2.3a has arrived.
by Nikolaos Daniel Willmore 17 Dec '03

17 Dec '03

I wrote, >:: >Request-Remailing-To: cypherpunks(a)toad.com All right, we're both dorks. I'll ask politely. Will you please put the new MacPGP onto the Cypherpunks ftp site? It's on ftp.netcom.com in /pub/mpj/... only so far. I was contacted by whoever is releasing this thing about his/her woes in getting it out there. But as I have a new ITAR-clean ftp site/project, I'd like to not carry crypto code there. I've attracted a bunch of programmers with promises of a worry-free environment, and was trying to keep some distance from this thing. I gotta get back off this list, as all I'm seeing is the same old cynicism, inaction, and endless threads about money. That said, BTW, we're interested in what utilities and features you all would like to see from a large userbase of PGP users. - Nik

2 1

thanks
by David C. Taylor 17 Dec '03

17 Dec '03

Thanks for all the replies on Dispersed DES - a bit wiser now, I have decided to junk that version of the idea (seeing as CBC probably provides a great deal more protection with seemingly much lower security cost). David C. Taylor

1 0

Re: procmail
by Martin Janzen 17 Dec '03

17 Dec '03

tim werner <werner(a)mc.ab.com> writes: >> With procmail, you can associate arbitrary actions with a match, so no >> it would not have to be silent. > >Will anyone who has procmail working please send me an example of how you >use it? I am totally confused. OK. First -- just checking -- I assume you're running some version of UNIX. I'm using HP-UX 9.03 on an HP 9000 workstation, but everything should work pretty much the same on other systems. First, you have to tell the mail system that you want your mail to be filtered through the procmail program. You do this by creating a one-line file called ".forward" in your home directory: "| IFS=' '; /usr/local/bin/procmail -p" The quotes are necessary. Replace /usr/local/bin with the name of the directory in which you've installed the procmail program. Do a "chmod 644 .forward" to make sure that your mail software can read this file. Now you can create a ".procmailrc" file in your which tells procmail how to filter your mail. Here are some excerpts from mine: ------------------------------------------------------------------------------- # ~/.procmailrc # # Configuration file for procmail mail processing software # # General environment variables (You may not need all of these; see the # procmail(1) man page to find out what each one means. Of course, the # HOME variable should be set to your own home directory.) # HOME= /Home/janzen PATH=/usr/local/bin:/usr/ucb:/bin:/usr/bin:$HOME/bin MAILDIR = $HOME/Mail LOGFILE = $HOME/.procmaillog LOCKFILE = $HOME/Mail/procmail TMP= $HOME/tmp SENDMAIL= /usr/lib/sendmail TMPFILE= $TMP/procmail.$$ LOCKFILE= $HOME/Mail/.procmail # # First, toss out junk mail # :2H ^From:.*root@idacom.hp.com ^Subject:.*cron /dev/null # The ":" introduces a new "recipe". The "2" means that two expressions # follow. The "H" indicates that procmail should search the header only, # ignoring case. (The man page lists all kinds of other flags.) # # The first regular expression (regexp) matches a line containing "From:" # at the start of the line ("^"), then any arbitrary characters (".*"), # then "root(a)idacom.hp.com". # # Similarly, the second regexp matches a header line beginning with # "Subject:" and containing the word "cron" anywhere in the subject. # # The line following the last expression tells procmail where to save # the message. In this case, I save it to /dev/null, throwing it away. # (When you're first setting up procmail, I suggest saving unwanted # messages to ~/junk or something, until you're satisfied that your # recipes work as expected!) # # You can also forward matched messages to another user (eg. !joeuser@host) # or pipe them to a UNIX command (eg. |$HOME/bin/my_fancy_mail_processor). :2H ^From:.*cypherpunks detweiler /dev/null :2H ^From:.*cypherpunks subscribe /dev/null # # Now, sort mail from mailing lists into the proper folders # :1H ^From:.+cypherpunks Cypherpunks # Put all mail with a "From:" line containing the word "cypherpunks" into # the file $HOME/Mail/Cypherpunks. :1H ^TOcypherpunks Cypherpunks # "^TO" is shorthand for "^(To|Cc|Apparently-To):.*". This is supposed to # catch all destination addresses. :1H ^Return-Path:.+cypherpunks Cypherpunks :1H ^From:.*pgpmip PGPMIP :1H ^From:.*wnet.edex.edu.au PGPMIP :1H ^From:.*Extropians Extropians :1H ^TOExtropians Extropians ------------------------------------------------------------------------------- One other thing: I like to get a summary each day, showing me what procmail has done. I do this by creating a script called procmailsummary.sh: ------------------------------------------------------------------------------- #!/bin/sh # # Summarize the ~/.procmaillog file # # Use the LOGFILE variable if it's set; otherwise, use a default LOGFILE=${LOGFILE:=$HOME/.procmaillog} # Add a header to the message # (This also avoids sending a message with a null body, which confuses Elm!) echo "Subject: Procmail Summary" echo " " sort ${LOGFILE} | awk ' /^ Folder:/ { folder = $2; nbytes = $3; msgcount[folder] += 1; totalbytes[folder] += nbytes; } END { for (folder in msgcount) printf "Folder %s:\tsaved %d messages (%d bytes)\n", \ folder, msgcount[folder], totalbytes[folder]; } ' if [ "$1" = "-clear" ]; then rm -f $LOGFILE; fi ------------------------------------------------------------------------------- I then use crontab to schedule this script so that it's executed at 7AM every morning, and mails me the result. When I come in, I can see at a glance which mailing lists have new messages. (WARNING: If you're not running HP-UX, the crontab(1) command may not exist on your system, or may work somewhat differently. Also, on some systems you must be root to use cron. If you have problems, try "man cron" or ask your sysadmin to give you a hand.) echo '0 7 * * * /usr/local/bin/procmailsummary.sh -clear | elm -s "Procmail Summary" janzen' | crontab This should all be on one line. Replace /usr/local/bin with the name of the directory in which you've put the script. Make sure to do a "chmod +x procmailsummary.sh", to make the script executable. Finally, if you are using a mailer other than elm, replace the "elm ... janzen" command with something appropriate (eg. "mail janzen"). Now verify that the crontab command worked: crontab -l Hope that helps... -- Martin Janzen janzen(a)idacom.hp.com Pegasus Systems Group c/o Hewlett-Packard, IDACOM Telecom Operation

1 0

Re: Hiding conventionally encrypted messages in PGP messages to someelse.
by Paul Franklin 17 Dec '03

17 Dec '03

In article <199409030238.AA18130@xtropia> you wrote: > -----BEGIN PGP SIGNED MESSAGE----- > I have been thinking about steganography lately. Correct me if I am > wrong, but it seems to me that if one wants to hide encrypted data, then > all this public key encryption stuff becomes irrelevant. It seems that > the sender and the recipient must agree on a way to hide the data. The > time of this agreement is a perfect time to exchange conventional > key(s). > Speaking of conventional encryption, PGP uses conventional > encryption (IDEA). So if we wish to hide conventionally encrypted > data, why not use the purloined letter method, and hide it as the > conventionally encrypted data in a PGP encrypted file? > To create such a file, we would simply create as PGP usually does, > except that we specify or record the conventional IDEA key used. Then to > decrypt the file, we simply ignore the RSA headers and use the specified > or recorded conventional IDEA key. We could even insure that the IDEA > key in the RSA encrypted headers is wrong. So, obiwan can not reveal > the data even if Darth can seize him. > I have created a hack to PGP ui to do all of the above! Isn't this what pgp -c does?

2 1

Is DES exportability context-dependent?
by m5＠vail.tivoli.com 17 Dec '03

17 Dec '03

I don't have my "Applied Cryptography" handy, but this keyboard's here in front of me always ready :-) Lets say I rigged up a "signature" system that cranked the message through a DES or 3DES engine in CBC mode, and used the last value as the signature (or something like that; whatever makes the most sense). In that context---as a signature algorithm---would DES be exportable? It's been demonstrated that something developed as a signature algorithm but later adapted to encryption purposes remains exportable, right? What about going the other direction? -- | GOOD TIME FOR MOVIE - GOING ||| Mike McNally <m5(a)tivoli.com> | | TAKE TWA TO CAIRO. ||| Tivoli Systems, Austin, TX: | | (actual fortune cookie) ||| "Like A Little Bit of Semi-Heaven" |

2 1

Re: http://digicash.support.nl = NULL
by sidney＠apple.com 17 Dec '03

17 Dec '03

[Harry Bartholomew wrote about problems accessing digicash web page via lynx.] It looks to me like the web page requires Mosaic forms support. I could see a little bit more than you did using MacMosaic, which shows the pictures but doesn't support forms. It was a bit confusing, since I could see a number of entries for things with prices next to them, such as $5 for the e-cash software and $0.25 for "information". I couldn't tell how you are supposed to get either of those without either the software or at least the information. Maybe someone who has X or Windows Mosaic can tell us more about what's there. I sent e-mail to the info e-mail address that the page mentioned and got back the following. (I sent just the word "info" in the subject and body of the message.) What I find strange about it is that it looks like an automated reply, but it is asking me to reply as if the mail will be read by a human. Another interesting thing about it is that Chaum does not include consumers in his list, just people who are interested in selling products or clearing money. After reading all of the copies of the digicash press announcement that were sent to this list, I'm a bit hesitant to post this, but what the heck. Following is the reply I got back from info(a)digicash.nl: [begin quote] Date: Tue, 31 May 1994 14:51:25 CET From: "DigiCash Information" <info(a)DigiCash.nl> To: sidney(a)apple.com Subject: ecash-info Thank you for your interest in our electronic money technology. Because of all the reactions we have received, we have made available some background information on our Web server http://digicash.support.nl If you prefer, we would of course be pleased to provide similar information by electronic or paper mail. In any case, we plan to be keeping you informed of developments by email. It would be helpful for this purpose, if you could let us know more about the nature of your interest, and at least which of the following categories fits best: (a) potential acceptor of electronic cash for services offered over the network, (b) potentail provider of electronic cash service itself to other network service providers, (c) member of the press, or (d) interested in the technology for other purposes. We are looking forward to finding a way that we can work together. Very kind regards, David Chaum Managing Director [end quote]

1 0

Re: procmail
by tim werner 17 Dec '03

17 Dec '03

>Date: Tue, 31 May 1994 11:22:17 -0600 >From: Martin Janzen <janzen(a)idacom.hp.com> > >tim werner <werner(a)mc.ab.com> writes: >>> With procmail, you can associate arbitrary actions with a match, so no >>> it would not have to be silent. >> >>Will anyone who has procmail working please send me an example of how you >>use it? I am totally confused. > >First, you have to tell the mail system that you want your mail to be >filtered through the procmail program. You do this by creating a >one-line file called ".forward" in your home directory: > >"| IFS=' '; /usr/local/bin/procmail -p" Sorry to bother the list with this thread, but I need just one more question answered, and I don't know where else to ask. I work on a heterogeneous system. My personal workstation is a decstation, running Ultrix-4.3, but I'm pretty sure that email enters our local domain via a sparcstation running SunOS-4.1.3. My email ends up in /var/spool/mail/werner, which is one of the sparcstation disk partitions. If I use the above-mentioned .forward magic to start procmail, does it execute on my local decstation, or on the sparcstation. In other words, do I build a decstation or sparcstation executable? Is there some way I can test this without the mail daemon getting into some kind of infernal .forward loop if there is an error? thanks a lot, tw

4 3