Stack smashing detected: ./eggdrop terminated

[darthanubis]

Binary package hint: eggdrop

Attempting to Botnet two bots results in the hub crashing hard upon authentication with the leaf/other bot.

[Sami Haahtinen (ressu)]

confirming, i'm seeing this too.

[Sami Haahtinen (ressu)]

As an additional note, i'm seeing this on amd64 like the original reporter

[Devz (devzie)]

I too can confirm this occuring.

[Yutani (erick)]

I've also experienced this behavior by my eggdrop installation. Using Ubuntu 9.04 amd64.

[darthanubis (darthanubis)]

On Tuesday 15 September 2009 04:07:42 pm Yutani wrote:
> I've also experienced this behavior by my eggdrop installation. Using
> Ubuntu 9.04 amd64.
>
I forgot how I fixed this. I think it may have to do with running both bots
from the same machine, and trying to create a botnet?

[Yutani (erick)]

Yes, I'm trying to run two eggdrop's at the same time on the same pc with a botnet between the two bots. At first all goes well but after a while the bot crashes unexpected.

[darthanubis (darthanubis)]

On Tuesday 15 September 2009 07:29:28 pm Yutani wrote:
> Yes, I'm trying to run two eggdrop's at the same time on the same pc
> with a botnet between the two bots. At first all goes well but after a
> while the bot crashes unexpected.
>
Use two different PCs, or virtualize one? The same ip address is smashing.

[Yutani (erick)]

Problem is I've got about 4 or 5 bots all running on the same pc. Normally this would be no problem but to virtualize all bots would mean I need to install 4 or 5 virtual pc's running all linux... To keep this all running would be one hell of a task. Isn't there another way I could fix this?

[Yutani (erick)]

Would it help to have all the leafbots on one virtual machine and the hubbot on another? Would this avoid the stack smashing?

[darthanubis (darthanubis)]

On Saturday 19 September 2009 10:49:35 am Yutani wrote:
> Would it help to have all the leafbots on one virtual machine and the
> hubbot on another? Would this avoid the stack smashing?
>
Try playing with the forwarding of the ports option in the eggdrop.conf for
your bots. They can't have the same ip address. Did you try that?
Because when the eggdrop goes to valid during the handshakeand finds that
the ips are from thesame machine, it goes ape.

[Yutani (erick)]

I'm gonna try and install several virtual pcs and try getting it to run from there. Will update on how it goes.

[Yutani (erick)]

Currently installed VMWare with several Linux operating systems.

I came to the conclusion that the hub is causing all the problems with the handshake. So this means you can have all the leafbots on the same computer and the same operating system but the hubbot needs to be somewhere else. For example a virtual machine or other pc.

For now it works and I hope someone can fix this in a next release.

[plod (me-plod)]

I am getting this error, but this is the only eggy running an ubuntu 10.10 system

[cezary (cezary)]

Not sure whether this bug was answered, but I couldn't find answer before so I send it here.

It seems to have to do with lack of package TCL on an ubuntu system -
I had just the same bug until I installed TCL package - and than eggdrop started without problems.

TCL should be installed automatically with eggdrop, imho.

I'm using ubuntu-server with own grsec'd kernel, though I doubt grsec have something to do with this bug (as far as I remember it didn't work with ubuntu kernel either) AND eggdrop works fine on Slackware with grsec'd kernel

Greetz,
cezary

[darthanubis (darthanubis)]

Has nothing to do with the kernel or tcl and everything to do with eggdrop
faq.
On Mar 4, 2011 7:16 PM, "cezary" <email address hidden> wrote:
> Not sure whether this bug was answered, but I couldn't find answer
> before so I send it here.
>
> It seems to have to do with lack of package TCL on an ubuntu system -
> I had just the same bug until I installed TCL package - and than eggdrop
started without problems.
>
> TCL should be installed automatically with eggdrop, imho.
>
> I'm using ubuntu-server with own grsec'd kernel, though I doubt grsec
> have something to do with this bug (as far as I remember it didn't work
> with ubuntu kernel either) AND eggdrop works fine on Slackware with
> grsec'd kernel
>
> Greetz,
> cezary
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/220327
>
> Title:
> *** stack smashing detected ***: ./eggdrop terminated
>
> Status in “eggdrop” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: eggdrop
>
> Attempting to Botnet two bots results in the hub crashing hard upon
> authentication with the leaf/other bot.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/eggdrop/+bug/220327/+subscribe

[Zivago Lee (zivagolee)]

dpkg -l|grep tcl
ii tcl8.5 8.5.8-2 Tcl (the Tool Command Language) v8.5 - run-t

I have tcl and it still crashes the 2nd bot.

[Sami Haahtinen (ressu)]

Just as a side note, this bug is still there. Just ran into it a moment ago.

[Andrew Skalski (askalski)]

I ran into this error message yesterday when setting up a new Eggdrop bot. I'm posting to this ticket rather than creating a new bug report in case the two issues are related.

My crash happens every time the "md5" TCL function is called. The crash can be reproduced with this simple config file:

 #! /usr/bin/eggdrop
 md5 "crash!"

Removing patch "debian/eggdrop-1.6.19-ssl.patch" (aka "Rootie's SSL patch") fixes the issue for me. The error in the SSL patch is it changes src/tclmisc.c to include OpenSSL's declaration of the MD5_CTX struct, but still uses the bundled versions of MD5_Init/MD5_Update/MD5_Final in src/md5/md5c.c. Because the structs are different size (OpenSSL's is much smaller), the bundled MD5 functions end up smashing the stack.

It may also be possible to fix the issue without sacrificing the SSL patch, by ensuring that src/md5/md5c.c is not built or linked into the executable.

FWIW, the Eggdrop folks recommend against using Rootie's patch: http://www.eggheads.org/news/2011/05/25/39

I confirmed the crash exists on 1.6.19-1.2ubuntu3.1 (12.04 LTS) and 1.6.19-1.2ubuntu7 (13.04)

[Markus Blaschke (mblaschke)]

I confirm the crash for saucy (13.10)

[Marius Flage (marius-flage)]

Same for trusty (14.10). Is this being worked on, or is the eggdrop package in Ubuntu dead?