New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When I manipulated the device's time into the past, Offline Playback continues despite LicenseDuration expiration. #2622

Closed
brosvaby opened this Issue Mar 29, 2017 · 18 comments

Comments

Projects
None yet
9 participants
@brosvaby

brosvaby commented Mar 29, 2017

Issue description

the bottom line is that when I manipulated the device time into the past, mediadrm have not detected a change in device time. Playback continues despite expiration.

I succeeded in offline license acquisition and content playback using widevine drm.
We set the license period to 300 sec and confirmed LicenseDurationRemaining to 300 sec. In normal cases, a period expiration event occurs after 300 seconds and playback does not occur. However, during license has not been deleted, we have confirmed that if the device time is changed to 5 minutes ago, LicenseDurationRemaining increases and the playback continues even though the time to expire has passed.

The bottom line is that we have not detected a change in device time.

Reproduction steps

  1. download offline license.
  2. play the content offline
  3. Normally, confirm that LicenseDurationRemaining has been getting reduced.
  4. at your device : Settings -> Date & time -> turn off Auto-date & time
  5. at your device : Settings -> Date & time -> Set date -> turn back time
  6. Make sure that playback continues after the expiration time.

Version of ExoPlayer being used

2.3.0

Device(s) and version(s) of Android being used

device : All devices
version : 5.0 and over (5.0, 6.0, 7.0)

@ojw28 ojw28 added the question label Mar 29, 2017

@brosvaby

This comment has been minimized.

brosvaby commented Mar 31, 2017

Is anything updated?
For the above reasons, I think that we can't control period of expiration offline.
Do I misunderstand offline scenarios?
For example, is it necessary to control in the app area for device time manipulation?

@wvpaf

This comment has been minimized.

wvpaf commented Apr 25, 2017

Hi @brosvaby can you please provide a ADB bugreport. We need to understand what the device is running and what the system thinks is happening.

@wvpaf

This comment has been minimized.

wvpaf commented May 9, 2017

Hi @brosvaby any luck on the ADB bugreport?

@brosvaby

This comment has been minimized.

brosvaby commented May 15, 2017

Actions (please refer to below steps)

  1. I downloaded offline license at 12:24
  2. I Disconnected Wifi and LTE.
  3. I checked duration is 180 sec.
  4. I couldn't play content after 12:27
  5. However, after I returned the device time to 12:25 minutes, it was possible to play the content.
  6. You can always replay the device time back to 12:25 minutes without re-receiving the license
    (Attach the report.)
    bugreport-NRD90M-2017-05-15-12-25-50.zip

Is this the right scenario?

@daniel-inka

This comment has been minimized.

daniel-inka commented May 16, 2017

To support DTR(download to rent) scenario, there must be a way to prevent device-time manipulation as above. Maybe it is Widevine CDM's role, or it may be implemented in application level.
Anybody to confirm or advise on this issue?

@jefftinker

This comment has been minimized.

Collaborator

jefftinker commented May 23, 2017

Thank you for reporting this issue, we have opened an internal bug against the Widevine CDM and will investigate it further.

@uthonangi

This comment has been minimized.

uthonangi commented Jun 21, 2017

@jefftinker I am sorry but this is stunning. We can reproduce this issue as well and we are in a pretty bad spot. Rentals are essentially broken on WV and it is not even documented anywhere as a known issue on the WV side. Can you please give us an update when you get a minute on the status of the WV bug? I know this forum is not for WV bugs but such a fundamental piece of functionality being broken is disappointing.

@ram992

This comment has been minimized.

ram992 commented Jul 27, 2017

Hello @ojw28,
Any update on this issue, cause this is haunting my Downloaded content being valid for a particular time.

@ram992

This comment has been minimized.

ram992 commented Jul 27, 2017

Hey I got one more issue, If the device time is set in future and the license is requested, and if the device time is set to the current one, the license is valid till the end of future time+ it's expiry time period.
Like if for example my license is valid for 1 week, and I fast-forward the device time to one week, then downloaded the license whose validity is one week ,then the validity of the license is 2 weeks if I reset the device time.
How can I resolve this.

@ojw28

This comment has been minimized.

Contributor

ojw28 commented Jul 31, 2017

This is not an ExoPlayer issue. You need to get a response from Widevine (@wvpaf, @jefftinker, or by communicating directly with Widevine if you have a relationship with them).

@ram992

This comment has been minimized.

ram992 commented Aug 1, 2017

Hello @ojw28 how do we communicate with Widevine, any info would be great.
And does this communication needs to done at the time of license fetching ??

@wvpaf

This comment has been minimized.

wvpaf commented Aug 1, 2017

Hi if you are a Widevine partner you should have access to our CWIP/partner site. If not this is the next best method of communication.
Investigation continues.

@wvpaf

This comment has been minimized.

wvpaf commented Aug 29, 2017

quick update there is ongoing work to investigate and address this issue. Thank you for you patience.

@wvpaf

This comment has been minimized.

wvpaf commented Sep 12, 2017

potential fix in test now. will provide update on availability soon.

@ram992

This comment has been minimized.

ram992 commented Sep 14, 2017

@wvpaf can you comment on the time frame of the availability of the fix, and is it compatible with exoPlayer v2.2.0, as I am not in a position to update to the latest one now.

@wvpaf

This comment has been minimized.

wvpaf commented Sep 26, 2017

Looks like a fix for this case is intended to land in O MR1

@wvpaf wvpaf closed this Sep 26, 2017

@adesentenac

This comment has been minimized.

adesentenac commented Oct 3, 2017

@wvpaf Does that mean that this behavior will stay the same on Android versions before O?

@fredgc

This comment has been minimized.

Collaborator

fredgc commented Oct 10, 2017

@adesentenac: yes, the behavior for versions O and before will remain the same. It is unlikely for devices to receive field updates for older versions that are not security patches.

@google google locked and limited conversation to collaborators Jan 25, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.