asciidisco / asciidisco/plugin.video.netflix

Conversion to MSL V2 API

Open
#682 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.2k
Forks
213
PR merge metrics
No merged PRs in 30d

Description

*I'm submitting a ...*
- [ ] bug report
- [ ] feature request
- [X ] support request

## General infomration
Is there any reason you didn't implement the V2 format for the cipher text envelope when the header has been converted?

There is nothing about the V2 format in MSLCrypto.py and the 'cipherspec' line is commented out and the version set to 1 in MSLMediaDrm.py.
### Prerequisites

* [ ] Are you running the latest version?

### Description

[Description of the bug or feature]

### Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on...]

**Expected behavior:** [What you expected to happen]

**Actual behavior:** [What actually happened]

## Context (Environment)

### Installation

* [ ] I installed the plugin via zip from the Releases page
* [ ] I´m using the Netflix Repo
* [ ] I´m using a different source (Please tell which)

### Operating System

* [ ] Linux (x86/x64)
* [ ] OSX (x86/x64)
* [ ] Windows (x86/x64)
* [ ] Linux (ARM)
* [ ] Android

#### Additional informatin on the environment

[Descripe your environment a bit more detailed, are you using LibreElec f.e.]

## Debug log

[Please include a link to your debug log (use something like [http://sprunge.us/](http://sprunge.us/)) or similar, please do not paste]

## Other information

[e.g. detailed explanation, related issues, suggestions how to fix, links for us to have context, etc.]

### Screenshots

[Please add a screenshot if that helps understanding your problem]

[You can erase any parts of this template not applicable to your Issue.]

Contributor guide

Open the contributing guide

Research direction

Start by reading MSLCrypto.py and MSLMediaDrm.py, focusing on the commented cipherspec line and the version value mentioned in the report. Compare the existing header conversion with the referenced MSL V2 cipher-text envelope requirements. The issue does not provide reproduction details or a defined acceptance test, so confirm the intended behavior before estimating completion.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.