🚀 go-pugleaf

In article <B0CF2F8A9668103526@lovejoy.demon.co.uk>,
ben@lovejoy.demon.co.uk (Ben Lovejoy) wrote:

> Bruce Horrocks <bh@granby.demon.co.uk> wrote:
> 
> >[snip] include a firewall as well.
> 
> How real are the risks? Given that a hacker would have no knowledge of our
> internal IP addresses, nor any of the filenames, folder structures, etc,
> where would they start?

Try connecting to all the common ports (http, nntp, pop3, smtp, telnet,
ftp, etc.) for every machine on your subnet.  If one of those works,
take a look at the transcript and take it from there.  Should take two
or three seconds per machine to explore all the useful ports.

> Does anyone know of any documented cases of hacking
> into an NDU account?

I know of such cases.  I am not permitted to produce documentation
of them.  The machines attacked were at a company which had recently
installed a system like yours.  While the company involved did work
which would be 'spoiled' if leaked to the public, the work wasn't
anything to do with the military or anything SOOPER SEKRIT, just a
normal company with around 50 micros connected to the net.  I think
they were attacked not because of what they did, but because they
were there.

The installation was secure -- the cracking attempt showed only
because I noticed that the router was unusually busy and checked
some of the logs.

Simon.
-- 
Simon Slavin -- Computer Contractor. | Excessive quoting from Shakespeare:
   http://www.hearsay.demon.co.uk    |                  gag me with a folio.
Check email address for spam-guard.  | -- sclerc@ernie.bgsu.edu (Susan Clerc)
Junk email not welcome at this site. | I receive about 2.5 junk emails a day.