Just had an interesting chat with a friend who use Amazon Web Service - AWS - shell to house his eggdrop bot.
And he was trying to make that bot connect to Freenode.
Freenode balked, wouldn't let his bot connect, saying that an SASL connection was required.
So we looked around, and found some info online, etc.
I don't have an AWS account, but I tried it on a bot of mine that is on Freenode. Works fine. Bot logs in and ids with Nickserv.
Here's what I did:
1.) Go here: https://nullroute.eu.org/~grawity/journal-2013.html
and scroll down, or text search and find: SASL authentication in Eggdrop
and read those three paragraphs.
Not absolutely necessary, but it helps.
2.) Go here: https://gist.github.com/grawity/4455067
Read some.
Then find two tcl scripts there:
https://gist.github.com/grawity/4455067 ... base64-tcl
and
https://gist.github.com/grawity/4455067#file-g_cap-tcl
On the right side of the page of each, click on the Raw button.
That opens another page, and it is plain text. I simply right clicked, got a pop up menu, chose Select All to highlight, and copied.
Then I went to shell, creating new text file with nano, and pasted.
Saved.
That's how I created each of those two .tcl files.
3.) Have a look at them.
One of them must be loaded before the other. Pay attention.
Also, one of them has a few lines of configuration. Actually, you must copy them over to your working eggdrop.conf. I simply pasted them just below the source lines that load the two scripts.
I edited only one line in this section : # password for PLAIN
You'll see.
Also, notice that the script uses $username ?
Go look in the main part of your working eggdrop.conf, and be sure it is set correctly.
That's it.
I .restarted bot, and watched. It logged on to Freenode, and did the SASL thing, and was id'd with NickServ. Worked first time.
I hope this helps somebody.