awslabs / awslabs/speke-reference-server
SPEKE key is same for all Segemnts- No key Rotation.
- Dominant language
- Python
- Stars
- 124
- Forks
- 50
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 1
Description
I have created Job in MediaConvert
for Apple HLS AES-128 encryption by following guidance and setup the speke-reference-server.
but when I download the media file, for each segment the key is the same and it's not rotating for every segment.
used SystemId is: 81376844-f976-481e-a84e-cc25d39b0b33
Media File:
```
#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:13
#EXT-X-MEDIA-SEQUENCE:1
#EXT-X-PLAYLIST-TYPE:VOD
#EXT-X-KEY:METHOD=AES-128,URI="https://d3dmokwem007n8.cloudfront.net/af4672a0-9605-4d2e-8818-60c1f5b1c3f4/66de1985-cc52-4cbe-a86c-38c2515fb3e7",IV=0x00000000000000000000000000000001
#EXTINF:12,
db72c853-97dc-4e22-866e-3909e0f2bd6eTest_01_00001.ts
#EXT-X-KEY:METHOD=AES-128,URI="https://d3dmokwem007n8.cloudfront.net/af4672a0-9605-4d2e-8818-60c1f5b1c3f4/66de1985-cc52-4cbe-a86c-38c2515fb3e7",IV=0x00000000000000000000000000000002
#EXTINF:9,
db72c853-97dc-4e22-866e-3909e0f2bd6eTest_01_00002.ts
#EXT-X-ENDLIST
```
Need Help
or any suggestion to achieve a separate key for each segment.
Contributor guide
Research direction
Start by reproducing the MediaConvert Apple HLS AES-128 setup with the speke-reference-server and compare the playlist's EXT-X-KEY URIs, IVs, and SPEKE requests across segments. Done means establishing whether per-segment key rotation is supported or identifying the documented configuration or server change required to produce separate keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100