lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 25 Apr 2023 22:16:32 +0000
From:   "Limonciello, Mario" <Mario.Limonciello@....com>
To:     Jonathan Singer <jes965@....edu>,
        "platform-driver-x86@...r.kernel.org" 
        <platform-driver-x86@...r.kernel.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Function of the camera key on windows

[Public]

> The key itself triggers a hardware response both on windows and linux.
> It disconnects power from the camera USB module and raises a cover in front
> of the camera aperature. The keycode is as far as I know only to notify the
> operating system in case it wanted to show a message.
> 
> Is that the kind of use case that would benefit from emitting a KEY_CAMERA?

In my opinion it is something that for example GNOME could pick up and display
an image with a camera with a line through it.  If it comes again it could toggle.

This is pretty similar to how mic mute works for example.  The way you describe it
I think of it as "Camera mute".

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