From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.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 hOPvXEH9ORSx for <dm-crypt@saout.de>;
 Thu, 20 Oct 2011 10:43:58 +0200 (CEST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Thu, 20 Oct 2011 10:43:57 +0200 (CEST)
Received: from int-mx12.intmail.prod.int.phx2.redhat.com
 (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25])
 by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9K8huTw020422
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
 for <dm-crypt@saout.de>; Thu, 20 Oct 2011 04:43:56 -0400
Received: from [10.36.6.156] (vpn1-6-156.ams2.redhat.com [10.36.6.156])
 by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id
 p9K8hsnl010130
 for <dm-crypt@saout.de>; Thu, 20 Oct 2011 04:43:55 -0400
Message-ID: <4E9FDF4A.9080402@redhat.com>
Date: Thu, 20 Oct 2011 10:43:54 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <447BD5696AE910409E86411D8A0DEE73036632@NDHEP50002.na.corp.mckesson.com>
 <20111020081835.GA26340@tansi.org>
In-Reply-To: <20111020081835.GA26340@tansi.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Question regarding LUKS
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 10/20/2011 10:18 AM, Arno Wagner wrote:
> I don't think anybody ever invested the money needed
> to find out. 

Well, maybe you noticed some changes in dmcrypt and even
cryptsetup which were directly closely related
to this problem.

AFAIK FIPS 140-2 is always related to some hw config,
but in principle (and if you define cryptographic boundaries
properly) dm-crypt and LUKS have no serious issues here.

The main problem is proper RNG and crypto use (you have
to use only approved RNG and only certified crypto library),
and it cannot be isolated from the kernel certification etc.

So there are no principal problems I know about but
still some changes are needed (some of them are really
formal).

Milan