From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Question about backdoors and the NSL
Date: Fri, 30 May 2014 16:55:52 +0200 [thread overview]
Message-ID: <53889BF8.7060506@gmail.com> (raw)
In-Reply-To: <20140530131326.GA21263@tansi.org>
On 05/30/2014 03:13 PM, Arno Wagner wrote:
> On Fri, May 30, 2014 at 11:07:12 CEST, web1bastler@googlemail.com wrote:
>> Hello dear cryptsetup team,
>>
>> I want to ask if you received a national security letter because I want to
>> know if my LUKS encrypted volumes are still safe.
>
> First, you should know that your question is not very bright.
> Recipients of valid NSLs are not allowed to talk about them or
> admit they have gotten one. Hence what do you expect as answer if
> there were an NSL?
>
> But second, Milan and I are not located in the US, so I doubt
> that they could legally give either of us an NSL and even if
> they did, I doubt it would have any effect. But please notice
> that I am not answering your question, to be sure you have to
> verify what I just said yourself.
Exactly.
Cryptsetup is opensource under clear license, every meaningful
and independent audit is welcome of course.
...
>> 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.
Also I am releasing and signing source code only, so you have to trust
distro maintainers as well which are compiling the code.
Milan
next prev parent reply other threads:[~2014-05-30 15:25 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 [this message]
2014-05-30 16:14 ` ken
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=53889BF8.7060506@gmail.com \
--to=gmazyland@gmail.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