Gentoo Archives: gentoo-user

From: Marko Weber | 8000 <weber@×××××××.de>
To: Gentoo User <gentoo-user@l.g.o>
Subject: [gentoo-user] cryptsetup wont use aes-xts:plain64
Date: Sat, 18 Apr 2015 10:27:38
Message-Id: a120b9c08f9b974c0e4f931e075a20e8@zbfmail.de
1 hello list,
2
3 i try to crypt a partition with cryptsetup.
4 Yes, in Kernel i had all need things i think.
5
6 CONFIG_CRYPTO=y
7 CONFIG_CRYPTO_ALGAPI=y
8 CONFIG_CRYPTO_ALGAPI2=y
9 CONFIG_CRYPTO_AEAD=m
10 CONFIG_CRYPTO_AEAD2=y
11 CONFIG_CRYPTO_BLKCIPHER=y
12 CONFIG_CRYPTO_BLKCIPHER2=y
13 CONFIG_CRYPTO_HASH=y
14 CONFIG_CRYPTO_HASH2=y
15 CONFIG_CRYPTO_RNG=m
16 CONFIG_CRYPTO_RNG2=y
17 CONFIG_CRYPTO_PCOMP=m
18 CONFIG_CRYPTO_PCOMP2=y
19 CONFIG_CRYPTO_MANAGER=y
20 CONFIG_CRYPTO_MANAGER2=y
21 CONFIG_CRYPTO_USER=m
22 # CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
23 CONFIG_CRYPTO_GF128MUL=m
24 CONFIG_CRYPTO_NULL=m
25 CONFIG_CRYPTO_PCRYPT=m
26 CONFIG_CRYPTO_WORKQUEUE=y
27 CONFIG_CRYPTO_CRYPTD=m
28 CONFIG_CRYPTO_MCRYPTD=m
29 CONFIG_CRYPTO_AUTHENC=m
30 CONFIG_CRYPTO_TEST=m
31 CONFIG_CRYPTO_ABLK_HELPER=m
32 CONFIG_CRYPTO_GLUE_HELPER_X86=m
33 CONFIG_CRYPTO_CCM=m
34 CONFIG_CRYPTO_GCM=m
35 CONFIG_CRYPTO_SEQIV=m
36 CONFIG_CRYPTO_CBC=y
37 CONFIG_CRYPTO_CTR=m
38 CONFIG_CRYPTO_CTS=m
39 CONFIG_CRYPTO_ECB=m
40 CONFIG_CRYPTO_LRW=m
41 CONFIG_CRYPTO_PCBC=m
42 CONFIG_CRYPTO_XTS=m
43 CONFIG_CRYPTO_CMAC=m
44 CONFIG_CRYPTO_HMAC=m
45 CONFIG_CRYPTO_XCBC=m
46 CONFIG_CRYPTO_VMAC=m
47 CONFIG_CRYPTO_CRC32C=y
48 CONFIG_CRYPTO_CRC32C_INTEL=m
49 CONFIG_CRYPTO_CRC32=m
50 CONFIG_CRYPTO_CRC32_PCLMUL=m
51 CONFIG_CRYPTO_CRCT10DIF=y
52 CONFIG_CRYPTO_CRCT10DIF_PCLMUL=m
53 CONFIG_CRYPTO_GHASH=m
54 CONFIG_CRYPTO_MD4=m
55 CONFIG_CRYPTO_MD5=y
56 CONFIG_CRYPTO_MICHAEL_MIC=m
57 CONFIG_CRYPTO_RMD128=m
58 CONFIG_CRYPTO_RMD160=m
59 CONFIG_CRYPTO_RMD256=m
60 CONFIG_CRYPTO_RMD320=m
61 CONFIG_CRYPTO_SHA1=m
62 CONFIG_CRYPTO_SHA1_SSSE3=m
63 CONFIG_CRYPTO_SHA256_SSSE3=m
64 CONFIG_CRYPTO_SHA512_SSSE3=m
65 CONFIG_CRYPTO_SHA1_MB=m
66 CONFIG_CRYPTO_SHA256=m
67 CONFIG_CRYPTO_SHA512=m
68 CONFIG_CRYPTO_TGR192=m
69 CONFIG_CRYPTO_WP512=m
70 CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m
71 CONFIG_CRYPTO_AES=y
72 CONFIG_CRYPTO_AES_X86_64=m
73 CONFIG_CRYPTO_AES_NI_INTEL=m
74 CONFIG_CRYPTO_ANUBIS=m
75 CONFIG_CRYPTO_ARC4=m
76 CONFIG_CRYPTO_BLOWFISH=m
77 CONFIG_CRYPTO_BLOWFISH_COMMON=m
78 CONFIG_CRYPTO_BLOWFISH_X86_64=m
79 CONFIG_CRYPTO_CAMELLIA=m
80 CONFIG_CRYPTO_CAMELLIA_X86_64=m
81 CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64=m
82 CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64=m
83 CONFIG_CRYPTO_CAST_COMMON=m
84 CONFIG_CRYPTO_CAST5=m
85 CONFIG_CRYPTO_CAST5_AVX_X86_64=m
86 CONFIG_CRYPTO_CAST6=m
87 CONFIG_CRYPTO_CAST6_AVX_X86_64=m
88 CONFIG_CRYPTO_DES=m
89 CONFIG_CRYPTO_DES3_EDE_X86_64=m
90 CONFIG_CRYPTO_FCRYPT=m
91 CONFIG_CRYPTO_KHAZAD=m
92 CONFIG_CRYPTO_SALSA20=m
93 CONFIG_CRYPTO_SALSA20_X86_64=m
94 CONFIG_CRYPTO_SEED=m
95 CONFIG_CRYPTO_SERPENT=m
96 CONFIG_CRYPTO_SERPENT_SSE2_X86_64=m
97 CONFIG_CRYPTO_SERPENT_AVX_X86_64=m
98 CONFIG_CRYPTO_SERPENT_AVX2_X86_64=m
99 CONFIG_CRYPTO_TEA=m
100 CONFIG_CRYPTO_TWOFISH=m
101 CONFIG_CRYPTO_TWOFISH_COMMON=m
102 CONFIG_CRYPTO_TWOFISH_X86_64=m
103 CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=m
104 CONFIG_CRYPTO_TWOFISH_AVX_X86_64=m
105 CONFIG_CRYPTO_DEFLATE=m
106 CONFIG_CRYPTO_ZLIB=m
107 CONFIG_CRYPTO_LZO=m
108 CONFIG_CRYPTO_LZ4=m
109 CONFIG_CRYPTO_LZ4HC=m
110 CONFIG_CRYPTO_ANSI_CPRNG=m
111 CONFIG_CRYPTO_DRBG_MENU=m
112 CONFIG_CRYPTO_DRBG_HMAC=y
113 # CONFIG_CRYPTO_DRBG_HASH is not set
114 # CONFIG_CRYPTO_DRBG_CTR is not set
115 CONFIG_CRYPTO_DRBG=m
116 CONFIG_CRYPTO_USER_API=m
117 CONFIG_CRYPTO_USER_API_HASH=m
118 CONFIG_CRYPTO_USER_API_SKCIPHER=m
119 CONFIG_CRYPTO_HASH_INFO=y
120 # CONFIG_CRYPTO_HW is not set
121
122
123 but when i try to use cryptsetup i get this:
124
125 # cryptsetup -c aes-xts:plain64 -y -s 256 luksFormat
126 /dev/mapper/VolGroup01-media2
127
128 WARNING!
129 ========
130 This will overwrite data on /dev/mapper/VolGroup01-media2 irrevocably.
131
132 Are you sure? (Type uppercase yes): YES
133 Enter passphrase:
134 Verify passphrase:
135 device-mapper: reload ioctl on failed: Invalid argument
136 Failed to setup dm-crypt key mapping for device
137 /dev/mapper/VolGroup01-media2.
138 Check that kernel supports aes-xts:plain64 cipher (check syslog for more
139 info).
140
141
142
143 Any ideas?
144
145 i built cryptsetup with this useflags:
146
147 nls openssl python udev urandom
148
149
150
151 cryptsetup --help shows me i am able to use the options
152
153 Default compiled-in device cipher parameters:
154 loop-AES: aes, Key 256 bits
155 plain: aes-cbc-essiv:sha256, Key: 256 bits, Password hashing:
156 ripemd160
157 LUKS1: aes-xts-plain64, Key: 256 bits, LUKS header hashing:
158 sha1, RNG: /dev/random
159
160
161 any help / ideas or knowledge welcome.
162
163 best regards
164
165 marko
166
167
168
169
170
171 --

Replies

Subject Author
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64 Ralf <ralf+gentoo@×××××××××××××××××××.de>
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64 Heiko Baums <lists@××××××××××××.de>
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64 Heiko Baums <lists@××××××××××××.de>
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64 Heiko Baums <lists@××××××××××××.de>
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64 Fernando Rodriguez <frodriguez.developer@×××××××.com>
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64 Marko Weber | 8000 <weber@×××××××.de>
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64 bitlord <bitlord0xff@×××××.com>