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@xxxxxxxxx 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 -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
