DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ken <gebser@mousecar.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] Question about backdoors and the NSL
Date: Fri, 30 May 2014 12:14:37 -0400	[thread overview]
Message-ID: <5388AE6D.20406@mousecar.com> (raw)
In-Reply-To: <20140530131326.GA21263@tansi.org>

On 05/30/2014 09:13 AM Arno Wagner wrote:
> Hi,
>
> On Fri, May 30, 2014 at 11:07:12 CEST, web1bastler@googlemail.com wrote:
>> ....
>> I knew for quite a time that American agencies such as the NSA ask
>> developers to build in backdoors into their encryption programs or even HW
>> encryption chips.
>>
>> I think it’s ridiculous that those agencies get so many rights that they
>> can even stomp on the freedom of a person in a different country which is
>> totally not democratic.
>>
>> So I want to know if my sensitive data is still safe on a LUKS encrypted
>> volume.
>
> It should be. But also note that it depends on more than cryptsetup.
> cryptsetup is just a set-up front-end from dm-crypt and the kernel
> encryption code. On the other hand, the only thing that could have
> a relvant backdoor there is the crypto-RNG, and there is reson to
> believe the kernel folks are taking that one pretty serious and
> it likely is not compromised.
> ....

Julian reported <http://tinyurl.com/2know-src> that agency in question 
has a budget of $350M to corrupt developers into introducing backdoors 
into code.  I read decades ago that this same agency had a "slush fund" 
of $20B for whatever purpose they wanted and we would imagine that over 
the years it's just gotten much larger, in effect, may well have become 
unlimited funds to carry out whatever they believe their mission is. 
How many developers could resist a large suitcase full of cash in 
exchange for their principles?  (A lot of them, I would hope.  All of 
them...? not so sure.)

For this reason there should be (1) archived records of who introduced 
what code into software (both FOSS and proprietary), (2) *many* more 
eyes reviewing code in order to find and eliminate vulnerabilities, and 
(3) much more documentation within the code to make it less obscure and 
more readable by those others' eyes.

      parent reply	other threads:[~2014-05-30 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30  9:07 [dm-crypt] Question about backdoors and the NSL web1bastler
2014-05-30 13:13 ` Arno Wagner
2014-05-30 14:55   ` Milan Broz
2014-05-30 16:14   ` ken [this message]

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=5388AE6D.20406@mousecar.com \
    --to=gebser@mousecar.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox