Page MenuHomePhabricator

logmsgbot auth issues
Closed, ResolvedPublic


Followup from T276299 where logmsgbot had troubles reconnecting to freenode:

- pontoon was connecting without password as logmsgbot, and given the nick has no enforce on, it will just lie around, causing tcpircbot to be unable to connect
- this also caused problems with freenode's spam protection so even after ghosting the user, we had issues coming from that
- any attempt to !log while the bot is reconnecting (it can take up to 2 minutes) will crash the bot.

Event Timeline

I wonder if it would be worth it not explicitly setting the username in the role/profile, but setting it VIA hiera or something to prevent accidental usage of “logmsgbot”.

Agreed that's something we should do in addition to the nick enforcing (as anyone can log in with logmsgbot anyways)

lmata triaged this task as Medium priority.Mar 8 2021, 4:32 PM

Mentioned in SAL (#wikimedia-operations) [2021-03-16T08:18:53Z] <godog> enable nick enforcing for logmsgbot - T276303

colewhite claimed this task.
colewhite subscribed.

Nick enforcement seems enabled.