linux-kernel - Re: Problems with remote-wakeup settings

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1003052314130.10381-100000@netrider.rowland.org>
Date:	Fri, 5 Mar 2010 23:16:20 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
cc:	Oliver Neukum <oliver@...kum.org>,
	Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>,
	<linux-input@...r.kernel.org>, <linux-hotplug@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: Problems with remote-wakeup settings

On Fri, 5 Mar 2010, Rafael J. Wysocki wrote:

> On Friday 05 March 2010, Oliver Neukum wrote:
> > Am Freitag, 5. März 2010 21:59:31 schrieben Sie:
> > > > I guess it's better if drivers don't set should_wakeup if unsure, but of course
> > > > that's impossible to enforce.
> > > 
> > > That's the real question.  Ideally, drivers won't touch should_wakeup.  
> > > How do we get there from here?
> > 
> > Enable it only for devices specifically designed for wakeup, that is
> > keyboards, power buttons and WoL, perhaps also mice and modems.
> > Are we far away from that?
> 
> I don't think we're very far from that.
> 
> Mice are known dangerous, especially the USB ones, though.

I agree, especially for desktop systems.  You don't want the system to 
wake up merely because you happened to jostle the mouse.  That happened 
to me just a few days ago (and it was a PS/2 mouse, not USB).

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/