From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] [RFC] avformat: Add basic same origin check Date: Wed, 3 May 2023 15:33:59 +0200 Message-ID: <20230503133359.GD1391451@pb2> (raw) In-Reply-To: <09C1198A-DB0A-43CC-ADCA-23594E0BFEDA@remlab.net> [-- Attachment #1.1: Type: text/plain, Size: 1831 bytes --] Hi On Wed, May 03, 2023 at 02:16:03PM +0300, Rémi Denis-Courmont wrote: > Nit: different fixed > > But is there an actual threat model whence it is necessary or even useful for a media framework to implement origin policies? On top of my head, this can be used by content providers to prevent third parties from referencing their media files... but that seems user-hostile; it does not provide any security for the user of FFmpeg. > > I could be wrong, but IMU, origin policy is meant to prevent harmful embedding of images and frames, and to prevent cross-site scripting, but FFmpeg doesn't support either if these anyway, so it's not concerned. This patch was inspired by a report on ffmpeg-security about SSRF (for which custom io_open() callback or soem sort of sandboxing/VM can be used to avoid it) The patch here was intended to explore if we can provide something thats better tahn currently by default But the same issue with roles flipped occurs for the end user and the user cannot be expected to setup a custom io_open() callback for his player The current code can be also used to poke around the local network of the user. Which is unexpected by the user for example a avi file could be probed as a m3u8 playlist and then poke around on the local net while mixing that with remote urls from the timing of the remote accesses the remote party should be able to infer what happened with the local poking. Did it timeout? was the access rejected ? was there a file that was read and probed/played ? thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Whats the most studid thing your enemy could do ? Blow himself up Whats the most studid thing you could do ? Give up your rights and freedom because your enemy blew himself up. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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:[~2023-05-03 13:34 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-02 19:36 Michael Niedermayer 2023-05-02 20:00 ` James Almer 2023-05-02 20:16 ` Michael Niedermayer 2023-05-02 20:57 ` James Almer 2023-05-02 21:15 ` Michael Niedermayer 2023-05-03 9:26 ` Anton Khirnov 2023-05-03 10:05 ` Hendrik Leppkes 2023-05-03 10:49 ` Michael Niedermayer 2023-05-03 12:24 ` Hendrik Leppkes 2023-05-03 19:08 ` Michael Niedermayer 2023-05-03 21:01 ` Timo Rothenpieler 2023-05-03 22:26 ` Michael Niedermayer 2023-05-03 9:23 ` Anton Khirnov 2023-05-03 11:16 ` Rémi Denis-Courmont 2023-05-03 13:33 ` Michael Niedermayer [this message] 2023-05-03 16:07 ` Rémi Denis-Courmont 2023-05-03 19:05 ` Michael Niedermayer 2023-05-03 19:35 ` Rémi Denis-Courmont
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=20230503133359.GD1391451@pb2 \ --to=michael@niedermayer.cc \ --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