Gentoo Archives: gentoo-user

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