Audio/video stream recording forums
|
Attention Visitor: |
You may have to register or log in before you can post:
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Obfuscated tokenHi all! I'm trying to catch one of the free streams of football-hd.com
Unfortunately it looks like - besides the wowza protection changing every 5 minutes - these rtmp streams have also a token parameter, which is obviously obfuscated... Here is the structure of one of the free streams: Code:
rtmpdump -r "rtmp://free-tv.football-hd.com:1935/hdedge/" -a "hdedge/" -f "WIN 15,0,0,152" -W "https://football-hd.com/resources/player/jwplayer/jwplayer-6.10/jwplayer.flash.swf" -p "https://football-hd.com/?r=live-channel/25/2/True_Sport_HD4" -y "TRUEHD4_800?wmsAuthSign=[hash]" -T [obfuscated token] -o "test.flv" Do anyone happen to know the obfuscated token value (T) ? Also feel free to pm it, if you like. Thanks in advance! |
#2
|
|||
|
|||
Re: Obfuscated tokenciao Amigo
for token you can use that here Code:
-T "e39d5b0a7a8a37c8/" for wmsAuthSign=xxxx at the moment not possible from my side experts welcome Last edited by hasomaso : 09-25-2014 at 04:06 PM. |
#3
|
|||
|
|||
Re: Obfuscated tokenHi,
so you can also use only -y "TRUEHD4_800" and I don't think that the rest after is important.The channel does already play more than 20 minutes for me now with same datas. Token you can find in memory.Just check for the strings you can see below. Code:
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F 042B56D0 65 33 39 64 35 62 30 61 37 61 38 61 33 37 63 38 e39d5b0a7a8a37c8 042B56E0 62 6F 74 74 6F 6D 2D 72 69 67 68 74 00 00 00 00 bottom-right.... 042B56F0 66 6C 61 73 68 70 6C 61 79 65 72 00 00 00 00 00 flashplayer..... 042B5700 73 65 63 75 72 65 74 6F 6B 65 6E 00 00 00 00 00 securetoken..... 042B5710 62 75 66 66 65 72 6C 65 6E 67 74 68 00 00 00 00 bufferlength.... 04A1A150 69 64 3D 22 73 65 63 75 72 id="secur 04A1A160 65 74 6F 6B 65 6E 22 3E 3C 73 74 72 69 6E 67 3E etoken"><string> 04A1A170 65 33 39 64 35 62 30 61 37 61 38 61 33 37 63 38 e39d5b0a7a8a37c8 04A1A180 3C 2F 73 74 72 69 6E 67 3E </string> -T "e39d5b0a7a8a37c8" |
#4
|
|||
|
|||
Re: Obfuscated tokenThank you, that's even better! Yes, when I noticed the rtmp stream built with token & wowza, I imagined the real issue was the token
But I was not good in finding obfuscated tokens |
Tags: obfuscated, rtmpdump, token |
Thread Tools | |
Display Modes | |
|
|