egghelp/eggheads community

Eggdrop1.6.20rc1 and SSL

2010-10-22T02:00:21-04:00

Got a little problem with ssl patch. Any help will be much appreciated.

Code:

Eggdrop v1.6.20+SSL (C) 1997 Robey Pointer (C) 2010 Eggheads[06:40:32] * Last context: main.c/955 [][06:40:32] * Please REPORT this BUG![06:40:32] * Check doc/BUG-REPORT on how to do so.

Did you read anything in this thread?

Statistics: Posted by Pixelz — Fri Oct 22, 2010 2:00 am

Eggdrop1.6.20rc1 and SSL

2010-10-22T01:05:19-04:00

Got a little problem with ssl patch. Any help will be much appreciated.

Code:

Eggdrop v1.6.20+SSL (C) 1997 Robey Pointer (C) 2010 Eggheads[06:40:32] * Last context: main.c/955 [][06:40:32] * Please REPORT this BUG![06:40:32] * Check doc/BUG-REPORT on how to do so.

Statistics: Posted by nmph — Fri Oct 22, 2010 1:05 am

Eggdrop1.6.20rc1 and SSL

2010-10-12T13:04:25-04:00

I think its safe to say that the people complaining and the post referring to energymech have nothing better to do.

If the patch works then great! Use it and move along. The developers have said it will be addressed in the next release. The thread should be done with.

Can you imagine if everyone that had a problem with their bot or issues related to the bot started complaining and whining? This place would turn into yet another forum full of bs and no solutions or support. We all encounter problems and find solutions to them. The solutions are offered throughout this site and should be tested if they solve your given issue. if they do, great. If they don't, ask and/or look for a solution. The developers aren't being compensated for their efforts/time. Be grateful for their work and take the advice/info.

I think this thread has served its purpose. Thanks to the developers for your hard work.

Statistics: Posted by marvz — Tue Oct 12, 2010 1:04 pm

Eggdrop1.6.20rc1 and SSL

2010-10-12T11:03:10-04:00

So I guess we all have to wait for the next official release right ?

Statistics: Posted by spithash — Tue Oct 12, 2010 11:03 am

Eggdrop1.6.20rc1 and SSL

2010-09-26T18:53:35-04:00

pseudo have you heard about EnergyMech? It seems like they're well ahead of you guys.

Energymech? What was this, can you remind me? Who has heard of it?

Oh, and why are you addressing me, when this has nothing to do with the thread topic? The advertisement page is here.

Statistics: Posted by pseudo — Sun Sep 26, 2010 6:53 pm

Eggdrop1.6.20rc1 and SSL

2010-09-26T18:26:05-04:00

Energymech doesn't support SSL either. If your comment was not about SSL but in general, it would be better to open a new thread "Eggdrop sucks, Emech rulez" to make it easier to identify your post as what it is - trolling.

PS: If anyone feels like deleting the post above me, please delete this one too.

Statistics: Posted by thommey — Sun Sep 26, 2010 6:26 pm

Eggdrop1.6.20rc1 and SSL

2010-09-26T16:49:15-04:00

pseudo have you heard about EnergyMech? It seems like they're well ahead of you guys.

Statistics: Posted by topdogg — Sun Sep 26, 2010 4:49 pm

Eggdrop1.6.20rc1 and SSL

2010-09-13T09:30:17-04:00

how about going back and forth on whos right and whos wrong, lets update one of the most popular bot platforms out there to actually incorporate ssl and ipv6? how long has mirc had support for these two protocols? irssi? bitchx? .. point proven.

How about reading before commenting?

No, eggdrop 1.6.20 doesn't have built-in support for SSL. We will finally add full IPv6 and SSL in the next eggdrop version. The current patch for .19 would need some modifications to apply to .20, but I guess somebody will release an update to it soon.

On the other hand, IPv6 and SSL are the first things which will enter the cvs after .20 so it won't be a long wait for official support Wink

mIRC has IPv6 support since the last version (a month ago). Unofficial DLLs were available, just as unofficial patches for eggdrop. Oh and btw, have you ever contributed to Eggdrop or irssi or anything open source? If no, stick to what's available and be thankful, as it's coming out of our good will, not out of your neverending complaints.

