Article View: comp.security.firewalls
Article #193Re: Anyone use Hack Tracer?
From: Joe S
Date: Thu, 18 Jan 2001 08:05
Date: Thu, 18 Jan 2001 08:05
63 lines
3571 bytes
3571 bytes
Well said. "Michael Scheidell" <me@privacy.net> wrote in message news:lOK86.1826$Dd.10880505@news1.mia... > > "Lawrence Baldwin" <baldwinlSPAMMENOT@mynetwatchman.com> wrote in message > news:3A6296A5.2EA4B529@mynetwatchman.com... > > Not to be a pessimist, but my biggest realization regarding network > > security is that > > > > "SECURE" is not a state of being, it is a VERB describing the *continual > > process* of reviewing, researching, > > learning of matters of security. > > I agree. > > as in 'security is a process' not a product. > With so many new ways to hack into a system, not to mention the odd 'woops, > I forgot to apply that 15 month old patch to MS II2 and now the Russians > have bill's source code'. > > Basically, the only way to make sure, 100% that someone can't break into > your system is to use a little known hardware product, found at home depot, > and purchased for $4.95 (yep, less then $5 us) > > Its a pair of wire cutters. > > Other than that, it is important to be notified when you are being hacked, > and important that you report it to the ISP. > > Important, because that server is either a victim (already been hacked) or > the villain. > Either case, the ISP in question had better take actions or they could find > themselves in the receiving end of an FBI investigation (BellSouth, take > note: you are really down there on the list of ISP's who take hackers and > security seriously, with 15% of the Cayman routers you install, open to the > outside world with no passwords!) > > It isn't 6 hours that goes by that I don't have some luser on a BellSouth > dsl line scanning for either the netbus Trojan, or the sunrpc buffer > overflow. > > Stopped the attack? yep, my firewall stopped it from attacking here, but if > I get notified, and let BellSouth know about it and they actually did > something about it, then the infection would spread slower. > > (still need the$4.95 hardware security device to stop it) > > Bottom line, 15 to 20% of the dsl and cable modem connected computers are > infected with Trojans, sub seven, netbus or something similar. > > Just waiting to launch additional attacks. > Stop the attack, identify the attacker (in real time) and complain. > > > > >
Technical Details
Message-ID:
<Cpx96.3807$CR2.174436@news3.atl>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-03!supernews.com!newsfeed.wirehub.nl!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news3.atl.POSTED!not-for-mailReferences:
<mQp86.1663$Dd.9410278@news1.mia> <3A62709C.7EF9E66@mynetwatchman.com> <Zuw86.3425$Oe.16433@tor-nn1.netcom.ca> <3A6296A5.2EA4B529@mynetwatchman.com> <lOK86.1826$Dd.10880505@news1.mia>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f922c,67dc1e9da7b27b77 X-Google-Attributes: gidf922c,public X-Google-Thread: 1122a6,67dc1e9da7b27b77 X-Google-Attributes: gid1122a6,public X-Google-Thread: 10090f,67dc1e9da7b27b77 X-Google-Attributes: gid10090f,public X-Google-ArrivalTime: 2001-01-18 00:04:13 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-03!supernews.com!newsfeed.wirehub.nl!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news3.atl.POSTED!not-for-mail From: "Joe S" <nomail@bellmail.net> Newsgroups: comp.security.firewalls,bellsouth.net.support.adsl,bellsouth.net.security References: <mQp86.1663$Dd.9410278@news1.mia> <3A62709C.7EF9E66@mynetwatchman.com> <Zuw86.3425$Oe.16433@tor-nn1.netcom.ca> <3A6296A5.2EA4B529@mynetwatchman.com> <lOK86.1826$Dd.10880505@news1.mia> Subject: Re: Anyone use Hack Tracer? Lines: 65 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: <Cpx96.3807$CR2.174436@news3.atl> Date: Thu, 18 Jan 2001 03:05:17 -0500 NNTP-Posting-Host: 216.76.168.126 X-Trace: news3.atl 979804898 216.76.168.126 (Thu, 18 Jan 2001 03:01:38 EST) NNTP-Posting-Date: Thu, 18 Jan 2001 03:01:38 EST