1993-01-02 - Re: A solution remailer signature suppression

Header Data

From: edgar@spectrx.Saigon.COM (Edgar W. Swank)
To: Cypherpunks <cypherpunks@toad.com>
Message Hash: 59a711902be31004ea9dd8dbb1d1453e9645f2a856802b007b69b1a38ff099f2
Message ID: <1k4PwB7w165w@spectrx.saigon.com>
Reply To: N/A
UTC Datetime: 1993-01-02 01:10:34 UTC
Raw Date: Fri, 1 Jan 93 17:10:34 PST

Raw message

From: edgar@spectrx.Saigon.COM (Edgar W. Swank)
Date: Fri, 1 Jan 93 17:10:34 PST
To: Cypherpunks          <cypherpunks@toad.com>
Subject: Re: A solution remailer signature suppression
Message-ID: <1k4PwB7w165w@spectrx.saigon.com>
MIME-Version: 1.0
Content-Type: text/plain


Hugh Daniels said here on Dec 28:
 
    There are very good reasons to build remailers (and all mail
    tools) to pass on all the bytes they can, trailing spaces and
    .sigs included.
 
Hugh doesn't say what these reasons are.  They are not obvious to me,
so I must disagree. I've already stated what I think are good reasons
at least for remailers whose purpose is anonymity to remove automatic
sigs which are likley to destroy anonymity.
 
I've said I would accept either a less ambiguous sig delimiter than
"--" or a remailer option to remove the sig (default) or leave it in.
 
    Might I sugjest that we set up the remailers with a feature where
    it tests mail sent from its owner to make sure there is no
    "compromising" content and that the outer shell verifies
    correctly, if it fails either of these tests it is dumped in a
    file and a note returned to you saying someings not right.
 
Hugh doesn't say what criteria we are to use to detect "compromising"
content (short of genuine AI) or what the outer shell is supposed to
verify to.  Why limit this test to the remailers "owner"?
 
This system I use doesn't allow me to run my own software, so I
think this idea wouldn't work for me, in any case.

--
edgar@spectrx.saigon.com (Edgar W. Swank)
SPECTROX SYSTEMS +1.408.252.1005  Silicon Valley, Ca






Thread