From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <davexthc@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 Hrd6grZpZK64 for <dm-crypt@saout.de>;
 Sat, 27 Oct 2012 06:42:38 +0200 (CEST)
Received: from mail-ia0-f178.google.com (mail-ia0-f178.google.com
 [209.85.210.178])
 (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>; Sat, 27 Oct 2012 06:42:37 +0200 (CEST)
Received: by mail-ia0-f178.google.com with SMTP id y26so3326526iab.37
 for <dm-crypt@saout.de>; Fri, 26 Oct 2012 21:42:36 -0700 (PDT)
Message-ID: <508B6637.5020200@gmail.com>
Date: Sat, 27 Oct 2012 00:42:31 -0400
From: dave <davexthc@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [dm-crypt] Memory Overwrite Request in cryptsetup
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

Any plans to comply with TCG Platform Reset Attack Mitigation?