egghelp.org community Forum Index
[ egghelp.org home | forum home ]
egghelp.org community
Discussion of eggdrop bots, shell accounts and tcl scripts.
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

gseen won't find the most recent record over the botnet

 
Post new topic   Reply to topic    egghelp.org community Forum Index -> Modules & Programming
View previous topic :: View next topic  
Author Message
3rdBAR
Voice


Joined: 15 May 2006
Posts: 15

PostPosted: Thu Jul 19, 2007 11:30 am    Post subject: gseen won't find the most recent record over the botnet Reply with quote

I have a botnet comprising multiple eggs on multiple networks. When I use gseen to find out when and where a particular nick was last seen, gseen wants to stop at the first bot it queries who has seen the particular nick. It does this regardless of whether the instance it finds is much older than instances of the same nick on other bots in the net. And it even stops like this when it finds an instance of a nick on the first bot it checks when the queried nick (the same person being sought) is in fact present on one of the other botnet bot's networks in one of its channels.

Can gseen be effectively used in the way I want? I want it to find the most recent occurrence of a nick's presence across the botnet. I currently have one hub and 12 leafs. Is this stop-on-first-hit a configuration issue?

TIA
Back to top
View user's profile Send private message
3rdBAR
Voice


Joined: 15 May 2006
Posts: 15

PostPosted: Sat Jul 21, 2007 3:05 pm    Post subject: Reply with quote

No replies, eh? Two days ago I wrote to the author of gseen about this as well. He hasn't replied either (or at least he hasn't replied yet).

One thing about this problem that puzzles me a bit is this: If a botnet were on a single IRC network, but its individual bots were on separate channels (no common channels among them), I'm guessing the same stop-on-first-hit problem would occur. Here's the scenario: The botnet bots are linked, someone initiates a gseen query for a nick, gseen checks the bots one at a time until it finds an instance of the entered nick. When it finds this first instance in one of the bot's gseen.dat files, it checks no further. So if this first bot who replies that the nick has visited one of its channels reports that the nick had been there, say, 2 weeks ago, but yesterday the same nick had joined a channel monitored exclusively by one of the other not yet queried botnet bots, the person initiating the query will never learn of this nick's recent join to that channel.

So is this how it works? If not, why does gseen stop on the first hit and check no further on my multi-network botnet? If this is simply how gseen works, I'm surprised that it doesn't get more complaints from people using it with botnets. If I'm missing something, please tell me.
Back to top
View user's profile Send private message
Callisto
Halfop


Joined: 13 Mar 2005
Posts: 86

PostPosted: Sat Jul 21, 2007 4:38 pm    Post subject: Reply with quote

dont know if you checked this in the gseen.conf file or not

Code:
# forward a request to other bots, if a !seen returned no result?
set botnet-seens 1


If so apologies
Back to top
View user's profile Send private message
3rdBAR
Voice


Joined: 15 May 2006
Posts: 15

PostPosted: Sun Jul 22, 2007 1:37 am    Post subject: Reply with quote

Callisto wrote:
dont know if you checked this in the gseen.conf file or not

Code:

set botnet-seens 1




Yes, all bots in the net are set to "1" for set botnet-seens. I believe "1" is the default for that directive anyway. The !seen requests have always queried subsequent bots in the net fine. The process just stops cold after finding the first instance, irrespective of whether or not it's the most recent one.

Thanks for the reply.
Back to top
View user's profile Send private message
Sir_Fz
Revered One


Joined: 27 Apr 2003
Posts: 3793
Location: Lebanon

PostPosted: Sun Jul 22, 2007 6:42 am    Post subject: Reply with quote

If that's the case then I guess this is a bug in the module and should be fixed. Unfortunately, the author has stopped developing the module long time ago. I'm not sure if bseen has this feature, but you can try it (search the tcl archive for bseen).
_________________
Follow me on GitHub

- Opposing

Public Tcl scripts
Back to top
View user's profile Send private message Visit poster's website
3rdBAR
Voice


Joined: 15 May 2006
Posts: 15

PostPosted: Sun Jul 22, 2007 9:43 am    Post subject: Reply with quote

Okay, here's the bottom line. I've just received a response from the author of gseen and this is what he said:

Florian wrote:
IIRC this is the coded functionality, sorry. The only way to change it is to write an extension... either in gseen's c-code directly, or maybe via tcl (can't remember the details of the implementation, so I'm not sure if tcl is an option).


It's a bit astonishing to me that no one has noticed this flaw before. I'll have to check into bseen, as you've suggested.

Thanks.
Back to top
View user's profile Send private message
Alchera
Revered One


Joined: 11 Aug 2003
Posts: 3344
Location: Ballarat Victoria, Australia

PostPosted: Sun Jul 22, 2007 5:25 pm    Post subject: Reply with quote

3rdBAR wrote:
It's a bit astonishing to me that no one has noticed this flaw before.

Thanks.

Probably because no one bothered to set "botnet-seens"; I disabled it as I am interested in the results of just one channel, which would be the norm.
_________________
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM
Back to top
View user's profile Send private message Visit poster's website
3rdBAR
Voice


Joined: 15 May 2006
Posts: 15

PostPosted: Sun Jul 22, 2007 11:25 pm    Post subject: Reply with quote

Alchera wrote:

Probably because no one bothered to set "botnet-seens"; I disabled it as I am interested in the results of just one channel, which would be the norm.


Maybe, but I find that hard to imagine. Since botnet-seens is enabled by default, and since lots of eggdrop users have botnets and multiple channels, and since gseen has been around for a relatively long while, I'd have guessed someone would've reported it well before now.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    egghelp.org community Forum Index -> Modules & Programming All times are GMT - 4 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Forum hosting provided by Reverse.net

Powered by phpBB © 2001, 2005 phpBB Group
subGreen style by ktauber