Meanwhile, eggdrop 1.8.0 CVS already has IPv6 support added and it's far more useable than older versions + buggy patches. If anybody is interested, it's available here
Beware that 3rd party modules won't work with 1.8 due to version checks, we'll eventually provide updated versions of the most common ones, as they are abandoned by their authors.

Statistics: Posted by pseudo — Mon Sep 13, 2010 9:30 am

Eggdrop1.6.20rc1 and SSL

2010-09-12T21:35:46-04:00

how about going back and forth on whos right and whos wrong, lets update one of the most popular bot platforms out there to actually incorporate ssl and ipv6? how long has mirc had support for these two protocols? irssi? bitchx? .. point proven.

Statistics: Posted by kenh83 — Sun Sep 12, 2010 9:35 pm

Eggdrop1.6.20rc1 and SSL

2010-08-27T18:49:29-04:00

That's the crash causing bug I was speaking about. This patch shifts down the function lookup table for modules, but doesn't update properly the indices in module.h so sometimes completely wrong functions get called, causing crashes. (These are at the end of the lookup table, including console_chon which is usually called when you log in the partyline.)

Statistics: Posted by pseudo — Fri Aug 27, 2010 6:49 pm

Eggdrop1.6.20rc1 and SSL

2010-08-27T15:35:17-04:00

On eggdrop1.6.20... with TCL 8.5 and 8.6

ok so I tried the 1st patch and now I tried this one too:

http://www.egghelp.org/files/patches/eg ... e.patch.gz

SAME error again, the bot connects with SSL and everything, BUT, when you try to log in the party line, you get this wonderful cherry:

Code:

[15:25:34]  [15:25:34] * Last context: tclhash.c/710 [Tcl proc: *chon:console:chon, param:  $_chonof1 $_chonof2]                                                                      [15:25:34]  [15:25:34] * Please REPORT this BUG!                                                                                                                                      [15:25:34]  [15:25:34] * Check doc/BUG-REPORT on how to do so.                                                                                                                        [15:25:34]  [15:25:34] * Wrote DEBUG[15:25:34]  [15:25:34] * SEGMENT VIOLATION -- CRASHING!

I tried in both FreeBSD and OpenBSD.

Epic Fail.

Statistics: Posted by spithash — Fri Aug 27, 2010 3:35 pm

Eggdrop1.6.20rc1 and SSL

2010-08-23T04:56:53-04:00

It's a time worn argument whether to release something that's been hacked together in a far from ideal way, or better to have nothing until someone who really knows what they're doing creates something that more people would consider up-to-standard. Users tend to favour the former and developers the latter

Rootie didn't specifically ask to quote this part of his e-mail but I should add it for context:
You can post the text above in the forum to inform users that there's a
"silent update" on the patch that might fix their problems. Actually I
lifted this patch to the newest versions for my private use only. The
patches you get from me work fine on my shell. If it doesn't work on other
systems then everyone can of course change/update the patch. It's open
source

As the patch will become obsolete with the next eggdrop version (in 2 years?
) I've decided not to put any more effort on it. As I said: It works
perfectly fine for me - I can live with it until eggdrop natively supports
SSL.
And here I have to clarify the "in 2 years" remark is not a dig at the pace of eggdrop development, but a little joke in response to a comment I made about the regular timing of his patches. The perils of playing the go-between Rootie can sign up and speak for himself if he has anything to add.

I'm not trying to attack Rootie personally, it's good that he shared his work with the others. But if it has serious problems, I have to say it, can't keep silence about this. Would it make sense if I feel offended when people find bugs in eggdrop?

Statistics: Posted by pseudo — Mon Aug 23, 2010 4:56 am

Eggdrop1.6.20rc1 and SSL

2010-08-23T05:10:15-04:00

This guy obviously doesn't understand how autotools and autoconf in particular work. Don't blame this on us. The configure script isn't written manually, it's generated by the input templates. You don't edit it, don't patch it, don't do anything to it. You edit it's source files (configure.ac and aclocal.m4 for eggdrop) and run autoconf, which by it's sole purpose will create a completely new file, overwriting any existing old one. Now, since the end user shouldn't have to run or even install autoconf, you distribute the ready file in your patch, in the form of a diff to the old one.

