* [FFmpeg-devel] Bug report
@ 2022-04-20 12:56 Dan Rose
2022-04-20 20:24 ` Leo Izen
0 siblings, 1 reply; 2+ messages in thread
From: Dan Rose @ 2022-04-20 12:56 UTC (permalink / raw)
To: ffmpeg-devel
I tried to submit this on the bug tracker, but it never sent a verification email so posting here.
The `-protocol_whitelist ALL` option appears to be broken. I expect it to allow any protocol as per documentation https://ffmpeg.org/ffmpeg-protocols.html#Protocol-Options
> Set a ","-separated list of allowed protocols. "ALL" matches all protocols.
It seems to not match any protocols at all:
$ ffmpeg -v 9 -loglevel 99 -protocol_whitelist ALL -i file://in.mp4 out.mp4L
ffmpeg version N-106633-g25d3f96db7 Copyright (c) 2000-2022 the FFmpeg developers
built with Apple clang version 13.1.6 (clang-1316.0.21.2.3)
configuration: --prefix=/opt/homebrew/Cellar/ffmpeg/HEAD-25d3f96 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libdav1d --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librist --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack --enable-videotoolbox --enable-neon
libavutil 57. 24.101 / 57. 24.101
libavcodec 59. 26.100 / 59. 26.100
libavformat 59. 22.100 / 59. 22.100
libavdevice 59. 6.100 / 59. 6.100
libavfilter 8. 33.100 / 8. 33.100
libswscale 6. 6.100 / 6. 6.100
libswresample 4. 6.100 / 4. 6.100
libpostproc 56. 5.100 / 56. 5.100
Splitting the commandline.
Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'.
Reading option '-protocol_whitelist' ... matched as AVOption 'protocol_whitelist' with argument 'ALL'.
Reading option '-i' ... matched as input url with argument 'file://in.mp4'.
Reading option 'out.mp4L' ... matched as output url.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option v (set logging level) with argument 9.
Successfully parsed a group of options.
Parsing a group of options: input url file://in.mp4.
Successfully parsed a group of options.
Opening an input file: file://in.mp4.
[NULL @ 0x13f605000] Opening 'file://in.mp4' for reading
[file @ 0x13f604ae0] Protocol 'file' not on whitelist 'ALL'!
file://in.mp4: Invalid argument
_______________________________________________
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".
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [FFmpeg-devel] Bug report
2022-04-20 12:56 [FFmpeg-devel] Bug report Dan Rose
@ 2022-04-20 20:24 ` Leo Izen
0 siblings, 0 replies; 2+ messages in thread
From: Leo Izen @ 2022-04-20 20:24 UTC (permalink / raw)
To: ffmpeg-devel
On 4/20/22 08:56, Dan Rose wrote:
> I tried to submit this on the bug tracker, but it never sent a verification email so posting here.
>
> The `-protocol_whitelist ALL` option appears to be broken. I expect it to allow any protocol as per documentation https://ffmpeg.org/ffmpeg-protocols.html#Protocol-Options
>> Set a ","-separated list of allowed protocols. "ALL" matches all protocols.
The problem here is that ffurl_connect calls av_match_list instead of
av_match_name. For some reason, av_match_name treats "ALL" as a proper
wildcard, but av_match_list does not. av_match_name assumes ',' as the
delimiter, which should work in this context.
_______________________________________________
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".
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-04-20 20:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-20 12:56 [FFmpeg-devel] Bug report Dan Rose
2022-04-20 20:24 ` Leo Izen
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