From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Oleksandr Natalenko <oleksandr@natalenko.name>,
linux-media@vger.kernel.org, jani.nikula@linux.intel.com,
anisse@astier.eu, Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Ricardo Ribalda <ribalda@chromium.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] media: Virtual camera driver
Date: Mon, 2 Feb 2026 13:43:17 +0200 [thread overview]
Message-ID: <20260202114317.GB4173464@killaraus> (raw)
In-Reply-To: <aYBsBw2j6pkwAssn@kernel.org>
On Mon, Feb 02, 2026 at 11:19:03AM +0200, Jarkko Sakkinen wrote:
> On Mon, Feb 02, 2026 at 11:05:52AM +0200, Jarkko Sakkinen wrote:
> > On Mon, Feb 02, 2026 at 02:02:14AM +0100, Mauro Carvalho Chehab wrote:
> > > On Mon, 02 Feb 2026 00:25:37 +0100 Oleksandr Natalenko wrote:
> > > > On pondělí 2. února 2026 0:17:20, středoevropský standardní čas Mauro Carvalho Chehab wrote:
> > > > > No. At the machine with the camera, obs can read from a V4L2 input,
> > > > > generate a mpeg TS stream, and listen to a UDP port (for instance).
> > > > >
> > > > > At the remote machine, you can just pass the URL to ffmpeg.
> > > >
> > > > I can't, I have to feed the stream into Firefox somehow for it to see the stream as a virtual webcam.
> > >
> > > Motioneye could be used on such scenario. It has a proper web
> > > interface, allows multiple users to watch, has login control accepts
> > > multiple cameras.
> >
> > When proposed workarounds move in the area of motion detection systems
> > it feels like there was a competion who invents the most impractical
> > solution for a practical real-world problem out in the wild.
I'm also not quite sure how motioneye would be related. Please see my
reply to Gergo in this mail thread for a proposed solution that is (in
my opinion) not a workaround.
> A trivial Google search shows that the scope of the issue, which is
> also (on emphasis) a security issue, and net effect that is caused
> of not addressing it properly.
How is it a security issue ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-02-02 11:43 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 13:33 [RFC PATCH] media: Virtual camera driver Jarkko Sakkinen
2026-02-01 18:20 ` Laurent Pinchart
2026-02-01 19:04 ` Jarkko Sakkinen
2026-02-01 20:06 ` Laurent Pinchart
2026-02-01 20:14 ` Oleksandr Natalenko
2026-02-01 20:21 ` Mauro Carvalho Chehab
2026-02-01 20:26 ` Oleksandr Natalenko
2026-02-01 23:17 ` Mauro Carvalho Chehab
2026-02-01 23:17 ` Mauro Carvalho Chehab
2026-02-01 23:25 ` Oleksandr Natalenko
2026-02-02 1:02 ` Mauro Carvalho Chehab
2026-02-02 7:16 ` Oleksandr Natalenko
2026-02-02 11:41 ` Laurent Pinchart
2026-02-02 9:05 ` Jarkko Sakkinen
2026-02-02 9:19 ` Jarkko Sakkinen
2026-02-02 11:43 ` Laurent Pinchart [this message]
2026-02-02 11:36 ` Gergo Koteles
2026-02-02 11:40 ` Laurent Pinchart
2026-02-02 11:45 ` Oleksandr Natalenko
2026-02-03 1:23 ` Laurent Pinchart
2026-02-03 14:38 ` Oleksandr Natalenko
2026-02-03 14:53 ` Laurent Pinchart
2026-02-03 20:36 ` Laurent Pinchart
2026-02-03 21:39 ` Oleksandr Natalenko
2026-02-03 21:49 ` Laurent Pinchart
2026-02-03 20:49 ` Laurent Pinchart
2026-02-01 20:22 ` Laurent Pinchart
2026-02-01 20:27 ` Oleksandr Natalenko
2026-02-01 20:41 ` Laurent Pinchart
2026-02-01 20:35 ` Jarkko Sakkinen
2026-02-01 20:54 ` Jarkko Sakkinen
2026-02-01 21:09 ` Laurent Pinchart
2026-02-02 1:44 ` Jarkko Sakkinen
2026-02-01 21:01 ` Laurent Pinchart
2026-02-01 22:03 ` Jarkko Sakkinen
2026-02-03 9:50 ` Jani Nikula
2026-02-03 15:06 ` Laurent Pinchart
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=20260202114317.GB4173464@killaraus \
--to=laurent.pinchart@ideasonboard.com \
--cc=anisse@astier.eu \
--cc=hverkuil@kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=jani.nikula@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=oleksandr@natalenko.name \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox