Tip of the day: Channel mode +f is a powerful anti-flood feature. It is also slightly complex. Enable it in your most important channels, and consider setting a default in set::modes-on-join.
|
Search results
Jump to navigation
Jump to search
Page title matches
- When you enable SASL, users can authenticate against their [[Services|services]] account early i ...rver is under attack and the [[Connthrottle]] protection is activated then SASL users are still allowed in.4 KB (628 words) - 17:30, 1 December 2022
- 42 bytes (4 words) - 10:32, 17 December 2018
Page text matches
- When you enable SASL, users can authenticate against their [[Services|services]] account early i ...rver is under attack and the [[Connthrottle]] protection is activated then SASL users are still allowed in.4 KB (628 words) - 17:30, 1 December 2022
- [11:56:08] -server.test.net- Please reconnect using SASL, or authenticate now by typing: /AUTH nick:password The user can then (re)configure [[SASL]] in their IRC client (which is the recommended method). They can also simp1 KB (195 words) - 09:59, 11 February 2024
- ...via [[Set block#set::authentication-prompt|authprompt]] that will ask non-SASL users to authenticate interactively by typing <code>/AUTH nickname:password2 KB (228 words) - 16:33, 6 April 2024
- ...lways get in, regardless of the set rate. Same for users who login using [[SASL]]. * SASL to bypass the restrictions.6 KB (644 words) - 08:03, 16 May 2022
- [11:56:08] -server.test.net- Please reconnect using SASL, or authenticate now by typing: /AUTH nick:password The user can then configure [[SASL]] in their IRC client, or they can simply type <code>/AUTH nickname:passwor3 KB (499 words) - 21:07, 20 June 2023
- ...and assume they all have a [[Services]] account and log in to that using [[SASL]]. After [[Rehashing the IRCd|rehashing the IRCd]], let a user connect and use [[SASL]] to identify to their [[Services]] account.5 KB (713 words) - 08:40, 31 May 2023
- ...pplied to users who are authenticated with [[Services]] (preferably with [[SASL]]).985 bytes (138 words) - 12:44, 18 September 2023
- ...account</code> will bypass KLINE and GLINE server bans if the user uses [[SASL]] to login to the account ''SomeAccount''.<br> ...ers with a [[Reputation score|reputation score]] below 24 that don't use [[SASL]] to identify to [[Services]]. Note that using [[Connthrottle]] may be a be3 KB (539 words) - 11:34, 26 July 2023
- ...s that can be used for masks, such as lists, negative matching, matching [[SASL]] users, certificate fingerprints, etc. ** Users identified to services via [[SASL]] with the account name <code>TrustedUser1</code> or <code>TrustedUser2</co6 KB (825 words) - 16:24, 18 May 2023
- ...ation { }]] instead, which still allows registered users in (users using [[SASL]]). Also note that banning countries in general is usually not really an ef1 KB (245 words) - 08:54, 9 September 2023
- * Allow services to send a couple of protocol messages in the unregistered / SASL stage. These are: CHGHOST, CHGIDENT and SREPLY ** This allows services to set the vhost on a user during SASL, so the user receives the vhost straight from the start, before all the aut9 KB (1,438 words) - 18:07, 3 July 2023
- ...ly require all I2P users to have a [[Services|services account]] and use [[SASL]]. reason "I2P users need to authenticate to their services account using SASL";6 KB (1,117 words) - 17:38, 23 December 2023
- ...ly require all Tor users to have a [[Services|services account]] and use [[SASL]]. reason "Tor users need to authenticate to their services account using SASL";7 KB (1,147 words) - 11:56, 15 April 2023
- ...ode>GLINE ~country:BD 0 :Too much spam from this country</code> or forcing SASL authentication for a country, eg: <code>GLINE %~country:BD 0 :Too much spam3 KB (463 words) - 14:06, 12 December 2021
- ...pplied to users who are authenticated with [[Services]] (preferably with [[SASL]]).3 KB (448 words) - 11:58, 2 January 2021
- ...pplied to users who are authenticated with [[Services]] (preferably with [[SASL]]):3 KB (517 words) - 13:10, 10 September 2023
- ...ode>GLINE ~country:BD 0 :Too much spam from this country</code> or forcing SASL authentication for a country, eg: <code>GLINE %~country:BD 0 :Too much spam4 KB (595 words) - 08:16, 31 May 2023
- ...~country:BD 0 :Mucho spam desde este País</code> o forzar la autenticación SASL para un país, Ej: <code>GLINE %~country:BD 0 :Mucho spam desde este País,3 KB (541 words) - 18:51, 12 December 2021
- !SASL !sasl16 KB (2,744 words) - 14:11, 13 December 2021
- ...ges per minute and allowing services users in during attacks if they use [[SASL]] (see [[#Connthrottle|Connthrottle]] later in this article). ...gister their nickname at [[Services]] and also suggest your users to use [[SASL]] for authentication.14 KB (2,362 words) - 11:06, 20 March 2023