Xertion Wiki - User contributions [en]

User:Kaishiro

2022-09-06T11:30:49Z

Kaishiro:

{{Userboxtop}}
{{NetOp}}
{{UserXBL|x Kaishiro x}}
{{UserPSN|Kaishirox}}
{{UserWoW}}
{{UserDiablo3}}
{{UserDCUO}}
{{SupportLinux}}
{{AntiApple}}
{{Userboxbottom}}

Kaishiro (born December 2, 1988) is a network owner of Xertion, which launched February of 2011.

Making his internet debut at an early age of seven, Kaishiro did not know that he would be destined for great things. He now has two daughters and a decent job.

XDCC Commands

2022-04-03T03:13:25Z

Kaishiro: Making note of exception

* '''HELP'''
** -- <code>/msg [botname] XDCC HELP</code> -- Shows the supported user commands on the bot.
* '''LIST'''
** -- <code>/msg [botname] XDCC LIST</code> -- List all available packs on the bot.
** -- <code>/msg [botname] XDCC LIST [a]-[b]</code> -- Lists packs on the bot with numbers between a and b.
* '''STOP'''
** -- <code>/msg [botname] STOP</code> -- Stops [botname] from listing packs.
* '''SEND LIST'''
** -- <code>/msg [botname] XDCC SEND -1</code>
** -- <code>/msg [botname] XDCC SEND LIST</code> -- All 3 of these send you the bot's packlist as a text file, via DCC.
** -- <code>/msg [botname] XDCC GET LIST</code>
* '''SEARCH'''
** -- <code>/msg [botname] XDCC SEARCH '''''search terms'''''</code> -- Gives a list of packs matching search terms.
* '''INFO'''
** -- <code>/msg [botname] XDCC INFO [x]</code> -- Gives info on pack with number x, including a description, filesize, amount of times it's been requested, md5sum, CRC32 and more.
* '''SEND'''
** -- <code>/msg [botname] XDCC SEND [x]</code> -- Request pack with number x from the bot.
** -- <code>/msg [botname] XDCC GET [x]</code> -- Request pack with number x from the bot.
** -- <code>/msg [botname] XDCC SEND [x] [password]</code> -- Request passworded pack with number x and password "password" from the bot.
** -- <code>/msg [botname] XDCC GET [x] [password]</code> -- Request passworded pack with number x and password "password" from the bot.
* '''BATCH'''
** -- <code>/msg [botname] XDCC BATCH [a]-[b]</code> -- Request packs with numbers a to b, including a and b, from the bot.
** -- <code>/msg [botname] XDCC BATCH [a],[b],[c]</code> -- Request packs with numbers [a],[b] and [c] from the bot.
** -- <code>/msg [botname] XDCC BATCH [a]-[b] [password]</code> -- Request passworded packs with numbers a to b, including a and b, with password "password" from the bot.
** -- <code>/msg [botname] XDCC BATCH [a],[b],[c] [password]</code> -- Request packs with numbers [a],[b] and [c], with password "password" from the bot.
** -- <code>/msg [botname] XDCC BATCH [a],[b],[c]-[d]</code> -- Request packs with numbers a, b and c to d from the bot. (i.e, you can combine the two methods of saying which set of packs you want)
* '''QUEUE'''
** -- <code>/msg [botname] XDCC QUEUE</code> -- Shows the current packs you have queued to download from the bot, and the estimated time you have to wait.
* '''REMOVE'''
** -- <code>/msg [botname] XDCC REMOVE</code> - Remove all your currently queued packs from the queue on the bot.
** -- <code> /msg [botname] XDCC REMOVE ALL</code> - Remove all your currently queued packs from the queue on the bot.
** -- <code>/msg [botname] XDCC REMOVE [x]</code> - Remove pack with number x from the queue on the bot.
* '''CANCEL'''
** -- <code>/msg [botname] XDCC CANCEL</code> -- Cancel the currently running transfer from the bot.

Note:
* Do not include any square brackets '''''anywhere''''' when you input these commands. (Exception if brackets are in the botname)
* Replace [botname] with the name of the bot you wish to download from.

Return to [[Main Page]]

[[Category:Commands]]

Staff

2020-05-02T06:23:12Z

Kaishiro: added email

Channel Modes

2020-04-22T18:46:03Z

Kaishiro:

==How to change a channel mode==
To change a mode on a channel, use the <code>/mode</code> command with the channel mode you wish to change. For example:

To set +c on the channel #example:

<code>/mode #example +c</code>

Or to unset it:

<code>/mode #example -c</code>

'''NOTE:''' Some channels make use of ChanServ to lock certain modes from being unset (or even set, in some cases). By default, channel modes +n and +t are locked on all newly registered channels so they usually cannot be unset.

==Standalone Channel Modes==
These channel modes don't have any parameters, you simply set or unset them.

