Re: feature req: more info on TCP session for content filter and/or policy delegation server

• Previous message: Magnus Bäck: "Re: Virtual "catch all" problem"
• Next in thread: Mark Martinec: "Re: feature req: more info on TCP session for content filter and/or policy delegation server"
• Maybe reply: Mark Martinec: "Re: feature req: more info on TCP session for content filter and/or policy delegation server"
• Maybe reply: Wietse Venema: "Re: feature req: more info on TCP session for content filter and/or policy delegation server"
• Maybe reply: Mark Martinec: "Re: feature req: more info on TCP session for content filter and/or policy delegation server"
• Maybe reply: Wietse Venema: "Re: feature req: more info on TCP session for content filter and/or policy delegation server"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

On Fri, Dec 31, 2004 at 11:50:13PM -0500, Wietse Venema wrote:
> Neither source port nor destination port are relevant for
> client fingerprinting.

yes, but p0f require it to retreive data from it's
cache ...

Regards,

P.Y. Adi Prasaja

• Previous message: Magnus Bäck: "Re: Virtual "catch all" problem"
• Next in thread: Mark Martinec: "Re: feature req: more info on TCP session for content filter and/or policy delegation server"
• Maybe reply: Mark Martinec: "Re: feature req: more info on TCP session for content filter and/or policy delegation server"
• Maybe reply: Wietse Venema: "Re: feature req: more info on TCP session for content filter and/or policy delegation server"
• Maybe reply: Mark Martinec: "Re: feature req: more info on TCP session for content filter and/or policy delegation server"
• Maybe reply: Wietse Venema: "Re: feature req: more info on TCP session for content filter and/or policy delegation server"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]