|
@@ -191,7 +191,7 @@ The only major distribution that currently packages Ergo is Arch Linux; the afor
|
191
|
191
|
1. Confirm that the service started correctly with `systemctl status ergo.service`
|
192
|
192
|
|
193
|
193
|
|
194
|
|
-On a non-systemd system, ergo can be configured to log to a file and used [logrotate(8)](https://linux.die.net/man/8/logrotate), since it will reopen its log files (as well as rehashing the config file) upon receiving a SIGHUP. To rehash manually outside the context of log rotation, you can use `killall -HUP ergo` or `pkill -HUP ergo`.
|
|
194
|
+On a non-systemd system, ergo can be configured to log to a file and used [logrotate(8)](https://linux.die.net/man/8/logrotate), since it will reopen its log files (as well as rehashing the config file) upon receiving a SIGHUP. To rehash manually outside the context of log rotation, you can use `killall -HUP ergo` or `pkill -HUP ergo`. See [distrib/init](https://github.com/ergochat/ergo/tree/master/distrib/init) for init scripts and related tools for non-systemd systems.
|
195
|
195
|
|
196
|
196
|
|
197
|
197
|
## Using valid TLS certificates
|
|
@@ -257,7 +257,7 @@ If you want to use a TLS client certificate instead of a password to authenticat
|
257
|
257
|
|
258
|
258
|
/NS REGISTER *
|
259
|
259
|
|
260
|
|
-Once you've registered, you'll need to set up SASL to login. One of the more complete SASL instruction pages is Freenode's page [here](https://freenode.net/kb/answer/sasl). Open up that page, find your IRC client and then setup SASL with your chosen username and password!
|
|
260
|
+Once you've registered, you'll need to set up SASL to login. One of the more complete SASL instruction pages is libera.chat's page [here](https://libera.chat/guides/sasl). Open up that page, find your IRC client and then setup SASL with your chosen username and password!
|
261
|
261
|
|
262
|
262
|
If your client doesn't support SASL, you can typically use the "server password" (`PASS`) field in your client to log into your account automatically when connecting. Set the server password to `accountname:accountpassword`, where `accountname` is your account name and `accountpassword` is your account password.
|
263
|
263
|
|
|
@@ -273,7 +273,7 @@ In this mode (the default), registering an account gives you privileges over the
|
273
|
273
|
1. You must use your nickname, i.e., if you are logged into your account, then the server will require you to use your account name as your nickname
|
274
|
274
|
1. If you unregister your account, your nickname will be permanently unreclaimable (thus preventing people from impersonating you)
|
275
|
275
|
|
276
|
|
-In this mode, it is very important that end users authenticate to their accounts as part of the initial IRC handshake (traditionally referred to as "connection registration"); otherwise they will not be able to use their registered nicknames. The preferred mechanism for this is [SASL](https://freenode.net/kb/answer/sasl), which is supported by most modern clients. As a fallback, this can also be done via the `PASS` (server password) command; set the "server password" field of the client to `AzureDiamond:hunter2`, where `AzureDiamond` is the account name and `hunter2` is the account password.
|
|
276
|
+In this mode, it is very important that end users authenticate to their accounts as part of the initial IRC handshake (traditionally referred to as "connection registration"); otherwise they will not be able to use their registered nicknames. The preferred mechanism for this is [SASL](https://libera.chat/guides/sasl), which is supported by most modern clients. As a fallback, this can also be done via the `PASS` (server password) command; set the "server password" field of the client to `AzureDiamond:hunter2`, where `AzureDiamond` is the account name and `hunter2` is the account password.
|
277
|
277
|
|
278
|
278
|
As an end user, if you want to change your nickname, you can register a new account and transfer any channel ownerships to it using `/msg ChanServ transfer`.
|
279
|
279
|
|
|
@@ -336,7 +336,9 @@ By default, account registrations complete immediately and do not require a veri
|
336
|
336
|
key-file: "dkim.pem"
|
337
|
337
|
```
|
338
|
338
|
|
339
|
|
-You must create the corresponding TXT record `20200229._domainkey.my.network` to hold your public key. You can also use an MTA ("relay" or "smarthost") to send the email, in which case DKIM signing can be deferred to the MTA; see the example config for details.
|
|
339
|
+You must create the corresponding TXT record `20200229._domainkey.my.network` to hold your public key.
|
|
340
|
+
|
|
341
|
+You can also use an external SMTP server ("MTA", "relay", or "smarthost") to send the email, in which case DKIM signing can be deferred to that server; see the `mta` section of the example config for details.
|
340
|
342
|
|
341
|
343
|
|
342
|
344
|
## Channel Registration
|
|
@@ -544,6 +546,12 @@ Under these circumstances, users can follow the following steps:
|
544
|
546
|
|
545
|
547
|
Similarly, for a public channel (one without `+i`), users can ban nick/account names with `/mode #example +b bob`. (To restrict the channel to users with valid accounts, set it to registered-only with `/mode #example +R`.)
|
546
|
548
|
|
|
549
|
+
|
|
550
|
+## How do I send an announcement to all connected users?
|
|
551
|
+
|
|
552
|
+Ergo supports a simplified form of the "global notice" or "wallops" capabilities found in other ircds. With the `massmessage` operator capability, you can `/NOTICE $$* text of your announcement`, and it will be sent to all connected users. If you have human-readable hostnames enabled (in the default/recommended configuration they are not), you can also `/NOTICE $#wild*card.host.name`.
|
|
553
|
+
|
|
554
|
+
|
547
|
555
|
-------------------------------------------------------------------------------------------
|
548
|
556
|
|
549
|
557
|
|