XSF Discussion - 2020-10-17


  1. eevvoor

    I have this error message: > Server-to-server connection failed: Connecting failed: dh key too small When writing one of my contacts. He has his jid on jabber.org

  2. eevvoor

    Any know reason?

  3. eevvoor

    I can see the online-status of the contact though.

  4. Arne

    dh key of your server is maybe set wrong

  5. Zash

    Your server and jabber.org negotiated a cipher with ephemeral diffie-hellman key agreement. The parameters on jabber.org are 1024bit iirc. Your server didn't like it and gave up.

  6. Zash

    eevvoor, make sure your server is up to date and doesn't have weird tls configuration. normally these days most connections should be negotiating elliptic curve dh

  7. eevvoor

    It is not my own server.

  8. Zash

    Bother your local server admin then :)

  9. Daniel

    the 'proper' way would probably be to increase the dh param size on jabber.org tthough

  10. Daniel

    because 1024 is not a lot

  11. Daniel

    and many servers will have issues with that

  12. wurstsalat

    Isn't the migration of jabber.org underway?

  13. mdosch

    It is. The MUC component is already on a new server. But no idea whether there is any fixed schedule.

  14. mdosch

    MattJ might know.

  15. eevvoor

    yes, devilz gave me the feedback that he disabled the support for the short key.

  16. eevvoor

    Does someone know the jabber.org admins?

  17. eevvoor

    https://www.jabber.org/notices.html says nothing about planned updated.

  18. eevvoor

    Matthew, are you one of the admins?

  19. eevvoor

    Matthew, are you one of the admins?

  20. eevvoor

    Ok, I got the info about jabber.org from the jabber.de admin: Jabber.org is migrating to prosody rigth now, so I should just wait and dring tea ...

  21. Ge0rG

    eevvoor: the migration was slightly delayed because we had to show the ietf that they are using jabber wrong 😉

  22. MattJ

    eevvoor: yes, the migration is happening

  23. mdosch

    Looking at the Github issues I assume stpeter has "We are working on it!" on a shortcut. :D

  24. Ge0rG

    mdosch: stpeter is a github bot

  25. Ge0rG

    Damn, I wasn't supposed to say that in public.

  26. mdosch

    Reminds me when I wanted to debug an issue and posted a snippet from my debug log and no one cared about my problem but everyone was abused that according to my logs MattJ is a bot. :D

  27. mdosch

    s/abused/amused/

  28. mdosch

    ^^

  29. eevvoor

    MattJ, that is a good reason for a delay. 🙄 😂

  30. eevvoor

    The MattJ-Bot, oh yeah :D.

  31. eevvoor

    The jabber.de Admin is laughing btw. I informed him about the reason for the delay.

  32. MattJ

    So far we have most user data exported and conversion scripts written. There are are some bits of data which are not exported and we're working on ways to access that...

  33. MattJ

    With over a million user accounts we are likely looking at taking the server down for a day while we perform the migration

  34. MattJ

    And of course that will be announced once a date is set

  35. MattJ

    We (well, stpeter) just went through a lot of effort to renew the certificate and it would be good to get the migration done before we need to do that again

  36. MattJ

    So hopefully in the coming weeks

  37. eevvoor

    good luck then MattJ and stpeter

  38. Zash

    Is anyone aware of anything still relying on XEP-0091: Legacy Delayed Delivery ?

  39. Zash

    I looked at a raw MUC message and wondered if all 5 of the extra id tags were really necessary.

  40. moparisthebest

    emus: once again excellent job on newsletter and also thanks for posting it on fediverse! :D

  41. emus

    moparisthebest: Thank you very much! But I dont know who it did - maybe SouL! So thanks to him!

  42. lovetox

    its not good that the native bookmark xep loses no word about a correctly configured node

  43. lovetox

    it only has an example where some publish options are included, but says nothing about if they are important or not

  44. Zash

    No reference to XEP-0223 either?

  45. lovetox

    there is a reference, but i dont see how this is helpful

  46. lovetox

    this would be my node config

  47. lovetox

    'pubsub#notify_delete': 'true', 'pubsub#notify_retract': 'true', 'pubsub#persist_items': 'true', 'pubsub#max_items': 'max', 'pubsub#access_model': 'whitelist', 'pubsub#send_last_published_item': 'never',

  48. lovetox

    except send_last_published_item, i consider the other ones mandatory

  49. lovetox

    so the XEP should mention this

  50. lovetox

    and we need to add the max_items=max change to the xep

  51. lovetox

    hm ok, notify_delete is probably not mandatory is a edge case, and applies to all pubsub based xeps

  52. lovetox

    notify_react is not needed if clients add the notify=true attribute to the react

  53. lovetox

    persist and access are mentioned in 0223

  54. lovetox

    send last published item is not mandatory

  55. lovetox

    and max_items also not