2 ms·
This is pretty cool. Much simpler than what I did to get 1080p working some time ago. I pulled out the widevine so directly from a CrOS image, replaced the one
by sammko128 9y ago
This is pretty cool. Much simpler than what I did to get 1080p working some time ago. I pulled out the widevine so directly from a CrOS image, replaced the one I had installed and spoofed my User-Agent.
- adtac 9y agoThis sounds really interesting (and more future-proof; Netflix can just choose to change the JS file with the extension technique). Can you please go into more detail on how you pulled out widevine from a CrOS image?
- sammko128 9y agoSure. I figured out the relevant library was libwidevinecdm.so, normally located in /usr/lib/chromium/libwidevinecdm.so on Arch Linux with the chromium-widevine AUR package installed. I created a CrOS installation image for an x86_64 chromebook (not sure which one, I looked up a list of x86_64 ones a picked at random) using the official chrome extension (at the time, this was only possible to do from a Windows machine, not sure what the situation is rn). I mounted the rootfs of the installation image and located the libwidevinecdm.so file. I believe it was somewhere in /opt/google or something like that. This is probably the location on Google Chrome installs under GNU/Linux as well. Then I just replaced my libwidevinecdm.so with the new one. Spoofed my user agent to something containing CrOS and it magically worked. I was quite surprised then :D. Anyway, if you don't feel like doing that (you should do it), trust me (which you should not) and are ok with a (probably) relatively old version of the binary (I don't know whether it still even works, I haven't used netflix in quite some time now), you can get it here: https://transfer.sh/pYsRz/libwidevinecdm.so https://transfer.sh/pYsRz/libwidevinecdm.so SHA256: d84e87d89d8e95ccfcd3dd86157dfd608a022e1e8bee397c3d4541a162bab5c2