From: “Perry E. Metzger” <perry@piermont.com>
To: tien@well.sf.ca.us (Lee Tien)
Message Hash: 050554f716701aa6bb974fb7ca9914f17746746b11e1534cca0a992dd68766ce
Message ID: <199511070255.VAA14851@jekyll.piermont.com>
Reply To: <199511070249.SAA14921@well.com>
UTC Datetime: 1995-11-07 03:48:25 UTC
Raw Date: Tue, 7 Nov 1995 11:48:25 +0800
From: "Perry E. Metzger" <perry@piermont.com>
Date: Tue, 7 Nov 1995 11:48:25 +0800
To: tien@well.sf.ca.us (Lee Tien)
Subject: Re: forging headers
In-Reply-To: <199511070249.SAA14921@well.com>
Message-ID: <199511070255.VAA14851@jekyll.piermont.com>
MIME-Version: 1.0
Content-Type: text/plain
You didn't send ALL the headers, only some of them. You need to send
on the full set to make a trace possible.
Lee Tien writes:
> So I got this message. How would someone identify the sender of this
> message? I'm writing an article on anonymity, with some discussion of
> remailers, and want to argue that forging already permits people to raise
> the costs of tracing significantly, anonymous remailers or no.
>
> Lee
>
> >From: freeh@fbi.gov
> >Date: Tue, 24 Oct 95 16:07:08 -0400
> >Apparently-To: tien@well.sf.ca.us
> >X-UIDL: 814570964.056
> >
> >> How difficult is it to forge headers? How difficult is it to trace a
> >> message to the actual sender if the header is forged?
> >
> >Not very difficult at all (to forge, that is). This is a quick and dirty
> >example that should be somewhat traceable. If you want pointers on how to
> >trace it, post the whole thing, including headers, to cypherpunks.
> >
> >Louis
Return to November 1995
Return to “tien@well.sf.ca.us (Lee Tien)”