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
| ||
|
Message-ID: <20130927004832.GA15078@orion.maiolino.org> Date: Thu, 26 Sep 2013 21:48:33 -0300 From: Carlos Maiolino <cmaiolino@...hat.com> To: Eric Sandeen <sandeen@...hat.com> Cc: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org Subject: Re: [PATCH] e2image: Print a warning if running over a mounted filesystem Hey, sorry my late answer, I'm experimenting some new mutt configuration. > > If the user is trying to capture a raw or qcow image file, I agree > > that requiring that the file systme either be mounted read-only, not > > mounted at all, or that a force option be specified, makes sense. > > cool. :) > > -Eric I'd suggest then to need a force when using -r or -q on a RW image. In case of a normal image, just a warning but continue. Ted, as Eric said, I've got some useless images in the past too and just a warning won't really avoid the problem IMHO since, most of users don't even read what's being printed :-) so, request a force when getting at least a raw or QCOW2 image is very useful IMHO. any comments? > > > - Ted -- Carlos -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists