1596890 - Update rules to serve Widevine version 4.10.1582.2

Status: RESOLVED FIXED

(Release Engineering :: Release Requests, task)

Description

[Bryce Seager van Dyk [:bryce] (he/him) - Not reading bugmail]

We would like to update the balrog rules to serve Widevine version 4.10.1582.2 as part of our normal Widevine release schedule and as this version gives encrypted AV1 support.

Could we set up a nightlytest channel set of rules so I can test the new CDM? Could the rules target 72.0a1+ on all desktop platforms, please?

Output of my script to grab CDM zips and produce hashes:

Got https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-linux-ia32.zip
SHA256: 31e7f1ded497ec4edd3d4bc635de3d9191b65fb3e411eb829cb0615344872cd8
SHA512: feb9cfddf2b805122e450a3ee8c8843e2d46f868f5d10169ad5e4ce49b1e6736e0d11f11ffe5a74f3184eab8317608a80c7128e59bdfa0a14319f89ab830b39e
file size: 4289036 bytes

Got https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-linux-x64.zip
SHA256: 87fe864c030b382633cbf8b36580a27d3fa5b4095f245d2d9de024ffad433f3d
SHA512: e750e055ec563f2411ef84bf359037ff523f8db3c5143b42af2478a44e9b1ca9b135707d6dcacab178df355927c68c8eb43bdd63456e22c6d787fc86dd668aa2
file size: 4000517 bytes

Got https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-mac-x64.zip
SHA256: 19b80a3e33f4d37c3f6e964e10f31608d17a0ef6dd61bf41531a1e9f40cc129c
SHA512: 9ad5288a8c6488dc46ff4232beb440ad533c4c8e52d943673959d7a949f9cd68c09c45b1d23a1cf6e43241429e398d46873e94ef55b55c36e3d1da3942433837
file size: 4270381 bytes

Got https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-win-ia32.zip
SHA256: 8eeb72ff641c26eb563f6a0fdb1b3fe67f0f9b17be4c4f96a83304590ec99a83
SHA512: d448fa194996c3154b7a47a4447331125fab9c3d6d52a08a640ab21677535102117a0262798bc95ba75310060fe0517d7b4593245ad48da683956455417502cb
file size: 5197739 bytes

Got https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-win-x64.zip
SHA256: 36e84e32aad8963a66b0b2178c6a33c4b12af17aa50756c0a1d79ad28a34727d
SHA512: 8054294ad328f0b32e7474448e77fb4c56dbe4e7100920461508dd18cab94f69b13dbc1e9776800f49993d478827b4a65732a9bc39a3940251d9cb96ffffddd9
file size: 5097580 bytes

For reference bug 1566127 is the previous rule change.

Comment 1

[Jordan Lund (:jlund)]

I can look at this tomorrow

Comment 2

[Jordan Lund (:jlund)]

This should be done now:

added release blob:

{
  "hashFunction": "sha512",
  "name": "Widevine-4.10.1582.2",
  "product": "Widevine",
  "schema_version": 1000,
  "vendors": {
    "gmp-widevinecdm": {
      "platforms": {
        "Darwin_x86_64-gcc3": {
          "alias": "Darwin_x86_64-gcc3-u-i386-x86_64"
        },
        "Darwin_x86_64-gcc3-u-i386-x86_64": {
          "fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-mac-x64.zip",
          "filesize": 4270381,
          "hashValue": "9ad5288a8c6488dc46ff4232beb440ad533c4c8e52d943673959d7a949f9cd68c09c45b1d23a1cf6e43241429e398d46873e94ef55b55c36e3d1da3942433837"
        },
        "Linux_x86-gcc3": {
          "fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-linux-ia32.zip",
          "filesize": 4289036,
          "hashValue": "feb9cfddf2b805122e450a3ee8c8843e2d46f868f5d10169ad5e4ce49b1e6736e0d11f11ffe5a74f3184eab8317608a80c7128e59bdfa0a14319f89ab830b39e"
        },
        "Linux_x86_64-gcc3": {
          "fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-linux-x64.zip",
          "filesize": 4000517,
          "hashValue": "e750e055ec563f2411ef84bf359037ff523f8db3c5143b42af2478a44e9b1ca9b135707d6dcacab178df355927c68c8eb43bdd63456e22c6d787fc86dd668aa2"
        },
        "Linux_x86_64-gcc3-asan": {
          "alias": "Linux_x86_64-gcc3"
        },
        "WINNT_aarch64-msvc-aarch64": {
          "alias": "WINNT_x86-msvc"
        },
        "WINNT_x86-msvc": {
          "fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-win-ia32.zip",
          "filesize": 5197739,
          "hashValue": "d448fa194996c3154b7a47a4447331125fab9c3d6d52a08a640ab21677535102117a0262798bc95ba75310060fe0517d7b4593245ad48da683956455417502cb"
        },
        "WINNT_x86-msvc-x64": {
          "alias": "WINNT_x86-msvc"
        },
        "WINNT_x86-msvc-x86": {
          "alias": "WINNT_x86-msvc"
        },
        "WINNT_x86_64-msvc": {
          "fileUrl": "https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1582.2-win-x64.zip",
          "filesize": 5097580,
          "hashValue": "8054294ad328f0b32e7474448e77fb4c56dbe4e7100920461508dd18cab94f69b13dbc1e9776800f49993d478827b4a65732a9bc39a3940251d9cb96ffffddd9"
        },
        "WINNT_x86_64-msvc-x64": {
          "alias": "WINNT_x86_64-msvc"
        }
      },
      "version": "4.10.1582.2"
    }
  }
}

