Add secure SIP/SRTP implementation guide to SRTP topic - #10193
Open
tahiralmas wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The SRTP topic currently links to MDN's glossary entry for RTP. That covers the parent protocol, but not the security profile this topic is actually about, so the page is a little thin.
This adds one article on how SRTP gets negotiated and deployed in practice: SIP over TLS for the signalling, SRTP for the media, and the common misconfiguration where the media is encrypted but the call setup isn't.
Disclosure: I work at ICT Innovations and the linked article is on our site. It's written as documentation rather than a product pitch, but I'd rather flag that than slip it past you. Happy to drop it if you'd prefer a vendor neutral source, in which case RFC 3711 is the obvious alternative.
The diff also adds a trailing newline to the file, which it was missing.