{| class="wikitable"
|-
! Flag
! Title
! Description
|-
| '''c'''
| No control codes
| Blocks messages containing control codes (color, bold, underline, etc) from being sent to the channel
|-
| '''i'''
| Invite only
| Makes the channel invite-only. Users must be invited by a channel operator in the channel with the <code>/invite</code> command in order to join. Users who match an existing invex (+I) mask may join without being invited.
|-
| '''m'''
| Moderated
| Mutes the channel - users who do not have at least voice (+v) or higher cannot talk in the channel.
|-
| '''n'''
| No external messages
| Blocks external messages to the channel from outside the channel. In other words, you cannot <code>/msg #channel text</code> if you are not in #channel itself, with this mode set. '''NOTE:''' This mode is usually locked on by default, via ChanServ's mode locking, and thus cannot usually be unset.
|-
| '''p'''
| Private
| Marks the channel as private - the channel will not be shown in any user's <code>/whois</code> output, and will show up as * in /LIST. '''Note that Xertion network staff can still see the channel normally in /list and /whois even with this set'''
|-
| '''s'''
| Secret
| Marks the channel as secret - the channel will not be shown in any user's <code>/whois</code> output, nor will it be shown in /LIST. '''Note that Xertion network staff can still see the channel in /list and /whois even with this set'''
|-
| '''t'''
| (Half)Ops topic
| Restricts changing the channel's topic to those with half-operator (+h) or higher. '''NOTE:''' This mode is usually locked on by default, via ChanServ's mode locking, and thus cannot usually be unset.
|-
| '''u'''
| Auditorium
| Changes the channel into an "auditorium" - you can only see yourself, and cannot see joins, parts, quits, or kicks in the channel. It is intended to save bandwidth. '''Note that Xertion network staff can still see all activity in an auditorium channel.'''
|-
| '''z'''
| SSL only
| Users can only join if they are connected using SSL. '''NOTE: This mode cannot be set unless existing users in the channel are already connected using SSL!'''
|-
| '''A'''
| Allow Invite
| Permits any user to use <code>/invite</code> to invite users to the channel even if they don't have half-operator (+h) or above.
|-
| '''B'''
| Block Caps
| Blocks messages with too many capital letters, as determined by the network configuration
|-
| '''C'''
| No CTCPs
| Blocks users from sending CTCPs to the channel. This does NOT block /me however (CTCP ACTION).
|-
| '''D'''
| Delayed Join
| Joins from users are not shown until they speak in the channel.
|-
| '''G'''
| Censor
| Filters predefined words from channel messages, replacing them with "(censored)". For a list of words filtered by this mode, see [[Censorship list]].
|-
| '''M'''
| Mute unregistered
| Prevents unregistered and/or unidentified users from speaking in the channel. A user will need to either register or identify to NickServ in order to talk.
|-
| '''N'''
| No nick changes
| Blocks nickname changes from any user that does not have at least voice (+v) or higher.
|-
| '''Q'''
| Restricted Kick
| Disallows use of the <code>/kick</code> command in the channel. The only way to kick a user with this set is by way of ChanServ's KICK and/or BAN commands.
|-
| '''R'''
| Registered only
| Users must be registered with AND identified to NickServ to join. Users must be using a nickname on their account's group list in order to join - identifying to an account from an unregistered nickname will NOT suffice.
|-
| '''S'''
| Strip Colors
| Strips all control codes from incoming messages to the channel, but does not block the message. Less restrictive than +c.
|-
| '''T'''
| No notices
| Blocks users from sending notices to the channel using <code>/notice</code>.
|}

==Channel Modes requiring a parameter==
To set these modes, you need to provide one or more parameters to set it. Most modes do not require the same parameters to be unset. The exception is channel mode +k, which also requires a parameter to unset as well.

{| class="wikitable"
|-
! Flag
! Title
! Description
|-
| '''k'''
| Key
| Sets a key on a channel. You can think of it as a password to enter the channel. If you have the password, you can join the channel like so: <code>/join #channel key</code>.

To set this mode:

<code>/mode #channel +k key</code>

'''NOTE:''' You must specify the SAME key you used when setting this mode, in order to unset it.
|-
| '''F'''
| Nick Flood
| Restricts the number of nickname changes in a channel to x changes every y seconds.

Example: <code>/mode #channel +F 2:20</code> limits the number of nickname changes in the channel to 2 changes every 20 seconds.
|-
| '''J'''
| Delay Rejoin
| Delays a user from automatically rejoining for the specified number of seconds after being kicked from the channel.

Example: <code>/mode #channel +J 5</code> blocks users from rejoining the channel for 5 seconds after being kicked.
|-
| '''L'''
| Redirect/Link
| (used with channel mode '''l''') When channel is full as per channel mode '''l''', redirects users to the specified channel.

Example: <code>/mode #channel +lL 30 #channel2</code> will redirect users to #channel2 when they try to /join #channel and it already has 30 users.
|-
| '''d'''
| Delay Message
| Blocks messages from users until they've been joined to the channel for the given number of seconds.

Example: <code>/mode #channel +j 5</code> will block messages from users until they have been in #channel for at least 5 seconds.
|-
| '''f'''
| Message Flood
| Kicks and optionally bans users who exceed the given number of messages in a given number of seconds.

Example 1: <code>/mode #channel +f 5:3</code> will kick any user who sends 5 or more messages to the channel within 3 seconds.
Example 2: <code>/mode #channel +f *5:3</code> will kick '''and''' ban any user who sends 5 or more messages to the channel within 3 seconds. Note the use of the asterisk before the first number, this indicates that the user should be banned as well as kicked.
|-
| '''j'''
| Join Flood
| Blocks joins to the channel for 60 seconds if joins exceed a specified number within a given number of seconds.

Example: <code>/mode #channel +j 10:7</code> will temporarily block new joins to the channel for 60 seconds if the number of joins exceeds 10 joins in 7 seconds.

'''NOTE:''' The join lockout of 60 seconds can be cancelled by simply removing and resetting channel mode +j, which has the effect of resetting the lockout timer.
|-
| '''l'''
| Limit
| Sets the maximum number of users permitted in the channel to the given number.

Example: <code>/mode #channel +l 30</code> will limit the number of users in #channel at any given time to 30, all other users will not be able to join the channel.
|-
| '''v'''
| Voice
| Gives the specified user voice - they can speak when channel mode +m is set, and are not affected by restrictive extended bans.
|-
| '''h'''
| Half-operator
| Gives the specified user half-operator - they are able to toggle select channel modes, can kick users who have voice (+v) or below, can give voice to others, and can change the channel's topic. They cannot kick or remove the modes of channel operators (+o) and above, and they cannot toggle channel modes reserved for channel operators and up.
|-
| '''o'''
| Channel operator
| Gives the specified user channel operator - they can toggle most channel modes except +a and +q, can kick other opped users and below, and can grant or remove chanop or halfop from others. Chanops cannot perform actions on channel owners or channel administrators.
|-
| '''a'''
| Protected/Admin
| Gives the specified user channel admin - the same access rights as channel operators apply here as well, with the exception that protected/admin users can kick other protected/admin users. Protected/admin users cannot take actions against channel owners.
|-
| '''q'''
| Owner
| Gives the specified user channel owner - this grants full control over virtually all aspects of the channel, including the ability to toggle any channel mode (except those only settable by IRC operators), kick anyone, and set/unset +v/+h/+o/+a/+q on other users.
|}

== List-type Channel Modes ==
These modes store parameters in a list. Those that take a nick!user@host mask can also make use of [https://wiki.xertion.org/w/Channel_management#Extended_Bans Extended Bans].

{| class="wikitable"
|-
! Flag
! Title
! Description
|-
| '''b'''
| Channel ban
| Prevents users matching a nick!user@host mask from joining, or prevents matching users from speaking in the channel.

Examples:
* <code>/mode #channel +b LameUser!*@*</code> will ban all users with the nickname LameUser.
* <code>/mode #channel +b *!*@*.aol.com</code> will ban any user whose host portion (the part after the @) ends in "aol.com"
|-
| '''e'''
| Channel exemption
| Exempts users matching a nick!user@host mask from a matching ban.

Examples:
* <code>/mode #channel +e GoodUser!*@*</code> will allow any user with the nickname Gooduser to join even if they otherwise match an existing ban (+b)
* <code>/mode #channel +e *!*@*.net</code> permits any user whose host portion ends in ".net" even if they match an existing ban (+b)
|-
| '''I'''
| Invite exemption (invex)
| Allows a user matching a nick!user@host mask to join an invite-only (+i) channel without having to be invited with <code>/invite</code>.
|-
| '''g'''
| Channel censor
| Filters messages containing the specified text anywhere in the message from being sent to the channel. Unlike +G, the message is completely blocked if it contains the text anywhere in the message. Wildcards are accepted but not usually needed. Example: <code>/mode #channel +g poo</code> will block all messages that contain the word 'poo' anywhere in the message, even if it in the middle of a word.

You can view a channel's censor list by typing <code>/mode #channel +g</code> without any parameters.
|-
| '''w'''
| Channel ACL
| Grants users matching masks the specified mode. Some [http://wiki.xertion.org/w/Channel_management#Extended_Bans ExtBans] can be used here. Example: <code>/mode #channel +w v:R:BDRyan</code> will grant voice (+v) to anyone identified to the registered account BDRyan.

You can view a channel's internal access list by typing <code>/mode #channel +w</code> without any parameters.
|-
| '''X'''
| Exempt Chanops
| Exempts users with specific access from specific channel restrictions, for more information see [[ExemptChanops]]

'''NOTE:''' Despite the name "exempt chanops" this mode can, in fact, be used to apply the exemption to any specific level of channel access.
|}

== Restricted Channel Modes ==
'''These modes can be set/unset ONLY by either an IRC Operator and/or network Services, not by normal users!'''
{| class="wikitable"
|-
! Flag
! Title
! Description
|-
| '''O'''
| Oper Only
| Only IRC Operators can join the channel
|-
| '''P'''
| Permanent
| Marks the channel as permanent. Permanent channels will remain open even when all users have left, thereby preserving things like modes, ban lists, and the topic.
|-
| '''Y'''
| Oper Prefix
| Marks the user as an IRC Operator in the channel with a ! prefix.
|-
| '''r'''
| Registered Channel
| Marks the channel as a registered channel. '''Only network Services can set/unset this.'''
|}

==See also==
*[[Channel Management]]

[[Category:Commands]]

User Modes

2020-04-22T18:26:47Z

Kaishiro: Fixed user mode +I description

The following user modes are available for use on Xertion. To set one of these, issue a MODE command for your nickname, e.g <code>/mode YourNick +i</code> would set user mode +i for yourself (if your nickname was "YourNick"; replace with your actual nickname). To remove a usermode, use <code>/mode YourNick -(mode letter)</code>, replacing mode letter with the letter of the usermode to remove.
{| class="wikitable"
|-
!|Flag
!|Title
!|Description
|-
| style="background: white; padding-left: 1em" colspan="3"|Modes that prevent certain messages
|-
|'''c'''
|Common Channels
|Blocks private messages from users who do not share a common channel with you.
|-
|'''R'''
|Registered Only
|Blocks private messages from users who are not registered and identified to NickServ.
|-
|'''g'''
|Caller ID Mode
|Blocks all private messages server-side except for nicknames you allow with the '''/accept''' command. See [[Caller_ID|Caller ID]] for more information.
|-
| style="background: white; padding-left: 1em" colspan="3"|Modes that add privacy
|-
|'''i'''
|Invisible
|Makes you invisible in a wildcard <code>/who</code> command.
|-
|'''I''' (capital 'i')
|Private
|Hides your channels from a <code>/whois</code> command.
|-
|'''x'''
|Cloaked
|Partially cloaks your hostname. This usermode is set by default on connecting users.
|-
| style="background: white; padding-left: 1em" colspan="3"|Other user modes
|-
|'''w'''
|Wallops
|Can receive wallops messages. Xertion Network Staff use wallops messages from time to time in cases where it is either more convenient for a given situation, or network services (Global) are offline or otherwise unavailable. It is '''highly''' recommended you leave this mode set as you may miss out on important network information.
|-
|'''z'''
|Secure Messages
|Restrict private messages received to SSL/TLS verified users only.
|-
|'''S'''
|Strip Color
|Strips mIRC colour/bold/underline codes out of private messages to the user.
|-
|'''B'''
|Bot Mode
|Marks the user as a bot. Mostly used for XDCC bots and network service bots run by Xertion Network Staff.
|-
|'''G'''
|User Censor
|Filters your incoming private messages according to the pre-defined network list of [[Censorship_list|censored words]], replacing them with ''(censored)''.
|-
| style="background: white; padding-left: 1em" colspan="3"|Modes only settable by services or servers
|-
|'''r'''
|Registered
|''Only set by services''. NickServ will set this on you automatically when you successfully identify to your nickname. It cannot be set/unset except by services.
|}

[[Category:Commands]]

Channel Modes

2020-04-22T17:19:52Z

Kaishiro: /* Standalone Channel Modes */

==How to change a channel mode==
To change a mode on a channel, use the <code>/mode</code> command with the channel mode you wish to change. For example:

To set +c on the channel #example:

<code>/mode #example +c</code>

Or to unset it:

<code>/mode #example -c</code>

'''NOTE:''' Some channels make use of ChanServ to lock certain modes from being unset (or even set, in some cases). By default, channel modes +n and +t are locked on all newly registered channels so they usually cannot be unset.

==Standalone Channel Modes==
These channel modes don't have any parameters, you simply set or unset them.

{| class="wikitable"
|-
! Flag
! Title
! Description
|-
| '''c'''
| No control codes
| Blocks messages containing control codes (color, bold, underline, etc) from being sent to the channel
|-
| '''i'''
| Invite only
| Makes the channel invite-only. Users must be invited by a channel operator in the channel with the <code>/invite</code> command in order to join. Users who match an existing invex (+I) mask may join without being invited.
|-
| '''m'''
| Moderated
| Mutes the channel - users who do not have at least voice (+v) or higher cannot talk in the channel.
|-
| '''n'''
| No external messages
| Blocks external messages to the channel from outside the channel. In other words, you cannot <code>/msg #channel text</code> if you are not in #channel itself, with this mode set. '''NOTE:''' This mode is usually locked on by default, via ChanServ's mode locking, and thus cannot usually be unset.
|-
| '''p'''
| Private
| Marks the channel as private - the channel will not be shown in any user's <code>/whois</code> output, and will show up as * in /LIST. '''Note that Xertion network staff can still see the channel normally in /list and /whois even with this set'''
|-
| '''s'''
| Secret
| Marks the channel as secret - the channel will not be shown in any user's <code>/whois</code> output, nor will it be shown in /LIST. '''Note that Xertion network staff can still see the channel in /list and /whois even with this set'''
|-
| '''t'''
| (Half)Ops topic
| Restricts changing the channel's topic to those with half-operator (+h) or higher. '''NOTE:''' This mode is usually locked on by default, via ChanServ's mode locking, and thus cannot usually be unset.
|-
| '''u'''
| Auditorium
| Changes the channel into an "auditorium" - you can only see yourself, and cannot see joins, parts, quits, or kicks in the channel. It is intended to save bandwidth. '''Note that Xertion network staff can still see all activity in an auditorium channel.'''
|-
| '''z'''
| SSL only
| Users can only join if they are connected using SSL. '''NOTE: This mode cannot be set unless existing users in the channel are already connected using SSL!'''
|-
| '''A'''
| Allow Invite
| Permits any user to use <code>/invite</code> to invite users to the channel even if they don't have half-operator (+h) or above.
|-
| '''B'''
| Block Caps
| Blocks messages with too many capital letters, as determined by the network configuration
|-
| '''C'''
| No CTCPs
| Blocks users from sending CTCPs to the channel. This does NOT block /me however (CTCP ACTION).
|-
| '''D'''
| Delayed Join
| Joins from users are not shown until they speak in the channel.
|-
| '''G'''
| Censor
| Filters predefined words from channel messages, replacing them with "(censored)". For a list of words filtered by this mode, see [[Censorship list]].
|-
| '''M'''
| Mute unregistered
| Prevents unregistered and/or unidentified users from speaking in the channel. A user will need to either register or identify to NickServ in order to talk.
|-
| '''N'''
| No nick changes
| Blocks nickname changes from any user that does not have at least voice (+v) or higher.
|-
| '''Q'''
| Restricted Kick
| Disallows use of the <code>/kick</code> command in the channel. The only way to kick a user with this set is by way of ChanServ's KICK and/or BAN commands.
|-
| '''R'''
| Registered only
| Users must be registered with AND identified to NickServ to join. Users must be using a nickname on their account's group list in order to join - identifying to an account from an unregistered nickname will NOT suffice.
|-
| '''S'''
| Strip Colors
| Strips all control codes from incoming messages to the channel, but does not block the message. Less restrictive than +c.
|-
| '''T'''
| No notices
| Blocks users from sending notices to the channel using <code>/notice</code>.
|-
| '''z'''
| Secure Users
| Restrict access to the channel to SSL/TLS verified clients only.
|}

==Channel Modes requiring a parameter==
To set these modes, you need to provide one or more parameters to set it. Most modes do not require the same parameters to be unset. The exception is channel mode +k, which also requires a parameter to unset as well.

{| class="wikitable"
|-
! Flag
! Title
! Description
|-
| '''k'''
| Key
| Sets a key on a channel. You can think of it as a password to enter the channel. If you have the password, you can join the channel like so: <code>/join #channel key</code>.

To set this mode:

<code>/mode #channel +k key</code>

'''NOTE:''' You must specify the SAME key you used when setting this mode, in order to unset it.
|-
| '''F'''
| Nick Flood
| Restricts the number of nickname changes in a channel to x changes every y seconds.

Example: <code>/mode #channel +F 2:20</code> limits the number of nickname changes in the channel to 2 changes every 20 seconds.
|-
| '''J'''
| Delay Rejoin
| Delays a user from automatically rejoining for the specified number of seconds after being kicked from the channel.

Example: <code>/mode #channel +J 5</code> blocks users from rejoining the channel for 5 seconds after being kicked.
|-
| '''L'''
| Redirect/Link
| (used with channel mode '''l''') When channel is full as per channel mode '''l''', redirects users to the specified channel.

Example: <code>/mode #channel +lL 30 #channel2</code> will redirect users to #channel2 when they try to /join #channel and it already has 30 users.
|-
| '''d'''
| Delay Message
| Blocks messages from users until they've been joined to the channel for the given number of seconds.

Example: <code>/mode #channel +j 5</code> will block messages from users until they have been in #channel for at least 5 seconds.
|-
| '''f'''
| Message Flood
| Kicks and optionally bans users who exceed the given number of messages in a given number of seconds.

Example 1: <code>/mode #channel +f 5:3</code> will kick any user who sends 5 or more messages to the channel within 3 seconds.
Example 2: <code>/mode #channel +f *5:3</code> will kick '''and''' ban any user who sends 5 or more messages to the channel within 3 seconds. Note the use of the asterisk before the first number, this indicates that the user should be banned as well as kicked.
|-
| '''j'''
| Join Flood
| Blocks joins to the channel for 60 seconds if joins exceed a specified number within a given number of seconds.

Example: <code>/mode #channel +j 10:7</code> will temporarily block new joins to the channel for 60 seconds if the number of joins exceeds 10 joins in 7 seconds.

'''NOTE:''' The join lockout of 60 seconds can be cancelled by simply removing and resetting channel mode +j, which has the effect of resetting the lockout timer.
|-
| '''l'''
| Limit
| Sets the maximum number of users permitted in the channel to the given number.

Example: <code>/mode #channel +l 30</code> will limit the number of users in #channel at any given time to 30, all other users will not be able to join the channel.
|-
| '''v'''
| Voice
| Gives the specified user voice - they can speak when channel mode +m is set, and are not affected by restrictive extended bans.
|-
| '''h'''
| Half-operator
| Gives the specified user half-operator - they are able to toggle select channel modes, can kick users who have voice (+v) or below, can give voice to others, and can change the channel's topic. They cannot kick or remove the modes of channel operators (+o) and above, and they cannot toggle channel modes reserved for channel operators and up.
|-
| '''o'''
| Channel operator
| Gives the specified user channel operator - they can toggle most channel modes except +a and +q, can kick other opped users and below, and can grant or remove chanop or halfop from others. Chanops cannot perform actions on channel owners or channel administrators.
|-
| '''a'''
| Protected/Admin
| Gives the specified user channel admin - the same access rights as channel operators apply here as well, with the exception that protected/admin users can kick other protected/admin users. Protected/admin users cannot take actions against channel owners.
|-
| '''q'''
| Owner
| Gives the specified user channel owner - this grants full control over virtually all aspects of the channel, including the ability to toggle any channel mode (except those only settable by IRC operators), kick anyone, and set/unset +v/+h/+o/+a/+q on other users.
|}

== List-type Channel Modes ==
These modes store parameters in a list. Those that take a nick!user@host mask can also make use of [https://wiki.xertion.org/w/Channel_management#Extended_Bans Extended Bans].

{| class="wikitable"
|-
! Flag
! Title
! Description
|-
| '''b'''
| Channel ban
| Prevents users matching a nick!user@host mask from joining, or prevents matching users from speaking in the channel.

Examples:
* <code>/mode #channel +b LameUser!*@*</code> will ban all users with the nickname LameUser.
* <code>/mode #channel +b *!*@*.aol.com</code> will ban any user whose host portion (the part after the @) ends in "aol.com"
|-
| '''e'''
| Channel exemption
| Exempts users matching a nick!user@host mask from a matching ban.

Examples:
* <code>/mode #channel +e GoodUser!*@*</code> will allow any user with the nickname Gooduser to join even if they otherwise match an existing ban (+b)
* <code>/mode #channel +e *!*@*.net</code> permits any user whose host portion ends in ".net" even if they match an existing ban (+b)
|-
| '''I'''
| Invite exemption (invex)
| Allows a user matching a nick!user@host mask to join an invite-only (+i) channel without having to be invited with <code>/invite</code>.
|-
| '''g'''
| Channel censor
| Filters messages containing the specified text anywhere in the message from being sent to the channel. Unlike +G, the message is completely blocked if it contains the text anywhere in the message. Wildcards are accepted but not usually needed. Example: <code>/mode #channel +g poo</code> will block all messages that contain the word 'poo' anywhere in the message, even if it in the middle of a word.

You can view a channel's censor list by typing <code>/mode #channel +g</code> without any parameters.
|-
| '''w'''
| Channel ACL
| Grants users matching masks the specified mode. Some [http://wiki.xertion.org/w/Channel_management#Extended_Bans ExtBans] can be used here. Example: <code>/mode #channel +w v:R:BDRyan</code> will grant voice (+v) to anyone identified to the registered account BDRyan.

You can view a channel's internal access list by typing <code>/mode #channel +w</code> without any parameters.
|-
| '''X'''
| Exempt Chanops
| Exempts users with specific access from specific channel restrictions, for more information see [[ExemptChanops]]

'''NOTE:''' Despite the name "exempt chanops" this mode can, in fact, be used to apply the exemption to any specific level of channel access.
|}

== Restricted Channel Modes ==
'''These modes can be set/unset ONLY by either an IRC Operator and/or network Services, not by normal users!'''
{| class="wikitable"
|-
! Flag
! Title
! Description
|-
| '''O'''
| Oper Only
| Only IRC Operators can join the channel
|-
| '''P'''
| Permanent
| Marks the channel as permanent. Permanent channels will remain open even when all users have left, thereby preserving things like modes, ban lists, and the topic.
|-
| '''Y'''
| Oper Prefix
| Marks the user as an IRC Operator in the channel with a ! prefix.
|-
| '''r'''
| Registered Channel
| Marks the channel as a registered channel. '''Only network Services can set/unset this.'''
|}

==See also==
*[[Channel Management]]

[[Category:Commands]]

User Modes

2020-04-22T17:18:08Z

Kaishiro: Adding +z to user modes.

The following user modes are available for use on Xertion. To set one of these, issue a MODE command for your nickname, e.g <code>/mode YourNick +i</code> would set user mode +i for yourself (if your nickname was "YourNick"; replace with your actual nickname). To remove a usermode, use <code>/mode YourNick -(mode letter)</code>, replacing mode letter with the letter of the usermode to remove.
{| class="wikitable"
|-
!|Flag
!|Title
!|Description
|-
| style="background: white; padding-left: 1em" colspan="3"|Modes that prevent certain messages
|-
|'''c'''
|Common Channels
|Blocks private messages from users who do not share a common channel with you.
|-
|'''R'''
|Registered Only
|Blocks private messages from users who are not registered and identified to NickServ.
|-
|'''g'''
|Caller ID Mode
|Blocks all private messages server-side except for nicknames you allow with the '''/accept''' command. See [[Caller_ID|Caller ID]] for more information.
|-
| style="background: white; padding-left: 1em" colspan="3"|Modes that add privacy
|-
|'''i'''
|Invisible
|Makes you invisible in a wildcard <code>/who</code> command.
|-
|'''I''' (capital 'i')
|Private
|Hides your channels and idle time in a <code>/whois</code> command.
|-
|'''x'''
|Cloaked
|Partially cloaks your hostname. This usermode is set by default on connecting users.
|-
| style="background: white; padding-left: 1em" colspan="3"|Other user modes
|-
|'''w'''
|Wallops
|Can receive wallops messages. Xertion Network Staff use wallops messages from time to time in cases where it is either more convenient for a given situation, or network services (Global) are offline or otherwise unavailable. It is '''highly''' recommended you leave this mode set as you may miss out on important network information.
|-
|'''z'''
|Secure Messages
|Restrict private messages received to SSL/TLS verified users only.
|-
|'''S'''
|Strip Color
|Strips mIRC colour/bold/underline codes out of private messages to the user.
|-
|'''B'''
|Bot Mode
|Marks the user as a bot. Mostly used for XDCC bots and network service bots run by Xertion Network Staff.
|-
|'''G'''
|User Censor
|Filters your incoming private messages according to the pre-defined network list of [[Censorship_list|censored words]], replacing them with ''(censored)''.
|-
| style="background: white; padding-left: 1em" colspan="3"|Modes only settable by services or servers
|-
|'''r'''
|Registered
|''Only set by services''. NickServ will set this on you automatically when you successfully identify to your nickname. It cannot be set/unset except by services.
|}

[[Category:Commands]]

Immortal-Anime

2020-03-16T10:27:29Z

Kaishiro: Created page with "='''ATTENTION Immortal-Anime Users'''= <span style="color: rgb(255, 0, 0);" data-mce-style=..."

='''ATTENTION Immortal-Anime Users'''=
''''''<brclass="mw_emptyline_first" /><brclass="mw_emptyline" />'''Welcome to Xertion!''''''''''''Immortal-Anime has merged with Xertion due to the original owners of Immortal-Anime wanting to step down.''''''This merge will bring you a better user experience overall with a larger community, better security, up-to-date services, and stability.''''''<brdata-mce-bogus="1" />''''''''Unfortunately, due to a database incompatibility, all Immortal-Anime users will have to register their nicknames and their channels again.''''''''''<brdata-mce-bogus="1" />''''''''''If you were the owner of a channel on Immortal-Anime, and there is currently no ops, an AFK op, or an unknown op in your channel and you would like to regain access of your channel, please contact us in #help''''''''''<brdata-mce-bogus="1" />''''''''''We will be happy to assist you!''''''''''''Be sure to check out our main page[https://wiki.xertion.org/w/Main Page here]'''

Staff

2020-03-12T03:05:57Z

Kaishiro:

If you have an issue that requires network staff, <code>/join #help</code> and ask there. It's the fastest way to get your issue resolved.
{| class="sortable" style="border: 1px solid rgb(0, 0, 0); border-collapse: collapse; width: 51.0566%;" border="1" cellspacing="1" cellpadding="5" align="center" data-mce-style="border: 1px solid #000000; border-collapse: collapse; width: 51.0566%;"
|-
! style="background-color: rgb(64, 128, 255); width: 23%;" scope="row" data-mce-style="background-color: #4080ff; width: 23%;"|Nick
! style="background-color: rgb(64, 128, 255); width: 21%;" scope="row" data-mce-style="background-color: #4080ff; width: 21%;"|Timezone
! style="background-color: rgb(64, 128, 255); width: 34.6194%;" scope="row" data-mce-style="background-color: #4080ff; width: 34.6194%;"|Rank
|-
| style="width: 23%;" data-mce-style="width: 23%;"|[[User:Kaishiro|Kaishiro]] ([mailto:kaishiro@xertion.org Email])
| style="width: 21%;" data-mce-style="width: 21%;"|Central
| style="width: 34.6194%;" data-mce-style="width: 34.6194%;"|Network Owner
|-
| style="width: 23%;" data-mce-style="width: 23%;"|[[User:Sakura|Sakura`Kinomoto]] ([mailto:sakura@xertion.org Email])
| style="width: 21%;" data-mce-style="width: 21%;"|Pacific
| style="width: 34.6194%;" data-mce-style="width: 34.6194%;"|Network Owner
|-
| style="width: 23%;" data-mce-style="width: 23%;"|[[User:IkarosBD|IkarosBD (BDRyan)]]
| style="width: 21%;" data-mce-style="width: 21%;"|Central
| style="width: 34.6194%;" data-mce-style="width: 34.6194%;"|Root Administrator, Routing Manager, Dev Lead
|-
| style="width: 23%;" data-mce-style="width: 23%;"|[[User:Valdearg|Valdearg]] ([mailto:valdearg@xertion.org Email])
| style="width: 21%;" data-mce-style="width: 21%;"|British
| style="width: 34.6194%;" data-mce-style="width: 34.6194%;"|Root Administrator
|-
| style="width: 23%;" data-mce-style="width: 23%;"|[[User:Koby|Koby]]
| style="width: 21%;" data-mce-style="width: 21%;"|Central
| style="width: 34.6194%;" data-mce-style="width: 34.6194%;"|Server Administrator
|-
| style="width: 23%;" data-mce-style="width: 23%;"|[[User:iCurse|iCurse]] ([mailto:icurse@xertion.org Email])
| style="width: 21%;" data-mce-style="width: 21%;"|N/A
| style="width: 34.6194%;" data-mce-style="width: 34.6194%;"|Server Administrator
|-
| style="width: 23%;" data-mce-style="width: 23%;"|[[User:Ravager|Ravager]] ([mailto:ravager@xertion.org Email])
| style="width: 21%;" data-mce-style="width: 21%;"|Central
| style="width: 34.6194%;" data-mce-style="width: 34.6194%;"|Operator
|-
| style="width: 23%;" data-mce-style="width: 23%;"|Kaugustino
| style="width: 21%;" data-mce-style="width: 21%;"|Mountain
| style="width: 34.6194%;" data-mce-style="width: 34.6194%;"|Operator
|-
| style="width: 23%;" data-mce-style="width: 23%;"|maverick_hunter_17
| style="width: 21%;" data-mce-style="width: 21%;"|Eastern
| style="width: 34.6194%;" data-mce-style="width: 34.6194%;"|Operator
|}

[[Category:General]]

Staff

2020-03-12T03:03:56Z

Kaishiro: Updating Mavvy's timezone

NickServ:CertFP

2018-11-18T18:21:45Z

Kaishiro: /* Mac */

==Introduction==

This page describes how to connect, and identify yourself to services securely via a certificate fingerprint.

A major advantage of using a CertFP to authenticate is that you don't have to use <code>/msg NickServ IDENTIFY</code> anymore.

By using SSL you are also encrypting the connection between you and the server.

==Prerequisites==
We will be using OpenSSL to create the certificate. Windows IRC clients will typically include OpenSSL support already, and so usually no additional installation is needed for SSL support on Windows.
===Linux===
Most Linux distributions already come with the OpenSSL binary and libraries either installed by default or available to be installed from a package management system (e.g apt-get, yum, etc). If neither of these is true for you, you will need to go to the official [http://www.openssl.org/ OpenSSL] website, download the sources, and compile it yourself.

===Windows===
OpenSSL support on Windows is typically included with more recent versions of such clients like mIRC and HexChat. You no longer need to download and install OpenSSL for Windows so long as you are using either mIRC version 7.36 or better, or HexChat for Windows.

===Mac===
Mac already comes with the OpenSSL binary and libraries installed by default. Locate Keychain Access in your Utilities folder to begin.

==Creating the certificate==
Once you have verified you have OpenSSL support on your platform, you will need to create a key and certificate.

===Linux===
For Linux platforms, the following command should be sufficient:
<code>openssl req -nodes -newkey rsa:2048 -keyout Xertion.key -x509 -days 365 -out Xertion.cer</code>

===Windows===
For Windows systems:
* First, go to [http://slproweb.com/products/Win32OpenSSL.html http://slproweb.com/products/Win32OpenSSL.html] and download the latest OpenSSL '''Light''' installer. Install to the default location, keeping the default options.
* Click the Start button.
* Type <code>cmd</code> in the search bar, and click on Command Prompt.
* Type in <code>cd C:\OpenSSL-Win32\bin</code> and press Enter.
* Type <code>openssl</code> and press Enter. You should now see an OpenSSL prompt.
* At the prompt, type: <code>req -nodes -newkey rsa:2048 -keyout Xertion.key -x509 -days 365 -out Xertion.cer</code> and press Enter.

Alternatively, you can navigate directly to the Command Prompt if it does not show up when you search for it in the Start Menu - go to Start -> All Programs -> Accessories -> Command Prompt

NOTE: If you get the error
<pre>WARNING: can’t open config file: /usr/local/ssl/openssl.cnf</pre>
You will need to exit OpenSSL and run the following command in Command Prompt: <code>set OPENSSL_CONF=C:\OpenSSL-Win32\bin\openssl.cfg</code>. Do '''NOT''' close the Command Prompt afterwards. After you have executed the command, try generating the key and certificate again.

During certificate generation, you will be asked the following series of questions. Fill these in accordingly - enter your two-letter country code for the country you live in, the state/region/province name you live in + your city. Enter anything you like for organization name and organizational unit name. Use your main IRC nickname for the Common Name field. For Email Address, it does NOT have to be real but SHOULD be in proper email address format of user@domain.tld

<pre>
Country Name (2 letter code) [US]:
State or Province Name (full name) [Texas]:
Locality Name (eg, city) [San Antonio]:
Organization Name (eg, company) [Stealth3]: Xertion
Organizational Unit Name (eg, section) [ISP]: IRC
Common Name (eg, YOUR name) []:
Email Address []:
</pre>

Once this information has been entered, two files will then be created - the key and associated certificate - which will need to be combined together.

For Linux, run <code>cat Xertion.cer Xertion.key > Xertion.pem</code>. For Windows, run <code>type Xertion.cer Xertion.key > Xertion.pem</code>

===Mac===
For Mac operating systems:
* Open Keychain Access from your Utilities folder
* In the list labeled "keychains", select the keychain labeled "login"
* In the main menu, in the top left corner of the screen, open the bold Keychain Access menu. Within this menu, open the Certificate Assistant submenu, then click the menu item labeled Create a Certificate….
* Inside this window, enter a name into the field labeled Name. The name you chose is not important. It is only used to make your certificate easier to find.
* Leave the Identity Type as Self Signed Root
* Change the Certificate Type to SSL Client
* Click Create
* Ignore the You are about to create a self-signed certificate warning by clicking Continue.

Congratulations, you now have an SSL certificate!

==Configuring your client==
Now that you have your SSL certificate, you will need to configure your client to use it. This step will vary greatly from client to client - some well-known clients are covered below. If your client is not included here, check its documentation to see if it supports client SSL certificates and how to set it up to use one.

===KVIrc===

Move the Xertion.pem file to a safe place.
* Go to "Settings -> Configure KVIrc"
* Go to "Connection -> Advanced"
* On the Tab "SSL" check "Use SSL certificate" and "Use SSL private key' and point both to the Xertion.pem file you created.
* Change your connection settings and enable the SSL option.

===mIRC===

Move the Xertion.pem file to a safe place.
* Go to "Main Options Menu -> Connect -> Options"
* Click on the SSL button. (NOTE: If there is no SSL button, then OpenSSL is not installed correctly and you will need to reinstall it properly before continuing)
* Click on the empty box below "Private Key File", navigate to where you placed your Xertion.pem and select it.
* Do the same for "Certificate Chain File".
* Click OK, then click OK again.

===XChat===

XChat uses the pem file that corresponds with the name of the network under "Network list". If irc.xertion.org is named under Xertion, then all you have to do is move the Xertion.pem file to <code>~/.xchat2/Xertion.pem</code> or <code>C:\Users\xxx\AppData\Roaming\X-Chat 2</code>. If it's not named "Xertion", then you will have to either rename the .pem file, or rename the network that irc.xertion.org is listed under so they match each other. Once you are done with that:
* Go to Xchat menu and select "Network List"
* Find Xertion and select "edit".
* Select the boxes "Use SSL for all the servers on this network" and "Accept invalid SSL certificate".
* Click "Close" and then click "Connect".

===HexChat===

HexChat uses the pem file that corresponds with the name of the network under "Network list". If irc.xertion.org is named under Xertion, then all you have to do is move the Xertion.pem file to <code>~/.config/hexchat/certs/Xertion.pem</code> or <code>C:\Users\xxx\AppData\Roaming\hexchat\certs</code>. If it's not named "Xertion.pem", then you will have to either rename the .pem file, or rename the network that irc.xertion.org is listed under, so they match each other. Once you are done with that:
* Go to HexChat menu and select "Network List"
* Find Xertion and select "Edit".
* Select the box "Use SSL for all the servers on this network".
* Click "Close" and then click "Connect".
[https://hexchat.readthedocs.org/en/latest/tips.html#client-certificates HexChat Documentation]

Alternatively, if you choose to use the same .pem file for all networks (not recommended!), you can name the .pem file client.pem in the certs directory.

===WeeChat===
Move Xertion.pem to ~/.weechat/ssl/Xertion.pem. Create the directory ~/.weechat/ssl beforehand if it doesn't already exist.

The following commands assume your configured IRC network connection is labeled as "Xertion".

Verify SSL is properly configured:

<pre>/set irc.server.Xertion.addresses "irc.xertion.org/6697"
/set irc.server.Xertion.ssl on
/set irc.server.Xertion.ssl_dhkey_size 1024
/set irc.server.Xertion.ssl_verify off</pre>

Run the following commands for the certificate:
<pre>/set irc.server.Xertion.ssl_cert "%h/ssl/Xertion.pem"</pre>

If you're using a vhost, you'll most likely also need to set the following options to delay autojoin, so that the vhost can kick in before joining:

<pre>/set irc.server.Xertion.command "/mute"
/set irc.server.Xertion.command_delay 1</pre>

The above can also be set using the interactive iset perl script.

===irssi===
* Move the cert to <code>~/.irssi/certs/Xertion.pem</code>
* Use the command <code>/server add -ssl -ssl_cert ~/.irssi/certs/Xertion.pem -network Xertion irc.xertion.org 6697</code>

If you find that irssi does not auto-join channels on connect which want you to be identified before you are joining, add -autosendcmd "wait -xertion 2000" to your irssi network settings. This makes irssi wait 2 seconds before any further action, giving services time to identify you.

Command: <code>/network add -autosendcmd "wait -xertion 2000" Xertion</code>

===Textual===
* Begin by opening Server Properties using the keyboard combination Command U.
* In the window that appears, click Client Certificate under the Advanced section of the navigation list.
* Inside this window, click the Select Certificate button. A list of certificates will appear.
* Select the certificate that you created.
* Click the Chose button to continue. Server Properties will update the window to confirm your selection:
* Finish by clicking the Save button.

===ZNC===
* Ensure the [http://wiki.znc.in/Cert Cert module] is loaded.
* Log in to your web admin panel, go to the User Modules section, and select "Certificate".
* Copy the contents of the .pem file you created into the edit box and apply the changes.
* Reconnect your ZNC to the IRC network.

Now when you connect to Xertion, you should see something like this appear:
<pre>*** You are connected using SSL cipher "DHE-RSA-AES-256-CBC-SHA1" and your SSL fingerprint is xxxxxxxxxxxxxxxxxxxxxxx</pre>

If you see that message, then everything is configured properly and your client SSL certificate has been read in successfully. You are now ready to add this information to NickServ.

==Add the certificate fingerprint to NickServ==
Once you are connected with your SSL certificate, you will need to add its fingerprint to NickServ to be able to identify with it. Follow these steps:
* Identify yourself to services with your password: <code>/msg NickServ IDENTIFY password</code>
* Then, type (or copy/paste) this command: <code>/msg NickServ CERT ADD</code>. This will automatically add your current SSL certificate fingerprint to NickServ.

You're done! You no longer need any NickServ auto-authentication commands; you can safely disable those now. Keep your NickServ password handy just in case, though. Test it by reconnecting to the network. If everything was done correctly you should now be identified by services automatically using your SSL client certificate fingerprint - look for the following notice from NickServ: <pre>-NickServ- SSL certificate fingerprint accepted - you are now recognized.</pre>

If you have any questions, feel free to join [irc://irc.xertion.org/help #help] and ask.

[[Category:Tutorials]]

NickServ:CertFP

2018-11-18T18:20:36Z

Kaishiro: Added Textual for Mac to the How-To

==Introduction==

This page describes how to connect, and identify yourself to services securely via a certificate fingerprint.

A major advantage of using a CertFP to authenticate is that you don't have to use <code>/msg NickServ IDENTIFY</code> anymore.

By using SSL you are also encrypting the connection between you and the server.

==Prerequisites==
We will be using OpenSSL to create the certificate. Windows IRC clients will typically include OpenSSL support already, and so usually no additional installation is needed for SSL support on Windows.
===Linux===
Most Linux distributions already come with the OpenSSL binary and libraries either installed by default or available to be installed from a package management system (e.g apt-get, yum, etc). If neither of these is true for you, you will need to go to the official [http://www.openssl.org/ OpenSSL] website, download the sources, and compile it yourself.

===Windows===
OpenSSL support on Windows is typically included with more recent versions of such clients like mIRC and HexChat. You no longer need to download and install OpenSSL for Windows so long as you are using either mIRC version 7.36 or better, or HexChat for Windows.

===Mac===
Mac already comes with the OpenSSL binary and libraries either installed by default. Locate Keychain Access in your Utilities folder to begin.

==Creating the certificate==
Once you have verified you have OpenSSL support on your platform, you will need to create a key and certificate.

===Linux===
For Linux platforms, the following command should be sufficient:
<code>openssl req -nodes -newkey rsa:2048 -keyout Xertion.key -x509 -days 365 -out Xertion.cer</code>

===Windows===
For Windows systems:
* First, go to [http://slproweb.com/products/Win32OpenSSL.html http://slproweb.com/products/Win32OpenSSL.html] and download the latest OpenSSL '''Light''' installer. Install to the default location, keeping the default options.
* Click the Start button.
* Type <code>cmd</code> in the search bar, and click on Command Prompt.
* Type in <code>cd C:\OpenSSL-Win32\bin</code> and press Enter.
* Type <code>openssl</code> and press Enter. You should now see an OpenSSL prompt.
* At the prompt, type: <code>req -nodes -newkey rsa:2048 -keyout Xertion.key -x509 -days 365 -out Xertion.cer</code> and press Enter.

Alternatively, you can navigate directly to the Command Prompt if it does not show up when you search for it in the Start Menu - go to Start -> All Programs -> Accessories -> Command Prompt

NOTE: If you get the error
<pre>WARNING: can’t open config file: /usr/local/ssl/openssl.cnf</pre>
You will need to exit OpenSSL and run the following command in Command Prompt: <code>set OPENSSL_CONF=C:\OpenSSL-Win32\bin\openssl.cfg</code>. Do '''NOT''' close the Command Prompt afterwards. After you have executed the command, try generating the key and certificate again.

During certificate generation, you will be asked the following series of questions. Fill these in accordingly - enter your two-letter country code for the country you live in, the state/region/province name you live in + your city. Enter anything you like for organization name and organizational unit name. Use your main IRC nickname for the Common Name field. For Email Address, it does NOT have to be real but SHOULD be in proper email address format of user@domain.tld

<pre>
Country Name (2 letter code) [US]:
State or Province Name (full name) [Texas]:
Locality Name (eg, city) [San Antonio]:
Organization Name (eg, company) [Stealth3]: Xertion
Organizational Unit Name (eg, section) [ISP]: IRC
Common Name (eg, YOUR name) []:
Email Address []:
</pre>

Once this information has been entered, two files will then be created - the key and associated certificate - which will need to be combined together.

For Linux, run <code>cat Xertion.cer Xertion.key > Xertion.pem</code>. For Windows, run <code>type Xertion.cer Xertion.key > Xertion.pem</code>

===Mac===
For Mac operating systems:
* Open Keychain Access from your Utilities folder
* In the list labeled "keychains", select the keychain labeled "login"
* In the main menu, in the top left corner of the screen, open the bold Keychain Access menu. Within this menu, open the Certificate Assistant submenu, then click the menu item labeled Create a Certificate….
* Inside this window, enter a name into the field labeled Name. The name you chose is not important. It is only used to make your certificate easier to find.
* Leave the Identity Type as Self Signed Root
* Change the Certificate Type to SSL Client
* Click Create
* Ignore the You are about to create a self-signed certificate warning by clicking Continue.

Congratulations, you now have an SSL certificate!

==Configuring your client==
Now that you have your SSL certificate, you will need to configure your client to use it. This step will vary greatly from client to client - some well-known clients are covered below. If your client is not included here, check its documentation to see if it supports client SSL certificates and how to set it up to use one.

===KVIrc===

Move the Xertion.pem file to a safe place.
* Go to "Settings -> Configure KVIrc"
* Go to "Connection -> Advanced"
* On the Tab "SSL" check "Use SSL certificate" and "Use SSL private key' and point both to the Xertion.pem file you created.
* Change your connection settings and enable the SSL option.

===mIRC===

Move the Xertion.pem file to a safe place.
* Go to "Main Options Menu -> Connect -> Options"
* Click on the SSL button. (NOTE: If there is no SSL button, then OpenSSL is not installed correctly and you will need to reinstall it properly before continuing)
* Click on the empty box below "Private Key File", navigate to where you placed your Xertion.pem and select it.
* Do the same for "Certificate Chain File".
* Click OK, then click OK again.

===XChat===

XChat uses the pem file that corresponds with the name of the network under "Network list". If irc.xertion.org is named under Xertion, then all you have to do is move the Xertion.pem file to <code>~/.xchat2/Xertion.pem</code> or <code>C:\Users\xxx\AppData\Roaming\X-Chat 2</code>. If it's not named "Xertion", then you will have to either rename the .pem file, or rename the network that irc.xertion.org is listed under so they match each other. Once you are done with that:
* Go to Xchat menu and select "Network List"
* Find Xertion and select "edit".
* Select the boxes "Use SSL for all the servers on this network" and "Accept invalid SSL certificate".
* Click "Close" and then click "Connect".

===HexChat===

HexChat uses the pem file that corresponds with the name of the network under "Network list". If irc.xertion.org is named under Xertion, then all you have to do is move the Xertion.pem file to <code>~/.config/hexchat/certs/Xertion.pem</code> or <code>C:\Users\xxx\AppData\Roaming\hexchat\certs</code>. If it's not named "Xertion.pem", then you will have to either rename the .pem file, or rename the network that irc.xertion.org is listed under, so they match each other. Once you are done with that:
* Go to HexChat menu and select "Network List"
* Find Xertion and select "Edit".
* Select the box "Use SSL for all the servers on this network".
* Click "Close" and then click "Connect".
[https://hexchat.readthedocs.org/en/latest/tips.html#client-certificates HexChat Documentation]

Alternatively, if you choose to use the same .pem file for all networks (not recommended!), you can name the .pem file client.pem in the certs directory.

===WeeChat===
Move Xertion.pem to ~/.weechat/ssl/Xertion.pem. Create the directory ~/.weechat/ssl beforehand if it doesn't already exist.

The following commands assume your configured IRC network connection is labeled as "Xertion".

Verify SSL is properly configured:

<pre>/set irc.server.Xertion.addresses "irc.xertion.org/6697"
/set irc.server.Xertion.ssl on
/set irc.server.Xertion.ssl_dhkey_size 1024
/set irc.server.Xertion.ssl_verify off</pre>

Run the following commands for the certificate:
<pre>/set irc.server.Xertion.ssl_cert "%h/ssl/Xertion.pem"</pre>

If you're using a vhost, you'll most likely also need to set the following options to delay autojoin, so that the vhost can kick in before joining:

<pre>/set irc.server.Xertion.command "/mute"
/set irc.server.Xertion.command_delay 1</pre>

The above can also be set using the interactive iset perl script.

===irssi===
* Move the cert to <code>~/.irssi/certs/Xertion.pem</code>
* Use the command <code>/server add -ssl -ssl_cert ~/.irssi/certs/Xertion.pem -network Xertion irc.xertion.org 6697</code>

If you find that irssi does not auto-join channels on connect which want you to be identified before you are joining, add -autosendcmd "wait -xertion 2000" to your irssi network settings. This makes irssi wait 2 seconds before any further action, giving services time to identify you.

Command: <code>/network add -autosendcmd "wait -xertion 2000" Xertion</code>

===Textual===
* Begin by opening Server Properties using the keyboard combination Command U.
* In the window that appears, click Client Certificate under the Advanced section of the navigation list.
* Inside this window, click the Select Certificate button. A list of certificates will appear.
* Select the certificate that you created.
* Click the Chose button to continue. Server Properties will update the window to confirm your selection:
* Finish by clicking the Save button.

===ZNC===
* Ensure the [http://wiki.znc.in/Cert Cert module] is loaded.
* Log in to your web admin panel, go to the User Modules section, and select "Certificate".
* Copy the contents of the .pem file you created into the edit box and apply the changes.
* Reconnect your ZNC to the IRC network.

Now when you connect to Xertion, you should see something like this appear:
<pre>*** You are connected using SSL cipher "DHE-RSA-AES-256-CBC-SHA1" and your SSL fingerprint is xxxxxxxxxxxxxxxxxxxxxxx</pre>

If you see that message, then everything is configured properly and your client SSL certificate has been read in successfully. You are now ready to add this information to NickServ.

==Add the certificate fingerprint to NickServ==
Once you are connected with your SSL certificate, you will need to add its fingerprint to NickServ to be able to identify with it. Follow these steps:
* Identify yourself to services with your password: <code>/msg NickServ IDENTIFY password</code>
* Then, type (or copy/paste) this command: <code>/msg NickServ CERT ADD</code>. This will automatically add your current SSL certificate fingerprint to NickServ.

You're done! You no longer need any NickServ auto-authentication commands; you can safely disable those now. Keep your NickServ password handy just in case, though. Test it by reconnecting to the network. If everything was done correctly you should now be identified by services automatically using your SSL client certificate fingerprint - look for the following notice from NickServ: <pre>-NickServ- SSL certificate fingerprint accepted - you are now recognized.</pre>

If you have any questions, feel free to join [irc://irc.xertion.org/help #help] and ask.

[[Category:Tutorials]]

Main Page

2018-11-11T06:42:05Z

Kaishiro:

__NOTOC__
Welcome to the '''Xertion Wiki''', which is a project run by [[Staff|Xertion Staff]] and the [[Community|Xertion Community]] with the aim of answering everyday queries received by Xertion users, both specifically about this network, and IRC in general. The main editor of this wiki is [[User:IkarosBD|IkarosBD]] - contact him via IRC to suggest an edit.

<big><center>'''Xertion'''
[http://xertion.org Home] · [https://webchat.xertion.org Webchat] · [http://xertion.org/quote/ Quotes] [[Servers]] · [[Staff]] · [[Community]] · [[Network Beta Test|Network testing]]
</center></big>

<big><center>'''[[Rules|Rules and Policies]]'''
[[Bans]] · [[Linking]]
</center></big>

<big><center>'''[[Services]]'''
[[NickServ:Register|Nickname registration]] · [[ChanServ:Register|Channel registration]] · [[VHost|Requesting a vHost]] · [[NickServ:ResetPass|Reset nick password]] 
[[NickServ]] · [[ChanServ]] · [[BotServ]] · [[DenServ]] · [[HostServ]] · [[MemoServ]]</center></big>

<big><center>'''Tutorials''' 
[[Connecting to Xertion]] · [[Channel Management]] · [[Services]] · [[Channel Modes]] · [[User Modes]] · [[NickServ:CertFP|CertFP]] · [[XDCC]]</center></big>

<big><center>'''Games''' 
[http://idlerpg.xertion.org IdleRPG] · [[Werewolf]]</center></big>

Main Page

2018-11-11T06:41:23Z

Kaishiro: Removed Short URLs

__NOTOC__
Welcome to the '''Xertion Wiki''', which is a project run by [[Staff|Xertion Staff]] and the [[Community|Xertion Community]] with the aim of answering everyday queries received by Xertion users, both specifically about this network, and IRC in general. The main editor of this wiki is [[User:IkarosBD|IkarosBD]] - contact him via IRC to suggest an edit.

<big><center>'''Xertion'''
[http://xertion.org Home] · [https://webchat.xertion.org Webchat] · [http://xertion.org/quote/ Quotes] [[Servers]] · [[Staff]] · [[Community]] · [[Statistics]] · [[Network Beta Test|Network testing]]
</center></big>

<big><center>'''[[Rules|Rules and Policies]]'''
[[Bans]] · [[Linking]]
</center></big>

<big><center>'''[[Services]]'''
[[NickServ:Register|Nickname registration]] · [[ChanServ:Register|Channel registration]] · [[VHost|Requesting a vHost]] · [[NickServ:ResetPass|Reset nick password]] 
[[NickServ]] · [[ChanServ]] · [[BotServ]] · [[DenServ]] · [[HostServ]] · [[MemoServ]]</center></big>

<big><center>'''Tutorials''' 
[[Connecting to Xertion]] · [[Channel Management]] · [[Services]] · [[Channel Modes]] · [[User Modes]] · [[NickServ:CertFP|CertFP]] · [[XDCC]]</center></big>

<big><center>'''Games''' 
[http://idlerpg.xertion.org IdleRPG] · [[Werewolf]]</center></big>

2016-01-24T01:33:39Z

Kaishiro:

2013-09-18T16:13:57Z

Kaishiro: Mikio delinked, Tessa changing providers and location

===Disclaimer===
You should always try connecting via [irc://irc.xertion.org '''irc.xertion.org'''] before attempting to connect to any of the following servers. If the domain of the server listed cannot be resolved, don't ask for the IP, as we don't give out the IP for any of the servers.

===Ports===
Use '''6660-6669''', '''7000''' for standard connections and '''6697''', '''9998-9999''' for secure (SSL) connections. Other ports may be available upon request.

===IPv6===
The IPv6 connection address is [irc://irc6.xertion.org '''irc6.xertion.org''']. Again, always attempt to use this address before connecting to individual IPv6 servers.

===Servers===

====North America====
'''Round Robin:''' [irc://irc.us.xertion.org irc.us.xertion.org]

{| border="1" cellpadding="5" align="center" width="60%" cellspacing="1" style="border: 1px solid #000000; border-collapse: collapse;"
|-
|-
! style="background-color:#4080FF;"|Address
! style="background-color:#4080FF;"|Location
! style="background-color:#4080FF;"|IPv6
! style="background-color:#4080FF;"|Server Owner
|-
| [irc://chibi.xertion.org chibi.xertion.org]
| Beauharnois, Quebec, CA
| Yes
| [[User:Rilly|Rilly]]
|-
| [irc://hazuki.xertion.org hazuki.xertion.org]
| Los Angeles, California, US
| Yes
| [[User:White_Wolf|White_Wolf]]
|-
| [irc://iris.xertion.org iris.xertion.org]
| Chicago, Illinois, US
| No
| [[User:Usagi_Tsukino|Usagi_Tsukino]]
|-
| [irc://rena.xertion.org rena.xertion.org]
| Seattle, Washington, US
| Yes
| [[User:Sakura|Sakura`Kinomoto]]
|-
| [irc://xana.xertion.org xana.xertion.org]
| Denver, Colorodo, US
| Yes
| [[User:White_Wolf|White_Wolf]]
|-
|}

====Europe====
'''Round Robin:''' [irc://irc.eu.xertion.org irc.eu.xertion.org]

{| border="1" cellpadding="5" align="center" width="60%" cellspacing="1" style="border: 1px solid #00000; border-collapse: collapse;"
|-
|-
! style="background-color:#4080FF;"|Address
! style="background-color:#4080FF;"|Location
! style="background-color:#4080FF;"|IPv6
! style="background-color:#4080FF;"|Server Owner
|-
| [irc://blair.xertion.org blair.xertion.org]
| Falkenstein, Germany, EU
| Yes
| [[User:Valdearg|Valdearg]]
|-
| [irc://kusano.xertion.org kusano.xertion.org]
| Clermont-Ferrand, France, EU
| Yes
| [[User:Koby|Koby]]
|-
| [irc://zelos.xertion.org zelos.xertion.org]
| Paris, France, EU
| Yes
| [[User:AkaSoldats|akaSoldats]]
|-
| [irc://vyatta.xertion.org vyatta.xertion.org]
| Amsterdam, Netherlands, EU
| Yes
| [[User:Rails|rails]]
|-
|}

[[Category:General]]

Channel management

2013-08-29T10:19:31Z

Kaishiro: /* xOP */

== Types of Commands ==

* '''Fantasy commands''' are commands initiated with a period. "."
* Commands in this guide will be given in both the <code>/msg</code> format, and the fantasy command format.

Okay, so most things related to channel management are controlled via [[ChanServ]], part of Anope IRC services, the system we use on Xertion.

Commands to [[ChanServ]] can be given in a number of ways:
* Messages: <code>/msg ChanServ [command] [variable]</code>
* Fantasy: <code>.[command] [variable]</code>

==Owner Mode and Protect Mode==
When ''Owner Mode'' is set, Services will set +qo ('''~''') on founders when they join their channel.
Users with the ('''~''') cannot be kicked by admins ('''&''') ops ('''@''') or halfops ('''%''')

When ''Protect Mode'' is set, Services will set +ao ('''&''') on admins when they join the channel.
Users with the ('''&''') cannot be kicked by ops ('''@''') or halfops ('''%''')

By default, Owner Mode and Protect Mode are turned off for newly registered channels.

If you would like to turn these prefixes on, type the following:
* <code>/msg ChanServ SET #moo OWNERMODE ON
* /msg ChanServ SET #moo PROTECTMODE ON</code>

==Managing Channel Access==
===Adding Access===
====Access Levels====
Administrators and operators are an important part of a channel. You've probably seen them around, with the '''&''' (Admin) or '''@''' (Op) in front of their name on some of our larger channels. Now, how do you assign them?
* <code>/msg ChanServ ACCESS #moo ADD Elchzard level
* .access add Elchzard level</code>

<pre>Level = A number between 3 and 9999 inclusive.
Level 3 -- Gives user voice (+).
Level 4 -- Gives user half-operator (%) status.
Levels 5 - 9 -- Gives user operator (@) status.
Levels 10 - 9998 -- Gives user administrator (&) status.
Level 9999 -- Gives user co-founder (~) status.</pre>

For fantasy commands using .access, there is also a shortcut available - <code>.axx</code>

So one of the access commands would be -- <code>.axx add Elchzard level</code>

====xOP====
If you're confused by access levels, xOP might be easier for you. Rather than using 9996 different levels, there are four:

{{Note|Turning xOP ON will no longer allow usage of the access levels system.}}

* SOP - SuperOP -- Equivalent to admin status, &, or levels 10-9998
* AOP - AutoOP -- Equivalent to operator status, @, or levels 5-9.
* HOP - HalfOP -- Equivalent to half-op status, %, or level 4.
* VOP - VOicePerson -- Equivalent to voice, +, or level 3.

To turn on the xOP system, you need to use one ChanServ command, and then you're good to go with assigning your operators.
* Turn on XOP -- <code>/msg ChanServ SET #moo XOP on</code>
* Assign SOPs -- <code>/msg ChanServ SOP #moo add Elchzard</code>
* Assign AOPs -- <code>/msg ChanServ AOP #moo add Elchzard</code>
* Assign HOPs -- <code>/msg ChanServ HOP #moo add Elchzard</code>
* Assign VOPs -- <code>/msg ChanServ VOP #moo add Elchzard</code>

Or using fantasy commands...
* Turn on XOP -- <code>.set xop on</code>
* Assign SOPs -- <code>.sop add Elchzard</code>
* Assign AOPs -- <code>.aop add Elchzard</code>
* Assign HOPs -- <code>.hop add Elchzard</code>
* Assign VOPs -- <code>.vop add Elchzard</code>

===Removing Access===
If ever the sad time comes when you need to remove a user's status on a channel, then it's equally as simple as giving the person ops in the first place. Also, if you want to change from xOP back to the normal access list system, it's simple.
* <code>/msg ChanServ ACCESS #moo DEL Sakura`Kinomoto</code> -- This will remove a users access on a channel.
* <code>/msg ChanServ ''X''OP #moo DEL Sakura`Kinomoto</code> -- Replace "X" with S, A, H or V to reflect the users current position - This command will then remove a users access on a channel when using the xOP system.
* <code>/msg ChanServ SET #moo XOP off</code> -- Will move you from xOP back to the normal access list system.

Alternatively, use our good old friends fantasy commands...
* <code>.access del Sakura`Kinomoto</code> -- This will remove a users access on a channel.
* <code>.XOP del Sakura`Kinomoto</code> -- Replace "X" with S, A, H or V to reflect the users current position - This command will then remove a users access on a channel when using the xOP system.
* <code>.set XOP off</code> -- Will move you from xOP back to the normal access list system.

==Channel Modes==
To enable a mode, simply type this...
* <code>/mode #moo +''Mode letter''</code>
Or, to remove a mode...
* <code>/mode #moo -''Mode letter''</code>

So, now, some commonly used modes:
* Block all messages containing colour codes - +c
* Strip colour, bold, italics, underline (making them appear as plain text) - +S
* Makes a channel secret, hiding it from the "/list" command - +s
* Adds a channel password - +k cows (The channel password is now cows).
* Make a channel invite only. (Must be invited to enter) - +i
* Set a user-limit for your channel - +l 500 (That's a lower case "L").
* Moderate a channel - i.e, set it so only users with voice (+) and above can speak - +m
* Block messages containing over 50% capitals, when they're longer than 5 characters - +B

==Banning==
Banning a user from a channel basically means they can't join it and talk there. You can ban a user with a certain nick, hostmask or ident from the channel.
* To ban a user's hostmask, (the most effective way) - <code>/mode #moo +b *!*@xertion-moo.moomoo-moo</code>
* To ban a user's nick - <code>/mode #moo +b MooMooGirl!*@*</code>
* To ban a user's ident - <code>/mode #moo +b *!Moo@*</code>

Or, with fantasy commands -
* For a hostmask - <code>.ban *!*@xertion-moo.moomoo-moo</code>
* For a nick - <code>.ban MooMooGirl!*@*</code>
* For an ident - <code>.ban *!Moo@*</code>

===Extended Bans===
Is that guy just changing his nick that '''''bit''''' too much? Is the dude there talking too often for your liking? Well, that's all solvable too!
Extended bans allow you to control a user's actions within your channel very finely.
Bear in mind, though, that most of these bans don't work on users with voice, or above.
* Mutes, or m: bans - Prevent a user from talking in the channel.
* No nick-changes, or N: bans - Prevent a user from changing their nick.
* Caps-bans, or B: bans - Prevent a specific user from using more than 50% caps in messages over 5 characters.
* Kick-block, or Q: bans - Prevent a specific user from making kicks (DOES work on hops and ops).
* Colour-strips, or S: bans - Strips colour from a specific user's messages.
* Colour-blocks, or c: bans - Prevents a user from sending messages containing mIRC colour codes.

So, how do you implement these?

The simplest for most of these is to grab the users hostmask, and then type this:
<pre>/mode #moo +b N:*!*@xertion-moo.moomoo-moo</pre>

Obviously, you have to change the example to the correct values for your purpose.

So essentially, you use the method above for a classic ban, and add a colon, preceded by the letter of the extban you want to use at the front of the identifier for the user.

Bear in mind that these extended bans don't work with the ".ban" fantasy command.

Mute, however, does have its own fantasy command - <code>.mute MooCow</code>

==Miscellaneous==
* <code>/whois MooCow</code> - Will give you general information about a user, as well as their '''hostmask''', which you can take from the whois data, for easy use in a ban or extended ban.
* <code>/list</code> - Will give you a list of all the network's channels that don't have +s or +p active.

See also: [[Channel Modes]], [[ChanServ]], [[Channel Management (cont.)]]

[[Category:Tutorials]]
[[Category:Services]]
[[Category:Commands]]