mirror of
https://github.com/ergochat/ergo.git
synced 2024-11-21 19:39:43 +01:00
parent
e74da6c51e
commit
050e27b31b
@ -75,6 +75,8 @@ Once you have registered your account, you must configure SASL in your client, s
|
|||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
|
For information on how to use a client certificate for authentication, see the [operator manual](https://github.com/ergochat/ergo/blob/stable/docs/MANUAL.md#client-certificates).
|
||||||
|
|
||||||
# Channel registration
|
# Channel registration
|
||||||
|
|
||||||
Once you've registered your nickname, you can use it to register channels. By default, channels are ephemeral; they go away when there are no longer any users in the channel, or when the server is restarted. Registering a channel gives you permanent control over it, and ensures that its settings will persist. To register a channel, send a message to `ChanServ`:
|
Once you've registered your nickname, you can use it to register channels. By default, channels are ephemeral; they go away when there are no longer any users in the channel, or when the server is restarted. Registering a channel gives you permanent control over it, and ensures that its settings will persist. To register a channel, send a message to `ChanServ`:
|
||||||
|
@ -354,12 +354,13 @@ the result of a previous $bSENDPASS$b command.`,
|
|||||||
handler: nsCertHandler,
|
handler: nsCertHandler,
|
||||||
help: `Syntax: $bCERT <LIST | ADD | DEL> [account] [certfp]$b
|
help: `Syntax: $bCERT <LIST | ADD | DEL> [account] [certfp]$b
|
||||||
|
|
||||||
CERT examines or modifies the TLS certificate fingerprints that can be used to
|
CERT examines or modifies the SHA-256 TLS certificate fingerprints that can
|
||||||
log into an account. Specifically, $bCERT LIST$b lists the authorized
|
be used to log into an account. Specifically, $bCERT LIST$b lists the
|
||||||
fingerprints, $bCERT ADD <fingerprint>$b adds a new fingerprint, and
|
authorized fingerprints, $bCERT ADD <fingerprint>$b adds a new fingerprint, and
|
||||||
$bCERT DEL <fingerprint>$b removes a fingerprint. If you're an IRC operator
|
$bCERT DEL <fingerprint>$b removes a fingerprint. If you're an IRC operator
|
||||||
with the correct permissions, you can act on another user's account, for
|
with the correct permissions, you can act on another user's account, for
|
||||||
example with $bCERT ADD <account> <fingerprint>$b.`,
|
example with $bCERT ADD <account> <fingerprint>$b. See the operator manual
|
||||||
|
for instructions on how to compute the fingerprint.`,
|
||||||
helpShort: `$bCERT$b controls a user account's certificate fingerprints`,
|
helpShort: `$bCERT$b controls a user account's certificate fingerprints`,
|
||||||
enabled: servCmdRequiresAuthEnabled,
|
enabled: servCmdRequiresAuthEnabled,
|
||||||
minParams: 1,
|
minParams: 1,
|
||||||
|
Loading…
Reference in New Issue
Block a user