Please add support for SASL authentication over IRC
I would really love to switch to Quassel. However, the lack of SASL authentication support makes me unable to do so.
I tried to write a plugin adding support for it, but discovered that there are interfaces implemented.
If you need any help understanding the SASL implementation, let me know. There is code to implement SASL PLAIN in Conspire, at http://hg.atheme.org/conspire/conspire/file/tip/src/common/sasl.c which may be helpful.
Note that freenode has recently implemented SASL on their network, so there are real networks out there using this specification.
Infact, it is required in order to use TOR now.
#1 Updated by nenolod about 13 years ago
A detailed spec is available at http://hg.atheme.org/atheme/atheme/file/120dcbec1965/doc/SASL
#2 Updated by stitch about 13 years ago
- File quassel-sasl.patch quassel-sasl.patch added
I've created a patch which introduces SASL support. It only supports SASL PLAIN. I have also updated the DB schemas however I'm not 100% sure about any migration, so please look at that (and advise where I have went wrong)
#3 Updated by nenolod about 13 years ago
<al> in a nutshell: the sqlitestorage.cpp changes need to be applied to postgresqlstorage.cpp too i think
#4 Updated by stitch about 13 years ago
- File quassel-sasl.diff quassel-sasl.diff added
I've revised this patch, the database schema's should be correct, and the postgrestorage.cpp was modified with the changes.
#5 Updated by dalbers about 13 years ago
- Status changed from New to Resolved
- Assignee set to dalbers
- Target version set to 0.6.0
- % Done changed from 0 to 100
Fixed as of cf721fb75a7525b03c0086f98314b828f5322001
#6 Updated by nutam11 about 3 years ago
So, guys, I would like to tell that your employee portal is the difference then the customer cause it is full of security to keep success and safe your profile data.