AES decryption issue

[Axymeus]

I have a playlist that contains the following

#EXT-X-KEY:METHOD=AES-128,URI="https://[...]",IV=0x3230386236373936636331332d346433

When I try to decrypt the video using the provided key with an iv of 0 as I always try by default, it fails. When I try to use the iv above it says "hex string is too long/invalid hex iv value" how is that possible? I'm using openssl to do the decryption.

[2nHxWW6GkN1l916N3ayz8HQoi]

Video URL or at least playlist m3u8 URL?

[Axymeus]

Password protected. That's why I'm only asking about this issue with the IV string.

[lomero]

see this thread

[Axymeus]

Interesting, but it doesn't seem to work either. Must be a particularity of this video. At least your tool accepts the hex string so I guess it answered my question.

[2nHxWW6GkN1l916N3ayz8HQoi]

Can't do much without access. Find a person you trust and talk in private messages

[LZAA]

IV=3230386236373936636331332d346433 ?

[Axymeus]

Oh you mean without the 0x? Yeah it's accepted like that but the decryption is still failing. Actually it's starting to look a little odd, it's a video delivered through mediadelivery.net, but nothing I've tried is working so far.

What do you do when a request that works in your browser, doesn't work outside of it? Here's the part that's troubling me: I can see the GET request for the drm key in the browser's devtools. If I copy the request as curl and tries that in my terminal, it returns a 404. If I copy the request as fetch and try to run it from the browser's console, it *also* returns a 404. I don't understand how that's possible. It's a basic GET without any cookies, just the usual headers.

[Frieren]

https://github.com/mal1k-me/bunny-cdn-drm-video-dl

[Axymeus]

Yes I've tried that already and it does absolutely nothing.

Doesn't help that it has no error handling or anything.

[sarvo99]

where's the video link ?