From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Required kernel crypto interface not available
Date: Fri, 16 May 2014 12:54:34 +0200 [thread overview]
Message-ID: <20140516105434.GA31000@tansi.org> (raw)
In-Reply-To: <CAPzH-qC=wGOez3jHgKCFs+DFF_zHu8xv-7z3HFB5=nKd=XP0vQ@mail.gmail.com>
On Fri, May 16, 2014 at 03:58:31 CEST, Franz wrote:
> On Thu, May 15, 2014 at 8:43 PM, .. ink .. <mhogomchungu@gmail.com> wrote:
> > Summary of below steps:
> > 1. create a 10MB image file
> > 2. create a LUKS volume on the image file
> > 3. open the LUKS volume.
> > 4. put a file system on the volume.
> > 5. close the the volume.
> > 6. ?????
> > 7. profit!!!!! :-)
> >
> > dd if=/dev/urandom of=luks.img bs=1024 count=10000
> > cryptsetup luksFormat luks.img
> > cryptsetup luksOpen luks.img luks
> > mkfs.ext4 /dev/mapper/luks
> > cryptsetup luksClose luks
> >
> >
> >
> Wow it works!! I cannot believe it was that easy. Also I was able to create
> a container called only test, without the .img extension to hidden the file
> among other files. Many thanks INK you are great!
>
> I was breaking my head for nothing. Well it is easy when you know how to do
> it. Otherwise... Goodby to Truecrypt now.
>
> And to make a 200 MB container?
>
For a less obscure way to create files in any size you
like seel also FAQ item 2.6. Can also be done with /dev/urandom,
but that gets really slow on larger files, see FAQ Item 2.19
for the idea how to wipe faster.
The FAQ ist at
http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. - Plato
next prev parent reply other threads:[~2014-05-16 10:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 2:58 [dm-crypt] Required kernel crypto interface not available Franz
2014-05-15 7:53 ` Arno Wagner
2014-05-15 17:35 ` Milan Broz
2014-05-15 18:55 ` Franz
2014-05-15 20:18 ` Milan Broz
2014-05-15 20:30 ` .. ink ..
[not found] ` <CAPzH-qDFgUf8NGNkv0ebbPjf-GGk+S13oZqWtD+jRO6Tv6Q3wA@mail.gmail.com>
2014-05-15 21:46 ` .. ink ..
2014-05-15 23:04 ` Franz
2014-05-15 23:43 ` .. ink ..
2014-05-16 1:58 ` Franz
2014-05-16 3:00 ` .. ink ..
2014-05-16 10:56 ` Arno Wagner
2014-05-16 13:13 ` Franz
2014-05-16 21:23 ` .. ink ..
2014-05-17 23:48 ` Franz
2014-05-16 10:54 ` Arno Wagner [this message]
2014-05-16 7:52 ` Thomas Bastiani
2014-05-16 13:31 ` Franz
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=20140516105434.GA31000@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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.