Re: JDev Digest, Vol 188, Issue 2
April Morone <[email protected]> Tue, 31 Mar 2020 19:35:39 -0400
| Newsgroups | gmane.network.jabber.devel |
|---|---|
| Message-ID | <CAJQCUg8QHn5PgWRqW8h6fzJAk8UoUfYg1c2QBXCsF9bauuK4qQ@mail.gmail.com> |
--===============1618842049== Content-Type: multipart/alternative; boundary="000000000000536c8c05a22f0703" --000000000000536c8c05a22f0703 Content-Type: text/plain; charset="UTF-8" Thank you for this info. On Sun, Mar 29, 2020, 8:00 AM <[email protected]> wrote: > Send JDev mailing list submissions to > [email protected] > > 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 > [email protected] > > You can reach the person managing the list at > [email protected] > > 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 <[email protected]> > To: [email protected] > Subject: [jdev] [ANN] Bad XMPP - Connectivity test suite > Message-ID: <[email protected]> > 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 <[email protected]> > To: "Jabber/XMPP software development list" <[email protected]> > Subject: Re: [jdev] [ANN] Bad XMPP - Connectivity test suite > Message-ID: > <CAMJaV9=+OKb_U075D2gqhD6kB2k5xMG=4WiEn7d9Ps5Adhu= > [email protected]> > Content-Type: text/plain; charset="utf-8" > > This is super useful. Thanks! > > Op za 28 mrt. 2020 19:58 schreef Kim Alvefur <[email protected]>: > > > 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: [email protected] > > _______________________________________________ > > > -------------- 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 <[email protected]> > To: Jabber/XMPP software development list <[email protected]> > 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 > [email protected] > https://mail.jabber.org/mailman/listinfo/jdev > > > ------------------------------ > > End of JDev Digest, Vol 188, Issue 2 > ************************************ > --000000000000536c8c05a22f0703 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Thank you for this info.</div><br><div class=3D"gmail_quo= te"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Mar 29, 2020, 8:00 AM &l= t;<a href=3D"mailto:[email protected]">[email protected]</a>>= ; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .= 8ex;border-left:1px #ccc solid;padding-left:1ex">Send JDev mailing list sub= missions to<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:[email protected]" target=3D"_b= lank" rel=3D"noreferrer">[email protected]</a><br> <br> To subscribe or unsubscribe via the World Wide Web, visit<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://mail.jabber.org/mailman/list= info/jdev" rel=3D"noreferrer noreferrer" target=3D"_blank">https://mail.jab= ber.org/mailman/listinfo/jdev</a><br> or, via email, send a message with subject or body 'help' to<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:[email protected]" targ= et=3D"_blank" rel=3D"noreferrer">[email protected]</a><br> <br> You can reach the person managing the list at<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:[email protected]" target= =3D"_blank" rel=3D"noreferrer">[email protected]</a><br> <br> When replying, please edit your Subject line so it is more specific<br> than "Re: Contents of JDev digest..."<br> <br> <br> Today's Topics:<br> <br> =C2=A0 =C2=A01. [ANN] Bad XMPP - Connectivity test suite (Kim Alvefur)<br> =C2=A0 =C2=A02. Re: [ANN] Bad XMPP - Connectivity test suite (Guus der Kind= eren)<br> =C2=A0 =C2=A03. Re: [ANN] Bad XMPP - Connectivity test suite (Jonas Sch?fer= )<br> <br> <br> ----------------------------------------------------------------------<br> <br> Message: 1<br> Date: Sat, 28 Mar 2020 19:55:15 +0100<br> From: Kim Alvefur <<a href=3D"mailto:[email protected]" target=3D"_blank" rel= =3D"noreferrer">[email protected]</a>><br> To: <a href=3D"mailto:[email protected]" target=3D"_blank" rel=3D"noreferrer"= >[email protected]</a><br> Subject: [jdev] [ANN] Bad XMPP - Connectivity test suite<br> Message-ID: <<a href=3D"mailto:20200328185514.str7achubcgkfpvl@carcharod= on.zash.se" target=3D"_blank" rel=3D"noreferrer">20200328185514.str7achubcg= [email protected]</a>><br> Content-Type: text/plain; charset=3Dus-ascii<br> <br> Hello!<br> <br> Server-to-server connectivity is not perfect today. Certificates expire,<br= > mistakes are made in DNS zones and firewall configurations.<br> <br> In order to see how XMPP software react to such things without having to<br= > wait for problems to pop up, I have set up a few test cases. Most of<br> these have some sort of configuration problem, ranging from faulty DNS<br> and blocked ports up to certificate problems and XMPP s2s<br> authentication.<br> <br> I would be happy if this leads to improved error reporting all the way<br> to end users. Some hint about why their messages could not be delivered<br> are surely better than having them disappear into the void without a<br> trace. Logging and reporting for service operators is also important.<br> <br> Website with list of test cases: <<a href=3D"http://badxmpp.eu/" rel=3D"= noreferrer noreferrer" target=3D"_blank">http://badxmpp.eu/</a>><br> <br> Test cases can also be listed via XEP-0030 items request:<br> <xmpp:<a href=3D"http://badxmpp.eu?disco;type=3Dget;request=3Ditems" rel= =3D"noreferrer noreferrer" target=3D"_blank">badxmpp.eu?disco;type=3Dget;re= quest=3Ditems</a>><br> <br> Suggestions for additional tests are welcomed. Equivalent tests for XMPP<br= > client connectivity is one thing I would like to add, but as a server<br> developer I choose to focus on s2s first. <br> <br> -- <br> Happy testing,<br> Kim "Zash" Alvefur<br> Prosody developer<br> XMPP Council<br> <br> <br> ------------------------------<br> <br> Message: 2<br> Date: Sat, 28 Mar 2020 21:14:52 +0100<br> From: Guus der Kinderen <<a href=3D"mailto:[email protected]" = target=3D"_blank" rel=3D"noreferrer">[email protected]</a>><br= > To: "Jabber/XMPP software development list" <<a href=3D"mailto= :[email protected]" target=3D"_blank" rel=3D"noreferrer">[email protected]</a>&= gt;<br> Subject: Re: [jdev] [ANN] Bad XMPP - Connectivity test suite<br> Message-ID:<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <CAMJaV9=3D+OKb_U075D2gqhD6kB2k5xMG=3D4WiEn7= d9Ps5Adhu=3D<a href=3D"mailto:[email protected]" target=3D"_blank" rel=3D"n= oreferrer">[email protected]</a>><br> Content-Type: text/plain; charset=3D"utf-8"<br> <br> This is super useful. Thanks!<br> <br> Op za 28 mrt. 2020 19:58 schreef Kim Alvefur <<a href=3D"mailto:zash@zas= h.se" target=3D"_blank" rel=3D"noreferrer">[email protected]</a>>:<br> <br> > Hello!<br> ><br> > Server-to-server connectivity is not perfect today. Certificates expir= e,<br> > mistakes are made in DNS zones and firewall configurations.<br> ><br> > In order to see how XMPP software react to such things without having = to<br> > wait for problems to pop up, I have set up a few test cases. Most of<b= r> > these have some sort of configuration problem, ranging from faulty DNS= <br> > and blocked ports up to certificate problems and XMPP s2s<br> > authentication.<br> ><br> > I would be happy if this leads to improved error reporting all the way= <br> > to end users. Some hint about why their messages could not be delivere= d<br> > are surely better than having them disappear into the void without a<b= r> > trace. Logging and reporting for service operators is also important.<= br> ><br> > Website with list of test cases: <<a href=3D"http://badxmpp.eu/" re= l=3D"noreferrer noreferrer" target=3D"_blank">http://badxmpp.eu/</a>><br= > ><br> > Test cases can also be listed via XEP-0030 items request:<br> > <xmpp:<a href=3D"http://badxmpp.eu?disco;type=3Dget;request=3Ditems= " rel=3D"noreferrer noreferrer" target=3D"_blank">badxmpp.eu?disco;type=3Dg= et;request=3Ditems</a>><br> ><br> > Suggestions for additional tests are welcomed. Equivalent tests for XM= PP<br> > client connectivity is one thing I would like to add, but as a server<= br> > developer I choose to focus on s2s first.<br> ><br> > --<br> > Happy testing,<br> > Kim "Zash" Alvefur<br> > Prosody developer<br> > XMPP Council<br> > _______________________________________________<br> > JDev mailing list<br> > Info: <a href=3D"https://mail.jabber.org/mailman/listinfo/jdev" rel=3D= "noreferrer noreferrer" target=3D"_blank">https://mail.jabber.org/mailman/l= istinfo/jdev</a><br> > Unsubscribe: <a href=3D"mailto:[email protected]" target=3D"= _blank" rel=3D"noreferrer">[email protected]</a><br> > _______________________________________________<br> ><br> -------------- next part --------------<br> An HTML attachment was scrubbed...<br> URL: <<a href=3D"http://mail.jabber.org/pipermail/jdev/attachments/20200= 328/bdb1be24/attachment-0001.html" rel=3D"noreferrer noreferrer" target=3D"= _blank">http://mail.jabber.org/pipermail/jdev/attachments/20200328/bdb1be24= /attachment-0001.html</a>><br> <br> ------------------------------<br> <br> Message: 3<br> Date: Sun, 29 Mar 2020 13:15:09 +0200<br> From: Jonas Sch?fer <<a href=3D"mailto:[email protected]" target=3D"_b= lank" rel=3D"noreferrer">[email protected]</a>><br> To: Jabber/XMPP software development list <<a href=3D"mailto:jdev@jabber= .org" target=3D"_blank" rel=3D"noreferrer">[email protected]</a>><br> Subject: Re: [jdev] [ANN] Bad XMPP - Connectivity test suite<br> Message-ID: <5203905.4QTyD5tSvV@sinistra><br> Content-Type: text/plain; charset=3D"utf-8"<br> <br> On Samstag, 28. M?rz 2020 19:55:15 CEST Kim Alvefur wrote:<br> > Suggestions for additional tests are welcomed.<br> <br> I have a few!<br> <br> - Outright bogus DNSSEC<br> - Expired DNSSEC<br> - SRV record pointing at the root zone (`.`) mixed into other SRV records<b= r> - Only a single SRV record pointing at the root zone (`.`)<br> - Only DH suites with short (<1024 bits) DH parameters<br> - Only "export" ciphers<br> <br> Not necessarily bad, but would be good as test cases either way:<br> <br> - DNSSEC-signed SRV record pointing at a hostname different from the domain= <br> name and the service only has a certificate for that hostname. This is vali= d <br> from my understanding, but probably without widespread support.<br> - No SRV record, only A/AAAA records.<br> <br> <br> Echo-ing what moparisthebest suggested in xsf@:?<br> <br> - xmpps-server records where one of which points at an HTTPS port (with a <= br> valid one pointing at XMPPS)<br> <br> <br> Thanks for this service!<br> <br> <br> kind regards,<br> Jonas<br> <br> <br> <br> <br> ------------------------------<br> <br> Subject: Digest Footer<br> <br> _______________________________________________<br> JDev mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank" rel=3D"noreferrer">JDe= [email protected]</a><br> <a href=3D"https://mail.jabber.org/mailman/listinfo/jdev" rel=3D"noreferrer= noreferrer" target=3D"_blank">https://mail.jabber.org/mailman/listinfo/jde= v</a><br> <br> <br> ------------------------------<br> <br> End of JDev Digest, Vol 188, Issue 2<br> ************************************<br> </blockquote></div> --000000000000536c8c05a22f0703-- --===============1618842049== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ JDev mailing list Info: https://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________ --===============1618842049==--