DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "booger@post.pl" <a.stanoszek@core.com.pl>
To: dm-crypt@saout.de
Subject: [dm-crypt] cryptsetup with des or des3
Date: Sat, 12 Jun 2010 20:06:34 +0200	[thread overview]
Message-ID: <1954592487.20100612200634@core.com.pl> (raw)

Hello,

 I own the QNAP TS419 PRO NAS device which is basically:

 Linux NAS 2.6.30.6 #1 Tue Apr 27 02:06:10 CST 2010 armv5tel unknown

 It  has dm-crypt support and I am trying to encrypt my external disk,
 connected  by  esata interface. It is visible as /dev/sdy, it has one
 partition, /dev/sdy1.
 
 Unfortunatelly when I do cryptsetup luksFormat I get following error message:

Command failed: Failed to setup dm-crypt key mapping.
Check kernel for support for the aes-cbc-essiv:sha256 cipher spec and verify that /dev/sdy1 contains at least 133 sectors

Below I quote the result of cat /proc/crypto, the aes is not listed. I am ok with other encryption, but when I experiment with --cipher parameter of cryptsetup I still get the same error message. 

Can somebody quote me the right cryptsetup parameters to encypt my external drive?

name         : cbc(des)
driver       : cbc(des-generic)
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
type         : givcipher
async        : yes
blocksize    : 8
min keysize  : 8
max keysize  : 8
ivsize       : 8
geniv        : chainiv

name         : cbc(des)
driver       : cbc(des-generic)
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
type         : blkcipher
blocksize    : 8
min keysize  : 8
max keysize  : 8
ivsize       : 8
geniv        : <default>

name         : cbc(des3_ede)
driver       : cbc(des3_ede-generic)
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
type         : givcipher
async        : yes
blocksize    : 8
min keysize  : 24
max keysize  : 24
ivsize       : 8
geniv        : chainiv

name         : cbc(des3_ede)
driver       : cbc(des3_ede-generic)
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
type         : blkcipher
blocksize    : 8
min keysize  : 24
max keysize  : 24
ivsize       : 8
geniv        : <default>

name         : stdrng
driver       : krng
module       : kernel
priority     : 200
refcnt       : 2
selftest     : passed
type         : rng
seedsize     : 0

name         : crc32c
driver       : crc32c-generic
module       : kernel
priority     : 100
refcnt       : 2
selftest     : passed
type         : shash
blocksize    : 1
digestsize   : 4
descsize     : 4

name         : des3_ede
driver       : des3_ede-generic
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
type         : cipher
blocksize    : 8
min keysize  : 24
max keysize  : 24

name         : des
driver       : des-generic
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
type         : cipher
blocksize    : 8
min keysize  : 8
max keysize  : 8

name         : md5
driver       : md5-generic
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
type         : shash
blocksize    : 64
digestsize   : 16
descsize     : 88

             reply	other threads:[~2010-06-12 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-12 18:06 booger@post.pl [this message]
2010-06-26 15:29 ` [dm-crypt] cryptsetup with des or des3 Milan Broz
2010-06-26 18:39   ` Arno Wagner

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=1954592487.20100612200634@core.com.pl \
    --to=a.stanoszek@core.com.pl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox