kosmos/chef
kosmos
/
chef
8
3
Fork 0
Code Issues 37 Pull Requests 1 Projects 1 Activity

botka/hubot should connect to IRC using SASL #348

New Issue
Closed
opened 2021-10-23 09:35:44 +00:00 by raucao · 2 comments
raucao commented 2021-10-23 09:35:44 +00:00
Owner
Copy Link

After botka was banned by Libera.Chat for some reason, I improved the IRC config a little bit, but wasn't able to make SASL connections work. It looked to me like our version of node-irc has a bug in its SASL implementation, where the username ends up including additional characters.

Thus, when we can finally upgrade to the latest node-irc, we should make sure to connect using SASL from then on.

After botka was banned by Libera.Chat for some reason, I improved the IRC config a little bit, but wasn't able to make SASL connections work. It looked to me like our version of node-irc has a bug in its SASL implementation, where the username ends up including additional characters. Thus, when we can finally upgrade to the latest node-irc, we should make sure to connect using SASL from then on.
raucao added the
enhancement
 label 2021-10-23 09:35:44 +00:00
raucao changed title from botka/hubot should connect using SASL to botka/hubot should connect to IRC using SASL 2021-10-23 09:35:57 +00:00
raucao commented 2021-11-30 16:47:46 +00:00
Author
Owner
Copy Link

A potential fix has been submitted upstream:

https://github.com/nandub/hubot-irc/issues/181#issuecomment-979799394

A potential fix has been submitted upstream: https://github.com/nandub/hubot-irc/issues/181#issuecomment-979799394
raucao commented 2022-01-19 19:39:59 +00:00
Author
Owner
Copy Link

After testing the linked fix, and it also not working, I have ragequit this issue and recently configured botka to connect to Libera.Chat through a ZNC bouncer (which is using SASL, too). Not interested in looking into this further, since ZNC is just rock-solid.

After testing the linked fix, and it also not working, I have ragequit this issue and recently configured botka to [connect to Libera.Chat through a ZNC bouncer](https://gitea.kosmos.org/kosmos/chef/pulls/371) (which is using SASL, too). Not interested in looking into this further, since ZNC is just rock-solid.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
jammy_jellyfish
chore/replace_postgres_primary
chore/akkounts_configs
feature/libretranslate
feature/deploy_new_kredits_software
feature/jitsi-meet
chore/395-gitea_cron
chore/move_zerotier_controller
chore/upgrade_sockethub
chore/move_gitea_and_drone
feature/turn_ip_config
feature/103-chef_15
feature/chef_15
dev
Labels
Clear labels   
service
accounts
Kosmos Accounts

  
service
discourse
Kosmos Community Forums

  
service
drone-ci
Kosmos Drone CI

  
service
email
mail.kosmos.org

  
service
garage
S3-compatible object storage

  
service
gitea
Kosmos Gitea

  
service
ipfs
Kosmos IPFS

  
service
mastodon
kosmos.social

  
service
postgres
Database cluster

  
service
remotestorage
Portable data storage for the Web

  
service
wiki
Kosmos Wiki

  
service
xmpp
Kosmos Chat

  
bug

Something is not working

  
design

Graphic/visual design

  
dev environment

Config, builds, CI, deployment, etc.

  
docs

Documentation

  
duplicate

This issue or pull request already exists

  
enhancement

Improving existing functionality

  
feature

New functionality

  
good first issue

Dive in, and start contributing

  
idea

Something to consider

  
invalid

Not a bug

  
kredits-1

Small contribution

  
kredits-2

Medium contribution

  
kredits-3

Large contribution

  
on hold

Currently not actionable

  
ops

Manual IT ops activities

  
question

Looking for an answer

  
release
major

  
release
minor

  
release
patch

  
security

All your base are belong to us

  
ui/ux

User interface, process design, etc.

  
wontfix

This won't be fixed

No Label
service
accounts
service
discourse
service
drone-ci
service
email
service
garage
service
gitea
service
ipfs
service
mastodon
service
postgres
service
remotestorage
service
wiki
service
xmpp
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#348
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?