I don't use this patch and actually discourage it's usage, but from a brief look at the new version, the crash-causing problem with the symbols lookup table hasn't been solved. No need to look further.
Completely useless comment!

O'rly? My comment is useless and your rant isn't? Let's take the facts: the patch for 1.6.20 has serious flaws, which I've pointed out. People do report issues both here in the forum and on IRC support channels. Often these people don't even mention the patch and blame eggdrop itself. So we (the devs) have to check their bugreports only to find that the cause is yet another bug in the ssl patch.
It's naive to believe that since you in particular have no problems, it will work flawlessly for other people. In my 'useless' comment, I pointed out that the most serious bug of the patch stays unresolved. It does crash the bot in many situations. If it worked for you, maybe it would be more useful to stay silent and enjoy using it, wouldn't it? As in difference from you, I've put some effort investigating users' issues with the patch, so I definitely have the grounds to write these comments.

Feel free to correct his patch if you want. Feel free to make a new SSL patch if you want.

Guess what? That's what I've already done. In less than a month 1.8.0 CVS will have complete SSL support. Now I understand the need for a patch before official support is ready, but it's poor quality and has issues. What I'm doing is shedding some light on what are the problems, so why are you even complaining??

But don't blame Rootie for his effort in lifting code.

Sorry, it was not me blaming anybody, it's him blaming us (eggdrop devs) for his own ignorance:

The main problem is that autoconf - when applied on a clean eggdrop source - already creates a completely different configure file (unless I made something wrong...). Blame the devs for that Wink

If anybody is feeling offended by people pointing out his mistakes, it's his own fault.

Statistics: Posted by pseudo — Mon Aug 23, 2010 4:51 am

Eggdrop1.6.20rc1 and SSL

2010-08-22T20:16:28-04:00

It's a time worn argument whether to release something that's been hacked together in a far from ideal way, or better to have nothing until someone who really knows what they're doing creates something that more people would consider up-to-standard. Users tend to favour the former and developers the latter

Rootie didn't specifically ask to quote this part of his e-mail but I should add it for context:

You can post the text above in the forum to inform users that there's a
"silent update" on the patch that might fix their problems. Actually I
lifted this patch to the newest versions for my private use only. The
patches you get from me work fine on my shell. If it doesn't work on other
systems then everyone can of course change/update the patch. It's open
source

As the patch will become obsolete with the next eggdrop version (in 2 years?
) I've decided not to put any more effort on it. As I said: It works
perfectly fine for me - I can live with it until eggdrop natively supports
SSL.

And here I have to clarify the "in 2 years" remark is not a dig at the pace of eggdrop development, but a little joke in response to a comment I made about the regular timing of his patches. The perils of playing the go-between Rootie can sign up and speak for himself if he has anything to add.

Statistics: Posted by slennox — Sun Aug 22, 2010 8:16 pm

Eggdrop1.6.20rc1 and SSL

2010-08-22T10:22:52-04:00

finally that autoconf issue hits me ... I've been aware of that issue
before. The main problem is that autoconf - when applied on a clean eggdrop
source - already creates a completely different configure file (unless I
made something wrong...). Blame the devs for that
This guy obviously doesn't understand how autotools and autoconf in particular work. Don't blame this on us. The configure script isn't written manually, it's generated by the input templates. You don't edit it, don't patch it, don't do anything to it. You edit it's source files (configure.ac and aclocal.m4 for eggdrop) and run autoconf, which by it's sole purpose will create a completely new file, overwriting any existing old one. Now, since the end user shouldn't have to run or even install autoconf, you distribute the ready file in your patch, in the form of a diff to the old one.

I don't use this patch and actually discourage it's usage, but from a brief look at the new version, the crash-causing problem with the symbols lookup table hasn't been solved. No need to look further.

Completely useless comment! This guy keeps porting the SSL patch to the most recent version of Eggdrop and shares it with the community for free. I've been using his SSL patches for years and I don't have any problems even with the newest version. Feel free to correct his patch if you want. Feel free to make a new SSL patch if you want. But don't blame Rootie for his effort in lifting code. As long as it works on HIS system he's ok with it and he gives his final patch to us so we can use SSL, too.

Just my 2 cents,
fabius

Statistics: Posted by fabius — Sun Aug 22, 2010 10:22 am