[asterisk-dev] [Code Review] Fix problems when RTP packet frame size is changed

vadim at mbdsys.com vadim at mbdsys.com
Wed Mar 4 19:21:10 CST 2009


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard.digium.com/r/184/#review515
-----------------------------------------------------------



/branches/1.4/main/frame.c
<http://reviewboard.digium.com/r/184/#comment1191>

    I wonder, if this code is secure against s->data buffer overflow



/branches/1.4/main/frame.c
<http://reviewboard.digium.com/r/184/#comment1192>

    assert(size < SMOOTHER_SIZE) ?



/branches/1.4/main/frame.c
<http://reviewboard.digium.com/r/184/#comment1193>

    assert(bytes <= SMOOTHER_SIZE) ?


- vadim


On 2009-03-04 17:32:49, Kevin Fleming wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviewboard.digium.com/r/184/
> -----------------------------------------------------------
> 
> (Updated 2009-03-04 17:32:49)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Summary
> -------
> 
> During some code analysis, I found that calling ast_rtp_codec_setpref() on an ast_rtp session does not work as expected; it does not adjust the smoother that may on the RTP session, in fact it summarily drops it, even if it has data in it, even if the current format's framing size has not changed. This is not good.
> 
> This patch changes this behavior, so that if the packetization size for the current format changes, any existing smoother is safely updated to use the new size, and if no smoother was present, one is created. A new API call for smoothers, ast_smoother_reconfigure(), was required to implement these changes.
> 
> 
> Diffs
> -----
> 
>   /branches/1.4/include/asterisk/frame.h 180297 
>   /branches/1.4/main/frame.c 180297 
>   /branches/1.4/main/rtp.c 180297 
> 
> Diff: http://reviewboard.digium.com/r/184/diff
> 
> 
> Testing
> -------
> 
> Compile testing only.
> 
> 
> Thanks,
> 
> Kevin
> 
>




More information about the asterisk-dev mailing list