OpServ.trace (intra-userNode criteria)
Brought to you by:
entrope
A way to do searches by comparing data within the userNode.
example:
botnets where the nick and info are always the same
(not for all bots, but where each bot's nick is also
the same as its info)
?trace print authed no nick &info
or similar, so that instead of matching against the
string "&info", it matches against the client's info.
match_ircglob() could then take care of a string-wise
search if you're actually looking for the string
"&info", by using "\&info" (obviously that won't match
in a nick search, but if you're looking for info
"\&nick" for instance, it could.
Logged In: YES
user_id=258370
Patch attached, examples below:
<@madCoder> ?trace print nick &ident
-OpServ- The following users matched the criteria of your
search:
-OpServ- AuthServ!AuthServ@Services.TestNET.GamesNET.net
-OpServ- ChanServ!ChanServ@Services.TestNET.GamesNET.net
-OpServ- Global!Global@Services.TestNET.GamesNET.net
-OpServ- HelpServ!HelpServ@Services.TestNET.GamesNET.net
-OpServ- madCoder!madcoder@madCoder.TestNET.GamesNET.net
madCoder
-OpServ- OpServ!OpServ@Services.TestNET.GamesNET.net
-OpServ- QueueServ!QueueServ@Services.TestNET.GamesNET.net
-OpServ- Found 7 matches.
<@madCoder> ?trace print info &nick
-OpServ- The following users matched the criteria of your
search:
-OpServ- madCoder!madcoder@madCoder.TestNET.GamesNET.net
madCoder
-OpServ- Found 1 matches.
<@madCoder> ?whois hi2u
-OpServ- Nick : hi2u
-OpServ- Host : me@host.com
-OpServ- Real IP : 0.0.0.0
-OpServ- Modes : +i
-OpServ- Info : &ident
<@madCoder> ?trace print info \&amp;ident
-OpServ- The following users matched the criteria of your
search:
-OpServ- hi2u!me@host.com
-OpServ- Found 1 matches.
Implement comparisons between components of the userNode (eg nick = info)
Additional patch to help file
Logged In: YES
user_id=258370
Changed patch to make it compatible with SailorFrag's new
info_space criterion. Any input on possibly making a
"&ident" search ignore '~', and &info ignore leading
whitespaces? (I'm thinking that ignoring ~ in ident for all
cases should be effective, but I'm not sure about ignoring
all leading whitespaces, even though a whitespace will never
match any ident or nick.)
<@madCoder> ?dump AK N nick2 1 1066653427 user host.com +i
AAAAAA AKAAG : test
<@madCoder> ?whois test
-OpServ- Nick : test
-OpServ- Host : user@host.com
-OpServ- Real IP : 0.0.0.0
-OpServ- Info : test
<@madCoder> ?trace print info_space 1
-OpServ- The following users matched the criteria of your
search:
-OpServ- nick2!user@host.com
-OpServ- Found 1 matches.
<@madCoder> ?dump :nick2 nick test
<@madCoder> ?trace print nick &info info_space 1
-OpServ- The following users matched the criteria of your
search:
-OpServ- test!user@host.com
-OpServ- Found 1 matches.
same patch, compatible with info_space