SDES just allows for the master key to be exchanged within a new SDP field. That is the place of RFC 4567, which provides additional SDP fields for exchanging key management protocol information. SDES does not actually provide any methods to utilize key management or agreement protocols within SDP.
Of the security session to gain unauthorized access to session. Key over a medium where an attacker can snoop the key, alter theĭefinition of the key to render it useless, or change the parameters Parameters at least as well as the data are secured.ĪKE is needed because it is pointless to provide a It would be self-defeating not to secure cryptographic keys and other Indeed, RFC 4568 for SDES specifically mentions this reality: Therefore, we need to be using SIP over TLS, so that transportation of the key within SDP is secure. Also remember that SIP is usually unencrypted by default. Remember that SDP provides parameters, such as media encoding, for a connection. Essentially, SDES allows for key exchange within the SDP portion of a SIP packet. The Session Description Protocol Security Descriptions (SDES) provide one method for exchanging the keys that are used to encrypt RTP media. VoIP security is a fairly complex topic, rife with acronyms, competing solutions, and enough implementation challenges to make any administrator pull their hair out.
Hacking VoIP: Decrypting SDES Protected SRTP Phone Calls
0 kommentar(er)
