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  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:	Fri, 11 Mar 2016 16:44:16 -0800
From:	Linus Torvalds <>
To:	"Theodore Ts'o" <>,
	Dave Chinner <>,
	Linus Torvalds <>,
	Andy Lutomirski <>,
	One Thousand Gnomes <>,
	Ric Wheeler <>,
	Gregory Farnum <>,
	"Martin K. Petersen" <>,
	Christoph Hellwig <>,
	"Darrick J. Wong" <>,
	Jens Axboe <>,
	Andrew Morton <>,
	Linux API <>,
	Linux Kernel Mailing List <>,, Bruce Fields <>,
	linux-fsdevel <>,
	Jeff Layton <>,
	Eric Sandeen <>
Subject: Re: [PATCH 2/2] block: create ioctl to discard-or-zeroout a range of blocks

On Fri, Mar 11, 2016 at 4:35 PM, Theodore Ts'o <> wrote:
> At the end of the day it's about whether you trust the userspace
> program or not.

There's a big difference between "give the user rope", and "tie the
rope in a noose and put a banana peel so that the user might stumble
into the rope and hang himself", though.

So I do think that Dave is right that we should also strive to make
sure that our interfaces are not just secure in theory, but that they
are also good interfaces to make mistakes less likely.

I think we _should_ give users rope, but maybe we should also make
sure that there isn't some hidden rapidly spinning saw-blade right
next to the rope that the user doesn't even think about.


Powered by blists - more mailing lists