Bug#921266: Could this simple typo be the reason: "ream" <-> "realm"?

Bernhard Schmidt berni at debian.org
Sun Mar 10 23:11:25 GMT 2019


Control: severity -1 important
Control: tags -1 moreinfo

Hi Alf,

> I now tried to collect debug info with the cli-version - it crashes the
> same way with segfault:
> 
> linphonec -d 5 -l linphone-debug
> 
> the last lines in the debug output after password enty and before crash are:
> 
> Authentication-Info:
> qop=auth,rspauth="4aa9ccf88b3958bb460174863eccbb82",cnonce="0us2EQTtqGWgU6LP",nc=00000001
> 
> 
> 2019-03-08 22:17:07:834 ortp-message-channel [0x55f42b920dd0] [721]
> bytes parsed
> 2019-03-08 22:17:07:834 ortp-message-Found transaction matching response.
> 2019-03-08 22:17:07:834 ortp-message-Updating auth context for ream
> [tel.t-online.de] next nonce is going to be [(null)]
> 
> Please note the very last line:
> 
> it wants to update auth for "ream"
>   instead of "realm"
> 
> I cannot decide if this is just a typo in text output or actually a
> wrong named parameter. This auth cycle is the second one which probably
> only is used by German Telekom?
> 
> If more information is needed, please let me know
> 
> Fopr completeness I do attach the whole debug output as a plain txt-file
> named linphone-debug.

First of all, thanks a lot for your report.

Based on your feedback of only affecting t-online.de configurations and
also happening in the official Flatpak version (thus not being Debian
specific) I'm downgrading the severity again.

The ream <-> realm typo is just a typo as far as I can tell. It actually
comes from here:

https://github.com/BelledonneCommunications/belle-sip/blob/master/src/provider.c#L234

There have been quite a few commits to that file since it has been released

https://github.com/BelledonneCommunications/belle-sip/commits/master/src/provider.c

Release 1.6.3 which is imported in Debian has been tagged on 21.7.2017,
so there are quite a few commits to check on. And the totally screwed up
handling of the codebase by upstream, with dozens of interdependent
libraries that need to be upgraded in lockstep and have not seen tagged
release for almost two years, does not make it any easier.

You could try the daily snapshot of the official flatpak, which should
be available here

flatpak --user install --from
https://www.linphone.org/snapshots/flatpak-testing-repo/linphone.flatpakref

[totally untested, I don't use flatpak]

If you can still reproduce it, please report upstream at
http://lists.nongnu.org/archive/html/linphone-users/ .

Bernhard



More information about the Pkg-voip-maintainers mailing list