[43053] in Cypherpunks
Re: forging headers (with more header information)
daemon@ATHENA.MIT.EDU (Lee Tien)
Tue Nov 7 12:18:40 1995
Date: Tue, 7 Nov 1995 09:08:39 -0800
From: Lee Tien <tien@well.com>
To: cypherpunks@toad.com
My apologies. I followed Tim's advice and turned on verbose headers, and
this is what I got.
Lee
Return-Path: freeh@fbi.gov
Received: from nimitz.MIT.EDU (NIMITZ.MIT.EDU [18.80.0.161]) by well.com
(8.6.12/8.6.12) with SMTP id NAA20123 for <tien@well.sf.ca.us>; Tue, 24 Oct
1995 13:06:23 -0700
From: freeh@fbi.gov
Message-Id: <199510242006.NAA20123@well.com>
Received: from sgigate.SGI.COM by nimitz.MIT.EDU with SMTP
(1.37.109.4/16.2) id AA00301; Tue, 24 Oct 95 16:07:08 -0400
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
