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:	Sun, 1 Apr 2007 15:29:57 +0000
From:	Pavel Machek <pavel@....cz>
To:	Maxim <maximlevitsky@...il.com>
Cc:	Pete Zaitcev <zaitcev@...hat.com>,
	Alan Stern <stern@...land.harvard.edu>, gregkh@...e.de,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>,
	davidz@...hat.com
Subject: Re: USB: on suspend to ram/disk all usb devices are replugged

Hi!

> > > In that case the user would see data corruption - just as if he mounts a piece
> > > of removable media in a USB card reader; yanks out the card and modifies it
> > > elsewhere, and then puts it back in.
> > 
> > > I my opinion we can't really defend ourselves against such users... We can of
> > > course add checks in the file system drivers in the resume hooks to validate the
> > > super block and mount read-only if something change. 
> > 
> > The GNOME hath spoken?

> 	I also thought about that,
> 	
> 	I think that the best solution is still to hide connect/disconnect of usb devices from userspace (now it also causes corruption)
> 	But to refuse suspend with any usb mass storage device connected with mounted systems (and add a module param override
> 	 for users who know what they are doing)
> 
> 	What do you think ?

Agreed... and notice how easy is to do that in userspace :-))).

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