XMPP Service Operators - 2021-10-01

Can an server admin turn off omemo in a group chat ?

Probably not

soundconcept: they can block it server wide

MattJ: > Oct 01 09:59:12 s2sout564870e3f950 info Outgoing s2s stream diebesban.de->conference.jabber.org closed: No viable authentication method offered Guus: > Oct 01 09:59:25 s2sout564870ab4dd0 info Outgoing s2s stream mdosch.de->igniterealtime.org closed: No viable authentication method offered To whom it may concern: > Oct 01 09:53:40 s2sout56487184d420 info Outgoing s2s stream mdosch.de->ik.nu closed: No viable authentication method offered

I thought conference.jabber.org supports SASL EXTERNAL since it was moved to prosody… > Oct 01 10:03:12 x509 debug Cert dNSName conference.jabber.org matched hostname > Oct 01 10:03:12 s2sout5648711353d0 debug certificate identity validation result: valid > Oct 01 10:03:12 diebesban.de:watchuntrusted debug Checking certificate... > Oct 01 10:03:12 s2sout5648711353d0 debug RECV: <features xmlns='http://etherx.jabber.org/streams' xml:lang='en'><dialback xmlns='urn:xmpp:features:dialback'/></features> > Oct 01 10:03:12 s2sout5648711353d0 debug Received[s2sout_unauthed]: <features xmlns='http://etherx.jabber.org/streams' xml:lang='en'> > Oct 01 10:03:12 diebesban.de:tls debug Received features element > Oct 01 10:03:12 s2sout5648711353d0 warn No SASL EXTERNAL offer and Dialback doesn't seem to be enabled, giving up > Oct 01 10:03:12 conn190ZYDczRNsfGg3x debug Pause writes > Oct 01 10:03:12 s2sout5648711353d0 debug Disconnecting diebesban.de->conference.jabber.org[s2sout_unauthed], <stream:error> is: table: 0x5648721ba880 > Oct 01 10:03:12 s2sout5648711353d0 debug Sending[s2sout_unauthed]: <stream:error> > Oct 01 10:03:12 s2sout5648711353d0 debug SEND: <stream:error><unsupported-feature xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xmlns='urn:ietf:params:xml:ns:xmpp-streams'>No viable authentication method offered</text></stream:error> > Oct 01 10:03:12 s2sout5648711353d0 debug Sending[s2sout_unauthed]: </stream:stream>

Hello, everyone! I hope you're all well. 🙂

Martin, c.j.o might not accept your cert anymore.........

Mine? Damn, I thought it's valid…

Or you mean c.j.o is only looking at one chain?

I think that c.j.o might not have the new root in its store.

Martin: might be related that (yesterday?) I saw a change in how my Conversations fails to connect to a muc on your server from creep.im. First I was seeing the "s2s connection failed" plaque, then (and now, still) it's just the grey send button.

Different issue. Creep.im didn't use the new chain yesterday.

Martin, I just fiddled with c.j.o, any change in behaviour?

Conversations says timeout.

with c.j.o I got the last error at 9:13 CEST, so 2 hrs ago… since then no error anymore :)

Still the same: > Oct 01 11:05:19 s2sout56487215b910 warn No SASL EXTERNAL offer and Dialback doesn't seem to be enabled, giving up > Oct 01 11:05:19 s2sout56487215b910 info Outgoing s2s stream mdosch.de->conference.jabber.org closed: No viable authentication method offered

Martin: > Different issue. Creep.im didn't use the new chain yesterday. And now it does? Then yeah, there's something else failing now

Seems to have a valid chain again.

Okay, ty

Possibly unrelatedly, https://xmpp.net/result.php?domain=creep.im&type=server still says the cert is not trusted at the top (and on the badge), and then proceeds to list a valid chain. Caching issue?