From: Milan Broz <mbroz@redhat.com>
To: util-linux-ng <util-linux-ng@vger.kernel.org>
Subject: Re: remove encryption options from mount and losetup?
Date: Thu, 14 Jun 2012 21:43:11 +0200 [thread overview]
Message-ID: <4FDA3ECF.9060607@redhat.com> (raw)
In-Reply-To: <4FD9CF44.8090800@suse.de>
On 06/14/2012 01:47 PM, Ludwig Nussel wrote:
> Karel Zak wrote:
> Well, someone could come up with another tool to support cryptoloop, or
> rather 'transfer functions'.
cryptsetup can map all compatible mappings with cryptoloop using dmcrypt
(and it can automatically alloc loop device as well) so providing something
compatible is just question of simple wrapper.
IMHO cryptoloop should be removed from kernel... The only usable (and secure)
solution using this interface is out-of-mainline-tree loop-aes extension.
Milan
next prev parent reply other threads:[~2012-06-14 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 14:53 remove encryption options from mount and losetup? Ludwig Nussel
2012-06-13 15:01 ` Karel Zak
2012-06-14 11:47 ` Ludwig Nussel
2012-06-14 19:43 ` Milan Broz [this message]
2012-06-15 7:03 ` Ludwig Nussel
2012-06-15 8:47 ` Karel Zak
2012-06-15 9:13 ` Ludwig Nussel
2012-06-15 9:40 ` Karel Zak
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=4FDA3ECF.9060607@redhat.com \
--to=mbroz@redhat.com \
--cc=util-linux-ng@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).