From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <fhdata@unm.edu>
Received: from unm.edu (nusakan.unm.edu [129.24.170.106])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Fri,  8 Jul 2011 00:45:55 +0200 (CEST)
Received: from [129.24.208.83] (HELO dado.unm.edu)
 by nusakan.unm.edu (CommuniGate Pro SMTP 5.2.20)
 with ESMTP id 88984027 for dm-crypt@saout.de; Thu, 07 Jul 2011 16:15:52 -0600
Message-ID: <4E16300E.6050606@unm.edu>
Date: Thu, 07 Jul 2011 16:15:42 -0600
From: fhdata <fhdata@unm.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [dm-crypt] version compatibility
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


Greetings,

I have a simple question.

Is cryptsetup  1.2.x backward compatible with cryptsetup 1.0.3.x ?

e.g. devices can be encrypted/decrypted back and forth between the two 
versions?

Thanks,
F-