]>
Commit | Line | Data |
---|---|---|
8a7d33db AB |
1 | User modes |
2 | ========== | |
2ae078d8 | 3 | |
4245facd AB |
4 | ``+a``, server administrator |
5 | ---------------------------- | |
2ae078d8 AB |
6 | |
7 | This vanity usermode is used to denote a server administrator in WHOIS | |
8 | output. All local “admin” privileges are independent of it, though | |
4245facd | 9 | services packages may grant extra privileges to ``+a`` users. |
2ae078d8 | 10 | |
4245facd AB |
11 | ``+D``, deaf |
12 | ------------ | |
2ae078d8 | 13 | |
4245facd AB |
14 | .. note:: This is a user umode, which anybody can set. It is not |
15 | specific to operators. | |
2ae078d8 | 16 | |
4245facd | 17 | Users with the ``+D`` umode set will not receive messages sent to channels. |
2ae078d8 AB |
18 | Joins, parts, topic changes, mode changes, etc are received as normal, |
19 | as are private messages. | |
20 | ||
4245facd | 21 | Support of this umode is indicated by the ``DEAF`` token in ``RPL_ISUPPORT`` |
2ae078d8 AB |
22 | (005); the parameter indicates the letter of the umode. Note that |
23 | several common IRCD implementations have an umode like this (typically | |
4245facd | 24 | ``+d``) but do not have the token in 005. |
2ae078d8 | 25 | |
4245facd AB |
26 | ``+g``, Caller ID |
27 | ----------------- | |
2ae078d8 | 28 | |
4245facd AB |
29 | .. note:: This is a user umode, which anybody can set. It is not |
30 | specific to operators. | |
2ae078d8 | 31 | |
4245facd AB |
32 | Users with the ``+g`` umode set will only receive private messages |
33 | from users on a session-defined whitelist, defined by the ``/accept`` | |
34 | command. If a user who is not on the whitelist attempts to send a | |
35 | private message, the target user will receive a rate-limited notice | |
36 | saying that the user wishes to speak to them. | |
2ae078d8 AB |
37 | |
38 | Network operators are not affected by the callerid whitelist system in | |
39 | the event that they need to speak to users who have it enabled. | |
40 | ||
4245facd AB |
41 | Support of this umode is indicated by the ``CALLERID`` token in |
42 | ``RPL_ISUPPORT`` (005); the optional parameter indicates the letter of | |
43 | the umode, otherwise ``+g``. | |
2ae078d8 | 44 | |
4245facd AB |
45 | ``+i``, invisible |
46 | ----------------- | |
2ae078d8 | 47 | |
4245facd AB |
48 | .. note:: This is a user umode, which anybody can set. It is not |
49 | specific to operators. | |
2ae078d8 | 50 | |
b44a51d4 | 51 | Invisible users do not show up in ``WHO`` and ``NAMES`` unless you can see them. |
2ae078d8 | 52 | |
4245facd AB |
53 | ``+l``, receive locops |
54 | ---------------------- | |
2ae078d8 | 55 | |
b44a51d4 | 56 | ``LOCOPS`` is a version of ``OPERWALL`` that is sent to opers on a single server |
2ae078d8 AB |
57 | only. With cluster{} and shared{} blocks they can optionally be |
58 | propagated further. | |
59 | ||
b44a51d4 | 60 | Unlike ``OPERWALL``, any oper can send and receive ``LOCOPS``. |
2ae078d8 | 61 | |
4245facd AB |
62 | ``+o``, operator |
63 | ---------------- | |
2ae078d8 AB |
64 | |
65 | This indicates global operator status. | |
66 | ||
4245facd AB |
67 | ``+Q``, disable forwarding |
68 | -------------------------- | |
2ae078d8 | 69 | |
4245facd AB |
70 | .. note:: This is a user umode, which anybody can set. It is not |
71 | specific to operators. | |
2ae078d8 AB |
72 | |
73 | This umode prevents you from being affected by channel forwarding. If | |
74 | enabled on a channel, channel forwarding sends you to another channel if | |
4245facd | 75 | you could not join. See channel mode ``+f`` for more information. |
2ae078d8 | 76 | |
4245facd AB |
77 | ``+R``, reject messages from unauthenticated users |
78 | -------------------------------------------------- | |
2ae078d8 | 79 | |
4245facd AB |
80 | .. note:: This is a user umode, which anybody can set. It is not |
81 | specific to operators. | |
2ae078d8 | 82 | |
4245facd | 83 | If a user has the ``+R`` umode set, then any users who are not authenticated |
2ae078d8 | 84 | will receive an error message if they attempt to send a private message |
4245facd | 85 | or notice to the ``+R`` user. |
2ae078d8 | 86 | |
4245facd | 87 | Opers and accepted users (like in ``+g``) are exempt. Unlike ``+g``, the target |
2ae078d8 AB |
88 | user is not notified of failed messages. |
89 | ||
4245facd AB |
90 | ``+s``, receive server notices |
91 | ------------------------------ | |
2ae078d8 AB |
92 | |
93 | This umode allows an oper to receive server notices. The requested types | |
94 | of server notices are specified as a parameter (“snomask”) to this | |
95 | umode. | |
96 | ||
4245facd AB |
97 | ``+S``, network service |
98 | ----------------------- | |
2ae078d8 | 99 | |
4245facd AB |
100 | .. note:: This umode can only be set by servers named in a service{} |
101 | block. | |
2ae078d8 AB |
102 | |
103 | This umode grants various features useful for services. For example, | |
104 | clients with this umode cannot be kicked or deopped on channels, can | |
b44a51d4 AB |
105 | send to any channel, do not show channels in ``WHOIS``, can be the target of |
106 | services aliases and do not appear in ``/stats p``. No server notices are | |
2ae078d8 | 107 | sent for hostname changes by services clients; server notices about |
4245facd | 108 | kills are sent to snomask ``+k`` instead of ``+s``. |
2ae078d8 AB |
109 | |
110 | The exact effects of this umode are variable; no user or oper on an | |
111 | actual charybdis server can set it. | |
112 | ||
4245facd AB |
113 | ``+w``, receive wallops |
114 | ----------------------- | |
2ae078d8 | 115 | |
4245facd AB |
116 | .. note:: This is a user umode, which anybody can set. It is not |
117 | specific to operators. | |
2ae078d8 | 118 | |
b44a51d4 AB |
119 | Users with the ``+w`` umode set will receive ``WALLOPS`` messages sent by opers. |
120 | Opers with ``+w`` additionally receive ``WALLOPS`` sent by servers (e.g. remote | |
121 | ``CONNECT``, remote ``SQUIT``, various severe misconfigurations, many services | |
2ae078d8 AB |
122 | packages). |
123 | ||
4245facd AB |
124 | ``+z``, receive operwall |
125 | ------------------------ | |
2ae078d8 | 126 | |
b44a51d4 AB |
127 | ``OPERWALL`` differs from ``WALLOPS`` in that the ability to receive such |
128 | messages is restricted. Opers with ``+z`` set will receive ``OPERWALL`` | |
2ae078d8 AB |
129 | messages. |
130 | ||
4245facd AB |
131 | ``+Z``, SSL user |
132 | ---------------- | |
2ae078d8 AB |
133 | |
134 | This umode is set on clients connected via SSL/TLS. It cannot be set or | |
135 | unset after initial connection. | |
136 | ||
137 | Snomask usage | |
0f04574d | 138 | ============= |
2ae078d8 | 139 | |
b44a51d4 AB |
140 | Usage is as follows:: |
141 | ||
142 | MODE nick +s +/-flags | |
2ae078d8 | 143 | |
2ae078d8 AB |
144 | To set snomasks. |
145 | ||
b44a51d4 AB |
146 | :: |
147 | ||
148 | MODE nick -s | |
149 | ||
2ae078d8 AB |
150 | To clear all snomasks. |
151 | ||
4245facd | 152 | Umode ``+s`` will be set if at least one snomask is set. |
2ae078d8 | 153 | |
4245facd | 154 | Umode ``+s`` is oper only by default, but even if you allow nonopers to set |
2ae078d8 AB |
155 | it, they will not get any server notices. |
156 | ||
157 | Meanings of server notice masks | |
0f04574d | 158 | =============================== |
2ae078d8 | 159 | |
4245facd AB |
160 | ``+b``, bot warnings |
161 | -------------------- | |
2ae078d8 | 162 | |
4245facd | 163 | Opers with the ``+b`` snomask set will receive warning messages from the |
2ae078d8 AB |
164 | server when potential flooders and spambots are detected. |
165 | ||
4245facd AB |
166 | ``+c``, client connections |
167 | -------------------------- | |
2ae078d8 | 168 | |
4245facd | 169 | Opers who have the ``+c`` snomask set will receive server notices when |
2ae078d8 AB |
170 | clients attach to the local server. |
171 | ||
4245facd AB |
172 | ``+C``, extended client connection notices |
173 | ------------------------------------------ | |
2ae078d8 | 174 | |
4245facd AB |
175 | Opers who have the ``+C`` snomask set will receive server notices when |
176 | clients attach to the local server. Unlike the ``+c`` snomask, the | |
2ae078d8 | 177 | information is displayed in a format intended to be parsed by scripts, |
b44a51d4 | 178 | and includes the two unused fields of the ``USER`` command. |
2ae078d8 | 179 | |
4245facd AB |
180 | ``+d``, debug |
181 | ------------- | |
2ae078d8 | 182 | |
4245facd | 183 | The ``+d`` snomask provides opers extra information which may be of interest |
2ae078d8 AB |
184 | to debuggers. It will also cause the user to receive server notices if |
185 | certain assertions fail inside the server. Its precise meaning is | |
186 | variable. Do not depend on the effects of this snomask as they can and | |
187 | will change without notice in later revisions. | |
188 | ||
4245facd AB |
189 | ``+f``, full warning |
190 | -------------------- | |
2ae078d8 | 191 | |
4245facd | 192 | Opers with the ``+f`` snomask set will receive notices when a user |
2ae078d8 AB |
193 | connection is denied because a connection limit is exceeded (one of the |
194 | limits in a class{} block, or the total per-server limit settable with | |
b44a51d4 | 195 | ``/quote set max``). |
2ae078d8 | 196 | |
4245facd AB |
197 | ``+F``, far client connection notices |
198 | ------------------------------------- | |
2ae078d8 | 199 | |
4245facd AB |
200 | .. note:: This snomask is only available if the ``sno_farconnect.so`` |
201 | extension is loaded. | |
2ae078d8 | 202 | |
4245facd AB |
203 | Opers with ``+F`` receive server notices when clients connect or disconnect |
204 | on other servers. The notices have the same format as those from the ``+c`` | |
2ae078d8 AB |
205 | snomask, except that the class is ? and the source server of the notice |
206 | is the server the user is/was on. | |
207 | ||
208 | No notices are generated for netsplits and netjoins. Hence, these | |
209 | notices cannot be used to keep track of all clients on the network. | |
210 | ||
4245facd | 211 | There is no far equivalent of the ``+C`` snomask. |
2ae078d8 | 212 | |
4245facd AB |
213 | ``+k``, server kill notices |
214 | --------------------------- | |
2ae078d8 | 215 | |
4245facd | 216 | Opers with the ``+k`` snomask set will receive server notices when services |
2ae078d8 | 217 | kill users and when other servers kill and save (forced nick change to |
4245facd | 218 | UID) users. Kills and saves by this server are on ``+d`` or ``+s``. |
2ae078d8 | 219 | |
4245facd AB |
220 | ``+n``, nick change notices |
221 | --------------------------- | |
2ae078d8 | 222 | |
4245facd | 223 | An oper with ``+n`` set will receive a server notice every time a local user |
2ae078d8 AB |
224 | changes their nick, giving the old and new nicks. This is mostly useful |
225 | for bots that track all users on a single server. | |
226 | ||
4245facd AB |
227 | ``+r``, notices on name rejections |
228 | ---------------------------------- | |
2ae078d8 AB |
229 | |
230 | Opers with this snomask set will receive a server notice when somebody | |
231 | tries to use an invalid username, or if a dumb HTTP proxy tries to | |
232 | connect. | |
233 | ||
4245facd AB |
234 | ``+s``, generic server notices |
235 | ------------------------------ | |
2ae078d8 AB |
236 | |
237 | This snomask allows an oper to receive generic server notices. This | |
238 | includes kills from opers (except services). | |
239 | ||
4245facd AB |
240 | ``+u``, unauthorized connections |
241 | -------------------------------- | |
2ae078d8 AB |
242 | |
243 | This snomask allows an oper to see when users try to connect who do not | |
244 | have an available auth{} block. | |
245 | ||
4245facd AB |
246 | ``+W``, whois notifications |
247 | --------------------------- | |
2ae078d8 | 248 | |
4245facd AB |
249 | .. note:: This snomask is only available if the ``sno_whois.so`` |
250 | extension is loaded. | |
2ae078d8 | 251 | |
b44a51d4 | 252 | Opers with ``+W`` receive notices when a ``WHOIS`` is executed on them on their |
2ae078d8 AB |
253 | server (showing idle time). |
254 | ||
4245facd AB |
255 | ``+x``, extra routing notices |
256 | ----------------------------- | |
2ae078d8 | 257 | |
4245facd | 258 | Opers who have the ``+x`` snomask set will get notices about servers |
2ae078d8 AB |
259 | connecting and disconnecting on the whole network. This includes all |
260 | servers connected behind the affected link. This can get rather noisy | |
261 | but is useful for keeping track of all linked servers. | |
262 | ||
4245facd AB |
263 | ``+y``, spy |
264 | ----------- | |
2ae078d8 | 265 | |
b44a51d4 | 266 | Opers with ``+y`` receive notices when users try to join ``RESV``'ed (“juped”) |
2ae078d8 AB |
267 | channels. Additionally, if certain extension modules are loaded, they |
268 | will receive notices when special commands are used. | |
269 | ||
4245facd AB |
270 | ``+Z``, operspy notices |
271 | ----------------------- | |
2ae078d8 | 272 | |
4245facd | 273 | Opers with ``+Z`` receive notices whenever an oper anywhere on the network |
2ae078d8 AB |
274 | uses operspy. |
275 | ||
276 | This snomask can be configured to be only effective for admins. |