RE: [MLUG - DISCUSSION] network scanning?

["McNutt, Justin M." <EMAIL:PROTECTED>]

> IATS as a whole can't scan your system. Just because you work for IATS
> doesn't mean you can scan. Basically, Greg Johnson, myself, Olexander
> Krupoderov, and Justin McNutt are the only people I know of who can
> perform scans. The machines which are allowed to scan are the
> following:
> 
> chachi.iats.missouri.edu (McNutt)
> monad.iats.missouri.edu (Johnson)(Not Active)
> chiron.iats.missouri.edu (Johnson)
> metroid.iats.missouri.edu (Bradshaw)
> securityscan1.iats.missouri.edu (Johnson)
> securityscan2.iats.missouri.edu (Johnson)
> securityscan3.iats.missouri.edu (Bradshaw)
> securityscan4.iats.missouri.edu (Johnson)(Not Active)
> securityscan5.iats.missouri.edu (Bradshaw)(Not Active)

There are two others:

nin.iats.missouri.edu (me, not often) and
boomerang.iats.missouri.edu (also me, random)

Chachi is the production machine for the suite of perl scripts I wrote that
do various things (mostly SNMP stuff).  You'll get an SNMP 'ping' or two
once a week very early on Sunday mornings.

NiN is the test box.  It rarely does the 'ping', but every now and then I
need to test that function when I change the code for it (almost never).

Boomerang is both my laptop and my development box for my perl scripts
(where the *real* hacking goes on).  Strange things can come from this box,
although I try to keep it to a minimum.

> If you see scans coming from anywhere else, e-mail 
> EMAIL:PROTECTED or
> call Greg Johnson. I don't see as many hardcore scans as I do people
> scanning for individual things, like trojan horses.

True.

--J
--
To manage your subscription, go to http://mlug.missouri.edu/members/edit.php

Archives are available at http://mlug.missouri.edu/list-archives/