From: "J. Bruce Fields" <bfields@fieldses.org>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Linux NFS ML <linux-nfs@vger.kernel.org>
Subject: Re: [patch 0/3] First tranche of SGI Enhanced NFS patches
Date: Mon, 9 Feb 2009 15:47:26 -0500 [thread overview]
Message-ID: <20090209204726.GH13636@fieldses.org> (raw)
In-Reply-To: <498FBE0B.1040104@melbourne.sgi.com>
On Mon, Feb 09, 2009 at 04:24:27PM +1100, Greg Banks wrote:
> Bruce, any word on these? I don't seem to have any specific review
> items that I need to pay attention to with these patches, and I don't
> see them in your for-2.6.30 branch, so can I get an ack or a nack or
> feedback on things that need fixing?
Sorry, that came around the time of the citi compromise, so I just
registered that it had gotten some responses, figured it'd probably be
resent, and filed it away....
(And, by the way, if anyone's waiting for me to respond to email from
the last month--you mght want to resend. The longer version:
We now believe that password-logging ssh and sshd were installed on citi
machines as early as November. We got reports of ssh scanning in
December and January, but just took down the misbehaving machines. In
mid-January we finally realized the problem was serious, disconnected
ourselves from the internet completely, took everything on our local
network offline (including our main mail server and linux-nfs.org), then
brought our external connection back up and slowly reconnected machines
to our local network as we audited and/or rebuilt them as appropriate.
To be cautious, I also did the same for my personal machines (including
my personal mail server), though I didn't have specific evidence they'd
been compromised.
The upshot is: there were a few days when mail wasn't getting through at
all, and I know at least some was never delivered. When it did get
through, I wasn't necessarily able to pay it much attention. So besides
just a sob-story, this is a request that people ping me if I haven't
responded to something I should have lately.)
--b.
next prev parent reply other threads:[~2009-02-09 20:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 10:26 [patch 0/3] First tranche of SGI Enhanced NFS patches Greg Banks
2009-01-13 10:26 ` [patch 1/3] knfsd: remove the nfsd thread busy histogram Greg Banks
2009-01-13 16:41 ` Chuck Lever
2009-01-13 22:50 ` Greg Banks
[not found] ` <496D1ACC.7070106-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2009-02-11 21:59 ` J. Bruce Fields
2009-01-13 10:26 ` [patch 2/3] knfsd: avoid overloading the CPU scheduler with enormous load averages Greg Banks
2009-01-13 14:33 ` Peter Staubach
2009-01-13 22:15 ` Greg Banks
[not found] ` <496D1294.1060407-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2009-01-13 22:35 ` Peter Staubach
2009-01-13 23:04 ` Greg Banks
2009-02-11 23:10 ` J. Bruce Fields
2009-02-19 6:25 ` Greg Banks
2009-03-15 21:21 ` J. Bruce Fields
2009-03-16 3:10 ` Greg Banks
2009-01-13 10:26 ` [patch 3/3] knfsd: add file to export stats about nfsd pools Greg Banks
2009-02-12 17:11 ` J. Bruce Fields
2009-02-13 1:53 ` Kevin Constantine
2009-02-19 7:04 ` Greg Banks
2009-02-19 6:42 ` Greg Banks
2009-03-15 21:25 ` J. Bruce Fields
2009-03-16 3:21 ` Greg Banks
2009-03-16 13:37 ` J. Bruce Fields
2009-02-09 5:24 ` [patch 0/3] First tranche of SGI Enhanced NFS patches Greg Banks
2009-02-09 20:47 ` J. Bruce Fields [this message]
2009-02-09 23:26 ` Greg Banks
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=20090209204726.GH13636@fieldses.org \
--to=bfields@fieldses.org \
--cc=gnb@melbourne.sgi.com \
--cc=linux-nfs@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