New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forward NICKDELAY as RESV to non-EUID servers #137

Closed
cooper opened this Issue Sep 22, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@cooper
Owner

cooper commented Sep 22, 2016

  • NICKDELAY: ratbox does not support a nick delay command, which is used by
    services to prevent users from switching back to a nickname immediately after
    services forced them to a "Guest" nick. When linking ratbox to services, RESV
    is used instead, but if ratbox reaches services indirectly via juno, it cannot
    understand the NICKDELAY command that is forwarded to it. There are plans to fix
    this by specially translating NICKDELAY to RESV for ratbox (or any server
    without EUID).

@cooper cooper added the ts6 label Sep 22, 2016

@cooper cooper added this to the v12 milestone Sep 22, 2016

@cooper

This comment has been minimized.

Owner

cooper commented Sep 22, 2016

Hmm, this would require a ban agent to send out RESVs, so it depends on #119 being addressed first

@cooper cooper modified the milestones: v12, v13 Sep 22, 2016

@cooper cooper closed this in 3e61097 Dec 28, 2016

cooper added a commit that referenced this issue Dec 28, 2016

12.31: added a hack to address #137 which looks for NickServ when we …
…have to use RESV instead of NICKDELAY. added outgoing non-ENCAP TS6 RESV command (for use with CLUSTER capab).
@cooper

This comment has been minimized.

Owner

cooper commented Dec 28, 2016

OK this is done. Lots of hacks. NICKDELAY may be forwarded as ENCAP RESV, RESV, or even BAN R (but probably not) to servers not supporting EUID. If a RESV command has to be used, juno will look for NickServ according to services:nickserv config key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment