[PLUG-TALK] Hacking in TV SHows

[Daniel Herrington]

This all peaked my interest in what would it take to have a set of tools
that would do the following:

1) Trawl snort logs for ip addresses
2) Run whois and use other free tools to gather info on the ip address in
questions
3) Run nmap scans on the ip address
4) Build a profile on the attacking server

There could be steps further down the chain, but that's what I've come up
with so far. Are there already tools that do this?

(I'm building something in ruby just to chain snort, whois, and nmap
together since I wanted to play with ruby, but I'm wondering if there is
some commercial or open source product).

thanks,

On Mon, Nov 24, 2014 at 3:01 PM, Rich Shepard <rshepard at appl-ecosys.com>
wrote:

> On Mon, 24 Nov 2014, Paul Heinlein wrote:
>
> > [go ahead and say it: I have the viewing habits of a 14-year-old boy]
>
> Paul,
>
>    If it keeps you young, go for it.
>
> > I actually have no complaint with this. Research is tedious; few things
> > are more boring than watching someone extract interesting information
> from
> > a book, library, or computer. So writers use "advanced technology" or
> > "incredible hacker" as a stand-in. People might get the wrong idea about
> > systems administration, but they get more broadly engaging stories.
>
>    I don't watch TV so I know nothing about what goes into the programs.
> But
> over the years I've notices that almost all fiction authors (at least in
> the
> mystery/suspense/thriiler genres) get computers and firearms all wrong.
> You'd think the reality and accuracy would be easy to check, but it's
> apparently not done. Distracting, but not fatal. :-)
>
> Rich
>
> _______________________________________________
> PLUG-talk mailing list
> PLUG-talk at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug-talk
>



-- 
Daniel B. Herrington
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pdxlinux.org/pipermail/plug-talk/attachments/20141124/f65dc4e9/attachment.html>