[asterisk-bugs] [JIRA] (ASTERISK-28449) Scheduler variable too narrow

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247376#comment-247376 ] 

Asterisk Team commented on ASTERISK-28449:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> Scheduler variable too narrow
> -----------------------------
>
>                 Key: ASTERISK-28449
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28449
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Platform
>    Affects Versions: 16.3.0
>            Reporter: Gil Richard
>            Severity: Minor
>
> The schduler (main/sched.c) uses a signed integer value for setting timers in milliseconds.  The SIP RFC [3261 20.19] specifies an Expiry as being between 0 and (2**32)-1.  When converted to ms, the maximum value exceeds the bounds of an integer and becomes a negative value.
> This can replicated by issuing a PUBLISH with an Expiry of 4294967295.  sched_settime() will complain about a negative time and assert 0.
> Changing to an unsigned int or an unsigned long int will likely remedy the issue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)