All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: Stanislav Brabec <sbrabec@suse.cz>, util-linux@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs-safe implementation of -oloop
Date: Wed, 13 Apr 2016 13:41:32 +0200	[thread overview]
Message-ID: <20160413114132.4udmiqkxqqp5txkp@ws.net.home> (raw)
In-Reply-To: <201604131329.35899.sweet_f_a@gmx.de>

On Wed, Apr 13, 2016 at 01:29:35PM +0200, Ruediger Meier wrote:
> > There is nothing like loop devices encryption :-)
> 
> openSUSE had cryptoloop before 12.2. But it's not supported anymore.
> There was also losetup -e:
>        -e, -E, --encryption encryption_type
>               enable data encryption with specified name or number

   /me is sarcastic sometimes :-)  
 

It wasn't easy to force Suse to sent:

  commit 5cf05c71472bf7230075cbdcd5cd6eb12b1d3654
  Author: Ludwig Nussel <ludwig.nussel@suse.de>
  Date:   Tue Sep 11 10:46:11 2012 +0200

    mount: losetup: remove obsolete encryption support


... but I guess we all are happy with it after years.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2016-04-13 11:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 18:21 [PATCH 0/3] btrfs-safe implementation of -oloop Stanislav Brabec
2016-04-13 11:08 ` Karel Zak
2016-04-13 11:29   ` Ruediger Meier
2016-04-13 11:41     ` Karel Zak [this message]
2016-04-13 12:52   ` Stanislav Brabec
2016-04-22 11:22 ` Karel Zak
2016-04-22 12:42   ` Stanislav Brabec

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=20160413114132.4udmiqkxqqp5txkp@ws.net.home \
    --to=kzak@redhat.com \
    --cc=sbrabec@suse.cz \
    --cc=sweet_f_a@gmx.de \
    --cc=util-linux@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 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.