NODE 10bbc196testing remailers, the keys for my remailers
sameer@netcom.com (Sameer Parekh)Mon, 13 Sep 93 20:49:47 PDT
Has anyone written or is someone writing a script which will
take a list of remailers, and ping each of them to see if they are
working, both encrypted and unencrypted? If no one has taken on that
task, I'd be willing to do it.. I'll list here the remailers for whom
I have the keys for... if another remailer exists which I don't know
about please send me the key.
(Also-- here's the keys for my remailers...)
Type bits/keyID Date User ID
pub 1024/69464F 1993/09/11 Sameer's Remailer <sameer@soda.berkeley.edu>
pub 1024/9E3311 1993/09/02 Sameer's Remailer <sameer@netcom.com>
pub 1024/567449 1993/09/01 Sameer's Remailer <cs60a-qu@cory.EECS.Berkeley.EDU>
pub 512/64E8A7 1993/03/05 Remailing Service <remailer@dis.org>
Anonymous Remailer <remailer@utter.dis.org>
pub 1024/02C389 1993/06/07 Anonymous <remail@tamsun.tamu.edu>
Anonymous <remail@tamaix.tamu.edu>
pub 1024/DB04AB 1993/05/05 Mr. Remailer <elee6ue@rosebud.ee.uh.edu>
pub 1024/BA80A9 1992/11/26 Remailer (remailer@rebma.mn.org)
pub 1024/7B47C3 1993/01/20 Anonymous Remailer <phantom@mead.u.washington.edu>
pub 1024/EBCC89 1993/04/27 Cypherpunk Remailer at <remailer@entropy.linet.org>
pub 1024/B5A32F 1992/12/13 Remailer <remail@extropia.wimsey.com>
pub 510/0BB437 1992/11/12 Remailing Service <hal@alumni.caltech.edu>
pub 510/5620D5 1992/11/15 Remailing Service <hfinney@shell.portal.com>
pub 512/7D154B 1993/04/04 jarthur remailer c/o <ebrandt@jarthur.claremont.edu>
13 key(s) examined.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.3a
mQCNAiyRU70AAAEEALsLEv31NHZrNBsOYqsr064hT/SUtztIfGEkNxMS9KXo9Sil
3y8hY3r+mkeVPyvinmdjOPBIzHQmzezs9o9Tu/RAYQy8IdrWv/8KjIcZ0K3B+SVp
5d+fW14pOBm6MbcNpjK9RXVBpwAxjcYF2PXor8kT56J+2I9T4W08cWvcaUZPAAUR
sAEAtCxTYW1lZXIncyBSZW1haWxlciA8c2FtZWVyQHNvZGEuYmVya2VsZXkuZWR1
PrABAIkAlQIFECyVO8EL8mtIoS4LrQEBDywD/0P2Zx2xWOxv076XsyDSYBYMh3jb
iHbFisoaNwwJTcV8p6WwwBZNCsgGs3fEMuhrT2XHCN7f8CGkLvUivt6HvMgTl1EK
lD1gaV6b4ZAZzo6PoFB6/8Bxa1K2aMnp0nNXuvRoIHs/jzFVF5YcM1nucUG85pL4
BgK2hOsAPkTK2Ru3sAEAmQCNAiyGXXoAAAEEAMDtjyzGpLKugc49+Na4GZcUZ1Q1
jyZYeofTdNwlTIbs4bGYOaeFCXaQluD4ANsLn9muMVae+q+3gZsIq14klQLO6Xe5
5pZ0Efx5shfFU24S9+xARUrDfMMqD5TtaoBXH9aQBV9mVo0h5Pxu6ng9B0A+GPJg
/ygdVqW95EIJnjMRAAUTsAEAtCVTYW1lZXIncyBSZW1haWxlciA8c2FtZWVyQG5l
dGNvbS5jb20+sAEAiQCVAgUQLJU79gvya0ihLgutAQGZBQQAgoctBIYxoaL3wIm7
7cKiZFOpXvkgD6ihV1c8La/udKw6MsVCts2ry2Dc8gm3mfEHEWTtZ8h3Wj9yPCma
9C39FiyikxK/JVMm2mOtPxhokY6YBOZSSMlCBdvm7Gtox9Cy65AOLCo0YZh+X9GV
CPgyA5S3QyxPGRVSmxil7VHAHFKwAQCZAI0CLIToKAAAAQQAuoNVv3/OeG+gbSMy
AW/V7MlY0rILldtec7oO9u5we+oWwsdJi5C3G2spWy6TbIa26sxVYUCacfzEKal/
TBRYhXPJ01BuDggHr8XMn9l3Bdaa+9QmLZHogokHQ8YOGJalHB8esu2Fy7NfDErR
u5YZboEAUBwtXSKkTCGeeFJWdEkABRGwAQC0M1NhbWVlcidzIFJlbWFpbGVyIDxj
czYwYS1xdUBjb3J5LkVFQ1MuQmVya2VsZXkuRURVPrABAIkAlQIFECyVPBcL8mtI
oS4LrQEBKbgEAMSkfgm+PDdC2J6s+aq32TrO9iKmS3nZ1Q0/+eGznGcS6INys6qX
MH7GCF3VDwhDBGf1l7/egd8dnNLn29zYSi2uX/H90YqzDlIRW3JMtq9ZIjCkSakZ
SnSbEJOgJp/G1t9kZFPP/UDv9iMtqbJXxX7IP2r8Axzv1uXAmUI/WXEksAEA
=BdhD
-----END PGP PUBLIC KEY BLOCK-----
--
Sameer
sameer@netcom.com
NODE 03de10f1Re: testing remailers, the keys for my remailers
rjc@gnu.ai.mit.edu (Ray)Mon, 13 Sep 93 21:48:49 PDT
Sameer Parekh () writes:
>
> Has anyone written or is someone writing a script which will
> take a list of remailers, and ping each of them to see if they are
> working, both encrypted and unencrypted? If no one has taken on that
> task, I'd be willing to do it.. I'll list here the remailers for whom
> I have the keys for... if another remailer exists which I don't know
> about please send me the key.
Yes, I started writing such a system about 3 weeks ago but quit when
school started. Basically, it was a mail server to be operated at gnu.
Remailer operators would "register" their remailer along with
some stats (PGP or RIPEM capability? Public Key? Private Machine? Delay time?
Mix capability? Owner? Comment field.)
The software would then "ping" each remailer every 6 hours and update
its database. If you wanted a list of current working remailers, you would
ask the mail server (I was even thinking of adding socket capability
for fast query)
I might eventually take some time to finish it (it wasn't even 50%
done) but I've got too much work to do now.
-Ray
-- Ray Cromwell | Engineering is the implementation of science; --
-- EE/Math Student | politics is the implementation of faith. --
-- rjc@gnu.ai.mit.edu | - Zetetic Commentaries --
NODE 1202224bRe: REMAIL: testing remailer & keys
Karl Lui Barrus <klbarrus@owlnet.rice.edu>Tue, 14 Sep 93 13:35:22 PDT
I think there are two more remailers:
elee7h5@rosebud.ee.uh.edu, and
catalyst@netcom.com
(keys below)
Incidentally, I see you have the Mr. Remailer key
(elee6ue@rosebud.ee.uh.edu). How did that slip out? :-)
I must have extracted it instead of elee7h5@rosebud.ee.uh.edu.
Anyway, that one should be stable - I've used it for various scripts
hacks and testing, and I restored it to plain form recently.
In fact, it may become the preferred remailer on rosebud - the account
it is in is still "valid"; it belongs to a friend of mine who is
currently working in New Hampshire (he has no telnet access). His
password is still valid, and the remailer is set up with his
permission (even blessings).
I mention this since I have been told by a lawyer that running a
remailer on an account I no longer have legitimate access to breaks
about three laws here in Texas. So I attempted to re-legitimize my
account (described below).
Once upon a time that was my account, but I'm through with that grad
area, and university, so the account is locked now... but my directory
structure is still there. So, I mailed to two people in charge on
rosebud and told them to get back to me. So far, I haven't heard
anything, so maybe they don't care! Actually, if it doesn't impose a
cpu burden (it doesn't) or take up much space (it doesn't), they might
not give a crap.
elee7h5@rosebud.ee.uh.edu:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.3a
mQCNAiscKOYAAAED/jmrZbh5t5HgEHDGE2zzFZx3sIplEjIFRFsLpCfJYBfN36Rm
uT8VGIyCcUSmCTqEOJ5HJZF58CUCOsy3B215ptOvbZdGijC3Qs7FbtGHKGA49q0v
gBgVIcjjyppRI9YjfqlI2gUKDLPceCTw20ODAA7UTKYIa3IBS32zjcrFq/uzAAUR
tCZyZW1haWxlcjAzIDxlbGVlN2g1QHJvc2VidWQuZWUudWguZWR1PokAlQIFECtk
lUeDgOzqS1rWMwEBUdAEAIosaOm/+kTsQI53GAqPXr08v5AAfwup5lDiUbCWp17C
ueYHZrP4zolAqQ7kyWrkIeHgJHkX3yB6YH/jQ0MeDZERXS69kq2SGVQSH6inGoF9
3WerfGRpdONa597JVcRpklzMUz6bmXnhsiEm/K1FP9pNOZYyS6h/3gs92ikezq3X
=tUXb
-----END PGP PUBLIC KEY BLOCK-----
catalyst@netcom.com
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.3a
mQCNAiyBTjoAAAEEAMIKpRnqXb82TOQpx/vEDwGPXndXaxtfiZeSLZqullWCEbd4
YkCHG/F1i3Wzq4Pgz6nSbb58vMS5RonY7+ZC6IHI8zBpp9oMW3u+lqbk8Z61x49d
xwAKlE7Zsk/pOeGrqbsidm83WUqlSGgyOpvq0A8LzT4+WPra8ZvHue9jwOpJAAUR
tChBbm9ueW1vdXMgUmVtYWlsZXIgPGNhdGFseXN0QG5ldGNvbS5jb20+iQCVAgUQ
LIaqhIOA7OpLWtYzAQH4sgQAsc6s3X75LwWTV65Dw76wdSRKuoI57F2ZZWjSOIQK
n1CWUn6YEYOIs3kkdHNd0uz9Mspoy+6BsnWGSW11r8k88VThEoVpJ74o91apR1ML
yCEdD7O/+nZK8N484+mN2BcKOdeze4QvgTt+qHHUd+Q5alW9VfXtbNImmSnI3FC/
8n4=
=Hh6a
-----END PGP PUBLIC KEY BLOCK-----
--
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