XSF Discussion - 2020-09-19


  1. MattJ

    Glad you're ok Neustradamus, we missed you :)

  2. Seve

    😁

  3. Guus

    I'm no kinda interested myself

  4. MattJ

    xmpp.org and all up to date Prosody servers should have no problems with jabber.org now, as far as I know

  5. Zash

    It doesn't as far as I can tell.

  6. eevvoor

    F2F XMPP Meetup tommorow in Hamburg, Germany in case somebody does some Corona traveling by coincidence ...

  7. Guus

    I'm kinda interested myself

  8. Guus

    > xmpp.org and all up to date Prosody servers should have no problems with jabber.org now, as far as I know So migration had been completed?

  9. Zash

    No, up to date Prosody has a tweaked cipher preference and shouldn't have problems.

  10. Guus

    Oh, sorry. My mind doesn't see a difference between xmpp and jabber. Kind of an important distinction when referring to domain names though. 😉

  11. Zash

    jabber.org ←→ xmpp.org (including muc.) works fine from what I can tell

  12. Guus

    Nevermind, I took Matt's response as a "this was already done". Clearly, I was not paying enougt attention.

  13. Guus

    > Nevermind, I took Matt's response as a "this was already done". Clearly, I was not paying enough attention.

  14. Guus

    Haaaargh. I can't type or click today.

  15. Guus crawls back under his rock

  16. eevvoor

    And here the Link to the Movim Announcement of our Hamburg Meetup tomorrow: https://nl.movim.eu/?node/pubsub.movim.eu/de-hamburg-xmpp-meetup/xmpp-meetup-in-hamburg-september-20th-202014h-l3YCrR

  17. eevvoor

    Guus, jij wilt zeker straks in de trein stappen en erbij zijn, niet waar? Dan kan je ook weer klicken en typen van zo veel euphorie ... :D

  18. jonas’

    MattJ, I still see pings to jabber.org fail from some xmppobserve probers

  19. Zash

    jabber.org → jabber.de also fails (maybe the reverse direction, I can't tell)

  20. jonas’

    MattJ, one of them prominently being my own ;)

  21. Zash

    I suspect they may have set a custom cipher string, which ends up preferring DHE and then they get that 1024bit DHE problem

  22. jonas’

    DH key too small

  23. jonas’

    no custom cipher strings

  24. jonas’

    but prosoy 0.11.2-1 (debian buster)

  25. jonas’

    so maybe that doesn’t qualify as "up to date"

  26. jonas’

    the other failing one is, I think, mdosches

  27. jonas’

    the other failing one is, I think, the one from mdosch

  28. Zash

    The ECDHE > DHE string is default in 0.11.6

  29. Zash

    Earlier has DHE > ECDHE but with DHE disabled, intended to only be preferred if enabled by setting DH params.

  30. Zash

    Buuuuut if the remote has DHE enabled with small DH params... this happens.

  31. jonas’

    I see

  32. jonas’

    so I’d have to backports

  33. emus

    Stupid question (but serious), and I know I dont have technical understanding, why is it so hard to get jabber.org get running? I mean from your side and your knowledge 😅

  34. Neustradamus

    MattJ: I confirm that the problem is always here

  35. Neustradamus

    A jabber.org user can join this mucroom and will be kicked one second after.

  36. mdosch

    jabber.org can't cope with the nick Rixon 👁🗨

  37. eta

    isn'

  38. eta

    isn't jabber.org still running M-Link?

  39. emus

    Its the fifth entry if I search "jabber" in my search engine. I count it as important thereby

  40. Zash

    Future version of Prosody won't allow 👁🗨 or robot face in nicknames, thus solving that problem.

  41. eta

    Zash, nooo

  42. eta

    is that like no non-ASCII whatsoever or just no emoji

  43. Zash

    I don't wish to spend the night crying under my desk so I shall not discuss this. Short version is to be strict on validity when local resources are created. Usernames, MUC nicknames must comply with the relevant validation profile.

  44. eta

    Zash, reasonable; will go rtfm :)

  45. Zash

    More like read mailing list threads and issue tracker, tho I guess an RFC or five are relevant