From: "Michael H. Warfield" <mhw@wittsend.com>
To: Alex Buell <alex.buell@tahallah.demon.co.uk>
Cc: "Michael H. Warfield" <mhw@wittsend.com>,
Alexander Viro <viro@math.psu.edu>,
"Albert D. Cahalan" <acahalan@cs.uml.edu>, Adam <adam@eax.com>,
Mailing List - Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Duplicate '..' in /lib
Date: Tue, 17 Jul 2001 08:33:18 -0400 [thread overview]
Message-ID: <20010717083318.B4692@alcove.wittsend.com> (raw)
In-Reply-To: <20010716222215.A4695@alcove.wittsend.com> <Pine.LNX.4.33.0107171123320.3591-100000@tahallah.demon.co.uk>
In-Reply-To: <Pine.LNX.4.33.0107171123320.3591-100000@tahallah.demon.co.uk>; from alex.buell@tahallah.demon.co.uk on Tue, Jul 17, 2001 at 11:26:58AM +0100
On Tue, Jul 17, 2001 at 11:26:58AM +0100, Alex Buell wrote:
> I'm just wondering how they managed to get in given that I never download
> binaries and always compile from sources myself. Probably through a
> compromised TCP/IP service, I bet.
That would be a good guess. Without knowing what distribution
you are on and what services you are running, it's impossible to guess.
But there aren't too many out there that don't have something and all
of them have have security updates even for the latest distros. I just
got done researching a couple of DNS worms that are taking advantage
of Bind 8.2.2 and earlier. They probe through DNS only and are massively
scanning the entire IPv4 address space. In three weeks I saw over
30,000 probes into a /19 monitored address space from over 3,000 unique
compromised hosts. At that probing level, it's almost impossible NOT
to get poked by one of those suckers sooner or later. A lot of others
are scanning for port 111 (sun_rpc) or port 515 (lp) and there have been
a raft of problems in ftp. All of these are being automatically scanned
for and even slow dial-ups are going to get hit sooner or later.
It's gotten decidedly MORE hostile out there in the last year or
two with the appearance of these scripted worms, like Ramen, L1on, and TSIG,
that people can just tack more exploits onto and release in the wild.
> --
> Hey, they *are* out to get you, but it's nothing personal.
> http://www.tahallah.demon.co.uk
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!
next prev parent reply other threads:[~2001-07-17 12:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 4:50 Alex Buell
2001-07-16 5:07 ` Ben Collins
2001-07-16 5:08 ` Ignacio Vazquez-Abrams
2001-07-16 5:11 ` Adam
2001-07-16 5:16 ` Albert D. Cahalan
2001-07-16 5:38 ` Alexander Viro
2001-07-16 5:55 ` David Luyer
2001-07-16 6:30 ` Alex Buell
2001-07-16 8:07 ` Wichert Akkerman
2001-07-16 8:16 ` J Troy Piper
2001-07-17 2:22 ` Michael H. Warfield
2001-07-17 10:26 ` Alex Buell
2001-07-17 12:33 ` Michael H. Warfield [this message]
2001-07-17 12:44 ` Alex Buell
2001-07-17 12:58 ` Michael H. Warfield
2001-07-17 13:00 ` Large memory oops/odd behaviour Linux 2.2, seeking recommendations Mr. James W. Laferriere
2001-07-16 5:32 ` Duplicate '..' in /lib Alex Buell
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=20010717083318.B4692@alcove.wittsend.com \
--to=mhw@wittsend.com \
--cc=acahalan@cs.uml.edu \
--cc=adam@eax.com \
--cc=alex.buell@tahallah.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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®