From: Milan Broz <gmazyland@gmail.com>
To: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] (no subject)
Date: Sun, 30 Dec 2012 00:39:11 +0100 [thread overview]
Message-ID: <50DF7F1F.1020007@gmail.com> (raw)
In-Reply-To: <CAFnMBaR3S3nmYdvN4X=R4sbLJzE+3z3pZXgRLRE_xd+mmCC_QA@mail.gmail.com>
On 12/30/2012 12:15 AM, .. ink .. wrote:
>
> i meant "tcrypt" for "truecrypt".
>
> Way to test.
> 1. create a truecrypt mapper.
> 2. call "crypt_init_by_name" to create context through the opened mapper and the function call will fail.
interesting, cryptsetup close (action_close) uses this and it doesn't fail here...
How do you create that truecrypt device? (It cannot use devices directly mapped by
truecrypt itself, cryptsetup will handle only devices which have proper DM UUID,
activated by cryptsetup).
Can you send me some code sample which fails?
Milan
next prev parent reply other threads:[~2012-12-29 23:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 22:22 [dm-crypt] (no subject) .. ink ..
2012-12-29 22:46 ` Milan Broz
2012-12-29 23:15 ` .. ink ..
2012-12-29 23:39 ` Milan Broz [this message]
2012-12-29 23:53 ` .. ink ..
2012-12-30 7:12 ` .. ink ..
2012-12-30 9:05 ` Milan Broz
2012-12-30 9:19 ` .. ink ..
2012-12-30 10:51 ` Milan Broz
2012-12-30 11:49 ` .. ink ..
-- strict thread matches above, loose matches on Subject: below --
2017-04-29 17:48 Hammad Siddiqi
2017-04-29 18:30 ` Arno Wagner
2017-04-29 19:19 ` Hammad Siddiqi
2017-05-01 17:37 ` Hammad Siddiqi
2017-05-01 18:45 ` Michael Kjörling
2017-05-01 21:01 ` Arno Wagner
2017-05-02 0:29 ` Diagon
2017-05-02 20:49 ` Arno Wagner
2016-06-18 21:40 RAS RAS
2016-06-20 7:52 ` Milan Broz
[not found] ` <1466423154.44272313@f313.i.mail.ru>
2016-06-20 12:02 ` Milan Broz
2015-05-04 14:50 janemba
2015-05-04 16:41 ` Arno Wagner
2014-02-07 13:51 Redwood Hyd
2013-03-17 21:30 .. ink ..
2012-10-10 21:11 ffrizzy
2012-10-10 21:09 ffrizzy
2012-10-10 23:13 ` Claudio Moretti
2012-10-09 6:24 ffrizzy
2012-10-09 6:21 ffrizzy
2012-09-04 1:20 Anil
2012-09-04 1:29 ` Arno Wagner
2011-09-18 10:58 Ingo Schmitt
2011-03-09 2:04 Rookcifer
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=50DF7F1F.1020007@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=mhogomchungu@gmail.com \
/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