[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#416824: klaptopdaemon: lock & hibernate allowing unauthorised access



  Hello:

El Lunes, 2 de Abril de 2007 20:42, Marc Haber escribió:
> On Mon, Apr 02, 2007 at 04:48:04PM +0100, Ana Guerrero wrote:
> > anyone has experiment something like this:
> >
> > On Fri, Mar 30, 2007 at 03:39:02PM +0100, Sheridan Hutchinson wrote:
> > > Depending on the load on the system, klaptopdaemon appears to be
> > > allowing somone unhibernating a locked & hibernated system, brief
> > > access to the desktop.

  I think the first step step is knowing what procedure is used in order to 
hibernate. Is this guy using the hibernate scripts? is he using suspend or 
suspend2 method ? 

  Maybe part of this information is not relevant, but there are some guessing 
that could be done. I guess this happens using the hibernate scripts, and 
doesn't seem to me that the hibernate method is not relevant.

 For example, I remember hibernate scripts suffered from 
what I consider a kde "bug" which made a dcop call for locking the screen 
block the hibernate script, so even the hibernation could complete, the 
desktop couldn't be locked.

  What I'm trying to say is that maybe this is not a klaptodaemon problem, but 
instead the hibernate scripts. Following the previous rationale, the dcop 
call to KScreensaverIface lock should block and that seems to me. Problem is 
that I'm on 3.5.6 right now so i can't test. 

  I tested this using a text console and calling the involved dcop call like 
this:

  DISPLAY=:0 dcop kdesktop kScreensaverIface lock

  The first time it took 1.5secs approximately but on the second consecutive 
call, it just took 0.5secs to return to command line. Unlocking the kde 
session and then trying again I got same cualitative results.

>
> Yes, I notice this once in a while as well. Looks like the "Lock &
> Hibernate" function kicks off the screen saver, but sends the system
> into hibernation before the screen saver has fully started up.
>

  True, so if we want kdelaptop solves the problem we should use a solution as 
the one proposed by Sune, or alternatively we would need to get a verbose 
hibernate log and analyse it, increasing the LogVerbosity value up to 9 in 
the hibernate common.conf located at /etc/hibernate.


> Greetings
> Marc
>


-- 
     Raúl Sánchez Siles
----->Proud Debian user<-----
Linux registered user #416098

Attachment: pgp_4F_8CC8Cn.pgp
Description: PGP signature


Reply to: