Fingerprints are usually derived from the handshake, but don't have to be - until it has a fingerprint for the host, ntop will check each tcp packet to see if it can create the print (there is a long block of code in processIpPkt() in pbuf.c that does the actual 'printing').
However, just because ntop can create a print doesn't (1) mean it can match it to the file and (2) that it's not altered by any one of a bunch of things such as switches, routers, etc. All of that means it's a flakey process. (1) Make sure ntop is reading your new ettercap file - it reads from the execution directory, not the usual ones (I fixed the messages in the cvs last week so you can see what is being read) (2) To check the details, build ntop with #define FINGERPRINT_DEBUG (globals-defines.h) to get the extra log messages. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, May 11, 2006 2:43 PM To: [email protected] Subject: [Ntop] fingerprints I've added new fingerprints and confirmed that ntop loads them, however when I run ntop, it still doesn't detect the host's OS. I'm loading ntop with a pcap file, so I'm sure that the packet I took the signature from is being analyzed. My question is: does ntop report a host-fingerprint match after receiving a specified number of packets containing a given signature, or just after finding a first match? /Michal _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
