From: Dale Amon <amon@vnl.com>
To: Milan Broz <mbroz@redhat.com>
Cc: Dale Amon <amon@vnl.com>, Ryan Corder <ryanc@greengrey.org>,
"C.J. Adams-Collier KF7BMP" <cjac@colliertech.org>,
linux-crypto@vger.kernel.org, "roosa,
william MAJ RES" <william-roosa@us.army.mil>
Subject: Re: Status of aes in Debian/Ubuntu?
Date: Wed, 28 Mar 2012 22:33:05 +0100 [thread overview]
Message-ID: <20120328213305.GG10584@vnl.com> (raw)
In-Reply-To: <4F737F41.1090309@redhat.com>
On Wed, Mar 28, 2012 at 11:14:41PM +0200, Milan Broz wrote:
> If you want something simple, use LUKS. cryptsetup
> and dmcrypt is in all distributions by default.
> Truecrypt uses dmcrypt by default as backend as well.
Looking around a bit, it appears that cryptsetup is in
the ubuntu server set up disk.
> Of course, if you want use loop-aes, you have to
> patch all utilities and kernel, it is not so complicated.
I'm not wedded to it... as I noted I have been out of
the loop, crypt or otherwise, for half a decade.
> (cryptsetup can run loop-aes compatible mode as well and
> can allocate loop device as well. But it is your
> choice what encryption and utility to use to use
> of course.)
>
> For default losetup from util-linux, encryption option
> is in fact deprecated in favor to cryptsetup.
Okay. Now do cryptsetup and the others work in a pretty
standard way? ie, put them in your /etc/fstab and
just feed them a password when you want to mount? Or if
it is a loopback image, you just do the usual
mount -o loop file /mnt
?
next prev parent reply other threads:[~2012-03-28 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 12:17 Status of aes in Debian/Ubuntu? Dale Amon
2012-03-28 16:37 ` C.J. Adams-Collier KF7BMP
2012-03-28 18:06 ` Status of aes in Debian/Ubuntu? (UNCLASSIFIED) roosa, william MAJ RES
2012-03-28 19:03 ` Status of aes in Debian/Ubuntu? Ryan Corder
2012-03-28 20:42 ` Dale Amon
2012-03-28 21:14 ` Milan Broz
2012-03-28 21:33 ` Dale Amon [this message]
2012-03-29 11:00 ` Status of aes in Debian/Ubuntu? (UNCLASSIFIED) roosa, william MAJ RES
2012-03-29 22:53 ` Dale Amon
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=20120328213305.GG10584@vnl.com \
--to=amon@vnl.com \
--cc=cjac@colliertech.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=ryanc@greengrey.org \
--cc=william-roosa@us.army.mil \
/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