New firmware version 4.8 being released for beta testing

Hello,

I recently learned that the stable release of firmware 4.7.0 for the GL-AX1800 / Flint was canceled.

Having no other option, I flashed the 4.8.0 beta firmware. However, just like with 4.7.0, it seems that kernel cryptographic API features like cryptsetup are not working at all, and I am unable to use commands such as luksOpen.

For what it's worth, I should add that everything was working perfectly on the older firmware, version 4.6.8.

This is a significant issue for me as I was using a LUKS-encrypted storage device and sharing it on my LAN via a Samba server.

Is there any chance this will be fixed in a future release?

Thank you.

root@META-Flint:~# cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
Cannot initialize crypto backend.
PBKDF2-sha1          N/A
Cannot initialize crypto backend.
PBKDF2-sha256        N/A
Cannot initialize crypto backend.
PBKDF2-sha512        N/A
Cannot initialize crypto backend.
PBKDF2-ripemd160     N/A
Cannot initialize crypto backend.
PBKDF2-whirlpool     N/A
Cannot initialize crypto backend.
argon2i    N/A
Cannot initialize crypto backend.
argon2id   N/A
Cannot initialize crypto backend.
#     Algorithm |       Key |      Encryption |      Decryption
        aes-cbc        128b               N/A               N/A
Cannot initialize crypto backend.
    serpent-cbc        128b               N/A               N/A
Cannot initialize crypto backend.
    twofish-cbc        128b               N/A               N/A
Cannot initialize crypto backend.
        aes-cbc        256b               N/A               N/A
Cannot initialize crypto backend.
    serpent-cbc        256b               N/A               N/A
Cannot initialize crypto backend.
    twofish-cbc        256b               N/A               N/A
Cannot initialize crypto backend.
        aes-xts        256b               N/A               N/A
Cannot initialize crypto backend.
    serpent-xts        256b               N/A               N/A
Cannot initialize crypto backend.
    twofish-xts        256b               N/A               N/A
Cannot initialize crypto backend.
        aes-xts        512b               N/A               N/A
Cannot initialize crypto backend.
    serpent-xts        512b               N/A               N/A
Cannot initialize crypto backend.
    twofish-xts        512b               N/A               N/A
root@META-Flint:~# 
root@META-Flint:~# opkg list_installed | grep kmod-crypto
kmod-crypto-acompress - 5.4.164-1
kmod-crypto-aead - 5.4.164-1
kmod-crypto-cbc - 5.4.164-1
kmod-crypto-crc32c - 5.4.164-1
kmod-crypto-ecb - 5.4.164-1
kmod-crypto-gf128 - 5.4.164-1
kmod-crypto-hash - 5.4.164-1
kmod-crypto-hmac - 5.4.164-1
kmod-crypto-manager - 5.4.164-1
kmod-crypto-misc - 5.4.164-1
kmod-crypto-null - 5.4.164-1
kmod-crypto-rng - 5.4.164-1
kmod-crypto-seqiv - 5.4.164-1
kmod-crypto-sha1 - 5.4.164-1
kmod-crypto-sha256 - 5.4.164-1
kmod-crypto-sha512 - 5.4.164-1
kmod-crypto-user - 5.4.164-1
kmod-crypto-xts - 5.4.164-1
root@META-Flint:~# 
2 Likes