Mikaela/Limnoria-doc
1
0
Fork 0
mirror of https://github.com/Mikaela/Limnoria-doc.git synced 2024-11-28 23:39:25 +01:00
Code Issues Projects Releases Wiki Activity

identifying_to_services: Change commands to work around Charybdis/Solanum's differing protocol

Browse Source
This commit is contained in:
Valentin Lorentz 2021-06-17 19:54:36 +02:00
parent 27321d3782
commit 09943ffc54
1 changed files with 15 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
use/identifying_to_services.rst
View File

@ -24,24 +24,29 @@ First start by checking what is the syntax for registering with
Assuming that that is the syntax, we can register the bot with:: Assuming that that is the syntax, we can register the bot with::
owner ircquote nickserv register mypassword bot@example.com load Services
nickserv register mypassword bot@example.com
Or, on Limnoria versions older than 2021.06.15::
nickserv register mypassword bot@example.com
Note that the email address must be correct. Next check that Note that the email address must be correct. Next check that
``/msg nickserv info bot`` doesn't say something about being unverified. If ``/msg nickserv info bot`` doesn't say something about being unverified. If
it does, go to the email address and run:: it does, go to the email address and run::
owner ircquote nickserv VERIFY REGISTER nick <code from the email> nickserv VERIFY nick <code from the email>
Now your bot should be successfully registered and you can move to setting Now your bot should be successfully registered and you can move to setting
up automatic identifying below. If you need to identify to services now, up automatic identifying below. If you need to identify to services now,
``/msg nickserv help identify`` and following the syntax (I am still ``/msg nickserv help identify`` and following the syntax (I am still
assuming that you are on Atheme 7.x) assuming that you are on Atheme 7.x)::
``owner ircquote nickserv identify username password``.
Note: on *most* networks, ``/nickserv`` is defined as a server-side alias which nickserv IDENTIFY username password
forwards text to NickServ; this is why ``ircquote nickserv`` often will work
out of the box. On networks where this is not the case, you may need to run Note: the ``nickserv`` command was added in Limnoria 2021.06.15.
something like ``ircquote privmsg nickserv :register ...`` instead (notice If you have an older version, you need to run
something like ``ircquote privmsg nickserv :register ...`` instead (note
the placement of the ``:`` after ``nickserv`` and before the command name). the placement of the ``:`` after ``nickserv`` and before the command name).
SASL PLAIN SASL PLAIN
@ -110,7 +115,7 @@ This results in something like
``05dd01fedc1b821b796d0d785160f03e32f53fa8`` which you tell your bot to ``05dd01fedc1b821b796d0d785160f03e32f53fa8`` which you tell your bot to
tell services:: tell services::
owner ircquote NickServ cert add 05dd01fedc1b821b796d0d785160f03e32f53fa8 nickserv cert add 05dd01fedc1b821b796d0d785160f03e32f53fa8
Or if your bot identifies as you, you can do that by yourself with:: Or if your bot identifies as you, you can do that by yourself with::
@ -137,7 +142,7 @@ services about it (just like with CertFP/SASL EXTERNAL)::
config supybot.networks.<network>.sasl.username AccountName config supybot.networks.<network>.sasl.username AccountName
config supybot.networks.<network>.sasl.ecdsa_key /home/<username>/<BOT>_ecdsa.pem config supybot.networks.<network>.sasl.ecdsa_key /home/<username>/<BOT>_ecdsa.pem
ircquote nickserv set pubkey PUBKEY_WHICH_YOU_GOT_EARLIER nickserv set pubkey PUBKEY_WHICH_YOU_GOT_EARLIER
and after reconnecting, the bot should successfully identify using SASL and after reconnecting, the bot should successfully identify using SASL
ECDSA-NIST256P-CHALLENGE. ECDSA-NIST256P-CHALLENGE.