[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Identify Linux OS in packet Header
- From: Aaron Turner <aturner linuxkb org>
- To: Perry Blalock <perryb badger1 net>
- Cc: redhat-list redhat com, recipient list not shown: ;
- Subject: Re: Identify Linux OS in packet Header
- Date: Fri, 28 Jan 2000 00:01:31 -0800 (PST)
Port scanners such as nmap and OS detectors such as queso are known to do
this, but not the way you indicate. Rather they send a set of packets to
the machine and look at the responses. By looking at the response, one
can determine the OS and even sometimes the kernel version. This is
because there are situations that are not required as part of the TCP
state engine. Hence each vendor impliments it a different way.
On Thu, 27 Jan 2000, Perry Blalock wrote:
> Hello redhat-list,
>
> Anyone ever hear of Liunx, as an OS, being identified anywhere in a
> TCP/IP packet header? Reason I'm asking is that a certain software
> claims to be able to glean that specific information from the
> packet header, dunno which daemon, of a Linux machine.
>
> Best regards,
> Perry mailto:perryb badger1 net
>
>
>
> --
> To unsubscribe: mail redhat-list-request redhat com with "unsubscribe"
> as the Subject.
>
--
Aaron Turner, Core Developer http://vodka.linuxkb.org/~aturner/
Linux Knowledge Base Organization http://www.linuxkb.org/
Because world domination requires quality open documentation.
aka: aturner vicinity com, aturner pobox com, ion_beam_head ashtech net
The difference between `Unstable' and `Usable' is only two characters: NT
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]