No subject

Hopefully your firewall/NAT/router is configured to drop all incoming
packets with an internal IP address (block spoofed packets).  This
information would be helpful to a hacker that has already broken into =
your
firewall/NAT, but they would be able to get the same information and =
more if
they already had broken into your firewall/NAT.
	HTH, Rolf.

Rolf Mikkelson=20
Application System Specialist=20
rolf at dtcc.edu=20
302.739.6763 voice=20
302.739.6822 fax=20
-----Original Message-----
From: ipac-admin at lists.tblc.org [mailto:ipac-admin at lists.tblc.org] On =
Behalf
Of Natasha Stephan
Sent: Wednesday, July 30, 2003 10:43 AM
To: ipac at snoopy.tblc.org
Subject: RE: [ipac] Web Server IP address echoed in HIP URL... Security
risk?


Hi all,
I'm no network guru either, but here's my $.02...

I did a search of our iPac within our network.  I saw our private =
address -
a 192.x.x.x number.  But I figured that this was because I was within =
the
network.  When I saw Bruce's email, I did a search on his iPac to see =
how it
looked from the outside.  Here's what I got:

http://troi.richland.lib.sc.us/ipac20/ipac.jsp? [basic iPac stuff]
session=3D [session number]
&profile=3Dint
&uri=3Dlink=3D [not sure what these numbers are]
&aspect=3Dbasic_search
&menu=3Dsearch
&ri=3D1
&source=3D10.x.x.x@!horizon [Richland iPac's private address]
&term=3DAsimov%2C+Isaac%2C+1920-
&index=3DPUBAU
#focus

I would be that, were Bruce to search our iPac, he'd see our 192.x.x.x
number.  Probably not a good thing.
Natasha