Slidge - XMPP gateways - 2025-04-22

c3p0-slidge pushed 1 commit(s) to slidgram - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/slidgram/compare/f4f7cab05..be6f425d7

c3p0-slidge pushed 1 commit(s) to matteridge - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/matteridge/compare/30f34716e..918a0fb5f

c3p0-slidge pushed 1 commit(s) to matridge - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/matridge/compare/32a8f9155..431516323

c3p0-slidge pushed 1 commit(s) to sleamdge - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/sleamdge/compare/f5181e7c0..e49159e22

c3p0-slidge pushed 1 commit(s) to slidge-whatsapp - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/slidge-whatsapp/compare/85076ac81..7a2913558

c3p0-slidge pushed 1 commit(s) to slidcord - build(lockfile): automatic update (c3p0) https://codeberg.org/slidge/slidcord/compare/c6a818edc..086e58a09

✏

Passing the secret to matridge via `--secret` exposes it to other users who can run `ps`. Is there another way of passing the secret?

Hugo: I put all options in the config file. <option>=<value>

I'll try that out.

And the only cli options is `--config <file>`

And `--server ...`, no clue why I did that :)

My confusion is because the docs indicate that --secret is a mandatory field: https://slidge.im/docs/slidge/main/admin/config/#common-config

I assume it must be defined _somewhere_. Doesn't matter if it's config file, cli args or environment variable.

morsmortium: As it turns out my matridge was severely outdated

upgrading it fixed the issue

along with many others

Hugo: --secret / secret= is a secret used for connecting to your XMPP server, that's why it's marked as mandatory

I put everything in the config file

and run slidge with -c ConfigFilePathGoesHere

> Hugo: --secret / secret= is a secret used for connecting to your XMPP server, that's why it's marked as mandatory Right. The value is mandatory, but the flag isn't mandatory. ↺

I don't mean to be pedantic about it: by indicating that the flag was mandatory I got the impression that I couldn't supply the secret in some other way.

yeah probably can lead to confusion, I agree

> I don't mean to be pedantic about it: by indicating that the flag was mandatory I got the impression that I couldn't supply the secret in some other way. You could open a merge request, clarifying that it can be set in any config area ↺

is someone here also facing issues with privileges on prosody 13.x ? i added the mod and the config as well .but slidge complaints about no privileges

I had problem installing the module on debian 12 via `prosodyctl install ...` caused by a little mismatch in supported lua version in prosody and luarocks packages.. once sorted out, it worked ✏

i reinstalled the mod under prosody 13.x and will now check if it fixes the issue

i still get "The server did not grant us privileges to get rosters

