Linux cryptographic layer development
 help / color / mirror / Atom feed
From: jonathan.thieuleux@gmail.com
To: Milan Broz <gmazyland@gmail.com>, linux-crypto@vger.kernel.org
Subject: Re: Cipher block questions
Date: Tue, 21 Apr 2015 11:52:22 +0200	[thread overview]
Message-ID: <20150421095222.GB9043@arch.localdomain> (raw)
In-Reply-To: <55360553.5040102@gmail.com>

On Tue, Apr 21, 2015 at 10:07:47AM +0200, Milan Broz wrote:


> First, from the cryptsetup log
>   # Userspace crypto wrapper cannot use gost-xts-plain64 (-2).
> it seems that there is some problem with loading of your gost cipher implementation.
>
I relaunch the command into QEMU and I obtain "Userspace crypto wrapper cannot use
gost-xts-plain64 (-95)", and when I try with an algorithm which work fine I have the same
result "Userspace crypto wrapper cannot use aes-xts-plain64 (-95)". So, I don't
know what's the problem or where it came from. I quickly Googled the problem, but nothing.

> What key size you are using in cryptsetup (default is probably 256bit)?

Yes, the key size is 256-bit.

> LRW and XTS modes requires *two* keys in fact (tweaking+encryption).
>
> GOST should use 256bit key, so if you add --key-size 512 to your cryptsetup command
> does it help?

I already tried it, but that doesn't change anything.

--
Jonathan "Coldshell" Thieuleux
Mail : jonathan.thieuleux@gmail.com
IRC : coldshell [Freenode, OFTC]
Shaarli : https://links.stdcall.me/

"If you write interfaces with more than 4 or 5 function arguments, it's possible that you and I cannot be friends." -- David Miller

      reply	other threads:[~2015-04-21  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21  7:27 Cipher block questions jonathan.thieuleux
2015-04-21  8:07 ` Milan Broz
2015-04-21  9:52   ` jonathan.thieuleux [this message]

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=20150421095222.GB9043@arch.localdomain \
    --to=jonathan.thieuleux@gmail.com \
    --cc=gmazyland@gmail.com \
    --cc=linux-crypto@vger.kernel.org \
    /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