aboutsummaryrefslogtreecommitdiffstats
path: root/utils/conf2ael.c
diff options
context:
space:
mode:
authorphsultan <phsultan@f38db490-d61c-443f-a65b-d21fe96a405b>2007-08-16 09:45:22 +0000
committerphsultan <phsultan@f38db490-d61c-443f-a65b-d21fe96a405b>2007-08-16 09:45:22 +0000
commit6bc0bc518947208f89ba2630944267a45a3088fb (patch)
treed5b2e1b1913b10bc7d42cd36a24902a821ec5382 /utils/conf2ael.c
parentd913db99c9446b0d3459ad7804b9fe567eeaedcb (diff)
Merged revisions 79665 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r79665 | phsultan | 2007-08-16 11:37:10 +0200 (Thu, 16 Aug 2007) | 21 lines A fix for two critical problems detected while working with Daniel McKeehan in issue #10184. Upon priority change, the resource list is not NULL terminated when moving an item to the end of the list. This makes Asterisk endlessy loop whenever it needs to read the list. Jids with different resource and priority values, like in Gmail's and GoogleTalk's jabber clients put that problem in evidence. Upon reception of a 'from' attribute with an empty resource string, Asterisk crashes when trying to access the found->cap pointer if the resource list for the given buddy is not empty. This situation is perfectly valid and must be handled. The Gizmoproject's jabber client put that problem in evidence. Also added a few comments in the code as well as a handle for the capabilities from Gmail's jabber client, which are stored in a caps:c tag rather than the usual c tag. Closes issue #10184. ........ git-svn-id: http://svn.digium.com/svn/asterisk/trunk@79666 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'utils/conf2ael.c')
0 files changed, 0 insertions, 0 deletions