Skip to content
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

Clearly marking oper-only output so there's no doubt about what is public #141

Open
rscs opened this issue May 9, 2020 · 2 comments
Open

Comments

@rscs
Copy link
Contributor

rscs commented May 9, 2020

Use a start/end numeric or some other indicator for oper-only info, like +b on a channel that uses XFLAGS to hide the mode list. This way an oper can easily tell they're seeing into that is meant to be oper-only.

@eaescob
Copy link
Contributor

eaescob commented May 13, 2020

Do you have a list of messages that need to be marked as oper only?

@jfcantu
Copy link
Member

jfcantu commented Jul 3, 2020

wow, which idiot of an IRCop prompted this issue? 🤔

Possibly (probably?) incomplete list:

  • RPL_WHOISACTUALLY:
    if(IsUmodeH(acptr) && (sptr==acptr || IsAnOper(sptr)))
  • RPL_WHOISTEXT for squelched users:
    if(IsAnOper(sptr) && IsSquelch(acptr))
  • +I/+e/+b lists when XFLAG_HIDE_MODE_LISTS is set on the channel:
    if((chptr->xflags & XFLAG_HIDE_MODE_LISTS) && !IsAnOper(sptr) && !is_chan_op(sptr,chptr))
  • whois replies for services tags which have a umode:
    if(*servicestag->tag && (!servicestag->umode || (sptr->umode & servicestag->umode))) sendto_one(sptr, ":%s %d %s %s :%s", me.name, servicestag->raw, parv[0], name, servicestag->tag);

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

No branches or pull requests

3 participants