From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <benoit.canet@irqsave.net>
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 hNuhp699ZevL for <dm-crypt@saout.de>;
 Mon, 29 Jul 2013 18:00:24 +0200 (CEST)
Received: from paradis.irqsave.net (nodalink.pck.nerim.net [62.212.105.220])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Mon, 29 Jul 2013 18:00:24 +0200 (CEST)
Date: Mon, 29 Jul 2013 18:02:12 +0200
From: =?iso-8859-1?Q?Beno=EEt?= Canet <benoit.canet@irqsave.net>
Message-ID: <20130729160212.GA4550@irqsave.net>
References: <20130724150910.GC5115@irqsave.net>
 <51F56388.9060007@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <51F56388.9060007@gmail.com>
Subject: Re: [dm-crypt] cryptsetup alternate storage backend
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: Milan Broz <gmazyland@gmail.com>
Cc: =?iso-8859-1?Q?Beno=EEt?= Canet <benoit.canet@irqsave.net>, dm-crypt@saout.de


Hello,

We have some work to tackle before being able to implement dm-crypt in QEMU.
But it would like the following.

> Do you have some better specification what do you need from libcryptsetup?
I was thinking of a way to give libcryptsetup a structure containing some f=
iles
operation which would be implemented by QEMU.

something like
struct crypt_fops {
    .read
    .write
    .open
    .close
    .wipe
    .sync
}

The call would look like
cryptsetup_register_fops(struct crypt_fops *f);

This way other potentials users of libcryptsetup could implement their own =
fops
and link against it.

> And do you need this code to be portable to other OS environment as well,=
 correct?
Yes QEMU is cross platform.

Best regards

Beno=EEt