Comment 3

[Jordan Lund (:jlund)]

Attachment: nightlytest_rule.png

@bryce - adding the release json and screenshot of rules for some transparency. You can test against nightlytest at any time.

Comment 4

[Bryce Seager van Dyk [:bryce] (he/him) - Not reading bugmail]

Thanks. I'll get to testing.

Comment 5

[Bryce Seager van Dyk [:bryce] (he/him) - Not reading bugmail]

There's some discussion in media that we may want to hold until the the next Widevine release, but are clarifying when that will arrive. Holding NI.

Comment 6

[Bryce Seager van Dyk [:bryce] (he/him) - Not reading bugmail]

Following up on my previous comment, we are choosing to move ahead with this update. Bug 1601813 resulted in a delay in my testing of the new CDM, but I expect to test against nightly 73 upon it landing (as 72 has now moved to beta).

Comment 7

[Bryce Seager van Dyk [:bryce] (he/him) - Not reading bugmail]

I've tested the new CDM using nightlytest on nightly 73 and have not had any issues, so I think we can roll the CDM out and let it ride the trains. Since this relies on bug 1601813 we only want to target builds that have those changes, which landed on 2019-12-07 (looks like buildID >= 20191207092617).

Jordan, could you please check my working on the buildID above, as Widevine rule changes involving buildIDs are rare for me. Provided my working is good, could we update the rules to serve the CDMs discussed in comment 0, but to >= 73.0a1, only for buildID >= 20191207092617, and to target all/null channels?

Comment 8

[Jordan Lund (:jlund)]

Okay, I've queued this up for sign-off.

The buildid you gave matches: https://balrog.services.mozilla.com/releases/Firefox-mozilla-central-nightly-20191207092617

which lives here: https://archive.mozilla.org/pub/firefox/nightly/2019/12/2019-12-07-09-26-17-mozilla-central/

So I set the buildid>=20191207092617, bumped the min version to >=73.0a1 (it was 72.0 when we first started this bug), and removed the channel so that any channel is valid.

ryanvm or julien, could you sign off on this: https://balrog.services.mozilla.com/rules?product=Widevine#scId=2118

Comment 9

[Julien Cristau [:jcristau]]

I have signed off.

As a side note I wonder if we could get the widevine rule set so that (outside of the esr rules) they'd be sorted by increasing versions. It's pretty hard right now to figure out who gets what.

Comment 10

[Bryce Seager van Dyk [:bryce] (he/him) - Not reading bugmail]

Could we create rules to target ESR 68.5 for this version of Widevine, please?

Comment 11

[Jordan Lund (:jlund)]

Scheduled the change. Requesting sign off from relman

Comment 12

[Jordan Lund (:jlund)]

Attachment: Screen Shot 2020-01-23 at 11.30.55.png

Comment 13

[Jordan Lund (:jlund)]

Attachment: Screen Shot 2020-01-23 at 11.30.47.png

Comment 14

[Jordan Lund (:jlund)]

bryce: see comment 12 and 13. Do you think any of these rules can be deleted? I suspect many of them are pretty old and we don't really have many users on those versions that we need to provide widevine updates for?

We can leave them if you prefer. Just thought I'd house clean while I'm here.

Comment 15

[Jordan Lund (:jlund)]

(In reply to Jordan Lund (:jlund) from comment #11)

Scheduled the change. Requesting sign off from relman

I forgot to mention that this was signed off

Comment 16

[Bryce Seager van Dyk [:bryce] (he/him) - Not reading bugmail]

Thank you.

Acking. Holding NI while I try and gather usage data to understand user impact of removing/merging old rules.