-----BEGIN PGP SIGNED MESSAGE----- Cypherpunks, I have turned my old account (elee9sf@menudo.uh.edu) into a cypherpunks remailer that supports BOTH pgp and ripem. In addition to the pgp pasting token :: Encrypted: PGP there is also a ripem pasting token :: Encrypted: RIPEM I've just tested the remailer with pgp, ripem, pgp nested inside ripem, and ripem nested inside pgp, and all the messages have come back successfully. The installation went fairly quickly with Sameer's scripts; I essentially added the necessary lines to the maildelivery file, copied the pgpmail.pl file to ripemmail.pl (that's what I indicated in the maildelivery file), altered ripemmail.pl to recognize RIPEM message delimiters, and changed around the string that is built with the $system call. I apologize to those who have asked for a RIPEM remailer for taking so long; I was bogged down trying to get RIPEM compiled on rosebud, an HP/UX (cc, c89, -Aa flags: nothing worked; no gcc or disk space to install gcc, unproto didn't help - I now think the compiler is way broken). The only drawback is that account is due to expire sometime. Plus, if many people decide to support ripem in addition to pgp the scripts are going to need some reworking :-) In order to update the dos batch files I'll need an MSDOS ripem executable - has anyone seen any? (Apparently I don't have a command line compiler to build it myself; I have Turbo C++ for Windows) Here are the public keys: For the pgp half - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.3a mQCNAiyIBzwAAAEEALgRUlovklKVnasbE6qyNB82RL8emHh6+BwRwt49Yqt/YJaP Yl7V6k83/pnTE4w73S6rcWBo9jrSH1u1/Fcz7uUbRmGhteuMBEnB64wPqbxKEIrt vKJAx4xuNkTPGeNBCGOq5RtiEHbEt99hKF2H6lk9iLb8UwQCnV45xNlD3J7pAAUT tCByZW1haWxlciA8ZWxlZTlzZkBtZW51ZG8udWguZWR1PokAlQIFECyICuyDgOzq S1rWMwEBE44D/3Wwl0SLFvcN6BHe3BJhh6m1KBs3pRXsy2SBGN/y3+/NVRHbYhgy Q0MLEAPJ0PZnsJjH1pIyEDnoybcIvFyd5B3e9txawQJvaq238dyuzj5nzaTxe43H KUlh52fJzLCvXNa035p5ApvkaD1PpdAo6Vk3BGuYGOtEtGQLzLFntaqv =kIeo - -----END PGP PUBLIC KEY BLOCK----- and for the ripem half - -----BEGIN PUBLIC KEY----- User: elee9sf@menudo.uh.edu PublicKeyInfo: MFowCgYEVQgBAQICAgkDTAAwSQJCAXLNDW+7UU+XsgEfhDVdhgH0gq68Ss056URr 3VDg7lSUu61anW2wABEeVEzCgQwYR4/hYdV3rojbADx9UOAp+cOzAgMBAAE= MD5OfPublicKey: B6DB0C696304C9092F8A4493326461D3 - -----END PUBLIC KEY----- -----BEGIN PGP SIGNATURE----- Version: 2.3a iQCVAgUBLIlj+YOA7OpLWtYzAQEx8gP/YejO5r9+dCAQa2jdypuQTQmZOeLvXZLu UKK9sfn6Q2HJu0cp+ll0JVKh4qujLCmCFgFAeXwMbdBibJLByIowKzul6W0dNUEq haLRnhrI/iGiDO9VgD8463TpA7BHxM13t7iJp5TaaYI3KfwIxj7J6H43bjr9Ea6u aniKxu5WrDI= =imPY -----END PGP SIGNATURE----- Karl L. Barrus: klbarrus@owlnet.rice.edu keyID: 5AD633 hash: D1 59 9D 48 72 E9 19 D5 3D F3 93 7E 81 B5 CC 32 "One man's mnemonic is another man's cryptography" - my compilers prof discussing file naming in public directories