diff options
author | dvossel <dvossel@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-09-10 21:21:36 +0000 |
---|---|---|
committer | dvossel <dvossel@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-09-10 21:21:36 +0000 |
commit | 074b515cf5c2a6bd9a23c832b483731dbb75c28b (patch) | |
tree | 6d956f15fb93266edd84cde6b7fcbf48d4b3cc73 /contrib/editors | |
parent | 53b7d94feb8e3eb83c1b251ec5a75ff9d3ab8a0b (diff) |
Merged revisions 217807 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk
................
r217807 | dvossel | 2009-09-10 16:07:47 -0500 (Thu, 10 Sep 2009) | 28 lines
Merged revisions 217806 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r217806 | dvossel | 2009-09-10 16:06:07 -0500 (Thu, 10 Sep 2009) | 22 lines
IAX2 encryption regression
The IAX2 Call Token security patch inadvertently broke the use of
encryption due to the reorganization of code in the socket_process()
function. When encryption is used, an incoming full frame must first
be decrypted before the information elements can be parsed. The
security release mistakenly moved IE parsing before decryption in
order to process the new Call Token IE. To resolve this, decryption
of full frames is once again done before looking into the frame. This
involves searching for an existing callno, checking the pvt to see if
encryption is turned on, and decrypting the packet before the internal
fields of the full frame are accessed.
(closes issue #15834)
Reported by: karesmakro
Patches:
iax2_encryption_fix_1.4.diff uploaded by dvossel (license 671)
Tested by: dvossel, karesmakro
Review: https://reviewboard.asterisk.org/r/355/
........
................
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.2@217821 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'contrib/editors')
0 files changed, 0 insertions, 0 deletions