Skip to main content ↑ ↓
Topic: Ciphers like serpent-xts-plain64 often missing from LiveCD's /proc/crypto. Why?! (Read 847 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Ciphers like serpent-xts-plain64 often missing from LiveCD's /proc/crypto. Why?!

I'm using artix-xfce-openrc-20200506-x86_64.iso LiveCD with a correct SHA256 inside a VirtualBox VM. On some boots my
Code: [Select]
cat /proc/crypto | grep "serp"
output isn't empty, allowing me to use the ciphers like serpent-xts-plain64 mentioned in this instruction - https://forum.artixlinux.org/index.php/topic,1541.0.html . However, on many boots this output is empty, and the subsequent cryptsetup command fails saying that cipher is not available. Updating linux kernel or cryptsetup doesn't help. Do you know why strong Serpent ciphers are often missing while the crappy Intel AESNI are always available?

Re: Ciphers like serpent-xts-plain64 often missing from LiveCD's /proc/crypto. Why?!

Reply #1 –
Really interesting, it seems running
Code: [Select]
cryptsetup benchmark
helps: as soon as it gets to serpent-cbc part, these Serpent ciphers instantly become available and visible with
Code: [Select]
cat /proc/crypto | grep "serp"
command. I wonder why?

Re: Ciphers like serpent-xts-plain64 often missing from LiveCD's /proc/crypto. Why?!

Reply #2 –
Well, module loaded on demand? If that's the case, put your desired module in /etc/mkinitcpio.conf's MODULES array.

Re: Ciphers like serpent-xts-plain64 often missing from LiveCD's /proc/crypto. Why?!

Reply #3 –
Quote from: nous – on
Well, module loaded on demand? If that's the case, put your desired module in /etc/mkinitcpio.conf's MODULES array.
I think it would apply only on the next reboot, but for a LiveCD all the configuration from a previous boot is lost.