Hay i try to link two bots together, when i do it whit 1.6.21 it works fine whitout any problem at all, what more can i tell that is importent to now for you ppl to track down whats wrong.
I use it behind a firewall but all bots are running on same computer so it shuld not matter anyways i try to connect them to "127.0.0.1"
Hub
[15:23:00] Telnet connection: 127.0.0.1/55437
[15:23:00] Sent STARTTLS to BOT-1...
[15:23:00] Challenging BOT-1...
[15:24:03] Lost dcc connection to BOT-1 (Slaktarn@127.0.0.1/55437)
BOT-1
[15:23:00] Got STARTTLS from Hub. Replying...
[15:23:00] Received challenge from Hub... sending response ...
[15:24:03] Timeout: bot link to Hub at 127.0.0.1:1600
squeege wrote:You need to make sure you have followed what it details in the Conf regarding SSL certificates.
Do what that tells you and you should be ok.
Ummm im not sure i fallow, What has SSL to do whit my bot linking, espect if i not will use SSL and set it to use it, But i havent, So i don´t see how that make any sense at all
1.8's botnet uses SSL by default, unless the bot is compiled without TLS. If you do not setup a certificate on your hub, the bots will not link.
Hope this clarifies the situation. How exactly to do it, is documented in doc/TLS
One question, what is the latest 1.8 snapshot? I want to know if I am using the latest and if there's any official place anyone can check for new releases. (I already know about the nightly snapshots)
Maybe an ftp link?
Thanks.
Libera ##rtlsdr & ##re - Nick: spithash
Click here for troll.tcl
pseudo wrote:1.8's botnet uses SSL by default, unless the bot is compiled without TLS. If you do not setup a certificate on your hub, the bots will not link.
Hope this clarifies the situation. How exactly to do it, is documented in doc/TLS
I don´t agree whit that, Lets check how the config looks
##### BOTNET/DCC/TELNET #####
# Settings in this section should be unimportant for you until you deal
# with botnets (multiple Eggdrops connected together to maximize efficiency).
# You should read doc/BOTNET before modifying these settings.
# If you want to use a different nickname on the botnet than you use on
# IRC (i.e. if you're on an un-trusted botnet), un-comment the next line
# and set it to the nick you would like to use.
set botnet-nick "${network}"
# This opens a telnet port by which you and other bots can interact with the
# Eggdrop by telneting in.
#
# There are more options for the listen command in doc/tcl-commands.doc. Note
# that if you are running more than one bot on the same machine, you will want
# to space the telnet ports at LEAST 5 apart, although 10 is even better.
#
# Valid ports are typically anything between 1025 and 65535 assuming the
# port is not already in use.
#
# If you would like the bot to listen for users and bots in separate ports,
# use the following format:
#
# listen 3333 bots
# listen 4444 users
#
# If you wish to use only one port, use this format:
#
# listen 3333 all
#
# You can setup a SSL port by prepending a plus sign to it:
#
# listen +5555 all
#
# You need to un-comment this line and change the port number in order to open
# the listen port. You should not keep this set to 3333.
listen 1600 all
It looks quite clear to me that its not using SSL? Or have i relly missed something here? as it says it need a + to work whit SSL
Botnet links between TLS-enabled bots will automatically switch to SSL.
In this case however, the nickname and password will be sent before SSL
negotiation takes place (the password is not send as cleartext anyway).
If one of the bots doesn't support TLS, the connection will fall back to
plain text. To require SSL explicitly, you need to open a ssl telnet
port on your hub and prefix the port number with + when adding it on your leafs.
Hope it's clear this way. I think you should read doc/TLS in addition to the config file. But if you'd like to suggest a change to the config in order to explain it better, feel free to tell us.
Botnet links between TLS-enabled bots will automatically switch to SSL.
In this case however, the nickname and password will be sent before SSL
negotiation takes place (the password is not send as cleartext anyway).
If one of the bots doesn't support TLS, the connection will fall back to
plain text. To require SSL explicitly, you need to open a ssl telnet
port on your hub and prefix the port number with + when adding it on your leafs.
Hope it's clear this way. I think you should read doc/TLS in addition to the config file. But if you'd like to suggest a change to the config in order to explain it better, feel free to tell us.
Yeh i think i got it clear Pseudo, if i got it clear and understand everything right so is the only way to link over botnet whitout SSL to not build eggdrop whit SSL,
I can not whit other words just use the SSL when i connect to the server, as the client will force me to also use it on botnet, witch quite stupid way code it and in my eyes shuld be optional,
I mean if i need to connect to an SSL server thats good if i can do that, but thats relly not means i need to have botnet whit SSL and in my case the bots are on localhost so why shuld i need to have SSL for that.
You just need to read few lines of documentation and issue a command or two to get yourself a certificate and a key. Then it will work. That simple.
It's obviously not necessary to encrypt the botnet on localhost, but we just decided to enable encryption always when possible instead of relying on random factors.
Why does it bother you anyway? Let it work and forget how it works.
pseudo wrote:You just need to read few lines of documentation and issue a command or two to get yourself a certificate and a key. Then it will work. That simple.
It's obviously not necessary to encrypt the botnet on localhost, but we just decided to enable encryption always when possible instead of relying on random factors.
Why does it bother you anyway? Let it work and forget how it works.
Hmmm everythings sloved, finally i just have one question left.
My bots are just allowed to have botnicks whit max lenght of 9chars how do i make it to allow up to 32 chars?
I sloved that one two, if anyone have problem whit it, just move
set nick-len 32, to the start of the conf file
