Just try `cryptsetup benchmark`
Cheers
On 04/22/2015 06:09 AM, R0b0t1 wrote:
> AES cipher algo (AES-NI) is the fastest if you have the necessary
> hardware. Twofish cipher algo (x86_64, 3-way parallel) is a close
> second, but will slow access down slightly. Serpent is also usably
> fast.
>
> CON
AES cipher algo (AES-NI) is the fastest if you have the necessary
hardware. Twofish cipher algo (x86_64, 3-way parallel) is a close
second, but will slow access down slightly. Serpent is also usably
fast.
CONFIG_CRYPTO_AES_NI_INTEL = ~200mb/s (limited by disk in my case)
CONFIG_CRYPTO_TWOFISH_X86_
Am 21.04.2015 um 11:21 schrieb Marko Weber | 8000:
>
> Finally!
>
> ...
>
> i got it working!
>
> cryptsetup -c aes-xts-plain -h sha256 -y -s 256 luksFormat
> /dev/mapper/VolGroup01-media2
>
> But on writing a testfile of 4G with i get 22,9 Mb/sec.
> Is there a cipher/hash/keysize which alloows
Finally!
Am 2015-04-18 12:27, schrieb Marko Weber | 8000:
hello list,
i try to crypt a partition with cryptsetup.
Yes, in Kernel i had all need things i think.
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
C
Am 20.04.2015 um 15:43 schrieb Marko Weber | 8000:
> # cryptsetup -c aes-xts:plain64 -y -s 512 luksFormat
> /dev/mapper/VolGroup01-media2
As I've already mentioned in my first answer, there is a typo in this
command. Well, I actually didn't mention that it's a typo, but I gave
you the correct com
On Sat, 18 Apr 2015 12:27:15 +0200
Marko Weber | 8000 wrote:
>
> hello list,
>
> i try to crypt a partition with cryptsetup.
> Yes, in Kernel i had all need things i think.
>
> CONFIG_CRYPTO=y
...
> # CONFIG_CRYPTO_HW is not set
>
>
> but when i try to use cryptsetup i get this:
>
> # crypt
Am 2015-04-18 12:27, schrieb Marko Weber | 8000:
hello list,
i try to crypt a partition with cryptsetup.
Yes, in Kernel i had all need things i think.
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRY
hi fernando,
Am 2015-04-19 03:35, schrieb Fernando Rodriguez:
On Saturday, April 18, 2015 12:27:15 PM Marko Weber | 8000 wrote:
hello list,
i try to crypt a partition with cryptsetup.
Yes, in Kernel i had all need things i think.
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=
hi Heiko,
Am 2015-04-18 17:41, schrieb Heiko Baums:
Am 18.04.2015 um 12:27 schrieb Marko Weber | 8000:
i try to crypt a partition with cryptsetup.
Yes, in Kernel i had all need things i think.
Sorry, but I forgot some more kernel modules you need:
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
You
On Saturday, April 18, 2015 9:35:27 PM Fernando Rodriguez wrote:
> On Saturday, April 18, 2015 12:27:15 PM Marko Weber | 8000 wrote:
> >
> > hello list,
> >
> > i try to crypt a partition with cryptsetup.
> > Yes, in Kernel i had all need things i think.
> >
> > CONFIG_CRYPTO=y
> > CONFIG_CRYPTO
On Saturday, April 18, 2015 12:27:15 PM Marko Weber | 8000 wrote:
>
> hello list,
>
> i try to crypt a partition with cryptsetup.
> Yes, in Kernel i had all need things i think.
>
> CONFIG_CRYPTO=y
> CONFIG_CRYPTO_ALGAPI=y
> CONFIG_CRYPTO_ALGAPI2=y
> CONFIG_CRYPTO_AEAD=m
> CONFIG_CRYPTO_AEAD2=y
Am 18.04.2015 um 12:27 schrieb Marko Weber | 8000:
> i try to crypt a partition with cryptsetup.
> Yes, in Kernel i had all need things i think.
Sorry, but I forgot some more kernel modules you need:
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
You didn't mention them, so I don't know if you have them
Hi,
@Marko
tl;dr: it's going a bit offtopic.
Marko, try to hardcompile those modules into your kernel.
This should be the simplest fix of your problem.
On 04/18/2015 02:44 PM, Heiko Baums wrote:
> Am 18.04.2015 um 14:12 schrieb Ralf:
>
>> No. Could you please explain why you think so?
>> Even if
Am 18.04.2015 um 14:12 schrieb Ralf:
> No. Could you please explain why you think so?
> Even if your root partition is encrypted, your ramdisk could load the
> modules.
Are you sure about that? Are you sure that the necessary modules are
definitely put into the initrd and that the kernel will be
Am 18.04.2015 um 12:27 schrieb Marko Weber | 8000:
> i try to crypt a partition with cryptsetup.
> Yes, in Kernel i had all need things i think.
Depending on the password hash you're using (parameter -h) you need to
make the appropriate changes here, too:
> CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA
On 04/18/2015 02:07 PM, Heiko Baums wrote:
> You have to compile the modules which are necessary for the encryption
> method you're using directly into the kernel, not as a module, because
> the kernel needs them directly at boot time.
No. Could you please explain why you think so?
Even if your roo
Am 18.04.2015 um 12:27 schrieb Marko Weber | 8000:
> i try to crypt a partition with cryptsetup.
> Yes, in Kernel i had all need things i think.
No, you haven't.
You need to make those changes:
> CONFIG_CRYPTO_XTS=m
CONFIG_CRYPTO_XTS=y
> CONFIG_CRYPTO_AES_X86_64=m
CONFIG_CRYPTO_AES_X86_64=y
> CO
Hi Marko,
could you please paste the latest few lines of dmesg after trying to
create your volume?
And please paste the output of lsmod.
All your crypto-kernel-stuff are modules. Perhaps they're not loaded.
Check if corresponding modules are loaded.
Cheers
Ralf
On 04/18/2015 12:27 PM, Marko W
hello list,
i try to crypt a partition with cryptsetup.
Yes, in Kernel i had all need things i think.
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO
19 matches
Mail list logo
