16.04 OTA-5 kernel missing aes-xts-plain64 crypto ciphers on mako?
I have been using cryptsetup to encrypt disks on Ubuntu Touch for some years without a problem, after each update I simple need to run the following to install
sudo -i mount -o rw,remount / apt-get update apt-get install cryptsetup mount -o ro,remount /
I have upgraded a OnePlusOne to 16.04 OTA-5 and decrypted disks without issues, however on a mako, I can no longer decrypt disks:
cryptsetup luksOpen phablet.img phablet Enter passphrase for phablet.img: device-mapper: reload ioctl on failed: No such file or directory Failed to setup dm-crypt key mapping for device phablet.img. Check that kernel supports aes-xts-plain64 cipher (check syslog for more info).
Checking the kernel and ciphers (as suggested here) on the mako:
uname -a Linux ubuntu-phablet 3.4.0+ #4 SMP PREEMPT Wed Oct 10 19:51:07 UTC 2018 armv7l armv7l armv7l GNU/Linux grep name.*aes /proc/crypto|cut -d : -f 2 cbc(aes) aes
And on the OnePlusOne:
uname -a Linux ubuntu-phablet 3.4.0-Sultan-CAF #1 SMP PREEMPT Thu Oct 11 23:00:58 CEST 2018 armv7l armv7l armv7l GNU/Linux grep name.*aes /proc/crypto|cut -d : -f 2 __xts-aes-neonbs xts(aes) cbc(aes) rfc4309(ccm(aes)) ccm(aes) authenc(hmac(sha1),cbc(aes)) qcom-xts(aes) qcom-ctr(aes) qcom-cbc(aes) qcom-ecb(aes) aes xts(aes) ctr(aes) cbc(aes) __xts-aes-neonbs __ctr-aes-neonbs __cbc-aes-neonbs aes
So was a decision made to leave some crypto modules out of the mako kernel? Anyone know what happened here?
I just upgraded my Nexus 4 mako to OTA-6 and the and the lack of ciphers is unchanged.
Flohack last edited by
No we did not decide anything, kernels are mostly untouched and taken from Android or LineageOS or Cyanogenmod if possible. Every change to an Android kernel can cause problems, so we do not want to make too many changes there.
In this case we could however see if there is a huge disparity between supported ciphers and maybe unify them somehow. Please open a ticket on the ubuntu-touch tracker.
Please open a ticket on the ubuntu-touch tracker.
Thanks, I have opened a issue on GitHub.
Hey @chrisc, the issue you opened has been closed. Can you check to ensure it is working correctly?