From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@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 n_W4iMh2tMLV for <dm-crypt@saout.de>;
 Tue,  3 Jul 2012 22:17:19 +0200 (CEST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44])
 (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>; Tue,  3 Jul 2012 22:17:19 +0200 (CEST)
Received: by wgbdr13 with SMTP id dr13so6654718wgb.1
 for <dm-crypt@saout.de>; Tue, 03 Jul 2012 13:17:19 -0700 (PDT)
Message-ID: <4FF3534C.1000109@gmail.com>
Date: Tue, 03 Jul 2012 22:17:16 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <67C1678059C61F408194E53907AFB5CC0ABC3B3061@IS-EXMB01-RP.ad.reyrey.com>
 <57f586e1-bd02-4bed-82e1-0db64a280282@IS-EXHC02-RP.ad.reyrey.com>
In-Reply-To: <57f586e1-bd02-4bed-82e1-0db64a280282@IS-EXHC02-RP.ad.reyrey.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [dm-crypt] cryptsetup build question
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: "Simpson, John R" <john_simpson@reyrey.com>
Cc: "dm-crypt@saout.de" <dm-crypt@saout.de>

On 07/02/2012 07:08 PM, Simpson, John R wrote:
> I believe I=92ve answered my own question.

Well, you should never link to these internal things.

But, in RHEL5 there is old cryptsetup 1.0.3 and shared
library is quite problematic to use.
Anyway, please be sure you are using cryptsetup from RHEL 5.8,
(cryptsetup-luks-1.0.3-8) there were important fixes.

For RHEL6 and upwards, you should be able to use
libcryptsetup as normal shared library.

You can find some examples here
http://wiki.cryptsetup.googlecode.com/git/API/index.html

> I=92ve been tasked with adding support for a local passphrase system to
> cryptsetup.

Hm. What it means?
(And isn't simple binary wrapper/script simpler?)

Milan