THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#212 - pua_reginfo callid XML string assignment small bug
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
Additional comments about closing: Thanks, patch applied
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=212
You are receiving this message because you have requested it from the Flyspray bugtracking system. …
[View More]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.
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#213 - pua_reginfo: registration state may be incorrect when unregistering single contact
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
Additional comments about closing: Thanks, patch applied.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=213
You are receiving this message because you have requested it from …
[View More]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.
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#214 - Problem with Max-Forwards header parsing
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
Additional comments about closing: I pushed a patch in git master branch to return false in case MF header cannot be processed.
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=a15428e…
More information can be found at the following URL:
http://sip-router.org/…
[View More]tracker/index.php?do=details&task_id=214
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.
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
Daniel-Constantin Mierla has taken ownership of the following task:
FS#214 - Problem with Max-Forwards header parsing
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=214
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 …
[View More]settings at the URL shown above.
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Ladislav Jurak (ladis)
Attached to Project - sip-router
Summary - Problem with Max-Forwards header parsing
Task Type - Bug Report
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - Linux
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Hello,
I am testing …
[View More]some SIP DoS attacks vulnerabilities on Kamailio v3.2 server and I found in an loop based attack this thing:
When Max-Forwards header is set to some text value that server cannot parse or a numeric value higher than 99999, server only copy the Max-Forwards header and forwards the message with the same malformed Max-Forwards value.
Server logs this error - "ERROR: maxfwd [mf_funcs.c:80]: unable to parse the max forwards number" but does not drop the message.
Thus message can be forwarded infinitely. This can by exploitable in loop based attacks.
I think that message with malformed Max-Forward header that server cannot parse should be dropped, or at least reset the Max-Forward header to some defined value.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=214
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.
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A user has added themself to the list of users assigned to this task.
FS#214 - Problem with Max-Forwards header parsing
User who did this - Ladislav Jurak (ladis)
http://sip-router.org/tracker/index.php?do=details&task_id=214
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 …
[View More]the URL shown above.
[View Less]
Hello,
I just pushed GRUU support in git master branch. That implied adding two
new columns to location table, therefore if you use devel version, **you
have to update your db schema**.
Perhaps a bit of tuning will follow in the next days, but GRUU support
should be fully functional in terms of routing. Testing and feedback
will be very appreciated as well as hints on what SIP hard/phones
support GRUU properly.
Be also aware that now you may have to do lookup location even for
within …
[View More]dialog requests, if the r-uri is a local GRUU.
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/
[View Less]