All of lore.kernel.org
 help / color / mirror / Atom feed
From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Everything gone!
Date: 19 Mar 2003 16:18:59 -0500	[thread overview]
Message-ID: <m3vfyfdph8.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0303191059140.31680@chaos>

>>>>> "Richard" == Richard B Johnson <root@chaos.analogic.com> writes:

Richard> How did [they] do this?

If you look at the Received headers in the faked message, it actually
came to kernel.org from alog0102.analogic.com, from Analogic's
208.224.220.0/22 netblock, not from quark.analogic.com (in Analogic's
204.178.40.0/21 block) as it claimed:

Received: from alog0102.analogic.com ([208.224.220.117]:12804 "EHLO
	quark.analogic.com") by vger.kernel.org with ESMTP
	id <S263082AbTCSPfa>; Wed, 19 Mar 2003 10:35:30 -0500

If an analogic box was cracked, look at 208.224.220.117, not at quark.

The routing suggests they would not have been able to spoof the IP,
unless they did so over eg an 802.11 link at whatever site
208.224.220.0/22 is used.  

-JimC


  parent reply	other threads:[~2003-03-19 21:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 15:46 Everything gone! Richard B. Johnson
2003-03-19 16:02 ` Richard B. Johnson
2003-03-19 17:33   ` John Jasen
2003-03-19 17:50     ` Richard B. Johnson
2003-03-19 17:55     ` Jesse Pollard
2003-03-19 18:12       ` Richard B. Johnson
2003-03-20  2:04         ` Joshua Kwan
2003-03-19 21:18   ` James H. Cloos Jr. [this message]
2003-03-19 16:04 ` Matthias Schniedermeyer
2003-03-19 16:21   ` Richard B. Johnson
2003-03-19 16:37   ` Xavier Bestel
2003-03-19 16:51     ` Eli Carter
2003-03-19 17:12       ` Xavier Bestel
2003-03-19 17:01     ` Richard B. Johnson
2003-03-19 18:23       ` Eric Weigle
2003-03-19 18:32         ` Matthias Schniedermeyer
2003-03-20  8:57       ` Sean Neakums

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3vfyfdph8.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.