From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: joe briggs <jbriggs@briggsmedia.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Help with virus/hackers
Date: 17 Apr 2003 13:42:03 +0100 [thread overview]
Message-ID: <1050583322.31412.1.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <200304171015.13474.jbriggs@briggsmedia.com>
> Can anyone offer any advice or insight?
Without knowing what services were publically accessible, and internally
accessible (since you dont know if someone used something like a windows
worm to attack from the inside) no.
cert have good general faq's on cleaning up after attackers and also
track attacks for patterns so do notify them.
next prev parent reply other threads:[~2003-04-17 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 14:15 joe briggs
2003-04-17 12:42 ` Alan Cox [this message]
2003-04-17 13:55 ` Richard B. Johnson
2003-04-17 14:12 ` Alan Cox
2003-04-17 15:31 ` John Jasen
2003-04-17 15:45 ` John Bradford
2003-04-17 16:26 ` Alan Cox
2003-04-17 18:00 ` John Bradford
2003-04-17 17:17 ` Christopher Curtis
2003-04-17 14:12 ` Alan Cox
2003-04-17 16:34 Kenny Mann
2003-04-17 17:24 ` Leonard Milcin, Jr
2003-04-17 18:12 Kenny Mann
2003-04-17 20:56 Kenny Mann
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=1050583322.31412.1.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jbriggs@briggsmedia.com \
--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®