[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Re: Security Audit Request for Screenlocker Branch
From:       Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= <mgraesslin () kde ! org>
Date:       2011-10-11 19:13:36
Message-ID: 1890802.rDCHFPkn8A () martin-desktop
[Download RAW message or body]


On Tuesday 11 October 2011 21:06:13 Alexander Neundorf wrote:
> On Tuesday 11 October 2011, Martin Gräßlin wrote:
> > On Tuesday 11 October 2011 16:06:11 Andras Mantia wrote:
> > > From here:
> > > "If KWin crashes without restarting privacy is leaked but the system is
> > > hardly useable due to missing window manager. This situation can savely
> > > be ignored as a corner case as KWin normaly restart."
> > > 
> > > This is not true, the system can be used without a window manager and if
> > > you happen to have a running terminal or start one, it is possible to
> > > start a new window manager (which might not be kwin) and access
> > > everything.
> > 
> > yes if you have a terminal open and if it is the top most of stacking
> > order
> > it is possible to start another window manager. If that is not the case
> > you are not able to start anything as KRunner or kickoff cannot be opened.
> 
> You can also switch to a text-mode console (Ctrl+F1 etc), set DISPLAY, and
> start the window manager there.
Yes but you have to login to be able to do that and goint to a tty killing 
kwin, removing the lock file and starting kwin again is certainly a valid way 
to end the screen locker. That's the same as currently going to the tty and 
killing kscreenlocker.

Cheers
Martin
> 
> Alex

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]