On 9/22/2007, Bennett Lee ([EMAIL PROTECTED]) wrote: > Obviously, hiding an internal IP isn't security, but broadcasting it > *IS* insecure. Think of it like sticking a map on your front door > with a big red arrow that says "Our safe is here." If you have to > broadcast this information, then you should at least misdirect > trespassers so they waste their time on a fool's errand, thus > allowing you more time to detect/stop them with your REAL security. > And it shouldn't hinder troubleshooting. Even if you have multiple > mail servers, clusters, proxies, forwarders, etc., you can at least > obfuscate the internal IPs with a 1-to-1 mapping to a bogus network.
If someone is capable of hacking into your network, do you seriously think that they would *not* be capable of sniffing out all ofyour servers within minutes? Of course - I see nothing wrong with not broadcasting them, other than - as Michael pointed out - it can make troubleshooting a problem much more difficult... But I also don't see their existence as a problem either... Obviously you do - ain't freedom grand? -- Best regards, Charles ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
