UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Userspace crypto interface not available (algif_skcipher)

    Scheduled Pinned Locked Moved Volla Phone
    2 Posts 1 Posters 644 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • S Offline
        sirrosh
        last edited by

        Hi,

        cryptsetup is unusable because of lack of userspace cipher interface modules (algif_*).
        Kernel cipher support is sufficient:

        phablet@ubuntu-phablet:~$ grep name.*aes /proc/crypto|cut -d : -f 2
         cmac(aes)
         ecb(aes)
         cbc(aes)
         aes
         xts(aes)
         ctr(aes)
         cbc(aes)
         ecb(aes)
         __xts-aes-ce
         __ctr-aes-ce
         __cbc-aes-ce
         __ecb-aes-ce
         aes
        

        but any operation fails with the same reason: "Userspace crypto wrapper cannot use cipher_name"

        # Userspace crypto wrapper cannot use aes-xts-plain64 (-95).
        

        Even the benchmarking fails:

        phablet@ubuntu-phablet:~$ cryptsetup benchmark
        # Tests are approximate using memory only (no storage IO).
        PBKDF2-sha1       297890 iterations per second
        PBKDF2-sha256     185129 iterations per second
        PBKDF2-sha512     168907 iterations per second
        PBKDF2-ripemd160  263196 iterations per second
        PBKDF2-whirlpool   61134 iterations per second
        Required kernel crypto interface not available.
        Ensure you have algif_skcipher kernel module loaded.
        

        Suggesting some specific Volla kernel config nuances...

        1 Reply Last reply Reply Quote 0
        • S Offline
          sirrosh
          last edited by

          There's an interesting discussion on the Volla's github about deliberately disabled kernel crypto interface in Volla kernel.

          I don't quite understand the reason why theese people advertize their commercial product as a (not literally) privacy and security enhanced and then turning off the crypto support in their custom built kernel.

          Did I miss something?

          Please feel free to join the discussion and/or share this information on other social platforms to get more audience involved.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post