Re: Block Inbound Traffic
From: Thor Kottelin (thor_at_anta.net)
Date: 07/16/04
- Next message: lcs: "netscreen 5 firmware"
- Previous message: Thor Kottelin: "Re: crl.verisign.com is ok?"
- In reply to: Don Kelloway: "Re: Block Inbound Traffic"
- Next in thread: Greg Hennessy: "Re: Block Inbound Traffic"
- Reply: Greg Hennessy: "Re: Block Inbound Traffic"
- Reply: Don Kelloway: "Re: Block Inbound Traffic"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 16 Jul 2004 05:54:24 +0300
Don Kelloway wrote:
>
> "Don Kelloway" <dkelloway@commodon.com> wrote in message
> news:WFEJc.9201$sV2.2038@newsread2.news.atl.earthlink.net...
> > You cannot block an incoming connection by computer name because it
> can
> > be easily spoofed. Besides the computer name is not something that's
> > passed within an incoming packet.
Computer names are obtained by doing a reverse lookup on an IP address.
> I should have additionally stated that computer names are something that
> are only available to other computers within the same LAN.
If this name resolution occurs using DNS, it is often available throughout
the Internet. However, it is also correct (ObFirewall) that many name
services are confined to a LAN; typical examples are WINS and Windows Active
Directory. Host files are even more restricted, valid only for the machine
they are located on.
Thor
-- http://www.anta.net/
- Next message: lcs: "netscreen 5 firmware"
- Previous message: Thor Kottelin: "Re: crl.verisign.com is ok?"
- In reply to: Don Kelloway: "Re: Block Inbound Traffic"
- Next in thread: Greg Hennessy: "Re: Block Inbound Traffic"
- Reply: Greg Hennessy: "Re: Block Inbound Traffic"
- Reply: Don Kelloway: "Re: Block Inbound Traffic"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]