From owner-freebsd-security Mon Apr 23 8:29:48 2001 Delivered-To: freebsd-security@freebsd.org Received: from w2xo.pgh.pa.us (18.gibs5.xdsl.nauticom.net [209.195.184.19]) by hub.freebsd.org (Postfix) with ESMTP id AAE4737B422 for ; Mon, 23 Apr 2001 08:29:45 -0700 (PDT) (envelope-from durham@w2xo.pgh.pa.us) Received: from w2xo (w2xo [192.168.5.1]) by w2xo.pgh.pa.us (8.11.2/8.9.3) with ESMTP id f3NFSPq28106 for ; Mon, 23 Apr 2001 15:28:25 GMT (envelope-from durham@w2xo.pgh.pa.us) Date: Mon, 23 Apr 2001 15:28:24 +0000 (GMT) From: Jim Durham X-Sender: durham@w2xo.int To: freebsd-security@freebsd.org Subject: Re: Connection attempts In-Reply-To: <200104231229.f3NCTk939079@caerulus.cerintha.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 23 Apr 2001, Michael S Scheidell wrote: > In local.freebsd.security, you wrote: > > > >Script kiddies..just ignore it and get used to it. > > I don't suggest ignoring the 'kiddies' that walk down the street trying to > see if my windows are open either. > > 80% of these systems have bveen compromized, and the owner doesn't even > know it. > > Wouldn't you like to take these systems off the net? > You want one of them to run against your system (if you miss a security > bulitin?) > > its easy enough to log and alert the isp. > > I don't know what you folks' experience has been, but I've had almost no luck with alerting ISPs to these problems. A lot of this stuff comes from Korea and Chekoslovokia and I get no responses from the ISPs. -Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message