From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tazok.id0@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id WjUEt_9N1smq for <dm-crypt@saout.de>;
 Wed, 19 Sep 2012 06:51:57 +0200 (CEST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Wed, 19 Sep 2012 06:51:57 +0200 (CEST)
Received: by wgbdr13 with SMTP id dr13so506082wgb.1
 for <dm-crypt@saout.de>; Tue, 18 Sep 2012 21:51:57 -0700 (PDT)
Message-ID: <50594F83.4040908@gmail.com>
Date: Wed, 19 Sep 2012 06:52:19 +0200
From: =?ISO-8859-1?Q?Javier_Juan_Mart=EDnez_Cabez=F3n?= <tazok.id0@gmail.com>
MIME-Version: 1.0
References: <20120823090049.GB14639@Latty> <20120823112728.GA20834@tansi.org>
 <20120823151025.GM14639@Latty> <20120823160728.GA26979@tansi.org>
 <5036729B.1060905@gmail.com> <20120823193415.GA31534@tansi.org>
 <50378927.7090508@gmail.com> <20120824144028.GB2407@fancy-poultry.org>
 <20120824151439.GA30694@tansi.org>
 <CAK5fS_Hf=DigoTopgUZ9FJA3QVXCre-Nn1Z0LEFL+kwRL+LtGg@mail.gmail.com>
 <20120905130125.GB11942@tansi.org>
 <CAKRxpusY-BTQD_XVnVjnmhQt6_HX9zROddXM7sfFrQPqdhtBDQ@mail.gmail.com>
In-Reply-To: <CAKRxpusY-BTQD_XVnVjnmhQt6_HX9zROddXM7sfFrQPqdhtBDQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Encrypt all partitions with dm-crypt
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 19/09/12 06:15, Two Spirit wrote:
> I'm interested in knowing what are some of the trade offs of using the LUKS
> header v not using the LUKS header.Since I assume the content of the
> encrypted data is secure, it doesn't matter if someone knows the data is
> encrypted and has a header and the header only helps in recovery, so I'm
> not quite seeing what would be an advantage of not using LUKS, but from the
> email below, there seems to be some reason.
> 
> On Wed, Sep 5, 2012 at 6:01 AM, Arno Wagner <arno@wagner.name> wrote:
> 
>> Hi,
>>
>> On Wed, Sep 05, 2012 at 08:21:36AM +0400, Stayvoid wrote:
>>> Hello there,
>>>
>>> Let's move back to the initial questions...
>>>
>>> I'd like to use a plain version of dm-crypt because it doesn't
>>> store a header on a disk. (Yes, I know that LUKS is a recommended
>>> way, but I've already made my choice.)
>>
>> That is fine. I am doing the same in some places.
>>
>>
> 
> 
> 
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

Please check tha FAQ's