[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: forging headers (with more header information)
My apologies. I followed Tim's advice and turned on verbose headers, and
this is what I got.
Return-Path: [email protected]
Received: from nimitz.MIT.EDU (NIMITZ.MIT.EDU [184.108.40.206]) by well.com
(8.6.12/8.6.12) with SMTP id NAA20123 for <[email protected]>; Tue, 24 Oct
1995 13:06:23 -0700
From: [email protected]
Message-Id: <[email protected]>
Received: from sgigate.SGI.COM by nimitz.MIT.EDU with SMTP
(220.127.116.11/16.2) id AA00301; Tue, 24 Oct 95 16:07:08 -0400
Date: Tue, 24 Oct 95 16:07:08 -0400
Apparently-To: [email protected]
> 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.