Nmap Development mailing list archives
Re: Service Detection Patch: TANDBERG MXP Series telnetd
From: Tom Sellers <nmap () fadedcode net>
Date: Wed, 19 Mar 2008 19:27:44 -0500
Brandon Enright wrote:
That makes sense. Also, I just noticed a stray '*' on the end of the "...Release ([\w.]+)*|". I've dropped it for now. Did you mean the release is optional ('?'), a literal asterisk, ('\*'), or something else? If the capturing match is optional we'll have to split the match into two entries.
I am still trying to get a handle on PCRE. The strings it would need to match look like this - F6.01 The response string goes on from there. For Example: Welcome to NY-Main-Office TANDBERG Codec Release F6.01 Some other data here. It is entirely possible that the * is not needed. The last data that I wanted to capture was the release version, which is always in the banner. Sorry for the trouble, Tom _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Service Detection Patch: TANDBERG MXP Series telnetd Tom Sellers (Mar 19)
- Re: Service Detection Patch: TANDBERG MXP Series telnetd Tom Sellers (Mar 19)
- Re: Service Detection Patch: TANDBERG MXP Series telnetd Brandon Enright (Mar 19)
- Re: Service Detection Patch: TANDBERG MXP Series telnetd Tom Sellers (Mar 19)
- Re: Service Detection Patch: TANDBERG MXP Series telnetd Brandon Enright (Mar 19)
- Re: Service Detection Patch: TANDBERG MXP Series telnetd Tom Sellers (Mar 19)
- Re: Service Detection Patch: TANDBERG MXP Series telnetd Tom Sellers (Mar 20)
- Re: Service Detection Patch: TANDBERG MXP Series telnetd Tom Sellers (Mar 19)