Return-Path: <htd@fancy-poultry.org>
Received: from localhost (localhost [127.0.0.1])
	by mail.saout.de (Postfix) with ESMTP id AAAE8947C
	for <dm-crypt@saout.de>; Sat,  8 Aug 2009 19:23:45 +0200 (CEST)
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 RLQBzBgXNPWv for <dm-crypt@saout.de>;
	Sat,  8 Aug 2009 19:23:41 +0200 (CEST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.171]) by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Sat,  8 Aug 2009 19:23:41 +0200 (CEST)
Date: Sat, 8 Aug 2009 19:26:44 +0200
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20090808172644.GA1045@fancy-poultry.org>
References: <20090808132614.GA29656@fancy-poultry.org>
	<20090808152335.GA9818@tansi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090808152335.GA9818@tansi.org>
Subject: Re: [dm-crypt] LUKS/dm-crypt vulnerable?
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 08.08.2009, Arno Wagner wrote: 

> No, and they cannot do that on windows either. What they do is to 
> install this and then have you open the crypto container. Then 
> they can read.

Thank you, that was what I wanted to know.