Skip to main content

Decrypt SDES SRTP from pcap

If you have a pcap file with encrypted RTP (SDES SRTP) and have access to the SIP signalling to see the keys, these instructions will help you decrypt the RTP payload and save it as raw audio. Optionally, depending on the codec, you can then import the raw audio in Wireshark and save it as an audio file.

Steps

Build ‘srtp-decrypt’

These are the steps:

  1. Build ‘srtp-decrypt’

  2. Get crypto key for each direction

  3. Use the decrypt.sh bash script to decrypt into raw audio

  4. Import the raw audio into Wireshark as hex dump

  5. Generate the wav file

  6. Generate the wav file as two separate channels, one per direction


Follow instructions here:

https://github.com/gteissier/srtp-decrypt


Assume the binary will be produced in a path like ‘/root/code/srtp-decrypt/srtp-decrypt’


Get crypto key for each direction

Access the SIP involved and take note of the ‘crypto’ line from the SDP for each direction.

e.g.:


v=0

...

m=audio 16398 RTP/SAVP 96 8 97

c=IN IP4 xxxxx

...

a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:K7oAZZ5Fm9fePS5/t1ac00000000000000000000

...


The crypto key for the RTP stream produced by this party is K7oAZZ5Fm9fePS5/t1ac00000000000000000000


Use a bash script to decrypt into raw audio

Use this simple bash script to perform the actual decryption:


#!/bin/bash

set -x


SRTP_DECRYPT_BIN=/root/code/srtp-decrypt/srtp-decrypt

HEADER_SIZE=48


CRYPTO_KEY=5eKSVpIOePOgjjfep21R3b000000000000000000

RTP_PCAP=outbound.pcap

RAW_DATA=outbound.raw


${SRTP_DECRYPT_BIN} -d ${HEADER_SIZE} -k ${CRYPTO_KEY} < ${RTP_PCAP} > ${RAW_DATA}


Where:

CRYPTO_KEY needs the value of the crypto key seen earlier.

RTP_PCAP has the pcap with the RTP stream that you want to decrypt.

RAW_DATA is the output file where to put the decrypted raw audio.


HEADER_SIZE may vary, depending on the presence of the SLL header in the capture.

Import the raw audio into Wireshark as hex dump


In Wireshark:

  • File → Import from Hex Dump

  • Select the file with the raw audio

  • Offsets: Hexadecimal

  • Timestamp format: %M:%S.%f

  • Encapsulation type: Ethernet

  • UDP: source port 10000, destination port 20000

  • Import


Then go to:

  • Telephony → RTP → RTP Streams

  • Play

  • Select stream

  • Export as Synchronised audio file


If for example you have two RTP streams, one per direction for the same call, you can generate the wav file with two separate channels, one per direction.


Once you have the raw audio for both directions, you can use Audacity (https://www.audacityteam.org/) to import the audio.


  • Open the first file.

  • File → Import Audio for the second file.

  • Select the first audio, right click, “Set as Stereo file”

  • Save
Labels:

Popular posts from this blog

About ICE negotiation

Disclaimer: I wrote this article on March 2022 while working with Subspace, and the original link is here:  https://subspace.com/resources/ice-negotiation . This post in my personal blog is a way to ensure it doesn't get lost. There is nothing service-specific in it, I've made only minor edits and I hope it can be a good technical reference on the topic. WebRTC is a set of protocols that allow applications, typically running on Web browsers, to exchange media (audio, video, data) with other entities. Before media can flow, however, the WebRTC entities need to discover what type of connection is possible, and among the possible connections, what’s the best to be used. This needs to happen as fast as possible, so that users can perceive the service as instantaneous as possible. WebRTC includes protocols like STUN and TURN that are designed to facilitate the establishment of connections when a direct connection is not possible. The typical case is a computer inside a home or o...
Read more

Troubleshooting TURN

  WebRTC applications use the ICE negotiation to discovery the best way to communicate with a remote party. I t dynamically finds a pair of candidates (IP address, port and transport, also known as “transport address”) suitable for exchanging media and data. The most important aspect of this is “dynamically”: a local and a remote transport address are found based on the network conditions at the time of establishing a session. For example, a WebRTC client that normally uses a server reflexive transport address to communicate with an SFU. when running inside the home office, may use a relay transport address over TCP when running inside an office network which limits remote UDP targets. The same configuration (defined as “iceServers” when creating an RTCPeerConnection will work in both cases, producing different outcomes.
Read more

debian - Managing maintainer scripts for packages with multple .debs

If you've ever installed a package from command line on Linux, you must have noticed two main prompts related to package configuration: one asking what to do with installed configuration files with local changes, and one providing feedback right after the installation/upgrade/removal/purge has completed. Under Debian the latter was most probably the postinst script, one of the Package Maintainer Scripts which is executed after installation and configuration. These diagrams are very useful to understand what happens to the Maintainer Scripts in different circumstances: first installation, upgrade, removal, purge. Their name is probably self-explanatory: preinst , postinst , prerm , postrm . Each of them takes zero or more arguments depending on the scenario. It can help to understand that those are really just scripts executed by dpkg - and typically they are shell scripts, sometimes with interactive prompts. If you're building your own packages, you surely already h...
Read more