[RELEASE] ESPN3.com Addon - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: Add-on Support (https://forum.kodi.tv/forumdisplay.php?fid=27) +---- Forum: Video Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=154) +---- Thread: [RELEASE] ESPN3.com Addon (/showthread.php?tid=95053) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
RE: [RELEASE] ESPN3.com Addon - locomot1f - 2014-01-10 (2014-01-09, 06:36)m0ngr31 Wrote: I can't get this to work. I've tried it on every version I can find. (0.9.9 a few different default.py's and locomot1f's). This is my error on locomot1f's: i think you might have to take this advice: smirch1 Wrote:i have it working. After disabling on the login page, I backed out of the ad on and re-entered. Thanks for your help. unfortunately, only ESPN3 content works on this plugin. hoping someone would be around to helping those with access... I've seen Bluecop poking around... but i don't think he programs anymore... RE: [RELEASE] ESPN3.com Addon - m0ngr31 - 2014-01-10 What does it mean to disable the login page? EDIT: nevermind, stupid question. RE: [RELEASE] ESPN3.com Addon - hunkyn - 2014-01-10 Is it possible to make this work with Chrome Launcher? That may be an easier answer to have it work that way. Any developers interested in that? RE: [RELEASE] ESPN3.com Addon - locomot1f - 2014-01-10 (2014-01-10, 19:35)hunkyn Wrote: Is it possible to make this work with Chrome Launcher? That may be an easier answer to have it work that way. Any developers interested in that? i actually think that still works with the original default.py (can anyone verify this). I believe if authenticate through a browser, and then open up XBMC, the program should work. i believe this problem arises with those of us that use our systems solely for XBMC. again.. i could be wrong. RE: [RELEASE] ESPN3.com Addon - dfego - 2014-01-11 Update: It looks like the Adobe Flash Access is what's at play here. After tinkering with it a bit, it looks like we could theoretically send POST requests directly to the correct servers with the correct information to get the data we need such that we can access the ESPN stuff, but the protocols are entirely unknown to me at this point, as far as the specific binary formats sent back and forth. If anyone knows anyone familiar with this technology, or someone who knows a thing or two about reverse engineering, we might be able to get somewhere with this. As it stands, I'm not sure I've got the chops to continue, but it seems like it's just a matter of emulating the steps that the flash in the browser takes, and that should be enough if you have the proper authorization (TV provider etc) to view the content. ---------------------- I've followed as much of this discussion as I can over the last day, and did some investigating to see what's going on with non-ESPN3 streams. I discovered what locomot1f discovered, with the other URL and pkan and such, but did come up with one additional piece of potentially useful information: the long pkan string seems to be a base64 encoded string. I'm not sure if it was Wireshark or the way the data is actually sent, but I was initially thrown off because there are escaped codes in here. Like %2B and %0A, which are + and LF (linefeed), and those need to be converted before actually decoding the base64. So the base64 string (post-conversion) is: Code: PHNpZ25hdHVyZUluZm8+REwzdURBOFZSb1l6aTlpSmpBN0tpcGhPQ3pLdnl1aEFtV1NJVVExNGlD Thrown into a base64 decoder on the web, I get this (newlines and indentation added for clarity): Code: <signatureInfo> The resource string was similar: Code: PHJzcyB2ZXJzaW9uPSIyLjAiIHhtbG5zOm1lZGlhPSJodHRwOi8vc2VhcmNoLnlhaG9vLmNvbS9t Which produced this (once again formatted for clarity): Code: <rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/"> As you can see, I was testing with the Lakers vs. Clippers game. Also of note, these authentication strings seem to be time-sensitive, so if I use one and then come back 20 minutes later and try to stream with the same data, it will say "EXPIRED." But, when I came back later and got a new pkan string from Wireshark, the signatureInfo was different, but the sessionGUID was the same. Perhaps because I didn't log out in that time? That's all I've been able to dredge up for now. I initially messed up my base64 decoding so I was confused for a while, but now these are just straight-up xml strings. Maybe these are helpful? I've yet to experiment with what parts of the XML are necessary and need to be specific for things to work. The signatureInfo worries me a bit, but time will tell. More info: signatureInfo fields also seem to be base64 encoded, but these are just binary blobs that are 128 bytes (not bits). I initially thought it might be a hash, but that's too long for that, so I'm not sure. For the signatureInfo above, here's the hex representation of the base64 decoding: Code: 0x0C 0xBD 0xEE 0x0C 0x0F 0x15 0x46 0x86 It seems to be a signature of some kind, and it looks like it needs to match. I took a good pkan string, decoded it into its xml, and changed a single character of the signatureInfo and then converted it back, and I get a message about a corrupt signature back. So whatever solution we find will probably have to generate these signatures. With any luck it'll just be a matter of finding the right algorithm? Hopefully there's not some kind of secret key involved... Okay further investigation... It looks like relatively soon before the above data is sent by the browser to ESPN, there's an HTTP packet from an Adobe website (66.235.134.217) with 200 OK and a bunch of binary data, including the string "Adobe Systems Incorporated" and "Adobe Flash Access Individualization". Googling these terms yields some results, and it looks like their DRM scheme. RE: [RELEASE] ESPN3.com Addon - m0ngr31 - 2014-01-11 Hey, that's awesome man. I've forked locomot1f's repo on Github and removed the login settings for the time being since they don't work. I've also added it into my repo (HERE) so it can be automatically updated when we get new stuff figured out. Let me know if you are interested in getting something going. RE: [RELEASE] ESPN3.com Addon - m0ngr31 - 2014-01-11 It also appears as if masking that you are not on Comcast you can't mask it anymore with the userdata.xml file. Can anyone else confirm? RE: [RELEASE] ESPN3.com Addon - ima747 - 2014-01-15 Sorry for being late, but with 165 pages it's hard to figure out what's current... Is this plugin working for ESPN 3 currently? I'm on comcast but use a comcast account not associated with my physical connection to log in. On MacOS if it's a factor. By monkeying around with all the login settings I eventually got it to let me list content, but nothing I've tried gets it to play. Using 12.3 frodo. Any summary of the current status would be appreciated. RE: [RELEASE] ESPN3.com Addon - m0ngr31 - 2014-01-16 Logging in doesn't work at all right now. The only thing that works is ESPN3 while being on a network that supports it. You'll have to make sure your userdata.xml is in the right place too. RE: [RELEASE] ESPN3.com Addon - ima747 - 2014-01-16 Thanks! Hope the login system at least gets sorted soon. RE: [RELEASE] ESPN3.com Addon - Romans I XVI - 2014-01-19 Added a fork of this to the official XBMC repo. All non working parts removed and problems with userdata files / custom user files have been fixed. Enjoy. Any discussion about the fork should be directed to this thread --> http://forum.xbmc.org/showthread.php?tid=186028 |