From: Ricardo Ribalda <ribalda@chromium.org>
To: Brian Morrison <bdm@fenrir.org.uk>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Foscam W21 webcam not working in Fedora 37 with kernel-5.19.11
Date: Tue, 27 Sep 2022 15:57:12 +0200 [thread overview]
Message-ID: <CANiDSCtKTzUs_D1OTwi57B1ssLOSszNbP+oX9q5LTG0PEvt7Ug@mail.gmail.com> (raw)
In-Reply-To: <20220927144247.71ad1b8f@deangelis.fenrir.org.uk>
On Tue, 27 Sept 2022 at 15:42, Brian Morrison <bdm@fenrir.org.uk> wrote:
>
> On Tue, 27 Sep 2022 15:34:51 +0200
> Ricardo Ribalda <ribalda@chromium.org> wrote:
>
> > I am afraid that you need to ask in the fedora forum/ML why they are
> > not authorizing the device by default. Maybe some user reported some
> > malfunction with that device?
>
> So this is not a kernel-related issue? I don't know how this sort of
> authorization is controlled, perhaps you know?
>
It is not kernel related. Every distro handles that differently:
https://docs.kernel.org/usb/authorization.html
Maybe someone on the list knows how fedora does it. A fast google
search shows: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/sec-using-usbguard
Try on the fedora mailing list.
> --
>
> Brian Morrison
--
Ricardo Ribalda
prev parent reply other threads:[~2022-09-27 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 23:12 Foscam W21 webcam not working in Fedora 37 with kernel-5.19.11 Brian Morrison
2022-09-26 7:22 ` Ricardo Ribalda
2022-09-26 11:14 ` Brian Morrison
2022-09-26 15:34 ` Brian Morrison
2022-09-27 11:23 ` Ricardo Ribalda
[not found] ` <20220927135459.7d614076@deangelis.fenrir.org.uk>
2022-09-27 13:02 ` Ricardo Ribalda
2022-09-27 13:30 ` Brian Morrison
2022-09-27 13:34 ` Ricardo Ribalda
[not found] ` <20220927144247.71ad1b8f@deangelis.fenrir.org.uk>
2022-09-27 13:57 ` Ricardo Ribalda [this message]
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=CANiDSCtKTzUs_D1OTwi57B1ssLOSszNbP+oX9q5LTG0PEvt7Ug@mail.gmail.com \
--to=ribalda@chromium.org \
--cc=bdm@fenrir.org.uk \
--cc=linux-media@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.