THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Bayan Towfiq (btowfiq)
Attached to Project - sip-router
Summary - Sanity module fails to reject broken From/ To headers
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Summary:
1) Please make the sanity_check() function callable from onreply_route
2) Please make the sanity module or parser check for and reject SIP messages with duplicate parameter names on headers or uris.
Explanation:
Both headers parameters and URI parameters must be unique names within that header / uri respectively. There can not be duplicate parameter names according to RFC 3261 sections:
7.3.1 Header Field Format
19.1.1 SIP and SIPS URI Components
This problem was discovered by receiving some bad From/To headers on BYEs and 200OKs from a non-compliant client. These buggy headers had duplicate tags that looked like:
From: <sip:8005551212@x.x.x.x>;tag=SDf9rh299-14c034a8+1+5c4f05a4+f31e7fc5;tag=gfrC3Ghl.
This cleared out transactions in the dialog module and gave non matching EDRs for the From/To fields for the acc module (where the field was taken from the 200OK rather than the BYE).
Both the parser and the Sanity module URI checks are not checking for duplicated parameters in headers and uris.
Also, sanity module is not and should be callable from ONREPLY_ROUTE.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=177
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#173 - Double Free -- Crash/Coredump and possible security vulnerability
User who did this - Timo Reimann (tr)
----------
OK thanks. Will take a look at it as soon as time permits.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=173#comment348
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#173 - Double Free -- Crash/Coredump and possible security vulnerability
User who did this - Bayan Towfiq (btowfiq)
----------
Hi Timo, it is still crashing. I am emailing you a full backtrace instead of posting it due to certain information contained in the bt.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=173#comment347
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A user has added themself to the list of users assigned to this task.
FS#176 - server crash while running "tm.t_uac_wait" via sercmd
User who did this - Ovidiu Sas (osas)
http://sip-router.org/tracker/index.php?do=details&task_id=176
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Ovidiu Sas (osas)
Attached to Project - sip-router
Summary - server crash while running "tm.t_uac_wait" via sercmd
Task Type - Bug Report
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - High
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - The server crashes if the "tm.t_uac_wait" RPC command is run via sercmd.
Sercmd connects via "unix" transport.
It is quite straight forward to reproduce:
1. start the server with ctl module (binrpc set to unix transport)
2. run 'sercmd tm.t_uac_wait'
The server will crash and a core file will be generated.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=176
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
The TLS tutorial on the doc site doesn't seem up to date.
http://kamailio.org/docs/tls-devel.html
"1.1. Overview
TLS is an optional part of the Kamailio's core, not a module. TLS, as defined in the SIP RFC3261, is a mandatory feature for proxys and is used to secure the SIP signalling on a hop-by-hop basis (not end-to-end). TLS works on top of TCP. DTLS, or TLS over UDP is also defined by IETF and may become available in a future release of Kamailio."
To me, it seems like TLS is now only a module.
http://kamailio.org/docs/modules/devel/modules/tls.html says
"This module implements the TLS transport for SIP-router using the OpenSSL library (http://www.openssl.org). To enable the TLS support this module must be loaded and enable_tls=yes must be added to the SIP-router config file"
Maybe we should make a note on "http://kamailio.org/docs/" that the "TLS Tutorial" is now part of the module docs and refer to module docs above. I can't update that page myself.
Thanks,
/O
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#173 - Double Free -- Crash/Coredump and possible security vulnerability
User who did this - Bayan Towfiq (btowfiq)
----------
There have not been any segfaults since I set db_mode to 0, but the crashes are sporadic so it is hard to tell if this fixed the issue.
In production I need to use db_mode to 3. I will let you know the status over the next few days.
Bayan
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=173#comment346
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#175 - auth_db crash if table_version field does not exist
User who did this - Juha Heinanen (jh)
----------
here you go:
(gdb)
#1 0x080f54f9 in find_mod_export_record (mod=0xb73c1fc8 "db_mysql",
name=0xb7315353 "db_bind_api", param_no=0, flags=0, mod_if_ver=0xbffcebec)
at sr_module.c:657
657 if (mod!=0 && (strcmp(t->exports.name, mod) !=0))
(gdb) print t->exports
$1 = {name = 0x786e6570 <Address 0x786e6570 out of bounds>,
cmds = 0x706f3a67, params = 0x67786e65, init_f = 0x40333231,
response_f = 0x61636f6c, destroy_f = 0x736f686c, onbreak_f = 0x65732f74,
init_child_f = 0xb6700072, dlflags = 0, rpc_methods = 0x0, stats = 0x0,
mi_cmds = 0x0, items = 0x0, procs = 0x0}
-- juha
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=175#comment345
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#175 - auth_db crash if table_version field does not exist
User who did this - Timo Reimann (tr)
----------
Could you please show the content of t->exports from the core dump in gdb? Or, if that value is not accessible, just t?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=175#comment344
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.