DWIRC:Security & SASL Auth: Difference between revisions
m Protected "DWIRC:Security & SASL Auth" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) [cascading] |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{DWIRC_Guides}} | {{DWIRC_Guides}} | ||
{{DISPLAYTITLE:DWIRC: TLS & SASL Authentication}} | |||
__TOC__ | |||
= 🔐 TLS & SASL Authentication = | |||
Protecting your connection and IRC account is important when using the | |||
DarkWorld IRC Network. | |||
This guide explains how to: | |||
* Connect securely using TLS encryption. | |||
* Verify the IRC server certificate. | |||
* Authenticate automatically using SASL. | |||
* Protect your NickServ password. | |||
* Troubleshoot common TLS and SASL problems. | |||
== | == DarkWorld IRC connection settings == | ||
= | {| class="wikitable" | ||
! Setting | |||
! Value | |||
|- | |||
| Network name | |||
| DarkWorld | |||
|- | |||
| IRC server | |||
| <code>irc.darkworld.network</code> | |||
|- | |||
| Secure port | |||
| <code>6697</code> | |||
|- | |||
| Encryption | |||
| TLS enabled | |||
|- | |||
| Certificate verification | |||
| Enabled | |||
|- | |||
| SASL mechanism | |||
| <code>PLAIN</code> | |||
|- | |||
| SASL username | |||
| Your registered NickServ account name | |||
|- | |||
| SASL password | |||
| Your NickServ account password | |||
|} | |||
{{Note|Some IRC clients still use the older term “SSL.” When an IRC client offers an “SSL” connection option, it normally refers to a TLS-secured connection.}} | |||
'''Recommended connection address:''' | |||
<pre> | |||
irc.darkworld.network:6697 | |||
</pre> | |||
Always enable TLS and certificate verification. Do not accept an unexpected | |||
certificate warning without first checking the server address and contacting | |||
DarkWorld IRC support. | |||
= 🔒 What is TLS? = | |||
TLS stands for '''Transport Layer Security'''. | |||
TLS encrypts the connection between your IRC client and the DarkWorld IRC | |||
server. It helps prevent other parties on the network path from reading or | |||
modifying data travelling between your device and the IRC server. | |||
A secure DarkWorld IRC connection should use: | |||
* Server: <code>irc.darkworld.network</code> | |||
* Port: <code>6697</code> | |||
* TLS or SSL option: enabled | |||
* Certificate verification: enabled | |||
TLS protects data while it is travelling between your device and the IRC | |||
server. It does not make public channel messages private and does not replace | |||
good password, account or device security. | |||
== TLS and the PLAIN SASL mechanism == | |||
The SASL mechanism used by most IRC clients is called <code>PLAIN</code>. | |||
The name does not mean the entire IRC connection is unencrypted. It means the | |||
SASL credentials must be protected by the encrypted TLS connection. | |||
For this reason, only use SASL PLAIN when: | |||
* TLS is enabled. | |||
* The connection uses port <code>6697</code>. | |||
* The server certificate is valid. | |||
* Certificate verification is enabled. | |||
Never configure SASL PLAIN over an unencrypted IRC connection. | |||
== Certificate warnings == | |||
If your IRC client reports that the certificate is expired, untrusted or does | |||
not match <code>irc.darkworld.network</code>: | |||
# Do not disable certificate verification. | |||
# Do not permanently accept the unexpected certificate. | |||
# Confirm that the server address is exactly <code>irc.darkworld.network</code>. | |||
# Confirm that the port is <code>6697</code>. | |||
# Confirm that your device date, time and timezone are correct. | |||
# Update your IRC client and operating-system certificate store. | |||
# Contact DarkWorld IRC support if the warning continues. | |||
When asking for help, provide the exact certificate error. Do not include any | |||
password, authentication token, private key or recovery code. | |||
= 🔑 What is SASL? = | |||
SASL stands for '''Simple Authentication and Security Layer'''. | |||
SASL authenticates your registered NickServ account while the IRC connection | |||
is being established. This normally identifies your account before automatic | |||
channel joins and before commands requiring an identified account are used. | |||
SASL is safer and more reliable than placing a NickServ | |||
<code>IDENTIFY</code> command in an automatic perform list. | |||
To use SASL, you must already have a registered DarkWorld NickServ account. | |||
Your SASL username should be your registered NickServ account name. It may be | |||
different from the nickname currently displayed by your IRC client. | |||
{{Warning|Never post your NickServ password in a channel, private message, support request, screenshot or staff report. DarkWorld staff will never ask you to reveal your password.}} | |||
= 🧩 SASL setup by IRC client = | |||
== mIRC == | |||
=== Graphical setup === | |||
# Open '''Tools → Options'''. | |||
# Select '''Connect → Servers'''. | |||
# Add a new server entry or edit your existing DarkWorld entry. | |||
# Enter <code>irc.darkworld.network</code> as the server address. | |||
# Enter <code>+6697</code> as the port. | |||
# Select '''SASL''' as the login method. | |||
# Enter your registered NickServ account name as the SASL username. | |||
# Enter your NickServ password as the login password. | |||
# Save the server entry and connect. | |||
The plus sign before <code>6697</code> tells mIRC to establish a secure | |||
connection. | |||
{| class="wikitable" | |||
! mIRC field | |||
! Value | |||
|- | |||
| Description | |||
| DarkWorld | |||
|- | |||
| Address | |||
| <code>irc.darkworld.network</code> | |||
|- | |||
| Port | |||
| <code>+6697</code> | |||
|- | |||
| Login method | |||
| SASL | |||
|- | |||
| SASL username | |||
| Your registered NickServ account name | |||
|- | |||
| Login password | |||
| Your NickServ account password | |||
|} | |||
Do not enable any option that bypasses an invalid server certificate. | |||
=== mIRC connection command === | |||
Advanced users may connect with: | |||
<pre> | |||
/server -e irc.darkworld.network 6697 -l sasl YourNickServPassword -lname YourAccount | |||
</pre> | |||
Replace: | |||
* <code>YourAccount</code> with your registered NickServ account name. | |||
* <code>YourNickServPassword</code> with your NickServ password. | |||
Using the graphical server configuration is recommended because entering a | |||
password in a visible command can expose it through screenshots, command | |||
history or accidental pasting. | |||
== HexChat == | |||
# Open '''HexChat → Network List'''. | |||
# Select '''DarkWorld''' and choose '''Edit'''. | |||
# Add <code>irc.darkworld.network/6697</code> to the server list. | |||
# Enable '''Use SSL for all servers on this network'''. | |||
# Keep the option that accepts invalid certificates disabled. | |||
# Enter your normal nickname. | |||
# Select '''SASL (username + password)''' as the login method. | |||
# Enter your registered NickServ account name as the username. | |||
# Enter your NickServ password. | |||
# Save the configuration and connect. | |||
{{Note|HexChat 2.16.2 was announced as its final release. Existing users should keep their installation updated and consider moving to a maintained IRC client for long-term use.}} | |||
== WeeChat == | |||
=== Add the DarkWorld server === | |||
Use the following commands: | |||
<pre> | |||
/server add darkworld irc.darkworld.network/6697 -tls | |||
/set irc.server.darkworld.tls_verify on | |||
/set irc.server.darkworld.sasl_mechanism plain | |||
/set irc.server.darkworld.sasl_username "YourAccount" | |||
</pre> | |||
Replace <code>YourAccount</code> with your registered NickServ account name. | |||
=== Store the password securely === | |||
Store the NickServ password in WeeChat secure data instead of placing it | |||
directly in the server configuration: | |||
<pre> | |||
/secure passphrase YourEncryptionPassphrase | |||
/secure set darkworld_password YourNickServPassword | |||
/set irc.server.darkworld.sasl_password "${sec.data.darkworld_password}" | |||
/save | |||
/connect darkworld | |||
</pre> | |||
Replace: | |||
* <code>YourEncryptionPassphrase</code> with a strong passphrase used to protect WeeChat secure data. | |||
* <code>YourNickServPassword</code> with your NickServ password. | |||
Do not reuse your NickServ password as the WeeChat secure-data passphrase. | |||
Enter these commands only in WeeChat's command-input area. Never enter them | |||
in a channel or private-message window. | |||
== Irssi == | |||
Add the DarkWorld network with native SASL support: | |||
<pre> | |||
/NETWORK ADD -sasl_mechanism PLAIN -sasl_username YourAccount -sasl_password YourNickServPassword DarkWorld | |||
/SERVER ADD -auto -tls -tls_verify -network DarkWorld irc.darkworld.network 6697 | |||
/SAVE | |||
/CONNECT DarkWorld | |||
</pre> | |||
Replace: | |||
* <code>YourAccount</code> with your registered NickServ account name. | |||
* <code>YourNickServPassword</code> with your NickServ password. | |||
The <code>-tls</code> option enables TLS. The <code>-tls_verify</code> | |||
option enables certificate verification. | |||
Irssi may store the SASL password in its configuration file. Protect the | |||
account running Irssi and ensure that other users cannot read the | |||
configuration file. | |||
On a shared shell service, follow the provider's approved secure | |||
configuration procedure. Do not change file permissions or store credentials | |||
in shared locations without authorization. | |||
= ✅ Verify TLS and SASL = | |||
== Verify the TLS connection == | |||
After connecting, check the server or status window. | |||
Confirm that: | |||
* The server is <code>irc.darkworld.network</code>. | |||
* The port is <code>6697</code>. | |||
* The connection uses TLS. | |||
* Certificate verification succeeded. | |||
* No certificate warning was displayed. | |||
Some clients display a padlock icon for secure connections. A padlock is | |||
helpful, but you should also inspect the connection information in the | |||
client's server or status window. | |||
== Verify SASL authentication == | |||
A successful SASL connection may display a message similar to: | |||
<pre> | |||
You are now logged in as YourAccount | |||
</pre> | |||
You can also check your current identity with: | |||
<pre> | |||
/WHOIS YourNickname | |||
</pre> | |||
Replace <code>YourNickname</code> with your current IRC nickname. | |||
Look for account information showing that the nickname is logged in to your | |||
registered account. | |||
Do not include your password in a <code>WHOIS</code> command. | |||
== What successful authentication means == | |||
Successful SASL authentication confirms that your IRC connection has logged | |||
in to the specified NickServ account. | |||
It does not grant: | |||
* IRC operator access. | |||
* Channel operator access. | |||
* Staff authority. | |||
* Access to another DarkWorld project. | |||
* Permission to bypass network or channel rules. | |||
All access remains subject to the account's existing permissions and | |||
DarkWorld IRC policies. | |||
= 🛠 Troubleshooting = | |||
== SASL authentication failed == | |||
Check the following: | |||
# The NickServ account is already registered. | |||
# The SASL username is the registered account name, not necessarily the nickname currently displayed. | |||
# The password is correct and uses the correct capitalization. | |||
# The SASL mechanism is set to <code>PLAIN</code>. | |||
# TLS is enabled. | |||
# The connection uses port <code>6697</code>. | |||
# Certificate verification is enabled and succeeds. | |||
# There are no accidental spaces before or after the username or password. | |||
# The account is not suspended, unconfirmed or otherwise restricted. | |||
# The IRC client supports SASL. | |||
If you recently changed your NickServ password, update the stored SASL | |||
password in every IRC client, bot and bouncer that uses the account. | |||
== Connection succeeds but SASL does not == | |||
The IRC client may be connecting without sending SASL credentials. | |||
Confirm that: | |||
* SASL is enabled for the DarkWorld network entry. | |||
* The login method is set to SASL. | |||
* The username and password are saved under the correct network. | |||
* The client is not using a duplicate DarkWorld server entry. | |||
* The client is not relying on an old NickServ perform command. | |||
* The registered account name is being used as the SASL username. | |||
Remove outdated automatic identification commands after SASL has been | |||
configured successfully. | |||
== Nickname and account name are different == | |||
Your current nickname and registered account name do not always need to be | |||
identical. | |||
For example: | |||
{| class="wikitable" | |||
! Field | |||
! Example | |||
|- | |||
| Current nickname | |||
| <code>DarkUser-Away</code> | |||
|- | |||
| Registered account | |||
| <code>DarkUser</code> | |||
|- | |||
| SASL username | |||
| <code>DarkUser</code> | |||
|} | |||
Use the registered account name as the SASL username. | |||
== TLS certificate error == | |||
Do not bypass the certificate warning. | |||
Confirm: | |||
* Server: <code>irc.darkworld.network</code> | |||
* Port: <code>6697</code> | |||
* TLS: enabled | |||
* Certificate verification: enabled | |||
* Device date and time: correct | |||
* IRC client: updated | |||
* Operating system: updated | |||
If the error continues, contact DarkWorld IRC support and provide: | |||
* IRC client name and version. | |||
* Operating system. | |||
* Server address. | |||
* Port number. | |||
* Exact certificate error. | |||
Never provide passwords, authentication tokens, private keys or recovery | |||
codes. | |||
== Password accidentally exposed == | |||
A password is exposed if it is posted or stored somewhere unauthorized, | |||
including: | |||
* A public IRC channel. | |||
* A private message. | |||
* A support request. | |||
* A staff report. | |||
* A screenshot. | |||
* A public paste. | |||
* A shared configuration file. | |||
* A publicly accessible log. | |||
If your NickServ password is exposed: | |||
# Do not repeat, quote or copy the exposed password. | |||
# Change the NickServ password immediately using the password-change procedure documented by DarkWorld IRC Services. | |||
# Update the saved SASL password in every authorized IRC client, bot and bouncer. | |||
# Report the exposure through the approved DarkWorld support or security channel. | |||
# Review connected sessions and unexpected account activity where possible. | |||
# Change the password of any other account that reused the same password. | |||
# Remove or restrict access to the exposed content where authorized. | |||
Never reuse your NickServ password for email, websites, shell accounts, | |||
bots, staff portals or other services. | |||
= 🛡 Account and device security = | |||
== Account security recommendations == | |||
* Use a strong and unique NickServ password. | |||
* Store passwords in a reputable password manager. | |||
* Use TLS and SASL on every connection. | |||
* Enable MFA on related email, staff and project accounts wherever supported. | |||
* Never share account credentials. | |||
* Never send passwords through IRC messages. | |||
* Remove obsolete automatic NickServ identification commands. | |||
* Remove unused client and bouncer configurations. | |||
* Report suspected credential exposure immediately. | |||
== Device security recommendations == | |||
* Keep the operating system updated. | |||
* Keep the IRC client updated. | |||
* Use a supported IRC client. | |||
* Enable automatic screen locking. | |||
* Protect the device with a password, PIN or equivalent authentication. | |||
* Do not allow unauthorized people to use a privileged IRC session. | |||
* Use appropriate anti-malware protection where applicable. | |||
* Encrypt the device storage where supported. | |||
* Back up recovery information securely. | |||
* Avoid using privileged IRC accounts on public or untrusted devices. | |||
= 👥 Additional requirements for staff and trainees = | |||
DarkWorld IRC staff members and trainees must: | |||
* Use TLS for every staff-related IRC connection. | |||
* Use SASL where supported. | |||
* Use an approved and securely configured IRC client. | |||
* Protect staff and Services credentials. | |||
* Report suspected credential exposure immediately. | |||
* Keep privileged access separate from ordinary testing where required. | |||
* Follow the principle of least privilege. | |||
* Never request a user's password. | |||
* Never copy a user's exposed password into a report. | |||
* Follow approved account-recovery and incident-reporting procedures. | |||
Acceptance into staff training does not itself grant staff authority or | |||
privileged access. | |||
= ❓ Getting help = | |||
If you cannot configure TLS or SASL, ask for assistance in the official | |||
DarkWorld IRC support channel. | |||
When requesting help, provide: | |||
* IRC client name and version. | |||
* Operating system. | |||
* Server address and port. | |||
* The exact error message. | |||
* Whether the problem involves TLS, SASL or both. | |||
* Whether the problem occurs during connection or authentication. | |||
'''Never provide your password, authentication token, recovery code, | |||
private key or password-manager information.''' | |||
= 🧭 Next steps = | |||
After securing your connection and account, continue with: | |||
* [[DWIRC:Getting Started|Getting Started]] | |||
* [[DWIRC:IRC Client Setup|IRC Client Setup]] | |||
* [[DWIRC:Mobile Connection Guide|Mobile Connection Guide]] | |||
* [[DWIRC:Channel Management Tips|Channel Management Tips]] | |||
= References = | |||
* [https://www.mirc.com/help/html/connect.html mIRC connection and SASL documentation] | |||
* [https://www.mirc.com/help/html/mirc_commands.html mIRC server command documentation] | |||
* [https://weechat.org/doc/ WeeChat official documentation] | |||
* [https://irssi.org/documentation/help/1.4/network/ Irssi network and SASL documentation] | |||
* [https://irssi.org/documentation/help/connect/ Irssi TLS connection documentation] | |||
* [https://hexchat.github.io/ HexChat official website] | |||
* [https://www.anope.org/upgrading.html Anope 2.0 to 2.1 upgrade documentation] | |||
{{DWFooter}} | {{DWFooter}} | ||
Latest revision as of 01:42, 17 August 2026
📘 DWIRC Guides & Tutorials
Guides
Security
Channel Management
📚 Learn to Connect, Secure, and Manage Your IRC Experience
🔐 TLS & SASL Authentication
Protecting your connection and IRC account is important when using the DarkWorld IRC Network.
This guide explains how to:
- Connect securely using TLS encryption.
- Verify the IRC server certificate.
- Authenticate automatically using SASL.
- Protect your NickServ password.
- Troubleshoot common TLS and SASL problems.
DarkWorld IRC connection settings
| Setting | Value |
|---|---|
| Network name | DarkWorld |
| IRC server | irc.darkworld.network
|
| Secure port | 6697
|
| Encryption | TLS enabled |
| Certificate verification | Enabled |
| SASL mechanism | PLAIN
|
| SASL username | Your registered NickServ account name |
| SASL password | Your NickServ account password |
Recommended connection address:
irc.darkworld.network:6697
Always enable TLS and certificate verification. Do not accept an unexpected certificate warning without first checking the server address and contacting DarkWorld IRC support.
🔒 What is TLS?
TLS stands for Transport Layer Security.
TLS encrypts the connection between your IRC client and the DarkWorld IRC server. It helps prevent other parties on the network path from reading or modifying data travelling between your device and the IRC server.
A secure DarkWorld IRC connection should use:
- Server:
irc.darkworld.network - Port:
6697 - TLS or SSL option: enabled
- Certificate verification: enabled
TLS protects data while it is travelling between your device and the IRC server. It does not make public channel messages private and does not replace good password, account or device security.
TLS and the PLAIN SASL mechanism
The SASL mechanism used by most IRC clients is called PLAIN.
The name does not mean the entire IRC connection is unencrypted. It means the SASL credentials must be protected by the encrypted TLS connection.
For this reason, only use SASL PLAIN when:
- TLS is enabled.
- The connection uses port
6697. - The server certificate is valid.
- Certificate verification is enabled.
Never configure SASL PLAIN over an unencrypted IRC connection.
Certificate warnings
If your IRC client reports that the certificate is expired, untrusted or does
not match irc.darkworld.network:
- Do not disable certificate verification.
- Do not permanently accept the unexpected certificate.
- Confirm that the server address is exactly
irc.darkworld.network. - Confirm that the port is
6697. - Confirm that your device date, time and timezone are correct.
- Update your IRC client and operating-system certificate store.
- Contact DarkWorld IRC support if the warning continues.
When asking for help, provide the exact certificate error. Do not include any password, authentication token, private key or recovery code.
🔑 What is SASL?
SASL stands for Simple Authentication and Security Layer.
SASL authenticates your registered NickServ account while the IRC connection is being established. This normally identifies your account before automatic channel joins and before commands requiring an identified account are used.
SASL is safer and more reliable than placing a NickServ
IDENTIFY command in an automatic perform list.
To use SASL, you must already have a registered DarkWorld NickServ account.
Your SASL username should be your registered NickServ account name. It may be different from the nickname currently displayed by your IRC client.
🧩 SASL setup by IRC client
mIRC
Graphical setup
- Open Tools → Options.
- Select Connect → Servers.
- Add a new server entry or edit your existing DarkWorld entry.
- Enter
irc.darkworld.networkas the server address. - Enter
+6697as the port. - Select SASL as the login method.
- Enter your registered NickServ account name as the SASL username.
- Enter your NickServ password as the login password.
- Save the server entry and connect.
The plus sign before 6697 tells mIRC to establish a secure
connection.
| mIRC field | Value |
|---|---|
| Description | DarkWorld |
| Address | irc.darkworld.network
|
| Port | +6697
|
| Login method | SASL |
| SASL username | Your registered NickServ account name |
| Login password | Your NickServ account password |
Do not enable any option that bypasses an invalid server certificate.
mIRC connection command
Advanced users may connect with:
/server -e irc.darkworld.network 6697 -l sasl YourNickServPassword -lname YourAccount
Replace:
YourAccountwith your registered NickServ account name.YourNickServPasswordwith your NickServ password.
Using the graphical server configuration is recommended because entering a password in a visible command can expose it through screenshots, command history or accidental pasting.
HexChat
- Open HexChat → Network List.
- Select DarkWorld and choose Edit.
- Add
irc.darkworld.network/6697to the server list. - Enable Use SSL for all servers on this network.
- Keep the option that accepts invalid certificates disabled.
- Enter your normal nickname.
- Select SASL (username + password) as the login method.
- Enter your registered NickServ account name as the username.
- Enter your NickServ password.
- Save the configuration and connect.
WeeChat
Add the DarkWorld server
Use the following commands:
/server add darkworld irc.darkworld.network/6697 -tls /set irc.server.darkworld.tls_verify on /set irc.server.darkworld.sasl_mechanism plain /set irc.server.darkworld.sasl_username "YourAccount"
Replace YourAccount with your registered NickServ account name.
Store the password securely
Store the NickServ password in WeeChat secure data instead of placing it directly in the server configuration:
/secure passphrase YourEncryptionPassphrase
/secure set darkworld_password YourNickServPassword
/set irc.server.darkworld.sasl_password "${sec.data.darkworld_password}"
/save
/connect darkworld
Replace:
YourEncryptionPassphrasewith a strong passphrase used to protect WeeChat secure data.YourNickServPasswordwith your NickServ password.
Do not reuse your NickServ password as the WeeChat secure-data passphrase.
Enter these commands only in WeeChat's command-input area. Never enter them in a channel or private-message window.
Irssi
Add the DarkWorld network with native SASL support:
/NETWORK ADD -sasl_mechanism PLAIN -sasl_username YourAccount -sasl_password YourNickServPassword DarkWorld /SERVER ADD -auto -tls -tls_verify -network DarkWorld irc.darkworld.network 6697 /SAVE /CONNECT DarkWorld
Replace:
YourAccountwith your registered NickServ account name.YourNickServPasswordwith your NickServ password.
The -tls option enables TLS. The -tls_verify
option enables certificate verification.
Irssi may store the SASL password in its configuration file. Protect the account running Irssi and ensure that other users cannot read the configuration file.
On a shared shell service, follow the provider's approved secure configuration procedure. Do not change file permissions or store credentials in shared locations without authorization.
✅ Verify TLS and SASL
Verify the TLS connection
After connecting, check the server or status window.
Confirm that:
- The server is
irc.darkworld.network. - The port is
6697. - The connection uses TLS.
- Certificate verification succeeded.
- No certificate warning was displayed.
Some clients display a padlock icon for secure connections. A padlock is helpful, but you should also inspect the connection information in the client's server or status window.
Verify SASL authentication
A successful SASL connection may display a message similar to:
You are now logged in as YourAccount
You can also check your current identity with:
/WHOIS YourNickname
Replace YourNickname with your current IRC nickname.
Look for account information showing that the nickname is logged in to your registered account.
Do not include your password in a WHOIS command.
What successful authentication means
Successful SASL authentication confirms that your IRC connection has logged in to the specified NickServ account.
It does not grant:
- IRC operator access.
- Channel operator access.
- Staff authority.
- Access to another DarkWorld project.
- Permission to bypass network or channel rules.
All access remains subject to the account's existing permissions and DarkWorld IRC policies.
🛠 Troubleshooting
SASL authentication failed
Check the following:
- The NickServ account is already registered.
- The SASL username is the registered account name, not necessarily the nickname currently displayed.
- The password is correct and uses the correct capitalization.
- The SASL mechanism is set to
PLAIN. - TLS is enabled.
- The connection uses port
6697. - Certificate verification is enabled and succeeds.
- There are no accidental spaces before or after the username or password.
- The account is not suspended, unconfirmed or otherwise restricted.
- The IRC client supports SASL.
If you recently changed your NickServ password, update the stored SASL password in every IRC client, bot and bouncer that uses the account.
Connection succeeds but SASL does not
The IRC client may be connecting without sending SASL credentials.
Confirm that:
- SASL is enabled for the DarkWorld network entry.
- The login method is set to SASL.
- The username and password are saved under the correct network.
- The client is not using a duplicate DarkWorld server entry.
- The client is not relying on an old NickServ perform command.
- The registered account name is being used as the SASL username.
Remove outdated automatic identification commands after SASL has been configured successfully.
Nickname and account name are different
Your current nickname and registered account name do not always need to be identical.
For example:
| Field | Example |
|---|---|
| Current nickname | DarkUser-Away
|
| Registered account | DarkUser
|
| SASL username | DarkUser
|
Use the registered account name as the SASL username.
TLS certificate error
Do not bypass the certificate warning.
Confirm:
- Server:
irc.darkworld.network - Port:
6697 - TLS: enabled
- Certificate verification: enabled
- Device date and time: correct
- IRC client: updated
- Operating system: updated
If the error continues, contact DarkWorld IRC support and provide:
- IRC client name and version.
- Operating system.
- Server address.
- Port number.
- Exact certificate error.
Never provide passwords, authentication tokens, private keys or recovery codes.
Password accidentally exposed
A password is exposed if it is posted or stored somewhere unauthorized, including:
- A public IRC channel.
- A private message.
- A support request.
- A staff report.
- A screenshot.
- A public paste.
- A shared configuration file.
- A publicly accessible log.
If your NickServ password is exposed:
- Do not repeat, quote or copy the exposed password.
- Change the NickServ password immediately using the password-change procedure documented by DarkWorld IRC Services.
- Update the saved SASL password in every authorized IRC client, bot and bouncer.
- Report the exposure through the approved DarkWorld support or security channel.
- Review connected sessions and unexpected account activity where possible.
- Change the password of any other account that reused the same password.
- Remove or restrict access to the exposed content where authorized.
Never reuse your NickServ password for email, websites, shell accounts, bots, staff portals or other services.
🛡 Account and device security
Account security recommendations
- Use a strong and unique NickServ password.
- Store passwords in a reputable password manager.
- Use TLS and SASL on every connection.
- Enable MFA on related email, staff and project accounts wherever supported.
- Never share account credentials.
- Never send passwords through IRC messages.
- Remove obsolete automatic NickServ identification commands.
- Remove unused client and bouncer configurations.
- Report suspected credential exposure immediately.
Device security recommendations
- Keep the operating system updated.
- Keep the IRC client updated.
- Use a supported IRC client.
- Enable automatic screen locking.
- Protect the device with a password, PIN or equivalent authentication.
- Do not allow unauthorized people to use a privileged IRC session.
- Use appropriate anti-malware protection where applicable.
- Encrypt the device storage where supported.
- Back up recovery information securely.
- Avoid using privileged IRC accounts on public or untrusted devices.
👥 Additional requirements for staff and trainees
DarkWorld IRC staff members and trainees must:
- Use TLS for every staff-related IRC connection.
- Use SASL where supported.
- Use an approved and securely configured IRC client.
- Protect staff and Services credentials.
- Report suspected credential exposure immediately.
- Keep privileged access separate from ordinary testing where required.
- Follow the principle of least privilege.
- Never request a user's password.
- Never copy a user's exposed password into a report.
- Follow approved account-recovery and incident-reporting procedures.
Acceptance into staff training does not itself grant staff authority or privileged access.
❓ Getting help
If you cannot configure TLS or SASL, ask for assistance in the official DarkWorld IRC support channel.
When requesting help, provide:
- IRC client name and version.
- Operating system.
- Server address and port.
- The exact error message.
- Whether the problem involves TLS, SASL or both.
- Whether the problem occurs during connection or authentication.
Never provide your password, authentication token, recovery code, private key or password-manager information.
🧭 Next steps
After securing your connection and account, continue with:
References
- mIRC connection and SASL documentation
- mIRC server command documentation
- WeeChat official documentation
- Irssi network and SASL documentation
- Irssi TLS connection documentation
- HexChat official website
- Anope 2.0 to 2.1 upgrade documentation
Part of the DarkWorld Network Wiki Project Maintained by the DarkWorld Wiki Team
DarkWorld Network — Building an Open, Secure, and Collaborative Internet Since 2021
🌍 Connect with Us:
|
|
|
|
|
|
File:Telegram.png
Quick Links: 🏠 Home • 💬 DWIRC • 🔗 DWBouncers • 💻 DWShells • 📘 Tutorials • 📈 Stats • 🎮 Games • 🧭 Hosting
💡 Want to contribute? See How to Contribute and help build the DarkWorld knowledge base!
📅 Last Updated: 2026-08-17 • Content licensed under CC-BY-SA 4.0 unless otherwise noted.