run spamfilters against NICK #330
Conversation
|
This should also apply to the initial nick, otherwise one could still register with the bad nick. Alarm consumers would need to handle that situation, though. |
jesopo
force-pushed
the
jess/filter-nick
branch
from
3c68c0c
to
abc23d5
Compare
extensions/filter.c
Outdated
| } | ||
| if (r & ACT_ALARM) { | ||
| sendto_realops_snomask(SNO_GENERAL, L_ALL | L_NETWIDE, | ||
| "FILTER:REGISTER: %s@%s", |
There was a problem hiding this comment.
this is my initial solution for how alarm consumers are going to handle this case: slightly different snote. bikeshed on the format please
| struct Client *s = data->client; | ||
| struct sockaddr *addr = (void *)&s->localClient->ip; | ||
|
|
||
| if(find_conf_by_address( |
There was a problem hiding this comment.
we can't make people immune from this by them being an oper, obviously, and this is the only alternative that came to mind
There was a problem hiding this comment.
or maybe we just treat it like a RESV. you have to connect first and then switch your nick
jesopo
force-pushed
the
jess/filter-nick
branch
from
dca7d6e
to
7d5e73d
Compare
|
i plan to do a second PR after this that runs spamfilters against |
this isn't perfect because it'll format as
(note the
:) so maybe I should beat upmatch_message'ssnprintfa bit