From: Milan Broz <gmazyland@gmail.com>
To: jason_daly@lavabit.com
Cc: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] Unexpected behavior in cryptsetup-1.5.1
Date: Fri, 28 Dec 2012 20:15:41 +0100 [thread overview]
Message-ID: <50DDEFDD.4010102@gmail.com> (raw)
In-Reply-To: <56447.5.39.88.44.1356708146.squirrel@lavabit.com>
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
next prev parent reply other threads:[~2012-12-28 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 15:22 [dm-crypt] Unexpected behavior in cryptsetup-1.5.1 jason_daly
2012-12-28 19:15 ` Milan Broz [this message]
2012-12-29 14:37 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50DDEFDD.4010102@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=jason_daly@lavabit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.