Skip to content
This repository has been archived by the owner on Jun 6, 2021. It is now read-only.

Account-tag capability support #164

Open
ivucica opened this issue Jun 4, 2019 · 1 comment
Open

Account-tag capability support #164

ivucica opened this issue Jun 4, 2019 · 1 comment

Comments

@ivucica
Copy link

ivucica commented Jun 4, 2019

Hi,

I'd like to (safely) authenticate certain Freenode users against a web service by having them provide a token to a bot through Freenode.

I'd only like to authenticate users that are logged into a nickserv account.

Harder way involves activating identify-msg, extended-join and account-notify, then using WHOX with the a and n fields, keeping track of accounts, and only allowing PRIVMSG from a user that's in a known channel that my bot is also a member of. I'm sure I'm missing a race condition somewhere.

Easy way to do this would be to activate the account-tag capability in my bot, then have the users PRIVMSG my bot with the token generated by the web service.

In this case, there would be no need for the bot to join any channels or to keep track of the user's account; if the Freenode message includes both the correct account and the token generated by my web service, the bot can tell the web service authentication has succeeded.

Would it be feasible to complement identify-msg with account-tag?

@ilbelkyr
Copy link
Contributor

We're definitely interested in implementing this, however it depends on implementing message tags in general per issue #170 first.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants