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 FzExC878x-hj for ; Fri, 28 Dec 2012 20:15:45 +0100 (CET) Received: from mail-ee0-f47.google.com (mail-ee0-f47.google.com [74.125.83.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Fri, 28 Dec 2012 20:15:45 +0100 (CET) Received: by mail-ee0-f47.google.com with SMTP id e51so5259855eek.34 for ; Fri, 28 Dec 2012 11:15:44 -0800 (PST) Message-ID: <50DDEFDD.4010102@gmail.com> Date: Fri, 28 Dec 2012 20:15:41 +0100 From: Milan Broz MIME-Version: 1.0 References: <56447.5.39.88.44.1356708146.squirrel@lavabit.com> In-Reply-To: <56447.5.39.88.44.1356708146.squirrel@lavabit.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Unexpected behavior in cryptsetup-1.5.1 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: jason_daly@lavabit.com Cc: dm-crypt On 12/28/2012 04:22 PM, jason_daly@lavabit.com wrote: > I see that in the release notes for cryptsetup-1.5.1, it talks about "lazy > initializations." Could this be the cause of this new behavior, and if > so, is this an expected trade-off in order to allow for some cryptsetup > operations to be run by non-root users? Yes, it is caused by this change and it is a bug (and should be fixed in devel tree already), so next release will work again here. Your workaround (allocate loop in advance) should work always. (You still need to be root for LUKS format...) Thanks for report! (You can directly use http://code.google.com/p/cryptsetup/issues/list next time if you want track specific problem and the fix.) Milan