[Bug 273937] Security: graphics: private content on screen, during an otherwise effective screen lock (was: x11-wm/plasma5-kwin with x11/nvidia-driver-470: occasional title bar failures kwin_x11 --replace)
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Sep 20 01:27:19 BST 2023
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273937
Graham Perrin <grahamperrin at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also|https://bugs.freebsd.org/bu |
|gzilla/show_bug.cgi?id=2738 |
|12 |
Priority|--- |Normal
Version|Latest |unspecified
Summary|x11-wm/plasma5-kwin with |Security: graphics: private
|x11/nvidia-driver-470: |content on screen, during
|occasional title bar |an otherwise effective
|failures on at least one |screen lock (was:
|external display, worked |x11-wm/plasma5-kwin with
|around with kwin_x11 |x11/nvidia-driver-470:
|--replace |occasional title bar
| |failures kwin_x11
| |--replace)
Component|Individual Port(s) |Base
Assignee|danfe at FreeBSD.org |secteam at FreeBSD.org
Flags|maintainer-feedback?(danfe@ |
|FreeBSD.org) |
Group| |freebsd_committer
Keywords| |security
Product|Ports & Packages |Security
--- Comment #3 from Graham Perrin <grahamperrin at gmail.com> ---
To any privileged user of Bugzilla who reads this bug report:
* please do not discuss in public.
In particular:
* please do not treat open non-encrypted IRC in a publicised channel as a
suitable venue to encourage discussion of what should be private.
danfe@ I am making this report private. Keyword:
* security
secteam@ I am genuinely sorry for the public beginning of this report. I could,
or should, have predicted what follows.
Symptoms recurred after waking the computer from sleep (resume from suspend).
Texts were visible, photographed, whilst a screen lock was active.
To help distinguish this report from other reports:
* I could not use the desktop environment until after I entered my
passphrase to end the active lock.
I can not be certain that this is a ports bug … consider the possibility of a
bug in base causing, or partly causing, security issues that affect (or
involve) multiple graphics drivers; drivers that are quite different from each
other.
----
% date ; uptime ; grep -e BOOT -e suspend /var/log/messages
Wed 20 Sep 2023 00:33:59 BST
12:33a.m. up 5:50, 5 users, load averages: 0.61, 0.74, 0.66
Sep 19 06:54:36 mowa219-gjp4-8570p-freebsd acpi[16951]: suspend at 20230919
06:54:36
Sep 19 12:43:11 mowa219-gjp4-8570p-freebsd kernel: ---<<BOOT>>---
Sep 19 13:28:10 mowa219-gjp4-8570p-freebsd kernel: ---<<BOOT>>---
Sep 19 16:34:20 mowa219-gjp4-8570p-freebsd acpi[2826]: suspend at 20230919
16:34:20
Sep 19 19:56:58 mowa219-gjp4-8570p-freebsd acpi[11760]: suspend at 20230919
19:56:58
%
----
Information set aside, for reference, includes copies of:
/var/log/console.log
/var/log/dmesg.today
/var/log/dmesg.yesterday
/var/log/messages
----
There's more, but first I should restart the computer, because now (whilst
writing) I see that flickering can recur after 'kwin_x11 --replace' and before
putting the computer to sleep.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kde-freebsd
mailing list