Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S966735AbbBCRss (ORCPT <rfc822;w@1wt.eu>);
	Tue, 3 Feb 2015 12:48:48 -0500
Received: from imap.thunk.org ([74.207.234.97]:51366 "EHLO imap.thunk.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1756072AbbBCRso (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 3 Feb 2015 12:48:44 -0500
Date: Tue, 3 Feb 2015 12:48:39 -0500
From: "Theodore Ts'o" <tytso@mit.edu>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Al Viro <viro@ZenIV.linux.org.uk>, linux-fsdevel@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] WIP: Add syscall unlinkat_s (currently x86* only)
Message-ID: <20150203174839.GD2509@thunk.org>
Mail-Followup-To: Theodore Ts'o <tytso@mit.edu>,
	Alexander Holler <holler@ahsoftware.de>,
	Al Viro <viro@ZenIV.linux.org.uk>, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
References: <1422896713-25367-1-git-send-email-holler@ahsoftware.de>
 <1422896713-25367-2-git-send-email-holler@ahsoftware.de>
 <20150203060542.GZ29656@ZenIV.linux.org.uk>
 <54D071AA.1030302@ahsoftware.de>
 <20150203075616.GA29656@ZenIV.linux.org.uk>
 <54D08BF4.3000903@ahsoftware.de>
 <54D093A0.7090201@ahsoftware.de>
 <54D0C3B8.2050507@ahsoftware.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54D0C3B8.2050507@ahsoftware.de>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1410
Lines: 30

On Tue, Feb 03, 2015 at 01:48:56PM +0100, Alexander Holler wrote:
> 
> E.g. my parents are stull successfully using contact lists on paper. These
> are still more readable, easier to handle and smaller than any available
> electronic replacement. And they have absolutely no problem to destroy an
> old one when they replace it with a new one.

Sort of using crypto, which I think is still the best response to this
particular use case --- the trick is making it easy to use, but that's
a desktop/distro integration problem --- the most secure way to really
make sure information on paper and on an SSD is secure is actually the
same --- you use a shredder.

And this isn't just for "military grade security".  There are some
commercial cloud providers which do precisely this, because they know
that their customer's security and their reputation is not easily
valued, and certainly the cost of some piddling flash chips, after
they have been depreciated, is defintiely cheaper than a security
exposure.  Look at the estimates of how much money Target lost with
their little security oopsie.  Again, this is commercial, not military
security.

Cheers,

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