All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Michael Strauss <The.Whistler@live.de>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup-1.6.3/truecrypt container
Date: Sun, 29 Dec 2013 10:06:02 +0100	[thread overview]
Message-ID: <52BFE5FA.1030608@gmail.com> (raw)
In-Reply-To: <loom.20131228T054117-999@post.gmane.org>

On 12/28/2013 05:43 AM, Michael Strauss wrote:
> Hello,
> 
> can someone please enlighten me? I try to mount a truecrypt volume with
> cryptsetup-1.6.3 and get the error message:
> 
> cryptsetup -v --type tcrypt open /tmp/testconti.tc test
> Enter passphrase: 
> Required kernel crypto interface not available.
> Ensure you have algif_skcipher kernel module loaded.
> Command successful.
> 
> But it's there:
> 
> lsmod:
> 
> [...]
> algif_skcipher
> [...]
> 
> After mounting the fs it works, but why the error message?

Fixed in
http://code.google.com/p/cryptsetup/source/detail?r=8dc48776979c67cdbf4991510ead4d716f34db03

For now you can safely ignore this warning message :)

(This message is just try to help if command completely fails but it is sometimes
problematic to detect if it is missing required kernel interface or intentional kernel
module not-compiled-in system hardening...)

Thanks for reporting it,
Milan

  parent reply	other threads:[~2013-12-29  9:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28  4:43 [dm-crypt] cryptsetup-1.6.3/truecrypt container Michael Strauss
2013-12-28 23:46 ` Milan Broz
2013-12-29  9:06 ` Milan Broz [this message]
2013-12-29 16:14   ` Michael Strauss
2014-01-01 20:34     ` Milan Broz
2014-01-01 21:47       ` Michael Strauss
2014-01-01 22:30         ` Milan Broz
2014-01-02 18:02           ` Michael Strauss
2014-01-12 10:58             ` Milan Broz
2014-01-12 19:54               ` Michael Strauss

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=52BFE5FA.1030608@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=The.Whistler@live.de \
    --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.