Thank you for this info. On Sun, Mar 29, 2020, 8:00 AM <jdev-requ...@jabber.org> wrote:
> Send JDev mailing list submissions to > jdev@jabber.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.jabber.org/mailman/listinfo/jdev > or, via email, send a message with subject or body 'help' to > jdev-requ...@jabber.org > > You can reach the person managing the list at > jdev-ow...@jabber.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of JDev digest..." > > > Today's Topics: > > 1. [ANN] Bad XMPP - Connectivity test suite (Kim Alvefur) > 2. Re: [ANN] Bad XMPP - Connectivity test suite (Guus der Kinderen) > 3. Re: [ANN] Bad XMPP - Connectivity test suite (Jonas Sch?fer) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 28 Mar 2020 19:55:15 +0100 > From: Kim Alvefur <z...@zash.se> > To: jdev@jabber.org > Subject: [jdev] [ANN] Bad XMPP - Connectivity test suite > Message-ID: <20200328185514.str7achubcgkf...@carcharodon.zash.se> > Content-Type: text/plain; charset=us-ascii > > Hello! > > Server-to-server connectivity is not perfect today. Certificates expire, > mistakes are made in DNS zones and firewall configurations. > > In order to see how XMPP software react to such things without having to > wait for problems to pop up, I have set up a few test cases. Most of > these have some sort of configuration problem, ranging from faulty DNS > and blocked ports up to certificate problems and XMPP s2s > authentication. > > I would be happy if this leads to improved error reporting all the way > to end users. Some hint about why their messages could not be delivered > are surely better than having them disappear into the void without a > trace. Logging and reporting for service operators is also important. > > Website with list of test cases: <http://badxmpp.eu/> > > Test cases can also be listed via XEP-0030 items request: > <xmpp:badxmpp.eu?disco;type=get;request=items> > > Suggestions for additional tests are welcomed. Equivalent tests for XMPP > client connectivity is one thing I would like to add, but as a server > developer I choose to focus on s2s first. > > -- > Happy testing, > Kim "Zash" Alvefur > Prosody developer > XMPP Council > > > ------------------------------ > > Message: 2 > Date: Sat, 28 Mar 2020 21:14:52 +0100 > From: Guus der Kinderen <guus.der.kinde...@gmail.com> > To: "Jabber/XMPP software development list" <jdev@jabber.org> > Subject: Re: [jdev] [ANN] Bad XMPP - Connectivity test suite > Message-ID: > <CAMJaV9=+OKb_U075D2gqhD6kB2k5xMG=4WiEn7d9Ps5Adhu= > s...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > This is super useful. Thanks! > > Op za 28 mrt. 2020 19:58 schreef Kim Alvefur <z...@zash.se>: > > > Hello! > > > > Server-to-server connectivity is not perfect today. Certificates expire, > > mistakes are made in DNS zones and firewall configurations. > > > > In order to see how XMPP software react to such things without having to > > wait for problems to pop up, I have set up a few test cases. Most of > > these have some sort of configuration problem, ranging from faulty DNS > > and blocked ports up to certificate problems and XMPP s2s > > authentication. > > > > I would be happy if this leads to improved error reporting all the way > > to end users. Some hint about why their messages could not be delivered > > are surely better than having them disappear into the void without a > > trace. Logging and reporting for service operators is also important. > > > > Website with list of test cases: <http://badxmpp.eu/> > > > > Test cases can also be listed via XEP-0030 items request: > > <xmpp:badxmpp.eu?disco;type=get;request=items> > > > > Suggestions for additional tests are welcomed. Equivalent tests for XMPP > > client connectivity is one thing I would like to add, but as a server > > developer I choose to focus on s2s first. > > > > -- > > Happy testing, > > Kim "Zash" Alvefur > > Prosody developer > > XMPP Council > > _______________________________________________ > > JDev mailing list > > Info: https://mail.jabber.org/mailman/listinfo/jdev > > Unsubscribe: jdev-unsubscr...@jabber.org > > _______________________________________________ > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mail.jabber.org/pipermail/jdev/attachments/20200328/bdb1be24/attachment-0001.html > > > > ------------------------------ > > Message: 3 > Date: Sun, 29 Mar 2020 13:15:09 +0200 > From: Jonas Sch?fer <jo...@wielicki.name> > To: Jabber/XMPP software development list <jdev@jabber.org> > Subject: Re: [jdev] [ANN] Bad XMPP - Connectivity test suite > Message-ID: <5203905.4QTyD5tSvV@sinistra> > Content-Type: text/plain; charset="utf-8" > > On Samstag, 28. M?rz 2020 19:55:15 CEST Kim Alvefur wrote: > > Suggestions for additional tests are welcomed. > > I have a few! > > - Outright bogus DNSSEC > - Expired DNSSEC > - SRV record pointing at the root zone (`.`) mixed into other SRV records > - Only a single SRV record pointing at the root zone (`.`) > - Only DH suites with short (<1024 bits) DH parameters > - Only "export" ciphers > > Not necessarily bad, but would be good as test cases either way: > > - DNSSEC-signed SRV record pointing at a hostname different from the > domain > name and the service only has a certificate for that hostname. This is > valid > from my understanding, but probably without widespread support. > - No SRV record, only A/AAAA records. > > > Echo-ing what moparisthebest suggested in xsf@:? > > - xmpps-server records where one of which points at an HTTPS port (with a > valid one pointing at XMPPS) > > > Thanks for this service! > > > kind regards, > Jonas > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > JDev mailing list > JDev@jabber.org > https://mail.jabber.org/mailman/listinfo/jdev > > > ------------------------------ > > End of JDev Digest, Vol 188, Issue 2 > ************************************ >
_______________________________________________ JDev mailing list Info: https://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: jdev-unsubscr...@jabber.org _______________________________________________
