From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ONfb4hp4nmds for ; Mon, 3 Oct 2011 17:34:34 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Mon, 3 Oct 2011 17:34:33 +0200 (CEST) Message-ID: <4E89D604.90609@redhat.com> Date: Mon, 03 Oct 2011 17:34:28 +0200 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] clarification on the use of API with key slot argument on plain volumes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ".. ink .." Cc: dm-crypt@saout.de On 10/02/2011 11:26 PM, .. ink .. wrote: > > I am trying to move from using cryptsetup from the command line to > using the library and i dont seem to understand the API very well. There will be soon documentation with some examples soon (days, we have already some patches). > Most API like "crypt_activate_by_passphrase" has a keyslot argument > in them, plain volumes do not use key slots. How can this API and > others that has a keyslot argument be used on plain volumes? use CRYPT_ANY_SLOT (it is ignored anyway). See cryptsetup.c implementation as example for now. (I'll reply with some example later but I'll be not online for few days now...) Milan