Reinstalled from bionic-updates and confirmed working.
Thanks again to all involved in resolving this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different
This bug was fixed in the package cryptsetup - 2:2.0.2-1ubuntu1.1
---
cryptsetup (2:2.0.2-1ubuntu1.1) bionic-proposed; urgency=medium
* SRU
* Apply patch from Trent Nelson to fix cryptroot-unlock for busybox
compatibility. LP: #1651818
-- Matthias Klose Thu, 23 Aug 2018 16
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initram
works perfect!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about this bug
This was tested on Ubuntu 18.04.1 LTS and is working perfectly. Big
thanks to everyone who's worked on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs diff
Tested working! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about
Hello Linuxrider, or anyone else affected,
Accepted cryptsetup into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/cryptsetup/2:2.0.2-1ubuntu1.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Description changed:
+ SRU for bionic:
+
+ Acceptance criteria: An encrypted partition can be decrypted using
+ cryptroot-unlock.
+
+ Regression potential: It's not the default method, so unused by the
+ majority of people. Besides that the patched script runs fine in cosmic.
+
The cryptro
I had to install it manually in Bionic. Can confirm that after
installing
https://launchpad.net/ubuntu/+source/cryptsetup/2:2.0.2-1ubuntu2/+build/15039246/+files/cryptsetup_2.0.2-1ubuntu2_amd64.deb
it is fixed and unlocking works now.
--
You received this bug notification because you are a member
Will 2:2.0.2-1ubuntu2 released for Bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage n
I would also be interested to see this bug fixed in Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-un
Sorry, I'm not familiar with Ubuntu packaging.
I see:
```
"cryptsetup" versions published in Ubuntu
Cosmic (2:2.0.2-1ubuntu2): main/admin
Bionic (2:2.0.2-1ubuntu1): main/admin
```
Out of curiosity, what needs to happen for this change to make it to
Bionic?
--
You received this bug notification
Thanks Dimitri!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about this bug
This bug was fixed in the package cryptsetup - 2:2.0.2-1ubuntu2
---
cryptsetup (2:2.0.2-1ubuntu2) cosmic; urgency=medium
* Apply patch from Trent Nelson to fix cryptroot-unlock for busybox
compatibility. LP: #1651818
-- Dimitri John Ledkov 🌈 Thu, 21 Jun 2018 16:38:31
+0100
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
T
** No longer affects: busybox (Ubuntu Bionic)
** Changed in: busybox (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: busybox (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: cryptsetup (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Thanks for the confirmation @Thorsten!
Now to get some maintainer eyes on it...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to wor
@Trent Nelson: thanks for the patch! I applied it and it's working
flawlessly!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work
pls fix this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about this bug g
The attachment "Fix cryptroot-unlock for neutered Busybox env" seems to
be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchp
I took a crack at patching this. Works without complaints for
cryptroot-unlock as shipped with Ubuntu 18.04 Server.
Apply with:
$ cd /usr/share/cryptsetup/initramfs/bin/
$ sudo patch -bp1 < /path/to/cryptroot-unlock-neutered-busybox-progs.patch
$ sudo update-initramfs -uk all
Problems were:
1) B
Still an issue in bionic final beta
To unlock root partition, and maybe others like swap, run `cryptroot-
unlock`
BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# cryptroot-unlock
ps: invalid option -- 'e'
BusyBox v1.27.2 (Ubunt
Its just a shame that no one is interested in this bug. Debian Stretch
doesn't have this bug btw and bugs get fixed more quickly there ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about th
** Tags added: artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about th
18.04 so far as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about th
This bug is still present in 17.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notificat
I have developed a workaround until the bug is fixed:
https://hamy.io/blog/remote-unlocking-of-luks-encrypted-root-in-ubuntu-debian/#workaround
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Ti
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about thi
Hi,
I would like to see this issue solved asap, IMHO there are several ways of
doing that, both quite simple:
1: adapt the unlock script to only use commands and options available in the
small version of dropbox, i.e. only ps and adjusting the sed to reflect that
(seems possible after reviewing
Well of course it is not the default unlocking mechanism.
In my setup cryptroot-unlock is used to unlock remotely over dropbear.
Most probably the regex can adapted. But I have no experience with that.
When I encountered the issue I tested the script with standard busybox and it
worked. Then I com
** Changed in: cryptsetup (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile op
As far as I understand this is about the debian/initramfs/cryptroot-
unlock script, that is not used by default. (default unlocking is done
via lightdm).
Whilst indeed ps -eo pids,args is used, it doesn't have to be... if the
sed regexp is modified, I think it can just use the "ps" output, no?
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: busybox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
bu
** Tags added: yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about t
37 matches
Mail list logo
