From owner-freebsd-security Tue Oct 3 7: 2:32 2000 Delivered-To: freebsd-security@freebsd.org Received: from mail.houston.rr.com (sm1.texas.rr.com [24.93.35.54]) by hub.freebsd.org (Postfix) with ESMTP id 22ED937B502 for ; Tue, 3 Oct 2000 07:02:29 -0700 (PDT) Received: from bloop.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Tue, 3 Oct 2000 09:04:22 -0500 Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e93E29p53594 for ; Tue, 3 Oct 2000 09:02:10 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200010031402.e93E29p53594@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: security@freebsd.org Subject: Script kiddies and port 12345 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Oct 2000 09:02:09 -0500 From: Stephen Hocking Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After a couple of weeks of probing 139, the little darlings are now hammering on 12345 - anybody have an idea of what hole this is? Another backdoor? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message