DEBUG:slixmpp.xmlstream.xmlstream:RECV: <iq xml:lang="en" id="T3MqaIbrlZSc" from="thorsten@emevth.no-ip.biz/Cheogram.O3Xv" to="whatsapp.emevth.no-ip.biz" type="set"><command xmlns="http://jabber.org/protocol/commands" node="https://slidge.im/command/core/contacts" sessionid="1745342617.3429902-9aff7af3be824ec38e39a40e38d63e7b" action="next"><x xmlns="jabber:x:data" type="submit"><title>Are you sure you want to sync your roster?</title><field label="Confirm" type="boolean" var="confirm"><value>true</value></field></x></command></iq> DEBUG:slixmpp.xmlstream.xmlstream:Event triggered: command DEBUG:slixmpp.xmlstream.xmlstream:Event triggered: command_next DEBUG:slixmpp.plugins.xep_0050.adhoc:functools.partial(<bound method AdhocProvider.__wrap_confirmation of <slidge.command.adhoc.AdhocProvider object at 0x7cb12059ef10>>, <Session of thorsten@emevth.no-ip.biz>, Confirmation(prompt='Are you sure you want to sync your roster?', handler=<bound method SyncContacts.sync of <slidge.command.user.SyncContacts object at 0x7cb1203b2490>>, success=None, handler_args=[], handler_kwargs={})) is async DEBUG:slidge.command.adhoc:Exception in <bound method SyncContacts.sync of <slidge.command.user.SyncContacts object at 0x7cb1203b2490>> Traceback (most recent call last): File "/venv/lib/python3.11/site-packages/slidge/command/adhoc.py", line 142, in __wrap_handler return await f(*a, **k) ^^^^^^^^^^^^^^^^ File "/venv/lib/python3.11/site-packages/slidge/command/user.py", line 82, in sync roster_iq = await self.xmpp["xep_0356"].get_roster(session.user_jid.bare) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/venv/lib/python3.11/site-packages/slixmpp/plugins/xep_0356/privilege.py", line 127, in get_roster raise PermissionError( PermissionError: The server did not grant us privileges to get rosters DEBUG:slidge.core.gateway:SEND: <iq xml:lang="en" id="T3MqaIbrlZSc" from="whatsapp.emevth.no-ip.biz" to="thorsten@emevth.no-ip.biz/Cheogram.O3Xv" type="error"><error type="wait"><internal-server-error xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" /><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">The server did not grant us privileges to get rosters</text></error></iq> time=2025-04-22T17:24:02.442Z level=DEBUG msg="<iq id=\"252.138-860\" to=\"s.whatsapp.net\" type=\"get\" xmlns=\"w:p\"/>" module=Slidge.Send time=2025-04-22T17:24:02.493Z level=DEBUG msg="<iq from=\"s.whatsapp.net\" id=\"252.138-860\" t=\"1745342642\" type=\"result\"/>" module=Slidge.Recv

looks like your config is wrong

(or not loaded)

that's impossible

about this Prosody installation thundergreen@EmEvTh-Data-Center:~$ sudo prosodyctl check Checking config... Public registration is enabled on: emevth.no-ip.biz If this is intentional, review our guidelines on running a public server at https://prosody.im/doc/public_servers - otherwise, consider switching to invite-based registration, which is more secure. Done. Checking DNS for component conference.emevth.no-ip.biz... Host conference.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for component discord.emevth.no-ip.biz... Host discord.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for component email.emevth.no-ip.biz... Host email.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for host emevth.no-ip.biz... Host emevth.no-ip.biz does not seem to resolve to this server (IPv6) Checking DNS for component facebook.emevth.no-ip.biz... Host facebook.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for component irc.emevth.no-ip.biz... Host irc.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for component matrix.emevth.no-ip.biz... Host matrix.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for component matteridge.emevth.no-ip.biz... Host matteridge.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for component pubsub.emevth.no-ip.biz... Host pubsub.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for component signal.emevth.no-ip.biz... Host signal.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for component telegram.emevth.no-ip.biz... Host telegram.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for component upload.emevth.no-ip.biz... Host upload.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking DNS for component whatsapp.emevth.no-ip.biz... Host whatsapp.emevth.no-ip.biz does not seem to resolve to this server (IPv4/IPv6) Checking certificates... Checking certificate for conference.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to conference.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for discord.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to discord.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for email.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to email.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for facebook.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to facebook.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for irc.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to irc.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for matrix.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to matrix.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for matteridge.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to matteridge.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for pubsub.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to pubsub.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for signal.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to signal.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for telegram.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to telegram.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for upload.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to upload.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee Checking certificate for whatsapp.emevth.no-ip.biz Certificate: /etc/prosody/certs/emevth.no-ip.biz.crt Not valid for server-to-server connections to whatsapp.emevth.no-ip.biz. DANE: TLSA 3 1 1 ca0e5622de8bb6291589e424a6b493881c9997342e8e9bd8da75c8201f205bee For more information about certificates please see https://prosody.im/doc/certificates Testing TURN service emevth.no-ip.biz:3478... 1 warnings: STUN returned a private IP! Is the TURN server behind a NAT and misconfigured? Success! Problems found, see above. thundergreen@EmEvTh-Data-Center:~$

only "normal " certificate issues due to the components