dedicated test programs; libavformat/tests/aes.c may be
a good example to start with?
Seems to just return 0 if OK, and 1 if fail?
s
On Tue, Aug 30, 2016 at 4:17 PM, Michael Niedermayer wrote:
> On Tue, Aug 30, 2016 at 09:47:12AM +0100, Simon H wrote:
> >
libavformat-crypto-add-seek.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
patch split and advice taken :)
libavformat-crypto-buffer-count.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
thanks Michael,
try the attached file. I assume the corruption came from email word
wrapping? or was there something else wrong?
simon
On Mon, Aug 29, 2016 at 6:11 PM, Michael Niedermayer wrote:
> On Mon, Aug 29, 2016 at 11:08:36AM +0100, Simon H wrote:
> > crypto allows readin
crypto allows reading of data which has been aes-128-cbc encrypted given a
key and an iv.
But it did not handle filetypes which require seeking... e.g. it failed on
an encrypted .mp4 file.
example:
take 25.mp4 created with:
ffmpeg -f lavfi -i sine=frequency=1000:beep_factor=2:r=48000:duration=720
