Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

who is responsible for keeping private IP addresses private?



Suppose I have two machines connected to the same DSL router: Public, with
a generally-accessible IP address, and Private, with 192.168.1.1.  E.g.,
Public could be a domain's mail server, and Private could be a workstation
that downloads the mail.

Is there any way for an attacker elsewhere on the Net to impersonate
192.168.1.1?  (In other words, if Public trusts everything it receives from
192.168.1.1, can an attacker exploit that trust relationship as a first
step to cracking Public?)  If not, what part of the network infrastructure
prevents this from happening?

-- 
"The big dig might come in handy ... for a few project managers
 whom I think would make great landfill."  --Elaine Ashton
== seth gordon == sgordon at kenan.com == standard disclaimer ==
== documentation group, kenan systems corp., cambridge, ma ==
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org