Trying to extract Widewine key: A journey to failure
1–10 of 133 posts
Re: Trying to extract Widewine key: A journey to failure
#2Hmmm... Would love if this allows me watch netflix using a fully FLOSSed arm sbc.
Re: Trying to extract Widewine key: A journey to failure
#3actual title: Trying to extract Widewine key: A journey to FaIlUrE
Re: Trying to extract Widewine key: A journey to failure
#4Every time this is broken, am I right in saying all encrypted media needs to be re-encrypted with the updated version of widevine?
Re: Trying to extract Widewine key: A journey to failure
#5Hmmm... Would love if this allows me watch netflix using a fully FLOSSed arm sbc.
The point of semi-unusable DRMed crap when L1 released keep getting WEB-DLed?
Very likely it's not the Shield now which leaks L1, but an actual key recovery because they get the stream even before it gets watermarked in the secure domain.
My guess, it's Qualcomm's debugging TZ applets. They cannot really revoke keys because they will take down a giant amount of Snapdragon based handsets for which manufacturers don't bother to put a single OTA.
This is also likely why Netflix uses such a silly restrictions as refusing to run on old Android version numbers on some Snapdragon handsets, which are easily root bypassable.
Re: Trying to extract Widewine key: A journey to failure
#6Every time this is broken, am I right in saying all encrypted media needs to be re-encrypted with the updated version of widevine?
> Every time this is broken, am I right in saying all encrypted media needs to be re-encrypted with the updated version of widevine?
Yes, but so far no big Netflix-like website did it. It's a credible guess that all encrypted L1 content long been downloaded, and is just waiting decryption (NF used to use HTTP to serve encrypted files in the open, without any API wall some years ago)
Re: Trying to extract Widewine key: A journey to failure
#7Every time this is broken, am I right in saying all encrypted media needs to be re-encrypted with the updated version of widevine?
No. The media is encrypted with Common Encryption regardless.
This is only about key management.
Re: Trying to extract Widewine key: A journey to failure
#8actual title: Trying to extract Widewine key: A journey to FaIlUrE
The bad font on GitHub makes "FaIlUrE" look like "FallUrE". I thought it must have been a typo.
Re: Trying to extract Widewine key: A journey to failure
#9Every time this is broken, am I right in saying all encrypted media needs to be re-encrypted with the updated version of widevine?
By this point everyone would agree that platforms that eliminate all piracy dies. So they’ll send out couple DMCAs until it’s sufficiently unknown and that’ll be all.
Re: Trying to extract Widewine key: A journey to failure
#10actual title: Trying to extract Widewine key: A journey to FaIlUrE
The bad font on GitHub makes "FaIlUrE" look like "FallUrE". I thought it must have been a typo.
Bad Windows font, probably. It's just using the default system fonts, which in case of Segoe UI doesn't employ caps for I. Ironically, Segoe (just Segoe, the reference font) do have caps on I.