[Bug 2037574] Re: encrypted zfs partition not mountable from live session using recovery key

[Dimitri John Ledkov]

Reading the code, it seems like after one has completed ubiquity install.
Without shutting down the machine.
One should be able to unmount /target in full, and luksClose all the things.
And then straight away test if one can luksOpen again using main password, recovery password, or recovery key-file. And there at least appears UI to set either recovery password or recovery keyfile.
The final null-byte/new-line is not quite obvious, i.e. if there is one byte missing potentially off the recovery password or not.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/2037574

Title:
  encrypted zfs partition not mountable from live session using recovery
  key

Status in ubiquity package in Ubuntu:
  New
Status in ubiquity source package in Mantic:
  New

Bug description:
  I did an install in a VM with zfs+encryption, and I enabled the
  recovery key option in the install process.

  I then booted into a live session using the same storage and attempted to mount the storage using steps from the following:
  https://radagast.ca/linux/mounting-ubuntu-encrypted-zfs.html

  It works just fine (the cryptsetup command specifically) using the
  passphrase from the install process. However, the cryptsetup command
  does NOT work when using the recovery key chosen in the install
  process.

  I copied the recovery key down at install time, and wrote the key to a
  file in the live session. I then passed it to the cryptsetup command
  using --key-file and --master-key-file command line options (with
  /path/to/recovery.key). Neither options worked. The disk is only
  mountable using the passphrase.

  I may be using the recovery key incorrectly, but if that is the case,
  there is a lack of documentation surrounding this part of the install
  process.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 17:44:13 2023
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2023-09-27 (0 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Beta amd64 (20230925)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2037574/+subscriptions