IPTV Recorder HLS AES-128 Problem

[wnhtr2011@…]

I am unable to get the IPTV recorder to work with HLS AES-128 encrypted TS streams (such as this one: playertest.longtailvideo.com/adaptive/oceans_aes/oceans_aes.m3u8). The IPTV recorder works fine with unencrypted HLS streams.

I have compiled with the "USING_LIBCRYPTO" option and have libcrypto installed. Additional debugging shows that in HLSReader.cpp, the statement on line 1297 "if (segment.HasKeyPath?())" is returning false even though the stream has the #EXT-KEY-KEY manifest entry that was successfully parsed by myth (and logged as an AES stream in mythtvbackend).

Debugging backend logs also shows that the ts segments are downloading fine, but there is no attempt to download the AES keys.

[wnhtr2011@…]

backend log

[wnhtr2011@…]

I have fixed this issue and will provide details and patch later after some more testing.

[wnhtr2011@…]

Attached is the patch. This will resolve the issue of myth not downloading the AES-128 Keys on encrypted segments.

[JYA]

this seems wrong to me.

With HLS a key can be defined per stream ; per segment or for the entire hls.

While your patch may fix it for you, it likely breaks it where the key is defined per segment

[stuartm]

Yes, the patch cannot be accepted in it's current form for this reason.

[wnhtr2011@…]

Replying to jyavenard:

this seems wrong to me.

With HLS a key can be defined per stream ; per segment or for the entire hls.

While your patch may fix it for you, it likely breaks it where the key is defined per segment

Actually, I was wondering about that, however, my testing was with streams that rotate keys every 10min and the patch works perfectly. When the key rotates, the playlist (for a given ABR representation) has 2 key entries. Each EXT-X-KEY sets the key for the segments below it (until the next EXT-X-KEY entry). This should be able to handle the worst case where each segment has its own key (designated with its own preceeding EXT-X-KEY entry).

[Stuart Auchterlonie]

Moving unresolved tickets to next point release

[Stuart Auchterlonie]

Moving remaining open 0.28.1 tickets to 0.28.2

[Stuart Auchterlonie]

Closing any remaining tickets for 0.28, if the issue persists, feel free to reopen and align to v29 or master