Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=3.0 tests=BAYES_00,DKIM_ADSP_ALL, DKIM_INVALID,DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1821CC433E0 for ; Wed, 6 Jan 2021 11:09:46 +0000 (UTC) Received: from mail.server123.net (mail.server123.net [78.46.64.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 701ED22CA2 for ; Wed, 6 Jan 2021 11:09:45 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 701ED22CA2 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=kngnt.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dm-crypt-bounces@saout.de X-Virus-Scanned: amavisd-new at saout.de Authentication-Results: mail.server123.net (amavisd-new); dkim=pass (2048-bit key) header.d=kngnt.org Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=212.54.42.167; helo=smtpq4.tb.mail.iss.as9143.net; envelope-from=felix@kngnt.org; receiver= Received: from smtpq4.tb.mail.iss.as9143.net (smtpq4.tb.mail.iss.as9143.net [212.54.42.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Wed, 6 Jan 2021 12:08:50 +0100 (CET) Received: from [212.54.42.110] (helo=smtp7.tb.mail.iss.as9143.net) by smtpq4.tb.mail.iss.as9143.net with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kx6gL-00044S-Nx for dm-crypt@saout.de; Wed, 06 Jan 2021 12:08:49 +0100 Received: from 80-115-99-116.cable.dynamic.v4.ziggo.nl ([80.115.99.116] helo=mail.kngnt.org) by smtp7.tb.mail.iss.as9143.net with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1kx6gL-00CEtk-5x for dm-crypt@saout.de; Wed, 06 Jan 2021 12:08:49 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kngnt.org; s=mail; t=1609931327; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zxjyjqW13W81tU8dkAo/bwuJksJEEQgQkgiITuyQVjA=; b=R+RBafJN6KQsOyARiBL7IhsKtt1+/RFbGPCfydXLWWBEjKvW0QnOEhctVL9VhcrLTJqwTv hP+SFhO+TLWEgLjd+9WGMNqJjDuM9UFXAhN01dvst/Sf7qoyKqTtD1y0YIbrpKvnT8ECIS HXugTmdEXzMx8MjTkrIdRpyTd0+GsD70MrIEuwOq9XorW7QpOW2qZlF7a2cxQPVI8kiCfA VcuLrDxZqfBQ08JkOe16AnjFxRif70a2JK2FnWXwKvvAj9i6uA/zUBfWZaaVjvFPcsNF5t Z/7BuZl43NPGlxg6saJhgKLsm9IxviwPrr7dXnNwz9sbMTnQmfGJ1iY9ry4trw== MIME-Version: 1.0 Date: Wed, 06 Jan 2021 12:08:47 +0100 From: Felix Rubio To: dm-crypt@saout.de In-Reply-To: <20210106104746.GA3386@tansi.org> References: <20210106104746.GA3386@tansi.org> Message-ID: <3674619b2202e99b31fac7043e6edba5@kngnt.org> X-Sender: felix@kngnt.org X-SourceIP: 80.115.99.116 X-Authenticated-Sender: f.rubiodalmau@ziggo.nl (via SMTP) X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.4 cv=Ff+JeLy6 c=1 sm=1 tr=0 ts=5ff59a41 a=L5q10J0BAxueQzk5LW0IQA==:17 a=9+rZDBEiDlHhcck0kWbJtElFXBc=:19 a=IkcTkHD0fZMA:10 a=EmqxpYm9HcoA:10 a=WxEJytdoAAAA:8 a=NTQivLu059PGoLTBPBUA:9 a=QEXdDO2ut3YA:10 a=Pjb4ukjMmGjbsrBi06EW:22 X-Ziggo-Spam-Status: No Subject: Re: [dm-crypt] length of keyfiles X-BeenThere: dm-crypt@saout.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: dm-crypt-bounces@saout.de Sender: "dm-crypt" Thank you for your answer Arno... and for confirming that I should finally get rid of those double density floppy disks and reader :-P Regards! Felix --- Felix Rubio "Don't believe what you're told. Double check." On 2021-01-06 11:47, Arno Wagner wrote: > Hi Felix, > > I assume we are talking LUKS here, plain mode is different. > > The longer length is both convenience and helps if you > use low-entropy input. The keyfile does not actually > hold a key (LUKS mode), but a passphrase. Passphrases > get hashed, and once you have maximum entropy, you > cannot get more. I would need to look up what length > is actually used, but it does not depend on the lenght > of the encryption key. That one is stored in the anti-forensic > stripes, protected with the hash from that passphrase. > > So, to make this short, if you use LUKS with a keyfile, > putting in more entropy than used is meaningless. > If your random data is from /dev/random or (properly > initialized) /dev/urandom, 64 bytes are more than enough. > > Also, the differences between an 8kB passphrase and a > 64B one in execution time should not be noticeable at all. > Unless you read it from floppy disk ;-) > > Regards, > Arno > > > On Wed, Jan 06, 2021 at 10:17:22 CET, Felix Rubio wrote: >> Hi everybody, >> >> I have seen that keyfiles can be used in cryptsetup up to 8 kB, but >> internally the master key is 512 bits at max. Is there any >> recommendation >> / increased security by using a random sequence of 8 kB w.r.t., let's >> say, >> one of just 64 bytes? >> >> I understand that using one of 8kB will require more time than one of >> 64 B >> when unlocking the volume, but... is the former really that much more >> secure than the latter? >> >> Regards! >> Felix >> _______________________________________________ >> dm-crypt mailing list >> dm-crypt@saout.de >> https://www.saout.de/mailman/listinfo/dm-crypt _______________________________________________ dm-crypt mailing list dm-crypt@saout.de https://www.saout.de/mailman/listinfo/dm-crypt