New issue
Advanced search Search tips

Issue 721935 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Enable Clear Key key system support in MediaDrmBridge

Project Member Reported by xhw...@chromium.org, May 12 2017

Issue description

MediaDrm has Clear Key key system support. We should enable it in MediaDrmBridge so that we can test paths that only work with MediaDrm based CDM, e.g. AVDA.
 
This should only be enabled for testing for security reasons. Also, I'm not sure that all supported versions of Android have this support.
Project Member

Comment 2 by bugdroid1@chromium.org, May 13 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9d5f354616dea455ea08345c96b67081275a865d

commit 9d5f354616dea455ea08345c96b67081275a865d
Author: xhwang <xhwang@chromium.org>
Date: Sat May 13 03:57:41 2017

media: Add mojo_media_config to media/gpu configs

Otherwise, macros like ENABLE_MOJO_MEDIA_IN_GPU_PROCESS are not defined.
We should switch to use BUILDFLAG to prevent this from happening, that
is tracked by  issue 596252 .

BUG= 596252 ,721935
TEST=Manually tested encrypted playback.
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2876123004
Cr-Commit-Position: refs/heads/master@{#471553}

[modify] https://crrev.com/9d5f354616dea455ea08345c96b67081275a865d/media/gpu/BUILD.gn

Project Member

Comment 3 by sheriffbot@chromium.org, May 14 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by xhw...@chromium.org, May 14 2018

Labels: -Pri-3 M-70 Pri-2
Status: Assigned (was: Untriaged)
This is actually becoming more and more important given the difficulty in testing Widevine directly.
Labels: -M-70 M-72
Labels: Target-72
Cc: -jrumm...@chromium.org xhw...@chromium.org
Labels: -M-72 -Target-72 M-74 Target-74
Owner: jrumm...@chromium.org

Sign in to add a comment