aboutsummaryrefslogtreecommitdiffstats
path: root/modules
Commit message (Expand)AuthorAgeFilesLines
* Update modules/m_who.c•••Co-authored-by: Doug Freed <dwfreed@mtu.edu> jess/split-operspyGravatar Jess Porter2022-06-101-1/+1
* tentatively switch m_whois to oper:spy_channelGravatar jesopo2022-06-101-1/+1
* i don't like implicit operspyGravatar jesopo2022-06-101-5/+0
* switch m_who to use new oper:spy variantsGravatar jesopo2022-06-101-1/+2
* split oper:spy in to oper:spy_user and oper:spy_channelGravatar jesopo2022-06-106-7/+7
* don't truncate operspy WHOGravatar Jess Porter2022-06-101-2/+6
* Add description parameter to auth blocks (#327)Gravatar Eric Mertens2022-04-142-6/+7
* Apply cmode C to replies (#328)Gravatar Eric Mertens2022-04-141-2/+4
* Make opers talking through +g controllable by user mode +M (#275)•••Times out after 30 minutes, and adds oper:always_message privilege for bots and services to always talk through +gGravatar Stephen Bennett2022-04-121-29/+203
* m_list: fail on invalid parameters•••Loose port of 6ea60b2297948211925e22bd1f284179d680b4ae. I've chosen to reduce indentation where it's convenient, and I'm allowing >-[0-9] as a way of specifying a minimum of 0 because... I don't know, it just seems neater to me. Gravatar Ed Kellett2021-10-201-25/+37
* m_list: Treat valid names with wildcards as masks•••* and ? are valid characters for channel names on IRC, and ELIST M gives no way to distinguish between `LIST #foo-*` that's meant to search for channels beginning `#foo-` and `LIST #foo-*` that's meant to list one channel named literally `#foo-*`. In order to deal with this, we will always assume a name with wildcards is a mask. If it's also a channel name, that will be listed first. Gravatar Ed Kellett2021-10-191-2/+10
* Support *mask* and !*mask* in LISTGravatar Ed Kellett2021-10-191-2/+23
* m_names: use ITER_COMM_CHANNELSGravatar Ed Kellett2021-10-171-7/+7
* Send RPL_ENDOFTRACE on local /etraceGravatar Ryan Schmidt2021-09-231-0/+3
* hook_fn casts were hiding UB (#265)Gravatar Eric Mertens2021-08-199-44/+55
* Stop announcing SASL cap changes on services split/join (#263)Gravatar Eric Mertens2021-08-151-73/+1
* ERR_USERONCHANNEL when following a forward is missing a paramGravatar jesopo2021-08-151-0/+4
* Remove Windows supportGravatar jailbird7772021-07-302-5/+0
* Create configurations for user-facing messages within registration (#238)Gravatar Melissa Draper2021-07-291-0/+40
* Create configurable client rejection message for SASL only (#236)Gravatar Melissa Draper2021-07-291-0/+5
* modules/core/m_message.c: align comments about idle time (#252)Gravatar Aaron Jones2021-07-181-4/+3
* m_services: delete nick delay on RSFNCGravatar Doug Freed2021-07-161-0/+7
* kick,remove: don't confuse source and target membershipGravatar Ed Kellett2021-07-131-8/+8
* m_dline: make the private reason privateGravatar Ed Kellett2021-07-131-1/+2
* um_regonlymsg: copy auto-accept logic from +gGravatar Ed Kellett2021-07-101-0/+41
* Remove ziplinks (#218)Gravatar Ariadne Conill2021-06-261-34/+0
* um_callerid: Only people can have common channelsGravatar Ed Kellett2021-06-242-3/+5
* m_userhost: hide user's own IP if iline spoofedGravatar Ed Kellett2021-06-131-8/+2
* Manage IsDynSpoof when effecting a (post-reg) SIGNONGravatar Ed Kellett2021-06-081-0/+5
* Use MayHavePrivilege for oper:messageGravatar Ed Kellett2021-06-081-1/+1
* Keep propagated bans in a dictionary, not a listGravatar Ed Kellett2021-06-085-28/+22
* modules/m_sasl.c: use IsSecure() instead of IsSSL()•••Further to our implementation of the concept of "secure origins", we can indicate to services that the client is connected securely, rather than just that the client is using TLS. For example, connections from the local host (from the IRCd's perspective) can be considered secure against eavesdropping. Allow this to factor into services' decision on whether to allow an SASL negotiation or not. Atheme currently assumes this means the client is using TLS, but I have changed that in atheme/atheme@412d50103c1d8c2a Gravatar Aaron Jones2021-06-081-1/+1
* m_whois: show services even if they lack opernamesGravatar Ed Kellett2021-06-051-7/+11
* m_whois: put opername/privset in RPL_WHOISOPERATOR•••Show just the opername if you're an oper the target is not hidden from and you don't have oper:privs. close #100 Gravatar Ed Kellett2021-06-051-17/+24
* Allow privset-less OPER burstingGravatar Ed Kellett2021-06-051-14/+22
* m_oper: receive ircd-seven-style opernamesGravatar Ed Kellett2021-06-051-1/+15
* m_invite: send message tags (#173)Gravatar megubyte2021-06-051-3/+1
* Mailmap and copyright update for AriadneGravatar Ariadne Conill2021-06-0110-10/+10
* Allow temporary K-lines to extend shorter ones (#142)•••* Temp K-lines may extend shorter temp K-lines * /unkline removes multiple matching K-lines * K-lines remove any temp K-lines they're replacingGravatar Ed Kellett2021-04-271-35/+82
* Add channel::ip_bans_through_vhostGravatar Ed Kellett2021-04-261-0/+5
* add separate priv (oper:message) for walking over CALLERID (umode +g) (#152)Gravatar jess2021-04-261-1/+1
* Add an s2s cap for ECHO (#141)Gravatar Ed Kellett2021-04-201-1/+11
* make VERSION not include sid (#118)Gravatar David Schultz2021-04-101-4/+2
* send account-notify messages to subject connection tooGravatar jesopo2021-04-101-1/+1
* Make privilegeset_privs more constGravatar Ed Kellett2021-03-011-1/+1
* privilege: factor out a null checkGravatar Ed Kellett2021-03-011-1/+1
* Track and inform modules of privset changesGravatar Ed Kellett2021-03-012-22/+25
* wallops: require new oper:wallops right (#110)•••Split oper:wallops right from oper:mass_notice. Update documentation and examples to grant oper:wallops everywhere oper:mass_notice was granted. closes #103Gravatar Taavi Väänänen2021-01-281-2/+2
* /accept list should track nick changes when you share channels (#96)•••* move has_common_channel to s_user.c * don't remove clients from /accept on NICK when there's a common channel Co-authored-by: Ed Kellett <e@kellett.im>Gravatar jess2021-01-242-19/+17
* chmode: end the grace period more intelligently (#84)•••We were ending the flood grace period for any channel mode command other than `MODE #foo [bq]` by means of a hardcoded check. I've moved that to after we parse the mode string, so we can correctly identify all requests to change modes and end the grace period on exactly those. It would have been entirely possible to move the check even further down and flood_endgrace on only mode commands that *actually* change modes, but I don't like the idea of making it sensitive to external conditions.Gravatar Ed Kellett2020-11-301-7/+0