Skip to content

Conversation

gvking
Copy link
Contributor

@gvking gvking commented Jun 16, 2025

The PlayReady key system string should be updated to "com.microsoft.playready.recommendation.3000". This is to trigger the HWDRM permissions that PlayReady uses.

@lgarron
Copy link
Collaborator

lgarron commented Jun 16, 2025

https://learn.microsoft.com/en-us/playready/overview/key-system-strings suggests both com.microsoft.playready.recommendation and com.microsoft.playready.recommendation.3000 are active?

@gvking
Copy link
Contributor Author

gvking commented Jun 16, 2025

I understood it as:

If we just wanted one key system from each DRM provider, we should test the 3000, as that will test HWDRM and the permissions that come along with that.

@gvking gvking changed the title Update PlayReady key system string Add PlayReady HWDRM key system string Jun 16, 2025
@gvking
Copy link
Contributor Author

gvking commented Jun 16, 2025

Upon further thought, you're right, we should keep the playready key system string, and also add com.microsoft.playready.recommendation.3000 so we test HWDRM permission changes.

@lgarron
Copy link
Collaborator

lgarron commented Jun 18, 2025

Sounds good to me, I'll leave @engedy and @andypaicu to approve /& merge.

@engedy engedy merged commit cd59be7 into chromium:master Jun 20, 2025
2 checks passed
@gvking gvking deleted the main branch June 20, 2025 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants