Closed sss123next closed 11 months ago
Ouch, missed one case in newly added feature, which did cause it crash when using certaing sasl mechaninsm or using non-encypted connections. Fix for this issue is available in b5ce53c90710e54c3fa749d5d85a878c04043f48.
it seems problem still here:
Eh, you get things like when you just do a small update to your changes, after you properly tested original change...
Fix fixed by bdb513a66066e45cf049a290b44bc26855116e24, it should now work correctly.
works now, thx for quick fix.
Before creating a ticket, please consider if this should fit the discussion forum better.
Environment
Configuration (only if needed): grep -Ev '^$|^\s*#' ejabberd.yml
Errors from error.log/crash.log
Bug description
after update to b556fae08fc025f5f5228b6e74984678b6c31874 various clients start to have errors during login, for example
pidgin
,dino
,gajim
while at leastmcabber
andconversations
still work.as workaround following settings are works:
-completely disable every sha variant