From: Mark Gaiser <markg85@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Would a crypto file be acceptable?
Date: Wed, 28 Dec 2022 17:58:49 +0100
Message-ID: <CAPd6JnFWxar=2eiiDXH2BUUOyJYCAT8j0Q_bQcXsPvKnJ-rs2g@mail.gmail.com> (raw)
In-Reply-To: <Y6xvLWuO6szdaaG8@phare.normalesup.org>
On Wed, Dec 28, 2022 at 5:30 PM Nicolas George <george@nsup.org> wrote:
> Mark Gaiser (12022-12-28):
> > > Ok, that made me laugh :)
>
> I did not write that. And that feels rude.
>
> > Please correct me as I'm probably wrong.
> > But where did anyone say that there was a working alternative solution
> that
> > did not require customizing how ffmpeg is used?
> > Like disabling safe.
>
> Heuristics to not require safe in cases where it is quite safe would be
> much more acceptable than a redundant ad-hoc format.
>
That works for me.
But is that feasible?
My thinking is that you'd need to parse the entire file (the concat thing)
to know if it is safe or not.
>
> --
> Nicolas George
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-12-28 17:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 15:44 Mark Gaiser
2022-12-21 16:00 ` Mark Gaiser
2022-12-22 19:14 ` Gregor Riepl
2022-12-23 1:26 ` Mark Gaiser
2022-12-23 17:45 ` Gregor Riepl
2022-12-22 10:40 ` Nicolas George
2022-12-22 15:53 ` Mark Gaiser
2022-12-22 17:50 ` Hendrik Leppkes
2022-12-23 11:04 ` Tomas Härdin
2022-12-23 16:31 ` Mark Gaiser
2022-12-23 16:33 ` Nicolas George
2022-12-23 17:00 ` Mark Gaiser
2022-12-23 17:38 ` Nicolas George
2022-12-26 10:58 ` Tomas Härdin
2022-12-26 11:00 ` Nicolas George
2022-12-26 11:18 ` Tomas Härdin
2022-12-26 11:24 ` Nicolas George
2022-12-27 18:24 ` Mark Gaiser
2022-12-27 21:40 ` Michael Niedermayer
2022-12-27 22:46 ` Mark Gaiser
2022-12-28 14:27 ` Ronald S. Bultje
2022-12-28 16:13 ` Mark Gaiser
2022-12-28 16:22 ` Nicolas George
2022-12-28 16:27 ` Mark Gaiser
2022-12-28 16:30 ` Nicolas George
2022-12-28 16:58 ` Mark Gaiser [this message]
2022-12-29 14:04 ` Ronald S. Bultje
2022-12-28 21:02 ` Michael Niedermayer
2022-12-29 14:51 ` Mark Gaiser
2022-12-29 22:34 ` Michael Niedermayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPd6JnFWxar=2eiiDXH2BUUOyJYCAT8j0Q_bQcXsPvKnJ-rs2g@mail.gmail.com' \
--to=markg85@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git