The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
	"Henrique de Moraes Holschuh" <ibm-acpi@hmh.eng.br>,
	ibm-acpi-devel@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: ThinkPad T480s & LED_MUTE, LED_MICMUTE
Date: Sat, 16 Jun 2018 17:58:44 +0200	[thread overview]
Message-ID: <20180616155844.GA19005@amd> (raw)
In-Reply-To: <20180616141231.dy4mvirgeax2tviq@khazad-dum.debian.net>

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

Hi!

> > Question is if we want flexibility or security.
> 
> For thinkpad-acpi, it is security by default.  Flexibility is allowed as
> *compile*-time (Kconfig) option, and only as long as it defaults to
> secure *and* the help text is very explicit at instructing distros to
> NOT enable this option.

Yep, no problem with that.

> That said, if mic-mute is under HDA mixer control, it will only be
> "secure" if ALSA is also blocking userspace access to the relevant bits,
> and if that is not possible to do properly, might as well go for
> flexibility.  But only in that case.

That also makes sense.

> That would be why I use phisical shutters on embedded webcams unless the
> hardware actually airgaps them from the USB bus when the privacy switch
> is active.

And yes, I use them, too.
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-06-16 15:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08 11:10 ThinkPad T480s & LED_MUTE, LED_MICMUTE Pali Rohár
2018-06-15 11:26 ` Pavel Machek
2018-06-15 11:37   ` Pali Rohár
2018-06-15 12:30     ` Henrique de Moraes Holschuh
2018-06-15 19:09       ` Pali Rohár
2018-06-15 23:36         ` Henrique de Moraes Holschuh
2018-06-16  7:33           ` Pavel Machek
2018-06-16 14:12             ` Henrique de Moraes Holschuh
2018-06-16 15:58               ` Pavel Machek [this message]
2018-06-18 10:11           ` Pali Rohár
2018-06-21 11:37             ` Pali Rohár
2018-06-15 12:51 ` Takashi Iwai
2018-06-15 19:09   ` Pali Rohár
2018-06-16  7:05     ` Takashi Iwai
2018-06-16 15:43       ` Pali Rohár
2018-06-16 16:02         ` Takashi Iwai
2018-06-18 10:28           ` Pali Rohár
2018-06-18 10:36             ` Takashi Iwai
2018-06-18 11:21               ` Pali Rohár
2018-06-18 11:26                 ` Pali Rohár
2018-06-18 15:35                   ` Takashi Iwai
2018-06-21 11:30                     ` Pali Rohár
2018-06-21 11:35                       ` [ibm-acpi-devel] " Damjan Georgievski
2018-06-21 11:39                         ` Takashi Iwai
2018-06-23 12:46                           ` Damjan Georgievski
2018-06-21 11:40                         ` Pali Rohár
2018-06-19  8:37                 ` Pali Rohár
2018-06-19  8:42                   ` Takashi Iwai
2018-06-21 11:24                     ` Pali Rohár
2018-06-21 11:29                       ` Takashi Iwai

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=20180616155844.GA19005@amd \
    --to=pavel@ucw.cz \
    --cc=hmh@hmh.eng.br \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=ibm-acpi@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox