On 15/05/14 14:14, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
The issue was with previous fragment (misread the log message in the
first place). But was easy to spot what could be the previous fragment
and I think I fixed with commit:
-
http://git.sip-router.org/cgi-bin/gitweb.cgi/
Daniel-Constantin Mierla writes:
> The issue was with previous fragment (misread the log message in the
> first place). But was easy to spot what could be the previous fragment
> and I think I fixed with commit:
>
> -
> http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7992a2
The issue was with previous fragment (misread the log message in the
first place). But was easy to spot what could be the previous fragment
and I think I fixed with commit:
-
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7992a2b8d42bb7e8bcf1738cf042013ed126a47a
If you c
there was one more crash during the night caused by the same invite from
attacker.
i reproduced the tel2sip call that my sip proxy runs, but i didn't get the
crash:
$ru = "tel:00441212792194";
$avp(from_uri) = "sip:210.125.64.233";
xlog("L_INFO", "tel2sip $ru, $(avp(from_uri){uri.host
Daniel-Constantin Mierla writes:
> What version are you using?
this is version 4.1 taken from git on may 12.
> It looks like a buffer overflow somewhere. Can you give the output of
> next commands in gdb:
>
> frame 3
> p *f
i got this:
(gdb) frame 3
#3 0x08179f86 in qm_debug_frag (qm=0xb6de
What version are you using?
It looks like a buffer overflow somewhere. Can you give the output of
next commands in gdb:
frame 3
p *f
Cheers,
Daniel
On 14/05/14 21:19, Juha Heinanen wrote:
i just noticed that my proxy had crashed on invite request from
attacker:
May 14 22:03:06 sars /usr/sb
