| Summary: | net-im/ejabberd-16.04: crashed unexpectedly | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Amadeusz Żołnowski (RETIRED) <aidecoe> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://github.com/processone/ejabberd/issues/1295 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
error.log
crash.log ejabberd.yml |
||
|
Description
Toralf Förster
2016-07-27 15:21:16 UTC
Created attachment 441738 [details]
crash.log
and fwiw : dev-lang/erlang-18.3::gentoo was built with the following: USE="ssl -compat-ethread -doc -emacs -halfword -hipe -java -kpoll (-libressl) -odbc -sctp -smp -systemd -tk -wxwidgets" ABI_X86="64" in the info.log I got (snipped the user name)
2016-07-25 09:54:36.572 [info] <0.495.0>@ejabberd_listener:accept:333 (#Port<0.24154>) Accepted connection 2A02:8108:4A40:8D98:9424:E9BE:ABBA:B672:61395 -> 2A01:4F8:190:514A::2:5222
2016-07-25 09:54:36.895 [info] <0.14095.0>@ejabberd_c2s:wait_for_feature_request:782 ({socket_state,fast_tls,{tlssock,#Port<0.24154>,#Port<0.24155>},<0.14094.0>}) Failed authentication for <snip>@jabber.zwiebeltoralf.de from 2A02:8108:4A40:8D98:9424:E9BE:ABBA:B672
2016-07-25 09:54:38.652 [info] <0.495.0>@ejabberd_listener:accept:333 (#Port<0.24156>) Accepted connection 2A02:8108:4A40:8D98:9424:E9BE:ABBA:B672:61403 -> 2A01:4F8:190:514A::2:5222
2016-07-25 09:54:38.937 [info] <0.14097.0>@ejabberd_c2s:wait_for_feature_request:782 ({socket_state,fast_tls,{tlssock,#Port<0.24156>,#Port<0.24157>},<0.14096.0>}) Failed authentication for <snip>@jabber.zwiebeltoralf.de from 2A02:8108:4A40:8D98:9424:E9BE:ABBA:B672
2016-07-25 09:54:57.864 [info] <0.495.0>@ejabberd_listener:accept:333 (#Port<0.24158>) Accepted connection 2A02:8108:4A40:8D98:9424:E9BE:ABBA:B672:61422 -> 2A01:4F8:190:514A::2:5222
2016-07-25 09:54:58.191 [error] <0.14099.0> gen_fsm <0.14099.0> in state wait_for_feature_request terminated with reason: bad argument in call to crypto:sha_mac_n(error, <<79,103,224,133,46,244,34,23,98,95,199,199,141,33,206,62,0,0,0,1>>, 20) in scram:hi/3 line 73
Could you describe context a bit more? In which circumstances it happened? Are you doing something unusual? I am going to forward bug upstream and that information may be useful for them. (In reply to Amadeusz Żołnowski from comment #4) I reset a users password to a new one and he tried to login and to send my a message. The issue happened just once. The guy itself had have : ChatSecure 3.2.3 Created by Chris Ballinger u. David Chiles iOS 9.3.3 (13G34) libotr 4.1.1 libgpg-error 1.21 libgcrypt 1.6.5 tor 0.2.7.6 OpenSSL 1.0.2g 1 Mar 2016 libevent 2.0.22-stable (In reply to Toralf Förster from comment #5) > (In reply to Amadeusz Żołnowski from comment #4) > > I reset a users password to a new one and he tried to login and to send my a > message. The issue happened just once. The guy itself had have : Thanks. Which authentication mechanism do you use? How you've changed the password? At the moment of changing password, has the user been logged in (probably no) or was trying to log in? Could you provide excerpts of your config related to registration and authentication? Was the user connecting via tor? Have you tried to reproduce the issue, e.g. by creating new account and changing password to the same one you've changed for that user? Created attachment 442662 [details]
ejabberd.yml
attached is the config.
Unfortunately I cannot say when exactly the crash happened - the user contacted me too late. A subsequent attempt of him to connect succeeded and the behaviour doesn't occurred again in the mean while.
The URL to forum doesn't seem to be really relevant to the issue. I have reported the issue upstream, but unless there's something obvious in logs to developers, I doubt it's going to be resolved since even you cannot reproduce it. From <https://github.com/processone/ejabberd/issues/1295#issuecomment-275319371>: > By the way, did you report the issue to ChatSecure? Because this is also a client issue. From <https://github.com/processone/ejabberd/issues/1295#issuecomment-279127552>: > After some investigation, I found that the password contains a control character (\n) and SASLprep doesn't allow such characters. And it has been fixed on 12 Feb. It is fixed in ejabberd-17.04 which has just been added to the tree. |