On Wed, Oct 10, 2007 at 03:50:05PM +0200, Ludwig Nussel wrote:
> > Frankly, I'm still not sure. Maybe we (upstream) can completely
> > ignore everything around cryptoloop --just because it's deprecated--.
> > It means don't add a new option -k or loop-aes encryption style
> > strings.
>
> Personally I just like to see it because users want to continue to
> conveniently be able to mount their legacy files. There is no other
Yes, but it's more downstream problem. It's supported by Suse and
Debian, Fedora & RHEL completely ignore cryptoloop, some others
distributions directly use loop-aes. ..etc. It means it's currently
distribution specific and for **upstream** will be probably the best
solution keep status-quo and wait for real cryptoloop death.
> way to let regular users mount an encrypted file. LUKS with help of
> hal works fine for e.g. usb memory sticks but for loop mounted files
> or legacy partitions there is no good solution. I think the idea of
> some dm-crypt plugin for mount was already brought up on the list.
> Although that would probably just shift the above discussion to
> another backend technology :-)
:-)
Now it seems that more important step will be merge of blkid and
volume_id (at least in next few months).
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
-
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
