Revision history [back]
 | 1 | initial version | posted 2018-01-12 17:10:44 +0200  |
[regression] cryptsetup stopped working on upgrade to 2.1.4.2
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=2048
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access en encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2
PLATFORM: Any
LANGUAGE: Any
| | 2 | No.2 Revision |
[regression] cryptsetup stopped working on upgrade to 2.1.4.2
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=2048
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION:
This is an edge case (I use it to access en an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2
PLATFORM: Any
LANGUAGE: Any
| | 3 | No.3 Revision |
[regression] cryptsetup stopped working on upgrade to 2.1.4.2
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=2048
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.22.1.4.2; 2.1.4.11
PLATFORM: Any
LANGUAGE: Any
| | 4 | No.4 Revision |
[regression] cryptsetup stopped working on upgrade to 2.1.4.2
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=2048
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2; 2.1.4.11
PLATFORM: Any
LANGUAGE: Any
| | 5 | No.5 Revision |
[regression] cryptsetup stopped working on upgrade to 2.1.4.22.1.4.x
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=2048
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2; 2.1.4.11
PLATFORM: Any
LANGUAGE: Any
| | 6 | No.6 Revision |
[regression] cryptsetup stopped working on upgrade to 2.1.4.x
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=2048
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE:
2.1.4.2; 2.1.4.112.1.4.11; 2.1.4.13
PLATFORM: Any
LANGUAGE: Any
| | 7 | No.7 Revision |
[regression] cryptsetup stopped working on upgrade to 2.1.4.x
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=2048
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2; 2.1.4.11; 2.1.4.13
PLATFORM: Any
LANGUAGE: Any
| | 8 | No.8 Revision |
[regression] cryptsetup stopped working on upgrade to 2.1.4.x
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=2048
count=20480
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2; 2.1.4.11; 2.1.4.13
PLATFORM: Any
LANGUAGE: Any
| | 9 | No.9 Revision |
[regression] cryptsetup stopped working on upgrade to 2.1.4.x
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=20480
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE:
2.1.4.2; 2.1.4.11; 2.1.4.132.1.4.13; 2.2.0.29
PLATFORM: Any
LANGUAGE: Any
| | 10 | No.10 Revision |
[regression] cryptsetup stopped working on upgrade to 2.1.4.xSFOS 2.1.4 & 2.2.0
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=20480
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2; 2.1.4.11; 2.1.4.13; 2.2.0.29
PLATFORM: Any
LANGUAGE: Any
| | 11 | retagged |
[regression] cryptsetup stopped working on upgrade to SFOS 2.1.4 & 2.2.0
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=20480
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2; 2.1.4.11; 2.1.4.13; 2.2.0.29
PLATFORM: Any
LANGUAGE: Any
| | 12 | No.12 Revision |
[regression] cryptsetup stopped working on upgrade to SFOS 2.1.4 & 2.2.0
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=20480
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2; 2.1.4.11; 2.1.4.13; 2.2.0.29
PLATFORM: Any
LANGUAGE: Any
| | 13 | retagged |
[regression] cryptsetup stopped working on upgrade to SFOS 2.1.4 & 2.2.0
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=20480
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2; 2.1.4.11; 2.1.4.13; 2.2.0.29
PLATFORM: Any
LANGUAGE: Any
| | 14 | No.14 Revision |
[regression] cryptsetup stopped working on upgrade to SFOS 2.1.4 & 2.2.0
This post is currently set to private in the Community Beta Group. Please note that only members of the Community Beta Group can view and edit this post content…
DESCRIPTION: New version of cryptsetup isn't working, presumably you need a kernel with CONFIG_CRYPTO_USER_API_HASH and CONFIG_CRYPTO_USER_API_SKCIPHER compiled in, but I couldn't try it.
PRECONDITIONS: (as root)
pkcon refresh
pkcon install cryptsetup
dd if=/dev/urandom of=/tmp/luksTest count=20480
STEPS TO REPRODUCE: (as root)
losetup /dev/loop1 /tmp/luksTest
cryptsetup luksFormat /dev/loop1
(enter YES, passphrase twice)
EXPECTED RESULT: Obviusly a LUKS device :)
ACTUAL RESULT: You get a "Cannot initialize crypto backend.".
ADDITIONAL INFORMATION: This is an edge case (I use it to access an encrypted file), however, it used to work _and_ SFOS may need it for encrypted disks if they choose to use cryptsetup/LUKS.
REPRODUCIBILITY: Always
BUILD VERSION & TYPE: 2.1.4.2; 2.1.4.11; 2.1.4.13; 2.2.0.29
PLATFORM: Any
LANGUAGE: Any