mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael H. Warfield" <mhw@wittsend.com>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: TRG vger.timpanogas.org hacked
Date: Tue, 5 Jun 2001 14:42:16 -0400	[thread overview]
Message-ID: <20010605144216.A18046@alcove.wittsend.com> (raw)
In-Reply-To: <20010604183642.A855@vger.timpanogas.org> <E157AuE-0006Wc-00@the-village.bc.nu> <20010605113051.A6209@vger.timpanogas.org>
In-Reply-To: <20010605113051.A6209@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Tue, Jun 05, 2001 at 11:30:51AM -0700

On Tue, Jun 05, 2001 at 11:30:51AM -0700, Jeff V. Merkey wrote:
> On Tue, Jun 05, 2001 at 08:05:34AM +0100, Alan Cox wrote:
> > > is curious as to how these folks did this.  They exploited BIND 8.2.3
> > > to get in and logs indicated that someone was using a "back door" in 

> > Bind runs as root.

> > > We are unable to determine just how they got in exactly, but they 
> > > kept trying and created an oops in the affected code which allowed 
> > > the attack to proceed.  

> > Are you sure they didnt in fact simply screw up live patching the kernel to
> > cover their traces

> Could have.  The kernel is unable to dismount the root volume when booted.
> I can go through the drive and remove confidential stuffd and just leave 
> the system intact and post the entire system image to my ftp server. 

	This would be a good thing for those of us involved in investigating
these sorts of things.  :-/

> I have changed all the passwords on the server, so what's there is no 
> big deal.  This server was public FTP and web/email, so nothing really 
> super "confidential" on it.  

> Jeff

	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw@WittsEnd.com
  (The Mad Wizard)      |  (678) 463-0932   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!


  reply	other threads:[~2001-06-05 18:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-05  1:36 Jeff V. Merkey
2001-06-05  7:05 ` Alan Cox
2001-06-05 10:14   ` Daniel Roesen
2001-06-05 14:10   ` Michael H. Warfield
2001-06-05 18:30   ` Jeff V. Merkey
2001-06-05 18:42     ` Michael H. Warfield [this message]
2001-06-05 13:07 ` Henning P. Schmiedehausen
2001-06-05 13:41   ` Daniel Roesen
2001-06-05 10:33 Randal, Phil
2001-06-05 11:07 ` Matti Aarnio
2001-06-05 17:19 ` Brian Wellington

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=20010605144216.A18046@alcove.wittsend.com \
    --to=mhw@wittsend.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jmerkey@timpanogas.org \
    --cc=jmerkey@vger.timpanogas.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®