From owner-freebsd-stable Tue Nov 28 17:46:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from coresync.com (ns1.coresync.net [64.71.131.2]) by hub.freebsd.org (Postfix) with SMTP id 99AD937B402 for ; Tue, 28 Nov 2000 17:46:34 -0800 (PST) Received: (qmail 20274 invoked by uid 1153); 29 Nov 2000 01:46:29 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Nov 2000 01:46:29 -0000 Date: Tue, 28 Nov 2000 17:46:29 -0800 (PST) From: "Jonathan M. Slivko" To: Kris Kennaway Cc: Henk Wevers , , Subject: Re: FreeBSD hacked? In-Reply-To: <20001128161324.A89746@citusc17.usc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apparently, it happened again. -- Jonathan M. Slivko On Tue, 28 Nov 2000, Kris Kennaway wrote: > On Tue, Nov 28, 2000 at 10:28:33PM +0100, Henk Wevers wrote: > > > > > > > > FreeBSD got a new Security Officer > > > > Nohican and {} would like to wish the new Security Officer (Kris) good luck > > on his new job. We are sure you will do a great job! > > > > Look at the bottom of http://freebsd.org.index.html > > Yes, I can confirm this happened last night. We were immediately > informed by those who did it including how it was achieved. The > penetration mechanism was not a vulnerability in FreeBSD and was > corrected immediately. While we don't believe that any malicious > activity took place while the machine was compromised, we've taken > steps to sanitize things anyway. > > Kris > > P.S. This kind of thing would have been better sent to > security-officer..for example, it's off-topic for -stable. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message