Fwd: Mikey Intiator & Response Message Parsing in Secure RTSP 2.0

[ragh av]

Hi All,
  When i tried RTSP 2.0 back to back server and client.
   In sdp message i found below mikey parametes in Base64

a=key-mgmt:mikey
AQAFAAaC3cABAACdholzAAAAAAsA39SOMRCMLncKEM9XcnVKxlU+AiqkC9YwWvYBAAAAFQABAQEBEAIBAQMBCgcBAQgBAQoBAQAAACIAIAAe6zxuG+m5rliPZA+zkiG4pIUetv5UEBEq0/y9Wr71AA==

Base64 decode of mikey data above is


01 00 05 00 06 82 DD C0 01 00 00 9D 86 89 73 00 00 00 00 0B 00 DF D4 8E 31
10 8C 2E 77 0A 10 CF 57 72 75 4A C6 55 3E 02 2A A4 0B D6 30 5A F6 01 00 00
00 15 00 01 01 01 01 10 02 01 01 03 01 0A 07 01 01 08 01 01 0A 01 01 00 00
00 22 00 20 00 1E EB 3C 6E 1B E9 B9 AE 58 8F 64 0F B3 92 21 B8 A4 85 1E B6
FE 54 10 11 2A D3 FC BD 5A BE F5 00



* Decoded above Hex values as per RFC 3830*


Section 6.1

   - 01 – Version refers to the MIKEY as defined in the Spec
   - 00 – Data Type: Pre Shared Key
   - 05 – Next Payload: TimeStamp
   - 00 – PRF Func
   - 06 82 DD C0 – CSB ID
   - 01 - #CS
   - 00 – CS ID Map Type
   - CS Map Info
      - 00 – Policy_1
      - 9D 86 89 73 – SSRC_1
      - 00 00 00 00 – ROC_1
   - Section 6.6 TimeStamp
      - 0B – Next Payload: RAND
      - 00 – TS-Type 0 is NTP-UTC
      - DF D4 8E 31 10 8C 2E 77 – NTP (first 4 bytes integer part, next 4
      bytes fraction part)
   - Section 6.11 RAND
      - 0A – Next Payload: SP (Security Profile)
      - 10 – Length
      - RAND Value
         - CF 57 72 75 4A C6 55 3E 02 2A A4 0B D6 30 5A F6
      - Section 6.10 Security Profile
      - 01 – Next Payload: KEMAC
      - 00 – Policy Number
      - 00 – Prot Type: SRTP
      - 00 15 – Policy Param Len
      - Policy Params
         - 00 – Policy Type: Encr Algo
         - 01 – Policy Len
         - 01 – Policy Value: AES_CM
         - 01 – Policy Type: Encr. Key Length
         - 01 – Policy Len
         - 10 – Policy Param
         - 02 – Policy Type: Auth Algo
         - 01 – Policy Len
         - 01 – Policy Value: HMAC-SHA-1
         - 03 – Policy Type: Auth Key Len
         - 01 – Policy Len
         - 0A – Policy Value
         - 07 – Policy Type: SRTP Encryption
         - 01 – Policy Len
         - 01 – Policy Value: Enabled
         - 08 – Policy Type: SRTCP Encryption
         - 01 – Policy Len
         - 01 – Policy Value: Enabled
         - 0A – Policy Type: SRTP Authentication
         - 01 – Policy Type
         - 01 – Policy Value
      - Section 6.2 KEMAC
      - 00 – Next Payload: Last
      - 00 – Encr. Algo (NULL)
      - 00 22 – Encr. Length
      - Section 6.13 Encr. Data
         - 00 – Next Payload: Last
         - 2 – Type: TEK
         - 0 – KV
         - 00 1E – Key Data Length
         - Key Data (TEK)
            - EB 3C 6E 1B E9 B9 AE 58 8F 64 0F B3 92 21 B8 A4 85 1E B6 FE
            54 10 11 2A D3 FC BD 5A BE F5
         - 00 – MAC Algo (NULL)

Qusetion is.. what TEK contains as its size is 30 bytes am assumed it is
combination of 16 bytes of master and 14 bytes of Salt key.Is my assumption
is correct?

And also, SETUP request  sent by client alsohaving Mikey parameters when i
expanded as per RFC 3830 it also having one TEK which is different from SDP
TEK value. which TEK gstreamer used to use for encryption/decryption?

Thanks,
Raghav.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20190111/6898f079/attachment.html>