All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Meurer <jonas@freesources.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Re2:  nuke password to delete luks header
Date: Tue, 14 Jan 2014 23:42:44 +0100	[thread overview]
Message-ID: <52D5BD64.7040103@freesources.org> (raw)
In-Reply-To: <20140114073956.GA19051@tansi.org>

Am 14.01.2014 08:39, schrieb Arno Wagner:
> On Tue, Jan 14, 2014 at 06:01:38 CET, Jim O'Gorman wrote:
> [...] 
>> I understand that you are concerned about the risk of being sent to jail
>> but I am not sure that concern is inline with what we are encountering in
>> the real world.  If you look at the ACLU's guidance on the matter,
>> https://www.aclunc.org/blog/privacy-your-laptop-international-borders, the
>> risk of jail is not even mentioned.
> 
> I recommend you read that page again:
> 
> "This can put you in a very bad situation - disclosing the data or lying 
>  to law enforcement. Lying to US Customs or other law enforcement officer 
>  may result in criminal prosecution.  Just ask Martha Stewart, who was 
>  indicted, under Title 18, United States Code, Section 1001, for lying 
>  to federal government agents."
> 
> Now, a security professional will just stay truthful, understanding
> this. An ordinary person may lie and thereby land themselves in very 
> hot water.

While I get your arguments, I fail to understand why you oppose against
implementing the nuke password feature to cryptsetup.

From a theoretic point of view, this feature might not add much security
to your computer. But reality is more than just theory, and as Jim
clearly pointed out (and I agree with him), there's at least some
situations - at least for some people - where the nuke password feature
makes a whole lot of sense.

Also consider that there's many officials and (police) officers that
dont' know nothing about encryption techniques. Now imagine a situation
where one of these officers/officials powers on your laptop and asks you
to enter the password just before he's going to seize it. These
situations do happen (I know for sure). And they as well happen in
countries that don't send you to prison for denying to give them your
password.
While your supersafe password might be unbreakable for the forensics,
you will sleep much more soundly at night when you where able to nuke
all keyslots before, won't you?

Thanks to Jim for describing realworld szenarios where the nuke password
feature might be of help. I would love to see it implemented upstream,
and am considering to add it to the Debian package a least.

Kind regards,
 jonas

  reply	other threads:[~2014-01-14 23:09 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  2:10 [dm-crypt] nuke password to delete luks header Jim O'Gorman
2014-01-14  2:41 ` .. ink ..
2014-01-14  2:52   ` Jim O'Gorman
2014-01-14  4:04     ` .. ink ..
2014-01-14  4:36       ` Arno Wagner
2014-01-14  5:00         ` .. ink ..
2014-01-14  7:11           ` Arno Wagner
2014-01-14 12:05             ` .. ink ..
2014-01-14 14:34               ` Arno Wagner
2014-01-14 19:22                 ` .. ink ..
2014-01-15 19:36                   ` Milan Broz
2014-01-16 11:50                     ` Arno Wagner
2014-01-14  4:30     ` Arno Wagner
2014-01-14  5:01       ` Jim O'Gorman
2014-01-14  7:39         ` [dm-crypt] Re2: " Arno Wagner
2014-01-14 22:42           ` Jonas Meurer [this message]
2014-01-15  6:01             ` Arno Wagner
2014-01-15 10:00               ` Jonas Meurer
2014-01-15 10:47                 ` Arno Wagner
2014-01-15 11:39                 ` Matthias Schniedermeyer
2014-01-15 12:40                   ` Arno Wagner
2014-01-15 12:59                     ` Matthias Schniedermeyer
2014-01-15 13:38                       ` .. ink ..
2014-01-15 20:27       ` [dm-crypt] " Milan Broz
2014-01-16  9:50         ` Ondrej Kozina
2014-01-16 10:30           ` Thomas Bastiani
2014-01-16 13:09             ` Florian Junghanns
2014-01-16 19:33             ` Milan Broz
2014-01-16 20:09               ` helices
2014-01-16 20:11               ` Iggy
2014-01-16 21:36                 ` Matthias Schniedermeyer
2014-01-16 21:55                   ` Arno Wagner
2014-01-16 22:49                     ` Claudio Moretti
2014-01-17  8:17                       ` Thomas Bastiani
2014-01-17 23:18                         ` Claudio Moretti
2014-01-18  8:43                           ` Arno Wagner
2014-01-18 12:42                             ` Claudio Moretti
2014-01-18 19:18                               ` Arno Wagner
2014-01-16 20:18               ` Matthias Schniedermeyer
2014-01-16 20:28                 ` .. ink ..
2014-01-16 21:02                   ` Brian
2014-01-16 21:24                   ` Arno Wagner
2014-01-16 20:59                 ` Milan Broz
2014-01-16 21:43                   ` Arno Wagner
2014-01-17 12:43                 ` Jonas Meurer
2014-01-17 13:12                   ` Arno Wagner
2014-01-17 14:27                     ` Jonas Meurer
2014-01-17 15:16                       ` Matthias Schniedermeyer
2014-01-17 14:32                     ` Rick Moritz
2014-01-17 14:32                     ` Jonas Meurer
2014-01-17 14:57                       ` Arno Wagner
2014-01-17 14:51                     ` Heiko Rosemann
2014-01-17 15:10                       ` Arno Wagner
2014-01-16 12:01           ` Arno Wagner
2014-01-16 11:59         ` Arno Wagner
2014-01-21 22:40         ` Jonas
2014-01-23 21:26           ` Milan Broz
2014-01-23 22:11             ` .. ink ..
2014-01-23 22:30               ` Milan Broz
2014-01-23 23:43             ` Arno Wagner
2014-01-27  9:04             ` Jonas Meurer
2014-01-27 12:44               ` Arno Wagner
2014-01-27 20:30               ` Milan Broz
2014-01-28 10:28                 ` Jonas Meurer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D5BD64.7040103@freesources.org \
    --to=jonas@freesources.org \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.